Consolidated CDA Release 2.2
2.2 - CI Build United States of America flag

Consolidated CDA Release 2.2, published by Health Level Seven. This is not an authorized publication; it is the continuous build for version 2.2). This version is based on the current content of https://github.com/HL7/CDA-ccda-2.2/ and changes regularly. See the Directory of published versions

Resource Profile: US Realm Header for Patient Generated Document (V2)

Official URL: http://hl7.org/fhir/cda/ccda/StructureDefinition/2.16.840.1.113883.10.20.29.1 Version: 2.2
Active as of 2022-05-13 Computable Name: USRealmHeaderforPatientGeneratedDocument
Other Identifiers: : urn:hl7ii:2.16.840.1.113883.10.20.29.1:2015-08-01

This template is designed to be used in conjunction with the US Realm Header (V2). It includes additional conformances which further constrain the US Realm Header (V2). The Patient Generated Document Header template is not a separate document type. The document body may contain any structured or unstructured content from C-CDA.

Usage:

  • This Resource Profile is not used by any profiles in this Implementation Guide

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from USRealmHeader

Summary

Mandatory: 14 elements (15 nested mandatory elements)

Slices

This structure defines the following Slices:

  • The element ClinicalDocument.templateId is sliced based on the values of value:root, value:extension
  • The element ClinicalDocument.informant is sliced based on the value of value:relatedEntity

This structure is derived from USRealmHeader

