R4BServiceRequestElementMapToR3 - Extensions for Using Data Elements from FHIR R4B in FHIR STU3 v0.1.0

ProcedureRequest.meta

Element `ServiceRequest.meta` is mapped to FHIR STU3 element `ProcedureRequest.meta` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.meta` is mapped to FHIR STU3 element `ReferralRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.meta` do not cover the following types: Meta. The mappings for `ServiceRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, source, tag, versionId.

ServiceRequest.implicitRules

implicitRules

ProcedureRequest.implicitRules

Element `ServiceRequest.implicitRules` is mapped to FHIR STU3 element `ProcedureRequest.implicitRules` as `Equivalent`. Element `ServiceRequest.implicitRules` is mapped to FHIR STU3 element `ReferralRequest.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.

ServiceRequest.language

language

ProcedureRequest.language

Element `ServiceRequest.language` is mapped to FHIR STU3 element `ProcedureRequest.language` as `Equivalent`. Element `ServiceRequest.language` is mapped to FHIR STU3 element `ReferralRequest.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).

ServiceRequest.text

text

ProcedureRequest.text

Element `ServiceRequest.text` is mapped to FHIR STU3 element `ProcedureRequest.text` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.text` is mapped to FHIR STU3 element `ReferralRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.text` do not cover the following types: Narrative. The mappings for `ServiceRequest.text` do not cover the following types based on type expansion: div, status. 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.

ServiceRequest.contained

contained

ProcedureRequest.contained

Element `ServiceRequest.contained` is mapped to FHIR STU3 element `ProcedureRequest.contained` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.contained` is mapped to FHIR STU3 element `ReferralRequest.contained` as `SourceIsBroaderThanTarget`. 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.

ServiceRequest.identifier

identifier

ProcedureRequest.identifier

Element `ServiceRequest.identifier` is mapped to FHIR STU3 element `ProcedureRequest.identifier` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.identifier` is mapped to FHIR STU3 element `ReferralRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.identifier` do not cover the following types: Identifier. The mappings for `ServiceRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. 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.

ServiceRequest.instantiatesCanonical

instantiatesCanonical

ProcedureRequest.definition

