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

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

ConceptMap: R5ServiceRequestElementMapToR3

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

This ConceptMap represents cross-version mappings for elements from a FHIR R5 ServiceRequest to FHIR STU3.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0Codes from http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2
ServiceRequest.metameta​is equivalent toProcedureRequest.metaProcedureRequest.metaElement `ServiceRequest.meta` is mapped to FHIR STU3 element `ProcedureRequest.meta` as `Equivalent`. Element `ServiceRequest.meta` is mapped to FHIR STU3 element `ReferralRequest.meta` as `Equivalent`.
ServiceRequest.implicitRulesimplicitRules​is equivalent toProcedureRequest.implicitRulesProcedureRequest.implicitRulesElement `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 its narrative along with other profiles, value sets, etc.
ServiceRequest.languagelanguage​is equivalent toProcedureRequest.languageProcedureRequest.languageElement `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.texttext​is equivalent toProcedureRequest.textProcedureRequest.textElement `ServiceRequest.text` is mapped to FHIR STU3 element `ProcedureRequest.text` as `Equivalent`. Element `ServiceRequest.text` is mapped to FHIR STU3 element `ReferralRequest.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.
ServiceRequest.containedcontained​is related toProcedureRequest.containedProcedureRequest.containedElement `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.identifieridentifier​is equivalent toProcedureRequest.identifierProcedureRequest.identifierElement `ServiceRequest.identifier` is mapped to FHIR STU3 element `ProcedureRequest.identifier` as `Equivalent`. Element `ServiceRequest.identifier` is mapped to FHIR STU3 element `ReferralRequest.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.
ServiceRequest.instantiatesCanonicalinstantiatesCanonical​is related toProcedureRequest.definitionProcedureRequest.definitionElement `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. 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.
ServiceRequest.basedOnbasedOn​is related toProcedureRequest.basedOnProcedureRequest.basedOnElement `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 R5 element `ServiceRequest.basedOn` with unmapped reference targets: CarePlan, MedicationRequest, ServiceRequest.
ServiceRequest.replacesreplaces​is related toProcedureRequest.replacesProcedureRequest.replacesElement `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 R5 element `ServiceRequest.replaces` with unmapped reference targets: ServiceRequest.
ServiceRequest.requisitionrequisition​is equivalent toProcedureRequest.requisitionProcedureRequest.requisitionElement `ServiceRequest.requisition` is mapped to FHIR STU3 element `ProcedureRequest.requisition` as `Equivalent`. Element `ServiceRequest.requisition` is mapped to FHIR STU3 element `ReferralRequest.groupIdentifier` 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.
ServiceRequest.statusstatus​is equivalent toProcedureRequest.statusProcedureRequest.statusElement `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, 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.
ServiceRequest.intentintent​is related toProcedureRequest.intentProcedureRequest.intentElement `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.categorycategory​is equivalent toProcedureRequest.categoryProcedureRequest.categoryElement `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.prioritypriority​is equivalent toProcedureRequest.priorityProcedureRequest.priorityElement `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.doNotPerformdoNotPerform​is equivalent toProcedureRequest.doNotPerformProcedureRequest.doNotPerformElement `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.codecode​is related toProcedureRequest.codeProcedureRequest.codeElement `ServiceRequest.code` is mapped to FHIR STU3 element `ProcedureRequest.code` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.type` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.serviceRequested` as `RelatedTo`. 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.
ServiceRequest.subjectsubject​is related toProcedureRequest.subjectProcedureRequest.subjectElement `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 R5 element `ServiceRequest.subject` with unmapped reference targets: Device, Group, Location, Patient.
ServiceRequest.encounterencounter​is related toProcedureRequest.contextProcedureRequest.contextElement `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 R5 element `ServiceRequest.encounter` with unmapped reference targets: Encounter.
ServiceRequest.occurrence[x]occurrence[x]​is equivalent toProcedureRequest.occurrence[x]ProcedureRequest.occurrence[x]Element `ServiceRequest.occurrence[x]` is mapped to FHIR STU3 element `ProcedureRequest.occurrence[x]` as `Equivalent`. Element `ServiceRequest.occurrence[x]` is mapped to FHIR STU3 element `ReferralRequest.occurrence[x]` as `SourceIsBroaderThanTarget`. 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]​is equivalent toProcedureRequest.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.authoredOnauthoredOn​is equivalent toProcedureRequest.authoredOnProcedureRequest.authoredOnElement `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.requesterrequester​is equivalent toProcedureRequest.requesterProcedureRequest.requesterElement `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.
​is related toProcedureRequest.requester.agentProcedureRequest.requester.agentElement `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.
ServiceRequest.performerTypeperformerType​is equivalent toProcedureRequest.performerTypeProcedureRequest.performerTypeElement `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.performerperformer​is related toProcedureRequest.performerProcedureRequest.performerElement `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 R5 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 [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).
ServiceRequest.reasonreason​is related toProcedureRequest.reasonCodeProcedureRequest.reasonCodeElement `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonReference` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.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).
​is related toProcedureRequest.reasonReferenceProcedureRequest.reasonReferenceElement `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonReference` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.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).
ServiceRequest.supportingInfosupportingInfo​is related toProcedureRequest.supportingInfoProcedureRequest.supportingInfoElement `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: 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.
ServiceRequest.specimenspecimen​is related toProcedureRequest.specimenProcedureRequest.specimenElement `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 R5 element `ServiceRequest.specimen` with unmapped reference targets: Specimen. 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.
ServiceRequest.bodySitebodySite​is equivalent toProcedureRequest.bodySiteProcedureRequest.bodySiteElement `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 [http://hl7.org/fhir/StructureDefinition/procedure-targetBodyStructure](http://hl7.org/fhir/extensions/StructureDefinition-procedure-targetBodyStructure.html).
ServiceRequest.notenote​is equivalent toProcedureRequest.noteProcedureRequest.noteElement `ServiceRequest.note` is mapped to FHIR STU3 element `ProcedureRequest.note` as `Equivalent`. Element `ServiceRequest.note` is mapped to FHIR STU3 element `ReferralRequest.note` as `Equivalent`.
ServiceRequest.relevantHistoryrelevantHistory​is related toProcedureRequest.relevantHistoryProcedureRequest.relevantHistoryElement `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 R5 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|5.0.0 to http://hl7.org/fhir/StructureDefinition/ReferralRequest|3.0.2

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0Codes from http://hl7.org/fhir/StructureDefinition/ReferralRequest|3.0.2
ServiceRequest.metameta​is equivalent toReferralRequest.metaReferralRequest.metaElement `ServiceRequest.meta` is mapped to FHIR STU3 element `ProcedureRequest.meta` as `Equivalent`. Element `ServiceRequest.meta` is mapped to FHIR STU3 element `ReferralRequest.meta` as `Equivalent`.
ServiceRequest.implicitRulesimplicitRules​is equivalent toReferralRequest.implicitRulesReferralRequest.implicitRulesElement `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 its narrative along with other profiles, value sets, etc.
ServiceRequest.languagelanguage​is equivalent toReferralRequest.languageReferralRequest.languageElement `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.texttext​is equivalent toReferralRequest.textReferralRequest.textElement `ServiceRequest.text` is mapped to FHIR STU3 element `ProcedureRequest.text` as `Equivalent`. Element `ServiceRequest.text` is mapped to FHIR STU3 element `ReferralRequest.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.
ServiceRequest.containedcontained​is related toReferralRequest.containedReferralRequest.containedElement `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.identifieridentifier​is equivalent toReferralRequest.identifierReferralRequest.identifierElement `ServiceRequest.identifier` is mapped to FHIR STU3 element `ProcedureRequest.identifier` as `Equivalent`. Element `ServiceRequest.identifier` is mapped to FHIR STU3 element `ReferralRequest.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.
ServiceRequest.instantiatesCanonicalinstantiatesCanonical​is related toReferralRequest.definitionReferralRequest.definitionElement `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. 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.
ServiceRequest.basedOnbasedOn​is related toReferralRequest.basedOnReferralRequest.basedOnElement `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 R5 element `ServiceRequest.basedOn` with unmapped reference targets: CarePlan, MedicationRequest, ServiceRequest.
ServiceRequest.replacesreplaces​is related toReferralRequest.replacesReferralRequest.replacesElement `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 R5 element `ServiceRequest.replaces` with unmapped reference targets: ServiceRequest.
ServiceRequest.requisitionrequisition​is equivalent toReferralRequest.groupIdentifierReferralRequest.groupIdentifierElement `ServiceRequest.requisition` is mapped to FHIR STU3 element `ProcedureRequest.requisition` as `Equivalent`. Element `ServiceRequest.requisition` is mapped to FHIR STU3 element `ReferralRequest.groupIdentifier` 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.
ServiceRequest.statusstatus​is equivalent toReferralRequest.statusReferralRequest.statusElement `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, 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.
ServiceRequest.intentintent​is related toReferralRequest.intentReferralRequest.intentElement `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.categorycategory​is related toReferralRequest.typeReferralRequest.typeElement `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.prioritypriority​is equivalent toReferralRequest.priorityReferralRequest.priorityElement `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.codecode​is related toReferralRequest.serviceRequestedReferralRequest.serviceRequestedElement `ServiceRequest.code` is mapped to FHIR STU3 element `ProcedureRequest.code` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.type` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.serviceRequested` as `RelatedTo`. 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.
​is related toReferralRequest.typeReferralRequest.typeElement `ServiceRequest.code` is mapped to FHIR STU3 element `ProcedureRequest.code` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.type` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.serviceRequested` as `RelatedTo`. 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.
ServiceRequest.orderDetailorderDetail​is related toReferralRequest.serviceRequestedReferralRequest.serviceRequestedElement `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.subjectsubject​is related toReferralRequest.subjectReferralRequest.subjectElement `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 R5 element `ServiceRequest.subject` with unmapped reference targets: Device, Group, Location, Patient.
ServiceRequest.encounterencounter​is related toReferralRequest.contextReferralRequest.contextElement `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 R5 element `ServiceRequest.encounter` with unmapped reference targets: Encounter.
ServiceRequest.occurrence[x]occurrence[x]​is related toReferralRequest.occurrence[x]ReferralRequest.occurrence[x]Element `ServiceRequest.occurrence[x]` is mapped to FHIR STU3 element `ProcedureRequest.occurrence[x]` as `Equivalent`. Element `ServiceRequest.occurrence[x]` is mapped to FHIR STU3 element `ReferralRequest.occurrence[x]` as `SourceIsBroaderThanTarget`. 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.authoredOnauthoredOn​is equivalent toReferralRequest.authoredOnReferralRequest.authoredOnElement `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.requesterrequester​is equivalent toReferralRequest.requesterReferralRequest.requesterElement `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.
​is related toReferralRequest.requester.agentReferralRequest.requester.agentElement `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.
ServiceRequest.performerTypeperformerType​is equivalent toReferralRequest.specialtyReferralRequest.specialtyElement `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.performerperformer​is related toReferralRequest.recipientReferralRequest.recipientElement `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 R5 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 [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).
ServiceRequest.reasonreason​is related toReferralRequest.reasonCodeReferralRequest.reasonCodeElement `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonReference` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.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).
​is related toReferralRequest.reasonReferenceReferralRequest.reasonReferenceElement `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonReference` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.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).
ServiceRequest.supportingInfosupportingInfo​is related toReferralRequest.supportingInfoReferralRequest.supportingInfoElement `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: 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.
ServiceRequest.notenote​is equivalent toReferralRequest.noteReferralRequest.noteElement `ServiceRequest.note` is mapped to FHIR STU3 element `ProcedureRequest.note` as `Equivalent`. Element `ServiceRequest.note` is mapped to FHIR STU3 element `ReferralRequest.note` as `Equivalent`.
ServiceRequest.relevantHistoryrelevantHistory​is related toReferralRequest.relevantHistoryReferralRequest.relevantHistoryElement `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 R5 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 3 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: Instantiates FHIR protocol or definition additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.instantiatesCanonical (instantiatesCanonical)​maps to wider conceptExtension (R5: Instantiates FHIR protocol or definition additional types)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. 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.

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

