Medical device systems and hardware for sensor data acquisition

Abstract

A medical device system for providing sensor data capture includes a medical device, which may include one or more removably coupled sensor hubs, and includes a display for providing sensor data and at least one data DI port, which may be a sensor-unknown data interface port, i.e., an SA‑DI port, and a data transmission cable that may be compatible with the sensor-unknown DI port, and includes a first electromechanical connector configured to be removably coupled to the SA‑DI port and a second electromechanical connector configured to be coupled to the sensor, and includes a cable memory and a processor configured to execute stored software to format the sensor data according to a protocol of the SA‑DI port, an authentication circuit, and a cable isolation device, which limits patient leakage current from the medical device to the sensor and electrically isolates the authentication circuit from the cable processor and the cable memory.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Application Serial No. 63 / 001,565, filed on March 30, 2020, entitled “MEDICAL DEVICE SYSTEM AND HARDWARE FOR SENSOR DATA ACQUISITION,” the entire contents of which are incorporated herein by reference. Background Art

[0003] Medical devices such as patient monitors and defibrillators obtain physiological data and medical treatment data via sensors. For example, physiological data may include patient data such as vital signs, electrocardiogram (ECG), pulse oximetry data, and / or capnography data. Medical treatment data may include treatment administration metrics such as cardiopulmonary resuscitation (CPR) parameters. A sensor configured to provide the data may be coupled to the medical device via a cable connection to a data interface port. The data interface port captures the sensor data and provides the captured data to the medical device for analysis and display. Summary of the invention

[0004] An example of a data transmission cable for providing data communication between a sensor for collecting medical data and a sensor-unknown data interface port on a medical device, i.e., a sensor-unknown DI port, according to the present invention includes: a cable comprising a conductive wire arranged in a continuous insulating sheath; a first electromechanical connector, which is fixedly fastened to a first end of the cable and comprises: a housing, a first electrical fitting, which is arranged in the housing at an open end of the housing and is configured to be removably coupled to the sensor, a data interface circuit, which is arranged in the housing and electrically coupled to the first electrical fitting and the conductive wire of the cable, and comprises: a cable memory, a cable processor, and an isolation device for limiting the flow of patient leakage current from the medical device to the sensor, the isolation device being configured to: transmit power unidirectionally toward the cable processor across an isolation barrier, and transmit communication signals bidirectionally across the isolation barrier; and a second electromechanical connector, which is fixedly fastened to a second end of the cable, the second electromechanical connector comprising a cable contact, the cable contact being electrically coupled to the conductive wire of the cable, and being configured to removably electromechanically couple the data transmission cable to the sensor-unknown DI port.

[0005] Implementations of such a system may include one or more of the following features. The isolation device may be configured to transmit an amount of power specific to the sensor across the isolation barrier. The isolation device may be configured to transmit 0.1 to 1 watt. The isolation device may include one of a dual capacitive isolation barrier device, a digital isolator device, and an optical isolator. The cable contacts may include at least: (a) at least two communication cable contacts, (b) at least one power cable contact, and (c) at least one ground cable contact. Each of the cable contacts may be electrically coupled to at least one of the conductive wires. The cable contacts may include at least one connection detection cable contact, the at least one connection detection cable contact being used to electrically detect a connection between the data transmission cable and the unknown DI port of the sensor. The data interface circuit may include an authentication circuit, and the cable contacts may include at least one authentication cable contact. The authentication circuit may be configured to: in the absence of power transmission from the unknown DI port of the sensor to the data transmission cable, (a) receive an AU / ID request via the at least one authentication cable contact, and (b) send AU / ID information in response to the received AU / ID request. The authentication circuit may be configured to include encrypted AU / ID information for the sensor in the AU / ID information. The encrypted AU / ID information may include identification information of a manufacturer of the sensor. The cable processor may be configured to receive a request for sensor information from the sensor unknown DI port via a communication signal transmitted by the isolation device, the sensor information including unencrypted AU / ID information stored in the cable memory, execute software stored in the cable memory to determine the requested sensor information, and send the sensor information to the sensor unknown DI port via the communication signal transmitted by the isolation device. The cable processor may be configured to receive a request for a sensor data stream from the sensor unknown DI port via a communication signal transmitted by the isolation device, execute software stored in the cable memory to format the sensor data into a sensor unknown data format according to a protocol of the sensor unknown DI port, and send the sensor data stream in the sensor unknown data format to the sensor unknown DI port via the communication signal transmitted by the isolation device. The data interface circuit may include an analog-to-digital converter. The data transmission cable may include a noise shield between the isolation device and the cable processor. The data transmission cable may include at least one lighting device disposed on the cable and configured to illuminate in a color based on the type of the sensor. The at least one lighting device may include a light emitting diode (LED). The at least one lighting device may include a band around the circumference of the data transmission cable.The data transmission cable may include a microphone that is communicatively coupled to the cable processor and is configured to capture voice input. The cable processor may be configured to cause the at least one lighting device to illuminate in response to the voice input. The cable processor may be configured to recognize a query from the voice input recognition sensor. The at least one lighting device may provide infrared illumination. The data transmission cable may include a low light sensor that is electrically coupled to the at least one lighting device and is configured to disable illumination in low light conditions. The data transmission cable may include a user interface display that is configured to provide caregiver feedback and is arranged on a display housing positioned along the cable. The caregiver feedback may include one or more of CPR chest compression feedback and bag-mask feedback. The sensor may be one of an invasive blood pressure sensor, a non-invasive blood pressure sensor, a temperature sensor, a pulse oximetry sensor, a capnography sensor, and an airway flow sensor. The sensor may be an ECG sensor.

[0006] An example of a patient monitoring and treatment system for providing sensor data capture capabilities according to the present invention includes: a medical device, which includes: a display, at least one sensor-unknown data interface port, i.e., at least one sensor-unknown DI port, which includes a plurality of electrical contacts, the plurality of electrical contacts being configured to enable power delivery to the sensor and data communication between the sensor and the medical device, a host processor, a memory and associated circuits; and a data transmission cable, which includes: a first electromechanical connector, which is configured to removably couple the data transmission cable to the at least one sensor-unknown DI port, and a second electromechanical connector, which is configured to removably couple to the sensor and includes: a plurality of cable contacts, each cable contact a point configured to detachably mate with a corresponding contact of the plurality of electrical contacts, a cable memory, a cable processor configured to execute software stored in the cable memory to format sensor data into a data format unknown to the sensor according to a protocol of a DI port unknown to the at least one sensor, an authentication circuit configured to provide encrypted authentication / identification information for the sensor, i.e., encrypted AU / ID information, to the medical device, and a cable isolation device for limiting patient leakage current from the medical device to the sensor, the cable isolation device being configured to electrically isolate the authentication circuit from the cable processor and the cable memory, and the display being configured to provide at least one visual representation of the sensor data.

[0007] Implementations of such a system may include one or more of the following features. The at least one sensor unknown DI port excludes an isolation device for limiting the flow of patient leakage current from the medical device to the sensor. The plurality of electrical contacts may include at least: (a) at least one authentication contact, (b) at least two communication contacts, (c) at least one power contact, and (d) at least one ground cable contact. The host processor may be configured to send an AU / ID request via the at least one authentication contact. The authentication circuit may be configured to send encrypted AU / ID information in response to the received AU / ID request in the absence of power transmission from the at least one sensor unknown DI port to the data transmission cable. The plurality of electrical contacts may include at least one connection detection contact, the at least one connection detection contact being used to electrically detect connection and disconnection between the data transmission cable and the at least one sensor unknown DI port. The medical device may include a plurality of sensor unknown DI ports. The host processor may be configured to limit the number of sensor unknown data interface ports that transmit power simultaneously to less than the total number of sensor unknown data interface ports. The host processor may be configured to limit the number of sensor unknown DI ports based on the encrypted AU / ID information. The host processor may be configured to limit the number of sensor unknown DI ports to three ports connected to the invasive blood pressure sensor. The host processor may be configured to limit the number of sensor unknown DI ports based on sensor priority. The airway flow sensor and / or the invasive blood pressure sensor may have a higher priority than the temperature sensor. In response to the electrical detection of the disconnection, the host processor may be configured to disable the power supply from the at least one sensor unknown DI port to the data transmission cable. The encrypted AU / ID information may include identification information of the manufacturer of the sensor. The host processor may be configured to: authenticate the sensor based on the encrypted AU / ID information, enable power supply to the data transmission cable via the at least one power contact based on the authentication, send a request for a sensor data stream from the at least one sensor unknown DI port via the at least two communication contacts, and receive a sensor data stream in a sensor unknown data format according to the protocol of the at least one sensor unknown DI port.The cable processor may be configured to receive power from the medical device via the at least one sensor unknown DI port, receive a request for the sensor data stream via a communication signal transmitted by the cable isolation device, and execute software stored in the cable memory to format the sensor data into the sensor unknown data format according to a protocol of the at least one sensor unknown DI port, and send the sensor data stream in the sensor unknown data format to the host processor via the communication signal transmitted by the cable isolation device. The host processor may be configured to send a request for sensor identification information from the at least one sensor unknown DI port via the at least two communication contacts, receive unencrypted sensor identification information in response to the request, compare the encrypted AU / ID information with the unencrypted sensor identification information, and request and receive the sensor data stream if the encrypted AU / ID information corresponds to the unencrypted sensor identification information, otherwise disable power to the data transmission cable. The data transmission cable may include at least one lighting device, the at least one lighting device configured to illuminate in a color based on the type of the sensor. The host processor may be configured to cause the at least one lighting device to illuminate in response to a user input. The display may be a touch screen display, and the host processor may be configured to cause the at least one illumination device to illuminate in response to a user touch at the at least one visual representation of the sensor data.The medical device may include a patient monitor / defibrillator.

[0008] An example of a patient monitoring and treatment system for providing defibrillation and capturing data from sensors to collect medical data according to the present invention includes: a monitor / defibrillator, which includes: a first housing, which includes at least one sensor hub connector, a first display, which is coupled to the first housing, a first communication interface, and a first processor, memory and associated circuitry, which are communicatively coupled to the first communication interface and the first display; and at least one sensor hub, which includes: a second housing, which includes at least one mating mechanism, the at least one mating mechanism being configured to removably couple the at least one sensor hub to the at least one sensor hub connector, at least one data a data interface port, i.e., at least one DI port, coupled to the second housing and comprising a plurality of electrical contacts, the plurality of electrical contacts being configured to allow data communication between at least one sensor and the at least one sensor hub, a second communication interface, configured to be communicatively coupled to the first communication interface, and a second processor, memory, and associated circuitry, communicatively coupled to the second communication interface and configured to: receive sensor data via the at least one DI port, and send the sensor data to the monitor / defibrillator via the first communication interface and the second communication interface, and the first display being configured to provide a first visual representation of the sensor data.

[0009] Implementations of such a system may include one or more of the following features. The at least one sensor hub connector may include a receptacle disposed on an inner surface of the first housing to removably couple the at least one sensor hub to the monitor / defibrillator within the first housing. The at least one DI port may be accessible from an outer surface of the first housing when the at least one sensor hub is coupled to the first housing. The first communication interface and the second communication interface may be configured to communicate with each other via wired and / or wireless communication coupling. The first communication interface and the second communication interface may be configured to communicate with each other via wired communication coupling when the at least one sensor hub is coupled to the at least one sensor hub connector, and to communicate with each other via the wireless communication coupling when the at least one sensor hub is decoupled from the at least one sensor hub connector. The first communication interface and the second communication interface may be configured to communicate with each other via wired coupling when the at least one sensor hub is coupled to the at least one sensor hub connector and when the at least one sensor hub is decoupled from the at least one sensor hub connector. The second processor may be configured to process one or more predetermined and specific types of sensor data. The second processor may be configured to process pulse oximetry data and capnography data. The at least one sensor hub may include a pneumatic pump system for sidestream capnography. The second processor may be configured to process non-invasive blood pressure data. The at least one sensor hub may include a pneumatic pump system for non-invasive blood pressure. The at least one DI port may be a sensor-unknown DI port, the sensor-unknown DI port including a plurality of electrical contacts configured to allow power transmission to the sensor via a data transmission cable coupled to the sensor-unknown DI port and the sensor and data communication between the sensor and the monitor / defibrillator. The plurality of electrical contacts may include at least: (a) at least two communication contacts, (b) at least one power contact, and (c) at least one ground cable contact. The plurality of electrical contacts may include at least one connection detection contact, the at least one connection detection contact being used to electrically detect connection and disconnection between the data transmission cable and the sensor-unknown DI port. The plurality of electrical contacts may include at least one authentication contact.The second processor may be configured to send an AU / ID request for the sensor via the at least one authentication contact, receive encrypted AU / ID information in response to the AU / ID request in the absence of power transmission from the DI port unknown to the sensor to the data transmission cable, authenticate the sensor based on the encrypted AU / ID information, and provide power to the data transmission cable via the at least one power contact based on the authentication. The encrypted AU / ID information may include identification information of the manufacturer of the sensor. The second processor may be configured to provide power to the data transmission cable via the at least one power contact, send a request for a sensor data stream from the DI port unknown to the sensor via the at least two communication contacts, and receive a sensor data stream in a sensor unknown data format according to a protocol of the DI port unknown to the sensor. The second processor may be configured to: send a request for sensor information from the sensor unknown DI port via the at least two communication contacts, receive sensor information including unencrypted AU / ID information in response to the request, compare the encrypted AU / ID information with the unencrypted AU / ID information, and if the encrypted AU / ID information corresponds to the unencrypted AU / ID information, request and receive the sensor data stream, otherwise interrupt the power supply to the data transmission cable. The sensor unknown DI port excludes an isolation device for limiting patient leakage current from the monitor / defibrillator to the sensor. The at least one sensor hub may include a second display and a plurality of DI ports, the second display being configured to provide a second visual representation of the sensor data. The at least one sensor hub connector may be arranged on an outer surface of the first housing. The at least one sensor hub connector may include a bracket, and the at least one mating mechanism may include a profile on the at least one sensor hub, the mating mechanism being configured to removably couple the at least one sensor hub to the bracket. The at least one sensor hub connector may include one or more first electrical contacts, and the at least one mating mechanism may include one or more second electrical contacts. The monitor / defibrillator and the at least one sensor hub may be configured to be electrically and / or communicatively coupled via the one or more first electrical contacts and the one or more second electrical contacts with the at least one sensor hub physically held by the at least one sensor hub connector. The first housing may include one or more first electrical contacts, and the second housing may include one or more second electrical contacts.The at least one sensor hub connector and the at least one mating mechanism may be configured to couple the monitor / defibrillator and the at least one sensor hub such that the one or more first electrical contacts and the one or more second electrical contacts provide electrical connectivity and / or communication connectivity while the at least one sensor hub is physically retained in the at least one sensor hub connector. The at least one sensor hub may be configured to be electrically coupled to the monitor / defibrillator via a wired connection and communicatively coupled to the monitor / defibrillator via a wireless connection while the at least one sensor hub is physically retained in the at least one sensor hub connector. The at least one sensor hub may be configured to be communicatively coupled to the monitor / defibrillator via a wired cable or wireless coupling while the at least one sensor hub is physically separated from the at least one sensor hub connector. The at least one sensor hub may be configured to be communicatively coupled to the monitor / defibrillator and / or one or more remote computing devices. The at least one sensor hub may include at least one USB port. The at least one DI port may include a sensor-specific DI port. The at least one DI port may correspond to an ECG sensor. The at least one DI port may correspond to a pulse oximetry sensor. The at least one DI port may correspond to a capnography sensor. The at least one sensor hub may include a plurality of sensor-specific DI ports. The plurality of sensor-specific DI ports may correspond to one or more of a heart rate sensor, an invasive blood pressure sensor, a non-invasive blood pressure sensor, and a temperature sensor. The at least one DI port may correspond to a cardiopulmonary resuscitation compression sensor, i.e., a CPR compression sensor. The at least one DI port may correspond to an airway flow sensor. The at least one sensor hub may include a user interface. The user interface may include a second display configured to provide a second visual representation of the sensor data. The second display may be configured to provide a second visual representation of one or more of a pulse oximetry waveform, a capnography waveform, and an ECG waveform. The second display may be configured to provide a second visual representation of one or more of a physiological parameter corresponding to one or more discrete values. The one or more physiological parameters corresponding to the one or more discrete values ​​may include one or more of blood pressure, heart rate, instantaneous pulse oximetry, and instantaneous capnography. The second display may be configured to provide one or more of chest compression data and airway flow sensor data as one or more of a waveform, a discrete value, and a graphical indicator. The chest compression data may include one or more of a compression depth, a compression rate, a compression release indicator, a perfusion indicator, and a CPR timer.The user interface may include one or more of an alarm control and a power button. The user interface may include a data input control. The user interface may be configured to capture one or more of an audio input and a tactile input. The user interface may be configured to provide one or more of an audio output, a visual output, and a tactile output. The system may include a wired and / or wireless coupling port configured to couple the at least one sensor hub to a user input device. The user input device may include one of a mouse, a microphone, and a wireless remote control. The user input device may include a wearable computing device. The wearable computing device may include one or more of a headset, a watch, and glasses. The first communication interface and the second communication interface may be configured to be communicatively coupled to each other via a wired and / or wireless coupling. The monitor / defibrillator may be configured to receive sensor data for a patient from the at least one sensor hub and associate the received sensor data with sensor data received by the monitor / defibrillator for the patient. The at least one sensor hub may be configured to receive sensor data for a patient from the monitor / defibrillator and associate the received sensor data with sensor data received for the patient by the at least one sensor hub. The second communication interface may be configured to be communicatively coupled to a remote server via the first communication interface. The second communication interface may be configured to be communicatively coupled to a mobile computing device via the first communication interface, the mobile computing device including one or more of a smart phone and a computer tablet. The second communication interface may be configured to be communicatively coupled to one or more of a remote server, a mobile computing device, and a wearable computing device in the absence of an existing communicatively coupling to the first communication interface. The second communication interface may be configured to send one or more of a case file, sensor data, device readiness data, and device status data to a communicatively coupled device. The second communication interface may be configured to receive one or more of sensor data, software updates, settings updates, and protocol updates from a communicatively coupled device. The second communication interface can be configured to be communicatively coupled to one or more computing devices via one or more of a long-range wired and / or wireless connection and a short-range wired and / or wireless connection. The one or more computing devices can include one or more of a mobile computing device, a wearable computing device, a tablet computer, a smart phone, a watch, a head-up display, a laptop computer, or a combination thereof. The short-range wireless connection can include. and near field communication device connection. The long-range wired and / or wireless connection may include one or more of a cellular communication network and a computer network. The second communication interface may be configured to be communicatively coupled to one or more medical devices via one or more of a long-range wired and / or wireless connection and a short-range wired and / or wireless connection. The one or more medical devices may include one or more of a compression monitor, an airway flow sensor, a bag-mask, and a first aid kit. The monitor / defibrillator may be a first monitor / defibrillator, and the one or more medical devices may include a second monitor / defibrillator. The first communication interface and the second communication interface may be configured to be communicatively coupled in response to authentication of the at least one sensor hub. The at least one sensor hub may be configured to be communicatively coupled to only one monitor / defibrillator during treatment of a patient. The authentication may include information exchange for verifying that the monitor / defibrillator and the at least one sensor hub are associated with the same patient. The system may include at least two DI ports configured to allow communication between at least two sensors and the at least one sensor hub. The at least two DI ports may include a SS-DI port, a SA-DI port, or a combination thereof. The at least one sensor hub may include a respiratory distress hub.

