IP Library Granted Patent US 12,205,688
Granted Patent B2
US 12,205,688 · App. 17/703,838 · Granted Jan 21, 2025

Medical record digest

Inventors: Mario Sanchez, Jr. (Longmont, CO); Gary A. Freeman (Waltham, MA); Peter G. Goutmann (Gibsonia, PA); Gregory G. Howard (Pittsburgh, PA); Robert W. Krier (Boulder, CO); Gregory D. Mears (Carolina Beach, NC); Frederick W. Forester (Encinitas, CA); Kevin M. Zahora (Liberty Township, OH)
Assignee: ZOLL Medical Corporation
G16H10/60G06F16/93
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 12,205,688
App. No.
17/703,838
Granted
Jan 21, 2025
Kind
B2
Abstract

An EMS medical record acquisition system is provided. The system is configured to provide medical record information to an EMS rescuer in a mobile EMS environment. The system includes a user device, a patient identification data source, and a medical record digest system. The digest system is coupled to the user device and to the patient identification source. The digest system receives identification data from the patient identification source, queries a medical record repository using the identification data, receives a medical record for the patient from the medical record repository, generates a reference code based on the identification data, stores the medical record with the reference code, transmits the reference code to the user device, receives a query including the reference code from the user device, generates a digest at least a portion of the medical record, and provides the digest to the user device.

Claims (70)

1. An emergency medical services (EMS) medical record acquisition system for providing medical record information to an EMS rescuer for an encounter with a patient in a mobile EMS environment, the system comprising:

a user interface device comprising:

at least one user interface device processor; and

a non-transitory user interface device memory having stored therein instructions, that when executed by the at least one user interface device processor, cause the at least one user interface device processor to:

provide a user interface,

prompt, via the user interface, the EMS rescuer to request a medical record digest,

receive the medical record digest from a medical record digest system, and

present, via the user interface, the received medical record digest;

the medical record digest system, wherein the medical record digest system is in a cloud environment and is configured to communicatively couple to an incident data exchange system and the user interface device, the medical record digest system comprising:

at least one medical record digest system processor; and

a non-transitory medical record digest system memory having stored therein instructions, that when executed by the at least one medical record digest system processor, cause the at least one medical record digest system processor to:

generate, by a query service, a first medical record query for a medical record for the patient, and

transmit, by the query service, the generated first medical record query to the incident data exchange system;

one or more patient identification data sources; and

the incident data exchange system, wherein the incident data exchange system is in the cloud environment and is configured to communicatively couple to (a) the medical record digest system and to at least one medical record repository as an intermediary between the medical record digest system and the at least one medical record repository and (b) the one or more patient identification data sources, the incident data exchange system comprising:

one or more exchange system processors; and

a non-transitory incident data exchange system memory having stored therein instructions, that when executed by the one or more exchange system processors, cause the one or more exchange system processors to:

receive patient identification data from the one or more patient identification data sources for an EMS call for the patient,

generate a second medical record query for the medical record for the patient, wherein the second medical record query includes at least a first portion of the patient identification data,

send the second medical record query to the at least one medical record repository,

receive the medical record for the patient from the at least one medical record repository,

generate a patient reference code based on at least a second portion of the patient identification data,

store the medical record with the patient reference code in the incident data exchange system memory, and

transmit the medical record and the patient reference code to the medical record digest system,

wherein the instructions stored in the medical record digest system memory, when executed by the at least one medical record digest system processor, cause the at least one medical record digest system processor to;

receive the medical record and the patient reference code from the incident data exchange system,

store the medical record with the patient reference code in the medical record digest system memory,

select a portion of the medical record based on clinical relevance to the encounter with the patient,

generate the medical record digest that comprises the selected portion of the medical record, and

transmit the medical record digest with the patient reference code to the user interface device in the mobile EMS environment.

2. The EMS medical record acquisition system of claim 1 , wherein the one or more patient identification data sources comprise one or more of a computer-aided dispatch system or a patient charting system.

3. The EMS medical record acquisition system of claim 1 , wherein:

the incident data exchange system memory comprises a predetermined patient identification criterion; and

