Selectively routing patient data between field devices and treatment center destinations

• US 10,504,618 B2
• Filed: 01/23/2019
• Issued: 12/10/2019
• Est. Priority Date: 02/29/2008
• Status: Active Grant

• Current Assignee: Physio-Control Incorporated (Stryker Corporation)
• Original Assignee: Physio-Control Incorporated (Stryker Corporation)
• Inventors: Lewis, Dana, Merry, Randy L., Nova, Richard C.
• Primary Examiner(s): Burgess, Joseph D
• Application Number:
  US16/255,076
• Publication Number:
  US 20190156924A1
• Time in Patent Office: 321 Days
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/30 relating to physical therapies or activities, e.g. physiotherapy, acupressure or exercising
• 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 40/67 for remote operation

Abstract

Techniques for routing event data from a field device, such as an external defibrillator, to a selected subset of a plurality of possible destinations are described. The event data may include physiological data of the patient, such as a 12-lead electrocardiogram (ECG). The destinations may be associated with one of a plurality of patient treatment centers, and may include, as examples, computing device, printers, displays, personal digital assistants, or web-accessible accounts. In some examples, a server maintains user-configurable information or rules for at least some of the destinations, and uses the information or rules for determining whether event data received from a field device is routed to the destination. In some examples, the server may also make the routing determination based on an analysis of event data, such as a determination as to whether the event data indicates that the patient is suspected to be experiencing an acute myocardial infarction.

Claims

1. A method comprising:

receiving, at a server located remotely from a plurality of medical devices, medical event data from at least one of the plurality of medical devices, wherein the plurality of medical devices at least one of monitors or treats a patient outside of a patient treatment center, wherein the medical event data comprises physiological data of the patient;

maintaining, by the server, event data filtering rules for a plurality of destinations used by the server for determining whether the medical event data received from the at least one of the plurality of medical devices is routed to a destination of the plurality of destinations, wherein each destination of the plurality of destinations is associated with one of a plurality of patient treatment centers, wherein the event data filtering rules specify qualifications of a type of data that an associated destination should receive;

determining a data type of the physiological data included within the medical event data;

making a comparison of the medical event data to historical medical event data for the patient retrieved from a patient data server;

based on the comparison, determining whether the patient has a particular physiological condition;

based on (i) whether the patient has the particular physiological condition and (ii) on the determined data type, determining to which of the plurality of patient treatment centers the patient may be taken;

for the plurality of patient treatment centers to which the patient may be taken, applying the event data filtering rules to determine to which destinations to route the medical event data; and

routing the medical event data from the at least one of the plurality of medical devices to the determined destinations.

2. The method of claim 1, further comprising:

determining, by the server, destinations for the medical event data based on the event data filtering rules specifying which of the plurality of destinations should receive medical event data of the determined data type; and

routing the medical event data from the at least one of the plurality of medical devices to a selected subset of the plurality of destinations.

3. The method of claim 2, wherein at least one of the selected subset of the plurality of destinations has a facility and staffing to treat the patient.

4. The method of claim 2, wherein one of the plurality of destinations of the selected subset receives all of the medical event data and one of the plurality of destinations of the selected subset receives a subset of the medical event data.

5. The method of claim 1, wherein receiving medical event data from the at least one of a plurality of medical devices comprises receiving 12-lead ECG data.

6. The method of claim 1, wherein receiving medical event data from the at least one of a plurality of medical devices comprises receiving perfusion sensor data.

7. The method of claim 1, wherein determining whether the patient has a particular physiological condition comprises:

making a determination of whether the patient is suspected of having suffered an acute myocardial infarction (AMI).

8. The method of claim 7, further comprising:

routing the medical event data from the at least one of the plurality of medical devices to a selected one of the determined destinations only if the patient is suspected of having suffered the AMI.

9. The method of claim 1, wherein determining whether the patient has a particular physiological condition comprises:

analyzing a 12-lead ECG to determine if the 12-lead ECG has ST segment elevation in two or more contiguous sensor leads.

10. The method of claim 1, further comprising:

collecting a first time value indicating the time at which a patient arrived at a patient treatment center and a second time value indicating a time when the patient received percutaneous transluminal coronary intervention at the patient treatment center; and

calculating a door-to-balloon (D2B) time associated with the patient treatment center based on the first time value and the second time value.

11. The method of claim 1, further comprising:

collecting a first time value indicating a time of initiation of an emergency response procedure and a second time value indicating a time at which a paramedic arrived at a location of the patient; and