[0010] An example of a patient monitoring and treatment system for providing defibrillation and capturing data from sensors to collect medical data includes: a monitor / defibrillator, comprising: a first housing, comprising at least one sensor hub connector, a first display, coupled to the first housing, a first communication interface, and a first processor, memory, and associated circuitry, communicatively coupled to the first communication interface and the first display; and at least one sensor hub, comprising a respiratory distress hub (RD hub), the RD hub comprising: a second housing, comprising at least one mating mechanism, the at least one mating mechanism being configured to removably couple the at least one RD hub to the at least one sensor hub connector. a first display configured to provide a first visual representation of the sensor data; a second communication interface configured to be communicatively coupled to the first communication interface; and a second processor, memory and associated circuitry communicatively coupled to the second communication interface and configured to receive sensor data via the at least one DI port and to send the sensor data to the monitor / defibrillator via the first communication interface and the second communication interface.

[0011] Implementations of such a system may include one or more of the following features. The at least one sensor hub connector may include a receptacle disposed on an inner surface of the first housing to removably couple the at least one RD hub to the monitor / defibrillator within the first housing. The at least one DI port may be accessible from an outer surface of the first housing when the at least one RD hub is coupled to the first housing. The first communication interface and the second communication interface may be configured to communicate with each other via wired and / or wireless communication coupling. The first communication interface and the second communication interface may be configured to communicate with each other via wired communication coupling when the at least one RD hub is coupled to the at least one RD hub connector, and to communicate with each other via wireless communication coupling when the at least one RD hub is decoupled from the at least one RD hub connector. The first communication interface and the second communication interface may be configured to communicate with each other via wired coupling when the at least one RD hub is coupled to the at least one sensor hub connector and when the at least one RD hub is decoupled from the at least one sensor hub connector. The second processor may be configured to process one or more predetermined and specific types of sensor data. The second processor may be configured to process one or more of pulse oximetry data, capnography data, pneumotachometer data, flow rate data, tidal volume data, minute ventilation data, respiratory mechanics data, spirometry data, FVC data, FEV1 data, and PEF data. The at least one RD hub may include a mechanical ventilator. The at least one DI port may be a sensor unknown DI port, the sensor unknown DI port including a plurality of electrical contacts configured to allow power transfer to the sensor via a data transfer cable coupled to the sensor unknown DI port and the sensor and data communication between the sensor and the monitor / defibrillator. The plurality of electrical contacts may include at least: (a) at least two communication contacts, (b) at least one power contact, and (c) at least one ground cable contact. The plurality of electrical contacts may include at least one connection detection contact, the at least one connection detection contact being used to electrically detect connection and disconnection between the data transfer cable and the sensor unknown DI port.The plurality of electrical contacts may include at least one authentication contact, and the second processor may be configured to: send an AU / ID request for the sensor via the at least one authentication contact, receive encrypted AU / ID information in response to the AU / ID request in the absence of power transmission from the DI port unknown to the sensor to the data transmission cable, authenticate the sensor based on the encrypted AU / ID information, and based on the authentication, provide power to the data transmission cable via the at least one power contact. The encrypted AU / ID information may include identification information of the manufacturer of the sensor. The second processor may be configured to: provide power to the data transmission cable via the at least one power contact, send a request for a sensor data stream from the DI port unknown to the sensor via the at least two communication contacts, and receive a sensor data stream in a sensor unknown data format according to a protocol of the DI port unknown to the sensor. The second processor may be configured to: send a request for sensor information from the sensor unknown DI port via the at least two communication contacts, receive sensor information including unencrypted AU / ID information in response to the request, compare the encrypted AU / ID information with the unencrypted AU / ID information, and if the encrypted AU / ID information corresponds to the unencrypted AU / ID information, request and receive the sensor data stream, otherwise interrupt the power supply to the data transmission cable. The sensor unknown DI port may exclude a host isolation device for limiting patient leakage current from the monitor / defibrillator to the sensor. The at least one RD hub may include a second display and a plurality of DI ports, the second display being configured to provide a second visual representation of the sensor data. The at least one sensor hub connector may be arranged on an outer surface of the first housing. The at least one sensor hub connector may include a bracket, and the at least one mating mechanism may include a profile on the at least one RD hub, the mating mechanism being configured to removably couple the at least one RD hub to the bracket. The at least one RD hub connector may include one or more first electrical contacts, and the at least one mating mechanism may include one or more second electrical contacts, and wherein the monitor / defibrillator and the at least one RD hub may be configured to be electrically and / or communicatively coupled via the one or more first electrical contacts and the one or more second electrical contacts with the at least one RD hub physically retained by the at least one RD hub connector.The first housing may include one or more first electrical contacts, and the second housing may include one or more second electrical contacts, and wherein the at least one sensor hub connector and the at least one mating mechanism may be configured to couple the monitor / defibrillator and the at least one RD hub such that the one or more first electrical contacts and the one or more second electrical contacts provide electrical connectivity and / or communication connectivity with the at least one RD hub physically retained in the at least one sensor hub connector. The at least one RD hub may be configured to electrically couple to the monitor / defibrillator via a wired connection and communicatively couple to the monitor / defibrillator via a wireless connection with the at least one RD hub physically retained in the at least one sensor hub connector. The at least one RD hub may be configured to communicatively couple to the monitor / defibrillator via a wired cable or wireless coupling with the at least one RD hub physically separated from the at least one sensor hub connector. The at least one RD hub may be configured to be communicatively coupled to the monitor / defibrillator and / or one or more remote computing devices. The at least one RD hub may include at least one USB port. The at least one DI port may include a sensor-specific DI port. The at least one DI port may correspond to one or more of a lung mechanics sensor, a spirometry sensor, an airway pressure sensor, a pulse oximetry sensor, and a capnography sensor. The at least one RD hub may include multiple sensor-specific DI ports. The multiple sensor-specific DI ports correspond to one or more of an ECG sensor, a pulse oximetry sensor, a capnography sensor, a heart rate sensor, an invasive blood pressure sensor, a non-invasive blood pressure sensor, a temperature sensor, a lung mechanics sensor, a spirometry sensor, an airway pressure sensor, a pulse oximetry sensor, and a capnography sensor. The at least one DI port corresponds to a cardiopulmonary resuscitation compression sensor, i.e., a CPR compression sensor. The at least one RD hub may include a user interface. The user interface may include a second display configured to provide a second visual representation of the sensor data. The second display may be configured to provide a second visual representation of one or more of a pulse oximetry waveform, a capnography waveform, and an ECG waveform. The second display may be configured to provide a second visual representation of one or more physiological parameters corresponding to one or more discrete numerical values. The one or more physiological parameters that may correspond to one or more discrete numerical values ​​may include one or more of blood pressure, heart rate, instantaneous pulse oximetry value, and instantaneous capnography value.The second display may be configured to provide one or more of chest compression data and airway flow sensor data as one or more of a waveform, a discrete value, and a graphical indicator. The second display may be configured to provide ventilation settings, ventilation parameters, and respiratory physiological parameters. The user interface may include one or more of an alarm control and a power button. The user interface may include a data input control. The user interface may be configured to capture one or more of an audio input and a tactile input. The user interface may be configured to provide one or more of an audio output, a visual output, and a tactile output. The system may include a wired and / or wireless coupling port configured to couple the at least one RD hub to a user input device. The user input device may include one of a mouse, a microphone, and a wireless remote control. The user input device may include a wearable computing device. The wearable computing device may include one or more of a headset, a watch, and glasses. The first communication interface and the second communication interface may be configured to be communicatively coupled to each other via a wired and / or wireless coupling. The monitor / defibrillator may be configured to receive sensor data of the patient from the at least one RD hub and associate the received sensor data with sensor data received by the monitor / defibrillator for the patient. The at least one RD hub may be configured to receive sensor data of the patient from the monitor / defibrillator and associate the received sensor data with sensor data received by the at least one RD hub for the patient. The second communication interface may be configured to be communicatively coupled to a remote server via the first communication interface. The second communication interface may be configured to be communicatively coupled to a mobile computing device via the first communication interface, the mobile computing device may include one or more of a smart phone and a computer tablet. The second communication interface may be configured to be communicatively coupled to one or more of a remote server, a mobile computing device, and a wearable computing device in the absence of an existing communication coupling with the first communication interface. The second communication interface may be configured to send one or more of a case file, sensor data, device readiness data, and device status data to a communicatively coupled device. The second communication interface may be configured to receive one or more of sensor data, software updates, settings updates, and protocol updates from a communicatively coupled device. The second communication interface may be configured to be communicatively coupled to one or more computing devices via one or more of a long-range wired and / or wireless connection and a short-range wired and / or wireless connection. The one or more computing devices may include one or more of a mobile computing device, a wearable computing device, a tablet computer, a smart phone, a watch, a head-up display, a laptop computer, or a combination thereof. The short-range wireless connection may include. and near field communication device connection. The long-range wired and / or wireless connection may include one or more of a cellular communication network and a computer network. The second communication interface may be configured to be communicatively coupled to one or more medical devices via one or more of a long-range wired and / or wireless connection and a short-range wired and / or wireless connection. The one or more medical devices may include one or more of a compression monitor, an airway flow sensor, a bag-mask, and a first aid kit. The monitor / defibrillator may be a first monitor / defibrillator, and the one or more medical devices may include a second monitor / defibrillator. The first communication interface and the second communication interface may be configured to be communicatively coupled in response to authentication of the at least one RD hub. The at least one RD hub may be configured to be communicatively coupled to only one monitor / defibrillator during treatment of a patient. The authentication may include information exchange to verify that the monitor / defibrillator and the at least one RD hub can be associated with the same patient. The system may include at least two DI ports configured to allow communication between at least two sensors and the at least one RD hub. The at least two DI ports may include a SS-DI port, a SA-DI port, or a combination thereof. The RD hub may include a mechanical ventilation device. The mechanical ventilation device may include a gas propeller, an expiratory circuit, an inspiratory circuit, and one or more respiratory sensors. The RD hub may be configured to be coupled to an oxygen source and a gas delivery device. The RD hub may include a controller configured to provide a closed-loop control of one or more respiratory parameters during mechanical ventilation of a patient.

[0012] Other capabilities may be provided, and not every implementation according to the invention must provide any of the capabilities discussed, let alone all of them. In addition, the effects mentioned above may be achieved by means other than those mentioned, and the items / techniques mentioned may not necessarily produce the effects mentioned. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Various aspects of the present invention are discussed below with reference to the accompanying drawings, which are not intended to be drawn to scale. These figures are included to provide an explanation and further understanding of various examples, and are incorporated into and constitute a part of this specification, but are not intended to limit the scope of the invention. The accompanying drawings, together with the remainder of the specification, are used to explain the principles and operations of the described and claimed aspects and examples. In these figures, each identical or nearly identical component illustrated in the various figures is represented by a similar number. For clarity, not every component can be marked in each figure. The number of each component in a particular figure is only an example, and other numbers of each component or any component can be used.

[0014] Figure 1 An example of a system of medical devices, data transmission cables, and sensors for capturing data associated with a patient is shown.

[0015] Figure 2A is an example of a data transmission cable that is compatible with a sensor-unaware data interface port for transmitting sensor data to a medical device.

[0016] Figure 2B is a schematic diagram of an example of a flow path of a patient leakage current.

[0017] Figure 2C A schematic example of information available from the authentication circuit and the cable memory is shown.

[0018] Figure 3 Show Figure 2A An exemplary data cable contact configuration for a data transmission cable and a data interface port in FIG.

[0019] Figure 4 A schematic diagram showing an exemplary medical device / data transmission cable system having a sensor-unaware data interface port.

[0020] Figure 5 A state diagram showing a data interface port unknown to a sensor being controlled by a state engine.

[0021] Figure 6 An example of a swim lane diagram showing communication and data transfer between a sensor and a data interface port via a data transfer cable.

[0022] 7A to 7F An exemplary cable lighting configuration for use with a data transmission cable is shown.

[0023] Figure 8 A schematic diagram illustrating exemplary user input controlled cable lighting for a data transfer cable.

[0024] Fig. 9AA schematic diagram illustrating an exemplary data transfer cable with a cable user interface is shown.

[0025] Fig. 9B An example of a data transmission cable with an airway flow sensor and an airway flow sensor user interface is shown.

[0026] Fig. 9C An example of a data transmission cable with a CPR compression sensor and a CPR compression sensor user interface is shown.

[0027] Fig.10 Schematic diagram showing a removable sensor hub of a medical device physically coupled to the interior of a medical device housing.

[0028] Fig.11 A schematic diagram showing a removable sensor hub of a medical device physically coupled to the exterior of the medical device housing.

[0029] Fig.12 Schematic diagram showing a sensor hub removed from an internal medical device coupling.

[0030] Fig.13 Schematic diagram showing a sensor hub removed from an external medical device coupling.

[0031] Fig.14 Examples of various communication implementations for a sensor hub are shown.

[0032] Fig.15 A schematic diagram showing an example of a sensor hub.

[0033] Fig.16 Schematic diagram of an exemplary medical device delivery cable system showing multiple removable sensor hubs coupled to the interior of a defibrillator housing.

[0034] 17A to 17C Schematic diagram showing an example of a respiratory distress hub configuration.

[0035] FIG. 17D to FIG. 17E A schematic diagram showing an example of components of a respiratory distress hub.

[0036] Fig.17F An example of a display screen of a respiratory distress hub is shown.

[0037] Fig.18 A schematic diagram showing an example of components of a sensor data collection device. DETAILED DESCRIPTION

[0038] During a medical event, a medical device may be used by a caregiver (e.g., first responder, paramedic, physician, nurse, ambulance personnel, etc.) to provide medical treatment to a patient and / or may be used to monitor a patient. The medical device may be, for example, a patient monitor, a therapeutic medical device (e.g., a defibrillator, an automatic compression device, a ventilator, etc.), a therapeutic medical device / patient monitor, or a modular therapeutic medical device / patient monitor. These types of medical devices are examples only, and other types and combinations of medical devices are within the scope of the present invention.

[0039] The medical device may be configured to be coupled to one or more sensors. The sensor may include one or more combined therapy delivery / sensing components, such as defibrillation electrodes configured to sense and monitor the patient's electrocardiogram (ECG) and deliver electrotherapy. The medical device may collect data via one or more sensors. The data may include physiological sensor data and / or medical or resuscitation treatment data. Physiological sensor data may include, for example, invasive blood pressure (IBP), non-invasive blood pressure (NIBP), electrocardiogram (ECG) data, pulse oximetry data (SpO2), capnography data, methemoglobin (SpMet), hemoglobin, body temperature, brain oxygen saturation (rSO2), heart rate and / or other vital signs. Physiological data may also include imaging data such as laryngoscopy and / or ultrasound. Medical or resuscitation treatment data may include, for example, CPR performance data derived from measurements obtained from a chest compression sensor (e.g., compression depth, compression rate, chest release, perfusion performance, etc.) and / or ventilation data derived from measurements obtained from an airway flow sensor (e.g., ventilation tidal volume, ventilation rate, minute ventilation, ventilation performance, etc.). These types of data are merely examples and not limiting of the present invention, and are discussed in further detail below.

[0040] The medical device and one or more sensors can be coupled to each other via a data transmission cable. To achieve these wired couplings, the medical device can include one or more data interface (DI) ports. Each data interface port can be configured to be removably coupled to a data transmission cable, which in turn is coupled to the sensor.

[0041] The DI port may be a sensor-specific DI port. For example, in various implementations, the sensor-specific DI port may be configured with a cable contact count and wiring assignment, voltage (s) and / or processor configuration for a signal processing protocol that is compatible with one type of sensor but incompatible with another type of sensor. For example, a sensor-specific DI port may be compatible with an IBP accessory (e.g., a sensor / data transmission cable combination used with an IBP) but may be incompatible with a capnography accessory (e.g., a sensor / data transmission cable combination used for sensing exhaled gas flow such as carbon dioxide). As an incompatible accessory, the capnography accessory may not physically mate with the IBP-specific port and / or may not be electrically compatible and / or may provide the IBP-specific port with sensing data that the IBP-specific port cannot process due to differences in data protocols for different sensor data types.

[0042] Sensor-specific DI ports present usability issues for medical professionals and especially for emergency care personnel. Sensor-specific DI ports require that each sensor cable be connected to a specific port on a medical device. Emergency care situations are often chaotic, with significant urgency in terms of time. This chaos and urgency are partly due to the inherent nature of emergency medical events (such as cardiac arrest, drug overdose, car accident injuries, or gunshot wounds). In addition, the scene of an emergency may not be a calm and orderly doctor's office, but an ambulance, emergency room, chaotic workplace, home or school, highway, public sidewalk, or even a battlefield. The usability challenges presented by attempting to connect multiple sensor cables to specific ports on a medical device in these situations exceed the usability challenges of non-medical devices used in calmer and less time-sensitive situations.

[0043] The sensor-unaware DI port at least addresses this usability problem of the medical device. The sensor-unaware DI port can be configured to capture a variety of sensor data types, where each sensor data type is provided via a data transfer cable configured to provide the sensor data in a format compatible with the sensor-unaware DI port. Thus, a caregiver can attach any sensor cable to any available sensor-unaware DI port on the medical device, thereby reducing time and confusion in a potentially life-saving manner.

[0044] Sensor-specific DI ports also present adaptability issues for medical device manufacturers and users. The adaptability issue arises from the hardware changes required to adapt to new or changed sensors with sensor-specific DI ports. In order to adapt to sensor changes, the manufacturer of the medical device may have to change one or more of the processor configurations used for the cable contact count and wiring assignments, (one or more) voltages and / or signal processing protocols for the sensor-specific DI ports. In addition, the sensor-specific DI ports may include patient leakage current isolation customized according to the power requirements of the specific sensor. For example, the operating power requirements of the airway flow sensor may be greater than the operating power requirements of the IBP sensor. The airway flow sensor may require 0.5 watts, while the IBP sensor may only require 0.25 watts. As a result of these differences in operating power requirements, the patient leakage current isolation hardware on the two ports will be different. Therefore, in order to adapt to new or different sensors, the manufacturer must also change the patient leakage current isolation hardware for the sensor-specific DI ports. As a result of these changes, the user must make the medical device available for hardware modifications, and / or more likely, purchase a new device to accommodate the sensor changes.

[0045] The sensor unknown DI port can be coupled with a data transfer cable that is compatible with this type of port. The data transfer cable can include hardware that is compatible with the cable contact count and wiring assignments and voltage(s) of the sensor unknown DI port. In addition, the data transfer cable can include a processor, stored software, and patient leakage current isolation that provides sensor data in an unknown format, limits unknown power delivery as needed by the sensor, and customizes the patient leakage current isolation according to specific sensor power requirements.

