Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

An Extension

R4B: DeviceRequest.instantiatesCanonical (new:canonical(ActivityDefinition,PlanDefinition))

Element DeviceRequest.instantiatesCanonical has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest. Element DeviceRequest.instantiatesCanonical has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Note: This is a business identifier, not a resource identifier (see discussion). 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.

R4B: DeviceRequest.instantiatesUri (new:uri)

Element DeviceRequest.instantiatesUri has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest. Element DeviceRequest.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.

R4B: DeviceRequest.parameter (new:BackboneElement)

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

R4B: DeviceRequest.occurrence[x] additional types (Period, Timing)

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

R4B: DeviceRequest.insurance (new:Reference(Coverage,ClaimResponse))

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

May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

The status of the request.

This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid.

Codes representing the status of the request.

Whether the request is a proposal, plan, an original order or a reflex order.

The kind of diagnostic request

An Extension

R4B: DeviceRequest.intent

Element DeviceRequest.intent is mapped to FHIR STU3 element DeviceRequest.intent as RelatedTo. The target context DeviceRequest.intent is a modifier element, so this extension does not need to be defined as a modifier.

The details of the device to be used.

Codes for devices that can be requested

R4B: DeviceRequest.code[x] additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.code[x] is mapped to FHIR STU3 element DeviceRequest.code[x] as SourceIsBroaderThanTarget. The mappings for DeviceRequest.code[x] 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 DeviceRequest.code[x] with unmapped reference targets: Device. Source element DeviceRequest.code[x] has unmapped reference types. While the target element DeviceRequest.code[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

The patient who will use the device.

An Extension

R4B: DeviceRequest.subject

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

R4B: DeviceRequest.meta additional types (Meta) additional types from child elements (lastUpdated, profile, security, source, tag, versionId)

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

R4B: DeviceRequest.text additional types (Narrative) additional types from child elements (div, status)

Element DeviceRequest.text is mapped to FHIR STU3 element DeviceRequest.text as SourceIsBroaderThanTarget. The mappings for DeviceRequest.text do not cover the following types: Narrative. The mappings for DeviceRequest.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.

R4B: DeviceRequest.instantiatesCanonical (new:canonical(ActivityDefinition,PlanDefinition))

Element DeviceRequest.instantiatesCanonical has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest. Element DeviceRequest.instantiatesCanonical has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Note: This is a business identifier, not a resource identifier (see discussion). 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.

R4B: DeviceRequest.instantiatesUri (new:uri)

Element DeviceRequest.instantiatesUri has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest. Element DeviceRequest.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.

R4B: DeviceRequest.parameter (new:BackboneElement)

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

R4B: DeviceRequest.occurrence[x] additional types (Period, Timing)

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

R4B: DeviceRequest.insurance (new:Reference(Coverage,ClaimResponse))

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

R4B: DeviceRequest.identifier additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)

Element DeviceRequest.identifier is mapped to FHIR STU3 element DeviceRequest.identifier as SourceIsBroaderThanTarget. The mappings for DeviceRequest.identifier do not cover the following types: Identifier. The mappings for DeviceRequest.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.

R4B: DeviceRequest.basedOn additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.basedOn is mapped to FHIR STU3 element DeviceRequest.basedOn as SourceIsBroaderThanTarget. The mappings for DeviceRequest.basedOn 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 DeviceRequest.basedOn with unmapped reference targets: Resource.

R4B: DeviceRequest.priorRequest additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.priorRequest is mapped to FHIR STU3 element DeviceRequest.priorRequest as SourceIsBroaderThanTarget. The mappings for DeviceRequest.priorRequest 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 DeviceRequest.priorRequest with unmapped reference targets: Resource.

R4B: DeviceRequest.groupIdentifier additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)

Element DeviceRequest.groupIdentifier is mapped to FHIR STU3 element DeviceRequest.groupIdentifier as SourceIsBroaderThanTarget. The mappings for DeviceRequest.groupIdentifier do not cover the following types: Identifier. The mappings for DeviceRequest.groupIdentifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.

R4B: DeviceRequest.intent

Element DeviceRequest.intent is mapped to FHIR STU3 element DeviceRequest.intent as RelatedTo. The target context DeviceRequest.intent is a modifier element, so this extension does not need to be defined as a modifier.

