FHIR Chat · PID/PD1 Segment Community Review · v2 to FHIR

Stream: v2 to FHIR

Topic: PID/PD1 Segment Community Review


view this post on Zulip Hans Buitendijk (Jun 10 2019 at 18:39):

Today we are starting the first Community Review of the PID and PD1 segments. 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:

• PID-15 represents Primary Language. There is no clear agreement yet that the Patient.communication.preferred should be set to “true” when PID-15 is mapped into Patient.communication.language. Some believe it should. Others are concerned it may end up being used for something different than PID-15 is typically used for.

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 23 as on June 24 we start to review the comments during our project team meetings.

Any questions, please contact Craig and/or myself.


Last updated: Apr 12 2022 at 19:14 UTC