[0046] In addition to the availability advantage of the sensor-unknown DI port, the sensor-unknown DI port combined with a compatible data transmission cable can provide an adaptability advantage. A compatible data transmission cable is a data transmission cable that is mechanically, electrically, and programmatically compatible with the sensor-unknown DI port rather than the sensor-specific DI port. The adaptability advantage is that a medical device with a sensor-unknown DI port can adapt to new sensors and / or sensor changes through software updates without hardware changes. With the sensor-unknown DI port, the processor configuration used for the cable contact count and wiring allocation, (one or more than one) voltage and / or signal processing protocol is compatible with any type of sensor. Therefore, in order to adapt to new sensors, manufacturers can update the software on the medical device to adapt to the new sensor and provide a compatible data transmission cable for the sensor. Users of medical devices can add or purchase additional sensor / cable combinations without the need to replace or modify the medical device. Software updates can occur via a remote connection and / or via a connection to a medical device. For example, when the data transmission cable is first connected to the medical device, the data transmission cable and the medical device can communicate to download software to the data transmission cable, which provides a data format that enables the medical device to read and process data from the data transmission cable. Additionally, each time the data transfer cable is connected to the medical device, the data transfer cable and the medical device can communicate to provide any medical device software updates to the data transfer cable and / or to provide any data transfer cable formatting updates to the medical device. Thus, the communication between the data transfer cable and the medical device can ensure data and software compatibility between the data transfer cable and the medical device at each connection.

[0047] Another advantage imparted by the sensor-agnostic DI port combined with a compatible data transmission cable is a reduction in weight, volume, and signal noise of the medical device. This reduction stems from the removal of patient leakage current isolation from the sensor-agnostic DI port to the data transmission cable.

[0048] As discussed above, medical devices such as patient monitors or patient monitors / defibrillators will include the attachment of multiple sensors for effective patient care. Each sensor connection via a wired cable requires a DI port with patient leakage current isolation. This applies to sensor-specific DI ports and sensor-unknown DI ports. Each patient leakage current isolation included in the medical device increases the weight and volume of the medical device and contributes to signal noise. The higher the rated power of the sensor, the more weight, volume and signal noise increase. The weight increase is derived from isolation circuits and other physical isolation components and physical noise reduction components. In some cases, signal noise reduction requires a physical noise shield (e.g., a conductive layer around). The volume increase is derived from the physical separation distance between the ports required for isolation hardware and electrical isolation and noise reduction. The signal noise increase is derived from the power transmitted by the isolation circuit to power the sensor. Higher power transmission causes more signal noise. Therefore, higher power transmission requires more physical noise reduction components and physical separation, thereby contributing to the increase in weight and volume of the medical device.

[0049] For sensor unknown DI ports, if patient leakage current isolation is included in the port, each port is isolated and noise reduction is provided according to the port (one or more than one) with the maximum power requirement. For example, a medical device may provide three DI ports to enable connection to an IBP sensor, a temperature sensor, and an airway flow sensor. The IBP and temperature sensors may have an operating power requirement of at least between 0.1 watts and 0.5 watts (e.g., about 0.25 watts), and the airway flow sensor may have an operating power requirement of at least between 0.2 watts and 1.0 watts (e.g., about 0.5 watts). In various embodiments, the airway flow sensor may have an operating power requirement greater than the operating power requirement of the IBP and / or temperature sensor. If patient leakage current isolation is provided at the sensor unknown DI port, each port must provide patient leakage current isolation based on the operating power requirement of the airway flow sensor.

[0050] In order to reduce the weight and volume of the medical device, the data transmission cable may include patient leakage current isolation, and the sensor unknown DI port may not include (i.e., may exclude) patient leakage current isolation. The medical device may provide the same power to each sensor unknown DI port, and the isolation circuit in the compatible data transmission cable may control the power transmission based on the specific sensor attached to the cable. In the above example, regardless of the rated power of the airway flow sensor (e.g., 0.5W rated power), the IBP sensor cable can be isolated to a rated power between 0.1W and 0.5W (e.g., 0.25W rated power). In addition, the physical and electrical configuration of the isolation of noise is also customized for a specific sensor while maintaining the sensor unknown configuration of the DI port. In the case of providing isolation in the cable, the sensor unknown DI port at the medical device does not require isolation hardware, physical separation or noise reduction of the isolation hardware. Therefore, the sensor unknown DI port combined with the compatible data transmission cable reduces the total weight and volume of the medical device without reducing the signal quality or leakage current protection and increasing the total number of available ports.

[0051] Eliminating patient leakage current isolation can reduce the weight and volume of medical devices by 5 to 15%. Depending on the medical device, this can be a weight reduction of at least 0.5 kg. Depending on the number of ports, the total weight reduction of multiple sensor unknown DI ports can be about 0.1 to 0.6 kg. Emergency paramedics may need to carry 11 to 18 kg of equipment that does not include any protective clothing (which may also be heavy for firefighters). In some cases, these emergency paramedics are climbing multiple flights of stairs and / or running over rugged terrain to reach victims. Therefore, weight reduction of portable medical devices is critical. A similar situation is in backpacking, where hikers try to reduce the weight of each piece of backpack equipment to reduce the overall load.

[0052] Another advantage of locating patient leakage current isolation in a data transmission cable compatible with a sensor-unknown DI port is that the authentication circuit can be electrically separated from the cable processor. The medical device can authenticate the data transmission cable and sensor before applying power to the sensor-unknown DI port for sensor data communication.

[0053] In implementation, the medical device may include one or more removable sensor hubs that provide one or more DI ports. These DI ports may be sensor unknown, sensor specific, or a combination thereof. The removable sensor hub may also include hardware and / or hardware controls used for a specific sensor or sensor combination. For example, the sensor hub may provide pneumatic controls and pump systems used for NIBP and / or capnography. One or more removable sensor hubs may be removably coupled to a medical device within a medical device housing or to the outside of a medical device housing. The sensor hub may capture sensor data when physically coupled and when physically decoupled from the medical device. The removable sensor hub may be communicatively coupled to the medical device via a wired or wireless connection.

[0054] The sensor hub can provide several advantages. For example, instead of including sensor-specific hardware inseparably in the medical device, the sensor hub can include the hardware. This provides the following advantages: the manufacturer can customize the medical device according to the sensor requirements of the customer, and the customer can customize the medical device according to the desired sensor. In addition, the update and replacement of this hardware and associated software can only involve the sensor hub instead of the entire medical device. The additional advantage of the removable sensor hub is that the sensor hub can remain coupled to the patient while being physically decoupled from the medical device. In this implementation, the removable sensor hub can communicate wirelessly with the medical device, which provides the advantage of eliminating the cable connection between the patient and the medical device for a period of time. Alternatively, the removable sensor hub can communicate with the medical device via a single cable between the medical device and the sensor hub. This can provide the advantage of reducing the number of cable connections between the patient and the medical device to one (rather than multiple cables required for multiple sensors). Patients are often transferred between medical care locations and personnel during care. For example, patients can be transported from the scene of an emergency to an ambulance, a hospital emergency room, an operating room, an intensive care unit, a recovery room, a rehabilitation center, etc. The sensor hub allows for continuous patient monitoring during all of these physical transitions because the sensor hub can be detached and reattached to the larger medical monitoring instrument without removing the sensor from the patient, without moving the larger instrument, and reducing the cable connections to one or zero. Otherwise, without this enhancement, the caregiver would have to manage the cable connections of the larger and heavier medical device to the patient which could be much more cumbersome.

[0055] In addition, the caregiver can place the sensor hub on a wheel bed or other support items near the patient, and place it in a position that the caregiver can easily view and reach. In implementation, the sensor hub can be lightweight enough to be placed on the patient without any negative impact on patient care and / or resuscitation. Positioning the sensor hub as close to the patient as possible (including possibly on the patient) can enable the caregiver to provide care and view the data display on the sensor hub and / or connect or disconnect the sensor without having to divert attention from the patient, in a state where their eyes are staring at the patient's time with almost no interruption. The nearest position can also keep the sensor hub in the sterile surgical field. These positions may not be options for large medical instruments. However, the medical advantages of large instruments in data processing, analysis, storage and display will not be lost with the use of the sensor hub, because the sensor hub can be communicatively and physically coupled to the large instruments.

[0056] refer to Figure 1, shows an example of a system of medical devices, data transmission cables, and sensors for capturing data associated with a patient. System 100 includes at least one medical device 110, sensors 120a and 120b, and data transmission cables 130a and 130b. Each data transmission cable 130a and 130b couples a respective sensor 120a or 120b to medical device 110. In this example, sensor 120a is a medical or resuscitation treatment sensor (e.g., a chest compression sensor), and sensor 120b is a physiological sensor. The claimed subject matter is not limited to a particular type or class of sensors. In various implementations, sensor 120b may be one or more of an invasive blood pressure (IBP) sensor, a non-invasive blood pressure (NIBP) sensor, an electrocardiogram (ECG) sensor, a pulse oximetry (SpO2) sensor, a capnography sensor, a methemoglobin (SpMet) sensor, a hemoglobin sensor, a temperature sensor, a cerebral oxygen saturation (rSO2) sensor, a heart rate sensor, a spirometry sensor, a pneumotachometer, an airway pressure sensor, an airway flow sensor, and / or other physiological sensors. In various implementations, sensors 120a and / or 120b may be imaging sensors used for laryngoscopy and / or ultrasound. In various implementations, sensors 120a and / or 120b may be imaging sensors for laryngoscopy and / or ultrasound. In various implementations, sensor 120a may be a chest compression sensor or an airway flow sensor. Data transmission cables 130a and 130b may each be connected to respective DI ports 140a and 140b. One or more of the DI ports 140a and 140b may be a sensor-agnostic DI (SA-DI) port or a sensor-specific DI (SS-DI) port. The corresponding data transmission cable 130a or 130b may be a data transmission cable compatible with the SA-DI port or the SS-DI port. Figure 1 One medical device, two sensors, two DI ports, and two data transmission cables are shown in FIG. 1 , but in various implementations, system 100 may include one or more medical devices, one or more sensors, and one or more data transmission cables.

[0057] The medical device 110 can provide treatment to a patient 170 and / or monitor patient 170 and / or monitor treatment metrics of treatment provided by a caregiver 180. The medical device 110 can include a user interface 160 on a display 150. The user interface 160 can provide one or more of medical or resuscitation treatment data and physiological data from sensors 120a and / or 120b. The medical device 110 can be, for example, a patient monitor, a therapeutic medical device (e.g., a defibrillator, an automatic compression device, a ventilator, etc.), a therapeutic medical device / patient monitor, or a modular therapeutic medical device / patient monitor. The medical device 110 (or medical equipment 110) can be provided as one physical device (e.g., a single housing), or can be provided as multiple physical devices configured to be communicatively and / or operably coupled to each other (e.g., a modular physical device having two or more separate housings). Although in Figure 1 Although shown as one caregiver, caregiver 180 may represent multiple caregivers (eg, a care team) associated with patient 170 .

[0058] refer to Figure 2A And further reference Figure 1 , showing an example of a data transmission cable compatible with a sensor-unaware data interface port for transmitting sensor data to a medical device. The data transmission cable 210 (e.g., data transmission cables 130a and / or 130b) is configured to provide at least power transmission and data communication between a sensor 220 (e.g., sensor 120a and / or 120b) for collecting sensor data and a sensor-unaware data interface (DI) port 298 (e.g., DI port 140a and / or 140b) associated with a medical device 110.

[0059] Data transmission cable 210 compatible with SA-DI port 298 includes flexible cable 230 comprising conductive wires (e.g., conductive wires 240a, 240b, 240c, and 240d) disposed within a continuous insulating sheath 245. The conductive wires may include single and / or multiple strands of one or more conductive materials. Figure 2A The number of wires shown in FIG. 2 is merely an example and is not intended to limit the present invention. The cable 230 may be fixedly fastened to the first electromechanical connector 250 at a first end of the cable 230 and fixedly fastened to the second electromechanical connector 290 at a second end of the cable 230 .

[0060] The first electromechanical connector 250 may include a housing 252 and an electrical fitting 254 (e.g., a first electrical fitting) disposed within the housing 252 at an open end of the housing away from the cable 230. In other words, the cable 230 is connected to the housing at a first end of the housing, and the electrical fitting 254 for the sensor is disposed in a second and different end of the housing. The electrical fitting 254 is configured to be removably coupled to the sensor 220 (e.g., coupled to an electrical connector 225 associated with the sensor 220). The electrical fitting 254 provides electrical coupling between one or more contacts 226 associated with the sensor and one or more contacts 256 associated with the data transmission cable 210. The combination of the electrical fitting 254 and the electrical connector 225 may be, for example, a pin / socket combination, a plug / jack combination, a card edge / spring contact combination, etc.

[0061] The first electromechanical connector 250 also includes a data interface circuit 260 disposed within the housing 252 . Figure 2A The data interface circuit 260 in the first electromechanical connector 250 is schematically illustrated, and the components of the data interface circuit 260 are also illustrated as an inset box with an enlarged view of the data interface circuit 260. The data interface circuit is electrically coupled to the electrical mating piece 254 through one or more electrical contacts 256, and is electrically coupled to the conductive wires (e.g., wires 240a, 240b, 240c, and 240d) of the cable 230. The data interface circuit 260 includes a cable processor 265, a cable memory 266, and a cable patient leakage current isolation 270. In an implementation, the data interface circuit 260 includes an analog-to-digital (A / D) converter circuit 269 that is configured to convert an analog signal from the sensor 220 into a digital signal for use by the cable processor 265. For clarity, the A / D converter is shown separately from the cable processor 265, but can be integrated into the cable processor 265.

[0062] The cable patient leakage current isolation 270 includes an isolation device 270 and / or circuits and other hardware and / or physical components configured to limit the flow of patient leakage current from the medical device 110 to the patient via the sensor 220. In particular, for high voltage electrotherapy, leakage current isolation can be beneficial for safety reasons. Figure 2B , a schematic diagram showing an example of a flow path of a patient leakage current. In this illustrative example, the medical device 110 is a defibrillator, and the patient 170 is coupled to defibrillation electrodes 98 and 99. The patient 170 is also coupled to a sensor 220, which in turn is coupled to the medical device 110 via a data transmission cable 210. The defibrillation current (I defibrillation) follows a current path from the medical device 110 to the defibrillation electrode 98, through the patient 170 to the electrode 99, and then back to the medical device 110. For example, via stray capacitance between the medical device 110, the patient 170, and the sensor 220, there is a potential current path between the defibrillation circuit and the data transmission cable 210, through which the patient leakage current (I leakage ) can reach the patient 170 via the sensor 220. However, the isolation 270 in the data transmission cable 210 is configured to prevent any patient leakage current from reaching the sensor 220 and the patient 170, thereby providing a layer of safety protection built into the cable. In some embodiments, the SA-DI port 298 does not include (i.e., excludes) Figure 2B A patient leakage current isolation circuit is schematically shown in FIG.

[0063] Back to Figure 2A , the isolation device 270 and / or the circuit may include an isolation barrier device, such as a dual capacitive isolation barrier device, a digital isolator device, an optical isolator device, etc. The isolation device 270 is configured to transmit the power signal 274 and the communication signal 276 across the isolation barrier 278. These devices are only examples and are not intended to limit the present invention. The hardware and / or physical components may include, but are not limited to, conductive and insulating layers and / or coatings coupled to and / or surrounding the isolation device 270 and / or the circuit.

[0064] The isolation device 270 is configured to transmit power 274 unidirectionally across the isolation barrier 278 toward the cable processor 265. When the data transmission cable 210 is coupled to the medical device 110 via the SA-DI port 298, the medical device 110 can be a sensor power supply and can provide power 274 to the cable processor 265 and the sensor 220 via the port 298 and the data transmission cable 210. For example, the data transmission cable 210 can transmit power 274 via at least one conductive line 240d, wherein another conductive line 240c is grounded. The isolation device 270 can transmit the power 274 transmitted from the medical device 110 by the data transmission cable 210 to the cable processor 265 and the sensor 220 in one direction across the isolation barrier 278. With this unidirectional power transmission, the power transmission from the processor side of the isolation 270 toward the medical device 110 is substantially limited or absent. In implementation, the isolation device 270 can transmit or transfer 0.1 to 1 watt of power 274 across the isolation barrier 278. In implementation, the isolation device 270 is configured to transmit an amount of power 274 across the isolation barrier 278 that is specific to the power requirements of the sensor 220. For example, an invasive blood pressure sensor may require approximately 0.2 watts, while a flow sensor may require approximately 0.5 watts. Thus, the power transmission capabilities of the isolation device 270 are customized according to the power requirements of the sensor 220. Thus, the medical device 110 can be configured to apply an amount of power to the SA-DI port 298 that is compatible with a variety of sensors.

[0065] The isolation device 270 is also configured to bidirectionally transmit communication signals 276 across the isolation barrier 278. The bidirectional nature of the transmission enables the medical device 110 to be the source of the communication signals and send information to the cable processor 265 and the sensor 220 via these signals. Similarly, the bidirectionality enables the cable processor 265 and / or the sensor 220 to be the source of the communication signals and send information to the medical device 110 via these signals. In an implementation, the communication signals 276 conform to a controller area network (CAN) bus protocol using two communication lines 240a and 240b that control communication based on a voltage differential between two lines (e.g., CAN-hi and CAN-lo).

[0066] In an implementation, the data interface circuit 260 includes an authentication circuit 264, and the cable contacts include at least one authentication cable contact 395e. In such an implementation, the conductive wire includes at least one authentication wire 240e, and the contacts in the port 298 include at least one authentication contact 399e. The authentication circuit 264 is configured to receive an authentication / identification (AU / ID) request from the medical device 110 via the at least one authentication cable contact 395e. In addition, the authentication circuit 264 is configured to send AU / ID information back to the medical device 110 in response to the received AU / ID request.

[0067] like Figure 2C As shown, the authentication circuit 264 may include a built-in encryption engine 25 that uses an encryption key specific to the medical device 110. For example, the manufacturers of both the medical device 110 and the data transmission cable 210 may provide encryption keys that are compatible with and specific to both the medical device 110 and the data transmission cable 210 for authenticating the data transmission cable 210. The encryption engine 25 may provide the encrypted AU / ID information 26 to the medical device 110 for authenticating the data transmission cable 210. In implementation, the cable memory 266 may include stored unencrypted sensor information 21. In the absence of malicious and / or hacker modification of the data transmission cable 210, the unencrypted sensor information 21 matches the encrypted AU / ID information 26. The cable memory 266 may also include stored sensor software and / or application programming interface (API) 23 and corresponding software / API information (such as, but not limited to, software version number, API version number, update information, supported data protocols, sensor data formats, etc.).

[0068] In various implementations, the sensor software and / or API 23 are stored in the memory 266 at the time of manufacture of the data transmission cable 210. When the data transmission cable 210 is connected to the medical device 110, the medical device 110 can update the software. Alternatively, when the data transmission cable 210 is connected to the medical device 110, the sensor data format can be transmitted from the cable to the medical device, and the data format can be updated on the medical device. During communication with the data transmission cable 210, the medical device 110 can receive the version and update information of the sensor data format, software and / or API 23. If an update is required, the medical device 110 can command the cable processor 265 to enter the download mode. The cable processor 265 can accept or reject the request based on other ongoing activities. When accepted, the medical device 110 can initiate and continue the sensor data format, software and / or API update.

[0069] Reference again Figure 2A And further reference Figure 3, the data transmission cable 210 also includes a second electromechanical connector 290 fixedly fastened to the second end of the cable 230. The second electromechanical connector 290 includes cable contacts (e.g., cable contacts 395a, 395b, 395c, and 395d), each of which is electrically coupled to a respective conductive wire (e.g., wire 240a, 240b, 240c, and 240d) of the cable 230. The second electromechanical connector 290 is configured to removably electromechanically couple the data transmission cable 210 to the SA-DI port 298. The SA-DI port 298 includes port contacts (e.g., port contacts 399a, 399b, 399c, and 399d), which are configured to be electrically coupled to the cable contacts when the data transmission cable 210 is coupled to the port 298. The cable contacts include at least two communication cable contacts 395a and 395b, at least one power cable contact 395c, and at least one ground cable contact 395d. The cable contacts are electrically coupled to wires 240a, 240b, 240c, and 240d, respectively. In addition, the cable contacts are configured to be electrically coupled to contacts 399a, 399b, 399c, and 399d, respectively.