the instructions stored in the incident data exchange system memory, when executed by the one or more exchange system processors, cause the one or more exchange system processors to determine whether the patient identification data from the one or more patient identification data sources satisfies the predetermined patient identification criterion.

4. The EMS medical record acquisition system of claim 3 , wherein the predetermined patient identification criterion comprises a list of identification data items necessary to include in the second medical record query to distinguish between multiple patients represented in the at least one medical record repository.

5. The EMS medical record acquisition system of claim 4 , wherein the list of identification data items comprises patient demographic data comprising one or more of a first name of the patient, a last name of the patient, a date of birth of the patient, a government issued identifier of the patient, a telephone number of the patient, or a gender of the patient.

6. The EMS medical record acquisition system of claim 3 , wherein the instructions stored in the incident data exchange system memory, when executed by the one or more exchange system processors, cause the one or more exchange system processors to:

request supplemental patient identification data from one or more supplemental patient identification data sources in response to a determination that the predetermined patient identification criterion is unsatisfied by the patient identification data from the one or more patient identification data sources; and

generate combined patient identification data comprising the supplemental patient identification data from the one or more supplemental patient identification data sources and the patient identification data from the one or more patient identification data sources,

wherein the predetermined patient identification criterion is satisfied by the combined patient identification data.

7. The EMS medical record acquisition system of claim 6 , wherein:

the one or more patient identification data sources comprise a computer-aided dispatch (CAD) system;

the one or more supplemental patient identification data sources comprise an EMS patient charting system;

the patient identification data comprises one or more of patient medical data or patient demographic data from the CAD system; and

the supplemental patient identification data comprises one or more of patient medical data or patient demographic data from the EMS patient charting system.

8. The EMS medical record acquisition system of claim 6 , wherein the one or more patient identification data sources, the one or more supplemental patient identification data sources, the incident data exchange system, and the medical record digest system form a cloud-based platform.

9. The EMS medical record acquisition system of claim 6 , wherein the one or more supplemental patient identification data sources comprise the user interface device.

10. The EMS medical record acquisition system of claim 9 , wherein the instructions stored in the medical record digest system memory, when executed by the at least one medical record digest system processor, cause the at least one medical record digest system processor to:

provide a prompt, via the user interface, for for a user-entered confirmation of the patient identification data;

receive the user-entered confirmation of the patient identification data; and

transmit the generated first medical record query to the incident data exchange system in response to receipt of the user-entered confirmation.

11. The EMS medical record acquisition system of claim 1 , wherein the instructions stored in the incident data exchange system memory, when executed by the one or more exchange system processors, cause the one or more exchange system processors to generate the patient reference code based on a hash and/or encryption of the at least the second portion of the patient identification data.

12. The EMS medical record acquisition system of claim 1 , wherein the at least one medical record repository comprises one or more of a health information exchange, a hospital records database, or a health system database.

13. The EMS medical record acquisition system of claim 1 , wherein the instructions stored in the medical record digest system memory, when executed by the at least one medical record digest system processor, cause the at least one medical record digest system processor to:

serve the user interface to the user interface device.

14. The EMS medical record acquisition system of claim 13 , wherein the user interface is one or more of a visual user interface, an audio user interface, or an augmented reality user interface.

15. The EMS medical record acquisition system of claim 1 , wherein the mobile EMS environment comprises at least one emergency medical vehicle comprising one or more of an ambulance, a fire engine, an EMS crew transport vehicle, or a helicopter.

16. The EMS medical record acquisition system of claim 1 , wherein the medical record digest system memory, the user interface device, and the at least one medical record digest system processor are disposed in a mobile computing device.

17. The EMS medical record acquisition system of claim 1 , wherein:

the medical record digest system memory and the at least one medical record digest system processor are disposed in a cloud server configured to communicatively couple to the user interface device; and

the medical record digest system provides a medical record digest application at the user interface device.

18. The EMS medical record acquisition system of claim 1 , wherein the one or more patient identification data sources comprise one or more of a hospital information system, a medical billing system, a case data store, a charting system, a computer-aided dispatch system, a navigation system, a medical device, or the medical record digest system.

