R2-DocumentReference-element-map-to-R5
type: ConceptMap
node role: treeRoot
id:
  v: R2-DocumentReference-element-map-to-R5
text:
  status:
    v: generated
  div:
    v: 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…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r5
        l: hl7.fhir.uv.xver-r2.r5
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r5
        l: hl7.fhir.uv.xver-r2.r5
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R2-DocumentReference-element-map-to-R5
  l: R2-DocumentReference-element-map-to-R5
version:
  v: 0.1.0
name:
  v: R2DocumentReferenceElementMapToR5
title:
  v: Cross-version mapping for FHIR DSTU2 DocumentReference to FHIR R5 DocumentReference
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:05:26.1098386-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 DocumentReference to FHIR R5.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source scope: Canonical
  v: http://hl7.org/fhir/1.0
  l: http://hl7.org/fhir/1.0
target scope: Uri
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
    l: http://hl7.org/fhir/StructureDefinition/DocumentReference
  target:
    v: http://hl7.org/fhir/StructureDefinition/DocumentReference|5.0.0
    l: http://hl7.org/fhir/StructureDefinition/DocumentReference
  element:
    code:
      v: DocumentReference.meta
    display:
      v: meta
    target:
      code:
        v: DocumentReference.meta
      display:
        v: DocumentReference.meta
      relationship:
        v: source-is-broader-than-target
      comment:
        v: 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:
    code:
      v: DocumentReference.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: DocumentReference.implicitRules
      display:
        v: DocumentReference.implicitRules
      relationship:
        v: equivalent
      comment:
        v: 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:
    code:
      v: DocumentReference.language
    display:
      v: language
    target:
      code:
        v: DocumentReference.language
      display:
        v: DocumentReference.language
      relationship:
        v: equivalent
      comment:
        v: 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:
    code:
      v: DocumentReference.text
    display:
      v: text
    target:
      code:
        v: DocumentReference.text
      display:
        v: DocumentReference.text
      relationship:
        v: source-is-broader-than-target
      comment:
        v: 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:
    code:
      v: DocumentReference.contained
    display:
      v: contained
    target:
      code:
        v: DocumentReference.contained
      display:
        v: DocumentReference.contained
      relationship:
        v: equivalent
      comment:
        v: 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:
    code:
      v: DocumentReference.masterIdentifier
    display:
      v: masterIdentifier
    target:
      code:
        v: DocumentReference.identifier
      display:
        v: DocumentReference.identifier
      relationship:
        v: related-to
      comment:
        v: 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:
    code:
      v: DocumentReference.identifier
    display:
      v: identifier
    target:
      code:
        v: DocumentReference.identifier
      display:
        v: DocumentReference.identifier
      relationship:
        v: source-is-broader-than-target
      comment:
        v: 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:
    code:
      v: DocumentReference.subject
    display:
      v: subject
    target:
      code:
        v: DocumentReference.subject
      display:
        v: DocumentReference.subject
      relationship:
        v: source-is-broader-than-target
      comment:
        v: 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:
    code:
      v: DocumentReference.type

v: type

code:
  v: DocumentReference.type
display:
  v: DocumentReference.type
relationship:
  v: equivalent
comment:
  v: Element `DocumentReference.type` is mapped to FHIR R5 element `DocumentReference.type` as `Equivalent`. Key metadata element describing the document, used in searching/filtering.

code:
  v: DocumentReference.class
display:
  v: class
target:
  code:
    v: DocumentReference.category
  display:
    v: DocumentReference.category
  relationship:
    v: source-is-narrower-than-target
  comment:
    v: 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)).

code:
  v: DocumentReference.author
display:
  v: author
target:
  code:
    v: DocumentReference.author
  display:
    v: DocumentReference.author
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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).

code:
  v: DocumentReference.custodian
display:
  v: custodian
target:
  code:
    v: DocumentReference.custodian
  display:
    v: DocumentReference.custodian
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: DocumentReference.authenticator
display:
  v: authenticator
target:
  code:
    v: DocumentReference.attester.mode
  display:
    v: DocumentReference.attester.mode
  relationship:
    v: related-to
  comment:
    v: 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.

code:
  v: DocumentReference.status
display:
  v: status
target:
  code:
    v: DocumentReference.status
  display:
    v: DocumentReference.status
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: DocumentReference.docStatus
display:
  v: docStatus
