IP Library Granted Patent US 12,731,680
Granted Patent B2
US 12,731,680 · App. 19/095,885 · Granted Sep 8, 2026

Systems and methods of producing patient encounter records

Inventors: Elijah A. White (Wellesley, MA); Adam T. Dawson (Burlington, CA); David A. Jaros (Brooklyn Park, MN); Gary A. Freeman (Waltham, MA)
Assignee: ZOLL Medical Corporation
G16H40/20G06F16/242G06K7/1413G06K7/1417G16H10/60G16H40/67A61N1/3925
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,731,680
App. No.
19/095,885
Granted
Sep 8, 2026
Kind
B2
Abstract

A system for consolidating medical data from multiple devices involved in a patient encounter is provided. The system includes a mobile computing device that acquires, via a medical device interface, identifiers of each medical device, generates association information including the one or more identifiers, and transmits the association information to a server. The server receives and stores one or more medical device case files from the medical devices, receives the association information from the mobile computing device, associates the one or more medical device case files with one another, and produces an integrated data source encounter structure including case data from the one or more medical device case files for subsequent processing.

Claims (74)

1 . A system for consolidating data generated by multiple medical devices used for treating a patient during a patient encounter, the system comprising:

a plurality of medical devices, each respective medical device of the plurality of medical devices comprising:

a medical device communications interface configured to transmit at least one medical device case file to a server,

one or more processors coupled with the medical device communications interface and configured to:

store case data in the at least one medical device case file, wherein the case data comprises at least one of physiological data, treatment data, or performance data captured during patient treatment, and

transmit, via the medical device communications interface, the at least one medical device case file to the server, and

an identifier for uniquely identifying the respective medical device,

wherein at least one medical device of the plurality of medical devices comprises

at least one sensor configured to couple with a patient to acquire physiological signals from the patient,

wherein the one or more processors of each medical device of the at least one medical device is configured to

receive the physiological signals acquired by the at least one sensor, and

convert the physiological signals to the physiological data of the case data;

a mobile computing device comprising:

a network interface configured to communicate with the server,

a medical device interface configured to record a representation of the identifier of each medical device of the plurality of medical devices by at least one of

i) scanning a visible code or identifier or ii) acquiring content of a tag via near field communications (NFC) or radio frequency identification (RFID) connection, and

at least one processor coupled with the network interface and the medical device interface, the at least one processor being configured to:

responsive to user input at the mobile computing device, for each respective medical device of the plurality of medical devices,

a) record, via the medical device interface while the respective medical device is in range of the medical device interface, a respective representation of the identifier of the respective medical device, and

b) generate a respective timestamp indicating when the respective representation was recorded,

generate a data structure comprising a plurality of fields, the plurality of fields comprising:

at least one field storing a patient encounter identifier uniquely identifying a patient encounter corresponding to the patient at an emergency medical scene and involving use of the plurality of medical devices, and

a plurality of medical device identifier fields comprising, for each respective medical device of the plurality of medical devices,

a respective field storing the respective representation of the identifier, and

 a respective timestamp field storing the respective timestamp indicating when the respective representation was recorded, and

transmit, via the network interface, the data structure to the server; and

the server, comprising:

a server memory,

a server communications interface, and

at least one server processor coupled with the server memory and the server communications interface and configured to:

receive, via the server communications interface, the data structure from the mobile computing device,

receive, via the server communications interface and separately from the data structure, a plurality of medical device case files comprising the at least one medical device case file from each medical device of the plurality of medical devices,

store, to at least one non-transitory computer-readable data store, the plurality of medical device case files,

parse the data structure to extract the patient encounter identifier, the representations of the identifiers of the plurality of medical devices, and the respective timestamps,

identify a portion of the plurality of medical device case files as being associated with the patient encounter identifier by

matching the representation of the identifier of a given medical device of the plurality of medical devices and a given medical device case file, and

determining that a time range associated with the given medical device case file includes the respective timestamp indicating when the representation of the identifier of the given medical device was recorded,

consolidate the portion of the plurality of medical device case files into an integrated encounter structure corresponding to the patient encounter identifier, the integrated encounter structure comprising information identifying each medical device case file of the portion of the plurality of medical device case files, and

as further medical device case files are received from one or more medical devices of the plurality of medical devices, transmit, in real-time, updated consolidated case data to one or more remote computing devices, each remote computing device executing a data collection app configured to issue a notification based on receipt of new data.

2 . The system of claim 1 , wherein the at least one server processor is further configured to transmit the integrated encounter structure to a receiving computing device.

3 . The system of claim 2 , wherein the receiving computing device comprises the mobile computing device.

4 . The system of claim 3 , wherein the at least one processor of the mobile computing device is further configured to visually render at least a portion of the integrated encounter structure via a touch screen of the mobile computing device.

