Stream: cda to fhir
Topic: Mapping EntityNameUse
Yunwei Wang (Oct 15 2018 at 15:32):
I am trying to convert a C-CDA document to FHIR bundle. But there is a problem. C-CDA's patient.name.use comes from EntityNameUse value set (2.16.840.1.113883.1.11.15913). The patient mapping defined in FHIR points to EntityNameUseR2 (http://hl7.org/fhir/ValueSet/v3-EntityNameUseR2). And these is no ConceptMap defined for these two value set.
Lisa Nelson (Mar 07 2020 at 13:10):
@Brett Marquard @Grahame Grieve
LRN-IMO>
This is an additional example of the problem for implementers that occurs when we (the HL7 standards designers) don't take responsibility for creating the specification bridge between CDA and FHIR. Alignment (documented concepMaps between value sets) is a MUST HAVE requirement given the large-scale production use of CDA today (as evidenced by the quantity of CDA documents exchanged within the Carequality and CommonWell networks--not to mention DirectTrust and SHIEC.
Lloyd McKenzie (Mar 07 2020 at 16:16):
Actually, we don't have a responsibility. But we do have an opportunity. And the CCDA maping work is working to create this. Some of the mappings won't be great because there's misalignment. But if misalignment exists, it's generally intentional. Everything done in FHIR had full awareness of conventions in v2 and v3, so if there's a difference, it was to align with FHIR design principles.
Last updated: Apr 12 2022 at 19:14 UTC
