EP2805299A1 - Systèmes et procédés de surveillance à distance pour dispositifs médicaux - Google Patents

Systèmes et procédés de surveillance à distance pour dispositifs médicaux

Info

Publication number
EP2805299A1
EP2805299A1 EP13738062.2A EP13738062A EP2805299A1 EP 2805299 A1 EP2805299 A1 EP 2805299A1 EP 13738062 A EP13738062 A EP 13738062A EP 2805299 A1 EP2805299 A1 EP 2805299A1
Authority
EP
European Patent Office
Prior art keywords
data
medical device
remote monitoring
patient
server
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.)
Withdrawn
Application number
EP13738062.2A
Other languages
German (de)
English (en)
Other versions
EP2805299A4 (fr
Inventor
Joel D. Wiesner
Stacey B. HARRINGTON
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Covidien LP
Original Assignee
Covidien LP
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from US13/352,608 external-priority patent/US9495511B2/en
Application filed by Covidien LP filed Critical Covidien LP
Publication of EP2805299A1 publication Critical patent/EP2805299A1/fr
Publication of EP2805299A4 publication Critical patent/EP2805299A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/22—Social work or social welfare, e.g. community support activities or counselling services
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/40—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation

Definitions

  • the present application is directed to a remote monitoring system for monitoring medical devices in communication with a wireless communication network, and more particularly, to a remote monitoring system having a plurality of monitoring devices for monitoring medical devices that communicate with the wireless
  • ZIGBEE networks based on the TEEE 802.15.4 standard for wireless personal area networks have been used for collecting information from a variety of medical devices in accordance with IEEE 11073 Device Specializations for point-of-care medical device communication, including for example pulse oximeters, blood pressure monitors, pulse monitors, weight scales and glucose meters. See, e.g., ZIGBEE Wireless Sensor
  • ZIGBEE networks provide the advantage of being dynamically configurable, for example, in "self-healing" mesh configurations, and operating with low power requirements (enabling, for example, ZIGBEE transceivers to be integrally coupled to the medical devices under battery power).
  • transmission ranges between individual ZIGBEE transceivers are generally limited to no more than several hundred feet.
  • such networks are suitable for on-site communications with medical devices, but unusable for centralized monitoring locations located off-site.
  • a hybrid system may be employed in which one or more wireless personal area networks are configured to facilitate on-site communications between medical devices and one or more wireless relay modules which are further configured to communicate with off-site centralized monitoring systems (for example, via a wireless wide-area network (WWAN) such as a mobile telephone data network, for example, based on a Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA) cellular network, or associated wireless data channels).
  • WWAN wireless wide-area network
  • GSM Global System for Mobile Communications
  • CDMA Code Division Multiple Access
  • HIPAA Health Insurance Portability and Accountability Act of 1996
  • communication of information between the monitored medical devices and the central monitoring location must be done securely, and medical device and associated patient information must be made available only to personnel accessing the centralized monitoring systems who are in possession of the appropriate access credentials.
  • the centralized monitoring system In order to be viable, the centralized monitoring system must also be capable of recognizing medical device information indicating an alert condition requiring response by on-site or other specialized personnel and reaching those on-site or specialized personnel to report the alert condition in a timely " fashion.
  • a remote, centralized medical information monitoring system that communicates over a wireless network of wide reach (for example, a wireless wide area network) with one or more critical care and/or home care health service centers via one or more wireless relay modules at each site, where the wireless relay modules relay communications provided by on-site medical devices over a wireless local area network or wireless personal area network. It would further be desirable for the centralized medical information monitoring system to be capable of also configuring medical devices according to associations with individual sites and patients, of logging communications from medical devices, of displaying medical device data to users of the centralized medical information monitoring system who are able to provide sufficient credentials, and of recognizing medical device alert conditions and reporting these conditions to responsible personnel in a timely fashion.
  • the present invention is directed to a remote monitoring system and method for monitoring the status of a plurality of medical devices located remotely from the monitoring system at a patient care or home care facility.
  • one or more medical devices including but not limited to respirators, enteral feeding devices, pulse oximeters, blood pressure monitors, pulse monitors, weight scales and glucose meters
  • An interface circuit is coupled to each medical device, and is configured for communicating with one of a plurality of the wireless relay modules via a wireless relay network.
  • the wireless relay modules are further configured to communicate with the remote monitoring device over an internet-accessible wireless communication network, and preferably, a wireless wide-area network (WWAN) such as a mobile telephone data network including (for example, based on a Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA) cellular network or associated wireless data channels).
  • WWAN wireless wide-area network
  • GSM Global System for Mobile Communications
  • CDMA Code Division Multiple Access
  • communications over each of the wireless networks are preferably conducted securely.
  • the remote monitoring system and method includes a device integration server in communication with the wireless relay modules for receiving data packets from the wireless relay modules including information provided by the medical devices.
  • This information includes identification of an associated medical device and may include data of the medical device, and is preferably encrypted or otherwise securely transmitted, for example, in compliance with HIPAA patient data privacy provisions.
  • the information may include encrypted or otherwise securely transmitted patient identification information, which in addition may preferably be coded in its unencrypted state to avoid any reference to the patient's identity.
  • the remote monitoring system also includes a data management system including a secure device web server and a device control database, and an outbound web server.
  • the data management system is configured to log information provided to the device integration server concerning the medical devices.
  • the outbound web server (alternatively referred to as "web server” herein) is configured to provide webpages including the data of the medical devices for display on a first and second remote monitoring devices, subject to authentication of an associated data request originating from the monitoring device.
  • the second monitoring device may advantageously be for use by a relative of the patient, such as a parent, caregiver or nurse, who may be located proximate or remote to the patient.
  • a system for enabling the remote monitoring of at least one medical device includes a device integrator server in communication with at least one wireless relay device configured to transmit data packets containing information provided by at least one medical device. Each data packet includes medical device data and at least a medical device identifier or a patient identifier.
  • the system further includes a web server separate from the device integrator server. The web server is configured to provide web pages and to receive at least the medical data.
  • the web server is coupled to a first remote monitoring device via a secure internet connection and is configured to receive medical device data and transmit the medical device data to the first remote monitoring device.
  • the first remote monitoring device displays the medical device data.
  • the web server further transmits at least a portion of the medical device data to a second remote monitoring device for displaying the portion of the medical device data at the second remote monitoring device.
  • the system further includes a data manager system coupled to the device integrator server.
  • the data manager system includes at least a device control database.
  • the web server is configured to verify the patient identifier and medical device identifier before transmitting the medical device data to the first remote monitoring device over the secure internet connection. [0017] In one embodiment, the web server is configured to transmit the portion of the medical device data to the second remote monitoring device over a path which includes a wireless data link.
  • the wireless data link is over a wireless mobile data network.
  • the second remote monitoring device is a portable
  • communications device of least one of a mobile phone, a tablet computer or a portable computer.
  • the web server is configured to transmit to at least one of the first and the second remote monitoring devices, status information concerning a wireless relay network associated with the wireless relay device.
  • a system for enabling the remote monitoring of at least one medical device includes a device integrator server in communication with at least one wireless relay device configured to transmit data packets containing information provided by at least one medical device, wherein each data packet includes data identifying medical device data and at least one of a medical device identifier and a patient identifier and a web server configured for providing web pages for receiving at least the medical device data and, subject to verification of the patient identifier and medical device identifier, transmitting the medical device data to first and second remote monitoring devices via a secure internet connection for displaying the medical device data at the first and remote monitoring devices.
  • the system further includes a data manager system coupled to the device integrator server.
  • the data manager system includes at least a device control database.
  • the system further includes a network status server configured for transmitting to at least one of the first or second remote monitoring devices, status information concerning a wireless relay network associated with the wireless relay device.
  • the network status server is located at a different geographic location than the web server.
  • a method for displaying medical device data by a medical device monitoring system including receiving credentials from a user of a first monitoring device and a request from the user for medical device information for a patient to be monitored and verifying the user is authorized to receive the medical device information. In response to verification being achieved, then, (a) identifying, based at least upon the credentials and the request, an address for a secure patient database having information regarding the patient.
  • the method further includes (b) retrieving patient data and associated medical device identification data by a web server from the patient database over a secure communications link and (c) retrieving medical device data from a device control database for at least one medical device according to the retrieved medical device identification data.
  • the method further includes (d) transmitting the retrieved medical device data by the web server for display on the first monitoring device and (e) transmitting at least a portion of the medical device data to a second remote monitoring device for displaying at the second remote monitoring device.
  • the portion of the medical device data transmitted to the second remote monitoring device includes status information concerning a wireless relay network associated with a wireless relay device.
  • the method further includes receiving from the wireless relay module status information concerning a wireless relay network associated with the wireless relay device.
  • the status information concerning a wireless relay network concerns at least one of signal strength, data rates, particular transmission time stamp, number of active relay modules in the wireless relay network, and a unique identifier number for a particular relay module.
  • transmitting the portion of the medical device data to the second remote monitoring device includes encrypting the portion on the portion of the medical device data.
  • transmitting the retrieved medical device data for display on the first monitoring device further includes encrypting the medical device data with a first encryption technique, and wherein transmitting the portion of the medical device data to the second remote monitoring device includes encrypting the portion of the medical device data using a second encryption technique, wherein the first encryption technique differs from the second encryption technique.
  • a system for enabling the remote monitoring of at least one medical device includes an access point in communication with at least one wireless relay device and a separate patient care database node.
  • the access point includes a device integrator server coupled to a database having stored therein medical device data.
  • the access point further includes a secure device server coupled to the device integrator server.
  • the patient care database node includes a secure patient server coupled to a patient database having patient data stored therein.
  • the secure patient server is coupled through a secure link to the secure device server of the access node.
  • FIG. 1 presents a block diagram of an exemplary remote monitoring system for remotely monitoring medical devices according to the present invention
  • FIG. 2 presents a flow diagram illustrating an exemplary method for registering medical devices with the remote monitoring system according to FIG. 1 ;
  • FIG. 3(a) presents a flow diagram illustrating an exemplary method for retrieving and viewing medical data via the remote monitoring system according to FIG. 1;
  • FIGs. 3(b)-3(d) illustrate exemplary screen displays for retrieving and viewing the medical data according to the method of FIG. 3(a);
  • FIG.4(a) presents a flow diagram illustrating an exemplary method for issuing a command to a medical device via the remote monitoring system according to FIG. 1 ;
  • FIG.4(b) and 4(c) illustrate exemplary screen displays for commanding a medical device according to the method of FIG.4(a);
  • FIG. 5(a) presents a flow diagram illustrating an exemplary method for recognizing and reporting an alert condition according to medical data logged via the remote monitoring system according to FIG. 1;
  • FIG. 5(b) illustrates an exemplary screen display for selecting a recipient for receiving an alert message according to the method of FIG. 5(a);
  • FIG. 6 presents a block diagram of an exemplary computer or server device suitable for use in the remote monitoring system according to FIG. 1.
  • FIGs. 1-6 embodiments are described with reference to FIGs. 1-6.
  • FIG. 1 A diagram of an exemplary system 100 for monitoring medical devices in accordance with the present invention is illustrated in FIG. 1.
  • one or more medical devices 10 are provided at a patient facility 20 for monitoring the medical condition and/or administering medical treatment to one or more patients.
  • Patient facility 20 may comprise a critical care health service center (for example, including hospitals, clinics, assisted living centers and the like) servicing a number of patients, a home facility for servicing one or more patients, or a personal enclosure (for example, a backpack) that may be attached to or worn by an ambulatory patient.
  • a critical care health service center for example, including hospitals, clinics, assisted living centers and the like
  • a personal enclosure for example, a backpack
  • each medical device 10 includes a transceiver having one or more of a transmitter and/or a receiver for respectively transmitting and receiving signals in a facility-oriented wireless network 17 such as, for example, a Low-Rate Wireless Personal Area Networks or "LR-WPAN,” Z1GBEE network or another low-power personal area network such as a low power Bluetooth network, existing or presently under development or consideration.
  • LR-WPAN Low-Rate Wireless Personal Area Networks
  • Z1GBEE network Z1GBEE network
  • another low-power personal area network such as a low power Bluetooth network, existing or presently under development or consideration. See, e.g., Houda Labiod et al., Wi-Fi, Bluetooth. Zigbee and WiMax, Springer 2010, which is incorporated by reference herein in its entirety.
  • interlace circuit 15 may be contained within or disposed external to medical device 10 in accordance with the present invention.
  • Also provided within the patient facility 20 are one or more relay modules
  • Each relay module 30 includes a first transceiver for receiving signals from and transmitting signals to the interface circuits 15 in the facility-oriented wireless network 17, and further includes a second transceiver for wirelessly transmitting signals to and receiving signals from an access point 40 via a wireless wide-area network ("WWAN") 52.
  • WWANs for use with the present invention include, for example, networks based on a Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA) cellular network or associated with the 2G, 3G, 3G Long Term
  • ITU-R Telecommunication Union Radiocommunication Sector
  • communications over each of the facility-oriented wireless network and WWAN are preferably conducted securely using, for example, a Secure Sockets Layer (SSL) protocol or a Transport Layer Security (TLS) protocol or other cryptographic protocols.
  • SSL Secure Sockets Layer
  • TLS Transport Layer Security
  • the access point 40 useable with the present invention includes an inbound server (“device integration server”) 41 that incorporates or otherwise has access to a transceiver for communicating with the relay modules 30 over the WWAN.
  • Medical device data, medical device identifier, and/or patient identifier received by the device integration server 41 over the WWAN is forwarded to a secure device web server 42, which is configured for example to log the received data in association with identification information of the associated medical devices in a device control database 44.
  • Medical device data as generally used herein means data from or about the medical device including, for example, medical device identification, medical device software, medical device settings or status information (including alarm
  • patient identification information includes patient personal identification number(s) "PIN(s)", patient prescriptions, and/or patient medical and/or physiological data as is collected, produced and/or generated by at least one of the medical device and patient identification device; as well as wireless relay network information such as location or status information.
  • An outbound web server 43 is configured, for example, to receive and qualify data retrieval requests submitted by one or more of first remote monitoring devices 62 over a broad-band network 50 (for example, over the Internet), and/or second remote monitoring devices 70, 75 over a wired or wireless wide area network. Tt is advantageous for such requests be made in an encrypted format. Suitable encryption formats useable for such requests may include, for example, formats compliant with the HIP A A regulations described above.
  • the outbound web server 43 requests associated medical device data or portions thereof to be retrieved from the device control database 44 via the secure device web server 42, requests associated program data for constructing a display page from a metadata and applications database 46, and requests associated patient data to be retrieved from a patient database 66 provided in a patient care database node 60 over a secure link 54 via a secure patient web server 64.
  • the secure link 54 can be implemented, for example as another WW AN using a SSL protocol or a TLS protocol.
  • a third party service provider may host the access point 40 to simultaneously support a number of distinct patient and/or home care facilities, thereby eliminating the need for each of these facilities to configure and maintain their own private access point facilities and providing hosting service to each facility that are likely far less than the costs of configuring and maintaining dedicated access point facilities by each care facility provider.
  • access point 40 and patient care database node 60 may nevertheless be integrated into a single access point or node (for example, by a provider of a very large-scale facility provider monitoring many hundreds or thousands of patients).
  • the outbound web server 43 provides an interface for authenticated clinicians or other monitoring personnel to retrieve patient and medical device data from each of the patient care database node 60 and the access point 40 in a convenient and transparent manner such that the details of the configurations and operation of the access point 40 and patient care database node 60 are of no consequence to the clinicians or other monitoring personnel.
  • the first remote monitoring devices 62 are intended to be used by healthcare providers such for example, clinicians, physicians, technicians, nurses and other healthcare specialists monitoring patients associated with medical devices 10.
  • Suitable first remote monitoring devices 62 may include, for example, desktop or laptop computers, tablet computer smart or other mobile phones, or other fixed or portable display devices.
  • the second remote monitoring devices 70, 75 are advantageously intended to be used by caregivers and/or relatives of the patient such as parents, located proximate the patient such as in a homecare environment or small healthcare facility, or nurses at a larger healthcare facilities, e.g., hospitals.
  • Suitable second remote monitoring devices 70, 75 likewise may include, for example, desktop or laptop computers, tablet computer, smart or other mobile phones, or other fixed or other portable communication devices.
  • the outbound web server 43 is depicted coupled to a network status server 80, which monitors the status of the facility-oriented wireless network 17 and associated medical devices 10.
  • the network status server 80 is intended to provide status information concerning the facility-oriented wireless network 17 and associated medical devices 10 to the outbound web server 43.
  • Exemplary status information concerning the facility-oriented wireless network 17 includes, for example, signal strength, data rates, particular transmission time stamps between modules comprising the network 17, number active relay modules in the network 17, unique identifier number for a particular relay module of the network 17.
  • the network status server 80 may be implemented in hardware or software mniiing on an application specific or general purpose processor or computer, as part of or separate from the outbound web server 43. In addition, the network status server 80 is shown coupled to the outbound web server 43 for ease of illustration and discussion purposes only. The network status server 80 may be coupled to any component or network of the access point 40 or facility-oriented wireless network 17 in accordance with the invention.
  • the outbound web server 43 upon retrieving the requested medical device data and patient data from the patient care database node 60, the outbound web server 43 then proceeds to format and transmit the retrieved medical device data and patient data (and /or provide status information concerning the facility-oriented wireless network 17 and associated medical devices 10) as respective webpages or other formats for display by corresponding first and second remote monitoring devices 62, 70, 75 according to the retrieved program data. Tt is possible for the webpages or other formatted information for display to include the same or differing content and format for the intended remote monitoring device user depending upon the retrieved program data.
  • the detailed medical device data provided to and displayed on a first remote monitoring devices 62 for a clinician may differ from the less detailed information provided to and displayed on a second remote monitoring devices 70 monitored by a parent or visiting nurse or other healthcare professional in a homecare environment.
  • the status information concerning the facility- oriented wireless network 17 and associated medical devices 10 may advantageously be provided to first and/or second remote monitoring devices 62, 70 and 75 in the same or different encrypted formats as may be deemed appropriate.
  • the device integration server 41 of FIG. 1 is configured to transmit information and commands to the relay modules 30, for example, for transmitting medical device or alert messages to other WWAN-reachable nodes (for example, cellular telephones of emergency attendants), and/or transmitting operating commands and/or software or firmware updates to the medical devices 10 via the interface circuits 15 and facility-oriented wireless network 17.
  • WWAN-reachable nodes for example, cellular telephones of emergency attendants
  • the device integration server 41 may also be configured to receive and analyze patient metric information from the secure patient web server 64 via the outbound web server 43 and secure device web server 42, or by an alternate and direct secure data link to the secure patient web server 64 in order to prevent unsafe medical device usage based upon the patient metrics information. It is possible for a database (not depicted) accessible, for example, by the device integration server 41 and/or device web server 42, to store various safe and unsafe operating parameters and conditions for performing such analysis. In this manner, the device integration server 41 would function as an additional failsafe for preventing operating errors that could result in patient harm.
  • the device integration server 41 may act, for example, to (1) discard remote monitoring commands programming large bolus or excessive feeding rates that could be harmful to a young child; and (2) provide a warning message or other notification to the user of the likely unsafe usage condition that may result by implementation of such comment.
  • the patient metric information indicates that an enteral feeding pump is associated with a neonate
  • the device integration server 41 may act, for example, to (1) discard remote monitoring commands programming large bolus or excessive feeding rates that could be harmful to a young child; and (2) provide a warning message or other notification to the user of the likely unsafe usage condition that may result by implementation of such comment.
  • the patient metric information indicates that an enteral feeding pump is associated with a neonate
  • the device integration server 41 may act, for example, to (1) discard remote monitoring commands programming large bolus or excessive feeding rates that could be harmful to a young child; and (2) provide a warning message or other notification to the user of the likely unsafe usage condition that may result by implementation of such comment.
  • the patient metric information indicates that an enteral feeding pump is associated
  • the device integration server may act to discard remote monitoring commands programming a rate or bolus that deviates from the prescription.
  • FIG.2 illustrates a flow diagram of one exemplary method 200 in accordance with the invention for registering medical devices 10 with the system 100 of FIG. 1.
  • the method 200 begins at step 202, at which an authorized technician or other personnel having access to one of the remote monitoring devices 62, 70, 75 provides authenticating credentials (for example, a recognized log-in and password) to the outbound web server 43, and the web server responds by transmitting a device set-up screen to the remote monitoring device 62, 70, 75 requesting medical device identifying information and associated patient identifying information.
  • authenticating credentials for example, a recognized log-in and password
  • the outbound web server 43 preferably queries the metadata and application database 46 according to one or more of identifying information for the technician and/or identifying information for the patient to identify an associated patient care database node 60 from a plurality of patient care database nodes for the patient and record a destination address for the associated patient care database node 60 in the metadata and application database 46 in association with the identifying data for the medical device 10 and/or identifying information for the patient.
  • Identifying infonnation for the patient is preferably generated anonymously (for example as a random number), and transmitted at step 206 to the patient care database node 60 for association with securely-stored patient identifying information.
  • the outbound web server 43 requests that the secure device web server 42 assign an area of the device control database 44 for logging associated medical device data for the medical device 10 as it is received by the device integration server 41, such that it can be later retrieved by the outbound web server 43 upon receiving an authorized request from an authenticated user operating one of the remote monitoring devices 62, 70, 75.
  • step 204 of method 200 for identifying and storing the address of the patient care database node 60 may be omitted in accordance with the invention if a single patient care database node is utilized with system 100 of FIG. 1.
  • FIG. 3(a) presents a flow diagram illustrating one exemplary method 300 in accordance with the invention for retrieving and viewing medical device data on a remote monitoring device 62, 70, 75 for a registered medical device 10 according to the system of FIG. 1.
  • the method 300 begins at step 302 with a first authorized user having access to one of the first remote monitoring devices 62 provides authenticating credentials (for example, a recognized log-in and password) to the outbound web server 43.
  • authenticating credentials for example, a recognized log-in and password
  • a second authorized user having access to one of the second remote monitoring devices 70, 75 likewise provides respective authenticating credentials to the outbound web server 43
  • the outbound web server 43 queries the metadata and applications database 46 to identify the address of patient care database node(s) 60 to which the respective first and second authorized users are entitled to obtain access, and at step 306, requests data from the patient care database node 60 relating to at least one identified patient for which the first and second user are respectively authorized to view medical device data, including for example a listing of medical devices 10 which are presently associated with the identified patient, and/or status information of the facility- oriented network 17. .
  • the outbound web server 43 queries the device control database 44 via the secure device web server 42 for status information to determine which of the listed medical devices are presently active according to the data logged by the device control database 44.
  • one or more of a medical device 10, its associated interface device 15, an associated wireless relay module 30 and/or the device integration server 41 may be programmed to provide data from the medical device 10 to the device integration server 41 at predetermined, preset intervals or otherwise, which can then be provided to server 43 in response to inquiries therefrom.
  • FIG. 3(b) presents a first exemplary screen display 320 to the remote monitoring devices 62, 70, 75 that provides an array of medical devices 10 available for monitoring according to device type.
  • available device types include ventilators 321, urology devices 322, energy delivery devices 323, pulse oximeters 324, predictive thermometers 325, tympanic thermometers 326 and food pumps 327.
  • Each of the device types 321-327 in FIG. 3(b) is presented with an identifying label (for example, label 321 A) and an identifying image (for example, image 32 IB) for ease of recognition.
  • a second exemplary screen display 330 as illustrated by FIG. 3(c) may preferably be transmitted by the outbound web server 43 for display at the remote monitoring devices 62, 70 or 75.
  • labels 337A are provided in association with images 337B in order to identify individual food pumps (for example, by patient and/or by logical or physical location).
  • Medical devices 10 that are unavailable may for example preferably be depicted with a label 337A' ("Off Line") and an image 337B' (depicting the device with a slash or cross applied over the image or shaded or shadowed) that distinguish the unavailable medical devices 10 from available medical devices 10.
  • a third exemplary screen display 340 as illustrated by FIG. 3(d) may preferably transmitted by the outbound web server 43 for display at the corresponding remote monitoring device 62, 70, 75.
  • the display 340 for example, device information of the medical device 10 (in this case, a food pump) is displayed in a screen 347A preferably recreating a current screen generated and displayed by the medical device 10.
  • the screen display 340 includes any of a panel 347B providing identifying information for the medical device 10 (in this case, a pump location), a panel 347C for displaying a message indicating a current error condition of the pump, and an icon button 347D for selecting an alternate "status" mode of the screen display 340.
  • the screen display 340 also includes a control icon button 347E for selecting a system set-up screen display, and a control icon button 347F for enabling device control from the remote monitoring device 62.
  • the screen display 340 may preferably be refreshed to include the medical devices screen 347A and one or more operable buttons that mimic the appearance of control buttons on the medical device.
  • the control button features are described in greater detail below in relation to FIGs.4(b) and 4(c).
  • FIGs. 3(b), 3(c) and 3(d) are for illustration purposes only and that many other user screen images displays and interface tools may be utilized for carrying out the present invention including, for example, computer screens that depict accessible medical devices by other means than device type as illustrated in FIG. 3(b).
  • FIG. 3(b) For example, as a suitable alternative to the screen image 340 of FIG. 3(d) that conveys information from a single medical device, it is possible to implement displays that provide information from multiple medical devices.
  • the outbound web server 43 will preferably be operable to prepare display pages with encrypted medical device data for display on any of a wide variety of display devices (including, for example, workstations, personal computers, tablet devices including tablet computers, and display-based mobile devices including personal digital assistants, smartphones, portable game systems and the like.
  • display devices including, for example, workstations, personal computers, tablet devices including tablet computers, and display-based mobile devices including personal digital assistants, smartphones, portable game systems and the like.
  • the computer screen images to be available to first and second users of the first and second remote monitoring devices may be different depending upon whether such user is a clinician, nurse, patient relative or other caregiver, i.e., dependent on level of entitlement of the particular authorized user.
  • a display for a clinician at a first remote monitoring device 62 may enable the clinician to adjust the settings of a subject medical device 10, in contrast to a display for a second remote monitoring device 70, 75 used by a patient relative, which depicts only fundamental information from the medical device data with no option for the patient relative to adjust the medical device settings via the second remote monitoring device 70, 75.
  • different encryption methods or formats may be employed for medical device data transmitted to the first remote monitoring device 62 than the second remote monitoring device 70, 75.
  • FIG.4(a) presents a flow diagram illustrating an exemplary method 400 in accordance with the invention for issuing a command to a medical device 10 via the system 100 according to FIG. 1.
  • the method 400 begins at step 402 with an authorized user adjusts an operating parameter, such as a clinician (also referred to as a "authorized clinician” or “user” herein) logging into the outbound web server 43 using a first remote monitoring device 62 and navigating to the device screen display 340 of FIG.3(d) (for example, as described above with reference to FIGs.3(a)-3(d)).
  • a clinician also referred to as a "authorized clinician” or “user” herein
  • the clinician proceeds to select the "Enable Full Control" button 347F of FIG.
  • patient authentication information provided by the clinician is forwarded by the outbound web server 43 to a patient care database node 60 according to a patient care database node address stored by the metadata and applications database 46 in association with the clinician, and the clinician is authenticated for the patient by the outbound web server 43 upon receipt of an authentication confirmed message from the patient care database node 60.
  • a control request is forwarded by the outbound web server 43 at step 408 to the secure device web server 42 to be logged in the information record of the device control database 44 that is associated with the medical device 10 (and optionally, with an anonymous ID for the patient).
  • the secure device web server forwards the control request, such as an encrypted control request, to the device integration server 41, which transmits an associated device control command over the secure WW AN 52 for receipt by an associated wireless relay module 30 at step 412.
  • the wireless relay module 30 wirelessly communicates the command to the medical device 10 via an associated device interface IS, and awaits a reply confirming execution of the command transmitted by the device interface 15.
  • the device integration server 41 receives an update message from the wireless relay module 30 via the secure WW AN 52 which confirms that the command was executed by the medical device 10.
  • the device integration server 41 forwards the update message to the secure device web server 42 to be logged in the information record of the device control database 44 that is associated with the medical device 10.
  • the secure device web server 42 forwards information pertaining to the update message to the outbound web server 43, and the outbound web server 43 prepares an updated display screen that is securely transmitted to the remote monitoring device 62 to indicate that the command has been executed.
  • the authenticated clinician may select the
  • FIG. 4(b) illustrates a display screen 450 that is presented to the clinician upon selecting the control icon button 347E.
  • the display screen 450 includes a number of icon buttons that may be selected by the clinician (for example, as the result of a mouse-over or mouse-click initiated by the clinician) to select a specific setup command.
  • icon button 451 may be selected to initiate a command for providing identification information of the medical device 10.
  • Icon button 452 may be selected to provide text paging in response to an alert condition, as is further described herein.
  • Icon button 453 may be selected to initiate a software or firmware download for updating the medical device 10.
  • Icon button 454 may be selected to initiate a diagnostic test of the medical device 10.
  • FIG.4(c) illustrates an exemplary display screen 460 that may be displayed to the clinician upon selection of the icon button 454.
  • the clinician may select one or more of (including a progression of) a series of diagnostic tests 4 1 directed to components of the medical device (for example, including power components, memory components, alarm components and the like).
  • the clinician may select one or more of a series of performance statistics 462 to be gathered and displayed (for example, including various device error statistics such as feed error, rotor error and flush error rates for a food pump).
  • the clinician may select a version number test 463 to obtain version identifying information for the software and/or firmware (preferably including, for example, a software and/or firmware download history).
  • a version number test 463 to obtain version identifying information for the software and/or firmware (preferably including, for example, a software and/or firmware download history).
  • processes for performing the diagnostic tests 461, preparing the performance statistics 462 and identifying the software and/or firmware version number 463 may run automatically without specifically being selected by the clinician, with a complete reporting of all results on the display screen.
  • a bandwidth priority command or instruction to a relay module, such as relay module 30 of FIG. 1 , for the relay module to grant priority for relaying information received from a particular medical device relative to other medical devices that may send or receive communications via this relay module.
  • a critical care device such as a ventilator supporting the breathing function of a patient relative to a weight scale or thermometer.
  • bandwidth priority levels assignable to respective medical devices based upon, for example, the critical nature of the data or function provided by such devices.
  • icon button 455 may be selected to enable the clinician to specify data transfer rates, priorities and other parameters relating to the wireless transceiver of the interface device associated with the medical device.
  • Icon button 456 may be selected to provide the clinician with the an alarm history, event history and other information as has been logged for example for the medical device in the device control database 44 of FIG. 1.
  • the method 400 for remotely issuing a command to a medical device 10 was described with respect to a user of a first remote monitoring device 62 and not a user of the second remote monitoring 70, 75 because as described for example throughout this application, it is assumed that the user of the first remote monitoring device 62 is a clinician, technician or other highly-skilled healthcare professionals, while the user of the second remote monitoring device 70, 75 may be a patient relative or caregiver of lesser skill. Nevertheless, the method 400 is likewise useable to enable a user of the second monitoring device 70, 75 to also control particular settings of the medical device 10.
  • FIG. 5(a) presents a flow diagram illustrating one exemplary method 500 in accordance with the invention for recognizing and reporting an alert condition according to medical device data (including the status of the facility-oriented network 17) logged via the system 100 according to FIG. 1.
  • the method 500 begins at step 502 with the transmission of an alert message by a wireless relay module 30 over the secure WAN 52 to the device integration server 41.
  • the wireless relay module 30 is configured to analyze (such as by detecting flag or status information or comparing message data to information stored in an associated database) a message type of a message transmitted by an associated medical device 10 to determine that the message is an alert message, and to transmit the message to the device integration server 41 upon determining that the message is an alert message (for example, as a priority message).
  • the wireless relay module 30 may simply queue all messages for transmission to the device integration server 41 in order upon receipt, and rely upon the device integration server 41 to analyze an associated message type to determine that a message is an alert message.
  • the device integration server 41 Upon determining that the transmitted message is an alert message, the device integration server 41 proceed, at step 503, to log the message in the device control database 44, and at step 504, invokes a text messaging application that retrieves text messaging numbers associated with identifying information of the medical device 10 and/or anonymous patient identifying information.
  • the determination of whether the transmitted message is an alert message may be carried out by, for example, detecting an alert flag or trigger identifier in the message or scanning the message for other information indicative of an alert condition.
  • the text messaging application may preferably retrieve the text messaging numbers by querying the metadata and applications database 46 to identify the address of an associated patient care database node 60, and either making a direct request or instructing the outbound web server 43 to request the text messaging numbers from the associated patient care database node 60.
  • the device integration server 41 sends one or more messages including the retrieved text messaging numbers and text message information according to the alert message to one or more wireless relay modules 30 over the secure WWAN 52.
  • the one or more wireless relay modules 30 transmit the text message information addressed to the text messaging numbers over one or more of the secure WW AN 52 and/or the facility-oriented wireless network 17 to complete the method 500.
  • FIG. 5(b) illustrates a "Text Paging" 452 screen display 550 that may be invoked, for example, by using the method 400 of FIG.4(a) for issuing a command to a medical device 10.
  • the text paging screen 550 is displayed at the first remote monitoring device 62 of an authenticated clinician upon the clinician's selection of the "System Setup" icon button 347e of the screen display 340, and thereafter upon the clinician's selection go the "Text Paging" icon button of the screen display 450.
  • the 'Text Paging" screen display 550 include a listing of one or more names 551 of individuals responsible for responding to alert messages of at least two types: "Error Messages" 553, which may for example indicate a malfunction of the medical device 10, and/or "Info Messages" 554, which may for example indicate a significant patient health condition (for example, a patient respiration rate below a preset minimum rate specified for a ventilator device 321 of FIG. 3(b)).
  • the information retrieved by the outbound web server 43 to prepare this display is preferable retrieved from the patient care database node 60, by providing on one or more of identifying information for the medical device 10 and/or anonymous patient identifying information stored in the device control database 44.
  • the information provided on the 'Text Paging" screen display may be retrieved by the device integration server 41 by querying the metadata and applications server 46 to retrieve address information for the patient care database node 60, and forwarding a text paging information request to the patient care database node 60 based upon one or more of identifying information for the medical device 10 and/or anonymous patient identifying information stored in the device control database 44.
  • the recognition of whether the received message from the medical device 10 is an alert message may be carried out by, for example, detecting an alert flag or trigger identifier in the message or scanning the message for other information indicative of an alert condition.
  • alerts may be communicated in other ways in accordance with the present invention including email, audio messages via telephone calls, as well as any other wired and/or wireless text, audio, or multimedia based communication services receivable by, for example, by a smart phone or computer tablet software application or "App.”
  • FIG. 6 shows an illustrative computer system 600 suitable for
  • the computer system 600 as described herein may comprise, for example, a personal computer running the WINDOWS operating system, or a server computer running, WINDOWS Server, LINUX or another UNIX-based operating system.
  • the computer system 600 described herein may comprise a mobile device, tablet devices or computers, or information appliance running, for example, an operating system in the group including Symbian , Android, Apple iOS, Blackberry, Microsoft Windows Phone, Linux, Palm/HP WebOS, BADA, MAEMO and MEEGO.
  • the above-described methods carried out by the server and computer components of the present invention may be implemented on the computer system 600 as stored program control instructions directed to control application software.
  • Computer system 600 includes processor 610, memory 620, storage device
  • One of the input/output devices 640 may preferably include a display 645.
  • Some or all of the components 610, 620, 630 and 640 may be interconnected by a system bus 650.
  • Processor 610 may be single or multi-threaded, and may have one or more cores.
  • Processor 610 executes instructions which in the disclosed embodiments of the present invention are the steps described, for example, in one or more of FIGs.2, 3(a), 4(a) or 5(a). These instructions may be stored in one or more of memory 620 or in storage device 630. Information may be received and output using one or input/output devices 640.
  • Memory 620 may store information and may comprise a computer-readable medium, such as volatile or non-volatile memory.
  • Storage device 630 may provide storage for system 600 including for the example, the previously described database, and may be a computer-readable medium.
  • storage device 630 may be one or more of a flash memory device, a floppy disk drive, a hard disk device, and optical disk device, and/or a tape device.
  • Input devices 640 may provide input/output operations for system 600.
  • Input/output devices 640 may include one or more of a keyboard, a pointing device, and/or microphone.
  • Input/output devices 640 may further include a display unit for displaying graphical user interfaces, a speaker and a printer and any of a number of other serial devices (for example, configured as Universal Serial Bus (USB)-based devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Biomedical Technology (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Medical Informatics (AREA)
  • Epidemiology (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Educational Administration (AREA)
  • Development Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Child & Adolescent Psychology (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)
  • Telephonic Communication Services (AREA)
  • Alarm Systems (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

L'invention concerne un système de surveillance à distance pour surveiller une pluralité de dispositifs médicaux dans un système de soins pour malades ou un système de soins à domicile. Le système comprend un serveur d'intégration de dispositifs en communication avec des modules à relais sans fil destinés à recevoir des paquets de données en provenance des dispositifs médicaux, notamment un identifiant et des données relatives à chaque dispositif médical. Le système comprend également un serveur Web de sortie. Le serveur Web est conçu pour fournir des pages Web comprenant les données relatives aux dispositifs médicaux pour affichage sur un premier et un second dispositif de surveillance à distance, sous réserve d'une authentification en réponse à une demande de données associées à la demande de données provenant du dispositif de surveillance.
EP13738062.2A 2012-01-18 2013-01-15 Systèmes et procédés de surveillance à distance pour dispositifs médicaux Withdrawn EP2805299A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/352,608 US9495511B2 (en) 2011-03-01 2012-01-18 Remote monitoring systems and methods for medical devices
PCT/US2013/021530 WO2013109517A1 (fr) 2012-01-18 2013-01-15 Systèmes et procédés de surveillance à distance pour dispositifs médicaux

Publications (2)

Publication Number Publication Date
EP2805299A1 true EP2805299A1 (fr) 2014-11-26
EP2805299A4 EP2805299A4 (fr) 2015-09-09

Family

ID=48799601

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13738062.2A Withdrawn EP2805299A4 (fr) 2012-01-18 2013-01-15 Systèmes et procédés de surveillance à distance pour dispositifs médicaux

Country Status (13)

Country Link
EP (1) EP2805299A4 (fr)
JP (1) JP2015512175A (fr)
KR (1) KR20140105011A (fr)
CN (1) CN104067306A (fr)
AU (1) AU2013205106A1 (fr)
BR (1) BR112014017564A8 (fr)
CA (1) CA2861619A1 (fr)
IL (1) IL233633A0 (fr)
MX (1) MX2014008678A (fr)
RU (1) RU2014129938A (fr)
SG (1) SG11201404133RA (fr)
WO (1) WO2013109517A1 (fr)
ZA (1) ZA201405228B (fr)

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2441409A1 (fr) 2010-10-12 2012-04-18 Smith&Nephew, Inc. Dispositif médical
EP2968706B1 (fr) 2013-03-14 2022-12-07 Smith & Nephew, Inc. Systèmes et procédés pour appliquer une thérapie par pression réduite
US9737649B2 (en) 2013-03-14 2017-08-22 Smith & Nephew, Inc. Systems and methods for applying reduced pressure therapy
US10155070B2 (en) 2013-08-13 2018-12-18 Smith & Nephew, Inc. Systems and methods for applying reduced pressure therapy
JP2015188486A (ja) * 2014-03-27 2015-11-02 テルモ株式会社 医療用ポンプ管理システム
US10447573B2 (en) * 2014-07-17 2019-10-15 Sysmex Corporation Method and system for aggregating diagnostic analyzer related information
CN104434045A (zh) * 2014-11-10 2015-03-25 深圳市华士精成科技有限公司 一种区域性群体人员健康监控系统
GB2535744A (en) * 2015-02-25 2016-08-31 Elekta ltd Computer system integration
JP6942698B2 (ja) 2015-10-07 2021-09-29 スミス アンド ネフュー インコーポレイテッド 減圧療法を施すためのシステムおよび方法
EP3398099A1 (fr) * 2015-12-31 2018-11-07 Koninklijke Philips N.V. Actionnement sécurisé par connexion en chaîne
JP2019514591A (ja) 2016-05-13 2019-06-06 スミス アンド ネフュー インコーポレイテッド 陰圧創傷療法システムにおける自動化創傷結合検出
SE541780C2 (en) * 2016-07-07 2019-12-17 Brighter Ab Publ Method involving a mobile phone for monitoring a medical device
WO2018013666A1 (fr) * 2016-07-12 2018-01-18 Stryker Corporation Système de gestion d'équipements
WO2018064077A2 (fr) 2016-09-29 2018-04-05 Smith & Nephew, Inc. Construction et protection de composants dans des systèmes de thérapie de plaies par pression négative
EP3592313B1 (fr) 2017-03-07 2021-07-07 Smith & Nephew, Inc Systèmes et procédés de thérapie par pression réduite comprenant une antenne
DE102018001986A1 (de) * 2017-03-22 2018-09-27 Löwenstein Medical Technology S.A. Verfahren und Vorrichtung zur Übermittlung von Daten von Beatmungsgeräten
US10765379B2 (en) * 2017-05-01 2020-09-08 Cardiac Pacemakers, Inc. Systems and methods for medical alert management
EP4164176A1 (fr) * 2017-05-18 2023-04-12 F. Hoffmann-La Roche AG Procédés et systèmes de traitement de données d'un instrument d'analyse pour analyser des échantillons biologiques
WO2019010127A1 (fr) 2017-07-03 2019-01-10 Stryker Corporation Système de communication de données
US11712508B2 (en) 2017-07-10 2023-08-01 Smith & Nephew, Inc. Systems and methods for directly interacting with communications module of wound therapy apparatus
CN109663173A (zh) * 2017-10-16 2019-04-23 费森尤斯卡比健源（长沙）医疗科技有限公司 输液监护系统及其中继设备和数据处理装置
US11179208B2 (en) * 2017-12-28 2021-11-23 Cilag Gmbh International Cloud-based medical analytics for security and authentication trends and reactive measures
JP2020005751A (ja) * 2018-07-04 2020-01-16 オリンパス株式会社 内視鏡システム
GB201820668D0 (en) 2018-12-19 2019-01-30 Smith & Nephew Inc Systems and methods for delivering prescribed wound therapy
CN114036223A (zh) * 2020-11-13 2022-02-11 武汉联影医疗科技有限公司 医疗信息管理方法、系统、装置、计算机设备和存储介质

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2301606C (fr) * 1997-09-12 2005-11-01 Boston Scientific Limited Procede et systeme pour l'acquisition, le traitement et le partage synchronises de donnees fournies par des instruments, et pour la commande synchronisee dans un reseau client-serveur
JP4742182B2 (ja) * 2001-02-23 2011-08-10 アークレイ株式会社 データ送受信装置、データ管理装置、データ処理装置、およびプログラム
AU2002254463A1 (en) * 2001-03-28 2002-10-15 Televital, Inc. Real-time monitoring assessment, analysis, retrieval, and storage of physiological data
US20050055242A1 (en) * 2002-04-30 2005-03-10 Bryan Bello System and method for medical data tracking, analysis and reporting for healthcare system
US20050010451A1 (en) * 2003-05-08 2005-01-13 University Of Florida Method, system, and apparatus for clinical trial management over a communications network
JPWO2005122033A1 (ja) * 2004-06-08 2008-07-31 有喜 北岡 医療総合情報装置及び医療総合情報システム
JP2006167400A (ja) * 2004-12-16 2006-06-29 Ipsquare Inc 医療機器管理システム
JP2009199508A (ja) * 2008-02-25 2009-09-03 Ricoh Elemex Corp 無線通報システム
KR101002020B1 (ko) * 2008-03-27 2010-12-16 계명대학교 산학협력단 실시간 심전도 모니터링 시스템 및 방법, 패치형 심전도측정장치, 통신장치
KR20100028318A (ko) * 2008-09-04 2010-03-12 주식회사 케이티테크 듀얼 모드 통신 단말기 및 방법
US9656092B2 (en) * 2009-05-12 2017-05-23 Chronicmobile, Inc. Methods and systems for managing, controlling and monitoring medical devices via one or more software applications functioning in a secure environment
US8190651B2 (en) * 2009-06-15 2012-05-29 Nxstage Medical, Inc. System and method for identifying and pairing devices

Also Published As

Publication number Publication date
SG11201404133RA (en) 2014-08-28
WO2013109517A1 (fr) 2013-07-25
MX2014008678A (es) 2014-10-24
IL233633A0 (en) 2014-08-31
RU2014129938A (ru) 2016-03-20
EP2805299A4 (fr) 2015-09-09
ZA201405228B (en) 2017-05-31
CA2861619A1 (fr) 2013-07-25
AU2013205106A1 (en) 2013-08-01
BR112014017564A2 (pt) 2017-06-13
BR112014017564A8 (pt) 2017-07-04
KR20140105011A (ko) 2014-08-29
CN104067306A (zh) 2014-09-24
JP2015512175A (ja) 2015-04-23

Similar Documents

Publication Publication Date Title
US9495511B2 (en) Remote monitoring systems and methods for medical devices
EP2779008B1 (fr) Systèmes de surveillance à distance permettant de surveiller des dispositifs médicaux via des réseaux de communication sans fil
WO2013109517A1 (fr) Systèmes et procédés de surveillance à distance pour dispositifs médicaux
US20200206517A1 (en) Systems and methods for ems device communications interface
US9872087B2 (en) Platform for patient monitoring
US9801543B2 (en) Hand-held medical-data capture-device having detection of body core temperature by a microprocessor from a signal from a digital infrared sensor on a separate circuit board with no A/D converter and having interoperation with electronic medical record static IP address system
US20150070187A1 (en) Wireless Relay Module For Remote Monitoring Systems
US9965946B2 (en) Systems and methods for monitoring a patient health network
US20070180140A1 (en) Physiological alarm notification system
US20110295078A1 (en) Systems and methods for collection, organization and display of ems information
KR20150067289A (ko) 환자관리시스템과 방법
JP6416112B2 (ja) モニタ除細動器遠隔治療サーバ
US20170053086A1 (en) Systems and methods for ems device communications interface
US20220020491A1 (en) Systems and methods for ems device communications interface

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140711

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20150807

RIC1 Information provided on ipc code assigned before grant

Ipc: G06Q 10/06 20120101ALI20150803BHEP

Ipc: G06F 19/00 20110101ALI20150803BHEP

Ipc: G06Q 50/22 20120101AFI20150803BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170113

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20170524