IP Library › Granted Patent US 12,387,840
Granted Patent B2
US 12,387,840 · App. 17/204,303 · Granted Aug 12, 2025

Remote view playback tool

Inventors: Gary Colister (Hudson, OH); Giuseppe Saracino (Gainsville, FL); William Murphy (Aurora, OH); Harish Lecamwasam (Scottsdale, AZ)
Assignee: TALIS CLINICAL LLC
G16H40/20H04N21/2387H04N21/47202H04N21/47217
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,387,840
App. No.
17/204,303
Granted
Aug 12, 2025
Kind
B2
Abstract

A remote view playback system for use by medical practitioners to improve patient outcomes, including a patient database and data storage engine including means for collecting and storing data from any number of electronic devices and instructions for transmitting data to any number of electronic devices and for storing data associated with the patient records and/or data to be stored as quality data; a communication hub for collecting, agnostically, data from any number of electronic devices and instructions for transmitting data to any number of electronic devices, and for storing data associated with the patient records to be stored as quality data, and providing access to all data, so that data from multiple disparate sources can be acquired and consolidated within a unified view; optionally, at least one monitoring station; and a user interface rules engine to collect, store and process data in real time, compose views that organize data, notify end-users based on execution steps defined by end-users, display an organized view of data within a timeline of events, change, for end-users, or augment the execution steps, provide notifications at the same time the end-user is reviewing data, and apply one or more rules to the data selected from assessment data from each monitored patient to determine whether a rule for that monitor has been violated or whether best practice rules established by a health care provider are being adhered to as expected.

Claims (19)

1. A system for handling patient data, comprising:

one or more communication hubs configured to receive data from a plurality of electronic devices corresponding to one or more patients, the data acquired by the plurality of electronic devices in real time, each communication hub having a processor and memory and configured to execute instructions for storing and processing the received data in real time, the processing including transmitting selected portions of the received data to selected ones of the electronic devices and translating the received data to a first machine-language and translating the received data to be sent to a receiving one of the electronic devices from the first machine-language to a second language compatible with the receiving electronic device; and

a remote view system including a user interface rules engine and configured to receive and transmit input data input by a user and to allow the user to review remotely, in real time, the data received with the one or more communication hubs, including applicable data associated with an active case of a patient to determine recommended care for the patient, the applicable data including patient vital signs and waveforms obtained during the active case, the remote view system further configured to allow the user to define specific notification rules to define when to provide notification when a defined condition is met,

the user interface rules engine permitting the user to review the received data within a timeline of events depicting patient interactions for the patient and patient vital signs before and after each patient interaction,

the user interface rules engine being configured to permit the user to review the received data regarding treatment at a selected time and to review the received data corresponding to a time before or after the selected time, wherein the timeline of events is configured to be displayed along with a notification rules generator via which the user can set one or more filters for defining specific notification rules to define when to provide notification when the defined condition is met, the notification rules generator including one or more menus, each menu associated with a respective filter of the one or more filters, the notification rules generator displaying a plurality of user-defined rules for each filter, and each menu including an all selection and an any selection, the all selection dictating that all of the plurality of user-defined rules for that filter be met and the any selection dictating that any of the plurality of user-defined rules for that filter be met,

wherein the received data is sorted to generate a health history for each patient based on information regarding identified ones of the electronic devices currently connected to each patient.

2. The system of claim 1 , wherein the one or more communication hubs are connected to the remote view system via a communication network.

3. The system of claim 1 , wherein, upon occurrence of a predetermined event in regard to the patient, the user interface rules engine is configured to gather the received data corresponding to the patient for a first predetermined time before and a second predetermined time after the predetermined event to generate the timeline of events.

4. The system of claim 3 , wherein the predetermined event is detected based on the received data from a patient record corresponding to the first patient.

5. The system of claim 3 , wherein the predetermined event is indicated by the user to the user interface rules engine.

6. The system of claim 1 , wherein the user interface rules engine defines criteria determining when to communicate that cases meeting the defined criteria are available for review.

