PASSED PASSED rmim026 /ClinicalDocument if regionOfInterest is target of a renderMultimedia then it shall have exactly one ObservationMedia and not an ExternalObservation (RMIM-026) cdabasic-ClinicalDocumentSpec-rmim026 Context rmim051 /ClinicalDocument The Section.id element is unique into the CDA Document (RMIM-051) cdabasic-ClinicalDocumentSpec-rmim051 Cardinality rmim055 /ClinicalDocument ParentDocument/id SHALL be different from the id of ClinicalDocument/id, when the typeCode=RPLC or typeCode=APND (RMIM-055) cdabasic-ClinicalDocumentSpec-rmim055 Context rmim056_1 /ClinicalDocument All documents in a chain of replacement SHALL have the same setId (RMIM-056) cdabasic-ClinicalDocumentSpec-rmim056_1 Fixed value rmim056_2 /ClinicalDocument All documents in a chain of replacement SHALL have a versionNumber incrementing (RMIM-056) cdabasic-ClinicalDocumentSpec-rmim056_2 Fixed value rmim063 /ClinicalDocument The languageCode shall be from the valueSet HumanLanguage (RMIM-063) cdabasic-ClinicalDocumentSpec-rmim063 Vocabulary rmim064 /ClinicalDocument copyTime SHOULD NOT be used (4.2.1.9, [1]) (RMIM-064) cdabasic-ClinicalDocumentSpec-rmim064 Fixed value rmim065 /ClinicalDocument Only these combination of relatedDocument MAY be present : (APND), (RPLC), (XFR), (XFRM, RPLC), (XFRM, APND) (RMIM-065) cdabasic-ClinicalDocumentSpec-rmim065 Fixed value rmim109 /ClinicalDocument renderMultimedia@referencedObject SHALL have a value of ObservationMultimedia or RegionOfInterest within the same document (RMIM-109) cdabasic-ClinicalDocumentSpec-rmim109 Fixed value rmim110 /ClinicalDocument renderMultimedia SHALL refer to a single observationMedia, or to multiple regionOfInterest (RMIM-110) cdabasic-ClinicalDocumentSpec-rmim110 Cardinality rmim113 /ClinicalDocument the footnoteref SHALL reference a footnote in the same document (RMIM-113) cdabasic-ClinicalDocumentSpec-rmim113 Mandatory rmim114 /ClinicalDocument Ordered list style SHOULD be used only on the element list, with listType=ordered (RMIM-114) cdabasic-ClinicalDocumentSpec-rmim114 Fixed value rmim115 /ClinicalDocument Unordered list style SHOULD be used only on the element list, with listType=unordered (RMIM-115) cdabasic-ClinicalDocumentSpec-rmim115 Fixed value rmim079_1 /ClinicalDocument/recordTarget[0]/patientRole PatientRole SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-079, RIM-011) cdabasic-PatientRoleSpec-rmim079_1 Context rmim079_2 /ClinicalDocument/recordTarget[0]/patientRole The ids elements of PatientRole SHALL be distinct (RMIM-079, RIM-012) cdabasic-PatientRoleSpec-rmim079_2 Context rmim079_3 /ClinicalDocument/recordTarget[0]/patientRole PatientRole SHALL NOT have addr element with nullFlavor, if there are other addr (RMIM-079, RIM-016) cdabasic-PatientRoleSpec-rmim079_3 Context rmim079_4 /ClinicalDocument/recordTarget[0]/patientRole The addr elements of PatientRole SHALL be distinct (RMIM-079, RIM-017) cdabasic-PatientRoleSpec-rmim079_4 Context rmim079_5 /ClinicalDocument/recordTarget[0]/patientRole PatientRole SHALL NOT have telecom element with nullFlavor, if there are other telecom elements which are not null (RMIM-079, RIM-018) cdabasic-PatientRoleSpec-rmim079_5 Context rmim079_6 /ClinicalDocument/recordTarget[0]/patientRole The telecom elements of PatientRole SHALL be distinct (RMIM-079, RIM-019) cdabasic-PatientRoleSpec-rmim079_6 Context rmim080 /ClinicalDocument/recordTarget[0]/patientRole If patientRole has not a null of flavor and its enclosing recordTarget has not a null of flavor, it SHALL have a patient entity, or a providerOrganization (RMIM-080) cdabasic-PatientRoleSpec-rmim080 Context rmim101_1 /ClinicalDocument/recordTarget[0]/patientRole/patient Patient SHALL NOT have name element with nullFlavor, if there are other name (RMIM-101, RIM-022) cdabasic-PatientSpec-rmim101_1 Context rmim101_2 /ClinicalDocument/recordTarget[0]/patientRole/patient The name elements of Patient SHALL be distinct (RMIM-101, RIM-023) cdabasic-PatientSpec-rmim101_2 Context rmim102 /ClinicalDocument/recordTarget[0]/patientRole/patient id element SHOULD NOT be present (RMIM-102) cdabasic-PatientSpec-rmim102 Cardinality rmim078 /ClinicalDocument/author[0] If assignedAuthor has not a null of flavor and its enclosing author has not a null of flavor, it SHALL have an assignedAuthoringDevice or assignedPerson or a representedOrganization element (RMIM-078) cdabasic-AuthorSpec-rmim078 Context rmim077_1 /ClinicalDocument/author[0]/assignedAuthor AssignedAuthor SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-077, RIM-011) cdabasic-AssignedAuthorSpec-rmim077_1 Context rmim077_2 /ClinicalDocument/author[0]/assignedAuthor The ids elements of AssignedAuthor SHALL be distinct (RMIM-077, RIM-012) cdabasic-AssignedAuthorSpec-rmim077_2 Context rmim077_3 /ClinicalDocument/author[0]/assignedAuthor AssignedAuthor SHALL NOT have addr element with nullFlavor, if there are other addr (RMIM-077, RIM-016) cdabasic-AssignedAuthorSpec-rmim077_3 Context rmim077_4 /ClinicalDocument/author[0]/assignedAuthor The addr elements of AssignedAuthor SHALL be distinct (RMIM-077, RIM-017) cdabasic-AssignedAuthorSpec-rmim077_4 Context rmim097_1 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson Person SHALL NOT have name element with nullFlavor, if there are other name (RMIM-097, RIM-022) cdabasic-PersonSpec-rmim097_1 Context rmim097_2 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson The name elements of Person SHALL be distinct (RMIM-097, RIM-023) cdabasic-PersonSpec-rmim097_2 Context rmim094_1 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization Organization SHALL NOT have id element with nullFlavor, if there are other ids (RMIM-094, RIM-020) cdabasic-OrganizationSpec-rmim094_1 Context rmim094_2 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization The ids elements of Organization SHALL be distinct (RMIM-094, RIM-021) cdabasic-OrganizationSpec-rmim094_2 Context rmim094_3 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization Organization SHALL NOT have name element with nullFlavor, if there are other name (RMIM-094, RIM-022) cdabasic-OrganizationSpec-rmim094_3 Context rmim094_4 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization The name elements of Organizarion SHALL be distinct (RMIM-094, RIM-023) cdabasic-OrganizationSpec-rmim094_4 Context rmim094_5 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization Organization SHALL NOT have telecom element with nullFlavor, if there are other telecom elements which are not null (RMIM-094, RIM-024) cdabasic-OrganizationSpec-rmim094_5 Context rmim094_6 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization The telecom elements of Entity SHALL be distinct (RMIM-094, RIM-025) cdabasic-OrganizationSpec-rmim094_6 Context rmim095 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization Organization SHALL NOT have addr element with nullFlavor, if there are other (RMIM-095) cdabasic-OrganizationSpec-rmim095 Context rmim096 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization The addr elements of Organization SHALL be distinct (RMIM-096) cdabasic-OrganizationSpec-rmim096 Context rmim099_1 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization CustodianOrganization SHALL NOT have id element with nullFlavor, if there are other ids (RMIM-099, RIM-020) cdabasic-CustodianOrganizationSpec-rmim099_1 Context rmim099_2 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization The ids elements of CustodianOrganization SHALL be distinct (RMIM-099, RIM-021) cdabasic-CustodianOrganizationSpec-rmim099_2 Context rmim100 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization id element SHALL be present and is mandatory (RMIM-100) cdabasic-CustodianOrganizationSpec-rmim100 Mandatory rmim057_1 /ClinicalDocument/documentationOf[0]/serviceEvent ServiceEvent SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-057, RIM-001) cdabasic-ServiceEventSpec-rmim057_1 Context rmim057_2 /ClinicalDocument/documentationOf[0]/serviceEvent The ids elements of ServiceEvent SHALL be distinct (RMIM-057, RIM-002) cdabasic-ServiceEventSpec-rmim057_2 Context rmim072_1 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity AssignedEntity SHALL NOT have id element with nullFlavor, if there are other ids element (RMIM-072, RIM-011) cdabasic-AssignedEntitySpec-rmim072_1 Context rmim072_2 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity The ids elements of AssignedEntity SHALL be distinct (RMIM-072, RIM-012) cdabasic-AssignedEntitySpec-rmim072_2 Context rmim072_3 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity AssignedEntity SHALL NOT have addr element with nullFlavor, if there are other addr (RMIM-072, RIM-016) cdabasic-AssignedEntitySpec-rmim072_3 Context rmim072_4 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity The addr elements of AssignedEntity SHALL be distinct (RMIM-072, RIM-017) cdabasic-AssignedEntitySpec-rmim072_4 Context rmim073 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity If assignedEntity has not a null of flavor and its enclosing participation has not a null of flavor, it SHALL have an assignedPerson or a representedOrganization(RMIM-073) cdabasic-AssignedEntitySpec-rmim073 Context rmim097_1 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson Person SHALL NOT have name element with nullFlavor, if there are other name (RMIM-097, RIM-022) cdabasic-PersonSpec-rmim097_1 Context rmim097_2 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson The name elements of Person SHALL be distinct (RMIM-097, RIM-023) cdabasic-PersonSpec-rmim097_2 Context rmim094_1 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization Organization SHALL NOT have id element with nullFlavor, if there are other ids (RMIM-094, RIM-020) cdabasic-OrganizationSpec-rmim094_1 Context rmim094_2 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization The ids elements of Organization SHALL be distinct (RMIM-094, RIM-021) cdabasic-OrganizationSpec-rmim094_2 Context rmim094_3 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization Organization SHALL NOT have name element with nullFlavor, if there are other name (RMIM-094, RIM-022) cdabasic-OrganizationSpec-rmim094_3 Context rmim094_4 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization The name elements of Organizarion SHALL be distinct (RMIM-094, RIM-023) cdabasic-OrganizationSpec-rmim094_4 Context rmim094_5 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization Organization SHALL NOT have telecom element with nullFlavor, if there are other telecom elements which are not null (RMIM-094, RIM-024) cdabasic-OrganizationSpec-rmim094_5 Context rmim094_6 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization The telecom elements of Entity SHALL be distinct (RMIM-094, RIM-025) cdabasic-OrganizationSpec-rmim094_6 Context rmim095 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization Organization SHALL NOT have addr element with nullFlavor, if there are other (RMIM-095) cdabasic-OrganizationSpec-rmim095 Context rmim096 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization The addr elements of Organization SHALL be distinct (RMIM-096) cdabasic-OrganizationSpec-rmim096 Context rmim049 /ClinicalDocument/component/structuredBody The languageCode shall be from the valueSet HumanLanguage (RMIM-049) cdabasic-StructuredBodySpec-rmim049 Vocabulary rmim050 /ClinicalDocument/component/structuredBody/component[0]/section The languageCode shall be from the valueSet HumanLanguage (RMIM-050) cdabasic-SectionSpec-rmim050 Vocabulary rmim052 /ClinicalDocument/component/structuredBody/component[0]/section Section.text SHALL be specified, as it is a required element (RMIM-052) cdabasic-SectionSpec-rmim052 Mandatory rmim066 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0] When entry@typeCode=DRIV, the section containing the entry SHALL contain a text element (RMIM-066) cdabasic-EntrySpec-rmim066 Datatype rmim013_1 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer Organizer SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-013, RIM-001) cdabasic-OrganizerSpec-rmim013_1 Context rmim013_2 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer The ids elements of Organizer SHALL be distinct (RMIM-013, RIM-002) cdabasic-OrganizerSpec-rmim013_2 Context rmim004_1 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation Observation SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-004, RIM-001) cdabasic-ObservationSpec-rmim004_1 Context rmim004_2 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation The ids elements of Observation SHALL be distinct (RMIM-004, RIM-002) cdabasic-ObservationSpec-rmim004_2 Context rmim004_3 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation The statusCode if presents SHALL be from the valueSet ActStatus (RMIM-004, RIM-003) cdabasic-ObservationSpec-rmim004_3 Vocabulary rmim004_4 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation Observation SHALL NOT have interpretationCode element with nullFlavor, if there are other interpretationCode elements which are not null (RMIM-004, RIM-004) cdabasic-ObservationSpec-rmim004_4 Context rmim004_5 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation The interpretationCode elements of Act SHALL be distinct (RMIM-004, RIM-005) cdabasic-ObservationSpec-rmim004_5 Context rmim004_6 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation Observation SHALL NOT have methodCode element with nullFlavor, if there are other methodCode elements which are not null (RMIM-004, RIM-006) cdabasic-ObservationSpec-rmim004_6 Context rmim004_7 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation The methodCode elements of Act SHALL be distinct (RMIM-004, RIM-007) cdabasic-ObservationSpec-rmim004_7 Context rmim004_8 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation Observation SHALL NOT have targetSiteCode element with nullFlavor, if there are other targetSiteCode elements which are not null (RMIM-004, RIM-008) cdabasic-ObservationSpec-rmim004_8 Context rmim004_9 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation The targetSiteCode elements of Act SHALL be distinct (RMIM-004, RIM-009) cdabasic-ObservationSpec-rmim004_9 Context rmim005 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation The languageCode shall be from the valueSet HumanLanguage (RMIM-005) cdabasic-ObservationSpec-rmim005 Vocabulary rmim009 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation Numeric values SHALL NOT be communicated in Observation/value as a simple String (RMIM-009) cdabasic-ObservationSpec-rmim009 Datatype rmim010 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation CS datatype SHALL NOT be used in value element, because only datatypes with (RMIM-010) cdabasic-ObservationSpec-rmim010 Datatype rmim011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation interpretationCode values SHALL be from the valueSet ObservationInterpretation (RMIM-011) cdabasic-ObservationSpec-rmim011 Vocabulary rmim050 /ClinicalDocument/component/structuredBody/component[1]/section The languageCode shall be from the valueSet HumanLanguage (RMIM-050) cdabasic-SectionSpec-rmim050 Vocabulary rmim052 /ClinicalDocument/component/structuredBody/component[1]/section Section.text SHALL be specified, as it is a required element (RMIM-052) cdabasic-SectionSpec-rmim052 Mandatory rmim066 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0] When entry@typeCode=DRIV, the section containing the entry SHALL contain a text element (RMIM-066) cdabasic-EntrySpec-rmim066 Datatype rmim013_1 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer Organizer SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-013, RIM-001) cdabasic-OrganizerSpec-rmim013_1 Context rmim013_2 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer The ids elements of Organizer SHALL be distinct (RMIM-013, RIM-002) cdabasic-OrganizerSpec-rmim013_2 Context rmim078 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0] If assignedAuthor has not a null of flavor and its enclosing author has not a null of flavor, it SHALL have an assignedAuthoringDevice or assignedPerson or a representedOrganization element (RMIM-078) cdabasic-AuthorSpec-rmim078 Context rmim077_1 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor AssignedAuthor SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-077, RIM-011) cdabasic-AssignedAuthorSpec-rmim077_1 Context rmim077_2 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor The ids elements of AssignedAuthor SHALL be distinct (RMIM-077, RIM-012) cdabasic-AssignedAuthorSpec-rmim077_2 Context rmim077_3 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor AssignedAuthor SHALL NOT have addr element with nullFlavor, if there are other addr (RMIM-077, RIM-016) cdabasic-AssignedAuthorSpec-rmim077_3 Context rmim077_4 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor The addr elements of AssignedAuthor SHALL be distinct (RMIM-077, RIM-017) cdabasic-AssignedAuthorSpec-rmim077_4 Context rmim097_1 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson Person SHALL NOT have name element with nullFlavor, if there are other name (RMIM-097, RIM-022) cdabasic-PersonSpec-rmim097_1 Context rmim097_2 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson The name elements of Person SHALL be distinct (RMIM-097, RIM-023) cdabasic-PersonSpec-rmim097_2 Context rmim094_1 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization Organization SHALL NOT have id element with nullFlavor, if there are other ids (RMIM-094, RIM-020) cdabasic-OrganizationSpec-rmim094_1 Context rmim094_2 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization The ids elements of Organization SHALL be distinct (RMIM-094, RIM-021) cdabasic-OrganizationSpec-rmim094_2 Context rmim094_3 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization Organization SHALL NOT have name element with nullFlavor, if there are other name (RMIM-094, RIM-022) cdabasic-OrganizationSpec-rmim094_3 Context rmim094_4 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization The name elements of Organizarion SHALL be distinct (RMIM-094, RIM-023) cdabasic-OrganizationSpec-rmim094_4 Context rmim094_5 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization Organization SHALL NOT have telecom element with nullFlavor, if there are other telecom elements which are not null (RMIM-094, RIM-024) cdabasic-OrganizationSpec-rmim094_5 Context rmim094_6 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization The telecom elements of Entity SHALL be distinct (RMIM-094, RIM-025) cdabasic-OrganizationSpec-rmim094_6 Context rmim095 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization Organization SHALL NOT have addr element with nullFlavor, if there are other (RMIM-095) cdabasic-OrganizationSpec-rmim095 Context rmim096 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization The addr elements of Organization SHALL be distinct (RMIM-096) cdabasic-OrganizationSpec-rmim096 Context rmim004_1 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation Observation SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-004, RIM-001) cdabasic-ObservationSpec-rmim004_1 Context rmim004_2 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation The ids elements of Observation SHALL be distinct (RMIM-004, RIM-002) cdabasic-ObservationSpec-rmim004_2 Context rmim004_3 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation The statusCode if presents SHALL be from the valueSet ActStatus (RMIM-004, RIM-003) cdabasic-ObservationSpec-rmim004_3 Vocabulary rmim004_4 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation Observation SHALL NOT have interpretationCode element with nullFlavor, if there are other interpretationCode elements which are not null (RMIM-004, RIM-004) cdabasic-ObservationSpec-rmim004_4 Context rmim004_5 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation The interpretationCode elements of Act SHALL be distinct (RMIM-004, RIM-005) cdabasic-ObservationSpec-rmim004_5 Context rmim004_6 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation Observation SHALL NOT have methodCode element with nullFlavor, if there are other methodCode elements which are not null (RMIM-004, RIM-006) cdabasic-ObservationSpec-rmim004_6 Context rmim004_7 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation The methodCode elements of Act SHALL be distinct (RMIM-004, RIM-007) cdabasic-ObservationSpec-rmim004_7 Context rmim004_8 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation Observation SHALL NOT have targetSiteCode element with nullFlavor, if there are other targetSiteCode elements which are not null (RMIM-004, RIM-008) cdabasic-ObservationSpec-rmim004_8 Context rmim004_9 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation The targetSiteCode elements of Act SHALL be distinct (RMIM-004, RIM-009) cdabasic-ObservationSpec-rmim004_9 Context rmim005 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation The languageCode shall be from the valueSet HumanLanguage (RMIM-005) cdabasic-ObservationSpec-rmim005 Vocabulary rmim009 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation Numeric values SHALL NOT be communicated in Observation/value as a simple String (RMIM-009) cdabasic-ObservationSpec-rmim009 Datatype rmim010 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation CS datatype SHALL NOT be used in value element, because only datatypes with (RMIM-010) cdabasic-ObservationSpec-rmim010 Datatype rmim011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation interpretationCode values SHALL be from the valueSet ObservationInterpretation (RMIM-011) cdabasic-ObservationSpec-rmim011 Vocabulary rmim050 /ClinicalDocument/component/structuredBody/component[2]/section The languageCode shall be from the valueSet HumanLanguage (RMIM-050) cdabasic-SectionSpec-rmim050 Vocabulary rmim052 /ClinicalDocument/component/structuredBody/component[2]/section Section.text SHALL be specified, as it is a required element (RMIM-052) cdabasic-SectionSpec-rmim052 Mandatory rmim066 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0] When entry@typeCode=DRIV, the section containing the entry SHALL contain a text element (RMIM-066) cdabasic-EntrySpec-rmim066 Datatype rmim014_1 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure Procedure SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-014, RIM-001) cdabasic-ProcedureSpec-rmim014_1 Context rmim014_2 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure The ids elements of Procedure SHALL be distinct (RMIM-014, RIM-002) cdabasic-ProcedureSpec-rmim014_2 Context rmim014_3 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure The statusCode if presents SHALL be from the valueSet ActStatus (RMIM-014, RIM-003) cdabasic-ProcedureSpec-rmim014_3 Vocabulary rmim015 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure The languageCode shall be from the valueSet HumanLanguage (RMIM-015) cdabasic-ProcedureSpec-rmim015 Vocabulary rmim017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure Procedure SHALL NOT have methodCode element with nullFlavor, if there are other methodCode elements which are not null (RMIM-017) cdabasic-ProcedureSpec-rmim017 Context rmim018 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure The methodCode elements of Procedure SHALL be distinct (RMIM-018) cdabasic-ProcedureSpec-rmim018 Context rmim019 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure Procedure SHALL NOT have approachSiteCode element with nullFlavor, if there are other approachSiteCode elements which are not null (RMIM-019) cdabasic-ProcedureSpec-rmim019 Context rmim020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure The approachSiteCode elements of Procedure SHALL be distinct (RMIM-020) cdabasic-ProcedureSpec-rmim020 Context rmim021 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure Procedure SHALL NOT have targetSiteCode element with nullFlavor, if there are other targetSiteCode elements which are not null (RMIM-021) cdabasic-ProcedureSpec-rmim021 Context rmim022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure The targetSiteCode elements of Procedure SHALL be distinct (RMIM-022) cdabasic-ProcedureSpec-rmim022 Context rmim066 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1] When entry@typeCode=DRIV, the section containing the entry SHALL contain a text element (RMIM-066) cdabasic-EntrySpec-rmim066 Datatype rmim014_1 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure Procedure SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-014, RIM-001) cdabasic-ProcedureSpec-rmim014_1 Context rmim014_2 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure The ids elements of Procedure SHALL be distinct (RMIM-014, RIM-002) cdabasic-ProcedureSpec-rmim014_2 Context rmim014_3 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure The statusCode if presents SHALL be from the valueSet ActStatus (RMIM-014, RIM-003) cdabasic-ProcedureSpec-rmim014_3 Vocabulary rmim015 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure The languageCode shall be from the valueSet HumanLanguage (RMIM-015) cdabasic-ProcedureSpec-rmim015 Vocabulary rmim017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure Procedure SHALL NOT have methodCode element with nullFlavor, if there are other methodCode elements which are not null (RMIM-017) cdabasic-ProcedureSpec-rmim017 Context rmim018 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure The methodCode elements of Procedure SHALL be distinct (RMIM-018) cdabasic-ProcedureSpec-rmim018 Context rmim019 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure Procedure SHALL NOT have approachSiteCode element with nullFlavor, if there are other approachSiteCode elements which are not null (RMIM-019) cdabasic-ProcedureSpec-rmim019 Context rmim020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure The approachSiteCode elements of Procedure SHALL be distinct (RMIM-020) cdabasic-ProcedureSpec-rmim020 Context rmim021 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure Procedure SHALL NOT have targetSiteCode element with nullFlavor, if there are other targetSiteCode elements which are not null (RMIM-021) cdabasic-ProcedureSpec-rmim021 Context rmim022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure The targetSiteCode elements of Procedure SHALL be distinct (RMIM-022) cdabasic-ProcedureSpec-rmim022 Context rmim050 /ClinicalDocument/component/structuredBody/component[3]/section The languageCode shall be from the valueSet HumanLanguage (RMIM-050) cdabasic-SectionSpec-rmim050 Vocabulary rmim052 /ClinicalDocument/component/structuredBody/component[3]/section Section.text SHALL be specified, as it is a required element (RMIM-052) cdabasic-SectionSpec-rmim052 Mandatory rmim066 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0] When entry@typeCode=DRIV, the section containing the entry SHALL contain a text element (RMIM-066) cdabasic-EntrySpec-rmim066 Datatype rmim032_1 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration SubstanceAdministration SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-032, RIM-001) cdabasic-SubstanceAdministrationSpec-rmim032_1 Context rmim032_2 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration The ids elements of SubstanceAdministration SHALL be distinct (RMIM-032, RIM-002) cdabasic-SubstanceAdministrationSpec-rmim032_2 Context rmim032_3 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration The statusCode if presents SHALL be from the valueSet ActStatus (RMIM-032, RIM-003) cdabasic-SubstanceAdministrationSpec-rmim032_3 Vocabulary rmim033 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration The approachSiteCode elements of SubstanceAdministration SHALL be distinct (RMIM-033) cdabasic-SubstanceAdministrationSpec-rmim033 Context rmim034 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration SubstanceAdministration SHALL NOT have approachSiteCode element with nullFlavor, if there are other approachSiteCode elements which are not null (RMIM-034) cdabasic-SubstanceAdministrationSpec-rmim034 Context rmim089_1 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct ManufacturedProduct SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-089, RIM-011) cdabasic-ManufacturedProductSpec-rmim089_1 Context rmim089_2 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct The ids elements of ManufacturedProduct SHALL be distinct (RMIM-089, RIM-012) cdabasic-ManufacturedProductSpec-rmim089_2 Context rmim001_1 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act Act SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-001, RIM-001) cdabasic-ActSpec-rmim001_1 Context rmim001_2 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act The ids elements of Act SHALL be distinct (RMIM-001, RIM-002) cdabasic-ActSpec-rmim001_2 Context rmim001_3 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act The statusCode if presents SHALL be from the valueSet ActStatus (RMIM-001, RIM-003) cdabasic-ActSpec-rmim001_3 Vocabulary rmim002 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act The languageCode shall be from the valueSet HumanLanguage (RMIM-002) cdabasic-ActSpec-rmim002 Vocabulary rmim050 /ClinicalDocument/component/structuredBody/component[4]/section The languageCode shall be from the valueSet HumanLanguage (RMIM-050) cdabasic-SectionSpec-rmim050 Vocabulary rmim052 /ClinicalDocument/component/structuredBody/component[4]/section Section.text SHALL be specified, as it is a required element (RMIM-052) cdabasic-SectionSpec-rmim052 Mandatory rmim066 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0] When entry@typeCode=DRIV, the section containing the entry SHALL contain a text element (RMIM-066) cdabasic-EntrySpec-rmim066 Datatype rmim032_1 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration SubstanceAdministration SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-032, RIM-001) cdabasic-SubstanceAdministrationSpec-rmim032_1 Context rmim032_2 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration The ids elements of SubstanceAdministration SHALL be distinct (RMIM-032, RIM-002) cdabasic-SubstanceAdministrationSpec-rmim032_2 Context rmim032_3 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration The statusCode if presents SHALL be from the valueSet ActStatus (RMIM-032, RIM-003) cdabasic-SubstanceAdministrationSpec-rmim032_3 Vocabulary rmim033 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration The approachSiteCode elements of SubstanceAdministration SHALL be distinct (RMIM-033) cdabasic-SubstanceAdministrationSpec-rmim033 Context rmim034 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration SubstanceAdministration SHALL NOT have approachSiteCode element with nullFlavor, if there are other approachSiteCode elements which are not null (RMIM-034) cdabasic-SubstanceAdministrationSpec-rmim034 Context rmim089_1 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct ManufacturedProduct SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-089, RIM-011) cdabasic-ManufacturedProductSpec-rmim089_1 Context rmim089_2 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct The ids elements of ManufacturedProduct SHALL be distinct (RMIM-089, RIM-012) cdabasic-ManufacturedProductSpec-rmim089_2 Context rmim050 /ClinicalDocument/component/structuredBody/component[5]/section The languageCode shall be from the valueSet HumanLanguage (RMIM-050) cdabasic-SectionSpec-rmim050 Vocabulary rmim052 /ClinicalDocument/component/structuredBody/component[5]/section Section.text SHALL be specified, as it is a required element (RMIM-052) cdabasic-SectionSpec-rmim052 Mandatory rmim066 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0] When entry@typeCode=DRIV, the section containing the entry SHALL contain a text element (RMIM-066) cdabasic-EntrySpec-rmim066 Datatype rmim001_1 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act Act SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-001, RIM-001) cdabasic-ActSpec-rmim001_1 Context rmim001_2 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act The ids elements of Act SHALL be distinct (RMIM-001, RIM-002) cdabasic-ActSpec-rmim001_2 Context rmim001_3 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act The statusCode if presents SHALL be from the valueSet ActStatus (RMIM-001, RIM-003) cdabasic-ActSpec-rmim001_3 Vocabulary rmim002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act The languageCode shall be from the valueSet HumanLanguage (RMIM-002) cdabasic-ActSpec-rmim002 Vocabulary rmim072_1 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity AssignedEntity SHALL NOT have id element with nullFlavor, if there are other ids element (RMIM-072, RIM-011) cdabasic-AssignedEntitySpec-rmim072_1 Context rmim072_2 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity The ids elements of AssignedEntity SHALL be distinct (RMIM-072, RIM-012) cdabasic-AssignedEntitySpec-rmim072_2 Context rmim072_3 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity AssignedEntity SHALL NOT have addr element with nullFlavor, if there are other addr (RMIM-072, RIM-016) cdabasic-AssignedEntitySpec-rmim072_3 Context rmim072_4 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity The addr elements of AssignedEntity SHALL be distinct (RMIM-072, RIM-017) cdabasic-AssignedEntitySpec-rmim072_4 Context rmim073 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity If assignedEntity has not a null of flavor and its enclosing participation has not a null of flavor, it SHALL have an assignedPerson or a representedOrganization(RMIM-073) cdabasic-AssignedEntitySpec-rmim073 Context rmim097_1 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson Person SHALL NOT have name element with nullFlavor, if there are other name (RMIM-097, RIM-022) cdabasic-PersonSpec-rmim097_1 Context rmim097_2 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson The name elements of Person SHALL be distinct (RMIM-097, RIM-023) cdabasic-PersonSpec-rmim097_2 Context rmim094_1 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization Organization SHALL NOT have id element with nullFlavor, if there are other ids (RMIM-094, RIM-020) cdabasic-OrganizationSpec-rmim094_1 Context rmim094_2 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization The ids elements of Organization SHALL be distinct (RMIM-094, RIM-021) cdabasic-OrganizationSpec-rmim094_2 Context rmim094_3 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization Organization SHALL NOT have name element with nullFlavor, if there are other name (RMIM-094, RIM-022) cdabasic-OrganizationSpec-rmim094_3 Context rmim094_4 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization The name elements of Organizarion SHALL be distinct (RMIM-094, RIM-023) cdabasic-OrganizationSpec-rmim094_4 Context rmim094_5 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization Organization SHALL NOT have telecom element with nullFlavor, if there are other telecom elements which are not null (RMIM-094, RIM-024) cdabasic-OrganizationSpec-rmim094_5 Context rmim094_6 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization The telecom elements of Entity SHALL be distinct (RMIM-094, RIM-025) cdabasic-OrganizationSpec-rmim094_6 Context rmim095 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization Organization SHALL NOT have addr element with nullFlavor, if there are other (RMIM-095) cdabasic-OrganizationSpec-rmim095 Context rmim096 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization The addr elements of Organization SHALL be distinct (RMIM-096) cdabasic-OrganizationSpec-rmim096 Context rmim092_1 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole ParticipantRole SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-092, RIM-011) cdabasic-ParticipantRoleSpec-rmim092_1 Context rmim092_2 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole The ids elements of ParticipantRole SHALL be distinct (RMIM-092, RIM-012) cdabasic-ParticipantRoleSpec-rmim092_2 Context rmim092_3 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole ParticipantRole SHALL NOT have addr element with nullFlavor, if there are other addr (RMIM-092, RIM-016) cdabasic-ParticipantRoleSpec-rmim092_3 Context rmim092_4 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole The addr elements of ParticipantRole SHALL be distinct (RMIM-092, RIM-017) cdabasic-ParticipantRoleSpec-rmim092_4 Context rmim092_5 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole ParticipantRole SHALL NOT have telecom element with nullFlavor, if there are other telecom elements which are not null (RMIM-092, RIM-018) cdabasic-ParticipantRoleSpec-rmim092_5 Context rmim092_6 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole The telecom elements of ParticipantRole SHALL be distinct (RMIM-092, RIM-019) cdabasic-ParticipantRoleSpec-rmim092_6 Context rmim093 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole If participantRole has not a null of flavor and its enclosing participant has not a null of flavor, it SHALL have a scopingEntity, or a playingEntityChoice (RMIM-093) cdabasic-ParticipantRoleSpec-rmim093 Context rmim104_1 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity PlayingEntity SHALL NOT have name element with nullFlavor, if there are other name (RMIM-104, RIM-022) cdabasic-PlayingEntitySpec-rmim104_1 Context rmim104_2 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity The name elements of PlayingEntity SHALL be distinct (RMIM-104, RIM-023) cdabasic-PlayingEntitySpec-rmim104_2 Context rmim105 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity PlayingEntity SHALL NOT have quantity element with nullFlavor, if there are other quantity elements which are not null (RMIM-105) cdabasic-PlayingEntitySpec-rmim105 Context rmim106 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity The quantity elements of PlayingEntity SHALL be distinct (RMIM-106) cdabasic-PlayingEntitySpec-rmim106 Context rmim001_1 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act Act SHALL NOT have id element with nullFlavor, if there are other ids elements (RMIM-001, RIM-001) cdabasic-ActSpec-rmim001_1 Context rmim001_2 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act The ids elements of Act SHALL be distinct (RMIM-001, RIM-002) cdabasic-ActSpec-rmim001_2 Context rmim001_3 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act The statusCode if presents SHALL be from the valueSet ActStatus (RMIM-001, RIM-003) cdabasic-ActSpec-rmim001_3 Vocabulary rmim002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act The languageCode shall be from the valueSet HumanLanguage (RMIM-002) cdabasic-ActSpec-rmim002 Vocabulary cdadt001 /ClinicalDocument/realmCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/realmCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/realmCode[0] if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/typeId NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/typeId The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/typeId When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/typeId when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/templateId[3] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/templateId[3] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/templateId[3] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/templateId[3] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/id NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/id The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/id When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/id when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/title NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/title The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/title mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/title if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/title In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/title In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/title In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/confidentialityCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/confidentialityCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/confidentialityCode codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/confidentialityCode In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/confidentialityCode code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/confidentialityCode originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/confidentialityCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/confidentialityCode When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/confidentialityCode IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/confidentialityCode In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/confidentialityCode In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/languageCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/languageCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/languageCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/recordTarget[0]/patientRole/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/recordTarget[0]/patientRole/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt032 /ClinicalDocument/recordTarget[0]/patientRole/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/country[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/country[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/country[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/country[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/country[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/country[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/country[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/state[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/state[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/state[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/state[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/state[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/state[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/state[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/city[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/city[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/city[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/city[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/city[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/city[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/city[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/postalCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/postalCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/postalCode[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/postalCode[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/postalCode[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/postalCode[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/postalCode[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/streetAddressLine[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/streetAddressLine[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/streetAddressLine[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/streetAddressLine[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/streetAddressLine[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/streetAddressLine[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/recordTarget[0]/patientRole/addr[0]/streetAddressLine[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/recordTarget[0]/patientRole/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/recordTarget[0]/patientRole/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/recordTarget[0]/patientRole/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/recordTarget[0]/patientRole/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/recordTarget[0]/patientRole/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/recordTarget[0]/patientRole/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/recordTarget[0]/patientRole/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt015 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0] the qualifier ofelements of PN datatype SHALL NOT include LS as value (CDADT-015) cdadt-PNSpec-cdadt015 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/family[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/family[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/family[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/family[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/family[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/family[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/family[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/family[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/given[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/given[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/given[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/given[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/given[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/given[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/given[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/given[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/prefix[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/prefix[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/prefix[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/prefix[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/prefix[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/prefix[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/prefix[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/prefix[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/suffix[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/suffix[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/suffix[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/suffix[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/suffix[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/suffix[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/suffix[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/recordTarget[0]/patientRole/patient/name[0]/suffix[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/recordTarget[0]/patientRole/patient/administrativeGenderCode In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/patient/birthTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/patient/birthTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/recordTarget[0]/patientRole/patient/birthTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/recordTarget[0]/patientRole/patient/birthTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/recordTarget[0]/patientRole/patient/maritalStatusCode In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/recordTarget[0]/patientRole/patient/religiousAffiliationCode In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/author[0]/time NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/time The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/author[0]/time In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/author[0]/time In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/author[0]/assignedAuthor/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/author[0]/assignedAuthor/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt032 /ClinicalDocument/author[0]/assignedAuthor/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/author[0]/assignedAuthor/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/author[0]/assignedAuthor/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/author[0]/assignedAuthor/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/author[0]/assignedAuthor/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/author[0]/assignedAuthor/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/author[0]/assignedAuthor/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/author[0]/assignedAuthor/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/author[0]/assignedAuthor/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt015 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0] the qualifier ofelements of PN datatype SHALL NOT include LS as value (CDADT-015) cdadt-PNSpec-cdadt015 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[1] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[1] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[1] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[1] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[1] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/given[1] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[1] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[1] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[1] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[1] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[1] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[1] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/telecom[1] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt032 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/name NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/name The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/name In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt001 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/telecom NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/telecom The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/telecom In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/telecom value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/telecom When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/telecom In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/telecom In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/telecom In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/telecom In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt032 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/country[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/country[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/country[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/country[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/country[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/country[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/country[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/state[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/state[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/state[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/state[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/state[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/state[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/state[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/city[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/city[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/city[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/city[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/city[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/city[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/city[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/postalCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/postalCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/postalCode[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/postalCode[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/postalCode[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/postalCode[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/postalCode[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/streetAddressLine[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/streetAddressLine[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/streetAddressLine[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/streetAddressLine[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/streetAddressLine[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/streetAddressLine[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/addr/streetAddressLine[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/documentationOf[0]/serviceEvent/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/documentationOf[0]/serviceEvent/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/documentationOf[0]/serviceEvent/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/documentationOf[0]/serviceEvent/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/documentationOf[0]/serviceEvent/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/documentationOf[0]/serviceEvent/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/documentationOf[0]/serviceEvent/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/documentationOf[0]/serviceEvent/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/documentationOf[0]/serviceEvent/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime/low NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime/low The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime/low In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime/low In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime/high NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime/high The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime/high In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/documentationOf[0]/serviceEvent/effectiveTime/high In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/time NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/time The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/time In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/time In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/time In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/time In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt032 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt015 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0] the qualifier ofelements of PN datatype SHALL NOT include LS as value (CDADT-015) cdadt-PNSpec-cdadt015 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[1] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[1] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[1] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[1] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[1] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/given[1] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[1] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[1] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[1] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[1] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[1] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[1] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/telecom[1] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt032 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/documentationOf[0]/serviceEvent/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/id NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/id The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/id When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/id when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[0]/section/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[0]/section/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[0]/section/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[0]/section/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[0]/section/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[0]/section/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[0]/section/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[0]/section/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/title NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/title The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[0]/section/title mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[0]/section/title if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[0]/section/title In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[0]/section/title In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[0]/section/title In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/effectiveTime In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/effectiveTime In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/text/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/effectiveTime In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/effectiveTime In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/value[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/value[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt035 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/value[0] In PQ datatype, the translation elements SHALL have distinct values (CDADT-035) cdadt-PQSpec-cdadt035 Datatype cdadt036 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/value[0] In PQ datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-036) cdadt-PQSpec-cdadt036 Datatype cdadt037 /ClinicalDocument/component/structuredBody/component[0]/section/entry[0]/organizer/component[0]/observation/value[0] In PQ datatype, the unit attribute SHALL be from UCUM code system (CDADT-037) cdadt-PQSpec-cdadt037 Vocabulary cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[1]/section/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/id NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/id The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/id When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[1]/section/id when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[1]/section/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[1]/section/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[1]/section/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[1]/section/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[1]/section/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[1]/section/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[1]/section/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[1]/section/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/title NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/title The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/title mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/title if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/title In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/title In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/title In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/effectiveTime In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/effectiveTime In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/time NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/time The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/time In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/time In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt032 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt015 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0] the qualifier ofelements of PN datatype SHALL NOT include LS as value (CDADT-015) cdadt-PNSpec-cdadt015 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/family[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/given[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/assignedPerson/name[0]/prefix[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt032 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/country[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/state[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/city[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/postalCode[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/author[0]/assignedAuthor/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/text/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/effectiveTime In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/effectiveTime In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[1]/section/entry[0]/organizer/component[0]/observation/value[0] In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/id NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/id The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/id When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/id when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[2]/section/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[2]/section/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[2]/section/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[2]/section/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[2]/section/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[2]/section/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[2]/section/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[2]/section/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/title NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/title The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[2]/section/title mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[2]/section/title if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[2]/section/title In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[2]/section/title In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[2]/section/title In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/text/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime/low NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime/low The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime/low In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime/low In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime/high NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime/high The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime/high In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/effectiveTime/high In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/priorityCode In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0] In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/approachSiteCode[0]/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0] In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[0]/procedure/targetSiteCode[0]/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/text/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime/low NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime/low The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime/low In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime/low In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime/high NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime/high The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime/high In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/effectiveTime/high In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/priorityCode In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0] In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/approachSiteCode[0]/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0] In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[2]/section/entry[1]/procedure/targetSiteCode[0]/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/id NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/id The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/id When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/id when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[3]/section/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[3]/section/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[3]/section/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[3]/section/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[3]/section/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[3]/section/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[3]/section/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[3]/section/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/title NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/title The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[3]/section/title mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[3]/section/title if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[3]/section/title In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[3]/section/title In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[3]/section/title In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[3] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[3] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[3] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/templateId[3] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[0] In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[0] In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[0] In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[0] In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt028 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[1] In PIVL datatype, if it is not null, it SHALL have a period (CDADT-028) cdadt-PIVLTSSpec-cdadt028 Datatype dtits016 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[1] In PIVL_TS datatype, unit attribute of period element SHALL have a value from the time units (DTITS-016) cdadt-PIVLTSSpec-dtits016 Datatype dtits017 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[1] In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/effectiveTime[1] In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity In IVL<PQ> datatype, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLPQSpec-cdadt017 Datatype cdadt018 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity In IVL<PQ> datatype, the low and high values SHALL use comparable units (CDADT-018) cdadt-IVLPQSpec-cdadt018 cdadt035 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity In PQ datatype, the translation elements SHALL have distinct values (CDADT-035) cdadt-PQSpec-cdadt035 Datatype cdadt036 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity In PQ datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-036) cdadt-PQSpec-cdadt036 Datatype cdadt037 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity In PQ datatype, the unit attribute SHALL be from UCUM code system (CDADT-037) cdadt-PQSpec-cdadt037 Vocabulary cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity/low NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity/low The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt035 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity/low In PQ datatype, the translation elements SHALL have distinct values (CDADT-035) cdadt-PQSpec-cdadt035 Datatype cdadt036 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity/low In PQ datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-036) cdadt-PQSpec-cdadt036 Datatype cdadt037 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/doseQuantity/low In PQ datatype, the unit attribute SHALL be from UCUM code system (CDADT-037) cdadt-PQSpec-cdadt037 Vocabulary cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/name NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/name The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/name In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/text/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[3]/section/entry[0]/substanceAdministration/entryRelationship[0]/act/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/id NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/id The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/id When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/id when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[4]/section/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[4]/section/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[4]/section/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[4]/section/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[4]/section/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[4]/section/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[4]/section/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[4]/section/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/title NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/title The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[4]/section/title mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[4]/section/title if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[4]/section/title In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[4]/section/title In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[4]/section/title In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[3] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[3] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[3] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[3] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[4] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[4] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[4] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/templateId[4] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/text/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/effectiveTime[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/effectiveTime[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/effectiveTime[0] In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/effectiveTime[0] In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/effectiveTime[0] In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/effectiveTime[0] In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/routeCode/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/approachSiteCode[0] In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[1] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[1] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[2] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[2] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[2] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/templateId[2] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/name NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/name The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/component/structuredBody/component[4]/section/entry[0]/substanceAdministration/consumable/manufacturedProduct/manufacturedMaterial/name In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[5]/section/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/id NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/id The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/id When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[5]/section/id when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[5]/section/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[5]/section/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[5]/section/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[5]/section/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[5]/section/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[5]/section/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[5]/section/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[5]/section/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/title NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/title The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/title mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/title if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/title In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/title In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/title In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/text/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/statusCode NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/statusCode The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt009 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/statusCode if the nullFlavor is not defined, the code SHALL be provided (CDADT-009) cdadt-CSSpec-cdadt009 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime/low NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime/low The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime/low In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime/low In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime/high NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime/high The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime/high In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/effectiveTime/high In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt032 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/country[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/country[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/country[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/country[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/country[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/country[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/country[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/state[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/state[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/state[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/state[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/state[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/state[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/state[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/city[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/city[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/city[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/city[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/city[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/city[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/city[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/postalCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/postalCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/postalCode[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/postalCode[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/postalCode[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/postalCode[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/postalCode[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/streetAddressLine[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/streetAddressLine[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/streetAddressLine[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/streetAddressLine[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/streetAddressLine[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/streetAddressLine[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/addr[0]/streetAddressLine[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt015 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0] the qualifier ofelements of PN datatype SHALL NOT include LS as value (CDADT-015) cdadt-PNSpec-cdadt015 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/family[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/given[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/assignedPerson/name[0]/prefix[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[1] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[1] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[1] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[1] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[1] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[1] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/telecom[1] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt032 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/country[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/state[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/city[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/postalCode[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/performer[0]/assignedEntity/representedOrganization/addr[0]/streetAddressLine[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt032 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/addr[0] In AD datatype, the use attribute SHALL have disctinct values (CDADT-032) cdadt-ADSpec-cdadt032 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/addr[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/addr[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/telecom[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/telecom[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/telecom[0] In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/telecom[0] value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/telecom[0] When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/telecom[0] In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/telecom[0] In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/telecom[0] In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/telecom[0] In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt034 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0] In EN datatype, the use attribute SHALL have distinct values (CDADT-034) cdadt-ENSpec-cdadt034 Datatype cdadt015 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0] the qualifier ofelements of PN datatype SHALL NOT include LS as value (CDADT-015) cdadt-PNSpec-cdadt015 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/family[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/family[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/family[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/family[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/family[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/family[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/family[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/family[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[1] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[1] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[1] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[1] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[1] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[1] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[1] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/given[1] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/prefix[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/prefix[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/prefix[0] mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/prefix[0] if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/prefix[0] In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/prefix[0] In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/prefix[0] In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt033 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/participant[0]/participantRole/playingEntity/name[0]/prefix[0] In ENXP datatype, the qualifier attribute SHALL have distinct values (CDADT-033) cdadt-ENXPSpec-cdadt033 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/templateId[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/templateId[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/templateId[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/templateId[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/id[0] NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/id[0] The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/id[0] When root is UUID, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-IISpec-cdadt011 Context cdadt012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/id[0] when nullFlavor is not defined, the root SHALL be provided (CDADT-012) cdadt-IISpec-cdadt012 Context cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt004 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code codeSystem attribute SHALL be provided when codeSystemName is provided (CDADT-004) cdadt-CDSpec-cdadt004 Mandatory cdadt005 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code In CD datatype, codeSystem attribute SHALL be provided when codeSystemVersion is provided (CDADT-005) cdadt-CDSpec-cdadt005 Datatype cdadt006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code code attribute SHALL be provided when displayName is provided (CDADT-006) cdadt-CDSpec-cdadt006 Mandatory cdadt007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code originalText attribute SHALL NOT have multimedia value, only reference or plain text form are allowed (CDADT-007) cdadt-CDSpec-cdadt007 Datatype cdadt008 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code if the nullFlavor is not defined, the code SHALL be provided (CDADT-008) cdadt-CDSpec-cdadt008 Context cdadt011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code When UUID is used in codeSystem, the hexadecimal digits A-F SHALL be in upper case (CDADT-011) cdadt-CDSpec-cdadt011 Context cdadt020 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code IN CD datatype, when CD/@nullFlavor= OTH , the CD/@codeSystem SHALL be present (CDADT-020) cdadt-CDSpec-cdadt020 Datatype cdadt029 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code In CD datatype, the translation elements SHALL be disctinct (CDADT-029) cdadt-CDSpec-cdadt029 Datatype cdadt030 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code In CD datatype, the translation elements SHALL not be null if there are translations which are not null (CDADT-030) cdadt-CDSpec-cdadt030 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/code/originalText/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt002 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text mediaType of the ED datatype SHOULD be from known mediaTypes (CDADT-002) cdadt-EDSpec-cdadt002 Datatype cdadt003 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text if integrityCheck attribute is provided, it SHALL have a valid value according to its integrityCheckAlgorithm (CDADT-003) cdadt-EDSpec-cdadt003 Context cdadt023 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text In ED datatype, if it is not null, it SHALL have a binary string or reference element (CDADT-023) cdadt-EDSpec-cdadt023 Datatype dtits006 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text In ED datatype, the language SHALL be as defined in RFC3066 (DTITS-006) cdadt-EDSpec-dtits006 Datatype dtits007 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text In ED datatype, when it has reference form, there shall not be white spaces before and after the reference, the binary data shall not be present or shall represent the same information in the reference (DTITS-007) cdadt-EDSpec-dtits007 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text/reference NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text/reference The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt031 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text/reference In TEL datatype, the use attribute SHALL have disctinct values (CDADT-031) cdadt-TELSpec-cdadt031 Datatype cdadt013 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text/reference value attribute SHALL have this form : ^(\w+:.+|#.+)$ (CDADT-013) cdadt-URLSpec-cdadt013 Fixed value cdadt014 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text/reference When the URL datatype is tel or fax, the structure of the litteral is specified according to the specification in the datatypes specification, paragraph 2.18.3, and where the value is defined according to this regex (tel|fax):\+?([0-9]|\(|\)|\.|\-)*$ (CDADT-014) cdadt-URLSpec-cdadt014 Datatype dtits009 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text/reference In URL datatype, the mail SHALL be as defined in RFC2368 (DTITS-009) cdadt-URLSpec-dtits009 Datatype dtits010 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text/reference In URL datatype, the http SHALL be as defined in RFC2396 (DTITS-010) cdadt-URLSpec-dtits010 Datatype dtits011 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text/reference In URL datatype, the ftp SHALL be as defined in RFC1738 (DTITS-011) cdadt-URLSpec-dtits011 Datatype dtits012 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/text/reference In URL datatype, the file SHALL be as defined in RFC1738 (DTITS-012) cdadt-URLSpec-dtits012 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context cdadt017 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime In IVL<TS> datatypes, the low value SHALL be lessOrEqual the high value (CDADT-017) cdadt-IVLTSSpec-cdadt017 Datatype cdadt019 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime In IVL<TS>, the width/@unit SHALL be from mesure of time values (CDADT-019) cdadt-IVLTSSpec-cdadt019 Fixed value dtits017 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime/low NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime/low The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime/low In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime/low In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype cdadt001 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime/high NP value of nullFlavor is not used for CDA documents (CDADT-001) cdadt-ANYSpec-cdadt001 Context cdadt022 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime/high The use of nullFlavor PINF and NINF SHALL be for datatypes QTY (CDADT-022) cdadt-ANYSpec-cdadt022 Context dtits017 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime/high In TS datatype, value SHALL have a valid timestamp (DTITS-017) cdadt-TSSpec-dtits017 Datatype dtits018 /ClinicalDocument/component/structuredBody/component[5]/section/entry[0]/act/entryRelationship[0]/act/effectiveTime/high In TS datatype, value SHALL be present, otherwise nullFlavor shall be provided, not both (DTITS-018) cdadt-TSSpec-dtits018 Datatype rmim112_1 /ClinicalDocument/component/structuredBody/component[0]/section/text/table[0] table.border SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_1 Fixed value rmim112_2 /ClinicalDocument/component/structuredBody/component[0]/section/text/table[0] table.cellpading SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_2 Fixed value rmim112_3 /ClinicalDocument/component/structuredBody/component[0]/section/text/table[0] table.cellspacing SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_3 Fixed value rmim112_1 /ClinicalDocument/component/structuredBody/component[1]/section/text/table[0] table.border SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_1 Fixed value rmim112_2 /ClinicalDocument/component/structuredBody/component[1]/section/text/table[0] table.cellpading SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_2 Fixed value rmim112_3 /ClinicalDocument/component/structuredBody/component[1]/section/text/table[0] table.cellspacing SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_3 Fixed value rmim112_1 /ClinicalDocument/component/structuredBody/component[2]/section/text/table[0] table.border SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_1 Fixed value rmim112_2 /ClinicalDocument/component/structuredBody/component[2]/section/text/table[0] table.cellpading SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_2 Fixed value rmim112_3 /ClinicalDocument/component/structuredBody/component[2]/section/text/table[0] table.cellspacing SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_3 Fixed value rmim112_1 /ClinicalDocument/component/structuredBody/component[3]/section/text/table[0] table.border SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_1 Fixed value rmim112_2 /ClinicalDocument/component/structuredBody/component[3]/section/text/table[0] table.cellpading SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_2 Fixed value rmim112_3 /ClinicalDocument/component/structuredBody/component[3]/section/text/table[0] table.cellspacing SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_3 Fixed value rmim112_1 /ClinicalDocument/component/structuredBody/component[4]/section/text/table[0] table.border SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_1 Fixed value rmim112_2 /ClinicalDocument/component/structuredBody/component[4]/section/text/table[0] table.cellpading SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_2 Fixed value rmim112_3 /ClinicalDocument/component/structuredBody/component[4]/section/text/table[0] table.cellspacing SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_3 Fixed value rmim112_1 /ClinicalDocument/component/structuredBody/component[5]/section/text/table[0] table.border SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_1 Fixed value rmim112_2 /ClinicalDocument/component/structuredBody/component[5]/section/text/table[0] table.cellpading SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_2 Fixed value rmim112_3 /ClinicalDocument/component/structuredBody/component[5]/section/text/table[0] table.cellspacing SHOULD NOT be used (RMIM-112) cdanblock-TableSpec-rmim112_3 Fixed value test_IDs /ClinicalDocument Success: Found all IDs referenced FAILED 2018, 04 16 11:18:31 HL7 - CDA Release 2 (strict) Gazelle CDA Validation FAILED 2.1.23