Stream: v2 to FHIR
Topic: MSH Segment Community Review
Hans Buitendijk (Jun 03 2019 at 21:41):
Today we are starting the first Community Review of the MSH segment (https://docs.google.com/spreadsheets/d/13pgda5xl-PwCgB9j0axyymwwv7RJVcrIzY8Ah1y1Y1M/edit#gid=0). This is NOT a ballot, rather the first opportunity to get wider input into the completeness and correctness of the proposed mapping. The intent is to solicit any comments to:
• Validate any mappings starting at the segment level, as well as for the referenced data types, which in turn may reference further data types, i.e., column F and onwards.
o Note that if the Condition cell is empty, that mapping is always meant to occur.
o Note that if a v2 field is included multiple times with different conditions, any condition that is true results in the subsequent mapping. We left the Derived Mapping column in for now, but that is expected to be removed once we are comfortable this approach works.
• Identify segment fields that may not be mapped to a FHIR attribute, but you are using, so there should be a mapping.
Additionally we have the following specific questions to provide feedback on:
• We have used three different ways to map attributes using the HD data type. We seek feedback whether one or two of those should be consistently used moving forward.
• MSH-21 allows for post-coordinated profiles to reflect by which rules the v2 message was constructed. In FHIR there is only one instance available for MessageHeader.definition requiring pre-coordination of all possible permutations as subsequent projects map specific implementation guides that use MSH-21 extensively. We seek feedback on what enhancements to request to FHIR to accommodate post-coordination, or accept the need for many pre-coordinated message definitions. To get an idea of the potential, the US Realm Lab v2 implementation guides.
• Any improvement opportunities to the format.
Comments and suggested updates should be entered in the spreadsheet against the cell to which they apply (select the cell and click on the + icon in the short cut bar). We appreciate to include in your comment the problem (if the cell is not blank) and a proposed solution/wording.
The deadline for your comments is June 16 as on June 17 we start to review the comments during our project team meetings.
Any questions, please contact Craig and/or myself.
Thank you!
Grahame Grieve (Jun 09 2019 at 06:53):
Thanks @Hans Buitendijk where should people look for documentation - in particular, there's some implied grammar in the FHIR Atttribute column (some of which I made up!): is it documented anywhere?
Hans Buitendijk (Jun 10 2019 at 18:11):
Just a reminder we have one more week available for your feedback before we put this segment, plus associated data types, into the queue for the next (first) ballot. Note that timing of the first ballot may be as soon as September as a For Comment Ballot.
Hans Buitendijk (Jun 10 2019 at 18:12):
@Grahame Grieve : I will be putting that on this page: https://confluence.hl7.org/display/OO/Segment+Mapping.
Grahame Grieve (Jun 10 2019 at 18:14):
thanks - is it possible to reference that from the spreadsheet somewhere?
Hans Buitendijk (Jun 10 2019 at 18:34):
I put the first one in for Segments on that page. Will be doing the same (although largely similar) for data types, and then for Message Structure once settled. Let me see whether GSheet allows me to put in definition tab that the column headers can jump to, or just a comment (but that latter would get confused with real comments).
Hans Buitendijk (Jun 10 2019 at 18:34):
Can you check the link I provided above and see whether anything is unclear?
Last updated: Apr 12 2022 at 19:14 UTC
