Eugene Henry Clark

US Patent:

7908293, Mar 15, 2011

Filed:

Feb 14, 2008

Appl. No.:

12/031492

Inventors:

Samuel J. Aronson - Brookline MA, US
Lawrence J. Babb - North Grafton MA, US
Mollie Ullman-Cullere - Newtonville MA, US
Eugene H. Clark - Belmont MA, US

Assignee:

The General Hospital Corporation - Boston MA

International Classification:

G06F 17/00

US Classification:

707791, 707802, 707822, 707828

Abstract:

A medical laboratory report communications gateway computer system is presented. The gateway is configured to receive medical laboratory reports from a plurality of clients. The gateway uses report form data stored in a database to perform an inbound translation on the medical laboratory report to transform the medical laboratory report to a canonical form. The gateway identifies a destination client for the medical laboratory report, and determines an outbound message form based on the destination client. The gateway performs the selected outbound translation on the medical laboratory report in the canonical form to transform the medical laboratory report in the canonical form into a form useable by the destination client. The gateway then transmits the translated medical laboratory report to the destination client.

US Patent:

20110119309, May 19, 2011

Filed:

Jan 21, 2011

Appl. No.:

13/011650

Inventors:

Samuel J. Aronson - Brookline MA, US
Lawrence J. Babb - North Grafton MA, US
Mollie Ullman-Cullere - Newtonville MA, US
Eugene H. Clark - Belmont MA, US

International Classification:

G06F 7/00

US Classification:

707791, 707803, 707E17044, 707E17032

Abstract:

A gateway enables medical (including genetic and genomic) laboratories and health care providers (collectively “clients”) to communicate electronic messages with each other without developing and maintaining an interface for each peer. The gateway translates messages sent between the parties. The gateway receives messages from each sender in a form, and containing diagnostic codes, preferred by the sender. For each received message, the gateway ascertains an intended receiving client. Each client may specify one or more receivers (such as applications) that are to receive messages sent to the client, as well as a separate form, and optionally a set of codes, for each receiver. For each receiver, the gateway generates translated messages, according to the receiver's preferred form and/or codes. The gateway sends the translated messages to each of the designated receivers. The gateway may include a validation component to cheek incoming messages to ensure the messages include required information and that information values are valid or acceptable. The gateway may include an exception handler that notifies a sending client if a message from the client fails to be translated or sent correctly. The gateway may maintain a repository in which the gateway stores copies of messages the gateway sent or would have sent to clients. The gateway provides an interface, such as a secure web interface, to this repository. Clients may access messages or lists of messages, especially messages the clients are not otherwise capable of receiving, through this interface. The gateway may store copies of some of the data that flows through the gateway in a bioinformatics database, which may be automatically analyzed by the gateway or queried for research or patient care purposes.