Priority based communication and organization system

• US 10,498,687 B2
• Filed: 04/22/2016
• Issued: 12/03/2019
• Est. Priority Date: 04/23/2015
• Status: Active Grant

• Current Assignee: Fusemsk Incorporated
• Original Assignee: Teleport Med, LLC
• Inventors: Kaplan, Lee D.
• Primary Examiner(s): Serrao, Ranodhi
• Application Number:
  US15/135,967
• Publication Number:
  US 20160315898A1
• Time in Patent Office: 1,320 Days
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
• CPC Class Codes: H04L 51/043 using or handling presence information
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 51/226 Delivery according to priorities

Abstract

A method includes receiving, by a receiver device, a request sent from a transmitter device. The request is identified by a case name and at least one of a type of the request and a due date of the request. The request has a transmitter priority designated by the transmitter device. The method also includes assigning, by the receiver device, a receiver priority for the request received by the receiver device. The method also includes determining a final priority by the receiver device. The final priority is based upon a combination of the transmitter priority and the receiver priority. The method further includes handling the request within the receiver device based on the final priority.

Claims

1. A method, comprising:

receiving, by a receiver device, a request sent from a transmitter device, wherein the request is identified by a case name and at least one of a type of the request and a due date of the request, and wherein the request has a transmitter priority designated by the transmitter device;

assigning, by the receiver device, a receiver priority for the request received by the receiver device, wherein the receiver priority is based on an availability of the receiver device or a user of the receiver device;

determining a final priority by the receiver device, the final priority based upon a combination of the transmitter priority and the receiver priority;

setting, by the receiver device, one or more filters for the receiver priority, wherein the one or more filters prescribe an action to be taken with respect to the request based on a characteristic of the request regardless of the receiver priority; and

handling the request within the receiver device based on the final priority and the one or more filters;

wherein the final priority is one of high or low, wherein if the final priority is low, notification of the request is postponed for as long as the receiver priority is active and wherein if the final priority is high, a notification of the request is not postponed.

2. The method of claim 1, wherein the transmitter priority is one of normal, urgent, and critical.

3. The method of claim 1, wherein the receiver priority is one of available, busy, limited availability, and do not disturb.

4. The method of claim 3, wherein the receiver priority is assigned by selecting one of the available, busy, limited availability, and do not disturb, and setting a reminder for a period of time such that the selected one of the receiver priority remains active until the reminder expires.

5. The method of claim 1, wherein the receiver priority is assigned for an indefinite period of time.

6. The method of claim 1, wherein the one or more filters allow the receiver device to receive the request from certain people regardless of the receiver priority.

7. The method of claim 1, wherein the receiver priority is do not disturb, the final priority is low.

8. The method of claim 1, wherein if the receiver priority is busy, the final priority is high if the transmitter priority of the request is critical and the final priority is low if the transmitter priority of the request is urgent or normal.

9. The method of claim 1, wherein if the receiver priority is limited availability, the final priority is high if the transmitter priority of the request is critical or urgent and the final priority is low if the transmitter priority of the request is normal.

10. The method of claim 1, wherein if the receiver priority is available, the final priority is high.

11. A receiver device comprising:

a memory configured to store application software;

a controller; and

a receiver configured to receive a request from a transmitter device, wherein the request is identified by a case name and at least one of a type of the request and a due date of the request, and wherein the request has a transmitter priority designated by the transmitter device; and

wherein the controller is configured to;

assign the request a receiver priority, wherein the receiver priority is based on an availability of the receiver device or a user of the receiver device;

determine a final priority based upon the transmitter priority and the receiver priority;

set one or more filters for the receiver priority, wherein the one or more filters prescribe an action to be taken with respect to the request based on a characteristic of the request regardless of the receiver priority; and

manage notification of the request based upon the final priority and the one or more filters;

wherein the final priority is one of high or low, wherein if the final priority is low, notification of the request is postponed for as long as the receiver priority is active and wherein if the final priority is high, a notification of the request is not postponed.

12. The receiver device of claim 11, wherein the receiver device is a smart computing device.

13. The receiver device of claim 11, wherein the request is received through the application software.

14. A non-transitory computer-readable medium having instructions stored thereon that, upon execution by a computing device, cause the computing device to perform operations, the instructions comprising:

instructions to receive a request from a transmitter device, wherein the request is identified by a case name and at least one of a type of the request and a due date of the request, and wherein the request has a transmitter priority designated by the transmitter device;

instructions to assign a receiver priority to the request, wherein the receiver priority is based on an availability of a receiver device or a user of the receiver device;

instructions to determine a final priority based at least in part on the transmitter priority and the receiver priority;

instructions to set one or more filters for the receiver priority, wherein the one or more filters prescribe an action to be taken with respect to the request based on a characteristic of the request regardless of the receiver priority; and

instructions to manage notification of the request based upon the final priority and the one or more filters;

wherein the final priority is one of high or low, wherein if the final priority is low, notification of the request is postponed for as long as the receiver priority is active and wherein if the final priority is high, a notification of the request is not postponed.

15. The non-transitory computer-readable medium of claim 14, wherein in addition to the transmitter priority, the request includes at least one of a case name, a type of request, a due date, text notes, audio notes, video notes, and photographic notes.

16. The non-transitory computer-readable medium of claim 14, wherein the request is used by at least one health care practitioner to communicate with at least one caregiver to facilitate care of at least one patient.

17. The non-transitory computer-readable medium of claim 14, wherein the instructions are accessible from a mobile platform or a web based platform.

18. The non-transitory computer-readable medium of claim 14, further comprising instructions to assign a date and time stamp to the request.

19. The non-transitory computer-readable medium of claim 14, further comprising instructions to at least one of add a new case, add participants to a case, add updates to a case, and keep track of time spent on a case.