IP Library Granted Patent US 10,372,875
Granted Patent B2
US 10,372,875 · App. 15/076,071 · Granted Aug 6, 2019

Method and apparatus for tracking context synchronization across multiple applications

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,372,875
App. No.
15/076,071
Granted
Aug 6, 2019
Kind
B2
Abstract

A method, computing device and computer program product are provided according to an example embodiment in order to track context synchronization of files operating on a plurality of participating applications. A synchronization tracking tool may receive contexts from a plurality of participating applications and provide an indication of a synchronization state based upon the timing and contexts received from the participating applications. An indication of the synchronization state may be provided to a user via a user interface in a visual and/or audible manner. The participating applications may further request synchronization state information from the synchronization tool.

Claims (53)

1. A radiology information system comprising a processor, at least one non-transitory memory having program code portions stored thereon, and a radiology information database having radiology images stored therein, the program code portions configured, upon execution, to:

receive an indication of two or more participating applications;

receive a first patient context associated with a first file in response to a first application of the two or more applications accessing the first file associated with a first patient stored in the radiology information database;

determine if the first patient context is different from patient contexts associated with other applications of the two or more participating applications;

initiate a timer in response to determining that the first patient context is different from the patient contexts associated with the other applications;

determine if the patient contexts associated with the other applications have changed to become the first patient context;

provide a first notification in response to the patient context associated with at least one of the other applications not matching the first patient context and the timer satisfying a first criterion; and

provide a second notification in response to the patient context associated with at least one of the other applications not matching the first patient context and the timer satisfying a second criterion.

2. The system of claim 1 , further comprising program code portions configured to:

provide a third notification in response to the patient contexts associated with the other applications matching the first patient context.

3. The system of claim 1 , further comprising program code portions configured to:

map the patient contexts associated with the two or more participating applications to a common patient context format.

4. The system of claim 1 , wherein the first notification comprises an in-progress notification indicating a number of the other applications associated with patient contexts not matching the first patient context.

5. The system of claim 4 , wherein the program code portions configured to provide a second notification in response to the patient context associated with at least one of the other applications not matching the first patient context comprises program code portions configured to provide an indication of a number of applications for which a patient context does not match the first patient context.

6. The system of claim 5 , further comprising program code portions configured to:

determine a severity level based on a number of other applications for which a patient context does not match the first patient context and the timer satisfying the first criterion and a number of other applications for which a patient context does not match the first patient context and the timer satisfying the second criterion; and

append information associated with one of the first notification or the second notification and the determined severity level to a study associated with the first patient.

7. An apparatus comprising a processor and at least one non-transitory memory having computer-executable program code instructions stored therein, the processor configured, in response to execution of the computer-executable program code instructions, to cause the apparatus to:

receive an indication of two or more participating applications;

receive a first patient context associated with a first file in response to a first application of the two or more applications accessing a study associated with a first patient;

determine if the first patient context is different from patient contexts associated with other applications of the two or more participating applications;

initiate a timer in response to determining that the first patient context is different from the patient contexts associated with the other applications;

determine if the patient contexts associated with the other applications have changed to become the first patient context;

provide a first notification in response to the patient context associated with at least one of the other applications not matching the first patient context and the timer satisfying a first criterion;

provide a second notification in response to the patient context associated with at least one of the other applications not matching the first patient context and the timer satisfying a second criterion; and

append information associated with one of the first notification or the second notification to the study associated with the first patient.

8. The apparatus of claim 7 , wherein the file comprises a radiology study, and wherein at least one of the two or more applications comprises a radiology image viewing application.

9. The apparatus of claim 7 , wherein the apparatus is further configured to map the patient contexts associated with the two or more participating applications to a common patient context format.

10. The apparatus of claim 7 , wherein the first notification comprises an in-progress notification indicating a number of the other applications associated with patient contexts not matching the first patient context.

11. The apparatus of claim 10 , wherein causing the apparatus to provide a second notification in response to the patient contexts associated with the other applications not matching the first patient context comprises causing the apparatus to provide an indication of a number of applications for which a patient context does not match the first patient context.

12. The apparatus of claim 11 , wherein the apparatus is further configured to:

determine a severity level based on a number of other applications for which a patient context does not match the first patient context and the timer satisfying the first criterion and a number of other applications for which a patient context does not match the first patient context and the timer satisfying the second criterion; and

include the severity level in the information appended to a study associated with the first patient.

13. The apparatus of claim 12 , wherein the apparatus is further configured to:

receive an acknowledgement of the first notification or the second notification, wherein causing the apparatus to determine the severity level is further based on whether an acknowledgment is received for the first notification or the second notification.

