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 Wording

Currently in the Patient Generated Document Header 13. MAY contain zero or more [0..*] documentationOf (CONF:1198-28710). The code should be selected from a value set established by the document-level template for a specific type of Patient Generated Document. The functionCode SHALL be selected from value set ParticipationType 2.16.840.1.113883.1.11.10901 When indicating the performer was the primary care physician the functionCode shall be =”PCP” ? a. The documentationOf, if present, SHALL contain exactly one [1..1] serviceEvent (CONF:1198-28711). i. This serviceEvent SHOULD contain zero or one [0..1] code (CONF:1198-28712). ? ii. This serviceEvent SHOULD contain zero or more [0..*] performer (CONF:1198-28713). 1. The performer, if present, MAY contain zero or one [0..1] functionCode (CONF:1198-28714). ? 2. The performer, if present, SHALL contain exactly one [1..1] assignedEntity (CONF:1198-28715).

Proposed Wording

The value set bindings in the serviceEvent/performer need to be updated to align with the US Realm header. This serviceEvent SHOULD contain zero or more [0..*] performer 1. The performer, if present, SHALL contain exactly one [1..1] @typeCode, which SHALL be selected from ValueSet x_ServiceEventPerformer urn:oid:2.16.840.1.113883.1.11.19601 STATIC [NEED BINDING DATE] 2. The performer, if present, MAY contain zero or one [0..1] functionCode (CONF:1198-16818). a. The functionCode, if present, SHOULD contain zero or one [0..1] @code, which SHOULD be selected from ValueSet ParticipationFunction urn:oid:2.16.840.1.113883.1.11.10267 STATIC [NEED BINDING DATE] Need to use same Binding Dates as decided for the US Realm Header.