7. The system of claim 1 , wherein the one or more filters include a primary filter and a secondary filter.

8. The system of claim 7 , wherein the one or more menus includes a first menu for the primary filter and a second menu for the secondary filter, wherein, via the first menu, one or more primary notification rules of the specific notification rules can be set and, via the second menu, one or more secondary notification rules of the specific notification rules can be set.

9. A method for handling patient data, comprising:

receiving data, at one or more communication hubs, from a plurality of electronic devices corresponding to one or more patients, the data acquired by the plurality of electronic devices in real time, each communication hub having a processor and memory and configured to execute instructions for storing and processing the received data in real time, the processing including transmitting selected portions of the received data to selected ones of the electronic devices and translating the received data to a first machine-language and translating the received data to be sent to a receiving one of the electronic devices from the first machine-language to a second language compatible with the receiving electronic device;

via a remote view system including a user interface rules engine, receiving and transmitting input data input by a user and allowing the user to review remotely, in real time, the data received with the one or more communication hubs, including applicable data associated with an active case of a patient to determine recommended care for the patient, the applicable data including patient vital signs and waveforms obtained during the active case, the remote view system further configured to allow the user to define specific notification rules to define when to provide notification when a defined condition is met;

permitting the user, via the user interface rules engine, to review the received data within a timeline of events depicting patient interactions for the patient and patient vital signs before and after each patient interaction; and

permitting the user, via the user interface rules engine, to review the received data regarding treatment at a selected time and to review the received data corresponding to a time before or after the selected time, wherein the timeline of events is configured to be displayed along with a notification rules generator via which the user can set one or more filters for defining specific notification rules to define when to provide notification when the defined condition is met, the notification rules generator including one or more menus, each menu associated with a respective filter of the one or more filters, the notification rules generator displaying a plurality of user-defined rules for each filter, and each menu including an all selection and an any selection, the all selection dictating that all of the plurality of user-defined rules for that filter be met and the any selection dictating that any of the plurality of user-defined rules for that filter be met,

