A record of a device being used by a patient where the record is the result of a report from the patient or another clinician.

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 it's narrative along with other profiles, value sets, etc.

An Extension

R5: DeviceUsage.category (new:CodeableConcept)

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

R5: DeviceUsage.context (new:Reference(Encounter,EpisodeOfCare))

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

R5: DeviceUsage.usageStatus (new:CodeableConcept)

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

R5: DeviceUsage.usageReason (new:CodeableConcept)

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

R5: DeviceUsage.adherence (new:BackboneElement)

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

R5: DeviceUsage.reason additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Condition), CodeableReference(http://hl7.org/fhir/StructureDefinition/Observation), CodeableReference(http://hl7.org/fhir/StructureDefinition/DiagnosticReport), CodeableReference(http://hl7.org/fhir/StructureDefinition/DocumentReference), CodeableReference(http://hl7.org/fhir/StructureDefinition/Procedure))

Element DeviceUsage.reason is mapped to FHIR R4B element DeviceUseStatement.reasonCode as SourceIsBroaderThanTarget. Element DeviceUsage.reason is mapped to FHIR R4B element DeviceUseStatement.reasonReference as SourceIsBroaderThanTarget. The mappings for DeviceUsage.reason do not cover the following types: CodeableReference. When the status is not done, the reason code indicates why it was not done.

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

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 representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed.

DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).

This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.

A coded concept indicating the current status of the Device Usage.

An Extension

R5: DeviceUsage.status

Element DeviceUsage.status is mapped to FHIR R4B element DeviceUseStatement.status as SourceIsBroaderThanTarget. The target context DeviceUseStatement.status is a modifier element, so this extension does not need to be defined as a modifier. DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).

This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.

The patient who used the device.

The details of the device used.

An Extension

R5: DeviceUsage.device additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Device), CodeableReference(http://hl7.org/fhir/StructureDefinition/DeviceDefinition)) additional types from child elements (concept)

Element DeviceUsage.device is mapped to FHIR R4B element DeviceUseStatement.device as SourceIsBroaderThanTarget. The mappings for DeviceUsage.device do not cover the following types: CodeableReference. The mappings for DeviceUsage.device do not cover the following types based on type expansion: concept.

R5: DeviceUsage.category (new:CodeableConcept)

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

R5: DeviceUsage.context (new:Reference(Encounter,EpisodeOfCare))

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

R5: DeviceUsage.usageStatus (new:CodeableConcept)

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

R5: DeviceUsage.usageReason (new:CodeableConcept)

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

R5: DeviceUsage.adherence (new:BackboneElement)

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

R5: DeviceUsage.reason additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Condition), CodeableReference(http://hl7.org/fhir/StructureDefinition/Observation), CodeableReference(http://hl7.org/fhir/StructureDefinition/DiagnosticReport), CodeableReference(http://hl7.org/fhir/StructureDefinition/DocumentReference), CodeableReference(http://hl7.org/fhir/StructureDefinition/Procedure))

Element DeviceUsage.reason is mapped to FHIR R4B element DeviceUseStatement.reasonCode as SourceIsBroaderThanTarget. Element DeviceUsage.reason is mapped to FHIR R4B element DeviceUseStatement.reasonReference as SourceIsBroaderThanTarget. The mappings for DeviceUsage.reason do not cover the following types: CodeableReference. When the status is not done, the reason code indicates why it was not done.

R5: DeviceUsage.status

Element DeviceUsage.status is mapped to FHIR R4B element DeviceUseStatement.status as SourceIsBroaderThanTarget. The target context DeviceUseStatement.status is a modifier element, so this extension does not need to be defined as a modifier. DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).

This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.

R5: DeviceUsage.derivedFrom

Element DeviceUsage.derivedFrom is mapped to FHIR R4B element DeviceUseStatement.derivedFrom as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element DeviceUsage.derivedFrom with unmapped reference targets: DocumentReference. The most common use cases for deriving a DeviceUsage comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUsage from.

R5: DeviceUsage.informationSource

Element DeviceUsage.informationSource is mapped to FHIR R4B element DeviceUseStatement.source as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element DeviceUsage.informationSource with unmapped reference targets: Organization.

R5: DeviceUsage.device additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Device), CodeableReference(http://hl7.org/fhir/StructureDefinition/DeviceDefinition)) additional types from child elements (concept)

Element DeviceUsage.device is mapped to FHIR R4B element DeviceUseStatement.device as SourceIsBroaderThanTarget. The mappings for DeviceUsage.device do not cover the following types: CodeableReference. The mappings for DeviceUsage.device do not cover the following types based on type expansion: concept.

R5: DeviceUsage.bodySite additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/BodyStructure)) additional types from child elements (reference)

