Automated exchange of healthcare information for fulfillment of medication doses

Patent metadata

Field	Value
Publication number	US-12412644-B2
Application number	US-201514922376-A
Country	US
Kind code	B2
Filing date	Oct 26, 2015
Priority date	Oct 24, 2014
Publication date	Sep 9, 2025
Grant date	Sep 9, 2025

Abstract

Automated healthcare information exchange. The healthcare information may comprise one or more dose orders corresponding to dose medications to be administered to a patient. The healthcare information may be received (e.g., from an EMR system such as a hospital information system (HIS) or the like) in the form of a healthcare information data stream. The information may then be standardized in to a standardized intermediate form. For instance, data may be parsed from the data stream and used to populate a staging table. In turn, data from the staging table may be transformed into an input format specific to a given dose fulfillment client to which the dose order is provided for fulfillment of the dose. Additionally, exception processing. logistical processing, and management functionality may be applied to the dose orders.

First claim

What is claimed is:

1. A method for an automated exchange of healthcare information between an electronic medical record (EMR) system and a selected dose fulfillment client for fulfillment of a dose order, the method comprising:
executing non-transitory machine-readable data for specifically configuring processors of a platform interface module, a transformation module, and a client router, execution of the non-transitory machine-readable data causing the processors to:
receive a healthcare information data stream at the platform interface module via a network from the EMR system, wherein the healthcare information data stream comprises information including dose order metadata related to dose orders that is provided in a Health Level 7 (“HL7”) format;
identify, via the platform interface module, individual dose orders from the healthcare information data stream by identifying express delineators within the healthcare information data stream and identifying the dose order metadata corresponding to dose order data fields, wherein the express delineators mark separations between the dose orders in the healthcare information data stream;
parse, via the platform interface module, the dose order metadata for each of the dose orders from the healthcare information data stream, wherein the dose order metadata comprises one or more dose characteristics associated with the respective dose order;
populate, via the platform interface module, a staging table with the dose order metadata for each of the dose orders, wherein the staging table comprises a plurality of dose order data fields populated with corresponding respective portions of the dose order metadata parsed from the healthcare information data stream, and wherein the dose order metadata is populated in a standardized intermediate format;
determine, via the transformation module from the dose order metadata, a dose fulfillment client type, among a plurality of different dose fulfillment client types for fulfilling each of the dose orders, the dose fulfillment client types including an automated dose preparation device, an automated total parenteral nutrition (TPN) compounder, and an automated dose dispensing cabinet;
select, via the transformation module, a dose fulfillment client that matches the dose fulfillment client type for fulfillment of each of the dose orders;
transform, via the transformation module, the dose order metadata from the standardized intermediate format into a predefined format dictated by the selected dose fulfillment client to generate transformed dose order metadata,
wherein the transforming is at least in part based on the respective predefined format of the selected dose fulfillment client, and
wherein the transforming includes mapping the plurality of dose order data fields of the staging table to corresponding respective ones of a plurality of dose fulfillment client input fields for the selected dose fulfillment client, including at least:
mapping one data field of the plurality of dose order data fields of the staging table to one data field of the plurality of dose fulfillment client input fields, and
mapping at least two data fields of the plurality of dose order data fields of the staging table to one data field of the plurality of dose fulfillment client input fields;

route, via the client router of the transformation module, the transformed dose order metadata to the selected dose fulfillment client via the network; and
cause each of the dose orders to be fulfilled automatically using the selected dose fulfillment client based on the transformed dose order metadata to provide a corresponding medication dose.

2. The method of claim 1 , further comprising:
receiving a first dose order in a first EMR form; and
receiving a second dose order in a second EMR from,
wherein the first dose order and the second dose order correspond to a dose order with identical constituent ingredients,
wherein a form of the constituent ingredients in the first EMR form differs from the second EMR form, and
wherein a form of the constituent ingredients for the first dose order is identical to a form of the constituent ingredients for the second dose order in the respective staging tables corresponding to the first dose order and the second dose order.

3. The method of claim 1 , wherein the staging table is independent of any of the plurality of dose fulfillment clients.

4. The method of claim 1 , wherein the dose fulfillment client input fields are defined by a unique input format associated with the dose fulfillment client.

5. The method of claim 4 , wherein the transforming comprises:
validating the dose order metadata of the plurality of dose order data fields with respect to the unique input format for corresponding ones of the dose fulfillment client input fields.

6. The method of claim 5 , wherein the validating comprises:
correlating the dose order metadata of the plurality of dose order data fields to formulary records of the dose fulfillment client with respect to the corresponding respective ones of the dose fulfillment client input fields.

7. The method of claim 6 , further comprising:
generating an exception in response to an error associated with at least one of the mapping or validating.

8. The method of claim 7 , wherein the exception comprises prompting a human user to resolve the error.

9. The method of claim 8 , further comprising:
receiving, from the human user, an input associated with the resolution of the error, wherein the input comprises at least one of a correct mapping between a dose order data field of the staging table and a corresponding respective one of a dose fulfillment client input fields or a correct correlation between a portion of dose order metadata and a formulary record of the dose fulfillment client.

10. The method of claim 9 , further comprising:
updating at least one of a mapping logic or a correlation logic for use in the mapping and correlating, respectively, based on the input received from the human user.

11. The method of claim 1 , further comprising:
updating the staging table to indicate the dose order metadata for each of the dose orders that have been routed to the dose fulfillment client.

12. The method of claim 1 , further comprising:
managing each of the dose orders prior to providing the dose order metadata in a second form to the dose fulfillment client.

13. The method of claim 12 , wherein the managing includes providing a user interface to allow a user to perform a management function relative to each of the dose orders.

14. The method of claim 13 , wherein the management function comprises at least one of modification of dose order metadata, cancellation of the dose order, organization of the dose order relative to other dose orders, or prioritization of the dose order relative to other dose orders.

15. The method of claim 1 , further comprising:
performing logistical processing on each of the dose orders.

16. The method of claim 15 , wherein the logistical processing comprises performing an action relative to each of the dose orders in response to receipt of an EMR system message subsequent to the receipt of the respective dose order.

17. The method of claim 16 , wherein the EMR system message comprises at least one of a dose order change message or a dose order discontinuation message.

18. The method of claim 17 , wherein the logistical processing comprises determining if the dose order metadata has been provided to the dose fulfillment client.

19. The method of claim 18 , wherei

Assignees

• Baxter Corp Englewood

Inventors

• Padmani Bhavesh S
• Olsen Gregory T
• Abbasi Ghalib A
• Dooley Cherie
• Leech Douglas
• Armstrong Cory D
• White Russell

Classifications

• G16H70/40

  relating to drugs, e.g. their side effects or intended usage · CPC title

• G16H20/10

  relating to drugs or medications, e.g. for ensuring correct administration to patients · CPC title

• G16H10/60 Primary

  for patient-specific data, e.g. for electronic patient records · CPC title