PATIENT MONITORING SYSTEM WITH NETWORK OF TREATMENT EQUIPMENT

• US 20170185732A1
• Filed: 12/29/2015
• Published: 06/29/2017
• Est. Priority Date: 12/29/2015
• Status: Abandoned Application

• Current Assignee: Cilag Gmbh International (Johnson & Johnson)
• Original Assignee: Ethicon Endo-Surgery, Inc. (Johnson & Johnson)
• Inventors: Bishop, Gregory D., Martin, James F., Mueller, Donn C., Krogh, Ross G., Niklewski, Paul J.
• Application Number:
  US14/982,185
• Publication Number:
  US 20170185732A1
• Time in Patent Office: Days
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: A61B 5/021 Measuring pressure in heart or blood vessels A61B5/0205 takes precedence
• CPC Class Codes: A61B 5/14542 for measuring blood gases A61B5/14551 takes precedence
• CPC Class Codes: A61B 5/4821 Determining level or depth of anaesthesia A61B5/1106 takes precedence
• CPC Class Codes: A61M 16/00 Devices for influencing the respiratory system of patients by gas treatment, e.g. mouth-to-mouth respiration; Tracheal tubes stimulating the respiratory movement by mechanical, pneumatic or electrical means, iron lungs combined with gas breathing means A61H31/00
• CPC Class Codes: A61M 2005/14208 with a programmable infusion control system, characterised by the infusion program
• CPC Class Codes: A61M 2205/14 Detection of the presence or absence of a tube, a connector or a container in an apparatus
• CPC Class Codes: A61M 2205/3553 remote, e.g. between patient's home and doctor's office
• CPC Class Codes: A61M 2205/3561 local, e.g. within room or hospital
• CPC Class Codes: A61M 2205/3584 using modem, internet or bluetooth
• CPC Class Codes: A61M 2205/502 User interfaces, e.g. screens or keyboards
• CPC Class Codes: A61M 2205/6072 Bar codes
• CPC Class Codes: A61M 5/142 Pressure infusion, e.g. using pumps
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

A patient preparing for a medical procedure is fitted with a modular connector device that stores patient data, medical procedure data, and other software. The patient connector can then be connected to other modular devices via wired or wireless means, allowing the other modular devices to access the patient connector storage to immediately identify the patient and determine its role within the medical procedure. The patient connector and each modular device may connect wirelessly to a localized network, allowing each device to communicate with each other or with a network server in order to receive updated information on a patient or medical procedure, or to download and configure new device drivers when two incompatible devices attempt to connect. In such a network, a patient may move seamlessly from room to room or from device to device without time consuming manual configurations.

Claims

1. An apparatus comprising:

(a) a device network server configured to store a set of device network data, the set of device network data comprising a patient identifier associated with a patient and a set of medical procedure data associated with a medical procedure to be performed on the patient;

(b) a patient connector comprising a memory and a first communication device, wherein the patient connector is configured to be located proximate to the patient; and

(c) a medical procedure device comprising a second communication device, wherein the medical procedure device is configured to be non-operable;

wherein the memory is configured to store a subset of device network data, the subset of device network data comprising the patient identifier;

wherein the patient connector is configured to send, via the first communication device, an identifying signal to the second communication device in response to a connection being established between the first communication device and the second communication device, wherein the identifying signal comprises the subset of device network data;

wherein the second communication device is configured to receive the identifying signal;

wherein the medical procedure device is configured to be operable based upon receiving the identifying signal via the second communication device.

2. The apparatus of claim 1, wherein the first communication device and the second communication device each comprise one or more of:

(i) an RFID device,

(ii) a Bluetooth device,

(iii) a Wi-Fi device,

(iv) a barcode scanner, or

(v) a wired data connection device.

3. The apparatus of claim 1, wherein the patient connector further comprises one or more of:

(i) a patient monitor,

(ii) a drug delivery connector,

(iii) a medication delivered manually and recorded, or

(iv) a gas delivery connector; and

wherein the medical procedure device comprises one or more of;

(i) a bedside monitoring unit,

(ii) a medical procedure room unit, or

(iii) an automated responsiveness monitor.

4. The apparatus of claim 1, wherein the subset of device network data further comprises a set of medical procedure data, and wherein the medical procedure device is further configured to configure itself with a set of operational parameters based upon the set of medical procedure data.

5. The apparatus of claim 4, wherein the medical procedure device comprises a drug delivery device, and wherein the set of operational parameters comprise a safety shell control algorithm, and wherein the drug delivery device is configured to modify a drug delivery rate of a drug in response to the safety shell control algorithm.

6. The apparatus of claim 1, wherein the first communication device and the second communication device are configured to establish the connection automatically based upon proximity between the first communication device and the second communication device, and wherein the first communication device and the second communication device each comprise a wireless communication device.

7. The apparatus of claim 1, wherein the medical procedure device is further configured to request a set of medical procedure information from an interconnected device, wherein the patient identifier is included in the request, and wherein the interconnected comprises is one or more of:

(i) the device network server,

(ii) the patient connector, or

(iii) a second medical procedure device.

8. The apparatus of claim 1, wherein the subset of the set of device network data further comprises a set of user data, and wherein the medical procedure device is configured with a user profile, a set of user privileges, and a set of training record validations based upon the set of user data.

