System and method for managing and reconciling asynchronous patient data

• US 20030220821A1
• Filed: 04/30/2003
• Published: 11/27/2003
• Est. Priority Date: 04/30/2002
• Status: Abandoned Application

• Current Assignee: Epic Systems Corporation
• Original Assignee: Epic Systems Corporation
• Inventors: Giesler, Andy, Walter, Ervin
• Application Number:
  US10/428,039
• Publication Number:
  US 20030220821A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records

Abstract

A method of managing asynchronous patient data in a healthcare setting including entering into an asynchronous operation between a client device and a patient health record repository, requesting access to a portion of a source patient health record, opening a temporary, unresolved patient health record, and modifying and saving the temporary record. The method also includes establishing a subsequent synchronous connection, submitting the temporary record to the repository for resolution, determining whether the temporary record can be matched to the source record in the repository, creating a new source record for the temporary record and deleting the temporary record if a match for the temporary record is not found in the repository. The method also includes updating the source record, and deleting the temporary record.

Claims

1. A method of managing asynchronous patient data in a healthcare setting comprising:

entering into an asynchronous operation between a client device and a patient health record repository when required by a system communication need, the patient health record repository storing a source patient health record;

requesting access to a portion of the source patient health record using the client device;

opening a temporary, unresolved patient health record;

modifying the requested portion of the temporary, unresolved patient health record;

saving the modified temporary, unresolved patient health record;

establishing a synchronous connection between the client device and the patient health record repository;

submitting the temporary, unresolved patient health record to the patient health record repository for resolution;

determining whether the temporary, unresolved patient health record can be matched to the source patient health record in the patient health record repository;

creating a new source patient health record for the temporary, unresolved patient health record and deleting the temporary, unresolved patient health record if a match for the temporary, unresolved patient health record is not found in the patient health record repository; and

updating the source patient health record, and deleting the temporary, unresolved patient health record.

2. The method of claim 1, comprising marking the temporary, unresolved patient health record as unresolved.

3. The method of claim 1, wherein opening the temporary, unresolved patient health record comprises opening a local version of the source patient health record.

4. The method of claim 1, wherein opening the temporary, unresolved patient health record comprises creating the temporary, unresolved patient health record when the requested portion of the source patient health record is not available locally.

5. The method of claim 1, comprising identifying a data conflict between the source patient health record and the temporary, unresolved patient health record if a match for the temporary, unresolved patient health record is found in the patient health record repository and invoking a conflict resolution rule to resolve the data conflict.

6. The method of claim 5, comprising determining whether the match between the source patient health record and the temporary, unresolved patient health record exceed a pre-defined threshold that indicates a satisfactory match.

7. The method of claim 6, comprising submitting the temporary, unresolved patient health record to a resolution work queue for later evaluation by a user.

8. The method of claim 5, comprising submitting the temporary, unresolved patient health record to a resolution work queue for later evaluation by a user when the conflict resolution rule does not resolve the data conflict.

9. The method of claim 8, comprising allowing the user to perform both a record-level resolution and an item-level resolution.

10. A method of managing asynchronous patient data in a healthcare setting comprising:

entering into an asynchronous operation between a client device and a patient health record repository, the patient health record repository storing a source patient health record;

requesting access to a portion of the source patient health record using the client device;

opening a corresponding local temporary unresolved patient health record;

modifying the requested portion of the local temporary unresolved patient health record;

saving the modified local temporary unresolved patient health record;

establishing a synchronous connection between the client device and the patient health record repository;

submitting the local temporary unresolved patient health record to the patient health record repository for resolution;

matching the local temporary unresolved patient health record to the source patient health record in the patient health record repository;

updating the source patient health record; and

deleting the local temporary unresolved patient health record.

11. The method of claim 10, comprising entering into the asynchronous operation when required by a system communication need.

12. The method of claim 10, comprising marking the local temporary unresolved patient health record as unresolved.

13. The method of claim 10, comprising identifying a data conflict between the source patient health record and the local temporary unresolved patient health record, and invoking a conflict resolution rule to resolve the data conflict.

14. The method of claim 13, comprising submitting the local temporary unresolved patient health record to a resolution work queue for later evaluation by a user when the conflict resolution rule does not resolve the data conflict.

15. The method of claim 13, comprising allowing the user to perform an item-level resolution.

16. A method of managing asynchronous patient data in a healthcare setting comprising:

entering into an asynchronous operation between a client device and a patient health record repository, the patient health record repository storing a source patient health record;

creating a temporary, unresolved patient health record;

saving the temporary, unresolved patient health record;

establishing a synchronous connection between the client device and the patient health record repository;

