Consolidated CDA Release 2.1 StructureDefinition Publication
2.1 - CI Build United States of America flag

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

Logical Model: US Realm Header for Patient Generated Document

Official URL: http://hl7.org/cda/us/ccda/StructureDefinition/USRealmHeaderforPatientGeneratedDocument Version: 2.1
Active as of 2023-09-29 Computable Name: USRealmHeaderforPatientGeneratedDocument
Other Identifiers: id: 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. It includes additional conformances which further constrain the US Realm Header. 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 Logical Model 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

NameFlagsCard.TypeDescription & Constraintsdoco
.. ClinicalDocument 1..1USRealmHeaderXML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @classCode, @moodCode, realmCode, typeId, templateId, id, code, title, effectiveTime, confidentialityCode, languageCode, setId, versionNumber, copyTime, recordTarget, author, dataEnterer, informant, custodian, informationRecipient, legalAuthenticator, authenticator, participant, inFulfillmentOf, documentationOf, relatedDocument, authorization, componentOf, component, realmCode, typeId, templateId, templateId, id, code, title, effectiveTime, confidentialityCode, languageCode, setId, versionNumber, recordTarget, author, dataEnterer, informant, informant, informant, custodian, informationRecipient, legalAuthenticator, authenticator, authenticator, participant, inFulfillmentOf, documentationOf, authorization, componentOf
Base for all types and resources
... templateId 2..*II
... templateId:secondary 1..1II
.... root 1..1oid, uuid, ruidRequired Pattern: 2.16.840.1.113883.10.20.29.1
.... extension 1..1stRequired 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..1CE
...... 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
.... 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..1csBinding: Personal And Legal Relationship Role Type (preferred)
... 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.
.... assignedEntity 1..1AssignedEntity
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
... 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.
... informant:informant1 0..*Informantinformant
.... relatedEntity 1..1RelatedEntity
..... code 0..1CE
...... code 0..1csBinding: 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..1oid, uuid, ruidFor 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..1csBinding: Personal And Legal Relationship Role Type (preferred)
... authenticator 0..*Authenticator
.... 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..1csUnless 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..1AssociatedEntity
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
... inFulfillmentOf 0..*InFulfillmentOf
.... 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..1ServiceEvent
..... 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..*Performer1
...... 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

Terminology Bindings (Differential)

