Generated Narrative: ConceptMap R2-DocumentReference-element-map-to-R5 Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/5.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DocumentReferenceversion: 5.0.0) Source Code Relationship Target Code Comment DocumentReference.meta (meta) is broader than DocumentReference.meta Element `DocumentReference.meta` is mapped to FHIR R5 element `DocumentReference.meta` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.meta` do not cover the following types: Meta. The mappings for `DocumentReference.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. DocumentReference.implicitRules (implicitRules) is equivalent to DocumentReference.implicitRules Element `DocumentReference.implicitRules` is mapped to FHIR R5 element `DocumentReference.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible. DocumentReference.language (language) is equivalent to DocumentReference.language Element `DocumentReference.language` is mapped to FHIR R5 element `DocumentReference.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). DocumentReference.text (text) is broader than DocumentReference.text Element `DocumentReference.text` is mapped to FHIR R5 element `DocumentReference.text` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.text` do not cover the following types: Narrative. The mappings for `DocumentReference.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. DocumentReference.contained (contained) is equivalent to DocumentReference.contained Element `DocumentReference.contained` is mapped to FHIR R5 element `DocumentReference.contained` as `SourceIsBroaderThanTarget`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. DocumentReference.masterIdentifier (masterIdentifier) is related to DocumentReference.identifier Element `DocumentReference.masterIdentifier` is mapped to FHIR R5 element `DocumentReference.identifier` as `RelatedTo`. The mappings for `DocumentReference.masterIdentifier` do not cover the following types: Identifier. The mappings for `DocumentReference.masterIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. CDA Document Id extension and root. DocumentReference.identifier (identifier) is broader than DocumentReference.identifier Element `DocumentReference.identifier` is mapped to FHIR R5 element `DocumentReference.identifier` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.identifier` do not cover the following types: Identifier. The mappings for `DocumentReference.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. DocumentReference.subject (subject) is broader than DocumentReference.subject Element `DocumentReference.subject` is mapped to FHIR R5 element `DocumentReference.subject` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DocumentReference.subject` with unmapped reference targets: Device, Group, Patient, Practitioner. DocumentReference.type (type) is equivalent to DocumentReference.type Element `DocumentReference.type` is mapped to FHIR R5 element `DocumentReference.type` as `Equivalent`. Key metadata element describing the document, used in searching/filtering. DocumentReference.class (class) is narrower than DocumentReference.category Element `DocumentReference.class` is mapped to FHIR R5 element `DocumentReference.category` as `SourceIsNarrowerThanTarget`. This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD)). DocumentReference.author (author) is broader than DocumentReference.author Element `DocumentReference.author` is mapped to FHIR R5 element `DocumentReference.author` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DocumentReference.author` with unmapped reference targets: Device, Organization, Patient, Practitioner, RelatedPerson. Not necessarily who did the actual data entry (i.e. typist) it in or who was the source (informant). DocumentReference.custodian (custodian) is broader than DocumentReference.custodian Element `DocumentReference.custodian` is mapped to FHIR R5 element `DocumentReference.custodian` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.custodian` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DocumentReference.custodian` with unmapped reference targets: Organization. Identifies the logical organization to go to find the current version, where to report issues, etc. This is different from the physical location of the document, which is the technical location of the document, which host may be delegated to the management of some other organization. DocumentReference.authenticator (authenticator) is related to DocumentReference.attester.mode Element `DocumentReference.authenticator` is mapped to FHIR R5 element `DocumentReference.attester.mode` as `RelatedTo`. The mappings for `DocumentReference.authenticator` do not cover the following types: Reference. The mappings for `DocumentReference.authenticator` do not cover the following types based on type expansion: display, reference. Represents a participant within the author institution who has legally authenticated or attested the document. Legal authentication implies that a document has been signed manually or electronically by the legal Authenticator. DocumentReference.status (status) is equivalent to DocumentReference.status Element `DocumentReference.status` is mapped to FHIR R5 element `DocumentReference.status` as `Equivalent`. This is the status of the DocumentReference object, which might be independent from the docStatus element. DocumentReference.docStatus (docStatus) is broader than DocumentReference.docStatus Element `DocumentReference.docStatus` is mapped to FHIR R5 element `DocumentReference.docStatus` as `RelatedTo`. The mappings for `DocumentReference.docStatus` do not cover the following types: CodeableConcept. The mappings for `DocumentReference.docStatus` do not cover the following types based on type expansion: coding. The mappings for `DocumentReference.docStatus` do not allow expression of the necessary codes, per the bindings on the source and target. The document that is pointed to might be in various lifecycle states. DocumentReference.relatesTo (relatesTo) is broader than DocumentReference.relatesTo Element `DocumentReference.relatesTo` is mapped to FHIR R5 element `DocumentReference.relatesTo` as `Equivalent`. DocumentReference.relatesTo.code (code) is broader than DocumentReference.relatesTo.code Element `DocumentReference.relatesTo.code` is mapped to FHIR R5 element `DocumentReference.relatesTo.code` as `SourceIsNarrowerThanTarget`. The mappings for `DocumentReference.relatesTo.code` do not allow expression of the necessary codes, per the bindings on the source and target. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document. DocumentReference.relatesTo.target (target) is broader than DocumentReference.relatesTo.target Element `DocumentReference.relatesTo.target` is mapped to FHIR R5 element `DocumentReference.relatesTo.target` as `RelatedTo`. The mappings for `DocumentReference.relatesTo.target` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DocumentReference.relatesTo.target` with unmapped reference targets: DocumentReference. DocumentReference.description (description) is equivalent to DocumentReference.description Element `DocumentReference.description` is mapped to FHIR R5 element `DocumentReference.description` as `Equivalent`. What the document is about, rather than a terse summary of the document. It is commonly the case that records do not have a title and are collectively referred to by the display name of Record code (e.g. a "consultation" or "progress note"). DocumentReference.securityLabel (securityLabel) is equivalent to DocumentReference.securityLabel Element `DocumentReference.securityLabel` is mapped to FHIR R5 element `DocumentReference.securityLabel` as `Equivalent`. The confidentiality codes can carry multiple vocabulary items. HL7 has developed an understanding of security and privacy tags that might be desirable in a Document Sharing environment, called HL7 Healthcare Privacy and Security Classification System (HCS). The following specification is recommended but not mandated, as the vocabulary bindings are an administrative domain responsibility. The use of this method is up to the policy domain such as the XDS Affinity Domain or other Trust Domain where all parties including sender and recipients are trusted to appropriately tag and enforce. In the HL7 Healthcare Privacy and Security Classification (HCS) there are code systems specific to Confidentiality, Sensitivity, Integrity, and Handling Caveats. Some values would come from a local vocabulary as they are related to workflow roles and special projects. DocumentReference.content (content) is broader than DocumentReference.content Element `DocumentReference.content` is mapped to FHIR R5 element `DocumentReference.content` as `Equivalent`. DocumentReference.content.attachment (attachment) is broader than DocumentReference.content.attachment Element `DocumentReference.content.attachment` is mapped to FHIR R5 element `DocumentReference.content.attachment` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.content.attachment` do not cover the following types: Attachment. The mappings for `DocumentReference.content.attachment` do not cover the following types based on type expansion: contentType, creation, data, hash, language, size, title, url. DocumentReference.context (context) is broader than DocumentReference.context Element `DocumentReference.context` is mapped to FHIR R5 element `DocumentReference.context` as `SourceIsNarrowerThanTarget`. These values are primarily added to help with searching for interesting/relevant documents. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: meta additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.meta (meta) is equivalent to Extension (DSTU2: meta additional types) Element `DocumentReference.meta` is mapped to FHIR R5 element `DocumentReference.meta` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.meta` do not cover the following types: Meta. The mappings for `DocumentReference.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: text additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.text (text) is equivalent to Extension (DSTU2: text additional types) Element `DocumentReference.text` is mapped to FHIR R5 element `DocumentReference.text` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.text` do not cover the following types: Narrative. The mappings for `DocumentReference.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Master Version Specific Identifier additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.masterIdentifier (masterIdentifier) is broader than Extension (DSTU2: Master Version Specific Identifier additional types) Element `DocumentReference.masterIdentifier` is mapped to FHIR R5 element `DocumentReference.identifier` as `RelatedTo`. The mappings for `DocumentReference.masterIdentifier` do not cover the following types: Identifier. The mappings for `DocumentReference.masterIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. CDA Document Id extension and root. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Other identifiers for the document additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.identifier (identifier) is equivalent to Extension (DSTU2: Other identifiers for the document additional types) Element `DocumentReference.identifier` is mapped to FHIR R5 element `DocumentReference.identifier` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.identifier` do not cover the following types: Identifier. The mappings for `DocumentReference.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Who/what authenticated the document additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.authenticator (authenticator) is broader than Extension (DSTU2: Who/what authenticated the document additional types) Element `DocumentReference.authenticator` is mapped to FHIR R5 element `DocumentReference.attester.mode` as `RelatedTo`. The mappings for `DocumentReference.authenticator` do not cover the following types: Reference. The mappings for `DocumentReference.authenticator` do not cover the following types based on type expansion: display, reference. Represents a participant within the author institution who has legally authenticated or attested the document. Legal authentication implies that a document has been signed manually or electronically by the legal Authenticator. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Document creation time (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.created (created) is equivalent to Extension (DSTU2: Document creation time (new)) Element `DocumentReference.created` has a context of DocumentReference based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.created` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Creation time is used for tracking, organizing versions and searching. This is the creation time of the document, not the source material on which it is based. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: When this document reference created (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.indexed (indexed) is equivalent to Extension (DSTU2: When this document reference created (new)) Element `DocumentReference.indexed` has a context of DocumentReference based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.indexed` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Referencing/indexing time is used for tracking, organizing versions and searching. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: preliminary | final | appended | amended | entered-in-error additional types additional codesversion: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.docStatus (docStatus) is equivalent to Extension (DSTU2: preliminary | final | appended | amended | entered-in-error additional types additional codes) Element `DocumentReference.docStatus` is mapped to FHIR R5 element `DocumentReference.docStatus` as `RelatedTo`. The mappings for `DocumentReference.docStatus` do not cover the following types: CodeableConcept. The mappings for `DocumentReference.docStatus` do not cover the following types based on type expansion: coding. The mappings for `DocumentReference.docStatus` do not allow expression of the necessary codes, per the bindings on the source and target. The document that is pointed to might be in various lifecycle states. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: replaces | transforms | signs | appends additional codesversion: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.relatesTo.code (code) is equivalent to Extension (DSTU2: replaces | transforms | signs | appends additional codes) Element `DocumentReference.relatesTo.code` is mapped to FHIR R5 element `DocumentReference.relatesTo.code` as `SourceIsNarrowerThanTarget`. The mappings for `DocumentReference.relatesTo.code` do not allow expression of the necessary codes, per the bindings on the source and target. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document. Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: attachment additional typesversion: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.content.attachment (attachment) is equivalent to Extension (DSTU2: attachment additional types) Element `DocumentReference.content.attachment` is mapped to FHIR R5 element `DocumentReference.content.attachment` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.content.attachment` do not cover the following types: Attachment. The mappings for `DocumentReference.content.attachment` do not cover the following types based on type expansion: contentType, creation, data, hash, language, size, title, url. Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Format/content rules for the document (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.content.format (format) is broader than Extension (DSTU2: Format/content rules for the document (new)) Element `DocumentReference.content.format` has a context of DocumentReference.content based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.content.format` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Note that while IHE mostly issues URNs for format types, not all documents can be identified by a URI. Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Context of the document content (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.context.encounter (encounter) is broader than Extension (DSTU2: Context of the document content (new)) Element `DocumentReference.context.encounter` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.encounter` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Main Clinical Acts Documented (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.context.event (event) is equivalent to Extension (DSTU2: Main Clinical Acts Documented (new)) Element `DocumentReference.context.event` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.event` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). An event can further specialize the act inherent in the type, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more event codes are included, they shall not conflict with the values inherent in the class or type elements as such a conflict would create an ambiguous situation. Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Time of service that is being documented (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.context.period (period) is equivalent to Extension (DSTU2: Time of service that is being documented (new)) Element `DocumentReference.context.period` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.period` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Kind of facility where patient was seen (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.context.facilityType (facilityType) is equivalent to Extension (DSTU2: Kind of facility where patient was seen (new)) Element `DocumentReference.context.facilityType` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.facilityType` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Additional details about where the content was created (e.g. clinical specialty) (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.context.practiceSetting (practiceSetting) is equivalent to Extension (DSTU2: Additional details about where the content was created (e.g. clinical specialty) (new)) Element `DocumentReference.context.practiceSetting` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.practiceSetting` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The value set for this content has an example binding because it is a value set decided by community policy. Other examples exist for consideration: * HITSP created the table HITSP/C80 Table 2-148 Clinical Specialty Value Set (a value set based upon SNOMED CT which is referenced by Direct (XDR and XDM for Direct Messaging Specification, Version 1), as well as Nationwide Health Information Network (NHIN). Query for Documents, Web Service Interface Specification, V 3.0, 07/27/2011 * ELGA (Austria) (ELGA CDA Implementie-rungsleitfäden Registrierung von CDA Dokumenten für ELGA mit IHE Cross-Enterprise Document Sharing: XDS Metadaten (XDSDocumentEntry), [1.2.40.0.34.7.6.3] * XDS Connect-a-thon practiceSettingCode. Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Patient demographics from source (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.context.sourcePatientInfo (sourcePatientInfo) is equivalent to Extension (DSTU2: Patient demographics from source (new)) Element `DocumentReference.context.sourcePatientInfo` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.sourcePatientInfo` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2 to DSTU2: Related identifiers or resources (new)version: 0.1.0) Source Code Relationship Target Code Comment DocumentReference.context.related (related) is equivalent to Extension (DSTU2: Related identifiers or resources (new)) Element `DocumentReference.context.related` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). May be identifiers or resources that caused the DocumentReference or referenced Document to be created. DocumentReference.context.related.identifier (identifier) is equivalent to Extension.extension:identifier (DSTU2: Identifier of related objects or events (new)) Element `DocumentReference.context.related.identifier` is part of an existing definition because parent element `DocumentReference.context.related` requires a cross-version extension. Element `DocumentReference.context.related.identifier` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related.identifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Order numbers, accession numbers, XDW workflow numbers. DocumentReference.context.related.ref (ref) is broader than Extension.extension:ref (DSTU2: Related Resource (new)) Element `DocumentReference.context.related.ref` is part of an existing definition because parent element `DocumentReference.context.related` requires a cross-version extension. Element `DocumentReference.context.related.ref` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related.ref` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Order, DiagnosticOrder, Procedure, EligibilityRequest, etc.
Cross-version mapping for FHIR DSTU2 DocumentReference to FHIR R5 DocumentReference
This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 DocumentReference to FHIR R5.
Element `DocumentReference.meta` is mapped to FHIR R5 element `DocumentReference.meta` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.meta` do not cover the following types: Meta. The mappings for `DocumentReference.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Element `DocumentReference.implicitRules` is mapped to FHIR R5 element `DocumentReference.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.
Element `DocumentReference.language` is mapped to FHIR R5 element `DocumentReference.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Element `DocumentReference.text` is mapped to FHIR R5 element `DocumentReference.text` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.text` do not cover the following types: Narrative. The mappings for `DocumentReference.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.
Element `DocumentReference.contained` is mapped to FHIR R5 element `DocumentReference.contained` as `SourceIsBroaderThanTarget`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
Element `DocumentReference.masterIdentifier` is mapped to FHIR R5 element `DocumentReference.identifier` as `RelatedTo`. The mappings for `DocumentReference.masterIdentifier` do not cover the following types: Identifier. The mappings for `DocumentReference.masterIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. CDA Document Id extension and root.
Element `DocumentReference.identifier` is mapped to FHIR R5 element `DocumentReference.identifier` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.identifier` do not cover the following types: Identifier. The mappings for `DocumentReference.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Element `DocumentReference.subject` is mapped to FHIR R5 element `DocumentReference.subject` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DocumentReference.subject` with unmapped reference targets: Device, Group, Patient, Practitioner.
Element `DocumentReference.type` is mapped to FHIR R5 element `DocumentReference.type` as `Equivalent`. Key metadata element describing the document, used in searching/filtering.
Element `DocumentReference.class` is mapped to FHIR R5 element `DocumentReference.category` as `SourceIsNarrowerThanTarget`. This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD)).
Element `DocumentReference.author` is mapped to FHIR R5 element `DocumentReference.author` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DocumentReference.author` with unmapped reference targets: Device, Organization, Patient, Practitioner, RelatedPerson. Not necessarily who did the actual data entry (i.e. typist) it in or who was the source (informant).
Element `DocumentReference.custodian` is mapped to FHIR R5 element `DocumentReference.custodian` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.custodian` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DocumentReference.custodian` with unmapped reference targets: Organization. Identifies the logical organization to go to find the current version, where to report issues, etc. This is different from the physical location of the document, which is the technical location of the document, which host may be delegated to the management of some other organization.
Element `DocumentReference.authenticator` is mapped to FHIR R5 element `DocumentReference.attester.mode` as `RelatedTo`. The mappings for `DocumentReference.authenticator` do not cover the following types: Reference. The mappings for `DocumentReference.authenticator` do not cover the following types based on type expansion: display, reference. Represents a participant within the author institution who has legally authenticated or attested the document. Legal authentication implies that a document has been signed manually or electronically by the legal Authenticator.
Element `DocumentReference.status` is mapped to FHIR R5 element `DocumentReference.status` as `Equivalent`. This is the status of the DocumentReference object, which might be independent from the docStatus element.
Element `DocumentReference.docStatus` is mapped to FHIR R5 element `DocumentReference.docStatus` as `RelatedTo`. The mappings for `DocumentReference.docStatus` do not cover the following types: CodeableConcept. The mappings for `DocumentReference.docStatus` do not cover the following types based on type expansion: coding. The mappings for `DocumentReference.docStatus` do not allow expression of the necessary codes, per the bindings on the source and target. The document that is pointed to might be in various lifecycle states.
Element `DocumentReference.relatesTo` is mapped to FHIR R5 element `DocumentReference.relatesTo` as `Equivalent`.
Element `DocumentReference.relatesTo.code` is mapped to FHIR R5 element `DocumentReference.relatesTo.code` as `SourceIsNarrowerThanTarget`. The mappings for `DocumentReference.relatesTo.code` do not allow expression of the necessary codes, per the bindings on the source and target. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document.
Element `DocumentReference.relatesTo.target` is mapped to FHIR R5 element `DocumentReference.relatesTo.target` as `RelatedTo`. The mappings for `DocumentReference.relatesTo.target` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DocumentReference.relatesTo.target` with unmapped reference targets: DocumentReference.
Element `DocumentReference.description` is mapped to FHIR R5 element `DocumentReference.description` as `Equivalent`. What the document is about, rather than a terse summary of the document. It is commonly the case that records do not have a title and are collectively referred to by the display name of Record code (e.g. a "consultation" or "progress note").
Element `DocumentReference.securityLabel` is mapped to FHIR R5 element `DocumentReference.securityLabel` as `Equivalent`. The confidentiality codes can carry multiple vocabulary items. HL7 has developed an understanding of security and privacy tags that might be desirable in a Document Sharing environment, called HL7 Healthcare Privacy and Security Classification System (HCS). The following specification is recommended but not mandated, as the vocabulary bindings are an administrative domain responsibility. The use of this method is up to the policy domain such as the XDS Affinity Domain or other Trust Domain where all parties including sender and recipients are trusted to appropriately tag and enforce. In the HL7 Healthcare Privacy and Security Classification (HCS) there are code systems specific to Confidentiality, Sensitivity, Integrity, and Handling Caveats. Some values would come from a local vocabulary as they are related to workflow roles and special projects.
Element `DocumentReference.content` is mapped to FHIR R5 element `DocumentReference.content` as `Equivalent`.
Element `DocumentReference.content.attachment` is mapped to FHIR R5 element `DocumentReference.content.attachment` as `SourceIsBroaderThanTarget`. The mappings for `DocumentReference.content.attachment` do not cover the following types: Attachment. The mappings for `DocumentReference.content.attachment` do not cover the following types based on type expansion: contentType, creation, data, hash, language, size, title, url.
Element `DocumentReference.context` is mapped to FHIR R5 element `DocumentReference.context` as `SourceIsNarrowerThanTarget`. These values are primarily added to help with searching for interesting/relevant documents.
Element `DocumentReference.created` has a context of DocumentReference based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.created` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Creation time is used for tracking, organizing versions and searching. This is the creation time of the document, not the source material on which it is based.
Element `DocumentReference.indexed` has a context of DocumentReference based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.indexed` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Referencing/indexing time is used for tracking, organizing versions and searching.
Element `DocumentReference.content.format` has a context of DocumentReference.content based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.content.format` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Note that while IHE mostly issues URNs for format types, not all documents can be identified by a URI.
Element `DocumentReference.context.encounter` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.encounter` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `DocumentReference.context.event` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.event` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). An event can further specialize the act inherent in the type, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more event codes are included, they shall not conflict with the values inherent in the class or type elements as such a conflict would create an ambiguous situation.
Element `DocumentReference.context.period` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.period` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `DocumentReference.context.facilityType` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.facilityType` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `DocumentReference.context.practiceSetting` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.practiceSetting` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The value set for this content has an example binding because it is a value set decided by community policy. Other examples exist for consideration: * HITSP created the table HITSP/C80 Table 2-148 Clinical Specialty Value Set (a value set based upon SNOMED CT which is referenced by Direct (XDR and XDM for Direct Messaging Specification, Version 1), as well as Nationwide Health Information Network (NHIN). Query for Documents, Web Service Interface Specification, V 3.0, 07/27/2011 * ELGA (Austria) (ELGA CDA Implementie-rungsleitfäden Registrierung von CDA Dokumenten für ELGA mit IHE Cross-Enterprise Document Sharing: XDS Metadaten (XDSDocumentEntry), [1.2.40.0.34.7.6.3] * XDS Connect-a-thon practiceSettingCode.
Element `DocumentReference.context.sourcePatientInfo` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.sourcePatientInfo` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `DocumentReference.context.related` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). May be identifiers or resources that caused the DocumentReference or referenced Document to be created.
Element `DocumentReference.context.related.identifier` is part of an existing definition because parent element `DocumentReference.context.related` requires a cross-version extension. Element `DocumentReference.context.related.identifier` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related.identifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Order numbers, accession numbers, XDW workflow numbers.
Element `DocumentReference.context.related.ref` is part of an existing definition because parent element `DocumentReference.context.related` requires a cross-version extension. Element `DocumentReference.context.related.ref` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related.ref` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Order, DiagnosticOrder, Procedure, EligibilityRequest, etc.