R4B: DeviceRequest.code[x] additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.code[x] is mapped to FHIR STU3 element DeviceRequest.code[x] as SourceIsBroaderThanTarget. The mappings for DeviceRequest.code[x] 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 DeviceRequest.code[x] with unmapped reference targets: Device. Source element DeviceRequest.code[x] has unmapped reference types. While the target element DeviceRequest.code[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

R4B: DeviceRequest.subject

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

R4B: DeviceRequest.encounter additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.encounter is mapped to FHIR STU3 element DeviceRequest.context as SourceIsBroaderThanTarget. The mappings for DeviceRequest.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 DeviceRequest.encounter with unmapped reference targets: Encounter.

R4B: DeviceRequest.requester

Element DeviceRequest.requester is mapped to FHIR STU3 element DeviceRequest.requester.agent as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R4B element DeviceRequest.requester with unmapped reference targets: Device, Organization, Practitioner, PractitionerRole.

R4B: DeviceRequest.performer

Element DeviceRequest.performer is mapped to FHIR STU3 element DeviceRequest.performer as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R4B element DeviceRequest.performer with unmapped reference targets: CareTeam, Device, HealthcareService, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.

R4B: DeviceRequest.reasonReference

Element DeviceRequest.reasonReference is mapped to FHIR STU3 element DeviceRequest.reasonReference as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R4B element DeviceRequest.reasonReference with unmapped reference targets: Condition, DiagnosticReport, DocumentReference, Observation.

R4B: DeviceRequest.supportingInfo additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.supportingInfo is mapped to FHIR STU3 element DeviceRequest.supportingInfo as SourceIsBroaderThanTarget. The mappings for DeviceRequest.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 DeviceRequest.supportingInfo with unmapped reference targets: Resource.

R4B: DeviceRequest.note additional types (Annotation) additional types from child elements (author[x], text, time)

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

R4B: DeviceRequest.relevantHistory additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.relevantHistory is mapped to FHIR STU3 element DeviceRequest.relevantHistory as SourceIsBroaderThanTarget. The mappings for DeviceRequest.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 DeviceRequest.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.

Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.meta additional types (Meta) additional types from child elements (lastUpdated, profile, security, source, tag, versionId)

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

The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted.

The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.

When the resource last changed - e.g. when the version changed.

This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant.

A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url.

It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.

Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.

The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.

Security Labels from the Healthcare Privacy and Security Classification System.

Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.

The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.

Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones"

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

The base language in which the resource is written.

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).

A human language.

A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

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 in formation is added later.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.text additional types (Narrative) additional types from child elements (div, status)

Element DeviceRequest.text is mapped to FHIR STU3 element DeviceRequest.text as SourceIsBroaderThanTarget. The mappings for DeviceRequest.text do not cover the following types: Narrative. The mappings for DeviceRequest.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.

The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.

The status of a resource narrative

The actual narrative content, a stripped down version of XHTML.

The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

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.

An Extension

R4B: DeviceRequest.instantiatesCanonical (new:canonical(ActivityDefinition,PlanDefinition))

Element DeviceRequest.instantiatesCanonical has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest. Element DeviceRequest.instantiatesCanonical has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Note: This is a business identifier, not a resource identifier (see discussion). 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.

R4B: DeviceRequest.instantiatesUri (new:uri)

Element DeviceRequest.instantiatesUri has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest. Element DeviceRequest.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.

R4B: DeviceRequest.parameter (new:BackboneElement)

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

R4B: DeviceRequest.occurrence[x] additional types (Period, Timing)

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

R4B: DeviceRequest.insurance (new:Reference(Coverage,ClaimResponse))

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

May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Identifiers assigned to this order by the orderer or by the receiver.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.identifier additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)

Element DeviceRequest.identifier is mapped to FHIR STU3 element DeviceRequest.identifier as SourceIsBroaderThanTarget. The mappings for DeviceRequest.identifier do not cover the following types: Identifier. The mappings for DeviceRequest.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.

The purpose of this identifier.

This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage.

Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

Protocol or definition followed by this request. For example: The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x%.

