When conformance statements are nested (or have subordinate clauses) the conformance statements are to be read and interpreted in hierarchical These hierarchical clauses can be interpreted as "if then, else" clauses. Thus... This structuredBody contain zero or one [0..1] component SHOULD (CONF:1098-29066) such that it contain exactly one [1..1] Plan of Treatment Section (V2) (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.2.10:2014-06-09) (CONF:1098-29067). ...is understood as: It is recommended (SHOULD) that the structureBody contains a component. If the component exists, then it must contain a Plan of Treatment Section (V2), else the component does not exist, and the conformance statement about the Plan of Treatment Section (V2) should be skipped. In the case the higher level conformance statement is a SHALL, there is no conditional clause. Thus... This structuredBody SHALL contain exactly one [1..1] component (CONF:1098-29086) such that it contain exactly one [1..1] (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.2.5.1:2014-06-09) (CONF:1098-29087). ...means that the structuredBody is always required to have a component. Cardinality The cardinality indicator (0..1, 1..1, 1..*, etc.) specifies the allowable occurrences within a document instance. The cardinality indicators are interpreted with the following format where m represents the least and n the most: “m…n” 0..1 zero or one 1..1 exactly one 1..* at one 0..* zero or more 1..n at least one and not more than n When a constraint has subordinate clauses, the scope of the cardinality of the parent constraint must be clear. In the next figure, the constraint says exactly one participant is to be present. The subordinate constraint specifies some additional characteristics of that participant.
When conformance statements are nested (or have subordinate clauses) the conformance statements are to be read and interpreted in hierarchical These hierarchical clauses can be interpreted as "if then, else" clauses. Thus... This structuredBody SHOULD contain zero or one [0..1] component (CONF:1098-29066) such that it contain exactly one [1..1] Plan of Treatment Section (V2) (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.2.10:2014-06-09) (CONF:1098-29067). ...is understood as: It is recommended (SHOULD) that the structureBody contains a component. If the component exists, then it must contain a Plan of Treatment Section (V2), else the component does not exist, and the conformance statement about the Plan of Treatment Section (V2) should be skipped. In the case the higher level conformance statement is a SHALL, there is no conditional clause. Thus... This structuredBody SHALL contain exactly one [1..1] component (CONF:1098-29086) such that it contain exactly one [1..1] (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.2.5.1:2014-06-09) (CONF:1098-29087). ...means that the structuredBody is always required to have a component. Cardinality The cardinality indicator (0..1, 1..1, 1..*, etc.) specifies the allowable occurrences within a document instance. The cardinality indicators are interpreted with the following format “m…n” where m represents the least and n the most: 0..1 zero or one 1..1 exactly one 1..* at one 0..* zero or more 1..n at least one and not more than n When a constraint has subordinate clauses, the scope of the cardinality of the parent constraint must be clear. In the next figure, the constraint says exactly one participant is to be present. The subordinate constraint specifies some additional characteristics of that participant.
CDAR2_IG_PACP_R1_DSTU1.0_2015NOV_Vol1_Introductory_Material20151108v2.docx