Details
-
Change Request
-
Resolution: Not Persuasive
-
Medium
-
C-CDA Templates Clinical Notes (CDA)
-
3.0.0-ballot
-
Structured Documents
-
STU
-
Care Experience Preference
-
-
Jean Duteau / Brett Marquard: 16-0-1
Description
Should this design narrow the relevant data absent reasons allowed?
What would be the best way to align these designs?
When shaping the code in an observation, it seems to make more sense to keep the nullFlavor attribute as an allowed structure, but constrain it to use the same Data Absent Reason VS and used in the DataAbsentReason element of the FHIR profile.
Seems like we could make a better alignment choice here, and then create a design principle which could be applied elsewhere.
Attachments
Issue Links
- is voted on by
-
BALLOT-58053 Negative - Lisa R. Nelson : 2024-Jan-CDAR2 IG CCDA CLINNOTES E1 STU
- Withdrawn
- relates to
-
CDA-20893 If code element carries a nullFlavor, then the value element should not be present.
- Duplicate
-
FHIR-43542 Should this design narrow the relevant data absent reasons allowed?
- Resolved - No Change
-
CDA-20889 Care Experience Preference code element should not permit nullFlavors
- Duplicate