Processing delay predictions based on queue assessments

• US 10,673,784 B1
• Filed: 08/22/2017
• Issued: 06/02/2020
• Est. Priority Date: 08/25/2016
• Status: Active Grant

• Current Assignee: C-HCA, Inc.
• Original Assignee: C-HCA, Inc.
• Inventors: Perez Rodreguez, Gabriel O., Azadi, Fariba Borjian
• Primary Examiner(s): Jacobs, Lashonda T
• Application Number:
  US15/683,151
• Time in Patent Office: 1,015 Days
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests

Abstract

Systems and methods of processing delay predictions based on queue assessments are described herein. In some examples, the queues may correspond to queues for usage and/or access of resources. A central server can manage one or more queues for the resources. Queue elements can correspond to requests for performing a task, which can include a task for using and/or accessing a resource. The queue elements can remain in the queue until processing of the task is initiated.

Claims

1. A computer-implemented method comprising:

receiving, at a server, a first communication from a device of an incoming patient, wherein the first communication corresponds to a request for a predicted wait time at at least one medical facility;

identifying, based on the first communication, a location of the device;

identifying, based on the location of the device, a medical facility to associate with the request;

identifying, based on the first communication, a medical condition being experienced by the incoming patient;

identifying at least one resource type that is associated with the medical condition being experienced by the incoming patient, wherein the at least one resource type comprises at least one of a type of medical professional, a type of medical equipment, a type of medical supplies, a type of room in the medical facility, or a type of medicine;

retrieving a plurality of queue elements that are associated with the medical facility, wherein each queue element of the plurality of queue elements corresponds to an instance for which service at the medical facility has been requested by a respective existing patient;

predicting, for each queue element, whether the service that has been requested by the respective existing patient will use a resource of each of the identified resource types that are associated with the medical condition being experienced by the incoming patient;

generating, for each of the identified resource types that are associated with the medical condition being experienced by the incoming patient, a predicted resource wait time;

predicting a wait time for the incoming patient at the medical facility based on each predicted resource wait time; and

transmitting, from the server to the device, a second communication that includes the wait time for the incoming patient at the medical facility.

2. The computer-implemented method according to claim 1, wherein the request is an implicit request indicating that an event is occurring or requesting directions to the medical facility.

3. The computer-implemented method according to claim 1, wherein the location of the device is identified based on location data or metadata within the first communication.

4. The computer-implemented method according to claim 1, wherein each queue element comprises at least one of identifying information about the respective existing patient, the medical condition being experienced by the respective existing patient, or a type of treatment for the medical condition being experienced by the respective existing patient.

5. The computer-implemented method according to claim 1, wherein the request indicates a change in a physiological factor of the incoming patient that is above a threshold.

6. The computer-implemented method according to claim 1, wherein the medical condition being experienced by the incoming patient is identified based on data or metadata within the first communication.

7. A system comprising:

one or more data processors; and

a non-transitory computer readable storage medium containing instructions that, when executed on the one or more data processors, cause the one or more data processors to perform actions including;

receiving, at a server, a first communication from a device of an incoming patient, wherein the first communication corresponds to a request for a predicted wait time at at least one medical facility;

identifying, based on the first communication, a location of the device;

identifying, based on the location of the device, a medical facility to associate with the request;

identifying, based on the first communication, a medical condition being experienced by the incoming patient;

identifying at least one resource type that is associated with the medical condition being experienced by the incoming patient, wherein the at least one resource type comprises at least one of a type of medical professional, a type of medical equipment, a type of medical supplies, a type of room in the medical facility, or a type of medicine;

retrieving a plurality of queue elements that are associated with the medical facility, wherein each queue element of the plurality of queue elements corresponds to an instance for which service at the medical facility been requested by a respective existing patient;

predicting, for each queue element, whether the service that has been requested by the respective existing patient will use a resource of each of the identified resource types that are associated with the medical condition being experienced by the incoming patient;

generating, for each of the identified resource types that are associated with the medical condition being experienced by the incoming patient, a predicted resource wait time;

predicting a wait time for the incoming patient at the medical facility based on each predicted resource wait time; and

transmitting, from the server to the device, a second communication that includes the wait time for the incoming patient at the medical facility.

8. The system according to claim 7, wherein the request is an implicit request indicating that an event is occurring or requesting directions to the medical facility.

9. The system according to claim 7, wherein the location of the device is identified based on location data or metadata within the first communication.

10. The system according to claim 7, wherein each queue element comprises at least one of identifying information about the respective existing patient, the medical condition being experienced by the respective existing patient, or a type of treatment for the medical condition being experienced by the respective existing patient.

11. The system according to claim 7, wherein the request indicates a change in a physiological factor of the incoming patient that is above a threshold.

12. The system according to claim 7, wherein the medical condition being experienced by the incoming patient is identified based on data or metadata within the first communication.

13. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium, including instructions configured to cause one or more data processors to perform actions including:

receiving, at a server, a first communication from a device of an incoming patient, wherein the first communication corresponds to a request for a predicted wait time at at least one medical facility;

identifying, based on the first communication, a location of the device;

identifying, based on the location of the device, a medical facility to associate with the request;

identifying, based on the first communication, a medical condition being experienced by the incoming patient;

identifying at least one resource type that is associated with the medical condition being experienced by the incoming patient, wherein the at least one resource type comprises at least one of a type of medical professional, a type of medical equipment, a type of medical supplies, a type of room in the medical facility, or a type of medicine;

retrieving a plurality of queue elements that are associated with the medical facility, wherein each queue element of the plurality of queue elements corresponds to an instance for which service at the medical facility has been requested by a respective existing patient;

predicting, for each queue element, whether the service that has been requested by the respective existing patient will use a resource of each of the identified resource types that are associated with the medical condition being experienced by the incoming patient;

generating, for each of the identified resource types that are associated with the medical condition being experienced by the incoming patient, a predicted resource wait time;

predicting a wait time for the incoming patient at the medical facility based on each predicted resource wait time; and

transmitting, from the server to the device, a second communication that includes the wait time for the incoming patient at the medical facility.

14. The computer-program product according to claim 13, wherein the request is an implicit request indicating that an event is occurring or requesting directions to the medical facility.

15. The computer-program product according to claim 13, wherein the location of the device is identified based on location data or metadata within the first communication.

16. The computer-program product according to claim 13, wherein each queue element comprises at least one of identifying information about the respective existing patient, the medical condition being experienced by the respective existing patient, or a type of treatment for the medical condition being experienced by the respective existing patient.

17. The computer-program product according to claim 13, wherein the medical condition being experienced by the incoming patient is identified based on data or metadata within the first communication.

18. The computer-program product according to claim 13, wherein the request indicates a change in a physiological factor of the incoming patient that is above a threshold.