Release 5 Draft Ballot

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Orders and Observations Work GroupMaturity Level: 1 Trial UseSecurity Category: Patient Compartments: Patient

Detailed Descriptions for the elements in the DeviceUsage resource.

DeviceUsage
Element IdDeviceUsage
Definition

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

Cardinality0..*
TypeDomainResource
Summaryfalse
DeviceUsage.identifier
Element IdDeviceUsage.identifier
Definition

An external identifier for this statement such as an IRI.

NoteThis is a business identifier, not a resource identifier (see discussion)
Cardinality0..*
TypeIdentifier
Summarytrue
DeviceUsage.basedOn
Element IdDeviceUsage.basedOn
Definition

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

Cardinality0..*
TypeReference(ServiceRequest)
Requirements

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

Alternate Namesfulfills
Summarytrue
DeviceUsage.status
Element IdDeviceUsage.status
Definition

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.

Cardinality1..1
Terminology BindingDeviceUsageStatus (Required)
Typecode
Is Modifiertrue (Reason: This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid)
Summarytrue
Comments

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.

DeviceUsage.category
Element IdDeviceUsage.category
Definition

This attribute indicates a category for the statement - The device statement may be made in an inpatient or outpatient settting (inpatient | outpatient | community | patientspecified).

Cardinality0..*
TypeCodeableConcept
Summaryfalse
DeviceUsage.subject
Element IdDeviceUsage.subject
Definition

The patient who used the device.

Cardinality1..1
TypeReference(Patient | Group)
PatternsReference(Patient,Group): Common patterns = Participant
Summarytrue
DeviceUsage.derivedFrom
Element IdDeviceUsage.derivedFrom
Definition

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

Cardinality0..*
TypeReference(ServiceRequest | Procedure | Claim | Observation | QuestionnaireResponse | DocumentReference)
PatternsReference(ServiceRequest,Procedure,Claim,Observation,QuestionnaireResponse,DocumentReference): No common pattern
Summarytrue
Comments

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.

DeviceUsage.context
Element IdDeviceUsage.context
Definition

The encounter or episode of care that establishes the context for this device use statement.

Cardinality0..1
TypeReference(Encounter | EpisodeOfCare)
PatternsReference(Encounter,EpisodeOfCare): Common patterns = Event
Summarytrue
DeviceUsage.timing[x]
Element IdDeviceUsage.timing[x]
Definition

How often the device was used.

Cardinality0..1
TypeTiming|Period|dateTime
[x] NoteSee Choice of Data Types for further information about how to use [x]
Summarytrue
DeviceUsage.dateAsserted
Element IdDeviceUsage.dateAsserted
Definition

The time at which the statement was recorded by informationSource.

Cardinality0..1
TypedateTime
Summarytrue
DeviceUsage.usageStatus
Element IdDeviceUsage.usageStatus
Definition

The status of the device usage, for example always, sometimes, never. This is not the same as the status of the statement.

Cardinality0..1
Terminology BindingDeviceUsageStatus (Required)
TypeCodeableConcept
Summaryfalse
DeviceUsage.usageReason
Element IdDeviceUsage.usageReason
Definition

The reason for asserting the usage status - for example forgot, lost, stolen, broken.

Cardinality0..*
TypeCodeableConcept
Summaryfalse
DeviceUsage.informationSource
Element IdDeviceUsage.informationSource
Definition

Who reported the device was being used by the patient.

Cardinality0..1
TypeReference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization)
PatternsReference(Patient,Practitioner,PractitionerRole,RelatedPerson,Organization): Common patterns = Participant
Summarytrue
DeviceUsage.device
Element IdDeviceUsage.device
Definition

Code or Reference to device used.

Cardinality1..1
TypeCodeableReference(Device | DeviceDefinition)
PatternsCodeableReference(Device,DeviceDefinition): No common pattern
Summarytrue
DeviceUsage.reason
Element IdDeviceUsage.reason
Definition

Reason or justification for the use of the device. A coded concept, or another resource whose existence justifies this DeviceUsage.

Cardinality0..*
TypeCodeableReference(Condition | Observation | DiagnosticReport | DocumentReference)
PatternsCodeableReference(Condition,Observation,DiagnosticReport,DocumentReference): Common patterns = Event
Summarytrue
Comments

When the status is not done, the reason code indicates why it was not done.

DeviceUsage.bodySite
Element IdDeviceUsage.bodySite
Definition

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

Cardinality0..1
Terminology BindingSNOMED CT Body Structures (Example)
TypeCodeableReference(BodyStructure)
Requirements

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.

Summarytrue
DeviceUsage.note
Element IdDeviceUsage.note
Definition

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.

Cardinality0..*
TypeAnnotation
Summaryfalse