submitting the temporary, unresolved patient health record to the patient health record repository for resolution;

determining whether the temporary, unresolved patient health record can be matched to the source patient health record in the patient health record repository;

saving the temporary, unresolved patient health record as a new source patient health record in the patient health record repository and deleting the temporary, unresolved patient health record if a match for the temporary, unresolved patient health record is not found in the patient health record repository; and

performing a number of actions if a match for the temporary, unresolved patient health record is found in the patient health record repository, including;

updating the source patient health record; and

deleting the temporary, unresolved patient health record.

17. The method of claim 16, comprising entering into the asynchronous operation when required by a system communication need.

18. The method of claim 16, comprising marking the temporary unresolved patient health record as unresolved.

19. The method of claim 16, wherein performing the number of actions comprises identifying a data conflict between the source patient health record and the temporary, unresolved patient health record, and invoking a conflict resolution rule to resolve the data conflict.

20. The method of claim 19, comprising submitting the temporary unresolved patient health record to a resolution work queue for later evaluation by a user when the conflict resolution rule does not resolve the data conflict.

21. The method of claim 20, comprising allowing the user to perform a record-level resolution.

22. The method of claim 16, comprising determining whether the match between the source patient health record and the temporary, unresolved patient health record exceed a pre-defined threshold that indicates a satisfactory match.

23. The method of claim 22, comprising submitting the temporary unresolved patient health record to a resolution work queue for later evaluation by a user when the match does not indicate a satisfactory match.

24. A system for managing asynchronous patient data in a healthcare setting comprising:

means for entering into an asynchronous operation between a client device and a database when required by a system communication need, the database storing a source patient health record;

means for requesting access to a portion of the source patient health record using the client device;

means for opening a temporary, unresolved patient health record;

means for modifying the requested portion of the temporary, unresolved patient health record;

means for saving the modified temporary, unresolved patient health record;

means for submitting the temporary, unresolved patient health record to the database for resolution;

means for determining whether the temporary, unresolved patient health record can be matched to the source patient health record in database;

means for creating a new source patient health record for the temporary, unresolved patient health record and deleting the temporary, unresolved patient health record if a match for the temporary, unresolved patient health record is not found in the database;

means for updating the source patient health record; and

means for deleting the temporary, unresolved patient health record.

25. The system of claim 24, comprising means for marking the temporary, unresolved patient health record as unresolved.

26. The system of claim 24, wherein opening the temporary, unresolved patient health record comprises a means for opening a local version of the source patient health record.

27. The system of claim 24, wherein opening the temporary, unresolved patient health record comprises a means for creating the temporary, unresolved patient health record when the requested portion of the source patient health record is not available locally.

28. The system of claim 24, comprising means for identifying a data conflict between the source patient health record and the temporary, unresolved patient health record if a match for the temporary, unresolved patient health record is found in the database, and means for invoking a conflict resolution rule to resolve the data conflict.

29. The system of claim 28, comprising means for determining whether the match between the source patient health record and the temporary, unresolved patient health record exceed a pre-defined threshold that indicates a satisfactory match.

30. The system of claim 28, comprising means for submitting the temporary, unresolved patient health record to a resolution work queue for later evaluation by a user when the conflict resolution rule does not resolve the data conflict.

31. The system of claim 28, comprising means for allowing the user to perform both a record-level resolution and an item-level resolution.

32. The system of claim 24, comprising means for establishing a synchronous connection between the client device and database.

33. An article comprising a machine-accessible medium having stored thereon instructions that, when executed by a machine, cause the machine to:

enter into an asynchronous operation between a client device and a patient health record repository, wherein the patient health record repository is configured to store a source patient health record;

request access to a portion of the source patient health record using the client device;

open a corresponding local temporary unresolved patient health record;

modify the requested portion of the local temporary unresolved patient health record;

save the modified local temporary unresolved patient health record;

establish a synchronous connection between the client device and the patient health record repository;

submit the local temporary unresolved patient health record to the patient health record repository for resolution;

match the local temporary unresolved patient health record to the source patient health record in the patient health record repository;

update the source patient health record; and

delete the local temporary unresolved patient health record.

34. The article of claim 33, having further instructions that, when executed by the machine, cause the machine to enter into the asynchronous operation when required by a system communication need.

35. The article of claim 33, having further instructions that, when executed by the machine, cause the machine to mark the local temporary unresolved patient health record as unresolved.

36. The article of claim 33, having further instructions that, when executed by the machine, cause the machine to identify a data conflict between the source patient health record and the local temporary unresolved patient health record and invoke a conflict resolution rule to resolve the data conflict.