14. A method comprising:

receiving an indication of two or more participating applications;

receiving a first patient context associated with a first file in response to a first application of the two or more applications accessing a file associated with a first patient;

determining if the first patient context is different from patient contexts associated with other applications of the two or more participating applications;

initiating a timer in response to determining that the first patient context is different from the patient contexts associated with the other applications;

determining if the patient contexts associated with the other applications have changed to become the first patient context;

providing a first notification in response to the patient context associated with at least one of the other applications not matching the first patient context and the timer satisfying a first criterion;

providing a second notification in response to the patient context associated with at least one of the other applications not matching the first patient context and the timer satisfying a second criterion; and

appending information associated with one of the first notification or the second notification to the study associated with the first patient.

15. The method of claim 14 , wherein the study comprises a radiology study, and wherein at least one of the two or more applications comprises a radiology image viewing application.

16. The method of claim 14 , further comprising mapping the patient contexts associated with the two or more participating applications to a common patient context format.

17. The method of claim 14 , wherein the first notification comprises an in-progress notification indicating a number of the other applications associated with patient contexts not matching the first patient context.

18. The method of claim 17 , wherein providing the second notification in response to the patient contexts associated with the other applications not matching the first patient context comprises providing an indication of a number of applications for which a patient context does not match the first patient context.

19. The method of claim 18 , further comprising:

determining a severity level based on a number of the other applications for which a patient context does not match the first patient context and the timer satisfying the first criterion and a number of the other applications for which a patient context does not match the first patient context and the timer satisfying the second criterion; and

including the severity level in the information appended to the study associated with the first patient.

20. The method of claim 19 , further comprising:

receiving an acknowledgement of the first notification or the second notification, wherein determining a severity level is further based on whether an acknowledgment is received for the first notification or the second notification.

Assignments (10)
RELEASE OF SECURITY INTEREST Recorded Oct 5, 2022
From: BANK OF AMERICA, N.A.
To: CHANGE HEALTHCARE RESOURCES, LLC (FORMERLY KNOWN AS ALTEGRA HEALTH OPERATING COMPANY LLC); CHANGE HEALTHCARE SOLUTIONS, LLC; CHANGE HEALTHCARE PERFORMANCE, INC. (FORMERLY KNOWN AS CHANGE HEALTHCARE, INC.); CHANGE HEALTHCARE OPERATIONS, LLC; CHANGE HEALTHCARE HOLDINGS, INC.; CHANGE HEALTHCARE TECHNOLOGIES, LLC (FORMERLY KNOWN AS MCKESSON TECHNOLOGIES LLC); CHANGE HEALTHCARE HOLDINGS, LLC
Reel/Frame 061620/0054 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 23, 2018
From: CHANGE HEALTHCARE LLC
To: CHANGE HEALTHCARE HOLDINGS, LLC
Reel/Frame 046449/0899 →
CHANGE OF ADDRESS Recorded Mar 23, 2017
From: CHANGE HEALTHCARE LLC
To: CHANGE HEALTHCARE LLC
Reel/Frame 042082/0061 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 10, 2017
From: PF2 IP LLC
To: CHANGE HEALTHCARE LLC
Reel/Frame 041966/0356 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 9, 2017
From: MCKESSON CORPORATION
To: PF2 IP LLC
Reel/Frame 041938/0501 →
SECURITY AGREEMENT Recorded Mar 2, 2017
From: CHANGE HEALTHCARE HOLDINGS, LLC; CHANGE HEALTHCARE, INC.; CHANGE HEALTHCARE HOLDINGS, INC.; CHANGE HEALTHCARE OPERATIONS, LLC; CHANGE HEALTHCARE SOLUTIONS, LLC; ALTEGRA HEALTH OPERATING COMPANY LLC; MCKESSON TECHNOLOGIES LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 041858/0482 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2017
From: MCKESSON FINANCIAL HOLDINGS UNLIMITED COMPANY
To: MCKESSON CORPORATION
Reel/Frame 041355/0408 →
CHANGE OF NAME Recorded Jan 11, 2017
From: MCKESSON FINANCIAL HOLDINGS
To: MCKESSON FINANCIAL HOLDINGS UNLIMITED COMPANY
Reel/Frame 041329/0879 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 31, 2016
From: MCKESSON CORPORATION
To: MCKESSON FINANCIAL HOLDINGS
Reel/Frame 039887/0935 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 21, 2016
From: TANG, XIAOWEI
To: MCKESSON CORPORATION
Reel/Frame 038053/0867 →