target:
  code:
    v: DocumentReference.docStatus
  display:
    v: DocumentReference.docStatus
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: DocumentReference.relatesTo
display:
  v: relatesTo
target:
  code:
    v: DocumentReference.relatesTo
  display:
    v: DocumentReference.relatesTo
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `DocumentReference.relatesTo` is mapped to FHIR R5 element `DocumentReference.relatesTo` as `Equivalent`.

code:
  v: DocumentReference.relatesTo.code
display:
  v: code
target:
  code:
    v: DocumentReference.relatesTo.code
  display:
    v: DocumentReference.relatesTo.code
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: DocumentReference.relatesTo.target
display:
  v: target
target:
  code:
    v: DocumentReference.relatesTo.target
  display:
    v: DocumentReference.relatesTo.target
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: DocumentReference.description
display:
  v: description
target:
  code:
    v: DocumentReference.description
  display:
    v: DocumentReference.description
  relationship:
    v: equivalent
  comment:
    v: 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").

code:
  v: DocumentReference.securityLabel
display:
  v: securityLabel
target:
  code:
    v: DocumentReference.securityLabel
  display:
    v: DocumentReference.securityLabel
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: DocumentReference.content
display:
  v: content
target:
  code:
    v: DocumentReference.content
  display:
    v: DocumentReference.content
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `DocumentReference.content` is mapped to FHIR R5 element `DocumentReference.content` as `Equivalent`.

code:
  v: DocumentReference.content.attachment
display:
  v: attachment
target:
  code:
    v: DocumentReference.content.attachment
  display:
    v: DocumentReference.content.attachment
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: DocumentReference.context
display:
  v: context
target:
  code:
    v: DocumentReference.context
  display:
    v: DocumentReference.context
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.meta|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.meta
element:
  code:
    v: DocumentReference.meta
  display:
    v: meta
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.text|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.text
element:
  code:
    v: DocumentReference.text
  display:
    v: text
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.masterIdentifier|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.masterIdentifier
element:
  code:
    v: DocumentReference.masterIdentifier
  display:
    v: masterIdentifier
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.identifier|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.identifier
element:
  code:
    v: DocumentReference.identifier
  display:
    v: identifier
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.authenticator|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.authenticator
element:
  code:
    v: DocumentReference.authenticator
  display:
    v: authenticator
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.created|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.created
element:
  code:
    v: DocumentReference.created
  display:
    v: created
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.indexed|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.indexed
element:
  code:
    v: DocumentReference.indexed
  display:
    v: indexed
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.docStatus|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.docStatus
element:
  code:
    v: DocumentReference.docStatus
  display:
    v: docStatus
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.relatesTo.code|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.relatesTo.code
element:
  code:
    v: DocumentReference.relatesTo.code
  display:
    v: code
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.content.attachment|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.content.attachment
element:
  code:
    v: DocumentReference.content.attachment
  display:
    v: attachment
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.content.format|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.content.format
element:
  code:
    v: DocumentReference.content.format
  display:
    v: format
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.encounter|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.encounter
element:
  code:
    v: DocumentReference.context.encounter
  display:
    v: encounter
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.event|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.event
element:
  code:
    v: DocumentReference.context.event
  display:
    v: event
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.period|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.period
element:
  code:
    v: DocumentReference.context.period
  display:
    v: period
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.facilityType|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.facilityType
element:
  code:
    v: DocumentReference.context.facilityType
  display:
    v: facilityType
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.practiceSetting|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.practiceSetting
element:
  code:
    v: DocumentReference.context.practiceSetting
  display:
    v: practiceSetting
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.sourcePatientInfo|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.sourcePatientInfo
element:
  code:
    v: DocumentReference.context.sourcePatientInfo
  display:
    v: sourcePatientInfo
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/DocumentReference|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/DocumentReference
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.related|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-DocumentReference.context.related
element:
  code:
    v: DocumentReference.context.related
  display:
    v: related
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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:
  code:
    v: DocumentReference.context.related.identifier
  display:
    v: identifier
  target:
    code:
      v: Extension.extension:identifier
    relationship:
      v: equivalent
    comment:
      v: 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:
  code:
    v: DocumentReference.context.related.ref
  display:
    v: ref
  target:
    code:
      v: Extension.extension:ref
    relationship:
      v: source-is-broader-than-target
    comment:
      v: 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.