Rule model for healthcare information

• US 8,244,555 B2
• Filed: 07/17/2006
• Issued: 08/14/2012
• Est. Priority Date: 07/17/2006
• Status: Active Grant

• Current Assignee: Merative US LP
• Original Assignee: Merge eClinical, Inc. (International Business Machines Corporation)
• Inventors: Masson, Arnaud, Demoustier, Romain
• Primary Examiner(s): Koppikar, Vivek
• Assistant Examiner(s): WINSTON III, EDWARD B
• Application Number:
  US12/160,479
• Publication Number:
  US 20090248604A1
• Time in Patent Office: 2,220 Days
• Field of Search: 705/2, 705/3, 705/4
• US Class Current: 705/2
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 50/20 for computer-aided diagnosis, e.g. based on medical expert systems
• CPC Class Codes: G16H 50/50 for simulation or modelling of medical disorders

Abstract

Healthcare information data is managed by, on a computer, maintaining a model of a state of a system based on the healthcare information, receiving a transaction representing a change to the system, determining that the change complies with a rule, and changing the model according to the transaction.

Claims

1. A computer-implemented method of managing healthcare information data of a clinical trial, the method comprising:

storing, in a short term storage component and a long term storage component, a data model that includes elements and associated values, the elements including clinical trial data, wherein the short term storage component maintains a representation of a current state of the data model;

receiving, by a controller module, a transaction instructing a change to a first current state of the data model, wherein the transaction includes an instruction to add, remove, or change values of elements of the data model, or an instruction to change relationships between elements of the data model;

analyzing the change instructed by the transaction;

making a backup copy of a portion of the data model that is to be modified by the transaction;

generating a revised data model by implementing the received transaction and storing the revised data model in the short term storage component as a new current state;

checking the new current state against a set of rules to determine whether the revised data model violates a rule among the set of rules;

if a rule among the set of rules is violated, rejecting the transaction and using the backup copy to restore the data model in the short term storage component to the first current state; and

if a rule among the set of rules is not violated, storing the transaction in the long term storage component.

2. The method of claim 1 in which generating a revised data model comprises altering a rule in the data model.

3. The method of claim 2 in which checking the new current state against a set of rules to determine whether the revised data model violates a rule among the set of rules comprises evaluating the new current state of the data model.

4. The method of claim 3 in which checking the new current state against a set of rules to determine whether the revised data model violates a rule among the set of rules comprises

evaluating a dynamic expression including a set of operations identifying a type of modification to the first current state of the data model and an ID and wherein the dynamic expression is unique to an element to which it is attached;

and

determining that the transaction represents the modification to the data model matching the type identified by the ID attached to the element.

5. The method of claim 4 in which evaluating the dynamic expression comprises

determining a relationship between a user submitting the transaction and a set of users.

6. The method of claim 5 in which the relationship is that the user is a member of the set of users.

7. The method of claim 5 in which

the relationship is that the user is a member of a first set of users, and the relationship is satisfied if the user is a member of a second set of users that is related to the first set of users.

8. The method of claim 2 in which the new current state is checked against the set of rules after each attempt to modify the data model.

9. The method of claim 8 in which checking the new current state against a set of rules to determine whether the revised data model violates a rule among the set of rules comprises

evaluating a dynamic expression including a set of operations identifying a type of modification to the first current state of the data model and an ID and wherein the dynamic expression is unique to an element to which it is attached;

and

determining that the transaction represents the modification to the data model matching the type identified by the ID attached to the element.

10. The method of claim 4 in which evaluating the dynamic expression comprises determining a relationship between two or more of:

a value of an element in the model,

a value of an item of data external to the model,

a value of an element in the transaction, and

a result of a computation.

11. The method of claim 1 in which checking the new current state against a set of rules to determine whether the revised data model violates a rule among the set of rules comprises evaluating an expression.

12. The method of claim 11 in which the expression comprises sub-expressions, and evaluating the expression comprises evaluating each of the sub-expressions to produce results, and evaluating the expression based on the results.

13. The method of claim 11 in which the expression includes a definition of a data item, and evaluating the expression includes constructing the data item according to the definition.

