MODULE AND SYSTEM FOR MEDICAL INFORMATION MANAGEMENT

• US 20140316819A1
• Filed: 07/03/2014
• Published: 10/23/2014
• Est. Priority Date: 10/12/2012
• Status: Active Grant

• Current Assignee: Baxter Healthcare SA (Baxter International Inc.), Baxter International Inc.
• Original Assignee: True Process, Inc. (Baxter International Inc.)
• Inventors: Dunsirn, Todd, Frede, Doug, Downey, Charles, Larsen, Kristian Lars, Klotz, Tony
• Granted Patent: US 10,535,423 B2
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: A61M 2205/3553 remote, e.g. between patient's home and doctor's office
• CPC Class Codes: A61M 2205/3561 local, e.g. within room or hospital
• CPC Class Codes: A61M 2205/502 User interfaces, e.g. screens or keyboards
• CPC Class Codes: A61M 2205/52 with memories providing a history of measured variating parameters of apparatus or patient
• CPC Class Codes: A61M 5/142 Pressure infusion, e.g. using pumps
• CPC Class Codes: A61M 5/1723 using feedback of body parameters, e.g. blood-sugar, pressure measurement of body parameters A61B5/00
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring

Abstract

A computer module for managing medical information is described. Aspects of the invention provide a “binding” or association process for mapping information from a patient, including at the bedside, to medical devices and/or locations containing medical devices. This may advantageously allow combining all patient-bound device data in a single repository and effectively enable viewing of all patient data in one location. Accordingly, numerous discrete device data with respect to a single patient may be captured, including from among differing medical device types, and conveniently stored together as part of an intelligent data warehouse for efficient retrieval, updating, processing, including with respect to data analytics, display and/or other advantageous features. A medical device communication system is also described.

Claims

1. A computer module for managing medical information stored in a non-transient medium, the module executable on an electronic computer operable to:

(a) provide a data structure mapping unique patient identifiers to unique medical device identifiers;

(b) receive an electronic message from each of at least two medical devices of different types, each medical device providing a medical device identifier, and each message including a patient measurement value;

(c) link at least two of the received messages from the medical devices of different types based on the medical device identifiers of the received messages mapping to a common patient identifier in the data structure; and

(d) store the patient measurement values of the linked messages in a common storage element.

2. The module of claim 1, further comprising to retrieve the patient measurement values of the linked messages upon receiving the common patient identifier.

3. The module of claim 1, further comprising to send the patient measurement values of the linked messages to an analytics module for determining analytic information about the patient based on the patient measurement values.

4. The module of claim 1, further comprising to periodically receive messages from at least one of the medical devices.

5. The module of claim 4, wherein the patient measurement values of the periodically received, messages provide at least one of a heartbeat measurement, a blood pressure measurement and a drug delivery measurement.

6. The module of claim 4, wherein the periodically received messages are received every 24 hours or less.

7. The module of claim 1, further comprising to receive update information with respect to a patient identifier and to update the data structure accordingly.

8. The module of claim 7, wherein the update information is provided via an HL7 ADT (Admit Discharge Transfer) feed.

9. The module of claim 7, wherein the data structure is updated by removing a mapping between a patient identifier and a medical device identifier.

10. The module of claim 1, wherein each medical device also provides a location identifier and the data structure includes mapping patient identifiers to location identifiers.

11. A computer module for managing medical information stored in a non-transient medium, the module executable on an electronic computer operable to:

(a) provide a data structure mapping unique medical device identifiers to unique location identifiers;

(b) update the data structure mapping to correspond unique patient identifiers to the location identifiers;

(c) receive an electronic message from each of at least two medical devices of different types, each medical device providing a medical device identifier, and each message including a patient measurement value;

(d) link at least two of the received messages from the medical devices of different types based on the medical device identifiers of the received messages mapping to a location identifier corresponding to common patient identifier; and

(e) store the patient measurement values of the linked messages in a common storage element.

12. The module of claim 11, further comprising to send the patient measurement values of the linked messages to an analytics module for determining analytic information about the patient based on the patient measurement values.

13. The module of claim 11, further comprising to receive update information with respect to a patient identifier and to update the data structure accordingly.

14. The module of claim 13, wherein the data structure is updated by removing a mapping between a patient identifier and a location identifier.

15. The module of claim 11, wherein, each medical device also provides a medical device identifier and the data structure includes mapping patient identifiers to medical device identifiers.

16. A medical device communication system for managing medical information comprising:

a data structure for mapping unique patient identifiers to unique medical device identifiers;

a communications port for receiving electronic messages from at least two medical devices of different types, each medical device providing a medical device identifier, and each message including a patient measurement value;

a binding engine for linking at least two of the received messages from the medical devices of different types based on the medical device identifiers of the received messages being mapped to a common patient identifier in the data structure; and

a storage element for storing the patient measurement values of the linked messages in a common location.

17. The medical device communication system of claim 16, further comprising an analytics engine for receiving the patient measurement values of the linked messages to determine analytic information about the patient based on the patient measurement values.

18. The medical device communication system of claim 16, further comprising a user interface for inputting patient identifiers and medical device identifiers for mapping.

19. The medical device communication system of claim 16, wherein a user interface is provided via a tablet computer.

20. The medical device communication system of claim 16, wherein each medical device also provides location identifier and the data structure includes mapping patient identifiers to location identifiers.