Stream: v2 to FHIR
Topic: NK1 Segment Community Review
Hans Buitendijk (Jun 19 2019 at 22:11):
Today we are starting the first Community Review of the NK1 segment. Note that NK1 could be mapped to either a RelatedPerson resource or a Contact attribute. We therefore defined two mappings: NK1[RelatedPerson] (https://docs.google.com/spreadsheets/d/1ATQBezpmTFj-ClJ2qMfAiz8sG6d_EGj3mInQl7RSlts/edit#gid=0) and NK1[Patient.contact] (https://docs.google.com/spreadsheets/d/1h9Z67WhrMJ5Va4CEY1UV_Fowy_mPHGJK-OvN6fW0GIk/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 June 30 as on July 1 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