Source CodeRelationshipTarget CodeComment
ServiceRequest.instantiatesUri (instantiatesUri)​maps to wider conceptExtension (R5: 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 5 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: proposal | plan | directive | order +version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.intent (intent)​maps to wider conceptExtension (R5: proposal | plan | directive | order +)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.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: What is being requested/ordered additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.code (code)​maps to wider conceptExtension (R5: What is being requested/ordered additional types)Element `ServiceRequest.code` is mapped to FHIR STU3 element `ProcedureRequest.code` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.type` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.code` is mapped to FHIR STU3 element `ReferralRequest.serviceRequested` as `RelatedTo`. 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.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: The context of the order details by reference (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.orderDetail.parameterFocus (parameterFocus)​maps to wider conceptExtension (R5: The context of the order details by reference (new))Element `ServiceRequest.orderDetail.parameterFocus` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.orderDetail.parameterFocus` has a context of ReferralRequest.serviceRequested based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.orderDetail.parameterFocus` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: The parameter details for the service being requested (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.orderDetail.parameter (parameter)​maps to wider conceptExtension (R5: The parameter details for the service being requested (new))Element `ServiceRequest.orderDetail.parameter` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.orderDetail.parameter` has a context of ReferralRequest.serviceRequested based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.orderDetail.parameter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ServiceRequest.orderDetail.parameter.code (code)​maps to wider conceptExtension.extension:code (R5: The detail of the order being requested (new))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 ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.orderDetail.parameter.code` has a context of ReferralRequest.serviceRequested based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.orderDetail.parameter.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ServiceRequest.orderDetail.parameter.value[x] (value[x])​maps to wider conceptExtension.extension:value (R5: The value for the order detail (new))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 ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.orderDetail.parameter.value[x]` has a context of ReferralRequest.serviceRequested based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.orderDetail.parameter.value[x]` has no mapping targets in FHIR STU3. 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.

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: Service amount (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.quantity[x] (quantity[x])​maps to wider conceptExtension (R5: 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 10 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: What the service request is about, when it is not about the subject of record (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.focus (focus)​maps to wider conceptExtension (R5: What the service request is about, when it is not about the subject of record (new))Element `ServiceRequest.focus` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.focus` has a context of ReferralRequest based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.focus` 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|5.0.0 to R5: Requested location (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.location (location)​maps to wider conceptExtension (R5: Requested location (new))Element `ServiceRequest.location` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.location` has a context of ReferralRequest based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.location` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: Explanation/Justification for procedure or service additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.reason (reason)​maps to wider conceptExtension (R5: Explanation/Justification for procedure or service additional types)Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ProcedureRequest.reasonReference` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `ServiceRequest.reason` is mapped to FHIR STU3 element `ReferralRequest.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).

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: Associated insurance coverage (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.insurance (insurance)​maps to wider conceptExtension (R5: 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 14 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceRequest|5.0.0 to R5: Additional clinical information additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ServiceRequest.supportingInfo (supportingInfo)​maps to wider conceptExtension (R5: Additional clinical information additional types)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: 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.

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

Source CodeRelationshipTarget CodeComment
ServiceRequest.patientInstruction (patientInstruction)​maps to wider conceptExtension (R5: Patient or consumer-oriented instructions (new))Element `ServiceRequest.patientInstruction` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.patientInstruction` has a context of ReferralRequest based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.patientInstruction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ServiceRequest.patientInstruction.instruction[x] (instruction[x])​maps to wider conceptExtension.extension:instruction (R5: Patient or consumer-oriented instructions (new))Element `ServiceRequest.patientInstruction.instruction[x]` is part of an existing definition because parent element `ServiceRequest.patientInstruction` requires a cross-version extension. Element `ServiceRequest.patientInstruction.instruction[x]` has a context of ProcedureRequest based on following the parent source element upwards and mapping to `ProcedureRequest`. Element `ServiceRequest.patientInstruction.instruction[x]` has a context of ReferralRequest based on following the parent source element upwards and mapping to `ReferralRequest`. Element `ServiceRequest.patientInstruction.instruction[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).