type: resource-definitionsresource: DeviceUsage

DeviceUsage Definitions

DeviceUsage

Record of use of a device

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.

Cardinality: 0..*

Mappings: workflow=Event; quick=DeviceUsePerformanceOccurrence; w5=workflow.order

DeviceUsage.identifier

External identifier for this record

Definition: An external identifier for this statement such as an IRI.

Cardinality: 0..*

Type: Identifier

Summary: true

Mappings: workflow=Event.identifier; w5=FiveWs.identifier; quick=ClinicalStatement.identifier

DeviceUsage.basedOn

Fulfills plan, proposal or order

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

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

Aliases: fulfills

Cardinality: 0..*

Type: Reference(ServiceRequest)

Summary: true

Mappings: workflow=Event.basedOn; v2=ORC in proximity to EVN segment; rim=.outboundRelationship[typeCode=FLFS].target

DeviceUsage.partOf

Part of referenced device usage

Definition: A larger event of which this particular device usage is one part the usage.

Cardinality: 0..*

Type: Reference(DeviceUsage)

Summary: true

Mappings: workflow=Event.partOf

DeviceUsage.status

preparation | active | completed | not-done | entered-in-error +

Definition: The current state of the device usage.

Comments: DeviceUsage 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. When the status is 'not-done', the event-statusReason extension should be used to indicate why the DeviceUsage was not done.

Cardinality: 1..1

Type: code

Binding: required:deviceusage-status

Summary: true

Is Modifier: true (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)

Mappings: workflow=Event.status; w5=FiveWs.status; rim=.statusCode; quick=…status

DeviceUsage.category

The category of the statement - classifying how the statement is made

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

Cardinality: 0..*

Type: CodeableConcept

Mappings: workflow=Event.category

DeviceUsage.subject

Individuals(s) who used the device

Definition: The individual(s) who used the device.

Comments: Group is only allowed in the circumstance where the group represents a family or a household, and should not represent groups of Practitioners where other more specific resources can be used instead.

Cardinality: 1..1

Type: Reference(Patient, Group)

Summary: true

Mappings: workflow=Event.subject; w5=FiveWs.subject; quick=ClinicalStatement.subject

DeviceUsage.derivedFrom

Supporting information

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

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.

Cardinality: 0..*

Type: Reference(ServiceRequest, Procedure, Claim, Observation, QuestionnaireResponse, DocumentReference)

Summary: true

DeviceUsage.context

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

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

Cardinality: 0..1

Type: Reference(Encounter, EpisodeOfCare)

Summary: true

Mappings: workflow=Event.encounter

DeviceUsage.timing[x]

How often the device was used

Definition: How often the device was used.

Cardinality: 0..1

Type: Timing, Period, dateTime

Summary: true

Mappings: workflow=Event.occurrence[x]; w5=FiveWs.done[x]; quick=DeviceUse.applicationSchedule

DeviceUsage.dateAsserted

When the statement was made (and recorded)

Definition: The time at which the statement was recorded by informationSource.

Cardinality: 0..1

Type: dateTime

Summary: true

Mappings: w5=FiveWs.recorded; quick=ClinicalStatement.statementDateTime; workflow=Event.recorded

DeviceUsage.usageStatus

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

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

Cardinality: 0..1

Type: CodeableConcept

Binding: required:deviceusage-status

DeviceUsage.usageReason

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

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

Cardinality: 0..*

Type: CodeableConcept

DeviceUsage.adherence

How device is being used

Definition: This indicates how or if the device is being used.

Cardinality: 0..1

Type: BackboneElement

DeviceUsage.adherence.code

always | never | sometimes

Definition: Type of adherence.

Cardinality: 1..1

Type: CodeableConcept

Binding: example:deviceusage-adherence-code

Mappings: rim=NA

DeviceUsage.adherence.reason

Definition: Reason for adherence type.

Cardinality: 1..*

Type: CodeableConcept

Binding: example:deviceusage-adherence-reason

Mappings: rim=NA

DeviceUsage.informationSource

Who made the statement

Definition: Who reported the device was being used by the patient.

Cardinality: 0..1

Type: Reference(Patient, Practitioner, PractitionerRole, RelatedPerson, Organization, Group)

Summary: true

Mappings: workflow=Event.performer.actor; w5=FiveWs.actor; workflow=Event.reported[x]

DeviceUsage.device

Code or Reference to device used

Definition: Code or Reference to device used.

Cardinality: 1..1

Type: CodeableReference

Summary: true

Mappings: w5=FiveWs.actor; workflow=Event.product

DeviceUsage.reason

Why device was used

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

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

Cardinality: 0..*

Type: CodeableReference

Summary: true

Mappings: workflow=Event.reason; w5=FiveWs.why[x]; rim=.outboundRelationship[typeCode=RSON].target; quick=Action.indication.reason

DeviceUsage.bodyStructure

Target body structure

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

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

Cardinality: 0..1

Type: CodeableReference

Binding: example:body-site

Summary: true

Mappings: workflow=Event.note; rim=targetSiteCode

DeviceUsage.note

Addition details (comments, instructions)

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.

Cardinality: 0..*

Type: Annotation

Mappings: workflow=Event.note; quick=ClinicalStatement.additionalText