MEDICAL COMMUNICATION PROTOCOL TRANSLATOR

• US 20160283665A1
• Filed: 12/18/2015
• Published: 09/29/2016
• Est. Priority Date: 03/04/2009
• Status: Active Grant

• Current Assignee: Masimo Corporation
• Original Assignee: Masimo Corporation
• Inventors: Sampath, Anand, Muhsin, Bilal, Housel, Peter Scott
• Granted Patent: US 11,145,408 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 40/00 ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 50/50 for simulation or modelling of medical disorders

Abstract

A medical communication protocol translator can be configured to facilitate communication between medical devices that are programmed to communicate with different protocol formats. The medical communication protocol translator can receive an input message formatted according to a first protocol format from a first medical device and to output an output message formatted according to a second protocol format supported by a second medical device using a set of translation rules. For example, a medical communication protocol translator can receive an input message from a hospital information system formatted according to a first HL7 protocol format and output an output message formatted according to a second HL7 protocol format based on a comparison with the set of translation rules.

Claims

1. A method for facilitating communication between first and second medical devices within a medical information network, the method comprising:

receiving a first input message from a first medical device, the first medical device having generated said input message according to a first communication protocol, said input message identifying a second medical device as an intended recipient of the input message;

translating said input message into an output message by applying one or more translation rules, said second medical device being configured to receive and process said output message; and

providing said output message to the second medical device.

2. The method of claim 1, wherein the first communication protocol comprises the HL7 protocol.

3. The method of claim 1, further comprising generating said translation rules based upon said input message.

4. The method of claim 1, wherein said translating comprises rearranging at least a portion of the input message.

5. The method of claim 1, wherein said providing comprises providing said output message to the second medical device over a network.

6. The method of claim 1, wherein said providing comprises providing said output message to the second medical device over the Internet.

7. The method of claim 1, further comprising:

receiving a second input message from the second medical device, the second medical device having generated said second input message according to a second communication protocol;

translating said second input message into a second output message by applying different translation rules, said first medical device being configured to receive and process said second output message; and

providing said second output message to the first medical device.

8. A medical device message translator configured to facilitate communication between first and second medical devices within a medical information network, the translator comprising:

a communication interface module configured to receive a first input message from a first medical device, the first medical device having generated said input message according to a first communication protocol, said input message identifying a second medical device as an intended recipient of the input message;

a rules module, configured to store one or more predetermined translation rules; and

a translation module configured to translate said input message into an output message by applying one or more translation rules retrieved from said rules module, said second medical device being configured to receive and process said output message.

9. A method for converting messages communicated between medical devices and a hospital or clinical information system, the method comprising:

receiving an input message from a hospital information system that comprises electronic patient medical records, the content of the input message being formatted according to a first set of formatting rules allowed under a medical electronic communication protocol;

comparing the input message to a set of transformation rules;

generating an output message, the content of the output message being re-formatted according to a second set of formatting rules allowed under the medical electronic communication protocol, wherein the conversion rules control the re-formatting of the content of the output message so as to comply with the second set of formatting rules; and

outputting the output message to a medical, device.

10. The method of claim 9, wherein the transformation rules are manually inputted.

11. The method of claim 9, wherein the transformation rules are automatically generated.

12. The method of claim 9, further comprising requesting a message and automatically determining a type of formatting to be implemented based on said message.

13. The method of claim 9, wherein the first set of formatting rules are implemented using HL7.

14. The method of claim 9, wherein the comparing includes parsing the input message.

15. The method of claim 9, wherein the comparing includes separating formatting and content of input message.

16. The method of claim 9, wherein the input message and output message use the same protocol but have different formats.

17. The method of claim 9, wherein the input message and output message use different protocol.

18. The method of claim 9, further comprising determining whether the input message complies with the HL7 standard.

19. The method of claim 9, wherein said generating comprises substituting field, delimiter characters and/or changing field positions.

20. The method of claim 9, wherein the message comprises an admit discharge transfer (ADT) message.

21. The method of claim 9, further comprising determining field repeatability, cardinality, position, usage status, data type, and/or length.

22. The method of claim 9, further comprising reading rules from updatable or user configurable file.

23-49. -49. (canceled)