FHIR IG analytics| Package | hl7.fhir.uv.xver-r4b.r4 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R4B-DocumentManifest-element-map-to-R4.json |
| FHIR Version | R4 |
| Source | http://hl7.org/fhir/uv/xver-r4b.r4/0.1.0/ConceptMap-R4B-DocumentManifest-element-map-to-R4.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R4B-DocumentManifest-element-map-to-R4 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:03:46.1713407-05:00 |
| Name | R4BDocumentManifestElementMapToR4 |
| Title | Cross-version mapping for FHIR R4B DocumentManifest to FHIR R4 DocumentManifest |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R4B DocumentManifest to FHIR R4. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R4B-DocumentManifest-element-map-to-R4
Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/4.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DocumentManifest|4.3.0 to DocumentManifestversion: 4.0.1)
| Source Code | Relationship | Target Code | Comment |
| DocumentManifest.meta (meta) | is equivalent to | DocumentManifest.meta | Element `DocumentManifest.meta` is mapped to FHIR R4 element `DocumentManifest.meta` as `Equivalent`. |
| DocumentManifest.implicitRules (implicitRules) | is equivalent to | DocumentManifest.implicitRules | Element `DocumentManifest.implicitRules` is mapped to FHIR R4 element `DocumentManifest.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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. |
| DocumentManifest.language (language) | is equivalent to | DocumentManifest.language | Element `DocumentManifest.language` is mapped to FHIR R4 element `DocumentManifest.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). |
| DocumentManifest.text (text) | is equivalent to | DocumentManifest.text | Element `DocumentManifest.text` is mapped to FHIR R4 element `DocumentManifest.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. |
| DocumentManifest.contained (contained) | is equivalent to | DocumentManifest.contained | Element `DocumentManifest.contained` is mapped to FHIR R4 element `DocumentManifest.contained` as `Equivalent`. 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
| DocumentManifest.masterIdentifier (masterIdentifier) | is equivalent to | DocumentManifest.masterIdentifier | Element `DocumentManifest.masterIdentifier` is mapped to FHIR R4 element `DocumentManifest.masterIdentifier` as `Equivalent`. |
| DocumentManifest.identifier (identifier) | is equivalent to | DocumentManifest.identifier | Element `DocumentManifest.identifier` is mapped to FHIR R4 element `DocumentManifest.identifier` as `Equivalent`. |
| DocumentManifest.status (status) | is equivalent to | DocumentManifest.status | Element `DocumentManifest.status` is mapped to FHIR R4 element `DocumentManifest.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes that mark the manifest as not currently valid. |
| DocumentManifest.type (type) | is equivalent to | DocumentManifest.type | Element `DocumentManifest.type` is mapped to FHIR R4 element `DocumentManifest.type` as `Equivalent`. Specifies the kind of this set of documents (e.g. Patient Summary, Discharge Summary, Prescription, etc.). The type of a set of documents may be the same as one of the documents in it - especially if there is only one - but it may be wider. |
| DocumentManifest.subject (subject) | is equivalent to | DocumentManifest.subject | Element `DocumentManifest.subject` is mapped to FHIR R4 element `DocumentManifest.subject` as `Equivalent`. |
| DocumentManifest.created (created) | is equivalent to | DocumentManifest.created | Element `DocumentManifest.created` is mapped to FHIR R4 element `DocumentManifest.created` as `Equivalent`. 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. |
| DocumentManifest.author (author) | is equivalent to | DocumentManifest.author | Element `DocumentManifest.author` is mapped to FHIR R4 element `DocumentManifest.author` as `Equivalent`. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant). |
| DocumentManifest.recipient (recipient) | is equivalent to | DocumentManifest.recipient | Element `DocumentManifest.recipient` is mapped to FHIR R4 element `DocumentManifest.recipient` as `Equivalent`. 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. |
| DocumentManifest.source (source) | is equivalent to | DocumentManifest.source | Element `DocumentManifest.source` is mapped to FHIR R4 element `DocumentManifest.source` as `Equivalent`. |
| DocumentManifest.description (description) | is equivalent to | DocumentManifest.description | Element `DocumentManifest.description` is mapped to FHIR R4 element `DocumentManifest.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"). |
| DocumentManifest.content (content) | is equivalent to | DocumentManifest.content | Element `DocumentManifest.content` is mapped to FHIR R4 element `DocumentManifest.content` as `Equivalent`. When used for XDS the intended focus of the DocumentManifest is for the reference to target to be a set of DocumentReference Resources. The reference is to "Any" to support EN 13606 usage, where an extract is DocumentManifest that references List and Composition resources. |
| DocumentManifest.related (related) | maps to wider concept | DocumentManifest.related | Element `DocumentManifest.related` is mapped to FHIR R4 element `DocumentManifest.related` as `Equivalent`. May be identifiers or resources that caused the DocumentManifest to be created. |
| DocumentManifest.related.identifier (identifier) | is equivalent to | DocumentManifest.related.identifier | Element `DocumentManifest.related.identifier` is mapped to FHIR R4 element `DocumentManifest.related.identifier` as `Equivalent`. If both identifier and ref elements are present they shall refer to the same thing. |
| DocumentManifest.related.ref (ref) | is equivalent to | DocumentManifest.related.ref | Element `DocumentManifest.related.ref` is mapped to FHIR R4 element `DocumentManifest.related.ref` as `Equivalent`. If both identifier and ref elements are present they shall refer to the same thing. |
{
"resourceType": "ConceptMap",
"id": "R4B-DocumentManifest-element-map-to-R4",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fhir"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 0,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-DocumentManifest-element-map-to-R4",
"version": "0.1.0",
"name": "R4BDocumentManifestElementMapToR4",
"title": "Cross-version mapping for FHIR R4B DocumentManifest to FHIR R4 DocumentManifest",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:03:46.1713407-05:00",
"contact": [
{
"name": "FHIR Infrastructure",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description": "This ConceptMap represents cross-version mappings for elements from a FHIR R4B DocumentManifest to FHIR R4.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceCanonical": "http://hl7.org/fhir/4.3",
"targetUri": "http://hl7.org/fhir/4.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/DocumentManifest",
"sourceVersion": "4.3.0",
"target": "http://hl7.org/fhir/StructureDefinition/DocumentManifest",
"targetVersion": "4.0.1",
"element": [
{
"code": "DocumentManifest.meta",
"display": "meta",
"target": [
{
"code": "DocumentManifest.meta",
"display": "DocumentManifest.meta",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.meta` is mapped to FHIR R4 element `DocumentManifest.meta` as `Equivalent`."
}
]
},
{
"code": "DocumentManifest.implicitRules",
"display": "implicitRules",
"target": [
{
"code": "DocumentManifest.implicitRules",
"display": "DocumentManifest.implicitRules",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.implicitRules` is mapped to FHIR R4 element `DocumentManifest.implicitRules` as `Equivalent`.\nAsserting 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."
}
]
},
{
"code": "DocumentManifest.language",
"display": "language",
"target": [
{
"code": "DocumentManifest.language",
"display": "DocumentManifest.language",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.language` is mapped to FHIR R4 element `DocumentManifest.language` as `Equivalent`.\nLanguage 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)."
}
]
},
{
"code": "DocumentManifest.text",
"display": "text",
"target": [
{
"code": "DocumentManifest.text",
"display": "DocumentManifest.text",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.text` is mapped to FHIR R4 element `DocumentManifest.text` as `Equivalent`.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later."
}
]
},
{
"code": "DocumentManifest.contained",
"display": "contained",
"target": [
{
"code": "DocumentManifest.contained",
"display": "DocumentManifest.contained",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.contained` is mapped to FHIR R4 element `DocumentManifest.contained` as `Equivalent`.\nThis 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels."
}
]
},
{
"code": "DocumentManifest.masterIdentifier",
"display": "masterIdentifier",
"target": [
{
"code": "DocumentManifest.masterIdentifier",
"display": "DocumentManifest.masterIdentifier",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.masterIdentifier` is mapped to FHIR R4 element `DocumentManifest.masterIdentifier` as `Equivalent`."
}
]
},
{
"code": "DocumentManifest.identifier",
"display": "identifier",
"target": [
{
"code": "DocumentManifest.identifier",
"display": "DocumentManifest.identifier",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.identifier` is mapped to FHIR R4 element `DocumentManifest.identifier` as `Equivalent`."
}
]
},
{
"code": "DocumentManifest.status",
"display": "status",
"target": [
{
"code": "DocumentManifest.status",
"display": "DocumentManifest.status",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.status` is mapped to FHIR R4 element `DocumentManifest.status` as `Equivalent`.\nThis element is labeled as a modifier because the status contains the codes that mark the manifest as not currently valid."
}
]
},
{
"code": "DocumentManifest.type",
"display": "type",
"target": [
{
"code": "DocumentManifest.type",
"display": "DocumentManifest.type",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.type` is mapped to FHIR R4 element `DocumentManifest.type` as `Equivalent`.\nSpecifies the kind of this set of documents (e.g. Patient Summary, Discharge Summary, Prescription, etc.). The type of a set of documents may be the same as one of the documents in it - especially if there is only one - but it may be wider."
}
]
},
{
"code": "DocumentManifest.subject",
"display": "subject",
"target": [
{
"code": "DocumentManifest.subject",
"display": "DocumentManifest.subject",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.subject` is mapped to FHIR R4 element `DocumentManifest.subject` as `Equivalent`."
}
]
},
{
"code": "DocumentManifest.created",
"display": "created",
"target": [
{
"code": "DocumentManifest.created",
"display": "DocumentManifest.created",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.created` is mapped to FHIR R4 element `DocumentManifest.created` as `Equivalent`.\nCreation 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."
}
]
},
{
"code": "DocumentManifest.author",
"display": "author",
"target": [
{
"code": "DocumentManifest.author",
"display": "DocumentManifest.author",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.author` is mapped to FHIR R4 element `DocumentManifest.author` as `Equivalent`.\nNot necessarily who did the actual data entry (i.e. typist) or who was the source (informant)."
}
]
},
{
"code": "DocumentManifest.recipient",
"display": "recipient",
"target": [
{
"code": "DocumentManifest.recipient",
"display": "DocumentManifest.recipient",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.recipient` is mapped to FHIR R4 element `DocumentManifest.recipient` as `Equivalent`.\nHow 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."
}
]
},
{
"code": "DocumentManifest.source",
"display": "source",
"target": [
{
"code": "DocumentManifest.source",
"display": "DocumentManifest.source",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.source` is mapped to FHIR R4 element `DocumentManifest.source` as `Equivalent`."
}
]
},
{
"code": "DocumentManifest.description",
"display": "description",
"target": [
{
"code": "DocumentManifest.description",
"display": "DocumentManifest.description",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.description` is mapped to FHIR R4 element `DocumentManifest.description` as `Equivalent`.\nWhat 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": "DocumentManifest.content",
"display": "content",
"target": [
{
"code": "DocumentManifest.content",
"display": "DocumentManifest.content",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.content` is mapped to FHIR R4 element `DocumentManifest.content` as `Equivalent`.\nWhen used for XDS the intended focus of the DocumentManifest is for the reference to target to be a set of DocumentReference Resources. The reference is to \"Any\" to support EN 13606 usage, where an extract is DocumentManifest that references List and Composition resources."
}
]
},
{
"code": "DocumentManifest.related",
"display": "related",
"target": [
{
"code": "DocumentManifest.related",
"display": "DocumentManifest.related",
"equivalence": "wider",
"comment": "Element `DocumentManifest.related` is mapped to FHIR R4 element `DocumentManifest.related` as `Equivalent`.\nMay be identifiers or resources that caused the DocumentManifest to be created."
}
]
},
{
"code": "DocumentManifest.related.identifier",
"display": "identifier",
"target": [
{
"code": "DocumentManifest.related.identifier",
"display": "DocumentManifest.related.identifier",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.related.identifier` is mapped to FHIR R4 element `DocumentManifest.related.identifier` as `Equivalent`.\nIf both identifier and ref elements are present they shall refer to the same thing."
}
]
},
{
"code": "DocumentManifest.related.ref",
"display": "ref",
"target": [
{
"code": "DocumentManifest.related.ref",
"display": "DocumentManifest.related.ref",
"equivalence": "equivalent",
"comment": "Element `DocumentManifest.related.ref` is mapped to FHIR R4 element `DocumentManifest.related.ref` as `Equivalent`.\nIf both identifier and ref elements are present they shall refer to the same thing."
}
]
}
]
}
]
}