9. The apparatus of claim 1, wherein the subset of device network data further comprises a device driver, wherein the device driver is configured to allow the medical procedure device to function with a second medical procedure device.

10. The apparatus of claim 1, further comprising a second medical procedure device, wherein the second medical procedure device is in communication with the patient connector, and wherein the second medical procedure device is configured to communicate with the medical procedure device indirectly via the patient connector.

11. The apparatus of claim 1, wherein the device network server is in communication with a patient record server, wherein the patient record server contains a set of patient data associated with the patient identifier, and wherein the device network server is configured to:

(a) receive a first subset of patient data from the patient record server; and

(b) transmit a second subset of patient data to the patient record server.

12. A method comprising:

(a) configuring a patient connector to receive a set of device network data from a device network server, the set of device network data comprising a patient identifier;

(b) associating a patient with the patient connector, the patient connector comprising a memory and a first communication device;

(c) connecting the patient connector with a medical procedure device via the first communication device;

(d) sending the set of device network data to the medical procedure device via the patient connector; and

(e) configuring the medical procedure device to prepare itself for a medical procedure based upon the patient identifier.

13. The method of claim 12, wherein the set of device network data further comprises a set of medical procedure data, the method further comprising the step of configuring the medical procedure device to prepare itself with a set of operational parameters based upon the set of medical procedure data.

14. The method of claim 13, wherein the medical procedure device comprises a drug delivery device, and wherein the set of operational parameters comprise a safety shell control algorithm, and wherein the drug delivery device modifies a drug delivery rate of a drug in response to the safety shell control algorithm.

15. The method of claim 12, wherein connecting the patient connector with a medical procedure device comprises the steps of:

(i) determining that the patient connector is proximate to the medical procedure device based upon a wireless signal communicated between the patient connector and the medical procedure device, and

(ii) causing the patient connector to connect to the medical procedure device when they are proximate to each other.

16. The method of claim 12, wherein the set of device network data further comprises a device driver, wherein the device driver is configured to allow the medical procedure device to function with a second medical procedure device, the method further comprising the step of configuring the medical procedure device with the device driver.

17. The method of claim 12, further comprising the steps of:

(a) connecting the patient connector to a second medical procedure device;

(b) receiving a signal from the medical procedure device at the patient connector, the signal comprising an indication that the signal is intended for the second medical procedure device; and

(c) sending the signal, via the patient connector, to the second medical procedure device.

18. The method of claim 12, further comprising the steps of:

(a) determining that the medical procedure device is not configured with a set of critical data that is needed for the medical procedure, the set of critical data comprising one or more of a device driver, a set of medical procedure info, or a set of user info;

(b) configuring the medical procedure device to request the set of critical data from the device network server;

(c) configuring the medical procedure device to, in response to an indication that the set of critical data is not available from the device network server, request the set of critical data from a local storage of the medical procedure device; and

(d) configuring the medical procedure device to, in response to an indication that the set of critical data is not available from the local storage of the medical procedure device, request the set of critical data from a second medical procedure device.

19. An apparatus comprising:

(a) a patient connector comprising;

(i) a memory, wherein the memory is configured to store a patient identifier,

(ii) a data connector, and

(iii) a medical device connector;

(b) a pre medical procedure device comprising a pre medical procedure device connector, wherein the pre medical procedure device connector is adapted to couple with the medical device connector;

(c) a medical procedure room unit comprising a medical procedure room unit connector, wherein the medical procedure room unit connector is adapted to couple with the medical device connector; and

(d) a post medical procedure monitoring device comprising a monitor connector, wherein the monitor connector is adapted to couple with the medical device connector;

wherein the pre medical procedure device is configured to receive, via the data connector, the patient identifier when the medical device connector is coupled with the pre medical procedure device connector;

wherein the patient connector is configured to receive, from the pre medical procedure device, a set of pre medical procedure data associated with the patient identifier;

wherein the medical procedure room unit is configured to receive, via the data connector, the patient identifier and the set of pre medical procedure data when the medical device connector is coupled with the medical procedure room unit connector, wherein the medical procedure room unit is automatically configured for a medical procedure based upon the patient identifier and the set of pre medical procedure data;

wherein the patient connector is configured to receive, from the medical procedure room unit, a set of medical procedure data associated with the patient identifier; and

wherein the post medical procedure monitoring device is configured to receive, via the data connector, the patient identifier, the set of pre medical procedure data, and the set of medical procedure data when the medical device connector is coupled with the monitor connector, wherein the post medical procedure monitoring device is automatically configured for monitoring a patient based upon the patient identifier, the set of pre medical procedure data, and the set of medical procedure data.

20. The apparatus of claim 19, wherein the data connector and the medical device connector are combined into a single connector;

wherein the pre medical procedure device comprises two or more of;

(i) an arterial oxygen saturation monitor,

(ii) a non invasive blood pressure monitor,

(iii) an automated responsiveness monitor, or

(iv) a communication device connected to a medical record server;

wherein the medical procedure room unit comprises a drug delivery device and an oxygen delivery device; and

wherein the memory comprises a removable digital memory card.