schematron.cda4cdt_20090206.templates.2.16.840.1.113883.10.20.3.ent Maven / Gradle / Ivy
The newest version!
CDA for CDT - General Header Constraints - errors validation phase
CONF-HP-1: A CDA R2 Document that claims conformance to the general header
constraints for Clinical Document Template (CDT) SHALL indicate so by including
the following template id in the header of the document, or by including a template
id in the header for a template that requires use of the general header constraint
template: <templateId root=”2.16.840.1.113883.10.20.3”/>.
CONF-HP-2: The root of a History and Physical SHALL be a ClinicalDocument element
from the urn:hl7-org:v3 namespace.
CONF-HP-15:The ClinicalDocument/realmCode element SHALL be present. It SHALL
use the fixed value US.
CONF-HP-16: The extension attribute of the typeId element SHALL be
POCD_HD000040.
CONF-HP-17: The ClinicalDocument/id/@root attribute SHALL be a syntactically
correct UUID or OID.
CONF-HP-18: UUIDs SHALL be represented in the form
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where each X is a character from the set
[A-Fa-f0-9].
CONF-HP-19: OIDs SHALL be represented in dotted decimal notation, where each
decimal number is either 0, or starts with a nonzero digit. More formally,
an OID SHALL be in the form ([0-2])(.([1-9][0-9]*|0))+.
CONF-HP-20: OIDs SHALL be no more than 64 characters in length.
CONF-HP-21: The ClinicalDocument/code element SHALL be present and specifies the
type of clincal document.
CONF-HP-22: The title element SHALL be present and specifies the local name used
for the document.
CONF-HP-23: The ClinicalDocument/effectiveTime element SHALL be present and
specifies the creation time of the document.
CONF-HP-24: ClinicalDocument / languageCode element SHALL be present.
CONF-HP-25: ClincalDocument / languageCode SHALL be in the form nn, or nn-CC.
CONF-HP-28: Both ClinicalDocument/setId and ClinicalDocument/versionNumber SHALL
be present or both SHALL be absent.
CONF-HP-29: The @extension and/or @root of ClinicalDocument/setId and
ClinicalDocument/id SHALL be different when both are present.
CONF-HP-30: A ClinicalDocument/copyTime element SHALL NOT be present.
CONF-HP-31: At least one recordTarget/patientRole element SHALL be present.
CONF-HP-32: A patient/birthTime element SHALL be present. The patient/birthTime
element SHALL be precise at least to the year. If unknown, it SHALL be
represented using a flavor of null.
CONF-HP-33: A patient/administrativeGenderCode element SHALL be present.
If unknown, it SHALL be represented using a flavor of null.
CONF-HP-37: The author/time element SHALL be present.
CONF-HP-38: The assignedAuthor/id element SHALL be present.
CONF-HP-39: An assignedAuthor element SHALL contain at least one assignedPerson
or assignedAuthoringDevice elements.
CONF-HP-25, CONF-HP-26, CONF-HP-27: ClinicalDocument / languageCode SHALL be in the
form nn, or nn-CC. The nn portion of ClinicalDocument / languageCode SHALL be a
legal ISO-639-1 language code in lowercase. The CC portion ClinicalDocument /
languageCode, if present, SHALL be an ISO-3166 country code in uppercase.
CONF-HP-6: All patient guardianPerson, assignedPerson, maintainingPerson, relatedPerson,
intendedRecipient/informationRecipient, associatedPerson, and relatedSubject/subject
elements SHALL have a name.
CONF-HP-6: All patient guardianPerson, assignedPerson, maintainingPerson, relatedPerson,
intendedRecipient/informationRecipient, associatedPerson, and relatedSubject/subject
elements SHALL have a name.
CONF-HP-7: All patientRole, assignedAuthor, assignedEntity[not(parent::dataEnterer)]
and associatedEntity elements SHALL have an addr and telecom element.
CONF-HP-9: All guardianOrganization, providerOrganization, wholeOrganization,
representedOrganization, representedCustodianOrganization, receivedOrganization,
scopingOrganization and serviceProviderOrganization elements SHALL have name,
addr and telecom elements.
CONF-HP-10: Times or time intervals found in the ClinicalDocument/effectiveTime,
author/time, dataEnterer/time, legalAuthenticator/time, authenticator/time and
encompassingEncounter/effectiveTime elements SHALL be precise to the day, and SHALL
include a time zone if more precise than to the day.
CONF-HP-11: Times or time intervals found in the asOrganizationPartOf/effectiveTime,
asMaintainedEntity/effectiveTime, relatedEntity/effectiveTime, serviceEvent/effectiveTime,
ClinicalDocument/participant/time, serviceEvent/performer/time and encounterParticipant/time
SHALL be precise at least to the year.
CONF-HP-11: Times or time intervals found in the asOrganizationPartOf/effectiveTime,
asMaintainedEntity/effectiveTime, relatedEntity/effectiveTime, serviceEvent/effectiveTime,
ClinicalDocument/participant/time, serviceEvent/performer/time and encounterParticipant/time
SHALL be precise at least to the year.
CONF-HP-9: When name, addr, telecom information is unknown and where these elements
are required to be present, the fact that the information is unknown SHALL be represented
using an appropriate value for the nullFlavor attribute on the element. Legal values
according to this specification come from the HL7 NullFlavor vocabulary.
CONF-HP-12: Telephone numbers SHALL match the regular expression pattern tel:\+?[-0-9().]+
CONF-HP-13: At least one dialing digit SHALL be present in the phone number after visual
separators are removed.
CONF-HP-14: If the telephone number is unknown it SHALL be represented using the appopriate
flavor of null.
CONF-HP-40: When dataEnterer is present, an assignedEntity/assignedPerson element SHALL
be present.
CONF-HP-45: Allowable values for informant/relatedEntity/@classCode SHALL be CON, PRS,
CAREGIVER, AGNT or PROV from the RoleClass vocabulary.
CONF-HP-43: When informant is present, an assignedEntity/assignedPerson or
relatedEntity/relatedPerson element SHALL be present.
CONF-HP-46: When relatedEntity/@classCode is PRS, values in relatedEntity/code SHALL come
from the HL7 PersonalRelationshipRoleType vocabulary or from SNOMED, any subtype of“
Person in the family” (303071001).
CONF-HP-50: When informationRecipient is used, at least one
informationRecipient/intendedRecipient/informationRecipient or
informationRecipient/intendedRecipient/receivedOrganization SHALL be present.
CONF-HP-10: Times or time intervals found in the ClinicalDocument/effectiveTime,
author/time, dataEnterer/time, legalAuthenticator/time, authenticator/time and
encompassingEncounter/effectiveTime elements SHALL be precise to the day, and SHALL
include a time zone if more precise than to the day.
CONF-HP-51: The assignedEntity/assignedPerson element SHALL be present
in legalAuthenticator.
CONF-HP-10: Times or time intervals found in the ClinicalDocument/effectiveTime,
author/time, dataEnterer/time, legalAuthenticator/time, authenticator/time and
encompassingEncounter/effectiveTime elements SHALL be precise to the day, and SHALL
include a time zone if more precise than to the day.
CONF-HP-52: The assignedEntity/assignedPerson element SHALL be present
in an authenticator element.
CDA for common document type - warning validation phase
CONF-HP-8: All guardian, dataEnterer/assignedEntity, relatedEntity, intendedRecipient,
relatedSubject and participantRole elements SHOULD have an addr and telecom element.
CONF-HP-10: Times or time intervals found in the ClinicalDocument/effectiveTime,
author/time, dataEnterer/time, legalAuthenticator/time, authenticator/time and
encompassingEncounter/effectiveTime elements SHOULD be precise to the second.
CONF-HP-11: Times or time intervals found in the asOrganizationPartOf/effectiveTime,
asMaintainedEntity/effectiveTime, relatedEntity/effectiveTime,
ClinicalDocument/participant/time, serviceEvent/effectiveTime, serviceEvent/performer/time
and encounterParticipant/time ... SHOULD be precise to the day.
CONF-HP-11: Times or time intervals found in the asOrganizationPartOf/effectiveTime,
asMaintainedEntity/effectiveTime, relatedEntity/effectiveTime,
ClinicalDocument/participant/time, serviceEvent/effectiveTime, serviceEvent/performer/time
and encounterParticipant/time ... SHOULD be precise to the day.
CONF-HP-11: Times or time intervals found in the asOrganizationPartOf/effectiveTime,
asMaintainedEntity/effectiveTime, relatedEntity/effectiveTime,
ClinicalDocument/participant/time, serviceEvent/effectiveTime, serviceEvent/performer/time
and encounterParticipant/time ... SHOULD be precise to the day.
CONF-HP-32: The patient/birthTime element SHOULD be precise at least to the day.
CONF-HP-33: Administrative Gender codes used to describe the gender of the patient
SHOULD come from the HL7 AdministrativeGender vocabulary. The OID for this
vocabulary domain is 2.16.840.1.113883.5.1.
CONF-HP-34: Marital status codes used to describe the marital status of the patient
SHOULD come from the HL7 MaritalStatus vocabulary. The OID for this vocabulary
domain is 2.16.840.1.113883.5.2.
CDA for common document type - note validation phase
CONF-HP-3: To indicate conformance to Level 1 (which also asserts compliance with
all general or non-level-specific constraints), ClinicalDocument/templateId elements
MAY be present with the value shown: <templateId root='2.16.840.1.113883.10.20.10'/>
CONF-HP-4: To indicate conformance to Level 2 (which also asserts compliance with
all general or non-level-specific constraints), ClinicalDocument/templateId elements
MAY be present with the value shown: <templateId root='2.16.840.1.113883.10.20.20'/>
CONF-HP-5: To indicate conformance to Level 3 (which also asserts compliance with
all general or non-level-specific constraints), ClinicalDocument/templateId elements
MAY be present with the value shown: <templateId root='2.16.840.1.113883.10.20.30'/>
CONF-HP-42: The informant element MAY be present.
CONF-HP-36: The providerOrganization element MAY be present.
CONF-HP-41: The time element MAY be present. If present, it represents the starting
time of entry of the data.