Page History

Describe the project; include what is expected to be accomplished/delivered along with specified features and functions. Include whether the deliverable(s) are universal, realm specific or applicable to various realms. Be sure to spell out all acronyms as these are carried forward to the NIB (Notice of Intent to Ballot) for ballot announcements..Definition of triggers and content in support of interaction between healthcare information systems (HIS) and automated dispensing cabinet systems (ADC).

Specifically, the HIS maintains a "floor stock" table that permits it to know whether or not a pharmacy dispense will be required for a new or changed medication order. This table maintains a list of the medications that are "floor stock" (that is, stored in an automated dispensing cabinet) on a particular nursing unit, and a list of the patient rooms on that unit. Using this table, the HIS can determine whether the pharmacy needs to dispense medication in response to a new or changed order based on whether or not that medication is already available in one or more automated dispensing cabinets that service that unit.

The list of medications stored is incremented based on a "load" event (placement of a new medication into the cabinet) or an "unload" event (removal of a medication supply from the cabinet). As a result of such events, the ADC system must notify the HIS that its floor stock table must be updated.

Typically, these interactions also provide information on the current inventory of the medication in the cabinet(s) serving a particular nursing unit, and the location(s) within the cabinet(s) where those medications may be loaded. This information permits electronic Medication Administration Records (eMAR) published by the HIS to inform the nurse where medications are located. Messages from the ADC to the HIS may therefore be generated any time the inventory within a cabinet is incremented (refilled, or loaded) or decremented (dispence from cabinet, unload from cabinet).

This information is required by ANSI for all ballots. Briefly explain the reason behind the need for this project. This may be related to legislative requirements, industry need, or similar justifications.
.

Current HL7 transactional systems do not support this interaction use case. The result is that these interactions are maintained in version 2.x HL7 messages using non-standard segments (Z-segments). The result of this implementation is that health systems that either change out HIS products (host conversions) or ADC systems are required to purchase and implement new interfaces at significant costs in both money and time. Standardizing these interactions would remove some, but not all, of the effort associated with such changes.