Element DeviceUsage.bodySite is mapped to FHIR R4B element DeviceUseStatement.bodySite as SourceIsBroaderThanTarget. The mappings for DeviceUsage.bodySite do not cover the following types: CodeableReference. The mappings for DeviceUsage.bodySite do not cover the following types based on type expansion: reference.

A record of a device being used by a patient where the record is the result of a report from the patient or another clinician.

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 might not always be associated with version changes to the resource.

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 it's 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

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

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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

An Extension

R5: DeviceUsage.category (new:CodeableConcept)

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

R5: DeviceUsage.context (new:Reference(Encounter,EpisodeOfCare))

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

R5: DeviceUsage.usageStatus (new:CodeableConcept)

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

R5: DeviceUsage.usageReason (new:CodeableConcept)

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

R5: DeviceUsage.adherence (new:BackboneElement)

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

R5: DeviceUsage.reason additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Condition), CodeableReference(http://hl7.org/fhir/StructureDefinition/Observation), CodeableReference(http://hl7.org/fhir/StructureDefinition/DiagnosticReport), CodeableReference(http://hl7.org/fhir/StructureDefinition/DocumentReference), CodeableReference(http://hl7.org/fhir/StructureDefinition/Procedure))

Element DeviceUsage.reason is mapped to FHIR R4B element DeviceUseStatement.reasonCode as SourceIsBroaderThanTarget. Element DeviceUsage.reason is mapped to FHIR R4B element DeviceUseStatement.reasonReference as SourceIsBroaderThanTarget. The mappings for DeviceUsage.reason do not cover the following types: CodeableReference. When the status is not done, the reason code indicates why it was not done.

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

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.

An external identifier for this statement such as an IRI.

A plan, proposal or order that is fulfilled in whole or in part by this DeviceUseStatement.

Allows tracing of authorization for the DeviceUseStatement and tracking whether proposals/recommendations were acted upon.

A code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed.

DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).

This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.

A coded concept indicating the current status of the Device Usage.

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

An Extension

R5: DeviceUsage.status

Element DeviceUsage.status is mapped to FHIR R4B element DeviceUseStatement.status as SourceIsBroaderThanTarget. The target context DeviceUseStatement.status is a modifier element, so this extension does not need to be defined as a modifier. DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).

This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.

Primitive value for code

The patient who used the device.

Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement.

The most common use cases for deriving a DeviceUseStatement comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUseStatement from.

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

An Extension

R5: DeviceUsage.derivedFrom

Element DeviceUsage.derivedFrom is mapped to FHIR R4B element DeviceUseStatement.derivedFrom as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element DeviceUsage.derivedFrom with unmapped reference targets: DocumentReference. The most common use cases for deriving a DeviceUsage comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUsage from.

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 RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

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

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.

How often the device was used.

The time at which the statement was made/recorded.

Who reported the device was being used by the patient.

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

An Extension

R5: DeviceUsage.informationSource

Element DeviceUsage.informationSource is mapped to FHIR R4B element DeviceUseStatement.source as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element DeviceUsage.informationSource with unmapped reference targets: Organization.

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 RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

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

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 details of the device used.

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

An Extension

R5: DeviceUsage.device additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Device), CodeableReference(http://hl7.org/fhir/StructureDefinition/DeviceDefinition)) additional types from child elements (concept)

Element DeviceUsage.device is mapped to FHIR R4B element DeviceUseStatement.device as SourceIsBroaderThanTarget. The mappings for DeviceUsage.device do not cover the following types: CodeableReference. The mappings for DeviceUsage.device do not cover the following types based on type expansion: concept.

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 RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

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

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 the device.

Indicates another resource whose existence justifies this DeviceUseStatement.

Indicates the anotomic location on the subject's body where the device was used ( i.e. the target).

SNOMED CT Body site concepts

Knowing where the device is targeted is important for tracking if multiple sites are possible. If more information than just a code is required, use the extension http://hl7.org/fhir/StructureDefinition/bodySite.

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

An Extension

R5: DeviceUsage.bodySite additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/BodyStructure)) additional types from child elements (reference)

Element DeviceUsage.bodySite is mapped to FHIR R4B element DeviceUseStatement.bodySite as SourceIsBroaderThanTarget. The mappings for DeviceUsage.bodySite do not cover the following types: CodeableReference. The mappings for DeviceUsage.bodySite do not cover the following types based on type expansion: reference.

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 alternative encodings within a code system, and translations to other code systems.

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.

Details about the device statement 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.