Element `ServiceRequest.instantiatesCanonical` is mapped to FHIR STU3 element `ProcedureRequest.definition` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.instantiatesCanonical` is mapped to FHIR STU3 element `ReferralRequest.definition` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.instantiatesCanonical` do not cover the following types: canonical. The mappings for `ServiceRequest.instantiatesCanonical` do not cover the following types based on type expansion: value. Note: This is a business identifier, not a resource identifier (see [discussion](https://hl7.org/fhir/resource.htm#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

ServiceRequest.basedOn

basedOn

ProcedureRequest.basedOn

Element `ServiceRequest.basedOn` is mapped to FHIR STU3 element `ProcedureRequest.basedOn` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.basedOn` is mapped to FHIR STU3 element `ReferralRequest.basedOn` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `ServiceRequest.basedOn` with unmapped reference targets: CarePlan, MedicationRequest, ServiceRequest.

ServiceRequest.replaces

replaces

ProcedureRequest.replaces

Element `ServiceRequest.replaces` is mapped to FHIR STU3 element `ProcedureRequest.replaces` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.replaces` is mapped to FHIR STU3 element `ReferralRequest.replaces` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.replaces` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `ServiceRequest.replaces` with unmapped reference targets: ServiceRequest.

ServiceRequest.requisition

requisition

ProcedureRequest.requisition

Element `ServiceRequest.requisition` is mapped to FHIR STU3 element `ProcedureRequest.requisition` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.requisition` is mapped to FHIR STU3 element `ReferralRequest.groupIdentifier` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.requisition` do not cover the following types: Identifier. The mappings for `ServiceRequest.requisition` do not cover the following types based on type expansion: assigner, period, system, type, use, value. 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.

ServiceRequest.status

status

ProcedureRequest.status

Element `ServiceRequest.status` is mapped to FHIR STU3 element `ProcedureRequest.status` as `Equivalent`. Element `ServiceRequest.status` is mapped to FHIR STU3 element `ReferralRequest.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, cancelled or suspended. 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.

ServiceRequest.intent

intent

ProcedureRequest.intent

Element `ServiceRequest.intent` is mapped to FHIR STU3 element `ProcedureRequest.intent` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.intent` is mapped to FHIR STU3 element `ReferralRequest.intent` as `SourceIsBroaderThanTarget`. The target context `ProcedureRequest.intent` is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

ServiceRequest.category

category

ProcedureRequest.category

Element `ServiceRequest.category` is mapped to FHIR STU3 element `ProcedureRequest.category` as `Equivalent`. Element `ServiceRequest.category` is mapped to FHIR STU3 element `ReferralRequest.type` as `SourceIsBroaderThanTarget`. 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.

ServiceRequest.priority

priority

ProcedureRequest.priority

Element `ServiceRequest.priority` is mapped to FHIR STU3 element `ProcedureRequest.priority` as `Equivalent`. Element `ServiceRequest.priority` is mapped to FHIR STU3 element `ReferralRequest.priority` as `Equivalent`.

ServiceRequest.doNotPerform

doNotPerform

ProcedureRequest.doNotPerform

Element `ServiceRequest.doNotPerform` is mapped to FHIR STU3 element `ProcedureRequest.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.

ServiceRequest.code

code

ProcedureRequest.code

Element `ServiceRequest.code` is mapped to FHIR STU3 element `ProcedureRequest.code` as `Equivalent`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.type` as `Equivalent`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.serviceRequested` as `SourceIsNarrowerThanTarget`. 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.

ServiceRequest.subject

subject

ProcedureRequest.subject

Element `ServiceRequest.subject` is mapped to FHIR STU3 element `ProcedureRequest.subject` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.subject` is mapped to FHIR STU3 element `ReferralRequest.subject` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `ServiceRequest.subject` with unmapped reference targets: Device, Group, Location, Patient.

ServiceRequest.encounter

encounter

ProcedureRequest.context

Element `ServiceRequest.encounter` is mapped to FHIR STU3 element `ProcedureRequest.context` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.encounter` is mapped to FHIR STU3 element `ReferralRequest.context` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.encounter` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `ServiceRequest.encounter` with unmapped reference targets: Encounter.

ServiceRequest.occurrence[x]

occurrence[x]

ProcedureRequest.occurrence[x]

Element `ServiceRequest.occurrence[x]` is mapped to FHIR STU3 element `ProcedureRequest.occurrence[x]` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.occurrence[x]` is mapped to FHIR STU3 element `ReferralRequest.occurrence[x]` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.occurrence[x]` do not cover the following types: Period, Timing. The target context `ProcedureRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ProcedureRequest`. The target context `ReferralRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ReferralRequest`.

ServiceRequest.asNeeded[x]

asNeeded[x]

ProcedureRequest.asNeeded[x]

Element `ServiceRequest.asNeeded[x]` is mapped to FHIR STU3 element `ProcedureRequest.asNeeded[x]` as `Equivalent`. The target context `ProcedureRequest.asNeeded[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ProcedureRequest`.

ServiceRequest.authoredOn

authoredOn

ProcedureRequest.authoredOn

Element `ServiceRequest.authoredOn` is mapped to FHIR STU3 element `ProcedureRequest.authoredOn` as `Equivalent`. Element `ServiceRequest.authoredOn` is mapped to FHIR STU3 element `ReferralRequest.authoredOn` as `Equivalent`.

ServiceRequest.requester

requester

ProcedureRequest.requester

Element `ServiceRequest.requester` is mapped to FHIR STU3 element `ProcedureRequest.requester` as `Equivalent`. Element `ServiceRequest.requester` is mapped to FHIR STU3 element `ProcedureRequest.requester.agent` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.requester` is mapped to FHIR STU3 element `ReferralRequest.requester` as `Equivalent`. Element `ServiceRequest.requester` is mapped to FHIR STU3 element `ReferralRequest.requester.agent` as `SourceIsBroaderThanTarget`. 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.

ProcedureRequest.requester.agent

ServiceRequest.performerType

performerType

ProcedureRequest.performerType

Element `ServiceRequest.performerType` is mapped to FHIR STU3 element `ProcedureRequest.performerType` as `Equivalent`. Element `ServiceRequest.performerType` is mapped to FHIR STU3 element `ReferralRequest.specialty` 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”.

ServiceRequest.performer

performer

ProcedureRequest.performer

Element `ServiceRequest.performer` is mapped to FHIR STU3 element `ProcedureRequest.performer` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.performer` is mapped to FHIR STU3 element `ReferralRequest.recipient` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `ServiceRequest.performer` with unmapped reference targets: CareTeam, Device, HealthcareService, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson. 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 [request-performerOrder extension](https://hl7.org/fhir/extension-request-performerorder.html). Use CareTeam to represent a group of performers (for example, Practitioner A *and* Practitioner B).

ServiceRequest.reasonCode

reasonCode

ProcedureRequest.reasonCode

Element `ServiceRequest.reasonCode` is mapped to FHIR STU3 element `ProcedureRequest.reasonCode` as `Equivalent`. Element `ServiceRequest.reasonCode` is mapped to FHIR STU3 element `ReferralRequest.reasonCode` as `Equivalent`. 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. Use `CodeableConcept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](https://hl7.org/fhir/servicerequest-example-di.html).

ServiceRequest.reasonReference

reasonReference

ProcedureRequest.reasonReference

Element `ServiceRequest.reasonReference` is mapped to FHIR STU3 element `ProcedureRequest.reasonReference` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reasonReference` is mapped to FHIR STU3 element `ReferralRequest.reasonReference` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `ServiceRequest.reasonReference` with unmapped reference targets: Condition, DiagnosticReport, DocumentReference, Observation. 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 when referencing *DiagnosticReport* it should contain a finding in `DiagnosticReport.conclusion` and/or `DiagnosticReport.conclusionCode`. When using a reference to *DocumentReference*, the target document should contain clear findings language providing the relevant reason for this service request. Use the CodeableConcept text element in `ServiceRequest.reasonCode` if the data is free (uncoded) text as shown in the [CT Scan example](https://hl7.org/fhir/servicerequest-example-di.html).

ServiceRequest.supportingInfo

supportingInfo

ProcedureRequest.supportingInfo

Element `ServiceRequest.supportingInfo` is mapped to FHIR STU3 element `ProcedureRequest.supportingInfo` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.supportingInfo` is mapped to FHIR STU3 element `ReferralRequest.supportingInfo` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.supportingInfo` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `ServiceRequest.supportingInfo` with unmapped reference targets: Resource. To represent information about how the services are to be delivered use the `instructions` element.

ServiceRequest.specimen

specimen

ProcedureRequest.specimen

Element `ServiceRequest.specimen` is mapped to FHIR STU3 element `ProcedureRequest.specimen` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.specimen` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `ServiceRequest.specimen` with unmapped reference targets: Specimen. Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the [Specimen](https://hl7.org/fhir/specimen.html) resource points to the ServiceRequest.

ServiceRequest.bodySite

bodySite

ProcedureRequest.bodySite

Element `ServiceRequest.bodySite` is mapped to FHIR STU3 element `ProcedureRequest.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 [procedure-targetBodyStructure](https://hl7.org/fhir/extension-procedure-targetbodystructure.html).

ServiceRequest.note

note

ProcedureRequest.note

Element `ServiceRequest.note` is mapped to FHIR STU3 element `ProcedureRequest.note` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.note` is mapped to FHIR STU3 element `ReferralRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.note` do not cover the following types: Annotation. The mappings for `ServiceRequest.note` do not cover the following types based on type expansion: author[x], text, time.

ServiceRequest.relevantHistory

relevantHistory

ProcedureRequest.relevantHistory

Element `ServiceRequest.relevantHistory` is mapped to FHIR STU3 element `ProcedureRequest.relevantHistory` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.relevantHistory` is mapped to FHIR STU3 element `ReferralRequest.relevantHistory` as `SourceIsBroaderThanTarget`. The mappings for `ServiceRequest.relevantHistory` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `ServiceRequest.relevantHistory` with unmapped reference targets: Provenance. 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.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to http://hl7.org/fhir/StructureDefinition/ReferralRequest|3.0.2

Source Concept Details

Relationship

Target Concept Details

Comment

Codes from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0

Codes from http://hl7.org/fhir/StructureDefinition/ReferralRequest|3.0.2

ServiceRequest.meta

category

ReferralRequest.type

ServiceRequest.priority

priority

ReferralRequest.priority

ServiceRequest.code

code

ReferralRequest.serviceRequested

ReferralRequest.type

ServiceRequest.orderDetail

orderDetail

ReferralRequest.serviceRequested

Element `ServiceRequest.orderDetail` is mapped to FHIR STU3 element `ReferralRequest.serviceRequested` as `Equivalent`. For information from the medical record intended to support the delivery of the requested services, use the `supportingInformation` element.

ServiceRequest.subject

subject

ReferralRequest.subject

ServiceRequest.encounter

encounter

ReferralRequest.context

ServiceRequest.occurrence[x]

occurrence[x]

ReferralRequest.occurrence[x]

ServiceRequest.authoredOn

authoredOn

ReferralRequest.authoredOn

ServiceRequest.requester

requester

ReferralRequest.requester

ReferralRequest.requester.agent

ServiceRequest.performerType

performerType

ReferralRequest.specialty

ServiceRequest.performer

performer

ReferralRequest.recipient

ServiceRequest.reasonCode

reasonCode

ReferralRequest.reasonCode

ServiceRequest.reasonReference

reasonReference

ReferralRequest.reasonReference

ServiceRequest.supportingInfo

supportingInfo

ReferralRequest.supportingInfo

ServiceRequest.note

note

ReferralRequest.note

ServiceRequest.relevantHistory

relevantHistory

ReferralRequest.relevantHistory

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Metadata about the resource additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.meta (meta)

Extension (R4B: Metadata about the resource additional types)

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Text summary of the resource, for human interpretation additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.text (text)

Extension (R4B: Text summary of the resource, for human interpretation additional types)

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Identifiers assigned to this order additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.identifier (identifier)

Extension (R4B: Identifiers assigned to this order additional types)

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Instantiates FHIR protocol or definition additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.instantiatesCanonical (instantiatesCanonical)

Extension (R4B: Instantiates FHIR protocol or definition additional types)

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Instantiates external protocol or definition (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.instantiatesUri (instantiatesUri)

Extension (R4B: Instantiates external protocol or definition (new))

Element `ServiceRequest.instantiatesUri` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.instantiatesUri` has a context of ReferralRequest based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.instantiatesUri` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Composite Request ID additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.requisition (requisition)

Extension (R4B: Composite Request ID additional types)

Source Code

Relationship

Target Code

Comment

ServiceRequest.intent (intent)

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Service amount (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.quantity[x] (quantity[x])

Extension (R4B: Service amount (new))

Element `ServiceRequest.quantity[x]` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.quantity[x]` has a context of ReferralRequest based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.quantity[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: When service should occur additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.occurrence[x] (occurrence[x])

Extension (R4B: When service should occur additional types)

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Requested location (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.locationCode (locationCode)

Extension (R4B: Requested location (new))

Element `ServiceRequest.locationCode` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.locationCode` has a context of ReferralRequest based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.locationCode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Requested location (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.locationReference (locationReference)

Extension (R4B: Requested location (new))

Element `ServiceRequest.locationReference` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.locationReference` has a context of ReferralRequest based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.locationReference` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Associated insurance coverage (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.insurance (insurance)

Extension (R4B: Associated insurance coverage (new))

Element `ServiceRequest.insurance` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.insurance` has a context of ReferralRequest based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.insurance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Comments additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.note (note)

Extension (R4B: Comments additional types)

Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.3.0 to R4B: Patient or consumer-oriented instructions (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

ServiceRequest.patientInstruction (patientInstruction)