19. The EMS medical record acquisition system of claim 18 , wherein the instructions stored in the incident data exchange system memory, when executed by the one or more exchange system processors, cause the one or more exchange system processors to maintain, within the incident data exchange system memory, a cross-reference that relates the patient reference code with patient identifiers generated by one or more of the hospital information system, the medical billing system, the case data store, the charting system, the computer-aided dispatch system, the navigation system, the medical device, the medical record digest system, or a demographic verifier.

20. The EMS medical record acquisition system of claim 1 , wherein the instructions stored in the incident data exchange system memory, when executed by the one or more exchange system processors, cause the one or more exchange system processors to identify at least one subscription to receive the medical record of the patient, the at least one subscription identifying the medical record digest system.

21. The EMS medical record acquisition system of claim 1 , wherein the instructions stored in the medical record digest system memory, when executed by the at least one medical record digest system processor, cause the at least one medical record digest system processor to select the portion of the medical record based at least in part on a predetermined list of medical data specific to an EMS agency.

22. The EMS medical record acquisition system of claim 1 , wherein the instructions stored in the medical record digest system memory, when executed by the at least one medical record digest system processor, cause the at least one medical record digest system processor to select the portion of the medical record based at least in part on an attribute of the mobile EMS environment.

23. The EMS medical record acquisition system of claim 1 , wherein the instructions stored in the medical record digest system memory, when executed by the at least one medical record digest system processor, cause the at least one medical record digest system processor to select the portion of the medical record based at least in part on a category of medical data included in the medical record.

24. The EMS medical record acquisition system of claim 1 , wherein the instructions stored in the medical record digest system memory, when executed by the at least one medical record digest system processor, cause the at least one medical record digest system processor to select the portion of the medical record based at least in part on EMS call type data.

25. The EMS medical record acquisition system of claim 24 , wherein the EMS call type data includes physiological signals from the patient received from a medical device that is in the mobile EMS environment and that is coupled to the patient.

