Consolidated CDA Release 2.2
2.2 - CI Build

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: Transfer Summary

Defining URL:http://hl7.org/fhir/cda/ccda/StructureDefinition/2.16.840.1.113883.10.20.22.1.13
Version:2.2
Name:TransferSummary
Title:Transfer Summary
Status:Active as of 11/24/21, 5:43 PM
Definition:

This document describes constraints on the Clinical Document Architecture (CDA) header and body elements for a Transfer Summary. The Transfer Summary standardizes critical information for exchange of information between providers of care when a patient moves between health care settings. Standardization of information used in this form will promote interoperability; create information suitable for reuse in quality measurement, public health, research, and for reimbursement.

Publisher:Health Level Seven
Source Resource:XML / JSON / Turtle

The official URL for this profile is:

http://hl7.org/fhir/cda/ccda/StructureDefinition/2.16.840.1.113883.10.20.22.1.13

Formal Views of Profile Content

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

This structure is derived from USRealmHeader

Summary

Mandatory: 24 elements (35 nested mandatory elements)

Structures

This structure refers to these other structures:

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.participant is sliced based on the value of value:typeCode
  • The element ClinicalDocument.documentationOf.serviceEvent.performer is sliced based on the value of value:typeCode
  • The element ClinicalDocument.component.structuredBody.component is sliced based on the value of value:section.code

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:primary I1..1II1198-32946: 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-32946).
..... root 1..1stringRequired Pattern: 2.16.840.1.113883.10.20.22.1.13
..... extension 1..1stringRequired Pattern: 2015-08-01
... code 1..1CEThe Transfer Summary recommends use of the document type code 18761-7 "Provider Unspecified Transfer Summary", with further specification provided by author or performer, setting, or specialty. When pre-coordinated codes are used, any coded values describing the author or performer of the service act or the practice setting must be consistent with the LOINC document type. For example, an Obstetrics and Gynecology Transfer Summary note would not be authored by a Pediatric Cardiologist. Pre-coordinated codes are those that indicate the specialty or service provided in the LOINC Long Common Name (Print Name in the TransferDocumentType valueSet table). When using a generic type of code such as 18761-7 (Provider - Unspecified Transfer Summary), the types of services involved in the care are handled in documentationOf/serviceEvent with the use of serviceEvent/code (e.g., use a SNOMED CT procedure code such as 69031006 (Excision of breast tissue) while performers/providers involved in the care can be identified using the functionCode (bound to Healthcare Provider Taxonomy role codes).
Binding: http://hl7.org/fhir/ccda/ValueSet/2.16.840.1.113883.1.11.20.2.4 (required)
... title 1..1EDThe title can either be a locally defined name or the displayName corresponding to clinicalDocument/code
.... participant:participant1 0..*Participant1
..... typeCode 1..1codeRequired Pattern: IND
..... associatedEntity 1..1AssociatedEntity
...... classCode 1..1codeBinding: INDRoleclassCodes (required)
...... associatedPerson 1..1Person
....... name 1..*EN
.... participant:participant2 0..*Participant1The participant element identifies supporting entities, including parents, relatives, caregivers, insurance policyholders, guarantors, and others 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..1codeRequired Pattern: CALLBCK
..... associatedEntity 1..1AssociatedEntity
...... classCode 1..1codeRequired Pattern: ASSIGNED
...... id 1..*II
...... addr 0..*AD
...... telecom 1..*TEL
...... associatedPerson 1..1Person
....... name 1..*EN
...... scopingOrganization 0..1Organization
... documentationOf 1..1DocumentationOf
.... serviceEvent 1..1ServiceEventThe serviceEvent in a Transfer Note contains the representation of providers who are wholly or partially responsible for the safety and well-being of a subject of care.
..... classCode 1..1codeRequired Pattern: PCPR
..... code 0..1CEUse serviceEvent/code when using a generic document type code such as 18761-7 (Provider-Unspecified Transfer Summary) to represent the service.
..... Slices for 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.
Slice: Unordered, Open by value:typeCode
...... performer:performer1 1..*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.
....... typeCode 1..1codeRequired Pattern: PRF
....... functionCode 0..1CEUse performer/functionCode when using a generic document type code such as 18761-7 (Provider-Unspecified Transfer Summary) to represent the provider.
Binding: Healthcare Provider Taxonomy (preferred)
... component 1..1Component2
.... structuredBody I1..1StructuredBody1198-31582: This structuredBody **SHALL** contain an Assessment and Plan Section (V2) (2.16.840.1.113883.10.20.22.2.9:2014-06-09), or an Assessment Section (2.16.840.1.113883.10.20.22.2.8) and a Plan of Treatment Section (V2) (2.16.840.1.113883.10.20.22.2.10:2014-06-09) (CONF:1198-31582).
1198-31583: This structuredBody **SHALL NOT** contain an Assessment and Plan Section (V2) (2.16.840.1.113883.10.20.22.2.9:2014-06-09) when either an Assessment Section (2.16.840.1.113883.10.20.22.2.8) or a Plan of Treatment Section (V2) (2.16.840.1.113883.10.20.22.2.10:2014-06-09) is present (CONF:1198-31583).
..... Slices for component 0..1ElementSlice: Unordered, Open by value:section.code
...... component:advanceDirectives 0..1Element
....... section 1..1AdvanceDirectivesSectionentriesrequired
...... component:allergiesAndIntolerances 1..1Element
....... section 1..1AllergiesAndIntolerancesSectionEntriesRequired
...... component:physicalExam 0..1Element
....... section 1..1PhysicalExamSection
...... component:encounters 0..1Element
....... section 1..1EncountersSectionentriesrequired
...... component:familyHistory 0..1Element
....... section 1..1FamilyHistorySection
...... component:functionalStatus 0..1Element
....... section 1..1FunctionalStatusSection
...... component:dischargeDiagnosis 0..1Element
....... section 1..1DischargeDiagnosisSection
...... component:immunizations 0..1Element
....... section 1..1ImmunizationsSectionEntriesOptional
...... component:medicalEquip 0..1Element
....... section 1..1MedicalEquipmentSection
...... component:medications 1..1Element
....... section 1..1MedicationsSectionEntriesRequired
...... component:payers 0..1Element
....... section 1..1PayersSection
...... component:planOfTreatment 0..1Element
....... section 1..1PlanofTreatmentSection
...... component:problem 1..1Element
....... section 1..1ProblemSectionEntriesRequired
...... component:procedures 0..1Element
....... section 1..1ProceduresSectionentriesrequired
...... component:results 1..1Element
....... section 1..1ResultsSectionEntriesRequired
...... component:socialHistory 0..1Element
....... section 1..1SocialHistorySection
...... component:vitalSigns 1..1Element
....... section 1..1VitalSignsSectionEntriesRequired
...... component:mentalStatus 0..1Element
....... section 1..1MentalStatusSection
...... component:generalStatus 0..1Element
....... section 1..1GeneralStatusSection
...... component:reviewOfSystems 0..1Element
....... section 1..1ReviewofSystemsSection
...... component:nutrition 0..1Element
....... section 1..1NutritionSection
...... component:reasonForReferral 1..1Element
....... section 1..1ReasonforReferralSection
...... component:pastMedicalHistory 0..1Element
....... section 1..1PastMedicalHistory
...... component:historyOfPresentIllness 0..1Element
....... section 1..1HistoryofPresentIllnessSection
...... component:assessmentAndPlan 0..1Element
....... section 1..1AssessmentandPlanSection
...... component:assessment 0..1Element
....... section 1..1AssessmentSection
...... component:admissionMedications 0..1Element
....... section 1..1AdmissionMedicationsSectionentriesoptional
...... component:admissionDiagnosis 0..1Element
....... section 1..1AdmissionDiagnosisSection
...... component:courseOfCare 0..1Element
....... section 1..1CourseofCareSection

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 I1..1II1198-32946: 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-32946).
..... nullFlavor 0..1codeBinding: NullFlavor (required)
..... assigningAuthorityName 0..1string
..... displayable 0..1boolean
..... root 1..1stringRequired Pattern: 2.16.840.1.113883.10.20.22.1.13
..... extension 1..1stringRequired Pattern: 2015-08-01
... id I1..1II1198-9991: This id **SHALL** be a globally unique identifier for the document (CONF:1198-9991).
... code I1..1CEThe Transfer Summary recommends use of the document type code 18761-7 "Provider Unspecified Transfer Summary", with further specification provided by author or performer, setting, or specialty. When pre-coordinated codes are used, any coded values describing the author or performer of the service act or the practice setting must be consistent with the LOINC document type. For example, an Obstetrics and Gynecology Transfer Summary note would not be authored by a Pediatric Cardiologist. Pre-coordinated codes are those that indicate the specialty or service provided in the LOINC Long Common Name (Print Name in the TransferDocumentType valueSet table). When using a generic type of code such as 18761-7 (Provider - Unspecified Transfer Summary), the types of services involved in the care are handled in documentationOf/serviceEvent with the use of serviceEvent/code (e.g., use a SNOMED CT procedure code such as 69031006 (Excision of breast tissue) while performers/providers involved in the care can be identified using the functionCode (bound to Healthcare Provider Taxonomy role codes).
Binding: http://hl7.org/fhir/ccda/ValueSet/2.16.840.1.113883.1.11.20.2.4 (required)
... 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..1II1198-6380: If setId is present versionNumber **SHALL** be present (CONF:1198-6380).
... versionNumber I0..1INT1198-6387: If versionNumber is present setId **SHALL** be present (CONF:1198-6387).
... copyTime 0..1TS
... recordTarget 1..*RecordTargetThe recordTarget records the administrative and demographic data of the patient whose health information is described by the clinical document; each recordTarget must contain at least one patientRole element
.... 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..1TS1198-5299: **SHALL** be precise to year (CONF:1198-5299).
1198-5300: **SHOULD** be precise to day (CONF:1198-5300).
1198-32418: **MAY** be precise to the minute (CONF:1198-32418). For cases where information about newborn's time of birth needs to be captured.
...... 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..1AD1198-5402: If 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-5403: If 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).
......... 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..1BL
..... providerOrganization 0..1Organization
...... 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.
.... 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..1AssignedAuthor1198-16790: There **SHALL** be exactly one assignedAuthor/assignedPerson or exactly one assignedAuthor/assignedAuthoringDevice (CONF:1198-16790).
..... classCode 1..1codeBinding: RoleClassAssignedEntity (required)
Fixed Value: ASSIGNED
..... templateId 0..*II
..... Slices for id I1..*IISlice: Unordered, Open by value:root
1198-5449: If this assignedAuthor is not an assignedPerson, this assignedAuthor SHALL contain at least one [1..*] id (CONF:1198-5449).
...... 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..1CEOnly if this assignedAuthor is an assignedPerson should the assignedAuthor contain a code.
Binding: v3 Code System RoleCode (extensible)
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... code 1..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 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, into the clinical document. To clarify, an author provides the content found within the header or body of a document, subject to their own interpretation; a dataEnterer adds an author's information to the electronic system.
.... 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: Healthcare Provider Taxonomy (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 an information source (who is not a provider) for any content within the clinical document. This informant would be used when the source of information has a personal relationship with the patient or is the patient.
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..*II1198-9946: If 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).
...... 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 0..1RelatedEntity
.... 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 that is in charge of maintaining and is entrusted with the care of the document. There is only one custodian per CDA document. Allowing that a CDA document may not represent the original form of the authenticated document, 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.
.... 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..1CustodianOrganization
...... 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..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 was created. In cases where the intended recipient of the document is the patient's health chart, set the receivedOrganization to 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..*II
..... 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..1LegalAuthenticatorThe legalAuthenticator identifies the single person legally responsible for the document and must be present if the document has been legally authenticated. A clinical 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. Based on local practice, clinical documents may be released before legal authentication. All clinical documents have the potential for legal authentication, given the appropriate credentials. Local policies MAY choose to delegate the function of legal authentication to a device or system that generates the clinical document. In these cases, the legal authenticator is a 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..*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: Healthcare Provider Taxonomy (preferred)
..... addr I1..*USRealmAddressADUSFIELDED
..... telecom 1..*TEL
...... nullFlavor 0..1codeBinding: NullFlavor (required)
...... value 0..1uri
...... useablePeriod 0..*
....... useablePeriodIVL_TS
....... useablePeriod