Resource type: iteminstance

Description

A physical, countable instance of an item, for example one box or one unit.

Elements

PathShortDefinitionComments
A physical instance of an itemA physical, countable instance of an item, for example one box or one unit.
countThe count of itemsThe quantity or amount of instances. For example if several units are being counted for inventory, this quantity can be more than one, provided they are not unique. Seriallized items are considered unique and as such would have a quantity max 1. This element is required and its presence asserts that the reource refers to a physical item.
locationThe physical location of the itemThe location where the item is phisically located.
subjectThe patient that the item is affixed toThe patient that the item is associated with (implanted in, given to).
manufactureDateThe manufacture or preparation date and timeThe manufacture or preparation date and time. Times are necessary for several examples - for example biologically derived products, prepared or coumpounded medication, rapidly decaying isotopes.
expiryDateThe expiry or preparation date and timeThe expiry or preparation date and time.
currentSWVersionThe Software version associated with the deviceThe Software version associated with the device, typically only used for devices with embedded software or firmware.
lotNumberThe lot or batch numberThe lot or batch number.
serialNumberThe serial number if availableThe serial number if available.
carrierAIDCThe machine-readable AIDC string in base64 encodingThe machine-readable AIDC string in base64 encoding. Can correspond to the UDI pattern in devices.
carrierHRFThe human-readable barcode stringThe human-readable barcode string. Can correspond to the UDI pattern in devices.

Scope and Usage

This resource has not yet undergone proper review by the appropriate Workgroups. At this time, is considered only as a draft resource proposal for potential submission

Different resources have different ways to handle “physical instances”

  • Lack of clear support and guidance for instance has caused traceability to be a problem in implementations: Standards-guided implementations do not consider “instances” or do so inconsistently.
  • In border cases (medication containing devices), this can cause issues.
  • Inconsistency can also require extensions and further divergence. E.g. for adopting the EU Serialization directive, need to add “serial number” to the medication. What and where is that extension?

If the resources that represent physical entities were split into a "kind" resource and an "instance" resource, this resource would represent the instance that would be referenced by the "kind" resource. For example, Device would be split into Device ( representing the kind or type of Device ) + ItemInstance ( representing the instance of a Device ).

Resources impacted:

  • Substance
  • Medication
  • Device

Search Parameters

subjectThe identifier of the patient who has devices assigned toItemInstance.subject

Extension Definitions

These are extension definitions for this resource defined by the spec