Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R2-DocumentManifest-element-map-to-R5 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R2DocumentManifestElementMapToR5 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 DocumentManifest to FHIR 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/DocumentManifest|1.0.2 to Basicversion: 5.0.0)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.meta (meta) | is equivalent to | Basic.meta | Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `DocumentManifest.meta` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.meta` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
| DocumentManifest.implicitRules (implicitRules) | is equivalent to | Basic.implicitRules | Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `DocumentManifest.implicitRules` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.implicitRules` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). 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. |
| DocumentManifest.language (language) | is equivalent to | Basic.language | Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `DocumentManifest.language` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.language` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). 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). |
| DocumentManifest.text (text) | is equivalent to | Basic.text | Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `DocumentManifest.text` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.text` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. |
| DocumentManifest.contained (contained) | is equivalent to | Basic.contained | Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `DocumentManifest.contained` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.contained` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). 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. |
| DocumentManifest.identifier (identifier) | is equivalent to | Basic.identifier | Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `DocumentManifest.identifier` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.identifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
| DocumentManifest.subject (subject) | is equivalent to | Basic.subject | Element matches Basic element path `Basic.subject` (`Basic.subject`), use that element instead. Element `DocumentManifest.subject` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.subject` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
| DocumentManifest.author (author) | is equivalent to | Basic.author | Element matches Basic element path `Basic.author` (`Basic.author`), use that element instead. Element `DocumentManifest.author` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.author` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant). |
| DocumentManifest.created (created) | is equivalent to | Basic.created | Element matches Basic element path `Basic.created` (`Basic.created`), use that element instead. Element `DocumentManifest.created` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.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 set, not the documents on which it is based. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentManifest|1.0.2 to DSTU2: Unique Identifier for the set of documents (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.masterIdentifier (masterIdentifier) | is broader than | Extension (DSTU2: Unique Identifier for the set of documents (new)) | Element `DocumentManifest.masterIdentifier` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.masterIdentifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentManifest|1.0.2 to DSTU2: Intended to get notified about this set of documents (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.recipient (recipient) | is broader than | Extension (DSTU2: Intended to get notified about this set of documents (new)) | Element `DocumentManifest.recipient` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.recipient` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). How the recipient receives the document set or is notified of it is up to the implementation. This element is just a statement of intent. If the recipient is a person, and it is not known whether the person is a patient or a practitioner, RelatedPerson would be the default choice. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentManifest|1.0.2 to DSTU2: Kind of document set (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.type (type) | is broader than | Extension (DSTU2: Kind of document set (new)) | Element `DocumentManifest.type` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentManifest|1.0.2 to DSTU2: The source system/application/software (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.source (source) | is broader than | Extension (DSTU2: The source system/application/software (new)) | Element `DocumentManifest.source` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.source` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentManifest|1.0.2 to DSTU2: current | superseded | entered-in-error (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.status (status) | is broader than | Extension (DSTU2: current | superseded | entered-in-error (new)) | Element `DocumentManifest.status` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.status` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentManifest|1.0.2 to DSTU2: Human-readable description (title) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.description (description) | is broader than | Extension (DSTU2: Human-readable description (title) (new)) | Element `DocumentManifest.description` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.description` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). 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"). |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentManifest|1.0.2 to DSTU2: The items included (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.content (content) | is broader than | Extension (DSTU2: The items included (new)) | Element `DocumentManifest.content` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.content` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
| DocumentManifest.content.p[x] (p[x]) | is broader than | Extension.extension:p (DSTU2: Contents of this set of documents (new)) | Element `DocumentManifest.content.p[x]` is part of an existing definition because parent element `DocumentManifest.content` requires a cross-version extension. Element `DocumentManifest.content.p[x]` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.content.p[x]` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The intended focus of the DocumentManifest is for the reference to target either DocumentReference or Media Resources, and most implementation guides will restrict to these resources. The reference is to "Any" to support EN 13606 usage, where an extract is DocumentManifest that references List and Composition resources. |
Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentManifest|1.0.2 to DSTU2: Related things (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.related (related) | is broader than | Extension (DSTU2: Related things (new)) | Element `DocumentManifest.related` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.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 DocumentManifest to be created. |
| DocumentManifest.related.identifier (identifier) | is broader than | Extension.extension:identifier (DSTU2: Identifiers of things that are related (new)) | Element `DocumentManifest.related.identifier` is part of an existing definition because parent element `DocumentManifest.related` requires a cross-version extension. Element `DocumentManifest.related.identifier` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.related.identifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). If both identifier and ref elements are present they shall refer to the same thing. |
| DocumentManifest.related.ref (ref) | is broader than | Extension.extension:ref (DSTU2: Related Resource (new)) | Element `DocumentManifest.related.ref` is part of an existing definition because parent element `DocumentManifest.related` requires a cross-version extension. Element `DocumentManifest.related.ref` is not mapped to FHIR R5, since FHIR DSTU2 `DocumentManifest` is not mapped. Element `DocumentManifest.related.ref` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). If both identifier and ref elements are present they shall refer to the same thing. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r2.r5#0.1.0 based on FHIR 5.0.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change