Management of clinical data exceptions in clinical information systems

• US 20070100659A1
• Filed: 10/27/2005
• Published: 05/03/2007
• Est. Priority Date: 10/27/2005
• Status: Abandoned Application

• Current Assignee: IDX Investment Corporation (General Electric Company)
• Original Assignee: IDX Investment Corporation (General Electric Company)
• Inventors: Preiss, Erik
• Application Number:
  US11/261,333
• Publication Number:
  US 20070100659A1
• Time in Patent Office: Days
• US Class Current: 705/2
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 10/20 for electronic clinical trials or questionnaires

Abstract

A clinical data exception management system receives clinical messages from a third party system, applies data validation rules to perform validation of various components of the received clinical messages, and stores the invalidated message and a rule (or rules) that invalidated the message. The system then resolves an exception and performs validation of the original message. As a result, the system captures important clinical information rather than requiring the third party system to retransmit the message.

Claims

1. A method for validating a patient-related clinical message received by a clinical information system, the message including a plurality of data components, the method comprising:

applying data validation rules to the message components to validate the message;

responsive to at least one message component in the clinical message violating at least one data validation rule;

invalidating the message, and

storing the invalidated message in association with at least one rule that invalidated the message;

receiving a user input to display patient data;

providing, in response to the user input, the invalidated clinical message associated with the requested patient data and the at least one rule that invalidated the message;

receiving a user modifications to the components of the invalidated clinical message; and

applying the data validation rules to the modified message components to validate the message.

2. The method of claim 1, further comprising:

extracting message components from the invalidated clinical message;

generating a message exception record;

populating the message exception record with the extracted message components;

populating the message exception record with the at least one rule that invalidated the message; and

attaching the invalidated message to the message exception record.

3. The method of claim 1, wherein the message components in the received clinical message are in a first format and the system maintains data in a second format, the method further comprising:

translating the message components of the invalidated message from the first format to the second format.

4. The method of claim 1, further comprising providing an indication in the message exception record when the modified message was validated.

5. The method of claim 1, further comprising:

responsive to none of the message components in the clinical message violating validation rules;

extracting message components from the validated clinical message, and

storing the extracted message components as validated data.

6. The method of claim 1, further comprising:

providing, in response to the user input, requested patient data that includes validated and non-validated patient data; and

allowing the user to access the received clinical message associated with the non-validated patient data and the at least one rule that invalidated the received clinical message.

7. The method of claim 6, further comprising providing an indication that the displayed patient data includes non-validated data.

8. The method of claim 1, further comprising:

responsive to none of the message components in the modified clinical message violating data validation rules;

extracting message components from the modified clinical message, and

storing the extracted message components as validated data.

9. A system for validating a patient-related clinical message received by a clinical information system, the message including a plurality of data components, the system comprising:

a data validation engine adapted to;

apply data validation rules to the message components to validate the message, and

responsive to at least one message component in the clinical message violating at least one data validation rule, invalidate the message and store the non-validated message and the at least one rule that invalidated the message;

a data store adapted to store the non-validated message and the at least one rule that invalidated the message;

a record display user interface engine adapted to display patient data in response to a user request; and

an exception resolution engine adapted to provide to the user the invalidated clinical message associated with the requested patient data and the at least one rule that invalidated the message, to receive a user modification to the components of the invalidated clinical message, and to apply the data validation rules to the modified message components to validate the message.

10. The system of claim 9, wherein the data validation engine is further adapted to:

extract message components from the invalidated clinical message,

generate a message exception record,

populate the message exception record with the extracted message components,

populate the message exception record with the at least one rule that invalidated the message, and

attach the invalidated message to the message exception record.

11. The system of claim 9, wherein the message components in the received clinical message are in a first format and the system maintains data in a second format, wherein the data validation engine is further adapted to:

translate the message components of the invalidated message from the first format to the second format.

12. The system of claim 9, wherein the exception resolution engine is further adapted to provide an indication in the message exception record when the modified message was validated.

13. The system of claim 9, wherein the data validation engine is further adapted to:

extract message components from the validated clinical message, and

store the extracted message components in the data store as validated data, responsive to none of the message components in the clinical message violating validation rules.

14. The system of claim 9, wherein the patient record user interface engine is further adapted to provide an indication that the displayed patient data includes non-validated data.

15. A computer program product comprising:

a computer-readable medium having computer program code embodied therein for validating a patient-related clinical message received by a clinical information system, the message including a plurality of data components, the computer program code adapted to;

apply data validation rules to the message components to validate the message;

responsive to at least one message component in the clinical message violating at least one data validation rule;

 

invalidate the message, and

 

store the invalidated message in association with at least one rule that invalidated the message;

receive a user input to display patient data;

provide, in response to the user input, the invalidated clinical message associated with the requested patient data and the at least one rule that invalidated the message;

receive a user modification to the components of the invalidated clinical message; and

apply the data validation rules to the modified message components to validate the message.