based on the first time value and the second time value, calculating an overall time from initiation of the emergency response procedure to treatment of the patient.

12. The method of claim 11, further comprising:

routing the medical event data from the at least one of the plurality of medical devices to additional destinations based on the overall time.

13. The method of claim 1, further comprising:

identifying, by the server, one of the plurality of patient treatment centers to which to direct the patient based on at least one of proximity or travel time from a location of the patient to the treatment center; and

routing the medical event data to destinations associated with the identified treatment center.

14. The method of claim 1, further comprising:

retrieving a first time at which a paramedic was dispatched to or arrived at the patient;

receiving a second time at which patient treatment was initiated;

calculating a treatment time interval for an event based on the first time and the second time; and

based on the treatment time interval, determining to which facilities to direct the patient and which destinations to route the medical event data.

15. The method of claim 1, further comprising:

prior to and during patient transport to one of the plurality of patient treatment centers, receiving updated medical event data from the at least one of the plurality of medical devices; and

routing the updated medical event data from the at least one of the plurality of medical devices to the determined destinations.

16. The method of claim 1, further comprising:

receiving, at the server, an update from medical facility personnel as to expected arrival time at the plurality of patient treatment centers to which the patient may be taken; and

based on the update, the server diverting the patient and previously transmitted medical event data to other destinations.

17. A non-transitory computer-readable medium comprising instructions that cause a programmable processor of a server to:

receive, at the server located remotely from a plurality of medical devices, medical event data from at least one of the plurality of medical devices, wherein the plurality of medical devices at least one of monitors or treats a patient outside of a patient treatment center, wherein the medical event data comprises physiological data of the patient;

maintain, by the server, event data filtering rules for a plurality of destinations used by the server for determining whether the medical event data received from the at least one of the plurality of medical devices is routed to a destination of the plurality of destinations, wherein each destination of the plurality of destinations is associated with one of a plurality of patient treatment centers, wherein the event data filtering rules specify qualifications of a type of data that an associated destination should receive;

determine a data type of the physiological data included within the medical event data;

make a comparison of the medical event data to historical medical event data for the patient retrieved from a patient data server;

based on the comparison, determine whether the patient has a particular physiological condition;

based on (i) whether the patient has the particular physiological condition and (ii) on the determined data type, determine to which of the plurality of patient treatment centers the patient may be taken;

for the plurality of patient treatment centers to which the patient may be taken, apply the event data filtering rules to determine to which destinations to route the medical event data; and

route the medical event data from the at least one of the plurality of medical devices to the determined destinations.

18. The non-transitory computer-readable medium of claim 17, wherein the non-transitory computer-readable medium further comprises instructions that cause the programmable processor of the server to:

collect a first time value indicating a time of initiation of an emergency response procedure and a second time value indicating a time at which a paramedic arrived at a location of the patient;

based on the first time value and the second time value, calculate an overall time from initiation of the emergency response procedure to treatment of the patient; and

route the medical event data from the at least one of the plurality of medical devices to additional destinations based on the overall time.

19. A system comprising:

a server including a processor;

memory storing instructions executable by the processor to perform functions comprising;

receiving, at the server located remotely from a plurality of medical devices, medical event data from at least one of the plurality of medical devices, wherein the plurality of medical devices at least one of monitors or treats a patient outside of a patient treatment center, wherein the medical event data comprises physiological data of the patient;

maintaining, by the server, event data filtering rules for a plurality of destinations used by the server for determining whether the medical event data received from the at least one of the plurality of medical devices is routed to a destination of the plurality of destinations, wherein each destination of the plurality of destinations is associated with one of a plurality of patient treatment centers, wherein the event data filtering rules specify qualifications of a type of data that an associated destination should receive;

determining a data type of the physiological data included within the medical event data;

making a comparison of the medical event data to historical medical event data for the patient retrieved from a patient data server;

based on the comparison, determining whether the patient has a particular physiological condition;

based on (i) whether the patient has the particular physiological condition and (ii) on the determined data type, determining to which of the plurality of patient treatment centers the patient may be taken;

for the plurality of patient treatment centers to which the patient may be taken, applying the event data filtering rules to determine to which destinations to route the medical event data; and

routing the medical event data from the at least one of the plurality of medical devices to the determined destinations.

20. The system of claim 19, wherein the functions further comprise:

identifying, by the server, one of the plurality of patient treatment centers to which to direct the patient based on at least one of proximity or travel time from a location of the patient to the treatment center; and

routing the medical event data to destinations associated with the identified treatment center.