Stream: v2 to FHIR
Topic: OBX Community Review
Hans Buitendijk (Aug 28 2019 at 16:33):
• Today we are starting the first Community Review of the OBX segment: https://docs.google.com/spreadsheets/d/1--KYCqp4IKrDO4NyW6ieA69pJylKfnGYHoOTAU7Rkyk/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.
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 September 13 as on September 14 we start to review the comments during our Connectathon and subsequent project team meetings.
Any questions, please contact Craig and/or myself.
Hans Buitendijk (Oct 01 2019 at 20:29):
• We determined that we need to split the OBX mapping into an OBX[Observation] (https://docs.google.com/spreadsheets/d/1--KYCqp4IKrDO4NyW6ieA69pJylKfnGYHoOTAU7Rkyk/edit#gid=0) and OBX[ObservationComponent] (https://docs.google.com/spreadsheets/d/1otkCEXuRkQy7kJ--_4WycdG2yQSM7eSfT9t8AUtylck/edit#gid=0) mapping, recognizing that which one to use will be driven based on the use of the OBX in a message and conditions that may involve multiple OBX instances. Considering that, and the ballot period reducing bandwidth, we are re-starting the Community Review.
•
• 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.
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 October 11 as on October 14 we start to review the comments during our project team meetings.
Any questions, please contact Craig and/or myself.
dsh (Dec 19 2019 at 00:30):
@Hans Buitendijk Not sure if this is obvious to everyone but what HL7v2 version is being implicitly referred in the Google Doc for mapping. The reason I ask I only see upto OBX-26 here https://hl7-definition.caristix.com/v2/HL7v2.7/Fields/OBX.17 but in the spreadsheets there are references to OBX-30 so which v2 version is the mapping for?
Hans Buitendijk (Dec 19 2019 at 15:00):
@Daya Sharma : We are actually mapping to the cumulative versions, starting with v2.8.2 (soon v2.9 once published), but then include everything that was deprecated as well using the last definition for the element at the time it was deprecated. Therefore, if you are trying to map a v2.3.1, or a v.2.8.2, everything present would map as intended. Clearly, in a v2.3.1 something may be a CE and now a CWE, or an ID and now a CNE, etc. But since those updates were all backwards compatible, the positions in the message still are effectively the same when present. For the name/descriptions we do use the latest, e.g., Interpretation rather than Abnormal Flags in OBX, but again, that is not changing the mapping based on the version one starts with. For Vocabulary that works as well as we do not re-use codes and their meaning, so if deprecated, a new one should not be created with the same code but different meaning.
In the case you are seeing, Casistix provided the information on v2.7. Since that time we went up to v2.8.2 (current publication), and v2.9 is about to be published. If you only work with v2.7 at the moment, you can ignore OBX-27 onwards and check whether the mappings up to then still work.
dsh (Dec 20 2019 at 12:32):
Thanks for the detailed explanation @Hans Buitendijk
Last updated: Apr 12 2022 at 19:14 UTC
