Stream: v2 to FHIR
Topic: name type -> name use
Parker Phillips (May 11 2020 at 16:17):
Hi All,
Apologies if this has been asked before. I'm trying to map the PID.field[5].component[7] (Name type) to FHIR, and was wondering if there was a widely accepted mapping already in place to the FHIR name-use value set?
Craig Newman (May 11 2020 at 18:05):
I wouldn't call it "widely accepted" by any stretch of the imagination, but the v2-to-FHIR project has developed the mapping below
image.png
A google sheet is available at https://docs.google.com/spreadsheets/d/1pK0Uutb8ppFiPxR_Mnwh5-N5WINCwTyWtgbwLBgZfGg/edit#gid=0
Parker Phillips (May 12 2020 at 17:04):
thanks for the response Craig!
Keith Boone (May 13 2020 at 04:49):
Some of the items in that sheet are clearly mappable to nullFlavor, which might imply mapping that uses data-absent-reason extension and nullFlavor mappings there-unto-apertaining.
Hans Buitendijk (May 13 2020 at 20:51):
There is a lively debate that may surface during the connectathon as well about when to use nullflavors through the dataAbsentReason extension or when to explicitly suggest it be done through the code system at hand. There is also discussion on how to convey original code if the FHIR value set/code system is "fixed" and v2 supports more values. AL1 allergy severity is an example where we are trying to work through the approach.
Last updated: Apr 12 2022 at 19:14 UTC
