Specification - Extended HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes DSTU Release 2.1 - US Realm
Document Description extended per extended per TSC tracker 12437, again with 14128 and jira.hl7.org/browse/TSC-38
Existing Wording1.1.1 Properties ... 8. SHALL contain exactly one [1..1] confidentialityCode, which SHOULD be selected from ValueSet HL7 BasicConfidentialityKind urn:oid:2.16.840.1.113883.1.11.16926 STATIC (CONF:1198-5259).
Proposed Wording8. SHALL contain exactly one [1..1] confidentialityCode, which SHOULD be selected from ValueSet HL7 BasicConfidentialityKind urn:oid:2.16.840.1.113883.1.11.16926 STATIC (CONF:1198-5259) and SHALL NOT have a nullFlavor attribute. ---- We have seen cases where CCDs contained null confidentialityCode elements. There's really no valid business case for that; no one should generate a document in the first place if they aren't sure what level of confidentiality applies. So I assume those were just mistakes. We should explicitly prohibit nulls here in the specification.