5 . The system of claim 2 , wherein the receiving computing device comprises at least one medical device of the plurality of medical devices.

6 . The system of claim 2 , wherein the receiving computing device comprises a computing device within an emergency response center.

7 . The system of claim 6 , wherein:

the data structure comprises a token to access the integrated encounter structure;

the server is further configured to receive the token from the computing device within the emergency response center; and

the at least one server processor is configured to automatically transmit the integrated encounter structure to the computing device in response to reception of the token.

8 . The system of claim 7 , wherein the mobile computing device is configured to transmit the token to the computing device within the emergency response center.

9 . The system of claim 1 , wherein to transmit the at least one medical device case file comprises to transmit one or more streams of the case data to the at least one medical device case file.

10 . The system of claim 9 , wherein the integrated encounter structure comprises information identifying the case data of each stream of the one or more streams of the case data from the at least one medical device case file.

11 . The system of claim 1 , further comprising a computing device comprising at least one user interface and configured to:

receive the integrated encounter structure; and

render at least a portion of the integrated encounter structure via the at least one user interface.

12 . The system of claim 1 , wherein the plurality of medical devices comprises one or more of: a defibrillator, a patient monitor, an automated external defibrillator, a ventilator, an automated chest compression device, and a wearable defibrillator.

13 . The system of claim 1 , wherein the data structure comprises patient information.

14 . The system of claim 13 , wherein the patient information comprises one or more of patient name, patient identifier, age, gender, weight, height, and past medical history.

15 . The system of claim 1 , wherein the data structure comprises other timestamp information indicating when the at least one medical device case file was created.

16 . The system of claim 1 , wherein:

the at least one server processor is configured to generate at least one search criterion based at least in part on the respective timestamps; and

identifying portion of the plurality of medical device case files comprises using the generated at least one search criterion to match the representation of the identifier of the given medical device of the plurality of medical devices and the given medical device case file, and to determine the time range associated with the given medical device case file includes the respective timestamp indicating when the representation of the identifier of the given medical device was recorded.

17 . The system of claim 1 , wherein the data structure comprises geolocation information indicating where the mobile computing device was located when each respective representation of the identifier of each medical device was recorded.

18 . The system of claim 1 , wherein the medical device interface comprises at least one of: a camera, a near-field communication sensor, a radio frequency identification sensor, a universal serial bus connector, an infrared sensor, a personal area network sensor, a proximity detector, a geolocation detector, and a wireless network connector.

19 . The system of claim 1 , wherein:

the medical device interface of the mobile computing device comprises a camera; and

the identifiers of the plurality of medical devices comprise one or more of a QR bar code and a bar code.

20 . The system of claim 1 , wherein the mobile computing device is further configured to generate one or more log entries.

21 . The system of claim 20 , wherein the mobile computing device is configured to transmit the one or more log entries to the server for inclusion in the integrated encounter structure.

22 . The system of claim 1 , wherein the case data of at least one medical device of the plurality of medical devices comprises physiological data comprising one or more of: ECG data, oxygen saturation data, capnographic data, and blood pressure data.

23 . The system of claim 1 , wherein the case data of at least one medical device of the plurality of medical devices comprises treatment data comprising one or more of: defibrillation data, drug infusion data, chest compression data, and ventilation data.

24 . The system of claim 1 , wherein the case data of at least one medical device of the plurality of medical devices comprises performance data comprising one or more of: chest compression performance data and ventilation performance data.

25 . The system of claim 1 , wherein the case data of at least one medical device of the plurality of medical devices comprises protected health information.

26 . The system of claim 1 , wherein the identifiers of the plurality of medical devices comprise at least one of a quick reference (QR) bar code, a radio frequency identifier (RFID), a serial number, or a transmission control protocol/internet protocol (TCP/IP) address.

