Details
-
Change Request
-
Resolution: Persuasive
-
Medium High
-
US C-CDA on FHIR (FHIR)
-
1.2.0-ballot
-
Cross-Group Projects
-
STU
-
Mapping General and Structural Guidance
-
4.2.2 FHIR IDs
-
-
Jay Lyle/Michelle Currie: 10-0-0
-
Clarification
-
Non-substantive
Description
4.2.2 FHIR IDs
FHIR ids are strings: they have no system. We propose not preserving them. They could be used in II.extension but we have no way to identify a root. If someone can ascertain a reliable, repeatable way to do that, we might be able to keep the id.
In some cases, a CDA template requires an id, and the source FHIR resource may not have an identifier. In these cases, use of nullFlavor or UUID generation approach may be reasonable options.
This section seems like it shouldn't be on its own, but rather underneath the previous section of CDA id <-> FHIR identifier.
The first paragraph only applies to FHIR -> CDA conversions, and the 2nd also is talking about FHIR -> CDA conversions, but is back to the subject of CDA id and FHIR identifier, not FHIR id.
Attachments
Issue Links
- is voted on by
-
BALLOT-49134 Negative - Benjamin Flessner : 2023-May-FHIR IG CCDA R1 STU
- Withdrawn
-
BALLOT-49492 Negative - Mike Paetz : 2023-May-FHIR IG CCDA R1 STU
- Balloted
-
BALLOT-49543 Negative - Nick Hatt : 2023-May-FHIR IG CCDA R1 STU
- Balloted
-
BALLOT-49603 Negative - Matthew Moore : 2023-May-FHIR IG CCDA R1 STU
- Balloted