Plan/proposal/order fulfilled by this request.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.basedOn additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.basedOn is mapped to FHIR STU3 element DeviceRequest.basedOn as SourceIsBroaderThanTarget. The mappings for DeviceRequest.basedOn 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 DeviceRequest.basedOn with unmapped reference targets: Resource.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The request takes the place of the referenced completed or terminated request(s).

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.priorRequest additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.priorRequest is mapped to FHIR STU3 element DeviceRequest.priorRequest as SourceIsBroaderThanTarget. The mappings for DeviceRequest.priorRequest 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 DeviceRequest.priorRequest with unmapped reference targets: Resource.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Composite request this is part of.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.groupIdentifier additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)

Element DeviceRequest.groupIdentifier is mapped to FHIR STU3 element DeviceRequest.groupIdentifier as SourceIsBroaderThanTarget. The mappings for DeviceRequest.groupIdentifier do not cover the following types: Identifier. The mappings for DeviceRequest.groupIdentifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.

The purpose of this identifier.

This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage.

Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

The status of the request.

This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid.

Codes representing the status of the request.

Whether the request is a proposal, plan, an original order or a reflex order.

The kind of diagnostic request

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.intent

Element DeviceRequest.intent is mapped to FHIR STU3 element DeviceRequest.intent as RelatedTo. The target context DeviceRequest.intent is a modifier element, so this extension does not need to be defined as a modifier.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

Indicates how quickly the {{title}} should be addressed with respect to other requests.

Identifies the level of importance to be assigned to actioning the request

The details of the device to be used.

Codes for devices that can be requested

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.code[x] additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.code[x] is mapped to FHIR STU3 element DeviceRequest.code[x] as SourceIsBroaderThanTarget. The mappings for DeviceRequest.code[x] 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 DeviceRequest.code[x] with unmapped reference targets: Device. Source element DeviceRequest.code[x] has unmapped reference types. While the target element DeviceRequest.code[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

The patient who will use the device.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.subject

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

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

An encounter that provides additional context in which this request is made.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.encounter additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.encounter is mapped to FHIR STU3 element DeviceRequest.context as SourceIsBroaderThanTarget. The mappings for DeviceRequest.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 DeviceRequest.encounter with unmapped reference targets: Encounter.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013".

When the request transitioned to being actionable.

The individual who initiated the request and has responsibility for its activation.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

The device, practitioner, etc. who initiated the request.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.requester

Element DeviceRequest.requester is mapped to FHIR STU3 element DeviceRequest.requester.agent as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R4B element DeviceRequest.requester with unmapped reference targets: Device, Organization, Practitioner, PractitionerRole.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The organization the device or practitioner was acting on behalf of.

Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when authoring the request.

Desired type of performer for doing the diagnostic testing.

Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

The desired perfomer for doing the diagnostic testing.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.performer

Element DeviceRequest.performer is mapped to FHIR STU3 element DeviceRequest.performer as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R4B element DeviceRequest.performer with unmapped reference targets: CareTeam, Device, HealthcareService, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Reason or justification for the use of this device.

Diagnosis or problem codes justifying the reason for requesting the device.

Reason or justification for the use of this device.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.reasonReference

Element DeviceRequest.reasonReference is mapped to FHIR STU3 element DeviceRequest.reasonReference as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R4B element DeviceRequest.reasonReference with unmapped reference targets: Condition, DiagnosticReport, DocumentReference, Observation.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Additional clinical information about the patient that may influence the request fulfilment. For example, this may includes body where on the subject's the device will be used ( i.e. the target site).

Knowing where the device is targeted is important for tracking if multiple sites are possible.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.supportingInfo additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.supportingInfo is mapped to FHIR STU3 element DeviceRequest.supportingInfo as SourceIsBroaderThanTarget. The mappings for DeviceRequest.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 DeviceRequest.supportingInfo with unmapped reference targets: Resource.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Details about this request that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.note additional types (Annotation) additional types from child elements (author[x], text, time)

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

The individual responsible for making the annotation.

Indicates when this particular annotation was made.

The text of the annotation.

Key events in the history of the request.

This may 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.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R4B: DeviceRequest.relevantHistory additional types from child elements (display, identifier, reference, type)

Element DeviceRequest.relevantHistory is mapped to FHIR STU3 element DeviceRequest.relevantHistory as SourceIsBroaderThanTarget. The mappings for DeviceRequest.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 DeviceRequest.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.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.