NameFlagsCard.TypeDescription & Constraintsdoco
.. ClinicalDocument 1..1USRealmHeader
... Slices for templateId 0..*IISlice: Unordered, Open by value:root, value:extension
.... templateId:secondary I1..1II1198-32945: When asserting this templateId, all C-CDA 2.1 section and entry templates that had a previous version in C-CDA R1.1 **SHALL** include both the C-CDA 2.1 templateId and the C-CDA R1.1 templateId root without an extension. See C-CDA R2.1 Volume 1 - Design Considerations for additional detail (CONF:1198-32945).
..... root 1..1stringRequired Pattern: 2.16.840.1.113883.10.20.29.1
..... extension 1..1stringRequired Pattern: 2015-08-01
... recordTarget 1..1RecordTargetThe recordTarget records the patient whose health information is described by the clinical document; each recordTarget must contain at least one patientRole element. If the document receiver is interested in setting up a translator for the encounter with the patient, the receiver of the document will have to infer the need for a translator, based upon the language skills identified for the patient, the patient?s language of preference and the predominant language used by the organization receiving the CDA. HL7 Vocabulary simply describes guardian as a relationship to a ward. This need not be a formal legal relationship. When a guardian relationship exists for the patient, it can be represented, regardless of who is present at the time the document is generated. This need not be a formal legal relationship. A child?s parent can be represented in the guardian role. In this case, the guardian/code element would encode the personal relationship of "mother" for the child?s mom or "father" for the child?s dad. An elderly person's child can be represented in the guardian role. In this case, the guardian/code element would encode the personal relationship of "daughter" or "son", or if a legal relationship existed, the relationship of "legal guardian" could be encoded.
.... patientRole 1..1PatientRole
..... id 1..*II
..... patient 1..1Patient
...... guardian 0..*Guardian
....... id 0..*II
....... code 0..1CEBinding: Personal And Legal Relationship Role Type (required)
...... languageCommunication 0..*LanguageCommunication
....... preferenceInd 0..1BLIndicates a preference for information about care delivery and treatments be communicated (or translated if needed) into this language. If more than one languageCommunication is present, only one languageCommunication element SHALL have a preferenceInd with a value of 1.
..... providerOrganization 0..1OrganizationIf present, this organization represents the provider organization where the person is claiming to be a patient. undefined
... author 1..*AuthorThe author element represents the creator of the clinical document. The author may be a device, or a person. The person is the patient or the patient?s advocate.
.... assignedAuthor 1..1AssignedAuthor
..... id 1..*II
..... code 0..1CEWhen the author is a person who is not acting in the role of a clinician, this code encodes the personal or legal relationship between author and the patient.
...... code 1..1stringBinding: Personal And Legal Relationship Role Type (preferred)
.... assignedEntity 1..1AssignedEntity
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
... Slices for informant 0..*InformantThe informant element describes the source of the information in a medical document. Assigned health care providers may be a source of information when a document is created. (e.g., a nurse's aide who provides information about a recent significant health care event that occurred within an acute care facility.) In these cases, the assignedEntity element is used. When the informant is a personal relation, that informant is represented in the relatedEntity element, even if the personal relation is a medical professional. The code element of the relatedEntity describes the relationship between the informant and the patient. The relationship between the informant and the patient needs to be described to help the receiver of the clinical document understand the information in the document. Each informant can be either an assignedEntity (a clinician serving the patient) OR a relatedEntity (a person with a personal or legal relationship with the patient). The constraints here apply to relatedEntity.
Slice: Unordered, Open by value:relatedEntity
.... informant:informant1 0..*InformantThe informant element describes an information source for any content within the clinical document. This informant is constrained for use when the source of information is an assigned health care provider for the patient.
..... relatedEntity 1..1RelatedEntity
...... code 0..1CE
....... code 0..1stringBinding: Personal And Legal Relationship Role Type (preferred)
... custodian 1..1CustodianThe custodian element represents the organization or person that is in charge of maintaining the document. The custodian is the steward that is entrusted with the care of the document. Every CDA document has exactly one custodian. The custodian participation satisfies the CDA definition of Stewardship. Because CDA is an exchange standard and may not represent the original form of the authenticated document (e.g., CDA could include scanned copy of original), the custodian represents the steward of the original source document. The custodian may be the document originator, a health information exchange, or other responsible party. Also, the custodian may be the patient or an organization acting on behalf of the patient, such as a PHR organization.
.... assignedCustodian 1..1AssignedCustodian
..... representedCustodianOrganization 1..1CustodianOrganizationThe representedCustodianOrganization may be the person when the document is not maintained by an organization.
...... id 1..*IIThe combined @root and @extension attributes record the custodian organization?s identity in a secure, trusted, and unique way.
... informationRecipient 0..*InformationRecipientThe informationRecipient element records the intended recipient of the information at the time the document is created. For example, in cases where the intended recipient of the document is the patient's health chart, set the receivedOrganization to be the scoping organization for that chart.
.... intendedRecipient 1..1IntendedRecipient
..... id 0..*IIThe combined @root and @extension attributes to record the information recipient?s identity in a secure, trusted, and unique way.
...... root 0..1stringFor a provider, the id/@root ="2.16.840.1.113883.4.6" indicates the National Provider Identifier where id/@extension is the NPI number for the provider. The ids MAY reference the id of a person or organization entity specified elsewhere in the document.
... legalAuthenticator 0..1LegalAuthenticatorIn a patient authored document, the legalAuthenticator identifies the single person legally responsible for the document and must be present if the document has been legally authenticated. (Note that per the following section, there may also be one or more document authenticators.) Based on local practice, patient authored documents may be provided without legal authentication. This implies that a patient authored document that does not contain this element has not been legally authenticated. The act of legal authentication requires a certain privilege be granted to the legal authenticator depending upon local policy. All patient documents have the potential for legal authentication, given the appropriate legal authority. Local policies MAY choose to delegate the function of legal authentication to a device or system that generates the document. In these cases, the legal authenticator is the person accepting responsibility for the document, not the generating device or system. Note that the legal authenticator, if present, must be a person.
.... assignedEntity 1..1AssignedEntity
..... id 1..*IIThe combined @root and @extension attributes to record the information recipient?s identity in a secure, trusted, and unique way.
..... code 0..1CE
...... code 0..1stringBinding: Personal And Legal Relationship Role Type (preferred)
... authenticator 0..*AuthenticatorThe authenticator identifies a participant or participants who attest to the accuracy of the information in the document.
.... assignedEntity 1..1AssignedEntity
..... id 1..*IIThe combined @root and @extension attributes to record the authenticator?s identity in a secure, trusted, and unique way.
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
... participant 0..*Participant1The participant element identifies other supporting participants, including parents, relatives, caregivers, insurance policyholders, guarantors, and other participants related in some way to the patient. A supporting person or organization is an individual or an organization with a relationship to the patient. A supporting person who is playing multiple roles would be recorded in multiple participants (e.g., emergency contact and next-of-kin)
.... typeCode 1..1Unless otherwise specified by the document specific header constraints, when participant/@typeCode is IND, associatedEntity/@classCode SHALL be selected from ValueSet 2.16.840.1.113883.11.20.9.33 INDRoleclassCodes STATIC 2011-09-30
.... associatedEntity 1..1
..... code 0..1Binding: Personal And Legal Relationship Role Type (preferred)
... inFulfillmentOf 0..*InFulfillmentOfThe inFulfillmentOf element represents orders that are fulfilled by this document such as a radiologists? report of an x-ray.
.... order 1..1Order
..... id 1..*IIA scheduled appointment or service event in a practice management system may be represented using this id element.
... documentationOf 0..*DocumentationOf
.... serviceEvent 1..1ServiceEventA serviceEvent represents the main act being documented, such as a colonoscopy or a cardiac stress study. In a provision of healthcare serviceEvent, the care providers, PCP, or other longitudinal providers, are recorded within the serviceEvent. If the document is about a single encounter, the providers associated can be recorded in the componentOf/encompassingEncounter template.
..... code 0..1CEThe code should be selected from a value set established by the document-level template for a specific type of Patient Generated Document.
..... performer 0..*Performer1The performer participant represents clinicians who actually and principally carry out the serviceEvent. In a transfer of care this represents the healthcare providers involved in the current or pertinent historical care of the patient. Preferably, the patient?s key healthcare care team members would be listed, particularly their primary physician and any active consulting physicians, therapists, and counselors.
...... functionCode 0..1CEThe functionCode SHALL be selected from value set ParticipationType 2.16.840.1.113883.1.11.10901 When indicating the performer was the primary care physician the functionCode shall be =?PCP?
...... assignedEntity 1..1AssignedEntity
....... id 1..*IIThe combined @root and @extension attributes record the performer?s identity in a secure, trusted, and unique way.
....... code 0..1CEIf the assignedEntity is an individual, the code SHOULD be selected from value set PersonalandLegalRelationshipRoleType value set
Binding: Personal And Legal Relationship Role Type (preferred)

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. ClinicalDocument 1..1USRealmHeader
... classCode 1..1codeBinding: ActClass (extensible)
Fixed Value: DOCCLIN
... moodCode 1..1codeBinding: ActMood (required)
Fixed Value: EVN
... realmCode 1..1CSRequired Pattern: US
... typeId 1..1II
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... assigningAuthorityName 0..1string
.... displayable 0..1boolean
.... root 1..1stringRequired Pattern: 2.16.840.1.113883.1.3
.... extension 1..1stringRequired Pattern: POCD_HD000040
... Slices for templateId 0..*IISlice: Unordered, Open by value:root, value:extension
.... templateId:primary 1..1II
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... assigningAuthorityName 0..1string
..... displayable 0..1boolean
..... root 1..1stringRequired Pattern: 2.16.840.1.113883.10.20.22.1.1
..... extension 1..1stringRequired Pattern: 2015-08-01
.... templateId:secondary I1..1II1198-32945: When asserting this templateId, all C-CDA 2.1 section and entry templates that had a previous version in C-CDA R1.1 **SHALL** include both the C-CDA 2.1 templateId and the C-CDA R1.1 templateId root without an extension. See C-CDA R2.1 Volume 1 - Design Considerations for additional detail (CONF:1198-32945).
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... assigningAuthorityName 0..1string
..... displayable 0..1boolean
..... root 1..1stringRequired Pattern: 2.16.840.1.113883.10.20.29.1
..... extension 1..1stringRequired Pattern: 2015-08-01
... id I1..1II
... code I1..1CEBinding: http://terminology.hl7.org/ValueSet/v3-DocumentType (extensible)
... title 1..1EDThe title can either be a locally defined name or the displayName corresponding to clinicalDocument/code
... effectiveTime I1..1USRealmDateandTimeDTMUSFIELDED
... confidentialityCode 1..1CEBinding: HL7 BasicConfidentialityKind (preferred)
... languageCode 1..1CSBinding: VSAC 2.16.840.1.113883.1.11.11526 (required)
... setId I0..1II
... versionNumber I0..1INT
... copyTime 0..1TS
... recordTarget 1..1RecordTargetThe recordTarget records the patient whose health information is described by the clinical document; each recordTarget must contain at least one patientRole element. If the document receiver is interested in setting up a translator for the encounter with the patient, the receiver of the document will have to infer the need for a translator, based upon the language skills identified for the patient, the patient?s language of preference and the predominant language used by the organization receiving the CDA. HL7 Vocabulary simply describes guardian as a relationship to a ward. This need not be a formal legal relationship. When a guardian relationship exists for the patient, it can be represented, regardless of who is present at the time the document is generated. This need not be a formal legal relationship. A child?s parent can be represented in the guardian role. In this case, the guardian/code element would encode the personal relationship of "mother" for the child?s mom or "father" for the child?s dad. An elderly person's child can be represented in the guardian role. In this case, the guardian/code element would encode the personal relationship of "daughter" or "son", or if a legal relationship existed, the relationship of "legal guardian" could be encoded.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: RCT
.... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... patientRole 1..1PatientRole
..... classCode 1..1codeBinding: RoleClassRelationshipFormal (required)
Fixed Value: PAT
..... templateId 0..*II
..... id 1..*II
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... addr I1..*USRealmAddressADUSFIELDED
..... telecom 1..*TEL
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1uri
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
..... patient 1..1Patient
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... id 0..1II
...... name I1..*USRealmPatientNamePTNUSFIELDED
...... sdtcDesc 0..1EDXML: desc (urn:hl7-org:sdtc)
...... administrativeGenderCode 1..1CEBinding: Administrative Gender (HL7 V3) (required)
...... birthTime I1..1TS
...... sdtcDeceasedInd 0..1BLXML: deceasedInd (urn:hl7-org:sdtc)
...... sdtcDeceasedTime 0..1TSXML: deceasedTime (urn:hl7-org:sdtc)
...... sdtcMultipleBirthInd 0..1BLXML: multipleBirthInd (urn:hl7-org:sdtc)
...... sdtcMultipleBirthOrderNumber 0..1INT_POSXML: multipleBirthOrderNumber (urn:hl7-org:sdtc)
...... maritalStatusCode 0..1CEBinding: Marital Status (required)
...... religiousAffiliationCode 0..1CEBinding: Religious Affiliation (required)
...... raceCode 1..1CEBinding: Race Category Excluding Nulls (required)
...... sdtcRaceCode 0..*CEXML: raceCode (urn:hl7-org:sdtc)
Binding: Race Value Set (extensible)
...... ethnicGroupCode 1..1CEBinding: Ethnicity (required)
...... sdtcEthnicGroupCode 0..*CEXML: ethnicGroupCode (urn:hl7-org:sdtc)
Binding: Detailed Ethnicity (extensible)
...... guardian 0..*Guardian
....... classCode 1..1codeBinding: RoleClassAgent (required)
Fixed Value: GUARD
....... templateId 0..*II
....... id 0..*II
....... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
....... code 0..1CEBinding: Personal And Legal Relationship Role Type (required)
....... addr I0..*USRealmAddressADUSFIELDED
....... telecom 0..*TEL
........ nullFlavor 0..1codeBinding: NullFlavor (required)
........ value 0..1uri
........ useablePeriod 0..*
......... useablePeriodIVL_TS
......... useablePeriodEIVL_TS
......... useablePeriodPIVL_TS
......... useablePeriodSXPR_TS
........ use 0..1codeBinding: Telecom Use (US Realm Header) (required)
....... guardianPerson 1..1Person
........ classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
........ determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
........ templateId 0..*II
........ name I1..*USRealmPersonNamePNUSFIELDED
........ sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
....... guardianOrganization 0..1Organization
...... birthplace 0..1Birthplace
....... classCode 1..1codeBinding: RoleClassPassive (required)
Fixed Value: BIRTHPL
....... templateId 0..*II
....... place 1..1Place
........ classCode 1..1codeBinding: EntityClassPlace (required)
Fixed Value: PLC
........ determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
........ templateId 0..*II
........ name 0..1EN
........ addr I1..1AD
......... nullFlavor 0..1codeBinding: NullFlavor (required)
......... isNotOrdered 0..1boolean
......... use 0..*code
......... delimiter 0..*ADXP
.......... partType 0..1codeFixed Value: DEL
......... country 0..1ADXP
.......... partType 0..1codeFixed Value: CNT
......... state 0..*ADXP
.......... partType 0..1codeFixed Value: STA
......... county 0..*ADXP
.......... partType 0..1codeFixed Value: CPA
......... city 0..*ADXP
.......... partType 0..1codeFixed Value: CTY
......... postalCode 0..*ADXP
.......... partType 0..1codeFixed Value: ZIP
......... streetAddressLine 0..*ADXP
.......... partType 0..1codeFixed Value: SAL
......... houseNumber 0..*ADXP
.......... partType 0..1codeFixed Value: BNR
......... houseNumberNumeric 0..*ADXP
.......... partType 0..1codeFixed Value: BNN
......... direction 0..*ADXP
.......... partType 0..1codeFixed Value: DIR
......... streetName 0..*ADXP
.......... partType 0..1codeFixed Value: STR
......... streetNameBase 0..*ADXP
.......... partType 0..1codeFixed Value: STB
......... streetNameType 0..*ADXP
.......... partType 0..1codeFixed Value: STTYP
......... additionalLocator 0..*ADXP
.......... partType 0..1codeFixed Value: ADL
......... unitID 0..*ADXP
.......... partType 0..1codeFixed Value: UNID
......... unitType 0..*ADXP
.......... partType 0..1codeFixed Value: UNIT
......... careOf 0..*ADXP
.......... partType 0..1codeFixed Value: CAR
......... censusTract 0..*ADXP
.......... partType 0..1codeFixed Value: CEN
......... deliveryAddressLine 0..*ADXP
.......... partType 0..1codeFixed Value: DAL
......... deliveryInstallationType 0..*ADXP
.......... partType 0..1codeFixed Value: DINST
......... deliveryInstallationArea 0..*ADXP
.......... partType 0..1codeFixed Value: DINSTA
......... deliveryInstallationQualifier 0..*ADXP
.......... partType 0..1codeFixed Value: DINSTQ
......... deliveryMode 0..*ADXP
.......... partType 0..1codeFixed Value: DMOD
......... deliveryModeIdentifier 0..*ADXP
.......... partType 0..1codeFixed Value: DMODID
......... buildingNumberSuffix 0..*ADXP
.......... partType 0..1codeFixed Value: BNS
......... postBox 0..*ADXP
.......... partType 0..1codeFixed Value: POB
......... precinct 0..*ADXP
.......... partType 0..1codeFixed Value: PRE
......... other 0..1string
......... useablePeriod[x] 0..*
.......... useablePeriodHttp://hl7.org/fhir/cda/StructureDefinition/IVL-TSIVL_TS
.......... useablePeriodHttp://hl7.org/fhir/cda/StructureDefinition/EIVL-TSEIVL_TS
.......... useablePeriodHttp://hl7.org/fhir/cda/StructureDefinition/PIVL-TSPIVL_TS
.......... useablePeriodHttp://hl7.org/fhir/cda/StructureDefinition/SXPR-TSSXPR_TS
...... languageCommunication 0..*LanguageCommunication
....... templateId 0..*II
....... languageCode 1..1CSBinding: VSAC 2.16.840.1.113883.1.11.11526 (required)
....... modeCode 0..1CEBinding: LanguageAbilityMode (required)
....... proficiencyLevelCode 0..1CEBinding: LanguageAbilityProficiency (required)
....... preferenceInd 0..1BLIndicates a preference for information about care delivery and treatments be communicated (or translated if needed) into this language. If more than one languageCommunication is present, only one languageCommunication element SHALL have a preferenceInd with a value of 1.
..... providerOrganization 0..1OrganizationIf present, this organization represents the provider organization where the person is claiming to be a patient. undefined
...... classCode 1..1codeBinding: EntityClassOrganization (required)
Fixed Value: ORG
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... id 1..*II
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... assigningAuthorityName 0..1string
....... displayable 0..1boolean
....... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
....... extension 0..1string
...... name 1..*ON
...... telecom 1..*TEL
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... value 0..1uri
....... useablePeriod 0..*
........ useablePeriodIVL_TS
........ useablePeriodEIVL_TS
........ useablePeriodPIVL_TS
........ useablePeriodSXPR_TS
....... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
...... addr I1..*USRealmAddressADUSFIELDED
...... standardIndustryClassCode 0..1CEBinding: OrganizationIndustryClassNAICS (extensible)
...... asOrganizationPartOf 0..1OrganizationPartOf
... author 1..*AuthorThe author element represents the creator of the clinical document. The author may be a device, or a person. The person is the patient or the patient?s advocate.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUT
.... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... functionCode 0..1CE
.... time I1..1USRealmDateandTimeDTMUSFIELDED
.... assignedAuthor I1..1AssignedAuthor
..... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... Slices for id I1..*IISlice: Unordered, Open by value:root
...... id:id1 0..1II
....... nullFlavor 0..1codeIf id with @root="2.16.840.1.113883.4.6" National Provider Identifier is unknown then
Binding: NullFlavor (required)
Required Pattern: UNK
....... assigningAuthorityName 0..1string
....... displayable 0..1boolean
....... root 1..1stringRequired Pattern: 2.16.840.1.113883.4.6
....... extension 0..1string
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... code 0..1CEWhen the author is a person who is not acting in the role of a clinician, this code encodes the personal or legal relationship between author and the patient.
Binding: v3 Code System RoleCode (extensible)
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... code 1..1stringBinding: Personal And Legal Relationship Role Type (preferred)
...... codeSystem 0..1string
...... codeSystemName 0..1string
...... codeSystemVersion 0..1string
...... displayName 0..1string
...... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
...... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
...... originalText 0..1ED
...... translation 0..*CD
..... addr I1..*USRealmAddressADUSFIELDED
..... telecom 1..*TEL
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1uri
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
..... assignedPerson 0..1Person
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... name I1..*USRealmPersonNamePNUSFIELDED
...... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
..... assignedAuthoringDevice 0..1AuthoringDevice
...... classCode 1..1codeBinding: EntityClassDevice (required)
Fixed Value: DEV
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... code 0..1CEBinding: EntityCode (extensible)
...... manufacturerModelName 1..1SC
...... softwareName 1..1SC
...... asMaintainedEntity 0..*MaintainedEntity
..... representedOrganization 0..1Organization
... dataEnterer 0..1DataEntererThe dataEnterer element represents the person who transferred the content, written or dictated by someone else, into the clinical document. The guiding rule of thumb is that an author provides the content found within the header or body of the document, subject to their own interpretation, and the dataEnterer adds that information to the electronic system. In other words, a dataEnterer transfers information from one source to another (e.g., transcription from paper form to electronic system). If the dataEnterer is missing, this role is assumed to be played by the author.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: ENT
.... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... time 1..1TS
.... assignedEntity 1..1AssignedEntity
..... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... id 1..*II
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... assigningAuthorityName 0..1string
...... displayable 0..1boolean
...... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
...... extension 0..1string
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
..... addr I1..*USRealmAddressADUSFIELDED
..... telecom 1..*TEL
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1uri
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
..... assignedPerson 1..1Person
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... name I1..*USRealmPersonNamePNUSFIELDED
...... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
..... representedOrganization 0..1Organization
... Slices for informant 0..*InformantThe informant element describes the source of the information in a medical document. Assigned health care providers may be a source of information when a document is created. (e.g., a nurse's aide who provides information about a recent significant health care event that occurred within an acute care facility.) In these cases, the assignedEntity element is used. When the informant is a personal relation, that informant is represented in the relatedEntity element, even if the personal relation is a medical professional. The code element of the relatedEntity describes the relationship between the informant and the patient. The relationship between the informant and the patient needs to be described to help the receiver of the clinical document understand the information in the document. Each informant can be either an assignedEntity (a clinician serving the patient) OR a relatedEntity (a person with a personal or legal relationship with the patient). The constraints here apply to relatedEntity.
Slice: Unordered, Open by value:relatedEntity
.... informant:informant1 0..*InformantThe informant element describes an information source for any content within the clinical document. This informant is constrained for use when the source of information is an assigned health care provider for the patient.
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: INF
..... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... assignedEntity 1..1AssignedEntity
...... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
...... templateId 0..*II
...... id I1..*II
...... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
...... code 0..1CEBinding: Healthcare Provider Taxonomy (preferred)
...... addr I1..*USRealmAddressADUSFIELDED
...... telecom 0..*TEL
...... assignedPerson 1..1Person
....... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
....... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
....... templateId 0..*II
....... name I1..*USRealmPersonNamePNUSFIELDED
....... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
...... representedOrganization 0..1Organization
..... relatedEntity 1..1RelatedEntity
...... classCode 1..1codeBinding: RoleClassMutualRelationship (required)
...... templateId 0..*II
...... code 0..1CEBinding: PersonalRelationshipRoleType (extensible)
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... code 0..1stringBinding: Personal And Legal Relationship Role Type (preferred)
....... codeSystem 0..1string
....... codeSystemName 0..1string
....... codeSystemVersion 0..1string
....... displayName 0..1string
....... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
....... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
....... originalText 0..1ED
....... translation 0..*CD
...... addr 0..*AD
...... telecom 0..*TEL
...... effectiveTime 0..1IVL_TS
...... relatedPerson 0..1Person
.... informant:informant2 0..*Informant
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: INF
..... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... assignedEntity 0..1AssignedEntity
..... relatedEntity 1..1RelatedEntity
... custodian 1..1CustodianThe custodian element represents the organization or person that is in charge of maintaining the document. The custodian is the steward that is entrusted with the care of the document. Every CDA document has exactly one custodian. The custodian participation satisfies the CDA definition of Stewardship. Because CDA is an exchange standard and may not represent the original form of the authenticated document (e.g., CDA could include scanned copy of original), the custodian represents the steward of the original source document. The custodian may be the document originator, a health information exchange, or other responsible party. Also, the custodian may be the patient or an organization acting on behalf of the patient, such as a PHR organization.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: ENT
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... assignedCustodian 1..1AssignedCustodian
..... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... representedCustodianOrganization 1..1CustodianOrganizationThe representedCustodianOrganization may be the person when the document is not maintained by an organization.
...... classCode 1..1codeBinding: EntityClassOrganization (required)
Fixed Value: ORG
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... id 1..*IIThe combined @root and @extension attributes record the custodian organization?s identity in a secure, trusted, and unique way.
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... assigningAuthorityName 0..1string
....... displayable 0..1boolean
....... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
....... extension 0..1string
...... name 1..1ON
...... telecom 1..1TEL
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... value 0..1uri
....... useablePeriod 0..*
........ useablePeriodIVL_TS
........ useablePeriodEIVL_TS
........ useablePeriodPIVL_TS
........ useablePeriodSXPR_TS
....... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
...... addr I1..1USRealmAddressADUSFIELDED
... informationRecipient 0..*InformationRecipientThe informationRecipient element records the intended recipient of the information at the time the document is created. For example, in cases where the intended recipient of the document is the patient's health chart, set the receivedOrganization to be the scoping organization for that chart.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... intendedRecipient 1..1IntendedRecipient
..... classCode 1..1code
..... templateId 0..*II
..... id 0..*IIThe combined @root and @extension attributes to record the information recipient?s identity in a secure, trusted, and unique way.
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... assigningAuthorityName 0..1string
...... displayable 0..1boolean
...... root 0..1stringFor a provider, the id/@root ="2.16.840.1.113883.4.6" indicates the National Provider Identifier where id/@extension is the NPI number for the provider. The ids MAY reference the id of a person or organization entity specified elsewhere in the document.
...... extension 0..1string
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... addr 0..*AD
..... telecom 0..*TEL
..... informationRecipient 0..1Person
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... name I1..*USRealmPersonNamePNUSFIELDED
...... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
..... receivedOrganization 0..1Organization
...... classCode 1..1codeBinding: EntityClassOrganization (required)
Fixed Value: ORG
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... id 0..*II
...... name 1..1ON
...... telecom 0..*TEL
...... addr 0..*AD
...... standardIndustryClassCode 0..1CEBinding: OrganizationIndustryClassNAICS (extensible)
...... asOrganizationPartOf 0..1OrganizationPartOf
... legalAuthenticator 0..1LegalAuthenticatorIn a patient authored document, the legalAuthenticator identifies the single person legally responsible for the document and must be present if the document has been legally authenticated. (Note that per the following section, there may also be one or more document authenticators.) Based on local practice, patient authored documents may be provided without legal authentication. This implies that a patient authored document that does not contain this element has not been legally authenticated. The act of legal authentication requires a certain privilege be granted to the legal authenticator depending upon local policy. All patient documents have the potential for legal authentication, given the appropriate legal authority. Local policies MAY choose to delegate the function of legal authentication to a device or system that generates the document. In these cases, the legal authenticator is the person accepting responsibility for the document, not the generating device or system. Note that the legal authenticator, if present, must be a person.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: LA
.... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... time I1..1USRealmDateandTimeDTMUSFIELDED
.... signatureCode 1..1CS
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... code 1..1stringRequired Pattern: S
..... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
..... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
.... sdtcSignatureText 0..1EDXML: signatureText (urn:hl7-org:sdtc)
.... assignedEntity 1..1AssignedEntity
..... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... id 1..*IIThe combined @root and @extension attributes to record the information recipient?s identity in a secure, trusted, and unique way.
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... assigningAuthorityName 0..1string
...... displayable 0..1boolean
...... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
...... extension 0..1string
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... code 0..1CEBinding: Healthcare Provider Taxonomy (preferred)
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... code 0..1stringBinding: Personal And Legal Relationship Role Type (preferred)
...... codeSystem 0..1string
...... codeSystemName 0..1string
...... codeSystemVersion 0..1string
...... displayName 0..1string
...... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
...... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
...... originalText 0..1ED
...... translation 0..*CD
..... addr I1..*USRealmAddressADUSFIELDED
..... telecom 1..*TEL
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1uri
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
..... assignedPerson 1..1Person
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... name I1..*USRealmPersonNamePNUSFIELDED
...... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
..... representedOrganization 0..1Organization
... Slices for authenticator 0..*AuthenticatorThe authenticator identifies a participant or participants who attest to the accuracy of the information in the document.
Slice: Unordered, Open by value:signatureCode, value:assignedEntity
.... authenticator:All Slices Content/Rules for all slices
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUTHEN
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... time 1..1TS
..... signatureCode 1..1CS
..... sdtcSignatureText 0..1EDXML: signatureText (urn:hl7-org:sdtc)
..... assignedEntity 1..1AssignedEntity
...... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
...... templateId 0..*II
...... id 1..*IIThe combined @root and @extension attributes to record the authenticator?s identity in a secure, trusted, and unique way.
...... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
...... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
...... addr 0..*AD
...... telecom 0..*TEL
...... assignedPerson 0..1Person
...... representedOrganization 0..1Organization
.... authenticator:authenticator1 0..*Authenticator
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUTHEN
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... time I1..1USRealmDateandTimeDTMUSFIELDED
..... signatureCode 1..1CS
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... code 1..1stringRequired Pattern: S
...... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
...... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
..... sdtcSignatureText 0..1EDXML: signatureText (urn:hl7-org:sdtc)
..... assignedEntity 1..1AssignedEntity
...... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
...... templateId 0..*II
...... id 1..*II
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... assigningAuthorityName 0..1string
....... displayable 0..1boolean
....... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
....... extension 0..1string
...... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
...... code 0..1CEBinding: v3 Code System RoleCode (extensible)
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... code 0..1stringBinding: Healthcare Provider Taxonomy (preferred)
....... codeSystem 0..1string
....... codeSystemName 0..1string
....... codeSystemVersion 0..1string
....... displayName 0..1string
....... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
....... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
....... originalText 0..1ED
....... translation 0..*CD
...... addr I1..*USRealmAddressADUSFIELDED
...... telecom 1..*TEL
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... value 0..1uri
....... useablePeriod 0..*
........ useablePeriodIVL_TS
........ useablePeriodEIVL_TS
........ useablePeriodPIVL_TS
........ useablePeriodSXPR_TS
....... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
...... assignedPerson 1..1Person
....... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
....... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
....... templateId 0..*II
....... name I1..*USRealmPersonNamePNUSFIELDED
....... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
...... representedOrganization 0..1Organization
... Slices for participant 0..*Participant1The participant element identifies other supporting participants, including parents, relatives, caregivers, insurance policyholders, guarantors, and other participants related in some way to the patient. A supporting person or organization is an individual or an organization with a relationship to the patient. A supporting person who is playing multiple roles would be recorded in multiple participants (e.g., emergency contact and next-of-kin)
Slice: Unordered, Open by
.... participant:participant1 I0..*Participant11198-10006: **SHALL** contain associatedEntity/associatedPerson *AND/OR* associatedEntity/scopingOrganization (CONF:1198-10006).
1198-10007: When participant/@typeCode is *IND*, associatedEntity/@classCode **SHOULD** be selected from ValueSet 2.16.840.1.113883.11.20.9.33 INDRoleclassCodes *STATIC 2011-09-30* (CONF:1198-10007).
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
..... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... functionCode 0..1CE
..... time 0..1IVL_TS
..... associatedEntity 1..1AssociatedEntity
... inFulfillmentOf 0..*InFulfillmentOfThe inFulfillmentOf element represents orders that are fulfilled by this document such as a radiologists? report of an x-ray.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: FLFS
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... order 1..1Order
..... classCode 1..1codeBinding: ActClass (required)
..... moodCode 1..1codeBinding: ActMoodIntent (required)
Fixed Value: RQO
..... templateId 0..*II
..... id 1..*IIA scheduled appointment or service event in a practice management system may be represented using this id element.
..... code 0..1CEBinding: v3 Code System ActCode (extensible)
..... priorityCode 0..1CEBinding: ActPriority (extensible)
... documentationOf 0..*DocumentationOf
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: DOC
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... serviceEvent 1..1ServiceEventA serviceEvent represents the main act being documented, such as a colonoscopy or a cardiac stress study. In a provision of healthcare serviceEvent, the care providers, PCP, or other longitudinal providers, are recorded within the serviceEvent. If the document is about a single encounter, the providers associated can be recorded in the componentOf/encompassingEncounter template.
..... classCode 1..1codeBinding: ActClass (required)
..... moodCode 1..1codeBinding: ActMood (required)
Fixed Value: EVN
..... templateId 0..*II
..... id 0..*II
..... code 0..1CEThe code should be selected from a value set established by the document-level template for a specific type of Patient Generated Document.
..... effectiveTime 1..1IVL_TS
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1dateTime
...... inclusive 0..1boolean
...... operator 0..1code
...... low 1..1TS
...... high 0..1TS
...... width 0..1PQ
...... center 0..1TS
..... performer 0..*Performer1The performer participant represents clinicians who actually and principally carry out the serviceEvent. In a transfer of care this represents the healthcare providers involved in the current or pertinent historical care of the patient. Preferably, the patient?s key healthcare care team members would be listed, particularly their primary physician and any active consulting physicians, therapists, and counselors.
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... typeCode 1..1codeBinding: x_ServiceEventPerformer (required)
Fixed Value: DOC
...... realmCode 0..*CS
...... typeId 0..1II
...... templateId 0..*II
...... functionCode 0..1CEThe functionCode SHALL be selected from value set ParticipationType 2.16.840.1.113883.1.11.10901 When indicating the performer was the primary care physician the functionCode shall be =?PCP?
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... code 0..1stringBinding: Care Team Member Function (preferred)
....... codeSystem 0..1string
....... codeSystemName 0..1string
....... codeSystemVersion 0..1string
....... displayName 0..1string
....... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
....... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
....... originalText 0..1ED
....... translation 0..*CD
...... time 0..1IVL_TS
...... assignedEntity 1..1AssignedEntity
....... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
....... templateId 0..*II
....... id 1..*IIThe combined @root and @extension attributes record the performer?s identity in a secure, trusted, and unique way.
........ nullFlavor 0..1codeBinding: NullFlavor (required)
........ assigningAuthorityName 0..1string
........ displayable 0..1boolean
........ root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
........ extension 0..1string
....... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
....... code 0..1CEIf the assignedEntity is an individual, the code SHOULD be selected from value set PersonalandLegalRelationshipRoleType value set
Binding: Personal And Legal Relationship Role Type (preferred)
....... addr 0..*AD
....... telecom 0..*TEL
....... assignedPerson 0..1Person
....... representedOrganization 0..1Organization
... relatedDocument 0..*RelatedDocument
... Slices for authorization 0..*AuthorizationThe authorization element represents information about the patient?s consent. The type of consent is conveyed in consent/code. Consents in the header have been finalized (consent/statusCode must equal Completed) and should be on file. This specification does not address how 'Privacy Consent' is represented, but does not preclude the inclusion of ?Privacy Consent?. The authorization consent is used for referring to consents that are documented elsewhere in the EHR or medical record for a health condition and/or treatment that is described in the CDA document.
Slice: Unordered, Open by value:consent
.... authorization:authorization1 0..*Authorization
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUT
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... consent 1..1Consent
...... classCode 1..1codeBinding: ActClass (required)
Fixed Value: CONS
...... moodCode 1..1codeBinding: ActMood (required)
Fixed Value: EVN
...... templateId 0..*II
...... id 0..*II
...... code 0..1CEThe type of consent (e.g., a consent to perform the related serviceEvent) is conveyed in consent/code.
Binding: v3 Code System ActCode (extensible)
...... statusCode 1..1CSBinding: ActStatus (required)
....... code 1..1Fixed Value: completed
... componentOf 0..1ComponentOfThe encompassing encounter represents the setting of the clinical encounter during which the document act(s) or ServiceEvent(s) occurred. In order to represent providers associated with a specific encounter, they are recorded within the encompassingEncounter as participants. In a CCD, the encompassingEncounter may be used when documenting a specific encounter and its participants. All relevant encounters in a CCD may be listed in the encounters section.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUT
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... encompassingEncounter 1..1EncompassingEncounter
..... classCode 1..1codeBinding: ActClass (required)
Fixed Value: ENC
..... moodCode 1..1codeBinding: ActMood (required)
Fixed Value: EVN
..... templateId 0..*II
..... id 1..*II
..... code 0..1CEBinding: ActEncounterCode (extensible)
..... effectiveTime 1..1IVL_TS
..... sdtcAdmissionReferralSourceCode 0..1CEXML: admissionReferralSourceCode (urn:hl7-org:sdtc)
..... dischargeDispositionCode 0..1CEBinding: http://terminology.hl7.org/ValueSet/v3-EncounterDischargeDisposition (extensible)
..... responsibleParty 0..1Element
...... typeCode 1..1codeBinding: ParticipationType (required)
Fixed Value: RESP
...... assignedEntity 1..1AssignedEntity
..... encounterParticipant 0..*EncounterParticipant
..... location 0..1Element
...... typeCode 1..1codeBinding: ParticipationTargetLocation (required)
Fixed Value: LOC
...... healthCareFacility 1..1HealthCareFacility
... component 1..1Component2

doco Documentation for this format

This structure is derived from USRealmHeader

Summary

Mandatory: 14 elements (15 nested mandatory elements)

Slices

This structure defines the following Slices:

  • The element ClinicalDocument.templateId is sliced based on the values of value:root, value:extension
  • The element ClinicalDocument.informant is sliced based on the value of value:relatedEntity

Differential View

This structure is derived from USRealmHeader

NameFlagsCard.TypeDescription & Constraintsdoco
.. ClinicalDocument 1..1USRealmHeader
... Slices for templateId 0..*IISlice: Unordered, Open by value:root, value:extension
.... templateId:secondary I1..1II1198-32945: When asserting this templateId, all C-CDA 2.1 section and entry templates that had a previous version in C-CDA R1.1 **SHALL** include both the C-CDA 2.1 templateId and the C-CDA R1.1 templateId root without an extension. See C-CDA R2.1 Volume 1 - Design Considerations for additional detail (CONF:1198-32945).
..... root 1..1stringRequired Pattern: 2.16.840.1.113883.10.20.29.1
..... extension 1..1stringRequired Pattern: 2015-08-01
... recordTarget 1..1RecordTargetThe recordTarget records the patient whose health information is described by the clinical document; each recordTarget must contain at least one patientRole element. If the document receiver is interested in setting up a translator for the encounter with the patient, the receiver of the document will have to infer the need for a translator, based upon the language skills identified for the patient, the patient?s language of preference and the predominant language used by the organization receiving the CDA. HL7 Vocabulary simply describes guardian as a relationship to a ward. This need not be a formal legal relationship. When a guardian relationship exists for the patient, it can be represented, regardless of who is present at the time the document is generated. This need not be a formal legal relationship. A child?s parent can be represented in the guardian role. In this case, the guardian/code element would encode the personal relationship of "mother" for the child?s mom or "father" for the child?s dad. An elderly person's child can be represented in the guardian role. In this case, the guardian/code element would encode the personal relationship of "daughter" or "son", or if a legal relationship existed, the relationship of "legal guardian" could be encoded.
.... patientRole 1..1PatientRole
..... id 1..*II
..... patient 1..1Patient
...... guardian 0..*Guardian
....... id 0..*II
....... code 0..1CEBinding: Personal And Legal Relationship Role Type (required)
...... languageCommunication 0..*LanguageCommunication
....... preferenceInd 0..1BLIndicates a preference for information about care delivery and treatments be communicated (or translated if needed) into this language. If more than one languageCommunication is present, only one languageCommunication element SHALL have a preferenceInd with a value of 1.
..... providerOrganization 0..1OrganizationIf present, this organization represents the provider organization where the person is claiming to be a patient. undefined
... author 1..*AuthorThe author element represents the creator of the clinical document. The author may be a device, or a person. The person is the patient or the patient?s advocate.
.... assignedAuthor 1..1AssignedAuthor
..... id 1..*II
..... code 0..1CEWhen the author is a person who is not acting in the role of a clinician, this code encodes the personal or legal relationship between author and the patient.
...... code 1..1stringBinding: Personal And Legal Relationship Role Type (preferred)
.... assignedEntity 1..1AssignedEntity
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
... Slices for informant 0..*InformantThe informant element describes the source of the information in a medical document. Assigned health care providers may be a source of information when a document is created. (e.g., a nurse's aide who provides information about a recent significant health care event that occurred within an acute care facility.) In these cases, the assignedEntity element is used. When the informant is a personal relation, that informant is represented in the relatedEntity element, even if the personal relation is a medical professional. The code element of the relatedEntity describes the relationship between the informant and the patient. The relationship between the informant and the patient needs to be described to help the receiver of the clinical document understand the information in the document. Each informant can be either an assignedEntity (a clinician serving the patient) OR a relatedEntity (a person with a personal or legal relationship with the patient). The constraints here apply to relatedEntity.
Slice: Unordered, Open by value:relatedEntity
.... informant:informant1 0..*InformantThe informant element describes an information source for any content within the clinical document. This informant is constrained for use when the source of information is an assigned health care provider for the patient.
..... relatedEntity 1..1RelatedEntity
...... code 0..1CE
....... code 0..1stringBinding: Personal And Legal Relationship Role Type (preferred)
... custodian 1..1CustodianThe custodian element represents the organization or person that is in charge of maintaining the document. The custodian is the steward that is entrusted with the care of the document. Every CDA document has exactly one custodian. The custodian participation satisfies the CDA definition of Stewardship. Because CDA is an exchange standard and may not represent the original form of the authenticated document (e.g., CDA could include scanned copy of original), the custodian represents the steward of the original source document. The custodian may be the document originator, a health information exchange, or other responsible party. Also, the custodian may be the patient or an organization acting on behalf of the patient, such as a PHR organization.
.... assignedCustodian 1..1AssignedCustodian
..... representedCustodianOrganization 1..1CustodianOrganizationThe representedCustodianOrganization may be the person when the document is not maintained by an organization.
...... id 1..*IIThe combined @root and @extension attributes record the custodian organization?s identity in a secure, trusted, and unique way.
... informationRecipient 0..*InformationRecipientThe informationRecipient element records the intended recipient of the information at the time the document is created. For example, in cases where the intended recipient of the document is the patient's health chart, set the receivedOrganization to be the scoping organization for that chart.
.... intendedRecipient 1..1IntendedRecipient
..... id 0..*IIThe combined @root and @extension attributes to record the information recipient?s identity in a secure, trusted, and unique way.
...... root 0..1stringFor a provider, the id/@root ="2.16.840.1.113883.4.6" indicates the National Provider Identifier where id/@extension is the NPI number for the provider. The ids MAY reference the id of a person or organization entity specified elsewhere in the document.
... legalAuthenticator 0..1LegalAuthenticatorIn a patient authored document, the legalAuthenticator identifies the single person legally responsible for the document and must be present if the document has been legally authenticated. (Note that per the following section, there may also be one or more document authenticators.) Based on local practice, patient authored documents may be provided without legal authentication. This implies that a patient authored document that does not contain this element has not been legally authenticated. The act of legal authentication requires a certain privilege be granted to the legal authenticator depending upon local policy. All patient documents have the potential for legal authentication, given the appropriate legal authority. Local policies MAY choose to delegate the function of legal authentication to a device or system that generates the document. In these cases, the legal authenticator is the person accepting responsibility for the document, not the generating device or system. Note that the legal authenticator, if present, must be a person.
.... assignedEntity 1..1AssignedEntity
..... id 1..*IIThe combined @root and @extension attributes to record the information recipient?s identity in a secure, trusted, and unique way.
..... code 0..1CE
...... code 0..1stringBinding: Personal And Legal Relationship Role Type (preferred)
... authenticator 0..*AuthenticatorThe authenticator identifies a participant or participants who attest to the accuracy of the information in the document.
.... assignedEntity 1..1AssignedEntity
..... id 1..*IIThe combined @root and @extension attributes to record the authenticator?s identity in a secure, trusted, and unique way.
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
... participant 0..*Participant1The participant element identifies other supporting participants, including parents, relatives, caregivers, insurance policyholders, guarantors, and other participants related in some way to the patient. A supporting person or organization is an individual or an organization with a relationship to the patient. A supporting person who is playing multiple roles would be recorded in multiple participants (e.g., emergency contact and next-of-kin)
.... typeCode 1..1Unless otherwise specified by the document specific header constraints, when participant/@typeCode is IND, associatedEntity/@classCode SHALL be selected from ValueSet 2.16.840.1.113883.11.20.9.33 INDRoleclassCodes STATIC 2011-09-30
.... associatedEntity 1..1
..... code 0..1Binding: Personal And Legal Relationship Role Type (preferred)
... inFulfillmentOf 0..*InFulfillmentOfThe inFulfillmentOf element represents orders that are fulfilled by this document such as a radiologists? report of an x-ray.
.... order 1..1Order
..... id 1..*IIA scheduled appointment or service event in a practice management system may be represented using this id element.
... documentationOf 0..*DocumentationOf
.... serviceEvent 1..1ServiceEventA serviceEvent represents the main act being documented, such as a colonoscopy or a cardiac stress study. In a provision of healthcare serviceEvent, the care providers, PCP, or other longitudinal providers, are recorded within the serviceEvent. If the document is about a single encounter, the providers associated can be recorded in the componentOf/encompassingEncounter template.
..... code 0..1CEThe code should be selected from a value set established by the document-level template for a specific type of Patient Generated Document.
..... performer 0..*Performer1The performer participant represents clinicians who actually and principally carry out the serviceEvent. In a transfer of care this represents the healthcare providers involved in the current or pertinent historical care of the patient. Preferably, the patient?s key healthcare care team members would be listed, particularly their primary physician and any active consulting physicians, therapists, and counselors.
...... functionCode 0..1CEThe functionCode SHALL be selected from value set ParticipationType 2.16.840.1.113883.1.11.10901 When indicating the performer was the primary care physician the functionCode shall be =?PCP?
...... assignedEntity 1..1AssignedEntity
....... id 1..*IIThe combined @root and @extension attributes record the performer?s identity in a secure, trusted, and unique way.
....... code 0..1CEIf the assignedEntity is an individual, the code SHOULD be selected from value set PersonalandLegalRelationshipRoleType value set
Binding: Personal And Legal Relationship Role Type (preferred)

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. ClinicalDocument 1..1USRealmHeader
... classCode 1..1codeBinding: ActClass (extensible)
Fixed Value: DOCCLIN
... moodCode 1..1codeBinding: ActMood (required)
Fixed Value: EVN
... realmCode 1..1CSRequired Pattern: US
... typeId 1..1II
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... assigningAuthorityName 0..1string
.... displayable 0..1boolean
.... root 1..1stringRequired Pattern: 2.16.840.1.113883.1.3
.... extension 1..1stringRequired Pattern: POCD_HD000040
... Slices for templateId 0..*IISlice: Unordered, Open by value:root, value:extension
.... templateId:primary 1..1II
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... assigningAuthorityName 0..1string
..... displayable 0..1boolean
..... root 1..1stringRequired Pattern: 2.16.840.1.113883.10.20.22.1.1
..... extension 1..1stringRequired Pattern: 2015-08-01
.... templateId:secondary I1..1II1198-32945: When asserting this templateId, all C-CDA 2.1 section and entry templates that had a previous version in C-CDA R1.1 **SHALL** include both the C-CDA 2.1 templateId and the C-CDA R1.1 templateId root without an extension. See C-CDA R2.1 Volume 1 - Design Considerations for additional detail (CONF:1198-32945).
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... assigningAuthorityName 0..1string
..... displayable 0..1boolean
..... root 1..1stringRequired Pattern: 2.16.840.1.113883.10.20.29.1
..... extension 1..1stringRequired Pattern: 2015-08-01
... id I1..1II
... code I1..1CEBinding: http://terminology.hl7.org/ValueSet/v3-DocumentType (extensible)
... title 1..1EDThe title can either be a locally defined name or the displayName corresponding to clinicalDocument/code
... effectiveTime I1..1USRealmDateandTimeDTMUSFIELDED
... confidentialityCode 1..1CEBinding: HL7 BasicConfidentialityKind (preferred)
... languageCode 1..1CSBinding: VSAC 2.16.840.1.113883.1.11.11526 (required)
... setId I0..1II
... versionNumber I0..1INT
... copyTime 0..1TS
... recordTarget 1..1RecordTargetThe recordTarget records the patient whose health information is described by the clinical document; each recordTarget must contain at least one patientRole element. If the document receiver is interested in setting up a translator for the encounter with the patient, the receiver of the document will have to infer the need for a translator, based upon the language skills identified for the patient, the patient?s language of preference and the predominant language used by the organization receiving the CDA. HL7 Vocabulary simply describes guardian as a relationship to a ward. This need not be a formal legal relationship. When a guardian relationship exists for the patient, it can be represented, regardless of who is present at the time the document is generated. This need not be a formal legal relationship. A child?s parent can be represented in the guardian role. In this case, the guardian/code element would encode the personal relationship of "mother" for the child?s mom or "father" for the child?s dad. An elderly person's child can be represented in the guardian role. In this case, the guardian/code element would encode the personal relationship of "daughter" or "son", or if a legal relationship existed, the relationship of "legal guardian" could be encoded.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: RCT
.... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... patientRole 1..1PatientRole
..... classCode 1..1codeBinding: RoleClassRelationshipFormal (required)
Fixed Value: PAT
..... templateId 0..*II
..... id 1..*II
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... addr I1..*USRealmAddressADUSFIELDED
..... telecom 1..*TEL
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1uri
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
..... patient 1..1Patient
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... id 0..1II
...... name I1..*USRealmPatientNamePTNUSFIELDED
...... sdtcDesc 0..1EDXML: desc (urn:hl7-org:sdtc)
...... administrativeGenderCode 1..1CEBinding: Administrative Gender (HL7 V3) (required)
...... birthTime I1..1TS
...... sdtcDeceasedInd 0..1BLXML: deceasedInd (urn:hl7-org:sdtc)
...... sdtcDeceasedTime 0..1TSXML: deceasedTime (urn:hl7-org:sdtc)
...... sdtcMultipleBirthInd 0..1BLXML: multipleBirthInd (urn:hl7-org:sdtc)
...... sdtcMultipleBirthOrderNumber 0..1INT_POSXML: multipleBirthOrderNumber (urn:hl7-org:sdtc)
...... maritalStatusCode 0..1CEBinding: Marital Status (required)
...... religiousAffiliationCode 0..1CEBinding: Religious Affiliation (required)
...... raceCode 1..1CEBinding: Race Category Excluding Nulls (required)
...... sdtcRaceCode 0..*CEXML: raceCode (urn:hl7-org:sdtc)
Binding: Race Value Set (extensible)
...... ethnicGroupCode 1..1CEBinding: Ethnicity (required)
...... sdtcEthnicGroupCode 0..*CEXML: ethnicGroupCode (urn:hl7-org:sdtc)
Binding: Detailed Ethnicity (extensible)
...... guardian 0..*Guardian
....... classCode 1..1codeBinding: RoleClassAgent (required)
Fixed Value: GUARD
....... templateId 0..*II
....... id 0..*II
....... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
....... code 0..1CEBinding: Personal And Legal Relationship Role Type (required)
....... addr I0..*USRealmAddressADUSFIELDED
....... telecom 0..*TEL
........ nullFlavor 0..1codeBinding: NullFlavor (required)
........ value 0..1uri
........ useablePeriod 0..*
......... useablePeriodIVL_TS
......... useablePeriodEIVL_TS
......... useablePeriodPIVL_TS
......... useablePeriodSXPR_TS
........ use 0..1codeBinding: Telecom Use (US Realm Header) (required)
....... guardianPerson 1..1Person
........ classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
........ determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
........ templateId 0..*II
........ name I1..*USRealmPersonNamePNUSFIELDED
........ sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
....... guardianOrganization 0..1Organization
...... birthplace 0..1Birthplace
....... classCode 1..1codeBinding: RoleClassPassive (required)
Fixed Value: BIRTHPL
....... templateId 0..*II
....... place 1..1Place
........ classCode 1..1codeBinding: EntityClassPlace (required)
Fixed Value: PLC
........ determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
........ templateId 0..*II
........ name 0..1EN
........ addr I1..1AD
......... nullFlavor 0..1codeBinding: NullFlavor (required)
......... isNotOrdered 0..1boolean
......... use 0..*code
......... delimiter 0..*ADXP
.......... partType 0..1codeFixed Value: DEL
......... country 0..1ADXP
.......... partType 0..1codeFixed Value: CNT
......... state 0..*ADXP
.......... partType 0..1codeFixed Value: STA
......... county 0..*ADXP
.......... partType 0..1codeFixed Value: CPA
......... city 0..*ADXP
.......... partType 0..1codeFixed Value: CTY
......... postalCode 0..*ADXP
.......... partType 0..1codeFixed Value: ZIP
......... streetAddressLine 0..*ADXP
.......... partType 0..1codeFixed Value: SAL
......... houseNumber 0..*ADXP
.......... partType 0..1codeFixed Value: BNR
......... houseNumberNumeric 0..*ADXP
.......... partType 0..1codeFixed Value: BNN
......... direction 0..*ADXP
.......... partType 0..1codeFixed Value: DIR
......... streetName 0..*ADXP
.......... partType 0..1codeFixed Value: STR
......... streetNameBase 0..*ADXP
.......... partType 0..1codeFixed Value: STB
......... streetNameType 0..*ADXP
.......... partType 0..1codeFixed Value: STTYP
......... additionalLocator 0..*ADXP
.......... partType 0..1codeFixed Value: ADL
......... unitID 0..*ADXP
.......... partType 0..1codeFixed Value: UNID
......... unitType 0..*ADXP
.......... partType 0..1codeFixed Value: UNIT
......... careOf 0..*ADXP
.......... partType 0..1codeFixed Value: CAR
......... censusTract 0..*ADXP
.......... partType 0..1codeFixed Value: CEN
......... deliveryAddressLine 0..*ADXP
.......... partType 0..1codeFixed Value: DAL
......... deliveryInstallationType 0..*ADXP
.......... partType 0..1codeFixed Value: DINST
......... deliveryInstallationArea 0..*ADXP
.......... partType 0..1codeFixed Value: DINSTA
......... deliveryInstallationQualifier 0..*ADXP
.......... partType 0..1codeFixed Value: DINSTQ
......... deliveryMode 0..*ADXP
.......... partType 0..1codeFixed Value: DMOD
......... deliveryModeIdentifier 0..*ADXP
.......... partType 0..1codeFixed Value: DMODID
......... buildingNumberSuffix 0..*ADXP
.......... partType 0..1codeFixed Value: BNS
......... postBox 0..*ADXP
.......... partType 0..1codeFixed Value: POB
......... precinct 0..*ADXP
.......... partType 0..1codeFixed Value: PRE
......... other 0..1string
......... useablePeriod[x] 0..*
.......... useablePeriodHttp://hl7.org/fhir/cda/StructureDefinition/IVL-TSIVL_TS
.......... useablePeriodHttp://hl7.org/fhir/cda/StructureDefinition/EIVL-TSEIVL_TS
.......... useablePeriodHttp://hl7.org/fhir/cda/StructureDefinition/PIVL-TSPIVL_TS
.......... useablePeriodHttp://hl7.org/fhir/cda/StructureDefinition/SXPR-TSSXPR_TS
...... languageCommunication 0..*LanguageCommunication
....... templateId 0..*II
....... languageCode 1..1CSBinding: VSAC 2.16.840.1.113883.1.11.11526 (required)
....... modeCode 0..1CEBinding: LanguageAbilityMode (required)
....... proficiencyLevelCode 0..1CEBinding: LanguageAbilityProficiency (required)
....... preferenceInd 0..1BLIndicates a preference for information about care delivery and treatments be communicated (or translated if needed) into this language. If more than one languageCommunication is present, only one languageCommunication element SHALL have a preferenceInd with a value of 1.
..... providerOrganization 0..1OrganizationIf present, this organization represents the provider organization where the person is claiming to be a patient. undefined
...... classCode 1..1codeBinding: EntityClassOrganization (required)
Fixed Value: ORG
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... id 1..*II
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... assigningAuthorityName 0..1string
....... displayable 0..1boolean
....... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
....... extension 0..1string
...... name 1..*ON
...... telecom 1..*TEL
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... value 0..1uri
....... useablePeriod 0..*
........ useablePeriodIVL_TS
........ useablePeriodEIVL_TS
........ useablePeriodPIVL_TS
........ useablePeriodSXPR_TS
....... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
...... addr I1..*USRealmAddressADUSFIELDED
...... standardIndustryClassCode 0..1CEBinding: OrganizationIndustryClassNAICS (extensible)
...... asOrganizationPartOf 0..1OrganizationPartOf
... author 1..*AuthorThe author element represents the creator of the clinical document. The author may be a device, or a person. The person is the patient or the patient?s advocate.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUT
.... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... functionCode 0..1CE
.... time I1..1USRealmDateandTimeDTMUSFIELDED
.... assignedAuthor I1..1AssignedAuthor
..... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... Slices for id I1..*IISlice: Unordered, Open by value:root
...... id:id1 0..1II
....... nullFlavor 0..1codeIf id with @root="2.16.840.1.113883.4.6" National Provider Identifier is unknown then
Binding: NullFlavor (required)
Required Pattern: UNK
....... assigningAuthorityName 0..1string
....... displayable 0..1boolean
....... root 1..1stringRequired Pattern: 2.16.840.1.113883.4.6
....... extension 0..1string
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... code 0..1CEWhen the author is a person who is not acting in the role of a clinician, this code encodes the personal or legal relationship between author and the patient.
Binding: v3 Code System RoleCode (extensible)
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... code 1..1stringBinding: Personal And Legal Relationship Role Type (preferred)
...... codeSystem 0..1string
...... codeSystemName 0..1string
...... codeSystemVersion 0..1string
...... displayName 0..1string
...... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
...... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
...... originalText 0..1ED
...... translation 0..*CD
..... addr I1..*USRealmAddressADUSFIELDED
..... telecom 1..*TEL
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1uri
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
..... assignedPerson 0..1Person
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... name I1..*USRealmPersonNamePNUSFIELDED
...... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
..... assignedAuthoringDevice 0..1AuthoringDevice
...... classCode 1..1codeBinding: EntityClassDevice (required)
Fixed Value: DEV
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... code 0..1CEBinding: EntityCode (extensible)
...... manufacturerModelName 1..1SC
...... softwareName 1..1SC
...... asMaintainedEntity 0..*MaintainedEntity
..... representedOrganization 0..1Organization
... dataEnterer 0..1DataEntererThe dataEnterer element represents the person who transferred the content, written or dictated by someone else, into the clinical document. The guiding rule of thumb is that an author provides the content found within the header or body of the document, subject to their own interpretation, and the dataEnterer adds that information to the electronic system. In other words, a dataEnterer transfers information from one source to another (e.g., transcription from paper form to electronic system). If the dataEnterer is missing, this role is assumed to be played by the author.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: ENT
.... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... time 1..1TS
.... assignedEntity 1..1AssignedEntity
..... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... id 1..*II
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... assigningAuthorityName 0..1string
...... displayable 0..1boolean
...... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
...... extension 0..1string
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
..... addr I1..*USRealmAddressADUSFIELDED
..... telecom 1..*TEL
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1uri
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
..... assignedPerson 1..1Person
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... name I1..*USRealmPersonNamePNUSFIELDED
...... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
..... representedOrganization 0..1Organization
... Slices for informant 0..*InformantThe informant element describes the source of the information in a medical document. Assigned health care providers may be a source of information when a document is created. (e.g., a nurse's aide who provides information about a recent significant health care event that occurred within an acute care facility.) In these cases, the assignedEntity element is used. When the informant is a personal relation, that informant is represented in the relatedEntity element, even if the personal relation is a medical professional. The code element of the relatedEntity describes the relationship between the informant and the patient. The relationship between the informant and the patient needs to be described to help the receiver of the clinical document understand the information in the document. Each informant can be either an assignedEntity (a clinician serving the patient) OR a relatedEntity (a person with a personal or legal relationship with the patient). The constraints here apply to relatedEntity.
Slice: Unordered, Open by value:relatedEntity
.... informant:informant1 0..*InformantThe informant element describes an information source for any content within the clinical document. This informant is constrained for use when the source of information is an assigned health care provider for the patient.
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: INF
..... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... assignedEntity 1..1AssignedEntity
...... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
...... templateId 0..*II
...... id I1..*II
...... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
...... code 0..1CEBinding: Healthcare Provider Taxonomy (preferred)
...... addr I1..*USRealmAddressADUSFIELDED
...... telecom 0..*TEL
...... assignedPerson 1..1Person
....... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
....... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
....... templateId 0..*II
....... name I1..*USRealmPersonNamePNUSFIELDED
....... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
...... representedOrganization 0..1Organization
..... relatedEntity 1..1RelatedEntity
...... classCode 1..1codeBinding: RoleClassMutualRelationship (required)
...... templateId 0..*II
...... code 0..1CEBinding: PersonalRelationshipRoleType (extensible)
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... code 0..1stringBinding: Personal And Legal Relationship Role Type (preferred)
....... codeSystem 0..1string
....... codeSystemName 0..1string
....... codeSystemVersion 0..1string
....... displayName 0..1string
....... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
....... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
....... originalText 0..1ED
....... translation 0..*CD
...... addr 0..*AD
...... telecom 0..*TEL
...... effectiveTime 0..1IVL_TS
...... relatedPerson 0..1Person
.... informant:informant2 0..*Informant
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: INF
..... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... assignedEntity 0..1AssignedEntity
..... relatedEntity 1..1RelatedEntity
... custodian 1..1CustodianThe custodian element represents the organization or person that is in charge of maintaining the document. The custodian is the steward that is entrusted with the care of the document. Every CDA document has exactly one custodian. The custodian participation satisfies the CDA definition of Stewardship. Because CDA is an exchange standard and may not represent the original form of the authenticated document (e.g., CDA could include scanned copy of original), the custodian represents the steward of the original source document. The custodian may be the document originator, a health information exchange, or other responsible party. Also, the custodian may be the patient or an organization acting on behalf of the patient, such as a PHR organization.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: ENT
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... assignedCustodian 1..1AssignedCustodian
..... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... representedCustodianOrganization 1..1CustodianOrganizationThe representedCustodianOrganization may be the person when the document is not maintained by an organization.
...... classCode 1..1codeBinding: EntityClassOrganization (required)
Fixed Value: ORG
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... id 1..*IIThe combined @root and @extension attributes record the custodian organization?s identity in a secure, trusted, and unique way.
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... assigningAuthorityName 0..1string
....... displayable 0..1boolean
....... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
....... extension 0..1string
...... name 1..1ON
...... telecom 1..1TEL
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... value 0..1uri
....... useablePeriod 0..*
........ useablePeriodIVL_TS
........ useablePeriodEIVL_TS
........ useablePeriodPIVL_TS
........ useablePeriodSXPR_TS
....... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
...... addr I1..1USRealmAddressADUSFIELDED
... informationRecipient 0..*InformationRecipientThe informationRecipient element records the intended recipient of the information at the time the document is created. For example, in cases where the intended recipient of the document is the patient's health chart, set the receivedOrganization to be the scoping organization for that chart.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... intendedRecipient 1..1IntendedRecipient
..... classCode 1..1code
..... templateId 0..*II
..... id 0..*IIThe combined @root and @extension attributes to record the information recipient?s identity in a secure, trusted, and unique way.
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... assigningAuthorityName 0..1string
...... displayable 0..1boolean
...... root 0..1stringFor a provider, the id/@root ="2.16.840.1.113883.4.6" indicates the National Provider Identifier where id/@extension is the NPI number for the provider. The ids MAY reference the id of a person or organization entity specified elsewhere in the document.
...... extension 0..1string
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... addr 0..*AD
..... telecom 0..*TEL
..... informationRecipient 0..1Person
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... name I1..*USRealmPersonNamePNUSFIELDED
...... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
..... receivedOrganization 0..1Organization
...... classCode 1..1codeBinding: EntityClassOrganization (required)
Fixed Value: ORG
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... id 0..*II
...... name 1..1ON
...... telecom 0..*TEL
...... addr 0..*AD
...... standardIndustryClassCode 0..1CEBinding: OrganizationIndustryClassNAICS (extensible)
...... asOrganizationPartOf 0..1OrganizationPartOf
... legalAuthenticator 0..1LegalAuthenticatorIn a patient authored document, the legalAuthenticator identifies the single person legally responsible for the document and must be present if the document has been legally authenticated. (Note that per the following section, there may also be one or more document authenticators.) Based on local practice, patient authored documents may be provided without legal authentication. This implies that a patient authored document that does not contain this element has not been legally authenticated. The act of legal authentication requires a certain privilege be granted to the legal authenticator depending upon local policy. All patient documents have the potential for legal authentication, given the appropriate legal authority. Local policies MAY choose to delegate the function of legal authentication to a device or system that generates the document. In these cases, the legal authenticator is the person accepting responsibility for the document, not the generating device or system. Note that the legal authenticator, if present, must be a person.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: LA
.... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... time I1..1USRealmDateandTimeDTMUSFIELDED
.... signatureCode 1..1CS
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... code 1..1stringRequired Pattern: S
..... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
..... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
.... sdtcSignatureText 0..1EDXML: signatureText (urn:hl7-org:sdtc)
.... assignedEntity 1..1AssignedEntity
..... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... id 1..*IIThe combined @root and @extension attributes to record the information recipient?s identity in a secure, trusted, and unique way.
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... assigningAuthorityName 0..1string
...... displayable 0..1boolean
...... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
...... extension 0..1string
..... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
..... code 0..1CEBinding: Healthcare Provider Taxonomy (preferred)
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... code 0..1stringBinding: Personal And Legal Relationship Role Type (preferred)
...... codeSystem 0..1string
...... codeSystemName 0..1string
...... codeSystemVersion 0..1string
...... displayName 0..1string
...... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
...... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
...... originalText 0..1ED
...... translation 0..*CD
..... addr I1..*USRealmAddressADUSFIELDED
..... telecom 1..*TEL
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1uri
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
..... assignedPerson 1..1Person
...... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... name I1..*USRealmPersonNamePNUSFIELDED
...... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
..... representedOrganization 0..1Organization
... Slices for authenticator 0..*AuthenticatorThe authenticator identifies a participant or participants who attest to the accuracy of the information in the document.
Slice: Unordered, Open by value:signatureCode, value:assignedEntity
.... authenticator:All Slices Content/Rules for all slices
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUTHEN
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... time 1..1TS
..... signatureCode 1..1CS
..... sdtcSignatureText 0..1EDXML: signatureText (urn:hl7-org:sdtc)
..... assignedEntity 1..1AssignedEntity
...... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
...... templateId 0..*II
...... id 1..*IIThe combined @root and @extension attributes to record the authenticator?s identity in a secure, trusted, and unique way.
...... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
...... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
...... addr 0..*AD
...... telecom 0..*TEL
...... assignedPerson 0..1Person
...... representedOrganization 0..1Organization
.... authenticator:authenticator1 0..*Authenticator
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUTHEN
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... time I1..1USRealmDateandTimeDTMUSFIELDED
..... signatureCode 1..1CS
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... code 1..1stringRequired Pattern: S
...... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
...... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
..... sdtcSignatureText 0..1EDXML: signatureText (urn:hl7-org:sdtc)
..... assignedEntity 1..1AssignedEntity
...... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
...... templateId 0..*II
...... id 1..*II
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... assigningAuthorityName 0..1string
....... displayable 0..1boolean
....... root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
....... extension 0..1string
...... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
...... code 0..1CEBinding: v3 Code System RoleCode (extensible)
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... code 0..1stringBinding: Healthcare Provider Taxonomy (preferred)
....... codeSystem 0..1string
....... codeSystemName 0..1string
....... codeSystemVersion 0..1string
....... displayName 0..1string
....... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
....... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
....... originalText 0..1ED
....... translation 0..*CD
...... addr I1..*USRealmAddressADUSFIELDED
...... telecom 1..*TEL
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... value 0..1uri
....... useablePeriod 0..*
........ useablePeriodIVL_TS
........ useablePeriodEIVL_TS
........ useablePeriodPIVL_TS
........ useablePeriodSXPR_TS
....... use 0..1codeBinding: Telecom Use (US Realm Header) (required)
...... assignedPerson 1..1Person
....... classCode 1..1codeBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
....... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
....... templateId 0..*II
....... name I1..*USRealmPersonNamePNUSFIELDED
....... sdtcAsPatientRelationship 0..*CEXML: asPatientRelationship (urn:hl7-org:sdtc)
...... representedOrganization 0..1Organization
... Slices for participant 0..*Participant1The participant element identifies other supporting participants, including parents, relatives, caregivers, insurance policyholders, guarantors, and other participants related in some way to the patient. A supporting person or organization is an individual or an organization with a relationship to the patient. A supporting person who is playing multiple roles would be recorded in multiple participants (e.g., emergency contact and next-of-kin)
Slice: Unordered, Open by
.... participant:participant1 I0..*Participant11198-10006: **SHALL** contain associatedEntity/associatedPerson *AND/OR* associatedEntity/scopingOrganization (CONF:1198-10006).
1198-10007: When participant/@typeCode is *IND*, associatedEntity/@classCode **SHOULD** be selected from ValueSet 2.16.840.1.113883.11.20.9.33 INDRoleclassCodes *STATIC 2011-09-30* (CONF:1198-10007).
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
..... contextControlCode 0..1codeBinding: ContextControl (required)
Fixed Value: OP
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... functionCode 0..1CE
..... time 0..1IVL_TS
..... associatedEntity 1..1AssociatedEntity
... inFulfillmentOf 0..*InFulfillmentOfThe inFulfillmentOf element represents orders that are fulfilled by this document such as a radiologists? report of an x-ray.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: FLFS
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... order 1..1Order
..... classCode 1..1codeBinding: ActClass (required)
..... moodCode 1..1codeBinding: ActMoodIntent (required)
Fixed Value: RQO
..... templateId 0..*II
..... id 1..*IIA scheduled appointment or service event in a practice management system may be represented using this id element.
..... code 0..1CEBinding: v3 Code System ActCode (extensible)
..... priorityCode 0..1CEBinding: ActPriority (extensible)
... documentationOf 0..*DocumentationOf
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: DOC
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... serviceEvent 1..1ServiceEventA serviceEvent represents the main act being documented, such as a colonoscopy or a cardiac stress study. In a provision of healthcare serviceEvent, the care providers, PCP, or other longitudinal providers, are recorded within the serviceEvent. If the document is about a single encounter, the providers associated can be recorded in the componentOf/encompassingEncounter template.
..... classCode 1..1codeBinding: ActClass (required)
..... moodCode 1..1codeBinding: ActMood (required)
Fixed Value: EVN
..... templateId 0..*II
..... id 0..*II
..... code 0..1CEThe code should be selected from a value set established by the document-level template for a specific type of Patient Generated Document.
..... effectiveTime 1..1IVL_TS
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1dateTime
...... inclusive 0..1boolean
...... operator 0..1code
...... low 1..1TS
...... high 0..1TS
...... width 0..1PQ
...... center 0..1TS
..... performer 0..*Performer1The performer participant represents clinicians who actually and principally carry out the serviceEvent. In a transfer of care this represents the healthcare providers involved in the current or pertinent historical care of the patient. Preferably, the patient?s key healthcare care team members would be listed, particularly their primary physician and any active consulting physicians, therapists, and counselors.
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... typeCode 1..1codeBinding: x_ServiceEventPerformer (required)
Fixed Value: DOC
...... realmCode 0..*CS
...... typeId 0..1II
...... templateId 0..*II
...... functionCode 0..1CEThe functionCode SHALL be selected from value set ParticipationType 2.16.840.1.113883.1.11.10901 When indicating the performer was the primary care physician the functionCode shall be =?PCP?
....... nullFlavor 0..1codeBinding: NullFlavor (required)
....... code 0..1stringBinding: Care Team Member Function (preferred)
....... codeSystem 0..1string
....... codeSystemName 0..1string
....... codeSystemVersion 0..1string
....... displayName 0..1string
....... sdtcValueSet 0..1stringXML: valueSet (urn:hl7-org:sdtc)
....... sdtcValueSetVersion 0..1stringXML: valueSetVersion (urn:hl7-org:sdtc)
....... originalText 0..1ED
....... translation 0..*CD
...... time 0..1IVL_TS
...... assignedEntity 1..1AssignedEntity
....... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
....... templateId 0..*II
....... id 1..*IIThe combined @root and @extension attributes record the performer?s identity in a secure, trusted, and unique way.
........ nullFlavor 0..1codeBinding: NullFlavor (required)
........ assigningAuthorityName 0..1string
........ displayable 0..1boolean
........ root 0..1stringRequired Pattern: 2.16.840.1.113883.4.6
........ extension 0..1string
....... sdtcIdentifiedBy 0..*IdentifiedByXML: identifiedBy (urn:hl7-org:sdtc)
....... code 0..1CEIf the assignedEntity is an individual, the code SHOULD be selected from value set PersonalandLegalRelationshipRoleType value set
Binding: Personal And Legal Relationship Role Type (preferred)
....... addr 0..*AD
....... telecom 0..*TEL
....... assignedPerson 0..1Person
....... representedOrganization 0..1Organization
... relatedDocument 0..*RelatedDocument
... Slices for authorization 0..*AuthorizationThe authorization element represents information about the patient?s consent. The type of consent is conveyed in consent/code. Consents in the header have been finalized (consent/statusCode must equal Completed) and should be on file. This specification does not address how 'Privacy Consent' is represented, but does not preclude the inclusion of ?Privacy Consent?. The authorization consent is used for referring to consents that are documented elsewhere in the EHR or medical record for a health condition and/or treatment that is described in the CDA document.
Slice: Unordered, Open by value:consent
.... authorization:authorization1 0..*Authorization
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUT
..... realmCode 0..*CS
..... typeId 0..1II
..... templateId 0..*II
..... consent 1..1Consent
...... classCode 1..1codeBinding: ActClass (required)
Fixed Value: CONS
...... moodCode 1..1codeBinding: ActMood (required)
Fixed Value: EVN
...... templateId 0..*II
...... id 0..*II
...... code 0..1CEThe type of consent (e.g., a consent to perform the related serviceEvent) is conveyed in consent/code.
Binding: v3 Code System ActCode (extensible)
...... statusCode 1..1CSBinding: ActStatus (required)
....... code 1..1Fixed Value: completed
... componentOf 0..1ComponentOfThe encompassing encounter represents the setting of the clinical encounter during which the document act(s) or ServiceEvent(s) occurred. In order to represent providers associated with a specific encounter, they are recorded within the encompassingEncounter as participants. In a CCD, the encompassingEncounter may be used when documenting a specific encounter and its participants. All relevant encounters in a CCD may be listed in the encounters section.
.... nullFlavor 0..1codeBinding: NullFlavor (required)
.... typeCode 0..1codeBinding: ParticipationType (required)
Fixed Value: AUT
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... encompassingEncounter 1..1EncompassingEncounter
..... classCode 1..1codeBinding: ActClass (required)
Fixed Value: ENC
..... moodCode 1..1codeBinding: ActMood (required)
Fixed Value: EVN
..... templateId 0..*II
..... id 1..*II
..... code 0..1CEBinding: ActEncounterCode (extensible)
..... effectiveTime 1..1IVL_TS
..... sdtcAdmissionReferralSourceCode 0..1CEXML: admissionReferralSourceCode (urn:hl7-org:sdtc)
..... dischargeDispositionCode 0..1CEBinding: http://terminology.hl7.org/ValueSet/v3-EncounterDischargeDisposition (extensible)
..... responsibleParty 0..1Element
...... typeCode 1..1codeBinding: ParticipationType (required)
Fixed Value: RESP
...... assignedEntity 1..1AssignedEntity
..... encounterParticipant 0..*EncounterParticipant
..... location 0..1Element
...... typeCode 1..1codeBinding: ParticipationTargetLocation (required)
Fixed Value: LOC
...... healthCareFacility 1..1HealthCareFacility
... component 1..1Component2

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron

Terminology Bindings

PathConformanceValueSet / Code
ClinicalDocument.classCodeextensibleFixed Value: DOCCLIN
ClinicalDocument.moodCoderequiredFixed Value: EVN
ClinicalDocument.typeId.nullFlavorrequiredNullFlavor
ClinicalDocument.templateId:primary.nullFlavorrequiredNullFlavor
ClinicalDocument.templateId:secondary.nullFlavorrequiredNullFlavor
ClinicalDocument.codeextensiblehttp://terminology.hl7.org/ValueSet/v3-DocumentType
ClinicalDocument.confidentialityCodepreferredHL7 BasicConfidentialityKind
ClinicalDocument.languageCoderequiredhttp://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.1.11.11526
ClinicalDocument.recordTarget.nullFlavorrequiredNullFlavor
ClinicalDocument.recordTarget.typeCoderequiredFixed Value: RCT
ClinicalDocument.recordTarget.contextControlCoderequiredFixed Value: OP
ClinicalDocument.recordTarget.patientRole.classCoderequiredFixed Value: PAT
ClinicalDocument.recordTarget.patientRole.telecom.nullFlavorrequiredNullFlavor
ClinicalDocument.recordTarget.patientRole.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.recordTarget.patientRole.patient.classCoderequiredFixed Value: PSN
ClinicalDocument.recordTarget.patientRole.patient.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.recordTarget.patientRole.patient.administrativeGenderCoderequiredAdministrative Gender (HL7 V3)
ClinicalDocument.recordTarget.patientRole.patient.maritalStatusCoderequiredMaritalStatus
ClinicalDocument.recordTarget.patientRole.patient.religiousAffiliationCoderequiredReligious Affiliation
ClinicalDocument.recordTarget.patientRole.patient.raceCoderequiredRace Category Excluding Nulls
ClinicalDocument.recordTarget.patientRole.patient.sdtcRaceCodeextensibleRaceValueSet
ClinicalDocument.recordTarget.patientRole.patient.ethnicGroupCoderequiredEthnicity
ClinicalDocument.recordTarget.patientRole.patient.sdtcEthnicGroupCodeextensibleDetailedEthnicity
ClinicalDocument.recordTarget.patientRole.patient.guardian.classCoderequiredFixed Value: GUARD
ClinicalDocument.recordTarget.patientRole.patient.guardian.coderequiredPersonal And Legal Relationship Role Type
ClinicalDocument.recordTarget.patientRole.patient.guardian.telecom.nullFlavorrequiredNullFlavor
ClinicalDocument.recordTarget.patientRole.patient.guardian.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.recordTarget.patientRole.patient.guardian.guardianPerson.classCoderequiredFixed Value: PSN
ClinicalDocument.recordTarget.patientRole.patient.guardian.guardianPerson.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.recordTarget.patientRole.patient.birthplace.classCoderequiredFixed Value: BIRTHPL
ClinicalDocument.recordTarget.patientRole.patient.birthplace.place.classCoderequiredFixed Value: PLC
ClinicalDocument.recordTarget.patientRole.patient.birthplace.place.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.recordTarget.patientRole.patient.birthplace.place.addr.nullFlavorrequiredNullFlavor
ClinicalDocument.recordTarget.patientRole.patient.languageCommunication.languageCoderequiredhttp://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.1.11.11526
ClinicalDocument.recordTarget.patientRole.patient.languageCommunication.modeCoderequiredLanguageAbilityMode
ClinicalDocument.recordTarget.patientRole.patient.languageCommunication.proficiencyLevelCoderequiredLanguageAbilityProficiency
ClinicalDocument.recordTarget.patientRole.providerOrganization.classCoderequiredFixed Value: ORG
ClinicalDocument.recordTarget.patientRole.providerOrganization.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.recordTarget.patientRole.providerOrganization.id.nullFlavorrequiredNullFlavor
ClinicalDocument.recordTarget.patientRole.providerOrganization.telecom.nullFlavorrequiredNullFlavor
ClinicalDocument.recordTarget.patientRole.providerOrganization.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.recordTarget.patientRole.providerOrganization.standardIndustryClassCodeextensibleOrganizationIndustryClassNAICS
ClinicalDocument.author.nullFlavorrequiredNullFlavor
ClinicalDocument.author.typeCoderequiredFixed Value: AUT
ClinicalDocument.author.contextControlCoderequiredFixed Value: OP
ClinicalDocument.author.assignedAuthor.classCoderequiredFixed Value: ASSIGNED
ClinicalDocument.author.assignedAuthor.id:id1.nullFlavorrequiredPattern: UNK
ClinicalDocument.author.assignedAuthor.codeextensibleRoleCode
ClinicalDocument.author.assignedAuthor.code.nullFlavorrequiredNullFlavor
ClinicalDocument.author.assignedAuthor.code.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.author.assignedAuthor.telecom.nullFlavorrequiredNullFlavor
ClinicalDocument.author.assignedAuthor.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.author.assignedAuthor.assignedPerson.classCoderequiredFixed Value: PSN
ClinicalDocument.author.assignedAuthor.assignedPerson.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.author.assignedAuthor.assignedAuthoringDevice.classCoderequiredFixed Value: DEV
ClinicalDocument.author.assignedAuthor.assignedAuthoringDevice.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.author.assignedAuthor.assignedAuthoringDevice.codeextensibleEntityCode
ClinicalDocument.dataEnterer.nullFlavorrequiredNullFlavor
ClinicalDocument.dataEnterer.typeCoderequiredFixed Value: ENT
ClinicalDocument.dataEnterer.contextControlCoderequiredFixed Value: OP
ClinicalDocument.dataEnterer.assignedEntity.classCoderequiredFixed Value: ASSIGNED
ClinicalDocument.dataEnterer.assignedEntity.id.nullFlavorrequiredNullFlavor
ClinicalDocument.dataEnterer.assignedEntity.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.dataEnterer.assignedEntity.telecom.nullFlavorrequiredNullFlavor
ClinicalDocument.dataEnterer.assignedEntity.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.dataEnterer.assignedEntity.assignedPerson.classCoderequiredFixed Value: PSN
ClinicalDocument.dataEnterer.assignedEntity.assignedPerson.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.informant:informant1.nullFlavorrequiredNullFlavor
ClinicalDocument.informant:informant1.typeCoderequiredFixed Value: INF
ClinicalDocument.informant:informant1.contextControlCoderequiredFixed Value: OP
ClinicalDocument.informant:informant1.assignedEntity.classCoderequiredFixed Value: ASSIGNED
ClinicalDocument.informant:informant1.assignedEntity.codepreferredHealthcareProviderTaxonomy
ClinicalDocument.informant:informant1.assignedEntity.assignedPerson.classCoderequiredFixed Value: PSN
ClinicalDocument.informant:informant1.assignedEntity.assignedPerson.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.informant:informant1.relatedEntity.classCoderequiredRoleClassMutualRelationship
ClinicalDocument.informant:informant1.relatedEntity.codeextensiblePersonalRelationshipRoleType
ClinicalDocument.informant:informant1.relatedEntity.code.nullFlavorrequiredNullFlavor
ClinicalDocument.informant:informant1.relatedEntity.code.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.informant:informant2.nullFlavorrequiredNullFlavor
ClinicalDocument.informant:informant2.typeCoderequiredFixed Value: INF
ClinicalDocument.informant:informant2.contextControlCoderequiredFixed Value: OP
ClinicalDocument.custodian.nullFlavorrequiredNullFlavor
ClinicalDocument.custodian.typeCoderequiredFixed Value: ENT
ClinicalDocument.custodian.assignedCustodian.classCoderequiredFixed Value: ASSIGNED
ClinicalDocument.custodian.assignedCustodian.representedCustodianOrganization.classCoderequiredFixed Value: ORG
ClinicalDocument.custodian.assignedCustodian.representedCustodianOrganization.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.custodian.assignedCustodian.representedCustodianOrganization.id.nullFlavorrequiredNullFlavor
ClinicalDocument.custodian.assignedCustodian.representedCustodianOrganization.telecom.nullFlavorrequiredNullFlavor
ClinicalDocument.custodian.assignedCustodian.representedCustodianOrganization.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.informationRecipient.nullFlavorrequiredNullFlavor
ClinicalDocument.informationRecipient.typeCoderequiredParticipationType
ClinicalDocument.informationRecipient.intendedRecipient.id.nullFlavorrequiredNullFlavor
ClinicalDocument.informationRecipient.intendedRecipient.informationRecipient.classCoderequiredFixed Value: PSN
ClinicalDocument.informationRecipient.intendedRecipient.informationRecipient.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.informationRecipient.intendedRecipient.receivedOrganization.classCoderequiredFixed Value: ORG
ClinicalDocument.informationRecipient.intendedRecipient.receivedOrganization.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.informationRecipient.intendedRecipient.receivedOrganization.standardIndustryClassCodeextensibleOrganizationIndustryClassNAICS
ClinicalDocument.legalAuthenticator.nullFlavorrequiredNullFlavor
ClinicalDocument.legalAuthenticator.typeCoderequiredFixed Value: LA
ClinicalDocument.legalAuthenticator.contextControlCoderequiredFixed Value: OP
ClinicalDocument.legalAuthenticator.signatureCode.nullFlavorrequiredNullFlavor
ClinicalDocument.legalAuthenticator.assignedEntity.classCoderequiredFixed Value: ASSIGNED
ClinicalDocument.legalAuthenticator.assignedEntity.id.nullFlavorrequiredNullFlavor
ClinicalDocument.legalAuthenticator.assignedEntity.codepreferredHealthcareProviderTaxonomy
ClinicalDocument.legalAuthenticator.assignedEntity.code.nullFlavorrequiredNullFlavor
ClinicalDocument.legalAuthenticator.assignedEntity.code.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.legalAuthenticator.assignedEntity.telecom.nullFlavorrequiredNullFlavor
ClinicalDocument.legalAuthenticator.assignedEntity.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.legalAuthenticator.assignedEntity.assignedPerson.classCoderequiredFixed Value: PSN
ClinicalDocument.legalAuthenticator.assignedEntity.assignedPerson.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.authenticator.nullFlavorrequiredNullFlavor
ClinicalDocument.authenticator.typeCoderequiredFixed Value: AUTHEN
ClinicalDocument.authenticator.assignedEntity.classCoderequiredFixed Value: ASSIGNED
ClinicalDocument.authenticator.assignedEntity.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.authenticator:authenticator1.nullFlavorrequiredNullFlavor
ClinicalDocument.authenticator:authenticator1.typeCoderequiredFixed Value: AUTHEN
ClinicalDocument.authenticator:authenticator1.signatureCode.nullFlavorrequiredNullFlavor
ClinicalDocument.authenticator:authenticator1.assignedEntity.classCoderequiredFixed Value: ASSIGNED
ClinicalDocument.authenticator:authenticator1.assignedEntity.id.nullFlavorrequiredNullFlavor
ClinicalDocument.authenticator:authenticator1.assignedEntity.codeextensibleRoleCode
ClinicalDocument.authenticator:authenticator1.assignedEntity.code.nullFlavorrequiredNullFlavor
ClinicalDocument.authenticator:authenticator1.assignedEntity.code.codepreferredHealthcareProviderTaxonomy
ClinicalDocument.authenticator:authenticator1.assignedEntity.telecom.nullFlavorrequiredNullFlavor
ClinicalDocument.authenticator:authenticator1.assignedEntity.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.authenticator:authenticator1.assignedEntity.assignedPerson.classCoderequiredFixed Value: PSN
ClinicalDocument.authenticator:authenticator1.assignedEntity.assignedPerson.determinerCoderequiredFixed Value: INSTANCE
ClinicalDocument.participant:participant1.nullFlavorrequiredNullFlavor
ClinicalDocument.participant:participant1.typeCoderequiredParticipationType
ClinicalDocument.participant:participant1.contextControlCoderequiredFixed Value: OP
ClinicalDocument.inFulfillmentOf.nullFlavorrequiredNullFlavor
ClinicalDocument.inFulfillmentOf.typeCoderequiredFixed Value: FLFS
ClinicalDocument.inFulfillmentOf.order.classCoderequiredActClass
ClinicalDocument.inFulfillmentOf.order.moodCoderequiredFixed Value: RQO
ClinicalDocument.inFulfillmentOf.order.codeextensibleActCode
ClinicalDocument.inFulfillmentOf.order.priorityCodeextensibleActPriority
ClinicalDocument.documentationOf.nullFlavorrequiredNullFlavor
ClinicalDocument.documentationOf.typeCoderequiredFixed Value: DOC
ClinicalDocument.documentationOf.serviceEvent.classCoderequiredActClass
ClinicalDocument.documentationOf.serviceEvent.moodCoderequiredFixed Value: EVN
ClinicalDocument.documentationOf.serviceEvent.effectiveTime.nullFlavorrequiredNullFlavor
ClinicalDocument.documentationOf.serviceEvent.performer.nullFlavorrequiredNullFlavor
ClinicalDocument.documentationOf.serviceEvent.performer.typeCoderequiredFixed Value: DOC
ClinicalDocument.documentationOf.serviceEvent.performer.functionCode.nullFlavorrequiredNullFlavor
ClinicalDocument.documentationOf.serviceEvent.performer.functionCode.codepreferredCare Team Member Function
ClinicalDocument.documentationOf.serviceEvent.performer.assignedEntity.classCoderequiredFixed Value: ASSIGNED
ClinicalDocument.documentationOf.serviceEvent.performer.assignedEntity.id.nullFlavorrequiredNullFlavor
ClinicalDocument.documentationOf.serviceEvent.performer.assignedEntity.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.authorization:authorization1.nullFlavorrequiredNullFlavor
ClinicalDocument.authorization:authorization1.typeCoderequiredFixed Value: AUT
ClinicalDocument.authorization:authorization1.consent.classCoderequiredFixed Value: CONS
ClinicalDocument.authorization:authorization1.consent.moodCoderequiredFixed Value: EVN
ClinicalDocument.authorization:authorization1.consent.codeextensibleActCode
ClinicalDocument.authorization:authorization1.consent.statusCoderequiredActStatus
ClinicalDocument.componentOf.nullFlavorrequiredNullFlavor
ClinicalDocument.componentOf.typeCoderequiredFixed Value: AUT
ClinicalDocument.componentOf.encompassingEncounter.classCoderequiredFixed Value: ENC
ClinicalDocument.componentOf.encompassingEncounter.moodCoderequiredFixed Value: EVN
ClinicalDocument.componentOf.encompassingEncounter.codeextensibleActEncounterCode
ClinicalDocument.componentOf.encompassingEncounter.dischargeDispositionCodeextensiblehttp://terminology.hl7.org/ValueSet/v3-EncounterDischargeDisposition
ClinicalDocument.componentOf.encompassingEncounter.responsibleParty.typeCoderequiredFixed Value: RESP
ClinicalDocument.componentOf.encompassingEncounter.location.typeCoderequiredFixed Value: LOC

Constraints

IdGradePathDetailsRequirements
1198-32945errorClinicalDocument.templateId:secondaryWhen asserting this templateId, all C-CDA 2.1 section and entry templates that had a previous version in C-CDA R1.1 **SHALL** include both the C-CDA 2.1 templateId and the C-CDA R1.1 templateId root without an extension. See C-CDA R2.1 Volume 1 - Design Considerations for additional detail (CONF:1198-32945).
:
1198-9991warningClinicalDocument.idThis id **SHALL** be a globally unique identifier for the document (CONF:1198-9991).
:
1198-9992errorClinicalDocument.codeThis code **SHALL** specify the particular kind of document (e.g., History and Physical, Discharge Summary, Progress Note) (CONF:1198-9992).
:
1198-32948errorClinicalDocument.codeThis code **SHALL** be drawn from the LOINC document type ontology (LOINC codes where SCALE = DOC) (CONF:1198-32948).
:
81-10127errorClinicalDocument.effectiveTime**SHALL** be precise to the day (CONF:81-10127).
:
81-10128warningClinicalDocument.effectiveTime**SHOULD** be precise to the minute (CONF:81-10128).
:
81-10129warningClinicalDocument.effectiveTime**MAY** be precise to the second (CONF:81-10129).
:
81-10130warningClinicalDocument.effectiveTimeIf more precise than day, **SHOULD** include time-zone offset (CONF:81-10130).
:
1198-6380errorClinicalDocument.setIdIf setId is present versionNumber **SHALL** be present (CONF:1198-6380).
:
1198-6387errorClinicalDocument.versionNumberIf versionNumber is present setId **SHALL** be present (CONF:1198-6387).
:
81-7296errorClinicalDocument.recordTarget.patientRole.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-7278errorClinicalDocument.recordTarget.patientRole.patient.name**SHALL NOT** have mixed content except for white space (CONF:81-7278).
:
1198-5299errorClinicalDocument.recordTarget.patientRole.patient.birthTime**SHALL** be precise to year (CONF:1198-5299).
:
1198-5300warningClinicalDocument.recordTarget.patientRole.patient.birthTime**SHOULD** be precise to day (CONF:1198-5300).
:
1198-32418warningClinicalDocument.recordTarget.patientRole.patient.birthTime**MAY** be precise to the minute (CONF:1198-32418). For cases where information about newborn's time of birth needs to be captured.
:
81-7296errorClinicalDocument.recordTarget.patientRole.patient.guardian.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-9371errorClinicalDocument.recordTarget.patientRole.patient.guardian.guardianPerson.nameThe content of name **SHALL** be either a conformant Patient Name (PTN.US.FIELDED), or a string (CONF:81-9371).
:
81-9372errorClinicalDocument.recordTarget.patientRole.patient.guardian.guardianPerson.nameThe string **SHALL NOT** contain name parts (CONF:81-9372).
:
1198-5402warningClinicalDocument.recordTarget.patientRole.patient.birthplace.place.addrIf country is US, this addr **SHALL** contain exactly one [1..1] state, which **SHALL** be selected from ValueSet StateValueSet 2.16.840.1.113883.3.88.12.80.1 *DYNAMIC* (CONF:1198-5402).
:
1198-5403warningClinicalDocument.recordTarget.patientRole.patient.birthplace.place.addrIf country is US, this addr **MAY** contain zero or one [0..1] postalCode, which **SHALL** be selected from ValueSet PostalCode urn:oid:2.16.840.1.113883.3.88.12.80.2 *DYNAMIC* (CONF:1198-5403).
:
81-7296errorClinicalDocument.recordTarget.patientRole.providerOrganization.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-10127errorClinicalDocument.author.time**SHALL** be precise to the day (CONF:81-10127).
:
81-10128warningClinicalDocument.author.time**SHOULD** be precise to the minute (CONF:81-10128).
:
81-10129warningClinicalDocument.author.time**MAY** be precise to the second (CONF:81-10129).
:
81-10130warningClinicalDocument.author.timeIf more precise than day, **SHOULD** include time-zone offset (CONF:81-10130).
:
1198-16790errorClinicalDocument.author.assignedAuthorThere **SHALL** be exactly one assignedAuthor/assignedPerson or exactly one assignedAuthor/assignedAuthoringDevice (CONF:1198-16790).
:
1198-5449nullClinicalDocument.author.assignedAuthor.idIf this assignedAuthor is not an assignedPerson, this assignedAuthor SHALL contain at least one [1..*] id (CONF:1198-5449).
:
81-7296errorClinicalDocument.author.assignedAuthor.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-9371errorClinicalDocument.author.assignedAuthor.assignedPerson.nameThe content of name **SHALL** be either a conformant Patient Name (PTN.US.FIELDED), or a string (CONF:81-9371).
:
81-9372errorClinicalDocument.author.assignedAuthor.assignedPerson.nameThe string **SHALL NOT** contain name parts (CONF:81-9372).
:
81-7296errorClinicalDocument.dataEnterer.assignedEntity.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-9371errorClinicalDocument.dataEnterer.assignedEntity.assignedPerson.nameThe content of name **SHALL** be either a conformant Patient Name (PTN.US.FIELDED), or a string (CONF:81-9371).
:
81-9372errorClinicalDocument.dataEnterer.assignedEntity.assignedPerson.nameThe string **SHALL NOT** contain name parts (CONF:81-9372).
:
1198-9946warningClinicalDocument.informant:informant1.assignedEntity.idIf assignedEntity/id is a provider then this id, **SHOULD** include zero or one [0..1] id where id/@root ="2.16.840.1.113883.4.6" National Provider Identifier (CONF:1198-9946).
:
81-7296errorClinicalDocument.informant:informant1.assignedEntity.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-9371errorClinicalDocument.informant:informant1.assignedEntity.assignedPerson.nameThe content of name **SHALL** be either a conformant Patient Name (PTN.US.FIELDED), or a string (CONF:81-9371).
:
81-9372errorClinicalDocument.informant:informant1.assignedEntity.assignedPerson.nameThe string **SHALL NOT** contain name parts (CONF:81-9372).
:
81-7296errorClinicalDocument.custodian.assignedCustodian.representedCustodianOrganization.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-9371errorClinicalDocument.informationRecipient.intendedRecipient.informationRecipient.nameThe content of name **SHALL** be either a conformant Patient Name (PTN.US.FIELDED), or a string (CONF:81-9371).
:
81-9372errorClinicalDocument.informationRecipient.intendedRecipient.informationRecipient.nameThe string **SHALL NOT** contain name parts (CONF:81-9372).
:
81-10127errorClinicalDocument.legalAuthenticator.time**SHALL** be precise to the day (CONF:81-10127).
:
81-10128warningClinicalDocument.legalAuthenticator.time**SHOULD** be precise to the minute (CONF:81-10128).
:
81-10129warningClinicalDocument.legalAuthenticator.time**MAY** be precise to the second (CONF:81-10129).
:
81-10130warningClinicalDocument.legalAuthenticator.timeIf more precise than day, **SHOULD** include time-zone offset (CONF:81-10130).
:
81-7296errorClinicalDocument.legalAuthenticator.assignedEntity.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-9371errorClinicalDocument.legalAuthenticator.assignedEntity.assignedPerson.nameThe content of name **SHALL** be either a conformant Patient Name (PTN.US.FIELDED), or a string (CONF:81-9371).
:
81-9372errorClinicalDocument.legalAuthenticator.assignedEntity.assignedPerson.nameThe string **SHALL NOT** contain name parts (CONF:81-9372).
:
81-10127errorClinicalDocument.authenticator:authenticator1.time**SHALL** be precise to the day (CONF:81-10127).
:
81-10128warningClinicalDocument.authenticator:authenticator1.time**SHOULD** be precise to the minute (CONF:81-10128).
:
81-10129warningClinicalDocument.authenticator:authenticator1.time**MAY** be precise to the second (CONF:81-10129).
:
81-10130warningClinicalDocument.authenticator:authenticator1.timeIf more precise than day, **SHOULD** include time-zone offset (CONF:81-10130).
:
81-7296errorClinicalDocument.authenticator:authenticator1.assignedEntity.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-9371errorClinicalDocument.authenticator:authenticator1.assignedEntity.assignedPerson.nameThe content of name **SHALL** be either a conformant Patient Name (PTN.US.FIELDED), or a string (CONF:81-9371).
:
81-9372errorClinicalDocument.authenticator:authenticator1.assignedEntity.assignedPerson.nameThe string **SHALL NOT** contain name parts (CONF:81-9372).
:
1198-10006errorClinicalDocument.participant:participant1**SHALL** contain associatedEntity/associatedPerson *AND/OR* associatedEntity/scopingOrganization (CONF:1198-10006).
:
1198-10007warningClinicalDocument.participant:participant1When participant/@typeCode is *IND*, associatedEntity/@classCode **SHOULD** be selected from ValueSet 2.16.840.1.113883.11.20.9.33 INDRoleclassCodes *STATIC 2011-09-30* (CONF:1198-10007).
: