R5-ServiceRequest-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-ServiceRequest-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-ServiceRequest-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to ServiceRequestversion: 4.0.1) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 Codes from ServiceRequest ServiceRequest.meta meta is equivalent to ServiceRequest.meta ServiceRequest.meta Element `ServiceRequest.meta` is mapped to FHIR R4 element `ServiceRequest.meta` as `Equivalent`. ServiceRequest.implicitRules implicitRules is equivalent to ServiceRequest.implicitRules ServiceRequest.implicitRules Element `ServiceRequest.implicitRules` is mapped to FHIR R4 element `ServiceRequest.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. ServiceRequest.language language is equivalent to ServiceRequest.language ServiceRequest.language Element `ServiceRequest.language` is mapped to FHIR R4 element `ServiceRequest.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 Re…
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-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
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-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-ServiceRequest-element-map-to-R4
  l: R5-ServiceRequest-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5ServiceRequestElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 ServiceRequest to FHIR R4 ServiceRequest
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:48.137913-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 R5 ServiceRequest to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ServiceRequest
    l: ServiceRequest
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/ServiceRequest
    l: ServiceRequest
  target version:
    v: 4.0.1
  element:
    code:
      v: ServiceRequest.meta
    display:
      v: meta
    target:
      code:
        v: ServiceRequest.meta
      display:
        v: ServiceRequest.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `ServiceRequest.meta` is mapped to FHIR R4 element `ServiceRequest.meta` as `Equivalent`.
  element:
    code:
      v: ServiceRequest.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: ServiceRequest.implicitRules
      display:
        v: ServiceRequest.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `ServiceRequest.implicitRules` is mapped to FHIR R4 element `ServiceRequest.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.
  element:
    code:
      v: ServiceRequest.language
    display:
      v: language
    target:
      code:
        v: ServiceRequest.language
      display:
        v: ServiceRequest.language
      equivalence:
        v: equivalent
      comment:
        v: Element `ServiceRequest.language` is mapped to FHIR R4 element `ServiceRequest.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: ServiceRequest.text
    display:
      v: text
    target:
      code:
        v: ServiceRequest.text
      display:
        v: ServiceRequest.text
      equivalence:
        v: equivalent
      comment:
        v: Element `ServiceRequest.text` is mapped to FHIR R4 element `ServiceRequest.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.
  element:
    code:
      v: ServiceRequest.contained
    display:
      v: contained
    target:
      code:
        v: ServiceRequest.contained
      display:
        v: ServiceRequest.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `ServiceRequest.contained` is mapped to FHIR R4 element `ServiceRequest.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.
  element:
    code:
      v: ServiceRequest.identifier
    display:
      v: identifier
    target:
      code:
        v: ServiceRequest.identifier
      display:
        v: ServiceRequest.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element `ServiceRequest.identifier` is mapped to FHIR R4 element `ServiceRequest.identifier` as `Equivalent`. The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 V2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 V2). For further discussion and examples see the resource notes section below.
  element:
    code:
      v: ServiceRequest.instantiatesCanonical
    display:
      v: instantiatesCanonical
    target:
      code:
        v: ServiceRequest.instantiatesCanonical
      display:
        v: ServiceRequest.instantiatesCanonical
      equivalence:
        v: equivalent
      comment:
        v: Element `ServiceRequest.instantiatesCanonical` is mapped to FHIR R4 element `ServiceRequest.instantiatesCanonical` as `Equivalent`. The PlanDefinition resource is used to describe series, sequences, or groups of actions to be taken, while the ActivityDefinition resource is used to define each specific step or activity to be performed. More information can be found in the [Boundaries and Relationships](https://hl7.org/fhir/plandefi.html#12.23.2) section for PlanDefinition.
  element:
    code:
      v: ServiceRequest.instantiatesUri
    display:
      v: instantiatesUri
    target:
      code:
        v: ServiceRequest.instantiatesUri
      display:
        v: ServiceRequest.instantiatesUri
      equivalence:
        v: equivalent
      comment:
        v: Element `ServiceRequest.instantiatesUri` is mapped to FHIR R4 element `ServiceRequest.instantiatesUri` as `Equivalent`. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

code:
  v: ServiceRequest.basedOn
display:
  v: basedOn
target:
  code:
    v: ServiceRequest.basedOn
  display:
    v: ServiceRequest.basedOn
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.basedOn` is mapped to FHIR R4 element `ServiceRequest.basedOn` as `Equivalent`.

code:
  v: ServiceRequest.replaces
display:
  v: replaces
target:
  code:
    v: ServiceRequest.replaces
  display:
    v: ServiceRequest.replaces
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.replaces` is mapped to FHIR R4 element `ServiceRequest.replaces` as `Equivalent`.

code:
  v: ServiceRequest.requisition
display:
  v: requisition
target:
  code:
    v: ServiceRequest.requisition
  display:
    v: ServiceRequest.requisition
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.requisition` is mapped to FHIR R4 element `ServiceRequest.requisition` as `Equivalent`. Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

code:
  v: ServiceRequest.status
display:
  v: status
target:
  code:
    v: ServiceRequest.status
  display:
    v: ServiceRequest.status
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.status` is mapped to FHIR R4 element `ServiceRequest.status` as `Equivalent`. The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, revoked or placed on-hold. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](https://hl7.org/fhir/event.html) for general discussion) or using the [Task](https://hl7.org/fhir/task.html) resource.

code:
  v: ServiceRequest.intent
display:
  v: intent
target:
  code:
    v: ServiceRequest.intent
  display:
    v: ServiceRequest.intent
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.intent` is mapped to FHIR R4 element `ServiceRequest.intent` as `Equivalent`. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

code:
  v: ServiceRequest.category
display:
  v: category
target:
  code:
    v: ServiceRequest.category
  display:
    v: ServiceRequest.category
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.category` is mapped to FHIR R4 element `ServiceRequest.category` as `Equivalent`. There may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource. The level of granularity is defined by the category concepts in the value set.

code:
  v: ServiceRequest.priority
display:
  v: priority
target:
  code:
    v: ServiceRequest.priority
  display:
    v: ServiceRequest.priority
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.priority` is mapped to FHIR R4 element `ServiceRequest.priority` as `Equivalent`.

code:
  v: ServiceRequest.doNotPerform
display:
  v: doNotPerform
target:
  code:
    v: ServiceRequest.doNotPerform
  display:
    v: ServiceRequest.doNotPerform
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.doNotPerform` is mapped to FHIR R4 element `ServiceRequest.doNotPerform` as `Equivalent`. In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation.

code:
  v: ServiceRequest.code
display:
  v: code
target:
  code:
    v: ServiceRequest.code
  display:
    v: ServiceRequest.code
  equivalence:
    v: wider
  comment:
    v: Element `ServiceRequest.code` is mapped to FHIR R4 element `ServiceRequest.code` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.code` do not cover the following types: CodeableReference. The mappings for `ServiceRequest.code` do not cover the following types based on type expansion: reference. Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code.

code:
  v: ServiceRequest.orderDetail
display:
  v: orderDetail
target:
  code:
    v: ServiceRequest.orderDetail
  display:
    v: ServiceRequest.orderDetail
  equivalence:
    v: wider
  comment:
    v: Element `ServiceRequest.orderDetail` is mapped to FHIR R4 element `ServiceRequest.orderDetail` as `Equivalent`. For information from the medical record intended to support the delivery of the requested services, use the `supportingInformation` element.

code:
  v: ServiceRequest.quantity[x]
display:
  v: quantity[x]
target:
  code:
    v: ServiceRequest.quantity[x]
  display:
    v: ServiceRequest.quantity[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.quantity[x]` is mapped to FHIR R4 element `ServiceRequest.quantity[x]` as `Equivalent`. The target context `ServiceRequest.quantity[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ServiceRequest`.

code:
  v: ServiceRequest.subject
display:
  v: subject
target:
  code:
    v: ServiceRequest.subject
  display:
    v: ServiceRequest.subject
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.subject` is mapped to FHIR R4 element `ServiceRequest.subject` as `Equivalent`.

code:
  v: ServiceRequest.encounter
display:
  v: encounter
target:
  code:
    v: ServiceRequest.encounter
  display:
    v: ServiceRequest.encounter
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.encounter` is mapped to FHIR R4 element `ServiceRequest.encounter` as `Equivalent`.

code:
  v: ServiceRequest.occurrence[x]
display:
  v: occurrence[x]
target:
  code:
    v: ServiceRequest.occurrence[x]
  display:
    v: ServiceRequest.occurrence[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.occurrence[x]` is mapped to FHIR R4 element `ServiceRequest.occurrence[x]` as `Equivalent`. The target context `ServiceRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ServiceRequest`.

code:
  v: ServiceRequest.asNeeded[x]
display:
  v: asNeeded[x]
target:
  code:
    v: ServiceRequest.asNeeded[x]
  display:
    v: ServiceRequest.asNeeded[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.asNeeded[x]` is mapped to FHIR R4 element `ServiceRequest.asNeeded[x]` as `Equivalent`. The target context `ServiceRequest.asNeeded[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ServiceRequest`.

code:
  v: ServiceRequest.authoredOn
display:
  v: authoredOn
target:
  code:
    v: ServiceRequest.authoredOn
  display:
    v: ServiceRequest.authoredOn
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.authoredOn` is mapped to FHIR R4 element `ServiceRequest.authoredOn` as `Equivalent`.

code:
  v: ServiceRequest.requester
display:
  v: requester
target:
  code:
    v: ServiceRequest.requester
  display:
    v: ServiceRequest.requester
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.requester` is mapped to FHIR R4 element `ServiceRequest.requester` as `Equivalent`. This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource.

code:
  v: ServiceRequest.performerType
display:
  v: performerType
target:
  code:
    v: ServiceRequest.performerType
  display:
    v: ServiceRequest.performerType
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.performerType` is mapped to FHIR R4 element `ServiceRequest.performerType` as `Equivalent`. This is a role, not a participation type. In other words, does not describe the task but describes the capacity. For example, “compounding pharmacy”, “psychiatrist” or “internal referral”.

code:
  v: ServiceRequest.performer
display:
  v: performer
target:
  code:
    v: ServiceRequest.performer
  display:
    v: ServiceRequest.performer
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.performer` is mapped to FHIR R4 element `ServiceRequest.performer` as `Equivalent`. If multiple performers are present, it is interpreted as a list of *alternative* performers without any preference regardless of order. If order of preference is needed use the [http://hl7.org/fhir/StructureDefinition/request-performerOrder](http://hl7.org/fhir/extensions/StructureDefinition-request-performerOrder.html). Use CareTeam to represent a group of performers (for example, Practitioner A *and* Practitioner B).

code:
  v: ServiceRequest.location
display:
  v: location
target:
  code:
    v: ServiceRequest.locationCode
  display:
    v: ServiceRequest.locationCode
  equivalence:
    v: relatedto
  comment:
    v: Element `ServiceRequest.location` is mapped to FHIR R4 element `ServiceRequest.locationCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.location` is mapped to FHIR R4 element `ServiceRequest.locationReference` as `SourceIsBroaderThanTarget`.
target:
  code:
    v: ServiceRequest.locationReference
  display:
    v: ServiceRequest.locationReference
  equivalence:
    v: relatedto
  comment:
    v: Element `ServiceRequest.location` is mapped to FHIR R4 element `ServiceRequest.locationCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.location` is mapped to FHIR R4 element `ServiceRequest.locationReference` as `SourceIsBroaderThanTarget`.

code:
  v: ServiceRequest.reason
display:
  v: reason
target:
  code:
    v: ServiceRequest.reasonCode
  display:
    v: ServiceRequest.reasonCode
  equivalence:
    v: relatedto
  comment:
    v: Element `ServiceRequest.reason` is mapped to FHIR R4 element `ServiceRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR R4 element `ServiceRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.reason` do not cover the following types: CodeableReference. This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to *Observation* or *Condition* should be used if available. Otherwise, use `concept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](https://hl7.org/fhir/servicerequest-example-di.html).
target:
  code:
    v: ServiceRequest.reasonReference
  display:
    v: ServiceRequest.reasonReference
  equivalence:
    v: relatedto
  comment:
    v: Element `ServiceRequest.reason` is mapped to FHIR R4 element `ServiceRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR R4 element `ServiceRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.reason` do not cover the following types: CodeableReference. This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to *Observation* or *Condition* should be used if available. Otherwise, use `concept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](https://hl7.org/fhir/servicerequest-example-di.html).

code:
  v: ServiceRequest.insurance
display:
  v: insurance
target:
  code:
    v: ServiceRequest.insurance
  display:
    v: ServiceRequest.insurance
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.insurance` is mapped to FHIR R4 element `ServiceRequest.insurance` as `Equivalent`.

code:
  v: ServiceRequest.supportingInfo
display:
  v: supportingInfo
target:
  code:
    v: ServiceRequest.supportingInfo
  display:
    v: ServiceRequest.supportingInfo
  equivalence:
    v: wider
  comment:
    v: Element `ServiceRequest.supportingInfo` is mapped to FHIR R4 element `ServiceRequest.supportingInfo` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.supportingInfo` do not cover the following types: CodeableReference. The mappings for `ServiceRequest.supportingInfo` do not cover the following types based on type expansion: concept. To represent information about how the services are to be delivered use the `instructions` element.

code:
  v: ServiceRequest.specimen
display:
  v: specimen
target:
  code:
    v: ServiceRequest.specimen
  display:
    v: ServiceRequest.specimen
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.specimen` is mapped to FHIR R4 element `ServiceRequest.specimen` as `Equivalent`. The purpose of the ServiceRequest.specimen is to reflect the actual specimen that the requested test/procedure is asked to be performed on, whether the lab already has it or not. References to specimens for purposes other than to perform a test/procedure on should be made using the ServiceRequest.supportingInfo or the Specimen.parent where the Specimen.parent would enable descendency and ServiceRequest.supportingInfo a general reference for context.

code:
  v: ServiceRequest.bodySite
display:
  v: bodySite
target:
  code:
    v: ServiceRequest.bodySite
  display:
    v: ServiceRequest.bodySite
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.bodySite` is mapped to FHIR R4 element `ServiceRequest.bodySite` as `Equivalent`. Only used if not implicit in the code found in ServiceRequest.code. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension [http://hl7.org/fhir/StructureDefinition/procedure-targetBodyStructure](http://hl7.org/fhir/extensions/StructureDefinition-procedure-targetBodyStructure.html).

code:
  v: ServiceRequest.note
display:
  v: note
target:
  code:
    v: ServiceRequest.note
  display:
    v: ServiceRequest.note
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.note` is mapped to FHIR R4 element `ServiceRequest.note` as `Equivalent`.

code:
  v: ServiceRequest.patientInstruction
display:
  v: patientInstruction
target:
  code:
    v: ServiceRequest.patientInstruction
  display:
    v: ServiceRequest.patientInstruction
  equivalence:
    v: wider
  comment:
    v: Element `ServiceRequest.patientInstruction` is mapped to FHIR R4 element `ServiceRequest.patientInstruction` as `SourceIsBroaderThanTarget`.

code:
  v: ServiceRequest.relevantHistory
display:
  v: relevantHistory
target:
  code:
    v: ServiceRequest.relevantHistory
  display:
    v: ServiceRequest.relevantHistory
  equivalence:
    v: equivalent
  comment:
    v: Element `ServiceRequest.relevantHistory` is mapped to FHIR R4 element `ServiceRequest.relevantHistory` as `Equivalent`. This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceRequest
  l: ServiceRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ServiceRequest.code
  l: extension-ServiceRequest.code
target version:
  v: 0.1.0
element:
  code:
    v: ServiceRequest.code
  display:
    v: code
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `ServiceRequest.code` is mapped to FHIR R4 element `ServiceRequest.code` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.code` do not cover the following types: CodeableReference. The mappings for `ServiceRequest.code` do not cover the following types based on type expansion: reference. Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceRequest
  l: ServiceRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ServiceRequest.orderDetail.parameterFocus
  l: extension-ServiceRequest.orderDetail.parameterFocus
target version:
  v: 0.1.0
element:
  code:
    v: ServiceRequest.orderDetail.parameterFocus
  display:
    v: parameterFocus
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceRequest.orderDetail.parameterFocus` has a context of ServiceRequest.orderDetail based on following the parent source element upwards and mapping to `ServiceRequest`. Element `ServiceRequest.orderDetail.parameterFocus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceRequest
  l: ServiceRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ServiceRequest.orderDetail.parameter
  l: extension-ServiceRequest.orderDetail.parameter
target version:
  v: 0.1.0
element:
  code:
    v: ServiceRequest.orderDetail.parameter
  display:
    v: parameter
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceRequest.orderDetail.parameter` has a context of ServiceRequest.orderDetail based on following the parent source element upwards and mapping to `ServiceRequest`. Element `ServiceRequest.orderDetail.parameter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ServiceRequest.orderDetail.parameter.code
  display:
    v: code
  target:
    code:
      v: Extension.extension:code
    equivalence:
      v: wider
    comment:
      v: Element `ServiceRequest.orderDetail.parameter.code` is part of an existing definition because parent element `ServiceRequest.orderDetail.parameter` requires a cross-version extension. Element `ServiceRequest.orderDetail.parameter.code` has a context of ServiceRequest.orderDetail based on following the parent source element upwards and mapping to `ServiceRequest`. Element `ServiceRequest.orderDetail.parameter.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ServiceRequest.orderDetail.parameter.value[x]
  display:
    v: value[x]
  target:
    code:
      v: Extension.extension:value
    equivalence:
      v: wider
    comment:
      v: Element `ServiceRequest.orderDetail.parameter.value[x]` is part of an existing definition because parent element `ServiceRequest.orderDetail.parameter` requires a cross-version extension. Element `ServiceRequest.orderDetail.parameter.value[x]` has a context of ServiceRequest.orderDetail based on following the parent source element upwards and mapping to `ServiceRequest`. Element `ServiceRequest.orderDetail.parameter.value[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). CodeableConcept values are indented to express concepts that would normally be coded - when a code is not available for a concept, CodeableConcept.text can be used. When the data is a text or not a single identifiable concept, string should be used.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceRequest
  l: ServiceRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ServiceRequest.focus
  l: extension-ServiceRequest.focus
target version:
  v: 0.1.0
element:
  code:
    v: ServiceRequest.focus
  display:
    v: focus
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceRequest.focus` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`. Element `ServiceRequest.focus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceRequest
  l: ServiceRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ServiceRequest.reason
  l: extension-ServiceRequest.reason
target version:
  v: 0.1.0
element:
  code:
    v: ServiceRequest.reason
  display:
    v: reason
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceRequest.reason` is mapped to FHIR R4 element `ServiceRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR R4 element `ServiceRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.reason` do not cover the following types: CodeableReference. This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to *Observation* or *Condition* should be used if available. Otherwise, use `concept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](https://hl7.org/fhir/servicerequest-example-di.html).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceRequest
  l: ServiceRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ServiceRequest.supportingInfo
  l: extension-ServiceRequest.supportingInfo
target version:
  v: 0.1.0
element:
  code:
    v: ServiceRequest.supportingInfo
  display:
    v: supportingInfo
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `ServiceRequest.supportingInfo` is mapped to FHIR R4 element `ServiceRequest.supportingInfo` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.supportingInfo` do not cover the following types: CodeableReference. The mappings for `ServiceRequest.supportingInfo` do not cover the following types based on type expansion: concept. To represent information about how the services are to be delivered use the `instructions` element.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceRequest
  l: ServiceRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ServiceRequest.patientInstruction.instruction
  l: extension-ServiceRequest.patientInstruction.instruction
target version:
  v: 0.1.0
element:
  code:
    v: ServiceRequest.patientInstruction.instruction[x]
  display:
    v: instruction[x]
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceRequest.patientInstruction.instruction[x]` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`. Element `ServiceRequest.patientInstruction.instruction[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).