PathConformanceValueSet
ClinicalDocument.author.assignedAuthor.code.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.dataEnterer.assignedEntity.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.informant:informant1.relatedEntity.code.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.legalAuthenticator.assignedEntity.code.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.authenticator.assignedEntity.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.participant.associatedEntity.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.documentationOf.serviceEvent.performer.assignedEntity.codepreferredPersonal And Legal Relationship Role Type
NameFlagsCard.TypeDescription & Constraintsdoco
.. ClinicalDocument 1..1USRealmHeaderXML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @classCode, @moodCode, realmCode, typeId, templateId, id, code, title, effectiveTime, confidentialityCode, languageCode, setId, versionNumber, copyTime, recordTarget, author, dataEnterer, informant, custodian, informationRecipient, legalAuthenticator, authenticator, participant, inFulfillmentOf, documentationOf, relatedDocument, authorization, componentOf, component, realmCode, typeId, templateId, templateId, id, code, title, effectiveTime, confidentialityCode, languageCode, setId, versionNumber, recordTarget, author, dataEnterer, informant, informant, informant, custodian, informationRecipient, legalAuthenticator, authenticator, authenticator, participant, inFulfillmentOf, documentationOf, authorization, componentOf
Base for all types and resources
... realmCode 1..1CS
.... @code 1..1csRequired Pattern: US
... typeId 1..1II
.... @root 1..1stFixed Value: 2.16.840.1.113883.1.3
.... @extension 1..1stExtension
Fixed Value: POCD_HD000040
... Slices for templateId 2..*IISlice: Unordered, Open by value:root, value:extension
.... templateId:us-realm 1..1IItemplateId
..... @root 1..1oid, uuid, ruidRequired Pattern: 2.16.840.1.113883.10.20.22.1.1
..... @extension 1..1stRequired Pattern: 2023-05-01
.... templateId:secondary 1..1II
..... @root 1..1oid, uuid, ruidRequired Pattern: 2.16.840.1.113883.10.20.29.1
..... @extension 1..1stRequired Pattern: 2015-08-01
... code C1..1CEBinding: FHIRDocumentTypeCodes (extensible)
... title 1..1STThe title can either be a locally defined name or the displayName corresponding to clinicalDocument/code
... effectiveTime C1..1USRealmDateandTimeDTMUSFIELDEDBase for all types and resources
... confidentialityCode 1..1CEBinding: HL7 BasicConfidentialityKind (preferred)
... languageCode 1..1CSBinding: VSAC 2.16.840.1.113883.1.11.11526 (required)
... 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
..... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
..... telecom 1..*TEL
...... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
..... patient 1..1Patient
...... name C1..*USRealmPatientNamePTNUSFIELDEDBase for all types and resources
...... administrativeGenderCode 1..1CEBinding: Administrative Gender (HL7 V3) (required)
...... birthTime C1..1TS
...... raceCode 1..1CEBinding: Race Category Excluding Nulls (required)
...... ethnicGroupCode 1..1CEBinding: Ethnicity (required)
...... guardian 0..*Guardian
....... id 0..*II
....... code 0..1CEBinding: Personal And Legal Relationship Role Type (required)
....... guardianPerson 1..1Person
........ name C1..*USRealmPersonNamePNUSFIELDEDBase for all types and resources
...... languageCommunication 0..*LanguageCommunication
....... languageCode 1..1CSBinding: VSAC 2.16.840.1.113883.1.11.11526 (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
...... id 1..*II
...... name 1..*ON
...... telecom 1..*TEL
....... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
...... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
... 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.
.... time C1..1USRealmDateandTimeDTMUSFIELDEDBase for all types and resources
.... assignedAuthor C1..1AssignedAuthor
..... Slices for id 1..*IISlice: Unordered, Open by value:root
...... id:id1 0..1IIid
....... @root 1..1oid, uuid, ruidRequired Pattern: 2.16.840.1.113883.4.6
..... 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)
...... @code 1..1csBinding: Personal And Legal Relationship Role Type (preferred)
..... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
..... telecom 1..*TEL
...... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
... 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.
.... time 1..1TS
.... assignedEntity 1..1AssignedEntity
..... id 1..*II
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
..... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
..... telecom 1..*TEL
...... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
..... assignedPerson 1..1Person
...... name C1..*USRealmPersonNamePNUSFIELDEDBase for all types and resources
... 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..*Informantinformant
..... assignedEntity 1..1AssignedEntity
...... id C1..*II
...... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
...... assignedPerson 1..1Person
....... name C1..*USRealmPersonNamePNUSFIELDEDBase for all types and resources
..... relatedEntity 1..1RelatedEntity
...... @classCode 1..1csBinding: RoleClassMutualRelationship (required)
...... code 0..1CEBinding: PersonalRelationshipRoleType (extensible)
....... @code 0..1csBinding: Personal And Legal Relationship Role Type (preferred)
.... informant:informant2 0..*Informantinformant
..... 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.
.... 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.
...... name 1..1ON
...... telecom 1..1TEL
....... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
...... addr C1..1USRealmAddressADUSFIELDEDBase for all types and resources
... 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
..... @classCode 1..1cs
..... id 0..*IIThe combined @root and @extension attributes to record the information recipient's identity in a secure, trusted, and unique way.
...... @root 0..1oid, uuid, ruidFor 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.
.... time C1..1USRealmDateandTimeDTMUSFIELDEDBase for all types and resources
.... signatureCode 1..1CS
..... @code 1..1csRequired Pattern: S
.... 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..1CEBinding: Healthcare Provider Taxonomy (preferred)
...... @code 0..1csBinding: Personal And Legal Relationship Role Type (preferred)
..... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
..... telecom 1..*TEL
...... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
..... assignedPerson 1..1Person
...... name C1..*USRealmPersonNamePNUSFIELDEDBase for all types and resources
... Slices for authenticator 0..*AuthenticatorSlice: Unordered, Open by value:ClinicalDocument.signatureCode, value:ClinicalDocument.assignedEntity, value:ClinicalDocument.time
.... authenticator:All Slices Content/Rules for all slices
..... time 1..1TS
..... signatureCode 1..1CS
..... 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)
.... authenticator:authenticator1 0..*Authenticatorauthenticator
..... time C1..1USRealmDateandTimeDTMUSFIELDEDBase for all types and resources
..... signatureCode 1..1CS
...... @code 1..1csRequired Pattern: S
..... assignedEntity 1..1AssignedEntity
...... id 1..*II
...... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
...... telecom 1..*TEL
....... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
...... assignedPerson 1..1Person
....... name C1..*USRealmPersonNamePNUSFIELDEDBase for all types and resources
... participant C0..*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..1csUnless 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
Binding: ParticipationType (required)
.... associatedEntity 1..1AssociatedEntity
..... @classCode 1..1csBinding: RoleClassAssociative (required)
..... code 0..1CEBinding: Personal And Legal Relationship Role Type (preferred)
... inFulfillmentOf 0..*InFulfillmentOf
.... order 1..1Order
..... @classCode 1..1csBinding: ActClass (required)
..... 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..1ServiceEvent
..... @classCode 1..1csBinding: ActClass (required)
..... 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
...... low 1..1IVXB_TS
..... performer 0..*Performer1
...... @typeCode 1..1csBinding: x_ServiceEventPerformer (required)
...... 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)
... component 1..1Component

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
ClinicalDocument.codeextensibleFHIRDocumentTypeCodes
ClinicalDocument.confidentialityCodepreferredHL7 BasicConfidentialityKind
ClinicalDocument.languageCoderequiredhttp://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.1.11.11526
ClinicalDocument.recordTarget.patientRole.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.recordTarget.patientRole.patient.administrativeGenderCoderequiredAdministrative Gender (HL7 V3)
ClinicalDocument.recordTarget.patientRole.patient.raceCoderequiredRace Category Excluding Nulls
ClinicalDocument.recordTarget.patientRole.patient.ethnicGroupCoderequiredEthnicity
ClinicalDocument.recordTarget.patientRole.patient.guardian.coderequiredPersonal And Legal Relationship Role Type
ClinicalDocument.recordTarget.patientRole.patient.languageCommunication.languageCoderequiredhttp://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.1.11.11526
ClinicalDocument.recordTarget.patientRole.providerOrganization.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.author.assignedAuthor.codeextensibleRoleCode
ClinicalDocument.author.assignedAuthor.code.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.author.assignedAuthor.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.dataEnterer.assignedEntity.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.dataEnterer.assignedEntity.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.informant:informant1.relatedEntity.classCoderequiredRoleClassMutualRelationship
ClinicalDocument.informant:informant1.relatedEntity.codeextensiblePersonalRelationshipRoleType
ClinicalDocument.informant:informant1.relatedEntity.code.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.custodian.assignedCustodian.representedCustodianOrganization.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.legalAuthenticator.assignedEntity.codepreferredHealthcare Provider Taxonomy (a valid code from http://nucc.org/provider-taxonomy)
ClinicalDocument.legalAuthenticator.assignedEntity.code.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.legalAuthenticator.assignedEntity.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.authenticator.assignedEntity.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.authenticator:authenticator1.assignedEntity.telecom.userequiredTelecom Use (US Realm Header)
ClinicalDocument.participant.typeCoderequiredParticipationType
ClinicalDocument.participant.associatedEntity.classCoderequiredRoleClassAssociative
ClinicalDocument.participant.associatedEntity.codepreferredPersonal And Legal Relationship Role Type
ClinicalDocument.inFulfillmentOf.order.classCoderequiredActClass
ClinicalDocument.documentationOf.serviceEvent.classCoderequiredActClass
ClinicalDocument.documentationOf.serviceEvent.performer.typeCoderequiredx_ServiceEventPerformer
ClinicalDocument.documentationOf.serviceEvent.performer.assignedEntity.codepreferredPersonal And Legal Relationship Role Type

Constraints

IdGradePath(s)DetailsRequirements
4537-5299errorClinicalDocument.recordTarget.patientRole.patient.birthTime**SHALL** be precise to year (CONF:4537-5299).
:
4537-5300warningClinicalDocument.recordTarget.patientRole.patient.birthTime**SHOULD** be precise to day (CONF:4537-5300).
:
4537-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:4537-9946).
:
4537-9991warningClinicalDocument.idThis id **SHALL** be a globally unique identifier for the document (CONF:4537-9991).
:
4537-9992errorClinicalDocument.codeThis code **SHALL** specify the particular kind of document (e.g., History and Physical, Discharge Summary, Progress Note) (CONF:4537-9992).
:
4537-10006errorClinicalDocument.participant**SHALL** contain associatedEntity/associatedPerson *AND/OR* associatedEntity/scopingOrganization (CONF:4537-10006).
:
4537-10007warningClinicalDocument.participantWhen participant/@typeCode is *IND*, associatedEntity/@classCode **SHOULD** be selected from ValueSet 2.16.840.1.113883.11.20.9.33 INDRoleclassCodes *DYNAMIC* (CONF:4537-10007).
:
4537-16790errorClinicalDocument.author.assignedAuthorThere **SHALL** be exactly one assignedAuthor/assignedPerson or exactly one assignedAuthor/assignedAuthoringDevice (CONF:4537-16790).
:
4537-32418warningClinicalDocument.recordTarget.patientRole.patient.birthTime**MAY** be precise to the minute (CONF:4537-32418).
:
4537-32948errorClinicalDocument.codeThis code **SHALL** be drawn from the LOINC document type ontology (LOINC codes where SCALE = DOC) (CONF:4537-32948).
:
81-7278errorClinicalDocument.recordTarget.patientRole.patient.name**SHALL NOT** have mixed content except for white space (CONF:81-7278).
:
81-7296errorClinicalDocument.recordTarget.patientRole.addr, ClinicalDocument.recordTarget.patientRole.providerOrganization.addr, ClinicalDocument.author.assignedAuthor.addr, ClinicalDocument.dataEnterer.assignedEntity.addr, ClinicalDocument.informant:informant1.assignedEntity.addr, ClinicalDocument.custodian.assignedCustodian.representedCustodianOrganization.addr, ClinicalDocument.legalAuthenticator.assignedEntity.addr, ClinicalDocument.authenticator:authenticator1.assignedEntity.addr**SHALL NOT** have mixed content except for white space (CONF:81-7296).
:
81-9371errorClinicalDocument.recordTarget.patientRole.patient.guardian.guardianPerson.name, ClinicalDocument.dataEnterer.assignedEntity.assignedPerson.name, ClinicalDocument.informant:informant1.assignedEntity.assignedPerson.name, ClinicalDocument.legalAuthenticator.assignedEntity.assignedPerson.name, ClinicalDocument.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.recordTarget.patientRole.patient.guardian.guardianPerson.name, ClinicalDocument.dataEnterer.assignedEntity.assignedPerson.name, ClinicalDocument.informant:informant1.assignedEntity.assignedPerson.name, ClinicalDocument.legalAuthenticator.assignedEntity.assignedPerson.name, ClinicalDocument.authenticator:authenticator1.assignedEntity.assignedPerson.nameThe string **SHALL NOT** contain name parts (CONF:81-9372).
:
81-10127errorClinicalDocument.effectiveTime, ClinicalDocument.author.time, ClinicalDocument.legalAuthenticator.time, ClinicalDocument.authenticator:authenticator1.time**SHALL** be precise to the day (CONF:81-10127).
:
81-10128warningClinicalDocument.effectiveTime, ClinicalDocument.author.time, ClinicalDocument.legalAuthenticator.time, ClinicalDocument.authenticator:authenticator1.time**SHOULD** be precise to the minute (CONF:81-10128).
:
81-10129warningClinicalDocument.effectiveTime, ClinicalDocument.author.time, ClinicalDocument.legalAuthenticator.time, ClinicalDocument.authenticator:authenticator1.time**MAY** be precise to the second (CONF:81-10129).
:
81-10130warningClinicalDocument.effectiveTime, ClinicalDocument.author.time, ClinicalDocument.legalAuthenticator.time, ClinicalDocument.authenticator:authenticator1.timeIf more precise than day, **SHOULD** include time-zone offset (CONF:81-10130).
:
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
pn-no-lserrorClinicalDocument.recordTarget.patientRole.patient.name, ClinicalDocument.recordTarget.patientRole.patient.guardian.guardianPerson.name, ClinicalDocument.dataEnterer.assignedEntity.assignedPerson.name, ClinicalDocument.informant:informant1.assignedEntity.assignedPerson.name, ClinicalDocument.legalAuthenticator.assignedEntity.assignedPerson.name, ClinicalDocument.authenticator:authenticator1.assignedEntity.assignedPerson.nameNo PN name part may have a qualifier of LS.
: (delimiter | family | given | prefix | suffix).where(qualifier = 'LS').empty()
NameFlagsCard.TypeDescription & Constraintsdoco
.. ClinicalDocument 1..1USRealmHeaderXML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @classCode, @moodCode, realmCode, typeId, templateId, id, code, title, effectiveTime, confidentialityCode, languageCode, setId, versionNumber, copyTime, recordTarget, author, dataEnterer, informant, custodian, informationRecipient, legalAuthenticator, authenticator, participant, inFulfillmentOf, documentationOf, relatedDocument, authorization, componentOf, component, realmCode, typeId, templateId, templateId, id, code, title, effectiveTime, confidentialityCode, languageCode, setId, versionNumber, recordTarget, author, dataEnterer, informant, informant, informant, custodian, informationRecipient, legalAuthenticator, authenticator, authenticator, participant, inFulfillmentOf, documentationOf, authorization, componentOf
Base for all types and resources
... @classCode 0..1csBinding: ActClass (extensible)
Fixed Value: DOCCLIN
... @moodCode 0..1csBinding: ActMood (required)
Fixed Value: EVN
... realmCode 1..1CS
.... @nullFlavor 0..1csBinding: NullFlavor (required)
.... @code 1..1csRequired Pattern: US
.... @sdtcValueSet 0..1oidXML Namespace: urn:hl7-org:sdtc
XML: valueSet (urn:hl7-org:sdtc)
.... @sdtcValueSetVersion 0..1stXML Namespace: urn:hl7-org:sdtc
XML: valueSetVersion (urn:hl7-org:sdtc)
... typeId 1..1II
.... @root 1..1stFixed Value: 2.16.840.1.113883.1.3
.... @extension 1..1stExtension
Fixed Value: POCD_HD000040
... Slices for templateId 2..*IISlice: Unordered, Open by value:root, value:extension
.... templateId:us-realm 1..1IItemplateId
..... @nullFlavor 0..1csBinding: NullFlavor (required)
..... @assigningAuthorityName 0..1st
..... @displayable 0..1bl
..... @root 1..1oid, uuid, ruidRequired Pattern: 2.16.840.1.113883.10.20.22.1.1
..... @extension 1..1stRequired Pattern: 2023-05-01
.... templateId:secondary 1..1II
..... @nullFlavor 0..1csBinding: NullFlavor (required)
..... @assigningAuthorityName 0..1st
..... @displayable 0..1bl
..... @root 1..1oid, uuid, ruidRequired Pattern: 2.16.840.1.113883.10.20.29.1
..... @extension 1..1stRequired Pattern: 2015-08-01
... id C1..1II
... code C1..1CEBinding: FHIRDocumentTypeCodes (extensible)
... title 1..1STThe title can either be a locally defined name or the displayName corresponding to clinicalDocument/code
... effectiveTime C1..1USRealmDateandTimeDTMUSFIELDEDBase for all types and resources
... confidentialityCode 1..1CEBinding: HL7 BasicConfidentialityKind (preferred)
... languageCode 1..1CSBinding: VSAC 2.16.840.1.113883.1.11.11526 (required)
... setId C0..1II
... versionNumber C0..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..1csBinding: NullFlavor (required)
.... @typeCode 0..1csBinding: ParticipationType (required)
Fixed Value: RCT
.... @contextControlCode 0..1csBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... patientRole 1..1PatientRole
..... @classCode 0..1csBinding: RoleClassRelationshipFormal (required)
Fixed Value: PAT
..... templateId 0..*II
..... id 1..*II
..... sdtcIdentifiedBy 0..*IdentifiedByXML Namespace: urn:hl7-org:sdtc
XML: identifiedBy (urn:hl7-org:sdtc)
..... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
..... telecom 1..*TEL
...... @nullFlavor 0..1csBinding: NullFlavor (required)
...... @value 0..1url
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
..... patient 1..1Patient
...... @classCode 0..1csBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... @determinerCode 0..1csBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... id 0..1II
...... name C1..*USRealmPatientNamePTNUSFIELDEDBase for all types and resources
...... sdtcDesc 0..1EDXML Namespace: urn:hl7-org:sdtc
XML: desc (urn:hl7-org:sdtc)
...... administrativeGenderCode 1..1CEBinding: Administrative Gender (HL7 V3) (required)
...... birthTime C1..1TS
...... sdtcDeceasedInd C0..1BLXML Namespace: urn:hl7-org:sdtc
sdtc:deceasedInd
XML: deceasedInd (urn:hl7-org:sdtc)
...... sdtcDeceasedTime 0..1TSXML Namespace: urn:hl7-org:sdtc
sdtc:deceasedTime
XML: deceasedTime (urn:hl7-org:sdtc)
....... @nullFlavor 0..1csBinding: NullFlavor (required)
....... @value C0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
...... sdtcMultipleBirthInd 0..1BLXML Namespace: urn:hl7-org:sdtc
XML: multipleBirthInd (urn:hl7-org:sdtc)
...... sdtcMultipleBirthOrderNumber 0..1INT_POSXML Namespace: urn:hl7-org:sdtc
XML: 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 C0..*CEXML Namespace: urn:hl7-org:sdtc
The sdtc:raceCode is only used to record additional values when the patient has indicated multiple races or additional race detail beyond the five categories required for Meaningful Use Stage 2. The prefix sdtc: SHALL be bound to the namespace “urn:hl7-org:sdtc”. The use of the namespace provides a necessary extension to CDA R2 for the use of the additional raceCode elements.
XML: raceCode (urn:hl7-org:sdtc)
Binding: Race Value Set (required)
...... ethnicGroupCode 1..1CEBinding: Ethnicity (required)
...... sdtcEthnicGroupCode 0..*CEXML Namespace: urn:hl7-org:sdtc
ethnicGroupCode
XML: ethnicGroupCode (urn:hl7-org:sdtc)
Binding: Detailed Ethnicity (required)
...... guardian 0..*Guardian
....... @classCode 0..1csBinding: RoleClassAgent (required)
Fixed Value: GUARD
....... templateId 0..*II
....... id 0..*II
....... sdtcIdentifiedBy 0..*IdentifiedByXML Namespace: urn:hl7-org:sdtc
XML: identifiedBy (urn:hl7-org:sdtc)
....... code 0..1CEBinding: Personal And Legal Relationship Role Type (required)
....... addr C0..*USRealmAddressADUSFIELDEDBase for all types and resources
....... telecom 0..*TEL
........ @nullFlavor 0..1csBinding: NullFlavor (required)
........ @value 0..1url
........ useablePeriod 0..*
......... useablePeriodIVL_TS
......... useablePeriodEIVL_TS
......... useablePeriodPIVL_TS
......... useablePeriodSXPR_TS
........ @use 0..1csBinding: Telecom Use (US Realm Header) (required)
....... guardianPerson 1..1Person
........ @classCode 0..1csBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
........ @determinerCode 0..1csBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
........ templateId 0..*II
........ name C1..*USRealmPersonNamePNUSFIELDEDBase for all types and resources
........ sdtcAsPatientRelationship 0..*CEXML Namespace: urn:hl7-org:sdtc
XML: asPatientRelationship (urn:hl7-org:sdtc)
....... guardianOrganization 0..1Organization
...... birthplace 0..1Birthplace
....... @classCode 0..1csBinding: RoleClassPassive (required)
Fixed Value: BIRTHPL
....... templateId 0..*II
....... place 1..1Place
........ @classCode 0..1csBinding: EntityClassPlace (required)
Fixed Value: PLC
........ @determinerCode 0..1csBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
........ templateId 0..*II
........ name 0..1EN
........ addr C1..1AD
......... nullFlavor C0..1csPrimitive Type code
Binding: NullFlavor (required)
......... @isNotOrdered 0..1bl
......... @use 0..*cs
......... delimiter 0..*ADXP
.......... @partType 0..1csFixed Value: DEL
......... country 0..1ADXP
.......... @partType 0..1csFixed Value: CNT
......... state 0..*ADXP
.......... @partType 0..1csFixed Value: STA
......... county 0..*ADXP
.......... @partType 0..1csFixed Value: CPA
......... city 0..*ADXP
.......... @partType 0..1csFixed Value: CTY
......... postalCode 0..*ADXP
.......... @partType 0..1csFixed Value: ZIP
......... streetAddressLine 0..*ADXP
.......... @partType 0..1csFixed Value: SAL
......... houseNumber 0..*ADXP
.......... @partType 0..1csFixed Value: BNR
......... houseNumberNumeric 0..*ADXP
.......... @partType 0..1csFixed Value: BNN
......... direction 0..*ADXP
.......... @partType 0..1csFixed Value: DIR
......... streetName 0..*ADXP
.......... @partType 0..1csFixed Value: STR
......... streetNameBase 0..*ADXP
.......... @partType 0..1csFixed Value: STB
......... streetNameType 0..*ADXP
.......... @partType 0..1csFixed Value: STTYP
......... additionalLocator 0..*ADXP
.......... @partType 0..1csFixed Value: ADL
......... unitID 0..*ADXP
.......... @partType 0..1csFixed Value: UNID
......... unitType 0..*ADXP
.......... @partType 0..1csFixed Value: UNIT
......... careOf 0..*ADXP
.......... @partType 0..1csFixed Value: CAR
......... censusTract 0..*ADXP
.......... @partType 0..1csFixed Value: CEN
......... deliveryAddressLine 0..*ADXP
.......... @partType 0..1csFixed Value: DAL
......... deliveryInstallationType 0..*ADXP
.......... @partType 0..1csFixed Value: DINST
......... deliveryInstallationArea 0..*ADXP
.......... @partType 0..1csFixed Value: DINSTA
......... deliveryInstallationQualifier 0..*ADXP
.......... @partType 0..1csFixed Value: DINSTQ
......... deliveryMode 0..*ADXP
.......... @partType 0..1csFixed Value: DMOD
......... deliveryModeIdentifier 0..*ADXP
.......... @partType 0..1csFixed Value: DMODID
......... buildingNumberSuffix 0..*ADXP
.......... @partType 0..1csFixed Value: BNS
......... postBox 0..*ADXP
.......... @partType 0..1csFixed Value: POB
......... precinct 0..*ADXP
.......... @partType 0..1csFixed Value: PRE
......... other 0..1st
......... useablePeriod 0..*
.......... useablePeriodIVL_TS
.......... useablePeriodEIVL_TS
.......... useablePeriodPIVL_TS
.......... useablePeriodSXPR_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
...... @nullFlavor 0..1csBinding: NullFlavor (required)
...... @classCode 0..1csBinding: EntityClassOrganization (required)
Fixed Value: ORG
...... @determinerCode 0..1csBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... realmCode 0..*CS
...... typeId 0..1II
...... templateId 0..*II
...... id 1..*II
....... @nullFlavor 0..1csBinding: NullFlavor (required)
....... @assigningAuthorityName 0..1st
....... @displayable 0..1bl
....... @root 0..1oid, uuid, ruidRequired Pattern: 2.16.840.1.113883.4.6
....... @extension 0..1st
...... name 1..*ON
...... telecom 1..*TEL
....... @nullFlavor 0..1csBinding: NullFlavor (required)
....... @value 0..1url
....... useablePeriod 0..*
........ useablePeriodIVL_TS
........ useablePeriodEIVL_TS
........ useablePeriodPIVL_TS
........ useablePeriodSXPR_TS
....... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
...... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
...... 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..1csBinding: NullFlavor (required)
.... @typeCode 0..1csBinding: ParticipationType (required)
Fixed Value: AUT
.... @contextControlCode 0..1csBinding: ContextControl (required)
Fixed Value: OP
.... realmCode 0..*CS
.... typeId 0..1II
.... templateId 0..*II
.... functionCode 0..1CE
.... time C1..1USRealmDateandTimeDTMUSFIELDEDBase for all types and resources
.... assignedAuthor C1..1AssignedAuthor
..... @classCode 0..1csBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... Slices for id 1..*IISlice: Unordered, Open by value:root
...... id:id1 0..1IIid
....... @nullFlavor 0..1csBinding: NullFlavor (required)
Fixed Value: UNK
....... @assigningAuthorityName 0..1st
....... @displayable 0..1bl
....... @root 1..1oid, uuid, ruidRequired Pattern: 2.16.840.1.113883.4.6
....... @extension 0..1st
..... sdtcIdentifiedBy 0..*IdentifiedByXML Namespace: urn:hl7-org:sdtc
XML: 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..1csBinding: NullFlavor (required)
...... @code 1..1csBinding: Personal And Legal Relationship Role Type (preferred)
...... @codeSystem 0..1oid, uuid, ruid
...... @codeSystemName 0..1st
...... @codeSystemVersion 0..1st
...... @displayName 0..1st
...... @sdtcValueSet 0..1oidXML Namespace: urn:hl7-org:sdtc
XML: valueSet (urn:hl7-org:sdtc)
...... @sdtcValueSetVersion 0..1stXML Namespace: urn:hl7-org:sdtc
XML: valueSetVersion (urn:hl7-org:sdtc)
...... originalText 0..1ED
...... translation 0..*CD
..... addr C1..*USRealmAddressADUSFIELDEDBase for all types and resources
..... telecom 1..*TEL
...... @nullFlavor 0..1csBinding: NullFlavor (required)
...... @value 0..1url
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriodEIVL_TS
....... useablePeriodPIVL_TS
....... useablePeriodSXPR_TS
...... @use 0..1csBinding: Telecom Use (US Realm Header) (required)
..... assignedPerson 0..1Person
...... @classCode 0..1csBinding: EntityClassLivingSubject (required)
Fixed Value: PSN
...... @determinerCode 0..1csBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... name C1..*USRealmPersonNamePNUSFIELDEDBase for all types and resources
...... sdtcAsPatientRelationship 0..*CEXML Namespace: urn:hl7-org:sdtc
XML: asPatientRelationship (urn:hl7-org:sdtc)
..... assignedAuthoringDevice 0..1AuthoringDevice
...... @classCode 0..1csBinding: EntityClassDevice (required)
Fixed Value: DEV
...... @determinerCode 0..1csBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
...... templateId 0..*II
...... code 0..1CEBinding: EntityCode (extensible)
...... manufacturerModelName 1..1SCBinding: Manufacturer Model Name Example (example)
...... softwareName 1..1SCBinding: Software Name Example (example)
...... 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..1csBinding: NullFlavor (required)
.... @typeCode 0..1csBinding: ParticipationType (required)
Fixed Value: ENT
.... @contextControlCode 0..1csBinding: ContextControl (required)
Fixed Value: OP
.... realmCode