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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

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.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

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.

An Extension

DSTU2: DeviceUseRequest.bodySite[x] (new:CodeableConcept, Reference(BodySite))

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

DSTU2: DeviceUseRequest.prnReason (new:CodeableConcept)

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

DSTU2: DeviceUseRequest.timing[x] additional types (Timing, Period)

Element DeviceUseRequest.timing[x] is mapped to FHIR R5 element DeviceRequest.occurrence[x] as RelatedTo. The mappings for DeviceUseRequest.timing[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.

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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The status of the request.

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

Codes representing the status of the request.

An Extension

DSTU2: DeviceUseRequest.status additional codes

Element DeviceUseRequest.status is mapped to FHIR R5 element DeviceRequest.status as RelatedTo. The mappings for DeviceUseRequest.status do not allow expression of the necessary codes, per the bindings on the source and target. The target context DeviceRequest.status is a modifier element, so this extension does not need to be defined as a modifier.

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

The kind of diagnostic request.

If true, indicates that the provider is asking for the patient to either stop using or to not start using the specified device or category of devices. For example, the patient has undergone surgery and the provider is indicating that the patient should not wear contact lenses.

If do not perform is not specified, the request is a positive request e.g. "do perform". DeviceRequest.reasonCode includes the reason for marking the DeviceRequest as 'do not perform'.

The details of the device to be used.

Codes for devices that can be requested.

An Extension

DSTU2: DeviceUseRequest.device additional types (Reference(http://hl7.org/fhir/StructureDefinition/Device)) additional types from child elements (display, reference)

Element DeviceUseRequest.device is mapped to FHIR R5 element DeviceRequest.code as RelatedTo. The mappings for DeviceUseRequest.device do not cover the following types: Reference. The mappings for DeviceUseRequest.device do not cover the following types based on type expansion: display, reference.

The patient who will use the device.

An Extension

DSTU2: DeviceUseRequest.subject additional types from child elements (display, reference)

Element DeviceUseRequest.subject is mapped to FHIR R5 element DeviceRequest.subject as SourceIsBroaderThanTarget. The mappings for DeviceUseRequest.subject do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element DeviceUseRequest.subject with unmapped reference targets: 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.

DSTU2: DeviceUseRequest.meta additional types (Meta) additional types from child elements (lastUpdated, profile, security, tag, versionId)

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

DSTU2: DeviceUseRequest.text additional types (Narrative) additional types from child elements (div, status)

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

DSTU2: DeviceUseRequest.bodySite[x] (new:CodeableConcept, Reference(BodySite))

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

DSTU2: DeviceUseRequest.prnReason (new:CodeableConcept)

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

DSTU2: DeviceUseRequest.timing[x] additional types (Timing, Period)

Element DeviceUseRequest.timing[x] is mapped to FHIR R5 element DeviceRequest.occurrence[x] as RelatedTo. The mappings for DeviceUseRequest.timing[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.

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

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

DSTU2: DeviceUseRequest.status additional codes

Element DeviceUseRequest.status is mapped to FHIR R5 element DeviceRequest.status as RelatedTo. The mappings for DeviceUseRequest.status do not allow expression of the necessary codes, per the bindings on the source and target. The target context DeviceRequest.status is a modifier element, so this extension does not need to be defined as a modifier.

DSTU2: DeviceUseRequest.device additional types (Reference(http://hl7.org/fhir/StructureDefinition/Device)) additional types from child elements (display, reference)

Element DeviceUseRequest.device is mapped to FHIR R5 element DeviceRequest.code as RelatedTo. The mappings for DeviceUseRequest.device do not cover the following types: Reference. The mappings for DeviceUseRequest.device do not cover the following types based on type expansion: display, reference.

DSTU2: DeviceUseRequest.subject additional types from child elements (display, reference)

Element DeviceUseRequest.subject is mapped to FHIR R5 element DeviceRequest.subject as SourceIsBroaderThanTarget. The mappings for DeviceUseRequest.subject do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element DeviceUseRequest.subject with unmapped reference targets: Patient.

DSTU2: DeviceUseRequest.encounter additional types from child elements (display, reference)

Element DeviceUseRequest.encounter is mapped to FHIR R5 element DeviceRequest.encounter as SourceIsBroaderThanTarget. The mappings for DeviceUseRequest.encounter do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element DeviceUseRequest.encounter with unmapped reference targets: Encounter.

DSTU2: DeviceUseRequest.notes additional types (string) additional types from child elements (value)

Element DeviceUseRequest.notes is mapped to FHIR R5 element DeviceRequest.note as SourceIsBroaderThanTarget. The mappings for DeviceUseRequest.notes do not cover the following types: string. The mappings for DeviceUseRequest.notes do not cover the following types based on type expansion: value.

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.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might 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

DSTU2: DeviceUseRequest.meta additional types (Meta) additional types from child elements (lastUpdated, profile, security, tag, versionId)

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

The version specific identifier, as it appears in the version portion of the URL. This value 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 element is generally omitted in instances submitted in a PUT or POST. Instead, it is populated in the response instance and when retrieving information using a GET. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.

A uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.

The exact use of the source (and the possible implied Provenance.entity.role and agent.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. The source may correspond to Provenance.entity.what[x] or Provenance.agent.who[x], though it may be a more general or abstract reference.

This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.

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.

Unless not suitable, these codes SHALL be taken from AllSecurityLabels
(extensible to http://hl7.org/fhir/ValueSet/security-labels|5.0.0)

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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

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.

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

IETF language tag for a human language

A human-readable narrative that contains a summary of the resource and can 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 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.

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

An Extension

DSTU2: DeviceUseRequest.text additional types (Narrative) additional types from child elements (div, status)

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

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 SHALL 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, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

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.

An Extension

DSTU2: DeviceUseRequest.bodySite[x] (new:CodeableConcept, Reference(BodySite))

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

DSTU2: DeviceUseRequest.prnReason (new:CodeableConcept)

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

DSTU2: DeviceUseRequest.timing[x] additional types (Timing, Period)

Element DeviceUseRequest.timing[x] is mapped to FHIR R5 element DeviceRequest.occurrence[x] as RelatedTo. The mappings for DeviceUseRequest.timing[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.

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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

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

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

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

The purpose of this identifier.

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, an absolute URL that describes a set values that are unique.

Identifier.system is always case sensitive.

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 http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

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 URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest.

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.

The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest.

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

Plan/proposal/order fulfilled by this request.

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

A shared identifier common to multiple independent Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.

The status of the request.

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

Codes representing the status of the request.

unique id for the element within a resource (for internal references)

An Extension

DSTU2: DeviceUseRequest.status additional codes

Element DeviceUseRequest.status is mapped to FHIR R5 element DeviceRequest.status as RelatedTo. The mappings for DeviceUseRequest.status do not allow expression of the necessary codes, per the bindings on the source and target. The target context DeviceRequest.status is a modifier element, so this extension does not need to be defined as a modifier.

Primitive value for code

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

The kind of diagnostic request.

Indicates how quickly the request should be addressed with respect to other requests.

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

If true, indicates that the provider is asking for the patient to either stop using or to not start using the specified device or category of devices. For example, the patient has undergone surgery and the provider is indicating that the patient should not wear contact lenses.

If do not perform is not specified, the request is a positive request e.g. "do perform". DeviceRequest.reasonCode includes the reason for marking the DeviceRequest as 'do not perform'.

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

DSTU2: DeviceUseRequest.device additional types (Reference(http://hl7.org/fhir/StructureDefinition/Device)) additional types from child elements (display, reference)

Element DeviceUseRequest.device is mapped to FHIR R5 element DeviceRequest.code as RelatedTo. The mappings for DeviceUseRequest.device do not cover the following types: Reference. The mappings for DeviceUseRequest.device do not cover the following types based on type expansion: display, reference.

A reference to a concept - e.g. the information is identified by its general class to the degree of precision found in the terminology.

A reference to a resource the provides exact details about the information being referenced.

The number of devices to be provided.

Specific parameters for the ordered item. For example, the prism value for lenses.

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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A code or string that identifies the device detail being asserted.

A code that identifies the device detail.

The value of the device detail.

Range means device should have a value that falls somewhere within the specified range.

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

DSTU2: DeviceUseRequest.subject additional types from child elements (display, reference)

Element DeviceUseRequest.subject is mapped to FHIR R5 element DeviceRequest.subject as SourceIsBroaderThanTarget. The mappings for DeviceUseRequest.subject do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element DeviceUseRequest.subject with unmapped reference targets: 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.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|5.0.0)

Aa resource (or, for logical models, the URI of the logical model).

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents 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.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension.

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

DSTU2: DeviceUseRequest.encounter additional types from child elements (display, reference)

Element DeviceUseRequest.encounter is mapped to FHIR R5 element DeviceRequest.encounter as SourceIsBroaderThanTarget. The mappings for DeviceUseRequest.encounter do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element DeviceUseRequest.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.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|5.0.0)

Aa resource (or, for logical models, the URI of the logical model).

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents 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.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension.

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 or entity who initiated the request and has responsibility for its activation.

The desired individual or entity to provide the device to the subject of the request (e.g., patient, location).

Reason or justification for the use of this device.

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

This status is to indicate whether the request is a PRN or may be given as needed.

The reason for using the device.

Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.

Additional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject's body 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.

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

DSTU2: DeviceUseRequest.notes additional types (string) additional types from child elements (value)

Element DeviceUseRequest.notes is mapped to FHIR R5 element DeviceRequest.note as SourceIsBroaderThanTarget. The mappings for DeviceUseRequest.notes do not cover the following types: string. The mappings for DeviceUseRequest.notes do not cover the following types based on type expansion: value.

The individual responsible for making the annotation.

Organization is used when there's no need for specific attribution as to who made the comment.

Indicates when this particular annotation was made.

The text of the annotation in markdown format.

Key events in the history of the request.

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.