[0070] As shown herein, port 298 is a male connector, second electromechanical connector 290 is a female connector, electrical mating piece 254 is a male connector, and electrical connector 225 is shown as a female connector. However, these connection designations are merely examples and are not intended to limit the present invention. Connections shown as female connectors may be, and similarly, connections shown as male connectors may be female connectors. Cable contacts are shown as pins only as examples, and the present invention is not limited to pin / socket connections as shown. Various connection configurations (e.g., including (one or more than one) pin / socket contacts and (one or more than one) card edge / spring contacts) are within the scope of the present invention.

[0071] In an implementation, the cable contacts include at least one connection detection cable contact 395f for electrically detecting a connection and / or disconnection between the data transfer cable 210 and the at least one SA-DI port 298. For example, ground detection at contact 399f (e.g., detection of ground connection 398) indicates to port 298 that the data transfer cable 210 is electrically coupled to port 298. The connection detection cable contact 395f and contact 399f enable detection of an unconnected state (e.g., the cable 210 is not electrically coupled to port 298), a connected state (e.g., the cable 210 is electrically coupled to port 298), a change in state from unconnected to connected, and a change in state from connected to unconnected (i.e., the cable 210 is disconnected or removed from port 298).

[0072] Figure 3A schematic summary of the directionality of signal transmission between port 298 and data transfer cable 210 via the port's contacts and the cable's cable contacts is provided. The AU / ID cable contact / contact connection supports bidirectional signal transmission, the power cable contact / contact connection supports unidirectional signal transmission, and the communication cable contact / contact connection supports bidirectional signal transmission.

[0073] refer to Figure 4 , a schematic diagram of an exemplary medical device / data transmission cable system having a sensor-unaware data interface port is shown. The medical device / data transmission cable system 400 includes a medical device 110 and a data transmission cable 210. The medical device 110 includes a housing 410, a display 150, a power control 436, and at least one SA-DI port 298 (e.g., SA-DI ports 298a and 298b). Although Figure 4 Two ports are shown in FIG. 1 , but the number of ports is only an example and does not limit the present invention.

[0074] In various implementations, the medical device 110 may include only one or more SA-DI ports, or a combination of one or more sensor-agnostic DI ports and one or more sensor-specific DI ports. Figure 4 As schematically shown in FIG. 4 , SS-DI ports 498a and 498b include port patient leakage current isolation 470. SS-DI ports 498a and 498b are also spaced apart by a distance d>0 for noise reduction and electrical isolation. SS-DI ports 498a and 498b may also include a physical element 478 such as a conductive material layer to reduce electromagnetic interference that causes signal noise. As discussed above, these features of the SS-DI port increase the weight and volume of the medical device 110. In contrast, SA-DI ports 298a and 298b may exclude (i.e., not include) port patient leakage current isolation. These ports are coupled to a data transmission cable (e.g., data transmission cable 210) that is compatible with the SA-DI port and includes a cable patient leakage current isolation 270. In addition, SA-DI ports 298a and 298b are close to each other at a spacing approximately equal to zero. Since these ports do not include patient leakage current isolation, these ports do not require a noise reduction barrier or physical layer 478. The overall lack of port patient leakage current isolation, inter-port spacing, and physical noise reduction layers on multiple SA-DI ports reduces the weight and volume of the medical device 110. In implementations, the medical device 110 can accommodate more sensors with SA-DI ports than sensors with SS-DI ports and still achieve an overall weight and volume reduction. Note that the medical device 110 can include additional patient leakage current isolation 499 in addition to the patient leakage current isolation provided by the data transmission cable 210.

[0075] The SS-DI port 498 may include a host patient leakage current isolation circuit 470. In contrast, the SA-DI ports 298a and 298b do not include (i.e., exclude) a host patient leakage current isolation circuit 470. For the SA-DI ports 298a and 298b, the function of patient leakage current isolation is handled by the cable patient leakage current isolation 270.

[0076] SS-DI port 498 may include host noise shield 478. In contrast, in an implementation, SA-DI ports 298a and 298b do not include (i.e., exclude) host noise shield 478. For SA-DI ports 298a and 298b, the function of the noise shield is handled by cable noise shield 272.

[0077] The medical device 110 may also include a DI port electronics 420. In an implementation, one or more components of the DI port electronics 420 may be physically separated or separable from the medical device electronics (e.g., a processor, memory, and associated electronics and hardware controls for treatment delivery, data collection, processing, analysis, communication, and display, etc.), and communicatively and / or electronically coupled to the medical device electronics. In an implementation, the DI port electronics 420 may be integrated into the medical device electronics and / or may be a component of the medical device electronics. The DI port electronics 420 may include a host processor 425, a host memory 426, and a state engine 428. In an implementation, the state engine 428 may be a part and / or function of the host processor 425. The host processor 425 may receive sensor data from the sensor 220 via the data transmission cable 210, and may provide the sensor data to the medical device electronics for processing and / or display (e.g., at the physical display 150). In implementation, the host memory 426 may also include stored sensor software and / or API 427 and corresponding software / API information (eg, but not limited to, software version number, API version number, update information, supported data protocols, etc.).

[0078] In an implementation, the medical device 110 may be a defibrillator or a patient monitor / defibrillator. In such an implementation, the medical device 110 includes an electrotherapy delivery circuit 460 and a defibrillation electrode 465 that may also be used as an ECG sensor. For example, the electrotherapy delivery circuit 460 may include one or more capacitors configured to store electrical energy for a pacing pulse or a defibrillation pulse. The electrotherapy delivery circuit may also include resistors, additional capacitors, relays and / or switches, a bridge such as an H-bridge (e.g., including multiple insulated gate bipolar transistors or IGBTs), a voltage measurement component, and / or a current measurement component.

[0079] The display 150 is configured to provide at least one visual representation of sensor data received by the medical device 110 via SA-DI port 298a and / or 298b and / or via (one or more than one) SS-DI port 498. The visual representation can provide data as a graph and / or text data. The visual representation can include waveform data, such as but not limited to ECG, pulse oximetry and / or carbon dioxide tracing. The visual representation can include discrete numerical data, such as but not limited to blood pressure (NIBP, IBP), heart rate, instantaneous pulse oximetry and / or instantaneous carbon dioxide tracing. Additionally or alternatively, the visual representation can include or provide caregiver feedback, such as CPR feedback and / or ventilation feedback. CPR feedback can include, for example, compression depth, compression rate, compression time, compression release and / or perfusion performance. The display 1540 can provide CPR feedback in real time in units of compression. Ventilation feedback can include, for example, gas volume, ventilation rate, ventilation quality and / or ventilation time. In an implementation, the ventilation feedback may be bag-mask feedback. The visual representation may also include image data 1567, such as, but not limited to, laryngoscopy and / or ultrasound images. The ultrasound images may include ultrasound images of the patient's tendons, muscles, joints, internal organs, skeletal structures, abdomen, and / or other components of the patient's heart, blood vessels, carotid arteries, and / or cardiovascular system. The visual representation may be part of a guided medical intervention such as a biopsy, tissue or fluid sample, and / or other diagnostic or invasive procedure. In an implementation, the display 1540 may include the following information about Fig.17F One or more features of display 2790 are discussed.

[0080] DI port electronics 420 in Figure 4 DI port electronics 420 can control and process data from SA-DI ports 298a and 298b. Figure 4 498, but in implementation, the DI port electronics 420 may control and process data from the SS-DI port 498. Alternatively, the SS-DI port 498 may not be electrically and / or communicatively connected to the DI port electronics 420. For example, the medical device electronics may control and process data from the SS-DI port 498.

[0081] In an implementation, the DI port electronics 420 may include a state engine 428. The DI port state engine 428, the DI port electronics 420, and / or the host processor 425 may manage each SA-DI port 298 independently of one or more other DI ports 298. The DI port state engine 428 may manage the state of the SA-DI port 298.

[0082] refer to Figure 5 And about Figure 6 Further discussing, a state diagram 40 of a sensor-unknown data interface port controlled by a state engine is shown. The state of the SA-DI port 298 can be one of an unconnected state 41, a connected state 43, an authorized / identified state 45, a port active state 47, and a port closed state 49. Detection of a connection 42 between the data transmission cable 210 and the SA-DI port 298 can trigger a transition from the unconnected state 41 to the connected state 43. Once in the connected state 43, the state engine 428 automatically transitions to the authenticated / identified state 45. Successful authentication of the data transmission cable can trigger a transition from the authenticated / identified state 45 to the port active state 47. Once in the port active state 47, the medical device 110 and / or the sensor hub 1010 can apply sensor power 51 to the SA-DI port 298 and enable communication 55 between the sensor 220 and the medical device 110 and / or the sensor hub 1010. In the example, before sensor power 51 is applied to the SA-DI port 298, the voltage on the power contact 399c and the power cable contact 395c is zero volts. The medical device 110 can provide operating power for the operation of the SA-DI port 298, but the amount of power may be insufficient for the operation of the sensor 220. In implementation, in the port active state 47, the medical device 110 and / or the sensor hub 1010 can verify 53 the authentication of the data transmission cable 210. As described with respect to Figure 6 In more detail, upon successful authentication 53, communication 55 between the sensor 220 and the medical device 110 and / or sensor hub 1010 may continue.

[0083] In various implementations, one or more of a failed authentication, an accessory error, and a disconnected data transfer cable may trigger a transition from the port active state 47 to the port closed state 49. In the port closed state 49, the medical device 110 and / or the sensor hub 1010 may return the voltage on the power contact 399c to zero volts to disable sensor power 57 to the SA-DI port 298. Once in the port closed state 49, if the medical device 110 and / or the sensor hub 1010 detects a disconnect 48 or a disconnect that triggers a transition to the port closed state 49, the detection may trigger a transition from the port closed state 49 back to the unconnected state 41. Thus, in response to the electrical detection of the disconnect, the host processor 425 and / or the state engine 428 are configured to interrupt the provision of power to the data transfer cable 210 via at least one SA-DI port 298. In an implementation, the unconnected state 41 is the default state of the SA-DI port 298 when the medical device 110 and / or the sensor hub 1010 is powered on.

[0084] refer to Figure 6 , showing an example of a swim lane diagram for communication and data transfer between a sensor and a data interface port via a data transfer cable. Figure 6 The sequence shown in is only an example and does not limit the present invention. The sequence can be changed, for example, by adding, removing, rearranging, combining and / or performing stages simultaneously. Fig.18 As discussed, the functions described as being performed by the host 58, the medical device 110, and / or the SA-DI ports 298, 298a, and / or 298b may be performed by the host processor 425 and / or another processor associated with the medical device 110 and / or the sensor hub 1010. Figure 2A As discussed, the functions described as being performed by accessory 59 , data transmission cable 210 , and / or sensor 220 may be performed by cable processor 265 .

[0085] like Figure 6 As shown, communication and data transfer is between an accessory 59 (e.g., a sensor 220 and a data transfer cable 210) and a host 58. In an implementation, the host 58 is a medical device 110 that includes at least one SA-DI port 298. Alternatively, the host 58 is a sensor hub 1010 that is physically decoupled from the medical device 110 that includes at least one SA-DI port 298 (e.g., as described below with respect to Figures 11 to 16 ), and / or the host is a medical device 110 that is physically coupled to a sensor hub 1010 that includes at least one SA-DI port 298.

[0086] refer to Figure 6 In the unconnected state 41 in the swim lane diagram of FIG. 2 , initially, the host 58 and the accessory 59 are physically and electrically unconnected, and the SA-DI port 298 is in an inactive state. In this inactive state, the host (e.g., the medical device 110 and / or the sensor hub 1010) does not enable the SA-DI port 298 and does not apply power to the SA-DI port 298, and there is no power transmission from the SA-DI port 298 to the data transmission cable 210.

[0087] At stage 520, the user of accessory 59 connects data transfer cable 210 to SA-DI port 298. In implementation, port 298 may be connected to SA-DI port 298, for example, via a Figure 3 The detection cable contact 395f and the detection contact 399f are used to detect the connection of the cable 210. In response to the connection detection, the state engine 428 can cause the SA-DI port 298 to transition from the unconnected state 41 to the connected state 43.

[0088] In implementation, within the connection state 43, the state engine 428 may cause the SA-DI port 298 to transition to the authentication / identification (AU / ID) state 45. In the AU / ID state 45, the host processor 425 may send an AU / ID request 533 to the authentication circuit 264. In response to the AU / ID request 533, the authentication circuit 264 is configured to send an AU / ID response 536. The exchange of the AU / ID request 533 and the AU / ID response 536 may occur via at least one AU / ID contact 399e, the AU / ID cable contact 395e, and the authentication line 240e.

[0089] In an implementation, the exchange of AU / ID request 533 and AU / ID response 536 occurs in the absence of power transmission from host 58 to cable 210. In addition, isolation 270 electrically separates authentication circuit 264 from cable processor 265. In this manner, authentication and identification of accessory 59 occurs before host 58 provides power to cable processor 265 and sensor 220. Thus, processor 265 and sensor 220 are prevented from communicating with host 58 until authentication and identification are complete. In the absence of authentication of accessory 59 (e.g., an authentication sequence is incomplete and / or authentication fails), host processor 425 and / or state engine 428 can disable SA-DI port 298, and thereby disable power to cable 210.

[0090] The AU / ID response 536 includes AU / ID information that authenticates the accessory as a valid accessory recognized by the host 58 and identifies the sensor 220. For example, a valid accessory may include a sensor and a data transmission cable that provides data in a format compatible with the SA-DI port 298 and is identified by the host manufacturer as compatible with the medical device 110. The AU / ID information may include, for example, but not limited to, the model, serial number, hardware revision number, and / or power requirements of the sensor 220. In an implementation, the authentication circuit 264 provides encrypted AU / ID information 26 in response to the received AU / ID request 533. The encrypted AU / ID information 26 may include identification information of the manufacturer of the sensor. In an implementation, the manufacturer of the medical device 110 may provide or supply various hardware and / or software configuration options for the medical device 110. The AU / ID information may indicate compatibility between a specific medical device configuration and a specific accessory configuration.

