FHIR CI-Build

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

12.25 Resource DeviceDispense - Content

Orders and Observations icon Work GroupMaturity Level: 0 Trial UseSecurity Category: Business Compartments: No defined compartments

A record of dispensation of a device - i.e., assigning a device to a patient, or to a professional for their use.

12.25.1 Scope and Usage

The DeviceDispense resource is used to capture the assignment of a Device to a patient or practitioner for the purpose of care. The dispense may include a description of the device and the instructions for using the device. The request to initiate a DeviceDispense may be via a DeviceRequest resource but may be implicitly triggered by for example a ServiceRequest, or without any request. The details of the clinical application of the dispensed device may be captured in a Procedure resource.

12.25.2 Boundaries and Relationships

To determine the purchase date, a search of DeviceRequest, SupplyRequest, DeviceDispense, or SupplyDelivery as defined in an implementation guide can be done , as the context of the use case actually determines which date of either resource is considered the purchase date.

12.25.3 References to this Resource

12.25.4 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceDispense TU DomainResource A record of dispensation of a device

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ 0..* Identifier Business identifier for this dispensation

... basedOn 0..* Reference(CarePlan | DeviceRequest) The order or request that this dispense is fulfilling

... partOf 0..* Reference(Procedure) The bigger event that this dispense is a part of

... statusReason 0..1 CodeableReference(DetectedIssue) Why a dispense was or was not performed
Binding: DeviceDispense Status Reason Codes (Example)
... category 0..* CodeableConcept Type of device dispense

... device Σ 1..1 CodeableReference(Device | DeviceDefinition) What device was supplied
... subject Σ 1..1 Reference(Patient | Practitioner) Who the dispense is for
... receiver 0..1 Reference(Patient | Practitioner | RelatedPerson | Location | PractitionerRole) Who collected the device or where the medication was delivered
... encounter 0..1 Reference(Encounter) Encounter associated with event
... supportingInformation 0..* Reference(Any) Information that supports the dispensing of the device

... performer 0..* BackboneElement Who performed event

.... function 0..1 CodeableConcept Who performed the dispense and what they did
.... actor 1..1 Reference(Practitioner | PractitionerRole | Organization | Patient | Device | RelatedPerson | CareTeam) Individual who was performing
... location 0..1 Reference(Location) Where the dispense occurred
... type 0..1 CodeableConcept Trial fill, partial fill, emergency fill, etc
... quantity 0..1 SimpleQuantity Amount dispensed
... preparedDate Σ 0..1 dateTime When product was packaged and reviewed
... whenHandedOver 0..1 dateTime When product was given out
... destination 0..1 Reference(Location) Where the device was sent or should be sent
... note 0..* Annotation Information about the dispense

... usageInstruction 0..1 markdown Full representation of the usage instructions
... eventHistory 0..* Reference(Provenance) A list of relevant lifecycle events


doco Documentation for this format icon

See the Extensions for this resource

 

Additional definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions, the spreadsheet version & the dependency analysis

12.25.4.1 Terminology Bindings

Path ValueSet Type Documentation
DeviceDispense.status DeviceDispenseStatusCodes Required

DeviceDispense Status Codes
DeviceDispense.statusReason DeviceDispenseStatusReasonCodes Example

DeviceDispense Status Reason Codes

12.25.5 Search Parameters

Search parameters for this resource. See also the full list of search parameters for this resource, and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
code token Search for devices that match this code DeviceDispense.device.concept
identifier token The identifier of the dispense DeviceDispense.identifier
patient reference Returns device dispenses for a specific patient DeviceDispense.subject.where(resolve() is Patient)
(Patient)
status token The status of the dispense DeviceDispense.status
subject reference The identity of a patient for whom to list dispenses DeviceDispense.subject
(Practitioner, Patient)