Details
-
Technical Correction
-
Resolution: Persuasive
-
Medium
-
US Core (FHIR)
-
4.0.0
-
Cross-Group Projects
-
US Core CarePlan Profile
-
Differential Table and Snapshot Table in section 10.85.1.3 Formal Views of Profile Content
-
-
Correction
Description
The Differential Table has a Binding: US Core Narrative Status link and for the US Core use case, that value set correctly contains 2 concepts ("additional" and "generated"); however, the Binding is incorrectly tied to the CarePlan.text.div element vs. the CarePlan.text.status element.
The Snapshot Table has a Binding: NarrativeStatus link and that value set contains 4 concepts ("generated","extensions","additional" and "empty").
Is the difference between the Differential Table vs.Snapshot Table ** CarePlan.text.status value set bindings described above expected, or should both tables have that element bound to the same value set (http://hl7.org/fhir/us/core/STU4/ValueSet-us-core-narrative-status.html)?
Regardless, shouldn't the Binding: US Core Narrative Status link on the Differential Table be tied to the CarePlan.text.status element vs. the CarePlan.text.div element, and shouldn't the list of codes in the Description and Constraints column for the CarePlan.text.status element only contain the "additional" and "generated" code values vs. "generated | extensions | additional | empty"?