[0091] In implementations, authentication failure may cause host processor 425 to, for example, at display 150 and / or at cable display 910 (e.g., as described with respect to Fig. 9AIn implementation, in response to a failed authentication, the state engine 428 may transition the SA-DI port 298 to the port closed state 49 and require detection of a disconnection of the data transmission cable 210 before enabling a subsequent port active state 47.

[0092] In implementation, the host 58 may determine whether the accessory 59 is a newly connected accessory or a reconnected accessory based on the AU / ID information. In an example of a usage scenario, a user may have a first accessory (e.g., a first sensor and a first data transmission cable) and a second accessory (e.g., a second sensor and a second data transmission cable). The user may connect the first accessory, disconnect the first accessory, and connect the second accessory to the same SA-DI port 298. Alternatively, the user may connect the first accessory, disconnect the first accessory, and reconnect the first accessory to the same SA-DI port 298. The first accessory may be an IBP sensor that is newly connected and then reconnected. The host 58 may recognize the AU / ID information when reconnecting from the initial connection. Alternatively, the user may connect the first accessory, disconnect the first accessory, and connect the second accessory to the same SA-DI port 298. For example, the first accessory may be a newly connected IBP sensor, and the second accessory may include a newly connected temperature sensor. Based on the AU / ID information, the host may identify the second accessory as a new accessory that is different from the first accessory. In implementations, the authentication circuit 264 may send the AU / ID information in the AU / ID response 536 as encrypted AU / ID information 26 using the encryption engine 25 .

[0093] In implementations, if a connection of a particular sensor occurs after the medical device 110 is powered on (e.g., via the power on / off control 436) and after a specific power off duration (e.g., at least 30 seconds), the host 58 may identify the connection as a new connection. Additionally, if a connection of a particular sensor occurs after an indication of a new patient (e.g., via the new patient control 435), the host 58 may identify the connection as a new connection. The new connection corresponds to the first connection during a patient case. A patient case begins in response to powering on the medical device 110 after a specific power off duration and / or in response to a new patient indication. Similarly, a patient case ends in response to powering off the medical device 110 for a specific power off duration and / or in response to a new patient indication.

[0094] Upon completion of the AU / ID state 45 and in response to successful authentication, the host 58 may apply power to the SA-DI port 298 and apply sensor power 51 to the SA-DI port 298 to allow power transfer to the sensor 220. The state engine 428 may transition the SA-DI port 298 to the port active state 47. For example, the host processor 425 may authenticate the sensor 220 based on the encrypted AU / ID information 26 in the AU / ID response 536, and enable power to be provided to the data transmission cable 210 via the at least one power contact 399c and the power cable contact 395c based on the authentication.

[0095] In implementation, in the port active state 47, the host processor 425 may verify 53 the authentication. The host 58 may send a request 573 for sensor information from the SA-DI port 298 to the cable processor 265 via at least two communication contacts 399a and 399b and at least two communication cable contacts 395a and 395b. In implementation, the request 573 may include software and / or application programming interface (API) information used by the SA-DI port 298 and / or the host processor 425.

[0096] Accessory 59 (e.g., cable processor 265) receives request 573 from SA-DI port 298 at host 58 via communication signal 276 transmitted by isolation 270. In response, accessory 59 executes software stored in memory 266 to determine the requested sensor information and sends 579 the requested sensor information back to host 58 via communication signal 276 transmitted by isolation 270.

[0097] In an implementation, the unencrypted sensor information 21 includes one or more of sensor identification information (e.g., model, manufacturer, and / or serial number), software, and / or API information used by the data transmission cable 210. The sensor information can enable the host 58 to confirm compatibility with the accessory 59 and identify the data processing services required to process the sensor data before receiving the sensor data stream.

[0098] Upon receiving the unencrypted sensor information 21, the host processor 425 may compare the encrypted AU / ID information 26 received from the authentication circuit 264 with the unencrypted sensor information 21 from the cable processor 265. If the original manufacturing state of the data transmission cable 210 is intact, the unencrypted sensor information 21 will match the encrypted AU / ID information 26. However, if, for example, a malicious actor alters a third-party cable that is not authorized for use with the medical device 110 by adding the authentication circuit 264 and authentication wire / cable contacts from a data transmission cable 210 that is authorized for use with the medical device 110, the verification 53 will fail. In this case, the unencrypted sensor information 21 will not match the encrypted AU / ID information 26. In response, the host 58 may disable the SA-DI port 298 and transition back to the port closed state 49. In this way, the host 58 may prevent communication with a counterfeit or counterfeit data transmission cable.

[0099] If the encrypted AU / ID information 26 does not correspond to the unencrypted sensor information 21, the host 58 can disable sensor power 57 to the SA-DI port 298 and the data transfer cable 210. Conversely, if the encrypted AU / ID information 26 corresponds to the unencrypted sensor information 21, the host 58 can remain in the port active state 47 and enable data communication 55 between the host 58 and the accessory 59.

[0100] In implementation, during enabled data communication 55, the host 58 may send a request 583 for a sensor data stream via at least one SA-DI port 298 to the cable processor 265 of the accessory 59. In the port active state 47, the cable processor 265 may receive the power signal 274 transmitted by the isolation 270, and may receive the request 583 via the communication signal 276 transmitted by the isolation 270. In response to the request 583, the cable processor 265 may execute the software / API 23 stored in the memory 266 to format the sensor data into a data format unknown to the sensor according to the protocol of the SA-DI port 298. The cable processor may send 589 the sensor data stream in the sensor unknown format back to the host 58 via the communication signal 276 transmitted by the isolation 270.

[0101] In an implementation, before receiving and transmitting sensor data streams, host 58 may request accessory status and receive an accessory status response from cable processor 265. The accessory status response may include an indication of a fault, a current value of a timestamp and a serial number, a connection status with a patient, and / or a combination thereof. The timestamp may be a millisecond-based timestamp of reference port activity time 47 (i.e., when the port is activated, the time is initialized to zero). The serial number is a number associated with each message in a stream of data messages used for proper ordering and detection of missing data. The accessory status response may also include a hardware version number, a sensor manufacturing date, and / or a sensor expiration date.

[0102] In various implementations, the sensor data stream includes one or more of sensor parameter status data, digital data, and waveform data. The data stream may also provide data information, e.g., an update rate of a discrete numerical parameter or a sampling rate of a waveform parameter (e.g., messages / second, bits / sample, and samples / message). In an implementation, if host 58 fails to detect an active data stream within a predetermined period of time, host 58 may poll accessory 59 to determine whether accessory 59 is still operational.

[0103] In an implementation, medical device 110 may include a plurality of SA-DI ports 298 (e.g., 3 to 6, 3 to 10, 6 to 12 ports). Based on power delivery limitations, medical device 110 may limit the number L of activated SA-DI ports 298, where L < M. For example, medical device 110 may be configured to deliver a total amount of power P total to an aggregation group of SA-DI ports 298. Each sensor connected to SA-DI port 298 may require an amount of power P sensor,1 、P sensor,2 、…P sensor,N . The total number of SA-DI ports 298 provided by medical device 110 may be M ports. When sensors are connected to SA-DI ports 298, if the total required sensor power (P sensor,1 +P sensor,2 +…+P sensor,N ) exceeds the total amount of power P total (i.e., P sensor,1 +P sensor,2 +…+P sensor,N >P total ), then medical device 110 may limit the number of activated SA-DI ports 298 to a number L that is less than the total number M of SA-DI ports 298 provided by medical device 110 (i.e., L < M). The number L of activated ports depends on the power P required by each connected sensor sensor,N. Therefore, the maximum number of activated SA-DI ports 298 depends on the specific power requirements of each connected sensor 220. Therefore, the host processor 425 is configured to limit the number of sensor-unknown data interface ports that transmit power simultaneously to less than the total number of sensor-unknown data interface ports. The AU / ID information includes the specific power requirements of the connected sensor 220. Therefore, the medical device 110 can determine whether to activate a specific SA-DI port 298 using a connected sensor 220 based on the power requirements. Therefore, the host processor 425 is configured to limit the number of SA-DI ports 298 based on the AU / ID information.

[0104] In an implementation, in addition to or as an alternative to limiting the total number of activated SA-DI ports 298 based on total power requirements, the medical device 110 may also limit the total number of SA-DI ports 298 connected to a particular type of sensor. For example, the host processor 425 may be configured to limit the number of SA-DI ports 298 connected to an IBP sensor to three ports connected to an invasive blood pressure sensor. In an implementation, the host processor 425 may be configured to limit the number of SA-DI ports 298 connected to a particular type of sensor based on sensor priority. For example, an airway flow sensor and / or an invasive blood pressure sensor may have a higher priority than a temperature sensor.

[0105] In implementation, the software and / or API 23 stored in memory 266 is installed during manufacturing and updated via host 58. For example, as discussed above, accessory 59 provides version information to the software and / or API during validation of the data transfer cable.

[0106] refer to 7A to 7F , showing an example of a cable lighting configuration for a data transmission cable. The data transmission cable 210 can be coupled to a first sensor 720a or a second sensor 720b that is different from the first sensor. For example, the first sensor 720a can be a temperature sensor, and the second sensor 720b can be an IBP sensor. The data transmission cable 210 can include at least one lighting device 730 disposed on the cable. The lighting device 730 can be illuminated in a first color corresponding to the first sensor 720a (e.g., as indicated by Fig. 7A ) or in a second color corresponding to the second sensor 720b (e.g., as indicated by the cross-hatching in Figure 7B In this way, a caregiver can easily identify the type of sensor attached to the cable based on the color of the illumination. As an example without limiting the present invention, at least one illumination device 730 may include a light emitting diode (LED). In various implementations, at least one illumination device 730 may be, for example, Fig.7DThe band 740 is shown around the circumference of the data transmission cable 210, or may be provided circumferentially along the cable 210 750 (eg, Fig. 7E as shown) or radially 760 (as shown Figure 7F A series of two or more discrete devices arranged as shown).

[0107] refer to Figure 7C , the data transmission cable 210 may include a plurality of lighting devices arranged on the cable 230 and / or one or more of the electromechanical connectors 250 and 290. The plurality of lighting devices may have different assigned colors to indicate one or more of a power-on state, a power-off state, an authentication state, a sensor fault state, a sensor working state, a sensor type, a communication state, etc. The lighting device may indicate the sensor status information based on one or more of a color, a continuity of illumination (e.g., flashing or flashing continuously or at various rates), and the absence of illumination.

[0108] In an implementation, the lighting device 730 may provide infrared lighting. For example, the wavelength of the infrared lighting may be in the range of 900 to 1750 nm. The infrared lighting may provide advantages in a military environment by enabling identification of sensors, for example, using night vision goggles. In an implementation, the data transmission cable 210 may include a low light sensor 860 electrically coupled to at least one lighting device 730 and configured to disable the lighting in low light conditions.

[0109] refer to Figure 8 , showing an example of user input controlled cable lighting for a data transmission cable. In implementation, the lighting device 730 can be illuminated in response to voice input 830 from a caregiver 840 for the type of sensor 820 on the data transmission cable 210. For example, the data transmission cable 210 may include a microphone 810. The microphone can capture the voice input 830 and provide the voice input 830 to the processor 265. The processor 265 can recognize the sensor identification query from the voice input 830, verify the sensor type, and cause the lighting device 730 to illuminate in response to the voice input 830. In implementation, the device 730 can illuminate in a steady or strobe mode.

[0110] Alternatively or additionally, the illumination device 730 may illuminate in response to a user input to the medical device. For example, the medical device 110 may include a button and / or touch screen control 850 configured to accept a user query to identify the type of sensor on the data transmission cable. The host processor 425 may cause the illumination device 730 to illuminate in response to a user input at the medical device 110. In implementations, the data transmission cable 210 may include a button and / or touch screen control 850 configured to accept a user query to identify the type of sensor on the data transmission cable. Figure 7CThe host processor 425 may provide a signal to the lighting device 730 via the identification contact / line combination 795. In implementation, the host processor 425 may cause the lighting device 730 to illuminate in response to a user touch and / or other user input (e.g., a cursor or other selectable screen indicator) to the display 150 at at least one visual representation of the data from the sensor 220. Fig. 9A , showing an example of a data transmission cable with a cable user interface. In an implementation, the data transmission cable 210 may include a cable user interface 910. The user interface 910 may include a display configured for user input and / or output (e.g., caregiver feedback, caregiver prompts, sensor data display, etc.). The user interface 910 may be positioned or arranged along the cable 230 or at an electromechanical connector (e.g., connector 250 or 290). The user output may depend on the type of sensor coupled to the data transmission cable 210. For example, Fig. 9B A data transmission cable 210 is shown with an airway flow sensor 920 and an airway flow sensor user interface 925. The user interface 925 can provide bag-mask feedback for the user to administer ventilation according to a desired ventilation target (e.g., within a predetermined range (one or more) of ventilation tidal volume, ventilation rate, minute ventilation, etc.). As another example, Fig. 9C A data transmission cable 210 is shown with a CPR compression sensor 930 and a CPR compression sensor user interface 935 for a user to deliver chest compressions according to a desired chest compression target (e.g., within a predetermined range (one or more) of chest compression depth, chest compression rate, release rate, etc.). In some embodiments, as Fig. 9B and Fig. 9CAs shown, user interfaces 925, 935 can depict numerical values ​​​​of various ventilation / compression parameters. In addition or alternatively, if the ventilation and / or compression parameters are outside the desired target range, the user interfaces 925, 935 can provide instructive feedback to the user. For example, if the ventilation tidal volume is outside the desired target range, a portion of the user interface 925 can provide a visual indication of how much tidal volume the user should pay attention to administering to the patient (e.g., highlighting the numerical value indicating the tidal volume). Similarly, if the ventilation rate is outside the desired target range, a portion of the user interface 925 can provide a visual indication of how fast or slow the user should adjust the ventilation (e.g., highlighting the numerical value indicating the ventilation rate). In some embodiments, when the compression depth is outside the desired target range, the user interface 935 can indicate that the user should adjust the depth of the chest compression given (e.g., highlighting the numerical value indicating the compression depth). And when the compression rate falls outside the desired target range, the user interface 935 can similarly indicate that the user is outside the target range (e.g., highlighting the numerical value indicating the compression rate).

[0111] In implementations, the cable user interface 910 can provide user output for data other than data from the sensor 220 coupled to the data transmission cable. For example, the medical device 110 can provide data collected via other sensors to the cable user interface 910 to improve the medical care provided by the caregiver. For example, a cable user interface for a CPR compression sensor can provide vital sign data or bag-mask data that can assist the caregiver in performing a CPR response.

[0112] refer to Fig.10 and Fig.11 , a schematic diagram showing a removable sensor hub coupled to a medical device, respectively, inside and outside the medical device housing. The medical device 110 includes a housing 1020 (e.g., a first housing), a medical device display 150 (e.g., a first display) coupled to the housing 1020, a communication interface 1034 (e.g., a first communication interface), a processor 1036 (e.g., a first processor), a memory 1038 (e.g., a first memory), and associated circuitry. The processor 1036 and the memory 1038 are communicatively coupled to the display 150 and the communication interface 1034.

[0113] In implementations, the housing 1020 can include a sensor hub connector 1040. In various implementations, the sensor hub connector 1040 can be disposed within the housing 1020 (e.g., as shown in FIG. Fig.10 ), or may be arranged outside the housing 1020 (e.g., as Fig.11 on the outer surface as shown). Fig.12, the (one or more) sensor hub connectors 1040 disposed within the housing 1020 may, for example, form a receptacle 1047 configured to accept insertion of the sensor hub 1010 (e.g., as indicated by arrow 1299) and retain the sensor hub 1010 within the housing 1020. The receptacle 1047 is also configured to release (e.g., as indicated by arrow 1299) the sensor hub 1010 for removal from the medical device 110. Fig.13 , the (one or more) sensor hub connectors 1040 disposed on the exterior of the medical device 110 may include one or more of brackets, clips, clamps, magnets, receptacles, etc. configured to secure the sensor hub 1010 to the exterior of the housing 1020. The sensor hub 1010 may include one or more mating mechanisms 1045 configured to be removably coupled to the sensor hub connector 1040. In an implementation, the mating mechanism 1045 may be a profile on the sensor hub 1010.

[0114] In an implementation, the sensor hub connector 1040 can allow for wired electrical and / or communication coupling between the sensor hub 1010 and the medical device 110 via one or more contacts 1070a and 1070b. In an implementation, the contacts 1070b (e.g., one or more first electrical contacts) can be disposed on the sensor hub 1010, and the contacts 1070a (e.g., one or more second electrical contacts) can be disposed on the medical device 110. The sensor hub connector 1040 can hold the sensor hub 1010 in a position where the contacts contact each other. In an implementation, the sensor hub 1010 and the medical device 110 can communicate with each other via the wired connection 1080 when the sensor hub 1010 and the medical device 110 are physically coupled and / or decoupled. As shown in FIG. Fig.12 and Fig.13 As shown, in various implementations, the sensor hub 1010 can be configured to be communicatively coupled to one or more remote computing devices 1290 via a network connection 1295. The remote computing devices can include servers and other devices communicatively coupled via the server through the network 1295, such as personal computers, laptops, tablet computers, mobile devices, and / or other medical devices. In this way, the sensor hub 1010 can enable telemedicine and remote data viewing, analysis, storage, and / or sharing.

[0115] The sensor hub 1010 may include a housing 1012 (e.g., a second housing or a sensor hub housing). The housing 1012 may include one or more mating mechanisms 1045 configured to removably couple the sensor hub 1010 to the sensor hub connector 1040. The sensor hub 1010 also includes at least one DI port 1098 coupled to the housing 1012. The at least one DI port 1098 may be a SS-DI port (e.g., SS-DI ports 498a, 498b) or a SA-DI port (e.g., ports 298, 298a, 298b). The at least one DI port 1098 is configured to couple to a data transmission cable and a sensor (e.g., the data transmission cable 210 and the sensor 220 used by the SA-DI port), and is configured to receive sensor data. The sensor hub 1010 also includes a sensor hub processor 1050 (e.g., a second processor), a sensor hub memory 1052 (e.g., a second memory), and a sensor hub communication interface 1054 (e.g., a second communication interface). At least one DI port 1098 is communicatively coupled to the sensor hub processor 1050. The sensor hub processor 1050 is configured to receive sensor data via at least one DI port 1098 and send the sensor data to the sensor hub communication interface 1054. In an implementation, the sensor hub processor 1050 is configured to store the sensor data in the sensor hub memory 1052. In an implementation, the sensor hub 1010 includes at least one universal serial bus (USB) port. In an implementation, the sensor hub 1010 may also include a sensor hub power supply 1065. For example, the sensor hub power supply 1065 may include one or more batteries configured to provide power to the sensor hub 1010 independently of power provided to the sensor hub 1010 by the medical device 110. In an implementation, when the sensor hub 1010 is physically connected to the medical device 110 using the sensor hub connector 1040 (e.g., via the electrical contacts 1070a and 1070b), the one or more batteries may be recharged using power from the medical device 110.

[0116] The sensor hub communication interface 1054 is configured to communicatively couple to the medical device communication interface 1034 and send the sensor data to the medical device processor 1036 via the medical device communication interface 1034. The medical device processor 1036 is configured to control the medical device display 150 to display a visual representation (e.g., a first visual representation) of the sensor data obtained via the sensor hub to the user.

[0117] In an implementation, the sensor hub communication interface 1054 and the medical device communication interface 1034 are configured to communicate with each other via a wired and / or wireless communication coupling. Fig.10 and Fig.11 In an implementation, when the sensor hub 1010 is physically held by the sensor hub connector 1040, the communication interfaces 1054 and 1034 can communicate via a wired coupling (eg, via the contacts 1070a and 1070b and / or the cable 1080). Fig.12 and Fig.13 , when the sensor hub 1010 is decoupled from the sensor hub connector 1040, the communication interfaces 1054 and 1034 can communicate via the wireless coupling 1075. The sensor hub connector 1040 and the mating mechanism 1045 can be configured to physically couple the medical device 110 and the sensor hub 1010 such that the contacts 1070a and 1070b provide electrical connectivity and / or communication connectivity.

[0118] refer to Fig.14 , examples of various communication implementations of the sensor hub are shown. When the sensor hub 1010 and the medical device 110 are physically coupled or physically decoupled, the sensor hub 1010 can provide 1420 sensor data captured by the sensor hub 1010 to the medical device 110. Similarly, when the sensor hub 1010 and the medical device 110 are physically coupled or physically decoupled, the medical device 110 can provide 1425 sensor data captured by the medical device 110 to the sensor hub. As described above, the sensor hub 1010 and the medical device 110 can provide data to each other via the communicative coupling between the sensor hub communication interface 1054 and the medical device communication interface 1034. The data communication can be via a wired connection (e.g., contacts 1070a, 1070b and / or cable 1080) and / or via a wireless connection 1075. As Fig.14As schematically shown in , in an implementation, the medical device 110 is configured to associate sensor data of a first patient (e.g., patient A) received via the sensor hub 1010 with sensor data of the same patient (e.g., also patient A) received via the medical device. The medical device 110 is configured to associate sensor data of a second patient (e.g., patient B) received via the sensor hub 1010 with sensor data of the same patient (e.g., also patient B) received via the medical device. Similarly, in an implementation, the sensor hub 1010 is configured to associate sensor data of a first patient (e.g., patient A) received via the sensor hub 1010 with sensor data of the same patient (e.g., also patient A) received via the medical device. The sensor hub 1010 is configured to associate sensor data of a second patient (e.g., patient B) received via the sensor hub 1010 with sensor data of the same patient (e.g., also patient B) received via the medical device 110.

[0119] In implementations, the sensor hub 1010 and the medical device 110 may exchange authentication messages during the communicative coupling or to initiate the communicative coupling. In this manner, the two devices may verify that the sensor hub 1010 is recognized and compatible with the medical device 110. Additionally, authentication may include an exchange of information to verify that the medical device 110 and the sensor hub 1010 are associated with the same patient during patient treatment.

[0120] In various implementations, the sensor hub 1010 can be communicatively coupled to other computing devices via the network 1495. For example, the sensor hub 1010 can communicate with a remote server 1490 via the communication coupling 1430 and the sensor hub communication interface 1054. In an implementation, the remote server 1490 can be associated with a medical provider (e.g., a hospital, a physician's office, a medical records office, an emergency services office, an emergency services vehicle, a dispatch center, etc.). The communication coupling 1430 can exist in the absence of an existing communication coupling between the remote server 1490 and / or the network 1495 and the medical device 110. As another example, the sensor hub 1010 can communicate with the remote server 1490 via the communication coupling 1435 and the medical device 110. As yet another example, the sensor hub 1010 can communicate with one or more mobile and / or wearable computing devices 1412 via the communication coupling 1445. In the event that there is no existing communicative coupling between the mobile and / or wearable computing device(s) 1412 and the medical device 110, a communicative coupling 1445 may exist. The mobile and / or wearable computing device(s) 1412 may include one or more of a tablet, a smart phone, a watch, a heads-up display, a laptop computer, and combinations thereof.

[0121] In implementations, the sensor hub 1010 may communicate with (one or more) mobile and / or wearable computing devices 1412 via the communication coupling 1440 and the medical device 110. The sensor hub 1010 and / or the medical device 110 may communicate via a short-range wired or wireless coupling (e.g., The mobile and / or wearable computing devices 1412 may be communicatively coupled to the mobile and / or wearable computing devices 1412 (e.g., near field communication devices) or via a network 1495. The network 1495 may be a computer network (e.g., an Internet Protocol (IP) network, a cellular communication network, a satellite network, and combinations thereof). Communications between devices in proximity to each other (e.g., field devices) may be via a local area network, an ad hoc network, a mesh network, etc., and include coupling via radio frequency transmissions. Fig.14 Communications between devices in the may be encrypted and / or may include secure and / or authenticated communications.

[0122] As yet another example, the sensor hub 1010 can communicate with one or more medical devices 1414 other than the medical device 110 via a communication coupling 1446. The communication coupling 1446 can exist in the absence of an existing communication coupling between the medical device 1414 and the medical device 110. The medical device 1414 can include one or more of the following: a patient monitor, a defibrillator, a monitor / defibrillator, a wearable defibrillator, a compression delivery device, a ventilation device, a first aid kit, a compression monitor, an airway flow sensor, a bag-mask, and / or another medical device configured to monitor a patient and / or deliver therapy to a patient. In an implementation, the medical device 110 can be a first monitor / defibrillator, and the other medical devices 1414 can include a second monitor / defibrillator. In implementations, sensor hub 1010 may be configured to be communicatively coupled with only one monitor / defibrillator during treatment of a patient, but to be communicatively coupled with one or more monitor / defibrillators outside of ongoing patient treatment.

[0123] In an implementation, the sensor hub 1010 is configured to send one or more of the sensor data, the patient case file, the device readiness data, and the device status data to the Fig.14 Additionally or alternatively, the sensor hub 1010 is configured to receive one or more of the communicatively coupled devices shown. Fig.14 One or more of the communicatively coupled devices shown receive one or more of sensor data, software, software updates, settings, settings updates, protocols, and protocol updates.

[0124] refer to Fig.15 , a schematic diagram showing an example of a sensor hub. Fig.15 The features of the sensor hub 1010 shown are examples only and do not limit the present invention. In various implementations, the sensor hub 1010 may include one or more of these features. In addition, the number of features shown is only an example and does not limit the present invention.

[0125] In an implementation, the sensor hub 1010 may include one or more DI ports. The one or more DI ports include one or more SA-DI ports (e.g., ports 298a and 298b). Additionally or alternatively, the one or more DI ports may include one or more SS-DI ports (e.g., ports 498a and 498b) and / or one or more USB ports 1099. The sensor hub 1010 may be coupled to one or more sensors 1520 via one or more DI ports. Each sensor may be configured to be coupled to a SA-DI port and / or a SS-DI port. The SA-DI port may be coupled to the sensor via a data transmission cable 210. The SS-DI port may be coupled to the sensor via a cable compatible with the SS-DI port and the corresponding sensor. Sensor 1520 may include one or more of an ECG sensor, a pulse oximetry sensor, a capnography sensor, a heart rate sensor, an IBP sensor, a NIBP sensor, a temperature sensor, an airway flow sensor, a CPR compression sensor, an end-tidal carbon dioxide (e.g., EtCO2) sensor, a near infrared spectroscopy (NIRS) sensor, an ultrasound sensor, a spirometer, a pneumotachometer, a pressure sensor, and combinations thereof. Although Fig.15 The DI ports in the Fig.15 As shown, for simplicity, the DI ports can be configured with different shapes, types and numbers of electrical contacts, colors, etc. to differentiate between the DI ports in terms of usability and compatibility with sensor data and corresponding sensor cables.

[0126] refer to Fig.16 And further reference Fig.10 and Fig.11 , the medical device 110 may include one or more sensor hubs. Each sensor hub may include a sensor hardware control 1060 (e.g., Fig.10 and Fig.11 ). Sensor hardware controls 1060 may be customized for a particular sensor or sensor group. For example, Fig.16 The illustrated medical device 110a is an example of a medical device 110 that includes two sensor hubs 1010a and 1010b. Each sensor hub 1010a and 1010b may include sensor hardware controls 1060a and 1060b that are customized for one or more specific sensors configured to be coupled to the sensor hub via DI ports 1698a, 1698b, or 1698c, respectively. Fig.16The number of DI ports and sensors associated with the DI ports in the embodiment are merely examples and are not intended to limit the present invention. Each sensor hub 1010a and 1010b may include one or more DI ports. The display 150 may provide a visual representation of data from all sensor hubs coupled to the medical device 110a.

[0127] As an example, in an implementation, the sensor hub 1010a may include a hardware control 1060a for sidestream capnography. In addition, the sensor hub 1010a may be configured with two DI ports 1698a and 1698c. In an example, the DI port 1698a is connected to an SpO2 sensor, and the DI port 1698c may be connected to a capnography sensor. The DI ports 1698a and 1698c may be SA-DI ports with software / APIs suitable for sensor data from SpO2 and capnography. The DI port 1698b may be connected to an NIBP sensor, and the sensor hardware control 1060b may include a pneumatic pump system for NIBP. These modular sensor hubs may be independently maintainable and replaceable, and may enable manufacturers and customers to customize the medical device 110 for sensor capabilities and combinations according to specific customer needs.

[0128] Reference again Fig.15 , when the sensor hub 1010 is physically coupled to the medical device 110, the sensor hub 1010 can receive power from the medical device 110. For example, the sensor hub 1010 can receive power via the contacts 1070a, 1070b and / or the wired connection 1080 or via wireless power transmission from the medical device 110 and the sensor hub 1010. In an implementation, the sensor hub connector 1040 and the mating mechanism 1045 can provide power transmission from the medical device 110 to the sensor hub 1010. In addition to or as an alternative to power transmission from the medical device 110, the sensor hub 1010 can include a sensor hub power supply 1065, such as one or more batteries. The battery can provide power to the sensor hub 1010 when the sensor hub 1010 is physically coupled to the medical device 110, physically decoupled from the medical device 110, or both. The sensor hub may include a power control 1515 to power on / off the sensor hub when the sensor hub is physically decoupled from the medical device 110. In implementations, power to the sensor hub 1010 when the sensor hub 1010 is physically coupled to the medical device 110 may be provided via the power control 1515 and / or via the power control 436 used by the medical device 110 (e.g., Figure 4 shown).

[0129] In implementation, the sensor hub 1010 may include a user interface 1530. The user interface 1530 may include a display 1540 configured to provide (one or more) visual representations of data from (one or more) sensors 1520 in real time during ongoing patient care. The visual representation may provide the data as a graph and / or text data. The visual representation may include waveform data 1550. The waveform data 1550 may include, for example, but not limited to, ECG, pulse oximetry, and / or carbon dioxide markers. The visual representation may include discrete numerical data 1555. The discrete numerical data may include, for example, but not limited to, blood pressure (NIBP, IBP), heart rate, instantaneous pulse oximetry, and / or instantaneous capnography. Additionally or alternatively, the visual representation may include or provide caregiver feedback, for example, CPR feedback 1560 and / or ventilation feedback 1565. CPR feedback may include, for example, compression depth, compression rate, compression time, compression release, and / or perfusion performance. The display 1540 can provide CPR feedback in real time in units of compressions. Ventilation feedback can include, for example, gas volume, ventilation rate, ventilation quality, and / or ventilation time. In implementation, ventilation feedback can be bag-mask feedback. The visual representation can also include image data, such as but not limited to laryngoscopy and / or ultrasound images. The ultrasound image can include ultrasound images of the patient's tendons, muscles, joints, internal organs, bone structures, abdomen, and / or other components of the patient's heart, blood vessels, carotid arteries, and / or cardiovascular system. The visual representation can be part of a guided medical intervention such as a biopsy, tissue or fluid sample, and / or other diagnostic or invasive surgery.

[0130] The user interface 1530 may include (one or more) alarm controls 1570 and / or (one or more) data input controls 1580. In an implementation, the display 1540 may be a touch screen display configured to accept tactile input. The sensor hub may also include a speaker / microphone 1585 configured to receive audio input and provide audio output. In an implementation, the sensor hub 1010 may include at least one user input device port 1595. The (one or more) port 1595 may receive user input from a user input device such as a mouse, keyboard, remote control, tablet computer, smart phone, wearable device (e.g., headset, glasses, earphones, watch, etc.). The (one or more) port 1585 may be coupled to the (one or more) user input device via a wired or wireless connection. The sensor hub 1010 may also include a tactile output device 1590. The tactile output device 1590, display 1540, and / or speaker / microphone 1585 may provide user feedback, alerts, and / or confirmation of data input and / or sensor connection. The user interface 1530 may also include one or more soft key controls. In various implementations, the user interface 1530 may provide feedback and / or instructions as text, graphics, animation, video (e.g., real-time, streaming, or pre-recorded), chat, and / or text messages (e.g., via network 1495), or a combination thereof.

[0131] In an implementation, in response to sensor 1520 being connected or disconnected from sensor hub 1010, one or more of output devices 1590, 1540, and 1585 may provide a tactile signal, an audio signal, or a visual signal indicating the connection / disconnection and / or the type of sensor that was connected or disconnected.

[0132] refer to 17A to 17D , a schematic diagram showing an example of a respiratory distress (RD) hub. The RD hub is a respiratory distress system that includes a portable ventilator as well as ventilation sensors, sensor controls, and a ventilation data analysis engine. 17A to 17D The features of the RD hubs 1710, 1710a, 1710b, 1710c and 1710b shown are examples only and do not limit the present invention. In various implementations, the RD hub may include one or more than one of these features. In addition, the number of each feature shown is only an example and does not limit the present invention.

[0133] like Fig.17A As shown, RD hub 1710a is an example of a removable sensor hub 1010, 1010a, 1010b that can be coupled to the interior of the housing of the medical device 110 (e.g., as shown in FIG. Fig.10 , Fig.12 , Fig.14 and Fig.16). The RD hub 1710a can be inserted into or released from the interior of the housing (e.g., as shown by arrow 1299). Fig. 17B As shown, RD hub 1710b is an example of a removable sensor hub 1010 that can be coupled to the exterior of the housing of the medical device 110 (e.g., as shown in FIG. Fig.11 , Fig.13 , Fig.14 and Fig.15 As shown in Fig. 17C As shown, the RD hub 1710c is an example of a sensor hub 1710b used separately from the medical device 110. In addition, Fig.17D and Fig.17E The illustrated RD hub 1710 is a schematic diagram of an example of at least a portion of the components of any of the hubs 1710a, 1710b, and 1710c.

[0134] Fig.17A An example urgent care environment 1700 is shown that includes an RD hub 1710a coupled to the interior of a housing of a medical device 150. Similarly, Fig. 17B An urgent care environment 1701 is shown having an RD hub 1710b coupled to the exterior of a housing of a medical device 150, and Fig. 17C An acute care environment 1702 is shown with an RD hub 1710c operating independently of the medical device 110. When delivering mechanical ventilation, the RD hubs 1710a, 1710b, and / or 1710c may provide breathing gases to the patient 170 via a mechanical ventilator 1706 including a flow generator (such as a blower, turbine, or compressor or devices based thereon) and a gas delivery device including a patient circuit 1716 including a mask 1718. However, in some embodiments, ventilation may be provided via a cannula rather than via a mask 1718.

[0135] exist Fig.17A and Fig. 17B In the example shown, the medical device 150 and / or RD hub may include one or more of a pulse oximeter 1722 for measuring the patient's SpO2, a capnography sensor 1724 that may be used to measure EtCO2, a blood pressure sensor / monitor 1728, and may include various other components such as one or more flow sensors, pressure sensors, airway sensors, spirometers, or pneumotachometers, etc. Optionally, one or more of these sensors may be included in and / or coupled to one or more other sensor hubs 1010 as described above. The medical device 110 may also provide electrodes 1726 that may be used to provide electrotherapy to the patient 170. In Fig. 17CIn the example of , the RD hub 1710c may include one or more of a pulse oximeter 1722 for measuring patient SpO2, a capnography sensor 1724 that may be used to measure EtCO2, a blood pressure sensor / monitor 1728, and may include various other components such as one or more flow sensors, pressure sensors, airway sensors, spirometers or pneumotachometers, etc.

[0136] The RD hub (1710a, 1710b, and / or 1710c) may be coupled to a supplemental oxygen (O2) source. In various embodiments, the RD hub (1710a, 1710b, and / or 1710c) may be capable of supplying oxygen using the supplemental oxygen source in a plurality of different ways, or the RD hub (1710a, 1710b, and / or 1710c) may be capable of supplying oxygen in any of a number of different ways. In various embodiments, the manner in which oxygen is supplied may be determined without user selection, or may be selected by the user, and may or may not require user confirmation.

[0137] In some embodiments, a reservoir bag that allows entrainment of oxygen from an oxygen source may be used. For example, a user may adjust the flow rate of delivered oxygen based at least in part on the current SpO2 that may be monitored by one or more of the devices 1702, 1704, 1708. The medical device 110 or the RD hub (1710a, 1710b, and / or 1710c) may continuously monitor SpO2. In various embodiments, the current SpO2 may be displayed for viewing by the user via the medical device display 150 or the hub display 1540.

[0138] In some embodiments, the RD hub (1710a, 1710b, and / or 1710c) includes and uses a variable output regulating valve 1740, wherein the oxygen output rate allowed or facilitated by the variable output regulating valve 1740 can be varied and changed to a specific oxygen flow rate in a range of possible oxygen flow rates. The variable output regulating valve 1740 can be used to provide a variable and controllable oxygen flow rate for the gas provided by the RD hub (1710a, 1710b, and / or 1710c) during the provision of mechanical ventilation. In implementation, for example, the variable output regulating valve 1740 can be attached to the gas inlet of the RD hub (1710a, 1710b, and / or 1710c), the high pressure oxygen source, and can be attached to the medical device 110 (to monitor SpO2).

[0139] In some embodiments, the variable output regulating valve 1740 can be controlled automatically or without user interaction. For example, this can be based at least in part on the patient's continuously monitored SpO2 and can be set or adjusted according to the inspired oxygen concentration (FiO2) that can be determined at least in part based on the current SpO2. In some embodiments, the arrangement can be used to provide a closed-loop control (CLC) of FiO2 (FiO2 CLC). In some embodiments, a portable oxygen concentrator (POC) can be used. FiO2CLC can be used to control and adjust the output of the POC to entrain oxygen into the RD hub (1710a, 1710b and / or 1710c) for use in the gas delivered by the RD hub (1710a, 1710b and / or 1710c) during mechanical ventilation. In addition, in some embodiments including embodiments using the variable output regulating valve 1740 or POC, CLC (PEEPCLC) of positive end expiratory pressure (PEEP) can also be included in the control of the portable ventilator or RDM 1704. In some embodiments, the PEEP CLC may be based at least in part on a current inspired oxygen concentration (FiO2) setting and a current PEEP setting. In various embodiments, control using the FiO2 CLC and / or the PEEP CLC may be provided internally by the RD hub (1710a, 1710b, and / or 1710c) or by the medical device 110.

[0140] In some embodiments, the RD hub (1710a, 1710b and / or 1710c) can operate or can have one or more than one operation modes, which do not include or sometimes or during certain time periods do not include delivery mechanical ventilation. In addition, the RD hub (1710a, 1710b and / or 1710c) can include an operation or operation mode used outside an emergency care environment. For example, in some embodiments, the RD hub (1710a, 1710b and / or 1710c) can include a spirometer, which can be used for patient respiratory assessment outside an emergency care situation. For example, this assessment can be performed on a patient or individual who may not currently be receiving mechanical ventilation, may not need mechanical ventilation, and may not currently be experiencing RD. In some embodiments, such an assessment can include, for example, an assessment of the patient's respiratory parameters and respiratory status during a routine, scheduled or other doctor's office or medical facility or hospital. In addition, some assessments can be performed while the patient is lying, sitting or standing and during the patient is not experiencing RD.

[0141] The RD hub (1710a, 1710b, and / or 1710c) may include one or more pressure sensors and / or pneumotachometers 1730 that may be disposed within the patient circuit 1716 for sensing signals representative of gas flow within a gas delivery device of the RD hub (1710a, 1710b, and / or 1710c). In an implementation, for example, the one or more pressure sensors and / or pneumotachometers 1730 may be coupled to or part of one or more spirometers. In some embodiments, a controller (e.g., Fig.17D The controller 1705 shown in FIG. 1 receives a signal representing the gas flow. Based at least in part on the signal representing the gas flow, the controller can generate respiratory parameter data corresponding to at least one respiratory parameter of the patient, such as total compliance (Crs), total resistance (Rrs), volume control (VC), forced vital capacity (FVC), forced expiratory volume (FEV) (e.g., FEV1, FEF or FEF25-75, PEF, PEFR, MVV, etc.) at various timed ventilation intervals.

[0142] The controller may transmit or provide the received respiratory data to the medical device 110, such as for determining the patient's respiratory condition, etc. However, in some embodiments, the RD hub (1710a, 1710b, and / or 1710c) may determine or participate in determining the patient's respiratory condition.

[0143] In some embodiments, various aspects of the medical device system including the medical device 110 and the RD hub (1710a, 1710b and / or 1710c), such as the allocation and integration of roles between devices and various aspects of specific devices, can be optimized based on factors such as the desired degree of portability or ease of operation of the RD hub (1710a, 1710b and / or 1710c). In an embodiment, the RD hub 1710c can communicate with the telemedicine device 110, and / or the telemedicine device or another computing device can provide remote control of the RD hub 1710c. Therefore, the allocation and integration of roles can occur via two-way communication between linked devices. In addition, aspects of each device can be optimized. These aspects can include, for example, a collection of controls, processing and memory aspects, software, algorithms, and context-sensitive guidance or clinical decision support related aspects. In some embodiments, various capabilities may be included in the RD hub (1710a, 1710b and / or 1710c), or included in one or more other devices or systems, or may be distributed or integrated between them. This may include, for example, a processor, memory, controller, or stored software or algorithm. These capabilities may, for example, be used to process signals, generate respiratory parameter data, or determine the respiratory condition of a patient. These capabilities may also be used to coordinate or integrate between devices. Thus, in this and other ways, the roles and processing capabilities and components of the RD hub (1710a, 1710b and / or 1710c) may be more or less, or at least partially determined or allocated based on the roles of one or more other devices in the environment. In some embodiments, reducing or limiting the roles, processing capabilities, or components of the RD hub (1710a, 1710b, and / or 1710c), for example, by allowing a reduced RDM size, weight, complexity, volume, occupied space, or noise during operation, etc., may increase or improve the portability or portable practicality of the RD hub. This, in turn, may allow for various implementations that may be balanced or optimized for specific anticipated or likely scenarios, which may increase positive, potentially life-saving patient outcomes.

[0144] Fig.17D 17 is a schematic diagram of an RD hub 1710. RD hub 1710 shows exemplary components of RD hubs 1710a, 1710b, and 1710c as described above. In addition, RD hub 1710 is as described above in Figures 10 to 16 An example of a sensor hub 1010 described in .

[0145] In implementation, the RD hub 1710 may be customized for a specific sensor (i.e., a respiratory distress sensor) as Fig.16. For example, the RD hub 1710 may include sensors that are configured or capable of sensing signals representing gas flow that can be used in determining at least one patient breathing parameter, such as may include the use of one or more pressure sensors 14, pneumotachometers or spirometers (which in some embodiments may be included as part of the mechanical ventilator 8 or included within the mechanical ventilator 8 or partially included within the mechanical ventilator 8), etc. In various implementations, one or more spirometers may be included within the RD hub 1710 and / or may be coupled to the RD hub 1710. Although depicted in a separate box from the patient circuit 13, it should be understood that the pressure sensor 14 and / or other components (such as a pneumotachometer or spirometer, etc.) may be included within the patient circuit 13 (such as a patient inspiratory circuit and / or a patient expiratory circuit, etc.) or partially included within the patient circuit 13. In some embodiments, the pressure sensor(s) 14 and other associated components may be used to sense or obtain respiratory parameter data, which may be used to determine or generate respiratory conditions (which may include associated data). The respiratory parameter data and respiratory condition data may also be used in conjunction with control of the operation of the RD Hub 1710, such as in control of mechanical ventilation provided by the RD Hub 1710, whether such control is provided internally by the RD Hub 1710, remotely, or in conjunction with aspects of both.

[0146] Alternatively, the RD hub 1710 may include a respiratory distress sensor, where the other sensors are not directly directed to a respiratory distress parameter indicator. For example, the RD hub 1710 may include the above-mentioned RD sensor and one or more of an ECG sensor, a heart rate sensor, an IBP sensor, a NIBP sensor, a temperature sensor, a CPR compression sensor, a near infrared spectroscopy (NIRS) sensor, an ultrasound sensor, and combinations thereof.

[0147] The RD hub 1710 includes a mechanical ventilation device 8 and includes at least one controller 1705. The controller 1705 includes at least one processor 20 (e.g., the sensor hub processor 1050 described above) and at least one memory 16 for storing data (e.g., the sensor hub memory 1052 described above), and may also include software that can be stored in the at least one memory 16. The controller 1705 of the RD hub 1710 is an example of the sensor hub 1010. As such, the controller 1705 may also include an RD hub communication interface 22 (e.g., the sensor hub communication interface 1054 described above), an RD hub hardware control 24 (e.g., the sensor hardware control 1060 described above), and an RD hub power supply 28 (e.g., the sensor hub power supply 1065 described above). The RD hub 1710 may include or be connected to an oxygen source 4.

[0148] refer to Fig.17E , showing an example of a mechanical ventilator used in a ventilation system. The mechanical ventilator 2740 may include a gas propeller 12 configured to move oxygen from an oxygen source 4 through an inspiratory circuit 2743 to a patient 101 via a patient interface 2744. The ventilation system 280 may use the gas propeller 12 to provide a range of therapeutic ventilation modes to provide various interventions. These various interventions may include: 1) non-invasive ventilation (NIV), including continuous positive airway pressure (CPAP) and bi-level ventilation (bi-level); 2) high flow nasal cannula (HFNC); 3) invasive ventilation (IV) using assist / control (AC), synchronized intermittent mandatory ventilation (SIMV), and pressure support (PS) modes; and 4) synchronized ventilation during cardiopulmonary resuscitation (CPR) mode.

[0149] The RD hub 1710 can provide ventilation during CPR and can operate, for example, when coupled and integrated with one or more critical care monitors (e.g., one or more patient monitors / (one or more) defibrillators 110, etc.). In some embodiments, for example, during mask ventilation, unprotected airway, the RD hub 1710 can deliver 2 breaths per 30 compressions as measured by the monitor. In some embodiments, for example, when the airway is protected (e.g., endotracheal tube, manifold, etc.), the RD hub 1710 can continuously deliver 10 breaths / minute (asynchronous) independent of the compression rate.

[0150] Patient interface 2744 may include appropriate gas delivery devices, such as cannula, mask, nasal cannula, etc. Mechanical ventilation device 2740 also includes expiratory circuit 2745 and expiratory valve 2748. Both the inspiratory circuit and the expiratory circuit include respiratory sensor 2747. Sensor 2747 may include, for example, but not limited to, respiratory rate meter, airway pressure sensor and spirometer. When providing mechanical respiratory assistance to the patient, sensor 2747 enables RD hub 1710 to measure the patient's respiratory effort and the performance of RD hub 1710. Sensor 2747 can generate and provide data (which includes but is not limited to flow rate, tidal volume and minute ventilation, respiratory mechanics (e.g., resistance and compliance) and vital capacity measurement), and may include, for example, forced vital capacity (FVC), forced vital capacity in 1 second (FEV1) and peak expiratory flow rate (PEF or PEFR). In addition, the medical device 110 may provide, for example, capnographic and / or oximetry data, such as oxyhemoglobin and carboxyhemoglobin saturation, as well as mainstream or other capnographic data, such as end-tidal CO2 (ETCO2), etc. This data may allow calculation of CO2 elimination rate and volumetric capnography, for example, by the RD hub 1710 and / or the medical device 110, which may include using flow data from the RD hub 1710.

[0151] In some embodiments, for patients requiring supplemental oxygen (O2), the RD hub 1710 can provide multiple methods to support oxygenation through invasive and non-invasive ventilation. For example, one method can include the use of a small reservoir bag system that allows entrainment from an O2 flow source. In some embodiments, in a first method, a user can manage O2 delivery to a patient while monitoring oxygen saturation (SpO2) measured by the medical device 110. A second method can utilize an innovative smart O2 valve (SOV) or module, which can be attached to an inspiratory circuit 2743, a high pressure O2 cylinder / source, and a medical device 110, for example. This can provide automatic control of the patient's oxygenation, for example using a physiological closed loop control (PCLC), wherein the SpO2 signal can be used to adjust the output of the SOV. A third method can provide functional integration of a portable O2 concentrator (POC), which can, for example, use a PCLC to adjust the O2 output of the POC and the O2 entrainment entering the RD hub 1710.

[0152] refer to Fig.17F, showing an example of a user interface for a ventilation system. In an implementation, the RD Hub 1710b or 1710cb or 1710b or 1710cc may include a display screen 2790. The display screen 2790 may display data generated by the RD Hub 1710b or 1710c and / or may include controls (e.g., soft keys 2799) for a user to adjust ventilation parameters. In an implementation, the display screen 2790 may also include one or more features of the display 1540 as discussed above.

[0153] Data generated by the RD hub 1710b or 1710c can be displayed at screen 2790 and / or transmitted or provided to the medical device 110 for display at screen 150, and can include, for example, ventilation settings, ventilation parameters, and / or respiratory physiological parameters collected by the RD hub 1710b or 1710c. For example, ventilation settings can include respiratory rate (breaths per minute (BPM)) 2712, inspiration:expiration ratio (i.e., the ratio of inspiration time to expiration time) 2713, tidal volume (volume of air delivered per breath) (Vt) 2710, positive end-expiratory pressure (PEEP), the pressure in the lungs above atmospheric pressure that exists at the end of exhalation 2709, peak inspiratory pressure (PIP) limit 13708, inspired oxygen concentration (FiO2) 2706, mode settings (e.g., assist / control (AC), synchronized intermittent mandatory ventilation (SIMV), continuous positive airway pressure (CPAP), bi-level (BL)) 2714, etc. The ventilation settings 2704, 2706, 2708, 2709, 2710, and 2712 / 2713 may each have a corresponding user input 2722a, 2722b, 2722c, 2722d, 2722e, 2722f, and 2722g on the ventilation system 280 for adjusting the respective settings 2704, 2706, 2708, 2709, 2710, and 2712 / 2713. The ventilation parameters may include, for example, inspiratory pressure data, expiratory pressure data, inspiratory flow data, expiratory flow data, leak detection, or other information measured from the RD hub 1710b or 1710c. Examples of respiratory physiological parameters may include non-continuous pulse oximeter (SpO2) measurements 2704, end-tidal CO2 (EtCO2) measurements, continuous SpO2 waveform data 2716, airway waveform data 2718, continuous CO2 waveform data, heart rate 2702, blood pressure, airway pressure data, airway flow data, spirometry data, etc.

[0154] In some examples, the RD hub 1710b or 1710c can be configured to generate an alarm signal (e.g., a visual and / or audible indication) when one or more parameter set points are exceeded. In one example, an alarm can be generated when the airway pressure exceeds the airway high pressure limit 2720. Display screens 2790 and / or 150 can provide these alarms.

[0155] In some embodiments, the alarms generated by the RD hub 1710b or 1710c may include patient safety alarms, such as high / low airway pressure, high / low tidal volume, high / low respiratory rate / apnea, PEEP leak, insufficient flow, spontaneous breathing-PIP high / low, spontaneous breathing-VT high / low, unmet patient inspiratory demand, auto-PEEP, patient disconnect, expiratory system failure / malfunction, calibration error, suspected trigger, tubing compliance failure, SpO2 sensor off / low / error, heart rate high / low, etc. The RD hub 1710b or 1710c may also generate environmental alarms, such as low battery, power failure, climate environment failure, oxygen supply failure, gas intake failure, etc. Self-test alarms may include internal communication errors, pneumatic system events, power system failures, pulse oximetry module failures, preventive maintenance alarms, etc. In some examples, when an alarm is generated, a pop-up message may be displayed at the RD hub interface 2790. Additionally, one or more alarm set points may be adjustable by the user at the RD hub interface 2790. For example, alarm set points for airway pressure high / low, tidal volume high / low, respiratory rate, spontaneous breathing, SpO2 low, and heart rate high / low may be manually adjusted by the device user. When an alarm signal is generated and / or when an alarm pop-up message is displayed at interface 2790, the user may take one or more actions to silence the alarm signal and / or acknowledge the alarm.

[0156] Screen interface 2790 may include controls for a user to adjust parameter settings and / or alarm set points at RD hub 1710b or 1710c. For example, interface 2790 may include user inputs corresponding to setting inputs 2722a to 2722g so that a user can adjust the values ​​of ventilation system settings 2704, 2706, 2708, 2709, 2710, 2712, and 2713. In some embodiments, user interface screen 2790 may also include a user input corresponding to a manual breath button / plateau pressure input 2728 that causes RD hub 1710b or 1710c to deliver a manual breath to a patient and / or measure a plateau pressure.

[0157] refer to Fig.18, schematically illustrates an example of components of a sensor data collection device 1810 (e.g., medical device 110, sensor hub 1010, and / or RD hub 1710, 1710a, 1710b, and / or 1710c). The device 1810 may include at least one processor 1820, at least one memory 1821, one or more output devices 1830, one or more user input devices 1844, and at least one communication interface 1845.

[0158] In various implementations, the medical device 110 can be a defibrillator, a patient monitor, a defibrillator / monitor, an automated compression device, a therapeutic cooling device, an extracorporeal membrane oxygenation (ECMO) device, a ventilation device, a combination thereof, or another type of medical device configured to be coupled to one or more therapy delivery components to provide therapy to a patient. In implementations, the medical device 110 can be a single housing (e.g., Fig.10 1020). The single housing can at least partially enclose the therapy delivery component and the monitoring component. In implementation, the medical device 110 can be a modular therapy delivery / monitoring device in which a patient therapy component in one unit is communicatively coupled to a patient detection unit without a therapy delivery component.

[0159] The medical device 110 can be, for example, a therapeutic medical device capable of delivering medical treatment. For example, the medical treatment can be electrotherapy (e.g., defibrillation, cardiac pacing, synchronized cardioversion, diaphragm or phrenic nerve stimulation), and the medical device 110 can be a defibrillator, a defibrillator / monitor, a mechanical ventilator (such as ZOLL Z-Vent, etc.), and / or another medical device configured to provide electrotherapy. As another example, the medical treatment can be chest compression therapy for treating cardiac arrest, and the medical device 110 can be a mechanical chest compression device such as a belt-based chest compression device or a piston-based chest compression device. As other examples, the medical treatment can be ventilation therapy, therapeutic cooling or other temperature management, invasive hemodynamic support therapy (e.g., extracorporeal membrane oxygenation (ECMO)), etc., and the medical device 110 can be a device configured to provide corresponding treatment. In implementation, the medical device 110 can be a combination of one or more of these examples. The therapeutic medical device can include patient monitoring capabilities via one or more sensors. These types of medical treatments and devices are merely examples and are not limiting of the present invention.

[0160] The patient interface device 1860 may include one or more therapy delivery components 1861a and / or one or more sensor devices 1861b. The therapy delivery component(s) 1861a are configured to deliver therapy to the patient and may be configured to be coupled to the patient. For example, the therapy delivery component(s) 1861a may include one or more of the following: electrotherapy electrodes including defibrillation electrodes and / or pacing electrodes, a chest compression device (e.g., one or more belts or pistons), a ventilation device (e.g., a mask and / or a tube), a drug delivery device, etc. The medical device 110 may include one or more therapy delivery components 1861a and / or may be configured to be coupled to one or more therapy delivery components 1861a to provide medical therapy to the patient. The therapy delivery component(s) 1861a may be configured to be coupled to the patient 170. For example, a caregiver 180 may attach electrodes to a patient 170, and a medical device 110 (e.g., a defibrillator or a defibrillator / patient monitor) may provide electrical therapy to the patient 170 via the defibrillation electrodes. These examples are not limitations of the present invention, as other types of medical devices, therapy delivery components, sensors, and therapies are also within the scope of the present invention.

[0161] The device 1810 may include, incorporate and / or be configured to be coupled to one or more sensors 161b (e.g., (one or more) sensors 220 and 1520), which may be configured to be coupled to the patient 170. (One or more) sensors 161b are configured to provide a signal indicating sensor data to the device 1810. (One or more) sensors 1861b may be configured to be coupled to the patient. For example, (one or more) sensors 1861b may include cardiac sensing electrodes, chest compression sensors, and / or ventilation sensors. The cardiac sensing electrodes may be conductive and / or capacitive electrodes configured to measure changes in the electrophysiology of the patient to measure the ECG information of the patient. The sensing electrodes may also measure the transthoracic impedance and / or heart rate of the patient. The one or more sensors 1861b may generate a signal indicating a physiological parameter of the patient 170. For example, the physiological parameters may include one or more of the following: at least one vital sign, ECG, blood pressure, heart rate, pulse oximetry, respiratory rate, heart sounds, lung sounds, breath sounds, end-tidal CO2, muscle oxygen saturation (SMO2), arterial oxygen saturation (SpO2), cerebral blood flow, electroencephalogram (EEG) signals, brain oxygen levels, tissue pH, tissue fluid levels, physical parameters as determined via ultrasound images, parameters determined via near infrared reflectance spectroscopy, respiration and / or cardiomyography, etc. The ultrasound image may include an ultrasound image of the patient's heart, carotid arteries, and / or other components of the cardiovascular system. Additionally or alternatively, one or more sensors 1861b may generate signals indicating chest compression parameters, ventilation parameters, drug delivery parameters, fluid delivery parameters, etc.

[0162] In addition to delivering therapy to the patient, (one or more than one) therapy delivery components 1861a may include, be coupled to and / or function as sensors, and provide signals indicating sensor data to the device 1810. For example, the defibrillation electrodes may be configured as cardiac sensing electrodes as well as electrotherapy delivery devices, and may provide signals indicating transthoracic impedance, electrocardiogram (ECG), heart rate, and / or other physiological parameters. As another example, the therapeutic cooling device may be an intravenous cooling device. Such a cooling device may include an intravenous (IV) device as a therapy delivery component configured to deliver cooling therapy and sense the temperature of the patient. For example, the IV device may be a catheter including saline balloons configured to adjust the patient's temperature via circulation of a temperature-controlled saline solution. In addition, the catheter may include a temperature probe configured to sense the patient's temperature. As yet another example, the IV device may provide therapy via drug delivery and / or fluid management. The IV device may also monitor and / or enable monitoring of the patient via blood sampling and / or venous pressure monitoring (e.g., central venous pressure (CVP) monitoring).

[0163] The device 1810 may be configured to receive sensor signals (e.g., from (one or more) therapy delivery components 1861a and / or (one or more) sensors 1861b) and process the sensor signals to determine and collect patient data. The patient data may include patient data that may characterize the patient's condition and / or condition (e.g., physiological data such as ECG, heart rate, respiratory rate, temperature, pulse oximetry, non-invasive hemoglobin parameters, capnography, blood oxygen saturation (SpO2), end-tidal carbon dioxide (EtCO2), invasive blood pressure (IBP), non-invasive blood pressure (NIBP), tissue pH, tissue oxygenation, near infrared spectroscopy (NIRS) measurements, etc.). Additionally or alternatively, the patient data may characterize the delivery of therapy (e.g., chest compression data such as compression depth, compression rate, etc.), and / or the patient data may characterize the condition and / or condition of a medical device used to treat the patient (e.g., device data such as shock time, shock duration, attachment of electrodes, power-on, etc.).

[0164] Components 1820, 1821, 1830, 1844, 1845, and 1855 of device 1810 are communicatively coupled to each other (directly and / or indirectly) for bidirectional communication. Fig.18 Although shown as separate entities in the device 1810, one or more of the components of the device 1810 may be combined into one or more discrete components and / or may be part of the processor 1820 respectively. The processor 1820 and the memory 1821 may include and / or be coupled to associated circuits to perform the functions described herein.

[0165] In an implementation, the device 1810 may be a medical device 110 configured to deliver a medical treatment to a patient 170. Thus, the medical device 110 may include a treatment delivery control module 1855. For example, the treatment delivery control module 1855 may be an electrotherapy delivery circuit that includes one or more capacitors configured to store electrical energy for a pacing pulse or a defibrillation pulse. The electrotherapy delivery circuit may also include a resistor, an additional capacitor, a relay and / or a switch, a bridge such as an H-bridge (e.g., including a plurality of insulated gate bipolar transistors or IGBTs), a voltage measurement component, and / or a current measurement component. As another example, the treatment delivery control module 1855 may be a compression device electromechanical controller configured to control a mechanical compression device. As yet another example, the treatment delivery control module 1855 may be an electromechanical controller configured to control drug delivery, temperature management, ventilation, and / or other types of treatment delivery. Alternatively, the medical device 110 may be configured to provide patient monitoring and / or diagnostic care without providing medical treatment.

[0166] One or more therapy delivery components 1861a may include electrotherapy electrodes (e.g., electrotherapy electrodes 166a), (one or more) ventilation devices (e.g., ventilation device 1866b), (one or more) intravenous devices (e.g., intravenous device 1866c), (one or more) compression devices (e.g., compression device 1866d), etc. For example, the electrotherapy electrodes may include defibrillation electrodes, pacing electrodes, and / or combinations thereof. The ventilation devices may include tubes, masks, abdominal and / or chest compressors (e.g., belts, chest plates, etc.), mechanical ventilators, etc., and combinations thereof. As an example, the mechanical ventilator may be a portable battery-powered ventilator. The intravenous devices may include drug delivery devices, fluid delivery devices, and combinations thereof. The compression devices may include mechanical compression devices such as abdominal compressors, chest compressors, belts, pistons, and combinations thereof. In various implementations, (one or more) therapy delivery components 1861a may be configured to provide sensor data and / or be coupled to and / or incorporated into sensors. For example, the electrotherapy electrodes can provide sensor data such as transthoracic impedance, ECG, heart rate, etc. In addition, the electrotherapy electrodes can include and / or be coupled to a chest compression sensor. As another example, the ventilation device can be coupled to and / or incorporate a flow sensor, a gas type sensor (e.g., an oxygen sensor, a carbon dioxide sensor, etc.), etc. As yet another example, the intravenous device can be coupled to and / or incorporate a temperature sensor, a flow sensor, a blood pressure sensor, etc. As yet another example, the compression device can be coupled to and / or incorporate a chest compression sensor, a patient position sensor, etc. The therapy delivery control module 1855 can be configured to couple to and control (one or more than one) therapy delivery component 1861a.

[0167] In various implementations, the sensor(s) 1861b may include one or more sensor devices configured to provide sensor data, such as, but not limited to, electrocardiogram (ECG), blood pressure, heart rate, pulse oximetry, respiratory rate, heart sounds, lung sounds, breath sounds, end-tidal CO2, muscle oxygen saturation (SMO2), arterial oxygen saturation (SpO2), cerebral blood flow, electroencephalogram (EEG) signals, brain oxygen levels, tissue pH, tissue fluid levels, images and / or videos via ultrasound, laryngoscopy and / or other medical imaging techniques, near infrared reflectance spectroscopy, respiration, cardiomyography, and / or patient movement. The images and / or videos may be two-dimensional or three-dimensional.

[0168] (One or more than one) sensor 1861b may include sensing electrodes, ventilation sensors, temperature sensors, chest compression sensors, etc. For example, the sensing electrodes may include cardiac sensing electrodes. The cardiac sensing electrodes may be conductive and / or capacitive electrodes configured to measure changes in the electrophysiological phenomena of the patient, such as measuring the ECG information of the patient. In implementation, the sensing electrodes may be configured to measure the transthoracic impedance and / or heart rate of the patient 170. The ventilation sensor may include a spirometry sensor, a flow sensor, a pressure sensor, an oxygen and / or carbon dioxide sensor (e.g., one or more of a pulse oximetry sensor, an oxygenation sensor (e.g., muscle oxygenation / pH), an O2 gas sensor, and a carbon dioxide recording sensor, etc.), and combinations thereof. The temperature sensor may include an infrared thermometer, a contact thermometer, a remote thermometer, a liquid crystal thermometer, a thermocouple, a thermistor, etc., and may measure the patient's temperature from the inside and / or from the outside. The chest compression sensor may include one or more motion sensors, which include, for example, one or more accelerometers, one or more force sensors, one or more magnetic sensors, one or more velocity sensors, one or more displacement sensors, etc. The chest compression sensor may be, for example, but not limited to, a compression ball, a smart phone, a handheld device, a wearable device, etc. The chest compression sensor may be configured to detect chest movement imparted by a rescuer and / or an automatic chest compression device (e.g., a belt system, a piston system, etc.). The chest compression sensor may provide a signal indicating chest compression data, which includes displacement data, velocity data, release velocity data, acceleration data, compression rate data, dwell time data, hold time data, blood flow data, blood pressure data, etc. In implementation, the sensing electrode and / or the electrotherapy electrode may include or be configured to be coupled to the chest compression sensor.

[0169] The patient data provided at the operation interface and / or the playback interface may include patient data provided via one or more treatment delivery components 1861a and / or one or more sensors 1861b. For example, the medical device 110 may process signals received from (one or more) treatment delivery components 1861a and / or (one or more) sensors 1861b to determine patient data.

[0170] In various implementations, device 1810 may be coupled to other computing devices (e.g., device 1412 or 1414). These other computing devices may be medical devices or computing devices suitable for medical use (e.g., personal computers, laptop computers, mobile devices, handheld devices, wireless devices, tablet computers, wearable devices (e.g., wrist-worn devices, head-worn devices, heads-up displays, etc.), or combinations thereof). Other medical devices 1414 may incorporate and / or be configured to couple to one or more patient interface devices substantially as described for patient interface device(s) 1860.

[0171] refer to Figure 2A , Figure 4 , Fig.10 and Fig.18 , as described herein, the processors (e.g., 265, 425, 1036, 1050, and 1820) are physical processors (i.e., one or more integrated circuits configured to perform operations specified by software and / or firmware stored in computer storage media on the respective devices (e.g., 110, 210, 410, 1010, 1810)), which are operably coupled to at least one memory device (e.g., 266, 426, 1038, 1052, and 1821), respectively. The processors may be intelligent hardware devices (e.g., but not limited to, central processing units (CPUs), graphics processing units (GPUs), one or more microprocessors, controllers or microcontrollers, application specific integrated circuits (ASICs), digital signal processors (DSPs), etc.), which are designed to perform the functions described herein and are operable to execute instructions on the respective devices. The processors may each be one or more processors, and may be implemented as a combination of hardware devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or another such configuration). Each of the processors may include multiple separate physical entities that may be distributed in cable 210 or devices 110, 1010, or 1810, respectively. Each of the processors is configured to execute a processor-readable, processor-executable software code that contains one or more instructions or codes for controlling the processor to perform the functions described herein. The processors may utilize various architectures, including but not limited to complex instruction set computer (CISC) processors, reduced instruction set computer (RISC) processors, or minimum instruction set computer (MISC) processors. In various implementations, each processor may be a single-threaded or multi-threaded processor. The processor may be, for example, but not limited to (one or more) or Itanium processor, (One or more) Athlon Processor, Motorola series processors, or ARM, Intel Pentium Mobile, Intel Core i5 Mobile, AMD A6 series, AMD Phenom IIQuad CoreMobile or similar devices.

[0172] Device 1810 may include a patient interface device signal processor 1856 . Patient interface device signal processor 1856 may include an A / D converter and other hardware configured to receive and process signals from one or more of patient interface devices 1860 .

[0173] Memory (e.g., memory 266, 426, 1038, 1052, and 1821) generally refers to computer storage media, which includes, but is not limited to, RAM, ROM, FLASH, disk drives, fuse devices, and portable storage media such as universal serial bus (USB) flash drives. Each memory may include, for example, random access memory (RAM) or (one or more) another dynamic storage device, and may include read-only memory (ROM) or (one or more) another static storage device (such as a programmable read-only memory (PROM) chip for storing static information (such as instructions for coupling a processor, etc.). Each memory may include a USB flash drive, which may store an operating system and other applications. A USB flash drive may include input / output components, such as a wireless transmitter and / or a USB connector that can be inserted into a USB port of another computing device. Each memory may be long-term and / or short-term, and is not limited to a specific type of memory or a specific amount of memory, or a type of medium in which the memory is stored. Each memory includes (one or more) non-transitory processor-readable storage media storing processor-readable, processor-executable software code. Each memory can store information and instructions. For example, each memory can include flash memory, and / or another storage medium including removable or dedicated memory in a mobile or portable device can be used. As another example, a memory such as The memories may include, for example, removable storage media such as an external hard drive, a floppy drive, a flash drive, a zip drive, a compact disk-read only memory (CD-ROM), a compact disk-rewritable (CD-RW), or a digital video disk-read only memory (DVD-ROM).

[0174] The communication interface 1845 can transmit and / or receive information relative to one or more devices that are external to the device 1810 and communicatively coupled to the device 1810. The communication interface 1845 can transmit and / or receive information via wired and / or wireless communication coupling. The information may include information stored in at least one of the above-mentioned memories. The information may include, for example, but is not limited to resuscitation treatment information, physiological information, patient information, rescuer and / or caregiver information, location information, rescue and / or medical treatment center information, etc. The communication interface 1845 can implement short-range and / or long-range wireless communication capabilities, which may include communication via near-field communication, Wi-Fi, (one or more) satellites, radio waves, computer networks (e.g., the Internet), cellular networks, etc. The communication interface 1845 can enable communication via a network such as a local area network (LAN), a wide area network (WAN), a mesh network, an ad hoc network, or another network. The communication interface 1845 may include, for example, an RS-232 port for a modem-based dial-up connection, a copper or fiber 10 / 100 / 1000 Ethernet port, or a Or WiFi interface.

[0175] In implementations, the communication interface 1845 may allow for communication with one or more other computing or medical devices. The communication interface 1845 may be as described above with respect to Fig.10 and Fig.11 The communication interface 1034 or 1054.

[0176] (One or more) output devices 1830 and (one or more) user input devices 1844 may be included in the device 1810 and / or coupled to the device 1810. (One or more) output devices 1830 may include one or more of a display, a speaker, and a tactile device. The display may be a display screen. The medical device 110 may provide at least one first display screen, and the sensor hub 1010 may provide at least one second display screen. The display may provide a graphical user interface (GUI). The display may be, for example, but not limited to, a liquid crystal display (LCD) and / or a light emitting diode (LED) display. In implementation, (one or more) output devices 1830 may be (one or more) input / output devices capable of capturing user input. For example, the display (e.g., 150 and / or 1540) may be a touch screen. The touch screen may be, for example, a pressure-sensitive touch screen or a capacitive touch screen. The touch screen may capture user input provided via touch screen gestures and / or provided via applying pressure to a specific area of ​​the screen. Examples of touch screen gestures that can implement user input may include pushing on the touch screen to apply pressure exceeding a certain threshold to indicate user input to a pressure-sensitive touch screen. The touch screen and the corresponding control processor may be configured to recognize touch screen gestures, which touch screen gestures include, for example, but are not limited to tapping, double-clicking, caliper gestures, dragging and dropping, sliding, pressing and dragging, holding and pressing, etc. In implementation, the processor 1820 may control the corresponding display to provide a visual representation of the data captured by the device 1810 and / or received at the device 1810. The visual representation may include a still image and / or a video image (e.g., an animated image).

[0177] In implementations, the output device(s) 1830 and / or the input device(s) 1844 may include, for example, wearable devices (such as heads-up displays mounted on glasses, masks, watches, etc.), and / or devices that may be integrated with other wearable communication devices (such as earbuds or Hands-free phone adapter, etc.). The processor 1820 can respectively control the output device 1830 to provide information to the user. The information can include feedback such as CPR feedback (e.g., visible feedback, audible feedback, tactile feedback, textual feedback, digital feedback, and graphical feedback).

[0178] The one or more user input devices 1844 may include, for example, a keyboard, a mouse, a joystick, a trackball, or other pointing device, a microphone, a camera, etc. In addition, the user input device 1844 may be a touch screen and / or another input / output device capable of providing information to a user and capturing information from a user. The touch screen may be a pressure-sensitive touch screen.

[0179] In an implementation, the user input device 1844 may be configured to capture, for example, information such as: patient medical history (e.g., medical record information including age, gender, weight, body mass index, family history of heart disease, cardiac diagnosis, co-morbidity, left ventricular ejection fraction, medications, prior medical treatments, and / or other physiological information), physical examination results, patient identity, caregiver identity, medical institution information, etc.

[0180] The processors, memories, communication interfaces, input and / or output devices and other components described above are intended to illustrate some types of possibilities. Since the foregoing examples are merely exemplary embodiments of these components, these examples should by no means limit the scope of the present invention.

[0181] Various modifications and additions may be made to the discussed exemplary embodiments without departing from the scope of the invention. For example, although the above-described embodiments relate to specific features, the scope of the invention also includes embodiments having different combinations of features and embodiments that do not include all of the described features. Therefore, the scope of the invention is intended to include all such alternatives, modifications and variations and all equivalents thereof that fall within the scope of the claims.

Claims

1. A data transmission cable for providing data communication between a sensor for collecting medical data and a sensor-unknown data interface port on a medical device, i.e., a sensor-unknown DI port, the data transmission cable comprising: A cable comprising an electrically conductive wire arranged in a continuous insulating sheath; A first electromechanical connector fixedly secured to a first end of the cable, the first electromechanical connector comprising: case, a first electrical fitting disposed within the housing at an open end of the housing and configured to be removably coupled to the sensor, A data interface circuit is arranged in the housing and electrically coupled to the first electrical fitting and the conductive line of the cable, the data interface circuit comprising: Cable storage, Cable processors, and an isolation device for limiting the flow of patient leakage current from the medical device to the sensor, the isolation device being configured to: transmitting power unidirectionally across the isolation barrier toward the cable processor, and transmitting communication signals bidirectionally across the isolation barrier; and A second electromechanical connector is fixedly secured to the second end of the cable, the second electromechanical connector including a cable contact electrically coupled to the conductive wires of the cable and configured to removably electromechanically couple the data transmission cable to the unknown DI port of the sensor.

2. The data transmission cable according to claim 1, wherein: The isolation device is configured to transmit an amount of power specific to the sensor across the isolation barrier.

3. The data transmission cable according to claim 2, wherein: The isolation device is configured to deliver 0.1 to 1 Watt.

4. The data transmission cable according to claim 1, wherein: The isolation device includes one of a dual capacitive isolation barrier device, a digital isolator device, and an optical isolator.

5. The data transmission cable according to claim 1, wherein: The cable contact includes at least: (a) at least two communication cable contacts, (b) at least one power cable contact, and (c) at least one grounding cable contact, Wherein, each of the cable contacts is electrically coupled to at least one of the conductive wires.

6. The data transmission cable according to claim 5, wherein: The cable contacts include at least one connection detection cable contact for electrically detecting a connection between the data transmission cable and an unknown DI port of the sensor.

7. The data transmission cable according to claim 5, wherein: The data interface circuit includes an authentication circuit, and wherein the cable contacts include at least one authentication cable contact.

8. The data transmission cable according to claim 7, wherein: The authentication circuit is configured to: In the absence of power transmission from the DI port unknown to the sensor to the data transmission cable, (a) receiving an authentication / identification request, i.e., an AU / ID request, via said at least one authentication cable contact, and (b) Sending AU / ID information in response to a received AU / ID request.

9. The data transmission cable according to claim 8, wherein: The authentication circuit is configured to include encrypted AU / ID information for the sensor in the AU / ID information.

10. The data transmission cable according to claim 9, wherein: The encrypted AU / ID information includes identification information of the manufacturer of the sensor.

11. The data transmission cable according to claim 1, wherein: The cable processor is configured to: receiving a request for sensor information from a DI port unknown to the sensor via a communication signal transmitted by the isolation device, the sensor information comprising an unencrypted authentication / identification request, i.e., unencrypted AU / ID information, stored in the cable memory, executing software stored in the cable memory to determine the requested sensor information, and The sensor information is sent to a DI port unknown to the sensor via a communication signal transmitted by the isolation device.

12. The data transmission cable according to claim 11, wherein: The cable processor is configured to: receiving a request for a sensor data stream from a DI port unknown to the sensor via a communication signal transmitted by the isolation device, executing software stored in the cable memory to format the sensor data into a data format unknown to the sensor according to a protocol of the DI port unknown to the sensor, and A sensor data stream in a data format unknown to the sensor is sent to the sensor unknown DI port via a communication signal transmitted by the isolation device.

13. The data transmission cable according to claim 1, wherein: The data interface circuit includes an analog-to-digital converter.

14. The data transmission cable of claim 1, comprising a noise shield between the isolation device and the cable processor.

15. The data transmission cable according to claim 1, comprising: At least one lighting device is disposed on the cable and is configured to illuminate in a color based on the type of the sensor.

16. The data transmission cable according to claim 15, wherein: The at least one lighting device comprises a light emitting diode, or LED.

17. The data transmission cable according to claim 16, wherein: The at least one lighting device comprises a band surrounding the circumference of the data transmission cable.

18. The data transmission cable of claim 15, comprising a microphone communicatively coupled to the cable processor and configured to capture voice input, wherein the cable processor is configured to cause the at least one lighting device to illuminate in response to the voice input.

19. The data transmission cable according to claim 18, wherein: The cable processor is configured to recognize a query from the voice input recognition sensor.

20. The data transmission cable according to claim 15, wherein The at least one illumination device provides infrared illumination.

21. The data transmission cable of claim 15, comprising a low light sensor electrically coupled to the at least one lighting device and configured to disable lighting in low light conditions.

22. The data transmission cable of claim 1, comprising a user interface display configured to provide caregiver feedback and disposed on a display housing positioned along the cable.

23. The data transmission cable according to claim 22, wherein: The caregiver feedback includes one or more of CPR chest compression feedback and bag-mask feedback.

24. The data transmission cable according to claim 1, wherein: The sensor is one of an invasive blood pressure sensor, a non-invasive blood pressure sensor, a temperature sensor, a pulse oximetry sensor, a capnography sensor, and an airway flow sensor.

25. The data transmission cable according to claim 1, wherein: The sensor is an ECG sensor.

26. A patient monitoring and treatment system for providing sensor data capture capability, the system comprising: A medical device comprising: monitor, at least one sensor-unknown data interface port, i.e., at least one sensor-unknown DI port, comprising a plurality of electrical contacts configured to allow power delivery to a sensor and data communication between the sensor and the medical device, host processor, memory, and associated circuitry; and A data transmission cable, comprising: a first electromechanical connector configured to detachably couple the data transmission cable to a DI port unknown to the at least one sensor, and a second electromechanical connector configured to be detachably coupled to the sensor and comprising: a plurality of cable contacts, each cable contact being configured to removably mate with a corresponding contact of the plurality of electrical contacts, Cable storage, a cable processor configured to execute software stored in the cable memory to format the sensor data into a sensor-unknown data format according to a protocol of the at least one sensor-unknown DI port, an authentication circuit configured to provide encrypted authentication / identification information for the sensor, i.e., encrypted AU / ID information, to the medical device, and a cable isolation device for limiting the flow of patient leakage current from the medical device to the sensor, the cable isolation device being configured to electrically isolate the authentication circuit from the cable processor and the cable memory, Wherein the display is configured to provide at least one visual representation of the sensor data.

27. The system of claim 26, wherein: The at least one sensor unknown DI port does not include an isolation device for limiting the flow of patient leakage current from the medical device to the sensor.

28. The system of claim 26, wherein: The plurality of electrical contacts comprises at least: (a) at least one authentication contact, (b) at least two communication contacts, (c) at least one power contact, and (d) At least one ground cable contact.

29. The system according to claim 28, in, The host processor is configured to send an AU / ID request via the at least one authentication contact, and Wherein the authentication circuit is configured to send encrypted AU / ID information in response to the received AU / ID request in the absence of power transmission from the DI port unknown to the at least one sensor to the data transmission cable.

30. The system of claim 29, wherein: The plurality of electrical contacts include at least one connection detection contact for electrically detecting connection and disconnection between the data transmission cable and a DI port unknown to the at least one sensor.

31. The system according to claim 30, in, The medical device includes a plurality of sensor unknown DI ports, and Wherein the host processor is configured to limit the number of sensor-unknown data interface ports that simultaneously transmit power to be less than the total number of sensor-unknown data interface ports.

32. The system of claim 31, wherein: The host processor is configured to limit a number of DI ports that are unknown to the sensor based on the encrypted AU / ID information.

33. The system of claim 31, wherein: The host processor is configured to limit the number of sensor unknown DI ports to the three ports connected to the invasive blood pressure sensors.

34. The system of claim 31, wherein: The host processor is configured to limit the number of DI ports for which the sensor is unknown based on the sensor priority.

35. The system of claim 34, wherein: The airway flow sensor and / or the invasive blood pressure sensor have higher priority than the temperature sensor.

36. The system of claim 30, wherein: In response to electrically detecting the disconnection, the host processor is configured to disable power provision to the data transfer cable from the DI port unknown to the at least one sensor.

37. The system of claim 29, wherein: The encrypted AU / ID information includes identification information of the manufacturer of the sensor.

38. The system of claim 29, wherein: The host processor is configured to: authenticating the sensor based on the encrypted AU / ID information, based on the authentication, enabling power provision to the data transmission cable via the at least one power contact, sending a request for a sensor data stream from a DI port unknown to the at least one sensor via the at least two communication contacts, and A sensor data stream is received in a sensor-unknown data format according to a protocol of the at least one sensor-unknown DI port.

39. The system of claim 38, wherein: The cable processor is configured to: receiving power from the medical device via a DI port unknown to the at least one sensor, receiving a request for the sensor data stream via a communication signal transmitted by the cable isolation device, executing software stored in the cable memory to format sensor data into a data format unknown to the sensor according to a protocol of the DI port unknown to the at least one sensor, and A sensor data stream in a data format unknown to the sensor is sent to the host processor via a communication signal transmitted by the cable isolation device.

40. The system of claim 38, wherein: The host processor is configured to: sending a request for sensor identification information from a DI port unknown to the at least one sensor via the at least two communication contacts, receiving unencrypted sensor identification information in response to the request, comparing the encrypted AU / ID information with the unencrypted sensor identification information, and If the encrypted AU / ID information corresponds to the unencrypted sensor identification information, the sensor data stream is requested and received, otherwise power supply to the data transmission cable is disabled.

41. The system according to claim 26, in, The data transmission cable includes at least one lighting device configured to illuminate in a color based on the type of the sensor, and The host processor is configured to cause the at least one lighting device to illuminate in response to user input.

42. The system of claim 41, wherein: The display is a touch screen display, and the host processor is configured to cause the at least one illumination device to illuminate in response to a user touch at the at least one visual representation of the sensor data.

43. The system of claim 26, wherein: The medical device includes a patient monitor / defibrillator.

Images