Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
C-CDA R2.1 Companion Guide (CDA)
-
2.1.0.1 [deprecated]
-
Structured Documents
-
Narrative Guidance
-
Appendix B: Lot or Batch Number Observation
-
-
Brett Marquard / Marti Velezis: 19-0-0
-
Correction
-
Compatible, substantive
Description
Specification - Extended HL7 CDA® R2 Implementation Guide: C-CDA Templates for Clinical Notes Companion Guide, Release 2 STU - US Realm
Document Description extended per TSC vote https://confluence.hl7.org/x/Ujb9Aw
Existing WordingFrom the Lot or Batch Number Observation in Appendix B: 3. SHALL contain exactly one [1..1] value with @xsi:type="ST" (CONF:4437-3458). This contradicts the example immediately below it in Figure 10, where the type is "ED": It also contradicts the schematron, and presumably there's no reason that this needs to be a raw string and can't be a narrative reference or anything, so it seems like the type is supposed to be "ED" here. (Since ST is a subclass of ED, requiring an ED doesn't preclude the option of someone sending an ST, but requiring an ST does preclude the option of sending an ED.)
Proposed Wording3. SHALL contain exactly one [1..1] value with @xsi:type="ED" (CONF:4437-3458).
Existing WordingFrom the Lot or Batch Number Observation in Appendix B: 3. SHALL contain exactly one [1..1] value with @xsi:type="ST" (CONF:4437-3458). This contradicts the example immediately below it in Figure 10, where the type is "ED": It also contradicts the schematron, and presumably there's no reason that this needs to be a raw string and can't be a narrative reference or anything, so it seems like the type is supposed to be "ED" here. (Since ST is a subclass of ED, requiring an ED doesn't preclude the option of someone sending an ST, but requiring an ST does preclude the option of sending an ED.)
Proposed Wording3. SHALL contain exactly one [1..1] value with @xsi:type="ED" (CONF:4437-3458).