27 . The system of claim 1 , wherein the integrated encounter structure comprises the respective case data from each medical device case file of the portion of the plurality of medical device case files.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 6, 2025
From: WHITE, ELIJAH A.; DAWSON, ADAM T.; JAROS, DAVID A.; FREEMAN, GARY A.; OH, MEI QI MARIA; BARNABAS, CHRISTOPHER
To: ZOLL MEDICAL CORPORATION
Reel/Frame 071548/0218 →
Continuity (4)
Continuation 17217164 · Mar 30, 2021
Provisional Application 63111234 · Nov 9, 2020
Provisional Application 63002678 · Mar 31, 2020
Related Publication 20250232869A1 · Jul 17, 2025
References Cited (127)
US 5267155A · Buchanan et al. · 1993 [cited by applicant]
US 6083248A · Thompson · 2000 [cited by applicant]
US 6088616A · Olson et al. · 2000 [cited by applicant]
US 6106459A · Clawson · 2000 [cited by applicant]
US 6117073A · Jones et al. · 2000 [cited by applicant]
US 6282531B1 · Haughton et al. · 2001 [cited by applicant]
US 6363282B1 · Nichols et al. · 2002 [cited by applicant]
US 6370428B1 · Snyder et al. · 2002 [cited by applicant]
US 6397104B1 · Miller et al. · 2002 [cited by applicant]
US 6607481B1 · Clawson · 2003 [cited by applicant]
US 6610010B2 · Sjoqvist · 2003 [cited by applicant]
US 6684276B2 · Walker et al. · 2004 [cited by applicant]
US 6735272B1 · Sorenson · 2004 [cited by applicant]
US 6747556B2 · Medema et al. · 2004 [cited by applicant]
US 6754526B2 · Daynes et al. · 2004 [cited by applicant]
US 6813517B2 · Daynes et al. · 2004 [cited by applicant]
US 6937150B2 · Medema et al. · 2005 [cited by applicant]
US 7039628B2 · Logan, Jr. · 2006 [cited by applicant]
US 7044742B2 · Sumiya et al. · 2006 [cited by applicant]
US 7412395B2 · Rowlandson · 2008 [cited by applicant]
US 7490085B2 · Walker et al. · 2009 [cited by applicant]
US 7650181B2 · Freeman et al. · 2010 [cited by applicant]
US 7668820B2 · Zuleba · 2010 [cited by applicant]
US 7672720B2 · Heath · 2010 [cited by applicant]
US 7769465B2 · Matos · 2010 [cited by applicant]
US 7805190B2 · Chapman et al. · 2010 [cited by applicant]
US 7937146B2 · Banville et al. · 2011 [cited by applicant]
US 7979378B2 · West et al. · 2011 [cited by applicant]
US 8081071B1 · Vaisnys et al. · 2011 [cited by applicant]
US 8712793B2 · Jones et al. · 2014 [cited by applicant]
US 8738129B2 · Packer et al. · 2014 [cited by applicant]
US 8781577B2 · Freeman · 2014 [cited by applicant]
US 8818522B2 · Mass et al. · 2014 [cited by applicant]
US 8880166B2 · Tan et al. · 2014 [cited by applicant]
US 9119971B2 · Elghazzawi · 2015 [cited by applicant]
US 9220912B2 · Elghazzawi · 2015 [cited by applicant]
US 9658756B2 · Freeman et al. · 2017 [cited by applicant]
US 10137265B2 · Freeman et al. · 2018 [cited by applicant]
US 10692591B2 · Huang et al. · 2020 [cited by applicant]
US 10713377B2 · Joscelyne et al. · 2020 [cited by applicant]
US 11031139B2 · Barkol · 2021 [cited by examiner]
US 11177026B2 · Heavelyn · 2021 [cited by examiner]
US 11342075B2 · Podobas et al. · 2022 [cited by applicant]
US 20010016696A1 · Bystrom et al. · 2001 [cited by applicant]
US 20020004729A1 · Zak et al. · 2002 [cited by applicant]
US 20020073099A1 · Gilbert et al. · 2002 [cited by applicant]
US 20030014222A1 · Klass et al. · 2003 [cited by applicant]
US 20030025602A1 · Medema et al. · 2003 [cited by applicant]
US 20030028219A1 · Powers et al. · 2003 [cited by applicant]
US 20030105649A1 · Sheiner et al. · 2003 [cited by applicant]
US 20030212311A1 · Nova et al. · 2003 [cited by applicant]
US 20030212438A1 · Nova et al. · 2003 [cited by applicant]
US 20030212575A1 · Saalsaa · 2003 [cited by applicant]
US 20040049233A1 · Edwards · 2004 [cited by applicant]
US 20040064342A1 · Browne et al. · 2004 [cited by applicant]
US 20040088317A1 · Fabrick et al. · 2004 [cited by applicant]
US 20040214148A1 · Salvino et al. · 2004 [cited by applicant]
US 20050015115A1 · Sullivan et al. · 2005 [cited by applicant]
US 20050149363A1 · Loiterman et al. · 2005 [cited by applicant]
US 20050256740A1 · Kohan et al. · 2005 [cited by applicant]
US 20060015254A1 · Smith · 2006 [cited by applicant]
US 20060030891A1 · Saltzstein et al. · 2006 [cited by applicant]
US 20060084043A1 · Weaver et al. · 2006 [cited by applicant]
US 20060149321A1 · Merry et al. · 2006 [cited by applicant]
US 20070032830A1 · Bowers · 2007 [cited by applicant]
US 20070185545A1 · Duke · 2007 [cited by applicant]
US 20070203742A1 · Jones et al. · 2007 [cited by applicant]
US 20080097909A1 · Dicks et al. · 2008 [cited by applicant]
US 20080138778A1 · Eggert et al. · 2008 [cited by applicant]
US 20080243549A1 · Woronka et al. · 2008 [cited by applicant]
US 20080244717A1 · Jelatis et al. · 2008 [cited by applicant]
US 20090222539A1 · Lewis et al. · 2009 [cited by applicant]
US 20100250643A1 · Savage et al. · 2010 [cited by applicant]
US 20110060378A1 · Tuysserkani · 2011 [cited by applicant]
US 20110284004A1 · Silver et al. · 2011 [cited by applicant]
US 20110295078A1 · Reid et al. · 2011 [cited by applicant]
US 20120081230A1 · Sullivan et al. · 2012 [cited by applicant]
US 20120191476A1 · Reid et al. · 2012 [cited by applicant]
US 20120226771A1 · Harrington et al. · 2012 [cited by applicant]
US 20120253842A1 · Curran et al. · 2012 [cited by applicant]
US 20120304054A1 · Orf et al. · 2012 [cited by applicant]
US 20130096649A1 · Martin et al. · 2013 [cited by applicant]
US 20130132465A1 · Brown · 2013 [cited by applicant]
US 20130159021A1 · Felsher · 2013 [cited by applicant]
US 20130191161A1 · Churchwell 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 20140222805A1 · Huang 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 20140365175A1 · Packer et al. · 2014 [cited by applicant]
US 20150154367A1 · Shetty et al. · 2015 [cited by applicant]
US 20160026762A1 · Radhakrishnan et al. · 2016 [cited by applicant]
US 20160085914A1 · Douglass et al. · 2016 [cited by applicant]
US 20160256622A1 · Day et al. · 2016 [cited by applicant]
US 20160337829A1 · Fletcher et al. · 2016 [cited by applicant]
US 20170109502A1 · Labkoff et al. · 2017 [cited by applicant]
US 20170150939A1 · Shah · 2017 [cited by applicant]
US 20170169166A1 · Colley et al. · 2017 [cited by applicant]
US 20170323055A1 · Gaffield · 2017 [cited by applicant]
US 20170337338A1 · Dunn et al. · 2017 [cited by applicant]
US 20180114288A1 · Aldaz et al. · 2018 [cited by applicant]
US 20190076024A1 · Gosink et al. · 2019 [cited by applicant]
US 20210304860A1 · Hart et al. · 2021 [cited by applicant]
US 20220310219A1 · Sanchez, Jr. et al. · 2022 [cited by applicant]
CN 101589393A · 2009 [cited by applicant]
CN 102982226A · 2013 [cited by applicant]
WO WO2005043306A2 · 2005 [cited by examiner]
WO 2005109291 · 2005 [cited by applicant]
WO 2007058835 · 2007 [cited by applicant]
WO 2007089225 · 2007 [cited by applicant]
WO 2009136259 · 2009 [cited by applicant]
WO 2011127459 · 2011 [cited by applicant]
WO 2012100219 · 2012 [cited by applicant]
WO 2014105592 · 2014 [cited by applicant]
WO 2018013411A1 · 2018 [cited by applicant]
WO 2018218162A1 · 2018 [cited by applicant]
WO 2021202490A1 · 2021 [cited by applicant]
Alejandro Plaza Roncero, Gonçalo Marques, Beatriz Sainz-De-Abajo, Francisco Martín-Rodríguez, Carlos del Pozo Vegas, Begonya Garcia-Zapirain, Isabel de la Torre-Díez1; Mobile Health Apps for Emergencies: Systematic Revi… [cited by examiner]
International Search Report and Written Opinion received for PCT/US2021/024799; dated Jul. 14, 2021. 21 pages. [cited by applicant]
Wu et al., “Synchronizing Device Clocks Using IEEE 1588 and Blackfin Embedded Processors”, Analog Dialogue 43-11 (Nov. 2009). [cited by applicant]
Mozer R. et al., “Matching with Text Data: An Experimental Evaluation of Methods for Matching Documents and of Measuring Match Quality”, arXiv:1801.00644v7, Mar. 13, 2019, 71 pages. [cited by applicant]
Jones, Mike, “Get in Sync!: IEEE 1588v2 Transparent Clock Benefits for Industrial Control Distributed Networks,” Micrel, Inc., retrieved from http://ww1.microchip.com/downloads/en/AppNotes/Get%20in%20Sync.pdf on May 3, … [cited by applicant]
“IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems”, IEEE Instrumentation and Measurement Society, IEEE Std 1588™-2008 (Jul. 24, 2008). [cited by applicant]
Invitation to pay additional fees received for PCT/US2021/024833, dated Jul. 16, 2021. 13 pages. [cited by applicant]
Peng, et al., “A literature review of current technologies on health data integration for patient-centered health management,” Health Informatics Journal, Dec. 30, 2019. 26 pages. [cited by applicant]
European Communication Pursuant to Article 94(3) EPC issued in 21721254.7 dated Dec. 9, 2025. [cited by applicant]