FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r4b.r4
Resource TypeConceptMap
IdConceptMap-R4B-GraphDefinition-element-map-to-R4.json
FHIR VersionR4
Sourcehttp://hl7.org/fhir/uv/xver-r4b.r4/0.1.0/ConceptMap-R4B-GraphDefinition-element-map-to-R4.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R4B-GraphDefinition-element-map-to-R4
Version0.1.0
Statusactive
Date2026-03-17T16:03:48.1392035-05:00
NameR4BGraphDefinitionElementMapToR4
TitleCross-version mapping for FHIR R4B GraphDefinition to FHIR R4 GraphDefinition
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R4B GraphDefinition to FHIR R4.

Resources that use this resource

No resources found

Resources that this resource uses

No resources found

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ConceptMap R4B-GraphDefinition-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/GraphDefinition|4.3.0 to GraphDefinitionversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
GraphDefinition.meta (meta)is equivalent toGraphDefinition.metaElement `GraphDefinition.meta` is mapped to FHIR R4 element `GraphDefinition.meta` as `Equivalent`.
GraphDefinition.implicitRules (implicitRules)is equivalent toGraphDefinition.implicitRulesElement `GraphDefinition.implicitRules` is mapped to FHIR R4 element `GraphDefinition.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.
GraphDefinition.language (language)is equivalent toGraphDefinition.languageElement `GraphDefinition.language` is mapped to FHIR R4 element `GraphDefinition.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).
GraphDefinition.text (text)is equivalent toGraphDefinition.textElement `GraphDefinition.text` is mapped to FHIR R4 element `GraphDefinition.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.
GraphDefinition.contained (contained)is equivalent toGraphDefinition.containedElement `GraphDefinition.contained` is mapped to FHIR R4 element `GraphDefinition.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.
GraphDefinition.url (url)is equivalent toGraphDefinition.urlElement `GraphDefinition.url` is mapped to FHIR R4 element `GraphDefinition.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
GraphDefinition.version (version)is equivalent toGraphDefinition.versionElement `GraphDefinition.version` is mapped to FHIR R4 element `GraphDefinition.version` as `Equivalent`. There may be different graph definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the graph definition with the format [url]|[version].
GraphDefinition.name (name)is equivalent toGraphDefinition.nameElement `GraphDefinition.name` is mapped to FHIR R4 element `GraphDefinition.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
GraphDefinition.status (status)is equivalent toGraphDefinition.statusElement `GraphDefinition.status` is mapped to FHIR R4 element `GraphDefinition.status` as `Equivalent`. Allows filtering of graph definitions that are appropriate for use versus not.
GraphDefinition.experimental (experimental)is equivalent toGraphDefinition.experimentalElement `GraphDefinition.experimental` is mapped to FHIR R4 element `GraphDefinition.experimental` as `Equivalent`. Allows filtering of graph definitions that are appropriate for use versus not.
GraphDefinition.date (date)is equivalent toGraphDefinition.dateElement `GraphDefinition.date` is mapped to FHIR R4 element `GraphDefinition.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the graph definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
GraphDefinition.publisher (publisher)is equivalent toGraphDefinition.publisherElement `GraphDefinition.publisher` is mapped to FHIR R4 element `GraphDefinition.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the graph definition is the organization or individual primarily responsible for the maintenance and upkeep of the graph definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the graph definition. This item SHOULD be populated unless the information is available from context.
GraphDefinition.contact (contact)is equivalent toGraphDefinition.contactElement `GraphDefinition.contact` is mapped to FHIR R4 element `GraphDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
GraphDefinition.description (description)is equivalent toGraphDefinition.descriptionElement `GraphDefinition.description` is mapped to FHIR R4 element `GraphDefinition.description` as `Equivalent`. This description can be used to capture details such as why the graph definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the graph definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the graph definition is presumed to be the predominant language in the place the graph definition was created).
GraphDefinition.useContext (useContext)is equivalent toGraphDefinition.useContextElement `GraphDefinition.useContext` is mapped to FHIR R4 element `GraphDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
GraphDefinition.jurisdiction (jurisdiction)is equivalent toGraphDefinition.jurisdictionElement `GraphDefinition.jurisdiction` is mapped to FHIR R4 element `GraphDefinition.jurisdiction` as `Equivalent`. It may be possible for the graph definition to be used in jurisdictions other than those for which it was originally designed or intended.
GraphDefinition.purpose (purpose)is equivalent toGraphDefinition.purposeElement `GraphDefinition.purpose` is mapped to FHIR R4 element `GraphDefinition.purpose` as `Equivalent`. This element does not describe the usage of the graph definition. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this graph definition.
GraphDefinition.start (start)is equivalent toGraphDefinition.startElement `GraphDefinition.start` is mapped to FHIR R4 element `GraphDefinition.start` as `SourceIsNarrowerThanTarget`. The mappings for `GraphDefinition.start` do not allow expression of the necessary codes, per the bindings on the source and target.
GraphDefinition.profile (profile)is equivalent toGraphDefinition.profileElement `GraphDefinition.profile` is mapped to FHIR R4 element `GraphDefinition.profile` as `Equivalent`. The code does not include the '