Extensions for Using Data Elements from FHIR R5 in FHIR R4B
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR R4B - Downloaded Version null See the Directory of published versions

ConceptMap: R5ResearchSubjectElementMapToR4B

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R5-ResearchSubject-element-map-to-R4B Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5ResearchSubjectElementMapToR4B

This ConceptMap represents cross-version mappings for elements from a FHIR R5 ResearchSubject to FHIR R4B.

Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.3


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ResearchSubject|5.0.0 to ResearchSubjectversion: 4.3.0)

Source CodeRelationshipTarget CodeComment
ResearchSubject.meta (meta)​is equivalent toResearchSubject.metaElement `ResearchSubject.meta` is mapped to FHIR R4B element `ResearchSubject.meta` as `Equivalent`.
ResearchSubject.implicitRules (implicitRules)​is equivalent toResearchSubject.implicitRulesElement `ResearchSubject.implicitRules` is mapped to FHIR R4B element `ResearchSubject.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 its narrative along with other profiles, value sets, etc.
ResearchSubject.language (language)​is equivalent toResearchSubject.languageElement `ResearchSubject.language` is mapped to FHIR R4B element `ResearchSubject.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).
ResearchSubject.text (text)​is equivalent toResearchSubject.textElement `ResearchSubject.text` is mapped to FHIR R4B element `ResearchSubject.text` as `Equivalent`. Contained resources do not have a 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.
ResearchSubject.contained (contained)​is equivalent toResearchSubject.containedElement `ResearchSubject.contained` is mapped to FHIR R4B element `ResearchSubject.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.
ResearchSubject.identifier (identifier)​is equivalent toResearchSubject.identifierElement `ResearchSubject.identifier` is mapped to FHIR R4B element `ResearchSubject.identifier` as `Equivalent`.
ResearchSubject.status (status)​maps to wider conceptResearchSubject.statusElement `ResearchSubject.status` is mapped to FHIR R4B element `ResearchSubject.status` as `RelatedTo`. The mappings for `ResearchSubject.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `ResearchSubject.status` is a modifier element, so this extension does not need to be defined as a modifier.
ResearchSubject.period (period)​is equivalent toResearchSubject.periodElement `ResearchSubject.period` is mapped to FHIR R4B element `ResearchSubject.period` as `Equivalent`.
ResearchSubject.study (study)​is equivalent toResearchSubject.studyElement `ResearchSubject.study` is mapped to FHIR R4B element `ResearchSubject.study` as `Equivalent`.
ResearchSubject.subject (subject)​maps to wider conceptResearchSubject.individualElement `ResearchSubject.subject` is mapped to FHIR R4B element `ResearchSubject.individual` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `ResearchSubject.subject` with unmapped reference targets: BiologicallyDerivedProduct, Device, Group, Medication, Specimen, Substance.
ResearchSubject.assignedComparisonGroup (assignedComparisonGroup)​narrowerResearchSubject.assignedArmElement `ResearchSubject.assignedComparisonGroup` is mapped to FHIR R4B element `ResearchSubject.assignedArm` as `SourceIsNarrowerThanTarget`. Maybe this is really PlanDefinition.
ResearchSubject.actualComparisonGroup (actualComparisonGroup)​narrowerResearchSubject.actualArmElement `ResearchSubject.actualComparisonGroup` is mapped to FHIR R4B element `ResearchSubject.actualArm` as `SourceIsNarrowerThanTarget`.
ResearchSubject.consent (consent)​is equivalent toResearchSubject.consentElement `ResearchSubject.consent` is mapped to FHIR R4B element `ResearchSubject.consent` as `SourceIsBroaderThanTarget`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ResearchSubject|5.0.0 to R5: draft | active | retired | unknown additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ResearchSubject.status (status)​is equivalent toExtension (R5: draft | active | retired | unknown additional codes)Element `ResearchSubject.status` is mapped to FHIR R4B element `ResearchSubject.status` as `RelatedTo`. The mappings for `ResearchSubject.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `ResearchSubject.status` is a modifier element, so this extension does not need to be defined as a modifier.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ResearchSubject|5.0.0 to R5: Subject status (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ResearchSubject.progress (progress)​maps to wider conceptExtension (R5: Subject status (new))Element `ResearchSubject.progress` has a context of ResearchSubject based on following the parent source element upwards and mapping to `ResearchSubject`. Element `ResearchSubject.progress` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). This is intended to deal with the confusion routinely created by haing two conflated concepts of being in a particular state and having achieved a particular milestone. In strict terms a milestone is a point of time event that results in a change from one state to another. The state before the milestone is achieved is often given the same name as the milestone, and sometimes the state may have the same description. For instance "Randomised" and "Visit 1" may be different milestones but the state remains at "on study" after each of them. It is likely that more than one "state" pattern will be recorded for a subject and a type has been introduced to allow this simultaneous recording.
ResearchSubject.progress.type (type)​maps to wider conceptExtension.extension:type (R5: state | milestone (new))Element `ResearchSubject.progress.type` is part of an existing definition because parent element `ResearchSubject.progress` requires a cross-version extension. Element `ResearchSubject.progress.type` has a context of ResearchSubject based on following the parent source element upwards and mapping to `ResearchSubject`. Element `ResearchSubject.progress.type` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ResearchSubject.progress.subjectState (subjectState)​maps to wider conceptExtension.extension:subjectState (R5: candidate | eligible | follow-up | ineligible | not-registered | off-study | on-study | on-study-intervention | on-study-observation | pending-on-study | potential-candidate | screening | withdrawn (new))Element `ResearchSubject.progress.subjectState` is part of an existing definition because parent element `ResearchSubject.progress` requires a cross-version extension. Element `ResearchSubject.progress.subjectState` has a context of ResearchSubject based on following the parent source element upwards and mapping to `ResearchSubject`. Element `ResearchSubject.progress.subjectState` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ResearchSubject.progress.milestone (milestone)​maps to wider conceptExtension.extension:milestone (R5: SignedUp | Screened | Randomized (new))Element `ResearchSubject.progress.milestone` is part of an existing definition because parent element `ResearchSubject.progress` requires a cross-version extension. Element `ResearchSubject.progress.milestone` has a context of ResearchSubject based on following the parent source element upwards and mapping to `ResearchSubject`. Element `ResearchSubject.progress.milestone` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). There can be multiple entries but it is also valid to just have the most recent. This should npt be rlied upon as the full path the subject has taken.
ResearchSubject.progress.reason (reason)​maps to wider conceptExtension.extension:reason (R5: State change reason (new))Element `ResearchSubject.progress.reason` is part of an existing definition because parent element `ResearchSubject.progress` requires a cross-version extension. Element `ResearchSubject.progress.reason` has a context of ResearchSubject based on following the parent source element upwards and mapping to `ResearchSubject`. Element `ResearchSubject.progress.reason` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ResearchSubject.progress.startDate (startDate)​maps to wider conceptExtension.extension:startDate (R5: State change date (new))Element `ResearchSubject.progress.startDate` is part of an existing definition because parent element `ResearchSubject.progress` requires a cross-version extension. Element `ResearchSubject.progress.startDate` has a context of ResearchSubject based on following the parent source element upwards and mapping to `ResearchSubject`. Element `ResearchSubject.progress.startDate` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). This is NOT the date the change in state was recorded.
ResearchSubject.progress.endDate (endDate)​maps to wider conceptExtension.extension:endDate (R5: State change date (new))Element `ResearchSubject.progress.endDate` is part of an existing definition because parent element `ResearchSubject.progress` requires a cross-version extension. Element `ResearchSubject.progress.endDate` has a context of ResearchSubject based on following the parent source element upwards and mapping to `ResearchSubject`. Element `ResearchSubject.progress.endDate` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).