Method and Apparatus for Implementing a Messaging Interface

1 . A method for providing a messaging interface, the method comprising:

establishing, by processing circuitry of a computing device, a first listener thread to identify incoming message traffic from a first Health Level 7 (HL7) repeater;

initializing, on the computing device, one or more device interfaces accessible to at least one application executing on the computing device;

receiving, by a network interface of the computing device, at least one message from the HL7 repeater;

in response to receiving the at least one message, associating a message queue and a second listener thread with the HL7 repeater, wherein the second listener thread includes a socket configured to listen on the network interface to receive messages from the first HL7 repeater;

associating the message queue and the second listener thread with at least one of the device interfaces;

receiving, by the network interface and via the second listener thread, another message from the HL7 repeater;

placing, by the second listener thread, the another message on the message queue; and

making the another message stored on the message queue available to the at least one application via the at least one of the device interfaces.

2 . The method of claim 1 , further comprising:

storing an association between the at least one device interface and the first HL7 repeater in a file; and

accessing, by the application, the file to identify the first HL7 repeater associated with the at least one device interface.

3 . The method of claim 1 , further comprising:

retrieving, by the application, the another message via the device interface; and

removing the another message from the message queue in response to the application retrieving the another message.

4 . The method of claim 1 , further comprising converting, by the second listener thread, the another message to a markup representation prior to placing the another message on the message queue.

5 . The method of claim 1 , further comprising disabling conversion of the another message to a markup representation in response to receiving an ioctl( ) system call.

6 . The method of claim 1 , further comprising:

receiving a second message from a second HL7 repeater; and

associating the second HL7 repeater with a second device interface, a second message queue, and a third listener thread.

7 . The method of claim 1 , wherein the first listener thread is executed as part of a kernel module.

8 . The method of claim 1 , wherein the socket is a transmission control protocol (TCP) socket.

9 . The method of claim 1 , wherein the application is at least one of a medical records application, a hospital admissions system, or a picture archive and communications system.

10 . An apparatus for implementing a message interface, the apparatus comprising:

a network interface;

messaging management circuitry configured to:

establish a first listener thread to identify incoming message traffic from a first Health Level 7 (HL7) repeater;

initialize one or more device interfaces accessible to at least one application executing on the computing device and managed by device management circuitry;

receive, by the network interface, at least one message from the first HL7 repeater;

in response to receiving the at least one message, to associate a message queue and a second listener thread with the first HL7 repeater, wherein the second listener thread includes a socket configured to listen on the network interface to receive messages from the HL7 repeater; and

associate the message queue and the second listener thread with at least one of the device interfaces;

the device management circuitry configured to:

receive, by the network interface and via the second listener thread, another message from the HL7 repeater;

place the another message on the message queue;

make message contents of the message queue available via the at least one of the device interfaces; and

medical function circuitry configured to:

access the device interface to obtain the another message; and

implement the functionality of at least one application.

11 . The apparatus of claim 10 , wherein the messaging management circuitry is further configured to store an association between the at least one device interface and the HL7 repeater in a file, and the medical function circuitry is further configured to access the file to identify the HL7 repeater associated with the at least one device interface.

12 . The apparatus of claim 10 , wherein the medical function circuitry is further configured to retrieve the another message via the device interface, and the device management circuitry is further configured to remove the another message from the message queue in response to the application retrieving the another message.

13 . The apparatus of claim 10 , wherein the device management circuitry is further configured to convert the another message to a markup representation prior to placing the another message on the message queue.

14 . The apparatus of claim 10 wherein the device management circuitry is further configured to disable conversion of the another message to a markup representation in response to receiving an ioctl( ) system call.

15 . The apparatus of claim 10 , wherein the messaging management circuitry is further configured to:

receive a second message from a second HL7 repeater; and

associate the different HL7 repeater with a second device interface, a second message queue, and a third listener thread.

16 . The apparatus of claim 10 , wherein the first listener thread is executed as part of a kernel module.

17 . The apparatus of claim 10 , wherein the socket is a transmission control protocol (TCP) socket.

18 . The apparatus of claim 10 , wherein the application is at least one of a medical records application, a hospital admissions system, or a picture archive and communications system.

19 . A non-transitory computer readable storage medium comprising instructions that, when executed by a processor, cause the processor to configure an apparatus to:

establish a first listener thread to identify incoming message traffic from a first Health Level 7 (HL7) repeater;

initialize one or more device interfaces accessible to at least one application executing on the computing device;

receive, by a network interface of the computing device, at least one message from the HL7 repeater;

in response to receiving the at least one message, associate a message queue and a second listener thread with the HL7 repeater, wherein the second listener thread includes a socket configured to listen on the network interface to receive messages from the first HL7 repeater;

associate the message queue and the second listener thread with at least one of the device interfaces;

receive, by the network interface and via the second listener thread, another message from the HL7 repeater;

place, by the second listener thread, the another message on the message queue; and

make the another message stored on the message queue available to the at least one application via the at least one of the device interfaces.

20 . The computer readable storage medium of claim 19 , wherein the first listener thread is executed as part of a kernel module.