wherein the received data is sorted to generate a health history for each patient based on information regarding identified ones of the electronic devices currently connected to each patient.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 10, 2024
From: COLISTER, GARY; SARACINO, GIUSEPPE; MURPHY, WILLIAM; LECAMWASAM, HARISH
To: TALIS CLINICAL LLC
Reel/Frame 067676/0153 →
Continuity (3)
Continuation In Part 16239077 · Jan 3, 2019
Provisional Application 62613218 · Jan 3, 2018
Related Publication 20210202082A1 · Jul 1, 2021
References Cited (73)
US 5954666A · Snell · 1999 [cited by applicant]
US 6229536B1 · Alexander et al. · 2001 [cited by applicant]
US 6364834B1 · Reuss et al. · 2002 [cited by applicant]
US 6553436B2 · Ando et al. · 2003 [cited by applicant]
US 6559868B2 · Alexander et al. · 2003 [cited by applicant]
US 7315825B2 · Rosenfeld · 2008 [cited by applicant]
US 7467093B1 · Newton et al. · 2008 [cited by applicant]
US 8000937B2 · Zeng et al. · 2011 [cited by applicant]
US 8149131B2 · Blomquist · 2012 [cited by applicant]
US 8229760B2 · Hasan et al. · 2012 [cited by applicant]
US 8291337B2 · Gannin et al. · 2012 [cited by applicant]
US 8310336B2 · Muhsin et al. · 2012 [cited by applicant]
US 8553036B2 · Taylor et al. · 2013 [cited by applicant]
US 8660860B2 · Wehba et al. · 2014 [cited by applicant]
US 8674837B2 · Gilham et al. · 2014 [cited by applicant]
US 8730243B2 · Wenholz et al. · 2014 [cited by applicant]
US 8892171B2 · Ross et al. · 2014 [cited by applicant]
US 8990722B2 · Gannon et al. · 2015 [cited by applicant]
US 9095274B2 · Fein et al. · 2015 [cited by applicant]
US 9179852B2 · Audet et al. · 2015 [cited by applicant]
US 9393366B2 · Gannon et al. · 2016 [cited by applicant]
US 9400874B2 · Powell et al. · 2016 [cited by applicant]
US 9927943B2 · Gannon et al. · 2018 [cited by applicant]
US 10255408B2 · Blomquist · 2019 [cited by applicant]
US 10354751B1 · McNair · 2019 [cited by applicant]
US 10657222B2 · Chan et al. · 2020 [cited by applicant]
US 11030872B2 · Chan et al. · 2021 [cited by applicant]
US 11031129B2 · Zaleski · 2021 [cited by applicant]
US 20020143320A1 · Levin · 2002 [cited by examiner]
US 20040044775A1 · Takano · 2004 [cited by examiner]
US 20040054294A1 · Ramseth · 2004 [cited by applicant]
US 20050159666A1 · Pearce et al. · 2005 [cited by applicant]
US 20050171815A1 · Vanderveen · 2005 [cited by applicant]
US 20070179806A1 · Knowlton et al. · 2007 [cited by applicant]
US 20080097914A1 · Dicks et al. · 2008 [cited by applicant]
US 20080316045A1 · Sriharto et al. · 2008 [cited by applicant]
US 20090070054A1 · Zeng · 2009 [cited by examiner]
US 20110227739A1 · Gillham et al. · 2011 [cited by applicant]
US 20120035957A1 · Hanz et al. · 2012 [cited by applicant]
US 20120075103A1 · Powell · 2012 [cited by examiner]
US 20120278099A1 · Kelly · 2012 [cited by examiner]
US 20140046674A1 · Rosenfeld et al. · 2014 [cited by applicant]
US 20140142963A1 · Hill et al. · 2014 [cited by applicant]
US 20140222446A1 · Ash et al. · 2014 [cited by applicant]
US 20140249855A1 · Moore · 2014 [cited by applicant]
US 20140266787A1 · Tran · 2014 [cited by applicant]
US 20140350966A1 · Khatana et al. · 2014 [cited by applicant]
US 20150025329A1 · Amarasingham et al. · 2015 [cited by applicant]
US 20160117446A1 · Hussam · 2016 [cited by examiner]
US 20160246943A1 · Lake et al. · 2016 [cited by applicant]
US 20170140108A1 · Lee et al. · 2017 [cited by applicant]
US 20170372037A1 · Muecke et al. · 2017 [cited by applicant]
US 20200035366A1 · Gummireddy et al. · 2020 [cited by applicant]
US 20200227148A1 · Cohen et al. · 2020 [cited by applicant]
US 20200359913A1 · Ghodrati et al. · 2020 [cited by applicant]
US 20200394334A1 · Bulut et al. · 2020 [cited by applicant]
US 20210065889A1 · Page · 2021 [cited by applicant]
US 20210077035A1 · Kayser et al. · 2021 [cited by applicant]
US 20210141786A1 · Gubau i Forné et al. · 2021 [cited by applicant]
US 20210151145A1 · Dunn et al. · 2021 [cited by applicant]
US 20210151178A1 · Singh et al. · 2021 [cited by applicant]
US 20210202086A1 · Cherdak · 2021 [cited by applicant]
US 20210225505A1 · Khare et al. · 2021 [cited by applicant]
US 20210233628A1 · Rentas et al. · 2021 [cited by applicant]
EP 3839960 · 2021 [cited by applicant]
JP 2004533662A · 2004 [cited by applicant]
JP 2012529351 · 2012 [cited by applicant]
JP 2015530901 · 2015 [cited by applicant]
JP 2016519806A · 2016 [cited by applicant]
WO 2017218579 · 2017 [cited by applicant]
WO 2021067485 · 2021 [cited by applicant]
WO 2021002847 · 2021 [cited by applicant]
Canadian Intellectual Property Office, Office Action Issued in Application No. 3,087,566, Sep. 3, 2024, 5 pages. [cited by applicant]