37. The article of claim 34, having further instructions that, when executed by the machine, cause the machine to submit the local temporary unresolved patient health record to a resolution work queue for later evaluation by a user when the conflict resolution rule does not resolve the data conflict.

38. The article of claim 34, having further instructions that, when executed by the machine, cause the machine to allow the user to perform an item-level resolution.

39. A method of managing asynchronous patient data in a heal thc are setting comprising:

providing an asynchronous mode of operation in a client device responsive to an unavailability of a synchronous connection to a patient health record;

opening a temporary, unresolved patient health record;

receiving a modification to a portion of the temporary, unresolved patient health record to create a modified, temporary unresolved patient health record;

communicating the modified, temporary, unresolved patient health record to a patient health record repository for resolution;

receiving an acknowledgement of resolution of the patient health record, the acknowledgment being an indication that the patient health record has been resolved in accordance with a resolution criteria; and

deleting the modified, temporary unresolved patient health record responsive to receipt of the acknowledgement.

40. The method of claim 39, wherein opening the temporary, unresolved patient health record comprises opening a local version of the source patient health record.

41. The method of claim 39, wherein opening the temporary, unresolved patient health record comprises creating the temporary, unresolved patient health record when the requested portion of the source patient health record is not available locally.

42. The method of claim 39, wherein receiving the indication that the patient health record has been resolved in accordance with the resolution criteria comprises determining whether the temporary, unresolved patient health record can be matched to a source patient health record in the patient health record repository.

43. An article comprising a machine-accessible medium having stored thereon instructions that, when executed by a machine, cause the machine to:

provide an asynchronous mode of operation in a client device responsive to an unavailability of a synchronous connection to a patient health record;

open a temporary, unresolved patient health record;

receive a modification to a portion of the temporary, unresolved patient health record to create a modified, temporary unresolved patient health record;

communicate the modified, temporary, unresolved patient health record to a patient health record repository for resolution;

receive an acknowledgement of resolution of the patient health record, the acknowledgment being an indication that the patient health record has been resolved in accordance with a resolution criteria; and

delete the modified, temporary unresolved patient health record responsive to receipt of the acknowledgement.

44. The article of claim 43, having further instructions that, when executed by the machine, cause the machine to open a local version of the source patient health record.

45. The article of claim 43, having further instructions that, when executed by the machine, cause the machine to create the temporary, unresolved patient health record when the requested portion of the source patient health record is not available locally.

46. The article of claim 43, having further instructions that, when executed by the machine, cause the machine to determine whether the temporary, unresolved patient health record can be matched to a source patient health record in the patient health record repository.

47. A method of managing asynchronous patient data in a healthcare setting including a client device operable in an asynchronous mode to create temporary, unresolved patient health record data comprising:

receiving a temporary, unresolved patient health record from a client device;

determining whether the temporary, unresolved patient health record can be matched to the source patient health record in a patient health record repository;

creating a new source patient health record for the temporary, unresolved patient health record and deleting the temporary, unresolved patient health record if a match for the temporary, unresolved patient health record is not found in the patient health record repository;

updating the patient health record based upon the temporary, unresolved patient health record; and

communicating an acknowledgment to the client device.

48. The method of claim 47, wherein updating the patient health record comprises identifying a data conflict between the source patient health record and the temporary, unresolved patient health record if a match for the temporary, unresolved patient health record is found in the patient health record repository, and resolving the data conflict.

49. The method of claim 48, wherein resolving the data conflict comprises invoking a conflict resolution rule to resolve the data conflict.

50. The method of claim 48, wherein resolving the data conflict comprises submitting the temporary, unresolved patient health record to a resolution work queue for later evaluation by a user.

51. An article comprising a machine-accessible medium having stored thereon instructions that, when executed by a machine, cause the machine to:

receive a temporary, unresolved patient health record from a client device;

determine whether the temporary, unresolved patient health record can be matched to the source patient health record in a patient health record repository;

create a new source patient health record for the temporary, unresolved patient health record and delete the temporary, unresolved patient health record if a match for the temporary, unresolved patient health record is not found in the patient health record repository;

update the patient health record based upon the temporary, unresolved patient health record; and

communicate an acknowledgment to the client device.

52. The article of claim 51, having further instructions that, when executed by the machine, cause the machine to identify a data conflict between the source patient health record and the temporary, unresolved patient health record if a match for the temporary, unresolved patient health record is found in the patient health record repository, and resolve the data conflict.

53. The article of claim 52, having further instructions that, when executed by the machine, cause the machine to invoke a conflict resolution rule to resolve the data conflict.

54. The article of claim 52, having further instructions that, when executed by the machine, cause the machine to submit the temporary, unresolved patient health record to a resolution work queue for later evaluation by a user.