14. The method of claim 1 wherein checking the new current state against a set of rules to determine whether the revised data model violates a rule among the set of rules comprises identifying a hierarchy of elements, wherein a rule among the set of rules is associated with a first element in the hierarchy, determining that a second element is subordinate to the first element and evaluating the value of the second element.

15. The method of claim 14 in which the second element is a child of the first element.

16. The method of claim 1 wherein checking the new current state against a set of rules to determine whether the revised data model violates a rule among the set of rules comprises identifying a hierarchy of elements, wherein a rule among the set of rules is associated with a first element in the hierarchy, and evaluating values of a second and third element that are each subordinate to the first element but not to each other.

17. The method of claim 16 in which at least one of the second and third elements is a child of the first element.

18. An apparatus for managing healthcare information data of a clinical trial, the apparatus comprising a computer configured to:

store, in a short term storage component and a long term storage component, a data model that includes elements and associated values, the elements including clinical trial data, wherein the short term storage component maintains a representation of a current state of the data model;

receive, by a controller module, a transaction instructing a change to a first current state of the data model, wherein the transaction includes an instruction to add, remove, or change values of elements of the data model, or an instruction to change relationships between elements of the data model;

analyze the change instructed by the transaction;

make a backup copy of a portion of the data model that is to be modified by the transaction;

generate a revised data model by implementing the received transaction and store the revised data model in the short term storage component as a new current state;

check the new current state against a set of rules to determine whether the revised data model violates a rule among the set of rules;

if a rule among the set of rules is violated, reject the transaction and use the backup copy to restore the data model in the short term storage component to the first current state; and

if a rule among the set of rules is not violated, store the transaction in the long term storage component.

19. The apparatus of claim 18 in which the computer is configured to maintain the data model by, for each transaction in a set of transactions,

if the transaction alters data in the first current state of the data model, altering corresponding data in the new current state,

if the transaction alters a rule in the first current state of the data model, altering a corresponding rule in the new current state.

20. The apparatus of claim 19 in which the computer is configured to evaluate the new current state of the data model.

21. The apparatus of claim 20 in which the computer is configured to

evaluate a dynamic expression including a set of operations identifying a type of modification to the first current state of the data model and an ID and wherein the dynamic expression is unique to an element to which it is attached;

and

determine that the transaction represents the modification to the data model matching the type identified by the ID attached to the element.

22. The apparatus of claim 21 in which the computer is configured to check the new current state against the set of rules after each attempt to modify the data model.

23. A non-transitory computer readable medium for managing healthcare information data of a clinical trial, the medium comprising instructions to cause a computer to

store, in a short term storage component and a long term storage component, a data model that includes elements and associated values, the elements including clinical trial data, wherein the short term storage component maintains a representation of a current state of the data model;

receive, by a controller module, a transaction instructing a change to a first current state of the data model, wherein the transaction includes an instruction to add, remove, or change values of elements of the data model, or an instruction to change relationships between elements of the data model;

analyze the change instructed by the transaction;

make a backup copy of a portion of the data model that is to be modified by the transaction;

generate a revised data model by implementing the received transaction and store the revised data model in the short term storage component as a new current state;

check the new current state against a set of rules to determine whether the revised data model violates a rule among the set of rules;

if a rule among the set of rules is violated, reject the transaction and use the backup copy to restore the data model in the short term storage component to the first current state; and

if a rule among the set of rules is not violated, store the transaction in the long term storage component.

24. The medium of claim 23 in which the instructions also cause the computer to maintain the data model by, for each transaction in a set of transactions,

if the transaction alters data in the first current state of the data model, altering corresponding data in the new current state,

if the transaction alters a rule in the first current state of the data model, altering a corresponding rule in the new current state.

25. The medium of claim 24 in which the instructions also cause the computer to evaluate the new current state of the data model.

26. The medium of claim 25 in which the instructions also cause the computer to

evaluate a dynamic expression including a set of operations identifying a type of modification to the first current state of the data model and an ID and wherein the dynamic expression is unique to an element to which it is attached;

and

determine that the transaction represents the modification to the data model matching the type identified by the ID attached to the element.

27. The medium of claim 23 in which the instructions cause the computer to check the new current state against the set of rules after each attempt to modify the data model.