26. The EMS medical record acquisition system of claim 24 , wherein the EMS call type data includes billing information for the patient.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2022
From: SANCHEZ, MARIO, JR.; FREEMAN, GARY A.; GOUTMANN, PETER G.; HOWARD, GREGORY G.; KRIER, ROBERT W.; MEARS, GREGORY D.; FORESTER, FREDERICK W.; ZAHORA, KEVIN M.
To: ZOLL MEDICAL CORPORATION
Reel/Frame 059881/0287 →
Continuity (2)
Provisional Application 63165350 · Mar 24, 2021
Related Publication 20220310219A1 · Sep 29, 2022
References Cited (54)
US 6747561B1 · Reeves · 2004 [cited by applicant]
US 8169315B2 · Smith · 2012 [cited by applicant]
US 8554170B2 · Franz · 2013 [cited by applicant]
US 8712793B2 · Jones et al. · 2014 [cited by applicant]
US 9729480B2 · Bell · 2017 [cited by applicant]
US 10574606B2 · Bell · 2020 [cited by applicant]
US 20030052788A1 · Kwong-Tai Chung · 2003 [cited by applicant]
US 20030105649A1 · Sheiner et al. · 2003 [cited by applicant]
US 20030195567A1 · Jayne et al. · 2003 [cited by applicant]
US 20060229909A1 · Kaila · 2006 [cited by examiner]
US 20070083392A1 · Zaleski · 2007 [cited by applicant]
US 20080133572A1 · Verhey-Henke et al. · 2008 [cited by applicant]
US 20090037225A1 · Burchianti, II et al. · 2009 [cited by applicant]
US 20100227585A1 · Carroll et al. · 2010 [cited by applicant]
US 20110119088A1 · Gunn · 2011 [cited by applicant]
US 20110295078A1 · Reid et al. · 2011 [cited by applicant]
US 20120158074A1 · Hall · 2012 [cited by applicant]
US 20120191476A1 · Reid et al. · 2012 [cited by applicant]
US 20130096649A1 · Martin et al. · 2013 [cited by applicant]
US 20130275151A1 · Moore et al. · 2013 [cited by applicant]
US 20140019159A1 · Singh et al. · 2014 [cited by applicant]
US 20140046940A1 · Thomson et al. · 2014 [cited by applicant]
US 20140249854A1 · Moore et al. · 2014 [cited by applicant]
US 20140337047A1 · Mears et al. · 2014 [cited by applicant]
US 20140365241A1 · Dillie · 2014 [cited by applicant]
US 20150120794A1 · Phelan et al. · 2015 [cited by applicant]
US 20150127379A1 · Sorenson · 2015 [cited by applicant]
US 20150242574A1 · Antony · 2015 [cited by applicant]
US 20160070864A1 · Dotan et al. · 2016 [cited by applicant]
US 20160162643A1 · Newbold et al. · 2016 [cited by applicant]
US 20160180044A1 · Delisle et al. · 2016 [cited by applicant]
US 20170296107A1 · Reid · 2017 [cited by applicant]
US 20190214115A1 · Bell · 2019 [cited by applicant]
JP 2002032475A · 2002 [cited by applicant]
JP 4393112B2 · 2010 [cited by applicant]
WO 2014144846A1 · 2014 [cited by applicant]
WO 2015066650A1 · 2015 [cited by applicant]
Wikipedia. “Health Level 7”. Retrieved from the Wayback Machine as of Nov. 13, 2008. Accessed Dec. 9, 2019. (Year: 2008). [cited by applicant]
ZOLL Data Systems, “RescueNet ePCR 5.4.3 Defect Release Notes,” Jan. 26, 2014, 1 page. [cited by applicant]
ZOLL Data Systems, “RescueNet Dispatch—Billing 4.6 Services Install Guide,” Oct. 23, 2015, 34 pages. [cited by applicant]
ZOLL Data Systems, RescueNet Dispatch—Billing Administration Guide, Release 4.6.1, Oct. 22, 2015, 740 pages. [cited by applicant]
ZOLL Data Systems, RescueNet Eligibility Services Installation Guide, Software Release 4.6, 2015, 7 pages. [cited by applicant]
ZOLL Data Systems, “RescueNet ePCR 5.4.3 Feature Release Notes,” Jan. 26, 2014, 1 page. [cited by applicant]
ZOLL Data Systems, RescueNet TabletPCR and WebPCR User Guide, Software Version 5.4.3, 2015, 205 pages. [cited by applicant]
ZOLL Data Systems, RescueNet Billing User's Guide, Softwarex Version 4.5, 2015, 450 pages. [cited by applicant]
ZOLL Data Systems, RescueNet Billing—Dispatch Release Notes, Software Version 4.6.1, Dec. 8, 2015, 5 pages. [cited by applicant]
ZOLL Data Systems, “RescueNet ePCR Suite Administrator Guide,” Software Version 5.4.3, 2015, 389 pages. [cited by applicant]
ZOLL Data Systems, “RescueNet Dispatch—Billing Upgrade for Administrators,” Oct. 21, 2015, 16 pages. [cited by applicant]
Remoteoperations, SecureFlow Pro HL7 Specification ADS, MDM and ACK Message Types, Document Version 1.2, updated Nov. 3, 2005 (21 pages). [cited by applicant]
Smiley et al, “Implementation of EMS Access to Patient History” https://www.jems.com/operations/orange-county-calif-begins-field-implementation-of-ems-access-to-patient-history-via-hie/ May 1, 2017 (9 pages). [cited by applicant]
Kno2, ImageTrend Enable Broad-based Interoperability for EMS, Oct. 16, 2019 (7 pages). [cited by applicant]
www.imagetrend.com, Website know to of been captured as early as Jul. 25, 2002 (3 pages). [cited by applicant]
www.imagetrend.com/ems/, Website know to of been captured as early as Nov. 19, 2002 (33 pages). [cited by applicant]
ZOLL Data Systems, EMS and Hospital Partners: Transform the Way You Collaborate with ZOLL Care Exchange, Copyright 2021 (8 pages). [cited by applicant]