US20200412838A1 - Automated delivery of medical device support software - Google Patents
Automated delivery of medical device support software Download PDFInfo
- Publication number
- US20200412838A1 US20200412838A1 US16/930,399 US202016930399A US2020412838A1 US 20200412838 A1 US20200412838 A1 US 20200412838A1 US 202016930399 A US202016930399 A US 202016930399A US 2020412838 A1 US2020412838 A1 US 2020412838A1
- Authority
- US
- United States
- Prior art keywords
- server
- user device
- medical device
- software application
- communications connection
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H04L67/42—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- A61M1/10—
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M60/00—Blood pumps; Devices for mechanical circulatory actuation; Balloon pumps for circulatory assistance
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M60/00—Blood pumps; Devices for mechanical circulatory actuation; Balloon pumps for circulatory assistance
- A61M60/10—Location thereof with respect to the patient's body
- A61M60/104—Extracorporeal pumps, i.e. the blood being pumped outside the patient's body
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M60/00—Blood pumps; Devices for mechanical circulatory actuation; Balloon pumps for circulatory assistance
- A61M60/50—Details relating to control
- A61M60/585—User interfaces
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61N—ELECTROTHERAPY; MAGNETOTHERAPY; RADIATION THERAPY; ULTRASOUND THERAPY
- A61N1/00—Electrotherapy; Circuits therefor
- A61N1/18—Applying electric currents by contact electrodes
- A61N1/32—Applying electric currents by contact electrodes alternating or intermittent currents
- A61N1/38—Applying electric currents by contact electrodes alternating or intermittent currents for producing shock effects
- A61N1/39—Heart defibrillators
- A61N1/3925—Monitoring; Protecting
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61N—ELECTROTHERAPY; MAGNETOTHERAPY; RADIATION THERAPY; ULTRASOUND THERAPY
- A61N1/00—Electrotherapy; Circuits therefor
- A61N1/18—Applying electric currents by contact electrodes
- A61N1/32—Applying electric currents by contact electrodes alternating or intermittent currents
- A61N1/38—Applying electric currents by contact electrodes alternating or intermittent currents for producing shock effects
- A61N1/39—Heart defibrillators
- A61N1/3993—User interfaces for automatic external defibrillators
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/35—Communication
- A61M2205/3576—Communication with non implanted data transmission devices, e.g. using external transmitter or receiver
- A61M2205/3584—Communication with non implanted data transmission devices, e.g. using external transmitter or receiver using modem, internet or bluetooth
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M60/00—Blood pumps; Devices for mechanical circulatory actuation; Balloon pumps for circulatory assistance
- A61M60/20—Type thereof
- A61M60/289—Devices for mechanical circulatory actuation assisting the residual heart function by means mechanically acting upon the patient's native heart or blood vessel structure, e.g. direct cardiac compression [DCC] devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Definitions
- Embodiments of the present invention relate generally to emergency medical devices, and more specifically to applications for communicating with such devices.
- a defibrillator device may include a physical interface (such as a serial port or Ethernet interface) for connecting the defibrillator with a personal computer.
- the user must install device application software onto the personal computer, either by download or using physical media provided to the user, for example a DVD-ROM with the device software.
- This application software enables the exchange of data and, in some cases, control of the medical device by the computing device.
- a portable medical device includes a communication system, a web application server configured to create a server-client communications connection with a user device via the communication system, wherein the web application server is further configured to automatically send to the user device a software application to be run on the user device which will permit the user device to access data from the portable medical device, and may also permit the user device to exchange information and data with the medical device, for example configuration information, patient data, and/or initiation of internal checks.
- Example 2 the portable medical device of Example 1, wherein the portable medical device is a defibrillator.
- Example 3 the portable medical device of Example 1, wherein the portable medical device is an AED.
- Example 4 the portable medical device of Example 1, wherein the portable medical device is a non-invasive cardiac support pump.
- Example 5 the portable medical device of Example 1, wherein the portable medical device is a wearable cardioverter defibrillator.
- Example 6 the portable medical device of any of Examples 1 through 4, wherein the web application server is further configured to prompt automatic reboot of the user device upon the user device's receipt of the software application.
- Example 7 the portable medical device of any of Examples 1 through 6, wherein the web application server is further configured to prompt automatic display on the user device of a prompt asking for confirmation of the installation of the software application, for example upon reboot.
- a method for automated delivery of application software supporting the hardware/software capabilities of a medical device includes establishing a server-client communications connection with a user device with a web application server embedded in a medical device, automatically sending to the user device a software application to be run within a web browser of the user device, and sending data from the medical device to the software application running in the web browser.
- Example 9 the method of Example 8, wherein the medical device is a defibrillator and the user device is a computing device.
- Example 10 the method of Example 8, wherein the medical device is an AED.
- Example 11 the method of Example 8, wherein the medical device is a non-invasive cardiac support pump.
- Example 12 the method of Example 8, wherein the medical device is a wearable cardioverter defibrillator.
- Example 13 the method of any of Examples 8 through 12, further comprising prompting automatic reboot of the user device upon the user device's receipt of the software application.
- Example 14 the method of any of Examples 8 through 13, further comprising initiating automatic display on the user device of a prompt asking for confirmation of the installation of the software application upon reboot.
- FIG. 1 illustrates a conceptual diagram of a medical device with a web server capable of serving applications to a client device, according to embodiments of the present invention.
- FIG. 2 illustrates a computer system, or computing device system, according to embodiments of the present invention.
- FIG. 3 illustrates the system of FIG. 1 with a web browser 20 in the client device, according to embodiments of the present invention.
- FIG. 4 depicts a flow chart illustrating a device web server connection method, according to embodiments of the present invention.
- FIG. 5 illustrates a system with two medical devices connected, each having a web server and a web client, according to embodiments of the present invention.
- FIGS. 1 and 3 illustrate a system 100 for communication between a device 2 and a user device 4 , according to embodiments of the present invention.
- the term “user device” is used in its broadest sense to refer to any computing device, and may also be referred to as a user computing device, a client device, a computer system, a client computing device, and a client computing user device.
- the device 2 may be a medical device, for example a defibrillator, automatic external defibrillator (AED), a non-invasive cardiac support pump (for example a ZOLL® AutoPulse® device), a wearable cardioverter defibrillator (for example a ZOLL® LifeVest® device), and the like.
- User device 4 may be a personal computer or other computing device capable of running web applications, for example a mobile phone, an iPad®, and/or a personal computer. User device 4 may also be a medical device, for example the same kind of device as device 2 , according to embodiments of the present invention.
- Device 2 may include a web server 10 , according to embodiments of the present invention, and device 4 may include a web browser 20 configured to interact with the web server 10 of device, for example using Internet Protocol and/or Hypertext Transfer Protocol and/or other similar protocols, according to embodiments of the present invention.
- element 20 may also be a web client, which may or may not include a user interface component, and which may use web protocols for the interaction with the web server, according to embodiments of the present invention.
- Web interactions need not be limited to the exchange of web pages; web service protocols including REST, XML-RPC, JSON-RPC, SOAP, and PB may also be used.
- Embodiments of the present invention work with wired and/or wireless and/or other communications connections which support a web server delivering content.
- Embodiments of the present invention provide an ability to better manage device-specific or operating system-specific software applications by embedding a web application server 10 into the device 2 hardware.
- the web server 10 is configured to automatically serve a version of the software to the user's computer 4 which matches the version of the device 2 installed onto the user's computer, according to embodiments of the present invention.
- the web server 10 is configured to automatically serve the appropriate supporting application software to the target client computing device 4 that supports the functional capabilities of the medical device 2 , according to embodiments of the present invention.
- the software application will automatically get upgraded (or downgraded) as necessary based upon what is done to the baseline software of the device 2 , and multiple versions of the application will get transparently used as necessary (by client machine 4 ) for users using multiple versions of the same device 2 , according to embodiments of the present invention
- communicably coupled includes electrically coupled by, for example, a wire; optically coupled by, for example, an optical cable; and/or wirelessly coupled by, for example, a radio frequency or other transmission media.
- communicably coupled also includes, for example, indirect coupling, such as through a network or a series of devices and/or communication protocols, or direct coupling.
- communicably coupled may include coupled wirelessly via Wi-Fi and/or BlueTooth®.
- the device 2 and device 4 may also be coupled via an ad hoc, self-configuring, self-healing network, according to embodiments of the present invention.
- Embodiments of the present invention include a device 2 with a web server 10 embedded therein, in addition to the conventional code for running the device 2 .
- the web server 10 may be configured to target the web browser 20 of the device 4 as a sort of platform within a platform, which permits the manufacturer of device 2 to design for a much larger hardware and operating system cross section.
- the manufacturer of device 2 may also benefit as third parties upgrade the performance of their products, according to embodiments of the present invention.
- the software for device 2 and web server 10 may launch larger and more powerful applications for management within external device's 4 caching space by external devices 4 themselves, which may provide transparent version control for the device 2 manufacturer and a more seamless customer experience across devices 2 .
- the applications served by device 2 and server 10 are treated as blocks of data by the devices 2 themselves. Although such applications reside within device 2 in order to be served by them, the device 2 does not execute the application code, and instead all code execution occurs on the client-side machines 4 , according to embodiments of the present invention. As such, the device 2 and server 10 may act simply as a delivery agent for the software, according to embodiments of the present invention.
- Embodiments of the present invention employ standard auto-discovery systems like Bonjour, Zeroconf, mDNS, Avahi, and the like to set up ad hoc connections between device 2 and client computer 4 without requiring any additional hardware or supporting network.
- Device 2 has computing power to run a web server 10 , auto-advertising protocols, and to serve any required combination of JavaScript, HTML, CSS, RDF, JSON, SVG, XML, RSS, and the like kinds of files, according to embodiments of the present invention.
- a user device 4 discovers a medical device 2 and forms a wireless connection (block 402 ).
- the medical device 2 loads device-specific (and target client computing device platform-appropriate) application software onto the user device 4 (block 404 ).
- the user device 4 accesses and displays medical data from medical device 2 using the device-specific application software (block 406 ), according to embodiments of the present invention.
- the user device 4 has an ability to edit information or data on the medical device 2 , for example to display and edit the configuration information, or patient demographic information.
- User device 4 may also initiate some device 2 internal services, for example running diagnostics and/or having diagnostic results returned to device 4 , according to embodiments of the present invention.
- the device 2 and/or server 10 has the capability to auto-advertise its presence, for example with an active wireless signal.
- the device 4 may find device 2 and/or server 10 using one or more auto-discovery protocols, according to embodiments of the present invention.
- FIGS. 1 and 3 illustrate a direct wireless connection between devices 2 and 4
- the devices 2 and 4 may also be connected via a network, for example via the Internet, according to embodiments of the present invention.
- the device 2 may be configured to arbitrarily code data into an arbitrary number of formats, and make the data available to any web browser 20 on any device, according to embodiments of the present invention.
- the device 2 may include a global positioning system (GPS), and may be configured to provide client web browsers 20 with reports on its location, its identity, remote location, and remote diagnostics.
- GPS global positioning system
- the device 4 discovers and connects with the device 2 automatically, and the web server automatically loads the device-specific application software onto device 4 .
- Device 4 may then automatically reboot, and/or the next time device 4 is rebooted, may prompt the user on device startup to confirm the installation of the software provided by web server 10 , according to embodiments of the present invention. If such program installation failed, then the device 4 may be configured to send an error report or fault report back to the device 2 manufacturer, either via device 2 or via another internet connection, according to embodiments of the present invention.
- the web server 10 could also be used to enable other peripheral devices, for example configuring a Bluetooth® keyboard to work to enter data into device 2 .
- the server 10 could simply load software onto a Bluetooth® audio device to configure it to provide audio information to device 2 .
- a Bluetooth® audio device may be a headset which is configured to provide audio input and/or output.
- device 2 is a defibrillator or a cardiopulmonary resuscitation (CPR) assisting device
- audio or voice prompts for CPR could be provided from device 2 into such a headset, according to embodiments of the present invention.
- CPR cardiopulmonary resuscitation
- FIG. 2 is an example of a computer or computing device system 200 with which embodiments of the present invention may be utilized.
- defibrillator 2 and/or computing device 4 may be or incorporate a computer system 200 , according to embodiments of the present invention.
- the computer system includes a bus 201 , at least one processor 202 , at least one communication port 203 , a main memory 204 , a removable storage media 205 , a read only memory 206 , and a mass storage 207 .
- Processor(s) 202 can be any known processor, such as, but not limited to, an Intel® Itanium® or Itanium 2® processor(s), or AMD® Opteron® or Athlon MP® processor(s), or Motorola® lines of processors, or any known microprocessor or processor for a mobile device, such as, but not limited to, ARM, Intel Pentium Mobile, Intel Core i5 Mobile, AMD A6 Series, AMD Phenom II Quad Core Mobile, or like devices.
- Communication port(s) 203 can be any of an RS-232 port for use with a modem based dialup connection, a copper or fiber 10/100/1000 Ethernet port, or a Bluetooth® or WiFi interface, for example.
- Communication port(s) 203 may be chosen depending on a network such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 200 connects.
- Main memory 204 can be Random Access Memory (RAM), or any other dynamic storage device(s) commonly known to one of ordinary skill in the art.
- Read only memory 206 can be any static storage device(s) such as Programmable Read Only Memory (PROM) chips for storing static information such as instructions for processor 202 , for example.
- PROM Programmable Read Only Memory
- Mass storage 207 can be used to store information and instructions.
- flash memory or other storage media may be used, including removable or dedicated memory in a mobile or portable device, according to embodiments of the present invention.
- hard disks such as the Adaptec® family of SCSI drives, an optical disc, an array of disks such as RAID (e.g. the Adaptec family of RAID drives), or any other mass storage devices may be used.
- Bus 201 communicably couples processor(s) 202 with the other memory, storage and communication blocks.
- Bus 201 can be a PCI/PCI-X or SCSI based system bus depending on the storage devices used, for example.
- Removable storage media 205 can be any kind of external hard-drives, floppy drives, flash drives, zip drives, compact disc-read only memory (CD-ROM), compact disc-re-writable (CD-RW), or digital video disk-read only memory (DVD-ROM), for example.
- CD-ROM compact disc-read only memory
- CD-RW compact disc-re-writable
- DVD-ROM digital video disk-read only memory
- server 10 may be configured to not only provide content (e.g. software applications or medical data from device 2 ), but it may also be configured to provide one or more links to web browser 20 , thereby providing web browser 20 with information for finding and accessing such information on another device on a network 12 .
- the web browser 20 may be configured to access such content via the link through its own connection to the network 12 , such as the Internet, if it has such a connection, and/or may be configured to access such content via the link through a network 12 connection of the web server 10 , according to embodiments of the present invention.
- Web server 10 may provide such links for content which may be dynamic or changing over time, for example.
- system 200 may be configured to permit web server 10 to communicate not only with a computing device, but with a computing device that is another medical device 6 , such as, for example, another defibrillator or another type of medical device, according to embodiments of the present invention.
- Medical device 6 may include a web server 16 and/or web client 20 , according to embodiments of the present invention.
- the medical device 6 may be configured to auto-discover another medical device 2 , permit an automatic server-client communication to be established between server 10 and client 20 , and may even be configured to permit device 2 to automatically take control of one or more functions of device 6 (e.g. according to a “master-slave” relationship), according to embodiments of the present invention.
- Browser 26 may, in the same or a similar fashion, be configured to automatically connect with server 16 , for example using an auto-discovery protocol, according to embodiments of the present invention.
- Devices 2 , 6 configured in this way may also permit viral distribution of software and/or other content.
- another web browser enabled device (not shown) which is not within the range of device 2 , or is not otherwise in communication with device 2 , may instead automatically connect with the web server 16 of device 6 and receive the same type of software and/or content. This permits software, content, and/or updates thereto to be distributed across multiple devices in a viral fashion, according to embodiments of the present invention.
- the web server need not be restricted to typical embedded languages like C or C++.
- Modern interpreted and just-in-time compiled languages like Python and JavaScript can also be used for server implementation.
- Event-driven approaches found in these languages like Twisted for Python and promises for JavaScript offer many advantages that make them potentially better design choices than the more traditional offerings, according to embodiments of the present invention.
- JavaScript in particular makes it possible to directly share code between server and client, according to embodiments of the present invention.
Landscapes
- Health & Medical Sciences (AREA)
- Engineering & Computer Science (AREA)
- Heart & Thoracic Surgery (AREA)
- General Health & Medical Sciences (AREA)
- Cardiology (AREA)
- Veterinary Medicine (AREA)
- Biomedical Technology (AREA)
- Public Health (AREA)
- Life Sciences & Earth Sciences (AREA)
- Animal Behavior & Ethology (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Hematology (AREA)
- Anesthesiology (AREA)
- Mechanical Engineering (AREA)
- Nuclear Medicine, Radiotherapy & Molecular Imaging (AREA)
- Radiology & Medical Imaging (AREA)
- Human Computer Interaction (AREA)
- Computing Systems (AREA)
- Medical Informatics (AREA)
- Medical Treatment And Welfare Office Work (AREA)
- Electrotherapy Devices (AREA)
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 16/256,927 (filed 24 Jan. 2019), which is a continuation of U.S. patent application Ser. No. 15/354,156 (filed 17 Nov. 2016, now U.S. Pat. No. 10,230,823), which is a continuation of U.S. patent application Ser. No. 13/652,285 (filed 15 Oct. 2012, now U.S. Pat. No. 9,531,837), which claims the benefit of U.S. Provisional Patent Application 61/547,570 (filed 14 Oct. 2011) and U.S. Provisional Patent Application 61/592,386 (filed 30 Jan. 2012). All of these priority applications are hereby incorporated by reference herein in their entireties.
- Embodiments of the present invention relate generally to emergency medical devices, and more specifically to applications for communicating with such devices.
- Existing devices for use in emergency medical response situations, for example defibrillators, often each have their own software applications providing an interface for receiving data from such devices. For example, a defibrillator device may include a physical interface (such as a serial port or Ethernet interface) for connecting the defibrillator with a personal computer. The user must install device application software onto the personal computer, either by download or using physical media provided to the user, for example a DVD-ROM with the device software. This application software enables the exchange of data and, in some cases, control of the medical device by the computing device.
- However, distributing device application software in this way requires that the software developer provide separate development efforts based on target hardware and software platforms, for example MS-Windows, Mac OS X, Linux, iOS, Android, and Windows Mobile. Maintenance and upgrades for such software can also be challenging, as it requires redistribution of software and must often be carefully synchronized with vendor-specific upgrades. The makers of such software and devices also often have difficulty tracking which user is using which version of software; furthermore, the fact that a particular version of software was delivered to a user does not always mean that the user installed that particular version.
- In Example 1, a portable medical device according to an embodiment of the present invention includes a communication system, a web application server configured to create a server-client communications connection with a user device via the communication system, wherein the web application server is further configured to automatically send to the user device a software application to be run on the user device which will permit the user device to access data from the portable medical device, and may also permit the user device to exchange information and data with the medical device, for example configuration information, patient data, and/or initiation of internal checks.
- In Example 2, the portable medical device of Example 1, wherein the portable medical device is a defibrillator.
- In Example 3, the portable medical device of Example 1, wherein the portable medical device is an AED.
- In Example 4, the portable medical device of Example 1, wherein the portable medical device is a non-invasive cardiac support pump.
- In Example 5, the portable medical device of Example 1, wherein the portable medical device is a wearable cardioverter defibrillator.
- In Example 6, the portable medical device of any of Examples 1 through 4, wherein the web application server is further configured to prompt automatic reboot of the user device upon the user device's receipt of the software application.
- In Example 7, the portable medical device of any of Examples 1 through 6, wherein the web application server is further configured to prompt automatic display on the user device of a prompt asking for confirmation of the installation of the software application, for example upon reboot.
- In Example 8, a method for automated delivery of application software supporting the hardware/software capabilities of a medical device according to embodiments of the present invention includes establishing a server-client communications connection with a user device with a web application server embedded in a medical device, automatically sending to the user device a software application to be run within a web browser of the user device, and sending data from the medical device to the software application running in the web browser.
- In Example 9, the method of Example 8, wherein the medical device is a defibrillator and the user device is a computing device.
- In Example 10, the method of Example 8, wherein the medical device is an AED.
- In Example 11, the method of Example 8, wherein the medical device is a non-invasive cardiac support pump.
- In Example 12, the method of Example 8, wherein the medical device is a wearable cardioverter defibrillator.
- In Example 13, the method of any of Examples 8 through 12, further comprising prompting automatic reboot of the user device upon the user device's receipt of the software application.
- In Example 14, the method of any of Examples 8 through 13, further comprising initiating automatic display on the user device of a prompt asking for confirmation of the installation of the software application upon reboot.
- While multiple embodiments are disclosed, still other embodiments of the present invention will become apparent to those skilled in the art from the following detailed description, which shows and describes illustrative embodiments of the invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive.
-
FIG. 1 illustrates a conceptual diagram of a medical device with a web server capable of serving applications to a client device, according to embodiments of the present invention. -
FIG. 2 illustrates a computer system, or computing device system, according to embodiments of the present invention. -
FIG. 3 illustrates the system ofFIG. 1 with aweb browser 20 in the client device, according to embodiments of the present invention. -
FIG. 4 depicts a flow chart illustrating a device web server connection method, according to embodiments of the present invention. -
FIG. 5 illustrates a system with two medical devices connected, each having a web server and a web client, according to embodiments of the present invention. - While the invention is amenable to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and are described in detail below. The intention, however, is not to limit the invention to the particular embodiments described. On the contrary, the invention is intended to cover all modifications, equivalents, and alternatives falling within the scope of the invention as defined by the appended claims.
-
FIGS. 1 and 3 illustrate asystem 100 for communication between adevice 2 and auser device 4, according to embodiments of the present invention. As used herein, the term “user device” is used in its broadest sense to refer to any computing device, and may also be referred to as a user computing device, a client device, a computer system, a client computing device, and a client computing user device. Thedevice 2 may be a medical device, for example a defibrillator, automatic external defibrillator (AED), a non-invasive cardiac support pump (for example a ZOLL® AutoPulse® device), a wearable cardioverter defibrillator (for example a ZOLL® LifeVest® device), and the like.User device 4 may be a personal computer or other computing device capable of running web applications, for example a mobile phone, an iPad®, and/or a personal computer.User device 4 may also be a medical device, for example the same kind of device asdevice 2, according to embodiments of the present invention.Device 2 may include aweb server 10, according to embodiments of the present invention, anddevice 4 may include aweb browser 20 configured to interact with theweb server 10 of device, for example using Internet Protocol and/or Hypertext Transfer Protocol and/or other similar protocols, according to embodiments of the present invention. Althoughelement 20 is described as a browser,element 20 may also be a web client, which may or may not include a user interface component, and which may use web protocols for the interaction with the web server, according to embodiments of the present invention. Web interactions need not be limited to the exchange of web pages; web service protocols including REST, XML-RPC, JSON-RPC, SOAP, and PB may also be used. Embodiments of the present invention work with wired and/or wireless and/or other communications connections which support a web server delivering content. - Embodiments of the present invention provide an ability to better manage device-specific or operating system-specific software applications by embedding a
web application server 10 into thedevice 2 hardware. For device software code that is designed to work cross-platform, theweb server 10 is configured to automatically serve a version of the software to the user'scomputer 4 which matches the version of thedevice 2 installed onto the user's computer, according to embodiments of the present invention. In other words, in order to interoperate withclient computing devices 4 that are cross platform, theweb server 10 is configured to automatically serve the appropriate supporting application software to the targetclient computing device 4 that supports the functional capabilities of themedical device 2, according to embodiments of the present invention. The software application will automatically get upgraded (or downgraded) as necessary based upon what is done to the baseline software of thedevice 2, and multiple versions of the application will get transparently used as necessary (by client machine 4) for users using multiple versions of thesame device 2, according to embodiments of the present invention - As used herein, the phrase “communicably coupled” is used in its broadest sense to refer to any coupling whereby information may be passed. Thus, for example, communicably coupled includes electrically coupled by, for example, a wire; optically coupled by, for example, an optical cable; and/or wirelessly coupled by, for example, a radio frequency or other transmission media. “Communicably coupled” also includes, for example, indirect coupling, such as through a network or a series of devices and/or communication protocols, or direct coupling. For example, “communicably coupled” may include coupled wirelessly via Wi-Fi and/or BlueTooth®. The
device 2 anddevice 4 may also be coupled via an ad hoc, self-configuring, self-healing network, according to embodiments of the present invention. - Embodiments of the present invention include a
device 2 with aweb server 10 embedded therein, in addition to the conventional code for running thedevice 2. Theweb server 10 may be configured to target theweb browser 20 of thedevice 4 as a sort of platform within a platform, which permits the manufacturer ofdevice 2 to design for a much larger hardware and operating system cross section. The manufacturer ofdevice 2 may also benefit as third parties upgrade the performance of their products, according to embodiments of the present invention. According to some embodiments of the present invention, the software fordevice 2 andweb server 10 may launch larger and more powerful applications for management within external device's 4 caching space byexternal devices 4 themselves, which may provide transparent version control for thedevice 2 manufacturer and a more seamless customer experience acrossdevices 2. - According to some embodiments of the present invention, the applications served by
device 2 andserver 10 are treated as blocks of data by thedevices 2 themselves. Although such applications reside withindevice 2 in order to be served by them, thedevice 2 does not execute the application code, and instead all code execution occurs on the client-side machines 4, according to embodiments of the present invention. As such, thedevice 2 andserver 10 may act simply as a delivery agent for the software, according to embodiments of the present invention. - Embodiments of the present invention employ standard auto-discovery systems like Bonjour, Zeroconf, mDNS, Avahi, and the like to set up ad hoc connections between
device 2 andclient computer 4 without requiring any additional hardware or supporting network.Device 2 has computing power to run aweb server 10, auto-advertising protocols, and to serve any required combination of JavaScript, HTML, CSS, RDF, JSON, SVG, XML, RSS, and the like kinds of files, according to embodiments of the present invention. As illustrated inFIG. 4 , auser device 4 discovers amedical device 2 and forms a wireless connection (block 402). Themedical device 2 loads device-specific (and target client computing device platform-appropriate) application software onto the user device 4 (block 404). Theuser device 4 accesses and displays medical data frommedical device 2 using the device-specific application software (block 406), according to embodiments of the present invention. According to some embodiments of the present invention, theuser device 4 has an ability to edit information or data on themedical device 2, for example to display and edit the configuration information, or patient demographic information.User device 4 may also initiate somedevice 2 internal services, for example running diagnostics and/or having diagnostic results returned todevice 4, according to embodiments of the present invention. Thedevice 2 and/orserver 10 has the capability to auto-advertise its presence, for example with an active wireless signal. Thedevice 4 may finddevice 2 and/orserver 10 using one or more auto-discovery protocols, according to embodiments of the present invention. - Although
FIGS. 1 and 3 illustrate a direct wireless connection betweendevices devices device 2 may be configured to arbitrarily code data into an arbitrary number of formats, and make the data available to anyweb browser 20 on any device, according to embodiments of the present invention. According to some embodiments of the present invention, thedevice 2 may include a global positioning system (GPS), and may be configured to provideclient web browsers 20 with reports on its location, its identity, remote location, and remote diagnostics. - According to some embodiments of the present invention, as described above, the
device 4 discovers and connects with thedevice 2 automatically, and the web server automatically loads the device-specific application software ontodevice 4.Device 4 may then automatically reboot, and/or thenext time device 4 is rebooted, may prompt the user on device startup to confirm the installation of the software provided byweb server 10, according to embodiments of the present invention. If such program installation failed, then thedevice 4 may be configured to send an error report or fault report back to thedevice 2 manufacturer, either viadevice 2 or via another internet connection, according to embodiments of the present invention. Theweb server 10 could also be used to enable other peripheral devices, for example configuring a Bluetooth® keyboard to work to enter data intodevice 2. As another example, instead of installing a microphone indevice 2, theserver 10 could simply load software onto a Bluetooth® audio device to configure it to provide audio information todevice 2. For example, such an audio device may be a headset which is configured to provide audio input and/or output. For example, ifdevice 2 is a defibrillator or a cardiopulmonary resuscitation (CPR) assisting device, audio or voice prompts for CPR could be provided fromdevice 2 into such a headset, according to embodiments of the present invention. -
FIG. 2 is an example of a computer orcomputing device system 200 with which embodiments of the present invention may be utilized. For example,defibrillator 2 and/orcomputing device 4 may be or incorporate acomputer system 200, according to embodiments of the present invention. According to the present example, the computer system includes abus 201, at least oneprocessor 202, at least onecommunication port 203, amain memory 204, aremovable storage media 205, a read onlymemory 206, and amass storage 207. - Processor(s) 202 can be any known processor, such as, but not limited to, an Intel® Itanium® or
Itanium 2® processor(s), or AMD® Opteron® or Athlon MP® processor(s), or Motorola® lines of processors, or any known microprocessor or processor for a mobile device, such as, but not limited to, ARM, Intel Pentium Mobile, Intel Core i5 Mobile, AMD A6 Series, AMD Phenom II Quad Core Mobile, or like devices. Communication port(s) 203 can be any of an RS-232 port for use with a modem based dialup connection, a copper orfiber 10/100/1000 Ethernet port, or a Bluetooth® or WiFi interface, for example. Communication port(s) 203 may be chosen depending on a network such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which thecomputer system 200 connects.Main memory 204 can be Random Access Memory (RAM), or any other dynamic storage device(s) commonly known to one of ordinary skill in the art. Read onlymemory 206 can be any static storage device(s) such as Programmable Read Only Memory (PROM) chips for storing static information such as instructions forprocessor 202, for example. -
Mass storage 207 can be used to store information and instructions. For example, flash memory or other storage media may be used, including removable or dedicated memory in a mobile or portable device, according to embodiments of the present invention. As another example, hard disks such as the Adaptec® family of SCSI drives, an optical disc, an array of disks such as RAID (e.g. the Adaptec family of RAID drives), or any other mass storage devices may be used.Bus 201 communicably couples processor(s) 202 with the other memory, storage and communication blocks.Bus 201 can be a PCI/PCI-X or SCSI based system bus depending on the storage devices used, for example.Removable storage media 205 can be any kind of external hard-drives, floppy drives, flash drives, zip drives, compact disc-read only memory (CD-ROM), compact disc-re-writable (CD-RW), or digital video disk-read only memory (DVD-ROM), for example. The components described above are meant to exemplify some types of possibilities. In no way should the aforementioned examples limit the scope of the invention, as they are only exemplary embodiments of computer system 400 and related components. - As illustrated in
FIG. 3 ,server 10 may be configured to not only provide content (e.g. software applications or medical data from device 2), but it may also be configured to provide one or more links toweb browser 20, thereby providingweb browser 20 with information for finding and accessing such information on another device on anetwork 12. Theweb browser 20 may be configured to access such content via the link through its own connection to thenetwork 12, such as the Internet, if it has such a connection, and/or may be configured to access such content via the link through anetwork 12 connection of theweb server 10, according to embodiments of the present invention.Web server 10 may provide such links for content which may be dynamic or changing over time, for example. - As shown in
FIG. 5 ,system 200 may be configured to permitweb server 10 to communicate not only with a computing device, but with a computing device that is anothermedical device 6, such as, for example, another defibrillator or another type of medical device, according to embodiments of the present invention.Medical device 6 may include aweb server 16 and/orweb client 20, according to embodiments of the present invention. Themedical device 6 may be configured to auto-discover anothermedical device 2, permit an automatic server-client communication to be established betweenserver 10 andclient 20, and may even be configured to permitdevice 2 to automatically take control of one or more functions of device 6 (e.g. according to a “master-slave” relationship), according to embodiments of the present invention.Browser 26 may, in the same or a similar fashion, be configured to automatically connect withserver 16, for example using an auto-discovery protocol, according to embodiments of the present invention.Devices device 2 has connected todevice 6 and installed or otherwise implemented the software ondevice 6 for communicating withdevice 2, another web browser enabled device (not shown) which is not within the range ofdevice 2, or is not otherwise in communication withdevice 2, may instead automatically connect with theweb server 16 ofdevice 6 and receive the same type of software and/or content. This permits software, content, and/or updates thereto to be distributed across multiple devices in a viral fashion, according to embodiments of the present invention. - According to some embodiments of the present invention, the web server need not be restricted to typical embedded languages like C or C++. Modern interpreted and just-in-time compiled languages like Python and JavaScript can also be used for server implementation. Event-driven approaches found in these languages (like Twisted for Python and promises for JavaScript) offer many advantages that make them potentially better design choices than the more traditional offerings, according to embodiments of the present invention. JavaScript in particular makes it possible to directly share code between server and client, according to embodiments of the present invention.
- Various modifications and additions can be made to the exemplary embodiments discussed without departing from the scope of the present invention. For example, while the embodiments described above refer to particular features, the scope of this invention also includes embodiments having different combinations of features and embodiments that do not include all of the described features. Accordingly, the scope of the present invention is intended to embrace all such alternatives, modifications, and variations as fall within the scope of the claims, together with all equivalents thereof.
Claims (23)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/930,399 US11509705B2 (en) | 2011-10-14 | 2020-07-16 | Automated delivery of medical device support software |
US18/046,665 US20230133749A1 (en) | 2011-10-14 | 2022-10-14 | Automated delivery of medical device support software |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161547570P | 2011-10-14 | 2011-10-14 | |
US201261592386P | 2012-01-30 | 2012-01-30 | |
US13/652,285 US9531837B2 (en) | 2011-10-14 | 2012-10-15 | Automated delivery of medical device support software |
US15/354,156 US10230823B2 (en) | 2011-10-14 | 2016-11-17 | Automated delivery of medical device support software |
US16/256,927 US10757226B2 (en) | 2011-10-14 | 2019-01-24 | Automated delivery of medical device support software |
US16/930,399 US11509705B2 (en) | 2011-10-14 | 2020-07-16 | Automated delivery of medical device support software |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/256,927 Continuation US10757226B2 (en) | 2011-10-14 | 2019-01-24 | Automated delivery of medical device support software |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/046,665 Continuation US20230133749A1 (en) | 2011-10-14 | 2022-10-14 | Automated delivery of medical device support software |
Publications (2)
Publication Number | Publication Date |
---|---|
US20200412838A1 true US20200412838A1 (en) | 2020-12-31 |
US11509705B2 US11509705B2 (en) | 2022-11-22 |
Family
ID=48082559
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/652,285 Active 2033-10-31 US9531837B2 (en) | 2011-10-14 | 2012-10-15 | Automated delivery of medical device support software |
US15/354,156 Active 2032-10-29 US10230823B2 (en) | 2011-10-14 | 2016-11-17 | Automated delivery of medical device support software |
US16/256,927 Active 2032-11-08 US10757226B2 (en) | 2011-10-14 | 2019-01-24 | Automated delivery of medical device support software |
US16/930,399 Active 2032-12-07 US11509705B2 (en) | 2011-10-14 | 2020-07-16 | Automated delivery of medical device support software |
US18/046,665 Pending US20230133749A1 (en) | 2011-10-14 | 2022-10-14 | Automated delivery of medical device support software |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/652,285 Active 2033-10-31 US9531837B2 (en) | 2011-10-14 | 2012-10-15 | Automated delivery of medical device support software |
US15/354,156 Active 2032-10-29 US10230823B2 (en) | 2011-10-14 | 2016-11-17 | Automated delivery of medical device support software |
US16/256,927 Active 2032-11-08 US10757226B2 (en) | 2011-10-14 | 2019-01-24 | Automated delivery of medical device support software |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/046,665 Pending US20230133749A1 (en) | 2011-10-14 | 2022-10-14 | Automated delivery of medical device support software |
Country Status (3)
Country | Link |
---|---|
US (5) | US9531837B2 (en) |
EP (1) | EP2766819A4 (en) |
WO (1) | WO2013056194A1 (en) |
Families Citing this family (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7957798B2 (en) | 2003-12-17 | 2011-06-07 | Physio-Control, Inc. | Defibrillator/monitor system having a pod with leads capable of wirelessly communicating |
US10413742B2 (en) | 2008-03-05 | 2019-09-17 | Physio-Control, Inc. | Defibrillator patient monitoring pod |
US11881307B2 (en) * | 2012-05-24 | 2024-01-23 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US10453157B2 (en) | 2010-01-22 | 2019-10-22 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US11210611B2 (en) | 2011-12-21 | 2021-12-28 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US11244745B2 (en) | 2010-01-22 | 2022-02-08 | Deka Products Limited Partnership | Computer-implemented method, system, and apparatus for electronic patient care |
US10911515B2 (en) | 2012-05-24 | 2021-02-02 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US20110313789A1 (en) | 2010-01-22 | 2011-12-22 | Deka Products Limited Partnership | Electronic patient monitoring system |
WO2013056194A1 (en) | 2011-10-14 | 2013-04-18 | Zoll Medical Corporation | Automated delivery of medical device support software |
US8929980B2 (en) | 2012-05-03 | 2015-01-06 | Physio-Control, Inc. | External defibrillator electrode, method and system for reducing ECG artifact |
US9457197B2 (en) | 2012-05-08 | 2016-10-04 | Physio-Control, Inc. | Utility module system |
US20140005506A1 (en) | 2012-06-29 | 2014-01-02 | Zoll Medical Corporation | Rescue scene video transmission |
US10303852B2 (en) | 2012-07-02 | 2019-05-28 | Physio-Control, Inc. | Decision support tool for use with a medical monitor-defibrillator |
US10099063B2 (en) | 2012-07-02 | 2018-10-16 | Physio-Control, Inc. | Medical monitor-defibrillator with defibrillator and data operations processors |
US9026147B2 (en) | 2012-09-24 | 2015-05-05 | Physio-Control, Inc. | Defibrillator location tracking device |
US9282911B2 (en) | 2012-11-27 | 2016-03-15 | Physio-Control, Inc. | Linear display of ECG signals |
US9881132B2 (en) * | 2012-12-03 | 2018-01-30 | Change Healthcare Llc | Method and apparatus for remote workstation synchronization |
US9215516B2 (en) | 2013-03-15 | 2015-12-15 | Covidien Lp | System and method for identifying newly captured configuration parameters of a plurality of medical devices |
US10169064B2 (en) | 2014-04-29 | 2019-01-01 | Vmware, Inc. | Automatic network configuration of a pre-configured hyper-converged computing device |
WO2016160851A1 (en) | 2015-03-30 | 2016-10-06 | Zoll Medical Corporation | Customer-or patient-based selective data encryption in medical device management |
US10665341B2 (en) | 2015-03-30 | 2020-05-26 | Zoll Medical Corporation | Customer—or patient-based selective data encryption in medical device management |
US20160321400A1 (en) * | 2015-03-30 | 2016-11-03 | Zoll Medical Corporation | Clinical Data Handoff in Device Management and Data Sharing |
EP3277374A4 (en) | 2015-03-30 | 2019-01-09 | Zoll Medical Corporation | Medical device management |
US10747511B2 (en) * | 2015-04-28 | 2020-08-18 | Microsoft Technology Licensing, Llc | Compiler optimization of coroutines |
US10185513B1 (en) | 2015-06-05 | 2019-01-22 | Life365, Inc. | Device configured for dynamic software change |
US9974492B1 (en) | 2015-06-05 | 2018-05-22 | Life365, Inc. | Health monitoring and communications device |
US10560135B1 (en) | 2015-06-05 | 2020-02-11 | Life365, Inc. | Health, wellness and activity monitor |
US11329683B1 (en) | 2015-06-05 | 2022-05-10 | Life365, Inc. | Device configured for functional diagnosis and updates |
US10388411B1 (en) * | 2015-09-02 | 2019-08-20 | Life365, Inc. | Device configured for functional diagnosis and updates |
US11166628B2 (en) | 2016-02-02 | 2021-11-09 | Physio-Control, Inc. | Laryngoscope with handle-grip activated recording |
US10697811B2 (en) | 2016-10-31 | 2020-06-30 | Nokia Technologies Oy | Method, apparatus and computer program product for providing sensor data collection and sensor configuration |
EP3554630B1 (en) * | 2016-12-19 | 2023-07-12 | HeartHero, Inc. | Automated external defibrillator device |
US11524168B2 (en) | 2016-12-19 | 2022-12-13 | Hearthero, Inc. | Self-contained, connected automated external defibrillator systems and methods of use |
US11179293B2 (en) | 2017-07-28 | 2021-11-23 | Stryker Corporation | Patient support system with chest compression system and harness assembly with sensor system |
WO2019113598A1 (en) * | 2017-12-08 | 2019-06-13 | Visionary Technologies LLC | System and method for sharing contextually relevant information |
US10572314B2 (en) | 2018-01-11 | 2020-02-25 | Intel Corporation | Methods and apparatus to distribute a workload for execution |
USD873554S1 (en) | 2018-08-24 | 2020-01-28 | EIR, Inc. | Automated external defibrillator case |
USD889116S1 (en) | 2018-08-24 | 2020-07-07 | EIR, Inc. | Automated external defibrillator cardiac pad compartment cover |
USD889115S1 (en) | 2018-08-24 | 2020-07-07 | EIR, Inc. | Automated external defibrillator handle |
WO2022072734A1 (en) | 2020-09-30 | 2022-04-07 | Zoll Medical Corporation | Remote monitoring devices and related methods and systems with audible aed signal listening |
EP4228742A4 (en) | 2020-10-14 | 2024-04-03 | HeartHero, Inc. | Automated external defibrillator systems and methods of use |
US11529526B1 (en) | 2021-12-10 | 2022-12-20 | Hearthero, Inc. | Automated external defibrillator |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120082039A1 (en) * | 2010-10-04 | 2012-04-05 | Qualcomm Incorporated | Methods and apparatus for providing directional information for peer discovery in peer-to-peer wireless networks |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7281047B2 (en) * | 2001-01-16 | 2007-10-09 | Cognos Incorporated | System and method for automatic provision of an application |
US7103578B2 (en) * | 2001-05-25 | 2006-09-05 | Roche Diagnostics Operations, Inc. | Remote medical device access |
US6744753B2 (en) * | 2001-11-01 | 2004-06-01 | Nokia Corporation | Local service handover |
US20030107487A1 (en) * | 2001-12-10 | 2003-06-12 | Ronen Korman | Method and device for measuring physiological parameters at the wrist |
US20040204743A1 (en) * | 2003-01-14 | 2004-10-14 | Mcgrath Thomas J. | Remotely operating external medical devices |
EP1671253A2 (en) * | 2003-09-24 | 2006-06-21 | Medtronic, Inc. | Apparatus and method for serving medical device application content to a remote computing device |
DE10350538A1 (en) * | 2003-10-29 | 2005-06-16 | Corscience Gmbh & Co.Kg | Communication system and method for processing medical data |
US7788369B2 (en) * | 2003-12-01 | 2010-08-31 | Carefusion 303, Inc. | System and method for network discovery and connection management |
US7743151B2 (en) * | 2004-08-05 | 2010-06-22 | Cardiac Pacemakers, Inc. | System and method for providing digital data communications over a wireless intra-body network |
US7353063B2 (en) * | 2004-12-22 | 2008-04-01 | Cardiac Pacemakers, Inc. | Generating and communicating web content from within an implantable medical device |
CN101185079A (en) * | 2005-04-11 | 2008-05-21 | 霍夫曼-拉罗奇有限公司 | Web-enabled portable medical device |
EP1722310A1 (en) * | 2005-04-12 | 2006-11-15 | Roche Diagnostics GmbH | Medical software download to mobile phone |
US8051414B2 (en) * | 2005-08-01 | 2011-11-01 | Siemens Aktiengesellschaft | Method and system for remote software updating of a medical device |
US20070080223A1 (en) * | 2005-10-07 | 2007-04-12 | Sherwood Services Ag | Remote monitoring of medical device |
US7733224B2 (en) * | 2006-06-30 | 2010-06-08 | Bao Tran | Mesh network personal emergency response appliance |
US8532095B2 (en) * | 2005-11-18 | 2013-09-10 | Cisco Technology, Inc. | Techniques configuring customer equipment for network operations from provider edge |
US10637724B2 (en) * | 2006-09-25 | 2020-04-28 | Remot3.It, Inc. | Managing network connected devices |
US20090204422A1 (en) * | 2008-02-12 | 2009-08-13 | James Terry L | System and Method for Remotely Updating a Health Station |
US20090276515A1 (en) * | 2008-05-02 | 2009-11-05 | Boston Scientific Scimed, Inc. | Multi-modality network for improved workflow |
WO2010132617A2 (en) * | 2009-05-12 | 2010-11-18 | Chronicmobile, Inc. | Methods and systems for managing, controlling and monitoring medical devices via one or more software applications functioning in a secure environment |
US8565871B2 (en) * | 2009-09-07 | 2013-10-22 | Qualcomm Incorporated | Automated external defibrillator device with integrated wireless modem |
US8171094B2 (en) * | 2010-01-19 | 2012-05-01 | Event Medical, Inc. | System and method for communicating over a network with a medical device |
JP5418442B2 (en) * | 2010-08-18 | 2014-02-19 | 株式会社リコー | Information processing apparatus, electronic device, update processing support method, update processing support program, and update processing support system |
JP5782868B2 (en) * | 2010-09-16 | 2015-09-24 | 株式会社リコー | Communication device, update method and program |
JP2014502172A (en) * | 2010-10-18 | 2014-01-30 | スリーエム イノベイティブ プロパティズ カンパニー | Multifunctional medical device for telemedicine applications |
US20130013339A1 (en) * | 2010-10-27 | 2013-01-10 | Practice Communications LLC | Systems and methods for medical data storage and retrieval |
US8694100B2 (en) * | 2010-11-30 | 2014-04-08 | Physio-Control, Inc. | Medical device including setup option reporting |
US8676312B2 (en) * | 2011-05-19 | 2014-03-18 | Physio-Control, Inc. | Medical devices alerting user about potential interruption of wireless patient data transfer |
WO2013056194A1 (en) | 2011-10-14 | 2013-04-18 | Zoll Medical Corporation | Automated delivery of medical device support software |
-
2012
- 2012-10-13 WO PCT/US2012/060154 patent/WO2013056194A1/en active Application Filing
- 2012-10-13 EP EP12840431.6A patent/EP2766819A4/en not_active Withdrawn
- 2012-10-15 US US13/652,285 patent/US9531837B2/en active Active
-
2016
- 2016-11-17 US US15/354,156 patent/US10230823B2/en active Active
-
2019
- 2019-01-24 US US16/256,927 patent/US10757226B2/en active Active
-
2020
- 2020-07-16 US US16/930,399 patent/US11509705B2/en active Active
-
2022
- 2022-10-14 US US18/046,665 patent/US20230133749A1/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120082039A1 (en) * | 2010-10-04 | 2012-04-05 | Qualcomm Incorporated | Methods and apparatus for providing directional information for peer discovery in peer-to-peer wireless networks |
Also Published As
Publication number | Publication date |
---|---|
US20230133749A1 (en) | 2023-05-04 |
EP2766819A4 (en) | 2015-03-11 |
WO2013056194A1 (en) | 2013-04-18 |
US10230823B2 (en) | 2019-03-12 |
US20190230193A1 (en) | 2019-07-25 |
US10757226B2 (en) | 2020-08-25 |
US11509705B2 (en) | 2022-11-22 |
US20130132465A1 (en) | 2013-05-23 |
US9531837B2 (en) | 2016-12-27 |
US20170230483A1 (en) | 2017-08-10 |
EP2766819A1 (en) | 2014-08-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11509705B2 (en) | Automated delivery of medical device support software | |
US9471752B2 (en) | Operating environment monitor for medical device programming | |
US20150370973A1 (en) | Method for transferring operational data to a medical device located within a healthcare environment | |
JP2008535599A (en) | Download medical software to your mobile phone | |
EP2109287A1 (en) | Multiple client control system | |
TWI626593B (en) | Method and apparatus for upgrading software | |
CN108630308A (en) | Use the system and device of the electronic patient care of WEB service | |
JP2022524329A (en) | Automatic network provisioning of medical devices | |
US20120054735A1 (en) | Installing a computer program | |
EP2688361A2 (en) | Configuration method for data interface and terminal device | |
JP2023025114A (en) | Method and equipment for configuring medical device | |
US20040073276A1 (en) | Programming system for medical devices, a server for such a system and a method for managing the system | |
KR20180050001A (en) | Firmware upgrade system and method for IoT | |
CN102567050B (en) | The method and apparatus of B/S system remote deploying projects | |
CN112527669A (en) | Self-testing method and system for local service | |
US9870447B2 (en) | Medical data transfer component | |
WO2010028801A2 (en) | Extensible therapy delivery system and method thereof | |
US20140222905A1 (en) | Control device, and method for transfer control | |
CN114026833A (en) | Method for data communication between infusion station and front-end computing device in healthcare environment | |
US11997167B2 (en) | Method for data communication between a server system and a front-end computing device in a healthcare environment | |
US20240100232A1 (en) | Dialysis system having remote monitoring and control | |
WO2023046785A1 (en) | Usb terminal server | |
JP2019110395A (en) | VPN controller, VPN control method, and VPN control program | |
JP2002222121A (en) | Information terminal support system using internet | |
US20140304702A1 (en) | Centralized System With Components and Features Hosting |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ZOLL MEDICAL CORPORATION, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROWN, ERIC W.;REEL/FRAME:053226/0537 Effective date: 20141003 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |