US20230009417A1 - Drug library dynamic version management - Google Patents
Drug library dynamic version management Download PDFInfo
- Publication number
- US20230009417A1 US20230009417A1 US17/929,654 US202217929654A US2023009417A1 US 20230009417 A1 US20230009417 A1 US 20230009417A1 US 202217929654 A US202217929654 A US 202217929654A US 2023009417 A1 US2023009417 A1 US 2023009417A1
- Authority
- US
- United States
- Prior art keywords
- data
- drug library
- medication
- infusion pump
- generalized
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 239000003814 drug Substances 0.000 title claims abstract description 671
- 229940079593 drug Drugs 0.000 title claims abstract description 670
- 238000001802 infusion Methods 0.000 claims abstract description 324
- 238000000034 method Methods 0.000 claims abstract description 73
- 238000002483 medication Methods 0.000 claims description 70
- 230000008859 change Effects 0.000 claims description 12
- 238000004891 communication Methods 0.000 claims description 12
- 230000004044 response Effects 0.000 claims description 7
- 230000008569 process Effects 0.000 abstract description 34
- 238000007726 management method Methods 0.000 description 32
- QPJBONAWFAURGB-UHFFFAOYSA-L Lobenzarit disodium Chemical compound [Na+].[Na+].[O-]C(=O)C1=CC=CC=C1NC1=CC(Cl)=CC=C1C([O-])=O QPJBONAWFAURGB-UHFFFAOYSA-L 0.000 description 27
- 238000012545 processing Methods 0.000 description 20
- 238000010586 diagram Methods 0.000 description 14
- 230000009466 transformation Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 8
- 230000008901 benefit Effects 0.000 description 6
- 238000004422 calculation algorithm Methods 0.000 description 6
- 238000012423 maintenance Methods 0.000 description 6
- 230000003993 interaction Effects 0.000 description 5
- 238000013479 data entry Methods 0.000 description 4
- 239000012530 fluid Substances 0.000 description 4
- 238000012384 transportation and delivery Methods 0.000 description 4
- 230000036541 health Effects 0.000 description 3
- 238000000844 transformation Methods 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 229960005205 prednisolone Drugs 0.000 description 2
- OIGNJSKKLXVSLS-VWUMJDOOSA-N prednisolone Chemical compound O=C1C=C[C@]2(C)[C@H]3[C@@H](O)C[C@](C)([C@@](CC4)(O)C(=O)CO)[C@@H]4[C@@H]3CCC2=C1 OIGNJSKKLXVSLS-VWUMJDOOSA-N 0.000 description 2
- 229960004618 prednisone Drugs 0.000 description 2
- XOFYZVNMUHMLCC-ZPOLXVRWSA-N prednisone Chemical compound O=C1C=C[C@]2(C)[C@H]3C(=O)C[C@](C)([C@@](CC4)(O)C(=O)CO)[C@@H]4[C@@H]3CCC2=C1 XOFYZVNMUHMLCC-ZPOLXVRWSA-N 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000012517 data analytics Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012377 drug delivery Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000003168 generic drug Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000002547 new drug Substances 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
- G16H20/17—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered via infusion or injection
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/142—Pressure infusion, e.g. using pumps
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/168—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body
- A61M5/172—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body electrical or electronic
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16C—COMPUTATIONAL CHEMISTRY; CHEMOINFORMATICS; COMPUTATIONAL MATERIALS SCIENCE
- G16C20/00—Chemoinformatics, i.e. ICT specially adapted for the handling of physicochemical or structural data of chemical particles, elements, compounds or mixtures
- G16C20/60—In silico combinatorial chemistry
- G16C20/62—Design of libraries
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/40—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H70/00—ICT specially adapted for the handling or processing of medical references
- G16H70/40—ICT specially adapted for the handling or processing of medical references relating to drugs, e.g. their side effects or intended usage
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/142—Pressure infusion, e.g. using pumps
- A61M2005/14208—Pressure infusion, e.g. using pumps with a programmable infusion control system, characterised by the infusion program
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/35—Communication
- A61M2205/3546—Range
- A61M2205/3553—Range remote, e.g. between patient's home and doctor's office
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/35—Communication
- A61M2205/3576—Communication with non implanted data transmission devices, e.g. using external transmitter or receiver
- A61M2205/3584—Communication with non implanted data transmission devices, e.g. using external transmitter or receiver using modem, internet or bluetooth
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/35—Communication
- A61M2205/3576—Communication with non implanted data transmission devices, e.g. using external transmitter or receiver
- A61M2205/3592—Communication with non implanted data transmission devices, e.g. using external transmitter or receiver using telemetric means, e.g. radio or optical transmission
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/50—General characteristics of the apparatus with microprocessors or computers
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/50—General characteristics of the apparatus with microprocessors or computers
- A61M2205/52—General characteristics of the apparatus with microprocessors or computers with memories providing a history of measured variating parameters of apparatus or patient
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/60—General characteristics of the apparatus with identification means
- A61M2205/6009—General characteristics of the apparatus with identification means for matching patient with his treatment, e.g. to improve transfusion security
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/168—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body
- A61M5/16804—Flow controllers
Definitions
- This disclosure relates to the field of clinical management, and particularly to systems and methods for efficient management of drug libraries in a networked clinical environment.
- Infusion pumps permit the controlled delivery of fluids to a patient and provide flexible yet controlled delivery schedules.
- Drug libraries within the infusion pumps provide some limits pertaining to the delivery of fluids.
- Infusion pumps can communicate with a server configured to manage drug library updates and operational software updates of the individual infusion pumps.
- Various techniques for managing drug libraries across a clinical environment and a cloud environment are described herein. These techniques may include creating and maintaining medication and administration data in a drug library database, using the data to create and maintain drug libraries, and distributing the drug libraries to various systems and components. For example, customized drug library data may be provided to infusion pumps for use in administration of medication, while generalized drug library data is proved to middleware, archives, etc. for use in system management, reporting, backup, etc. These and other embodiments are described in greater detail below with reference to FIGS. 1 - 10 . Although many of the examples are described in the context of a hospital environment including particular infusion pumps, data formats, and the like, the techniques described herein can be applied to other types of infusion pumps, data formats, etc.
- Some aspects of the present disclosure relate to a drug library management system that facilitates centralized management of the drug libraries that are used by various infusion pumps, including in clinical environments that have different types and/or versions of infusion pumps. Medications, administration rules, critical care area rules, and the like are maintained using the drug library management system, also referred to herein as the “drug library manager.”
- the drug library manager generates and distributes drug library data in pump-specific formats or other customized formats as needed. Therefore, different types and versions of infusion pumps, even those that use drug library data in different formats or that use different drug library data altogether, may be used in a clinical environment and managed using a single drug library management system.
- Additional aspects of the present disclosure relate to generating versions of drug library data that can be used by systems or components in the clinical environment other than infusion pumps.
- drug library data may be used by middleware systems, reporting systems, archival systems, and the like.
- the drug library management system may generate a version of drug library data that is standardized or otherwise generalized, in addition to a version that is customized for the specific infusion pump(s) that use the drug library data.
- the generalized version of the drug library data can be used by middleware systems that process messages received from various infusion pumps, reporting systems that report data generated by or otherwise associated with various infusion pumps, etc.
- the generalized version can be archived so that historical versions of the drug library data may be available when needed (e.g., for historical reporting, for troubleshooting problems with infusion pumps when a prior version of the drug library was used, etc.).
- the generalized version may be archived separately from the drug library database used by the drug library manager, and therefore the drug library database does not need to store historical drug library data.
- FIG. 1 is a block diagram of an example clinical environment and an example cloud environment according to some embodiments.
- FIG. 2 is a block diagram illustrating components of a clinical environment according to some embodiments.
- FIG. 3 is a schematic diagram illustrating components of an infusion pump and a connectivity adapter of a clinical environment according to some embodiments.
- FIG. 4 is a block diagram illustrating components of a cloud environment according to some embodiments.
- FIG. 5 is a block diagram of various data flows and interactions between a drug library manager, an end user device, an infusion pump, and various other system components during the creation and distribution of drug libraries according to some embodiments.
- FIG. 6 is a block diagram of illustrative components of a drug library according to some embodiments.
- FIG. 7 is a flow diagram of an illustrative process for managing the creation, maintenance, and distribution of drug libraries according to some embodiments.
- FIG. 8 is a user interface diagram of an illustrative interface for creating and maintaining medication and administration data according to some embodiments.
- FIG. 9 is a user interface diagram of an illustrative interface for creating and maintaining organizational information according to some embodiments.
- FIG. 10 is a block diagram of various data flows and interactions between drug library manager, an infusion pump, and various other system components during the use of drug libraries according to some embodiments.
- the present disclosure is directed to management and use of drug libraries in a networked clinical environment.
- the clinical environment may include various types and/or versions of infusion pumps.
- An infusion pump operates using a drug library that describes the medications available for administration, rules for administration of the medications, clinical care areas in which the pump may operate, and the like.
- Different types or versions of infusion pumps may be configured to use different formats of drug library data.
- Some aspects of the present disclosure relate to a drug library management system that facilitates centralized management of the drug libraries that are used by various infusion pumps, including in clinical environments that have different types and/or versions of infusion pumps. Medications, administration rules, critical care area rules, and the like are maintained using the drug library management system, also referred to herein as the “drug library manager.”
- the drug library manager generates and distributes drug library data in pump-specific formats or other customized formats as needed. Therefore, different types and versions of infusion pumps, even those that use drug library data in different formats or that use different drug library data altogether, may be used in a clinical environment and managed using a single drug library management system.
- Additional aspects of the present disclosure relate to generating versions of drug library data that can be used by systems or components in the clinical environment other than infusion pumps.
- drug library data may be used by middleware systems, reporting systems, archival systems, and the like.
- the drug library management system may generate a version of drug library data that is standardized or otherwise generalized, in addition to a version that is customized for the specific infusion pump(s) that use the drug library data.
- the generalized version of the drug library data can be used by middleware systems that process messages received from various infusion pumps, reporting systems that report data generated by or otherwise associated with various infusion pumps, etc.
- the generalized version can be archived so that historical versions of the drug library data may be available when needed (e.g., for historical reporting, for troubleshooting problems with infusion pumps when a prior version of the drug library was used, etc.).
- the generalized version may be archived separately from the drug library database used by the drug library manager, and therefore the drug library database does not need to store historical drug library data.
- FIG. 1 illustrates network environment 100 in which clinical environment 102 communicates with cloud environment 106 via network 104 .
- the clinical environment 102 may include one or more healthcare facilities (e.g., hospitals). The components of the clinical environment 102 are described in greater detail below with reference to FIG. 2 .
- the network 104 may be any wired network, wireless network, or combination thereof.
- the network 104 may be a personal area network, local area network, wide area network, over-the-air broadcast network (e.g., for radio or television), cable network, satellite network, cellular telephone network, or combination thereof.
- the network 104 may be a publicly accessible network of linked networks such as the Internet.
- the clinical environment 102 and the cloud environment 106 may each be implemented on one or more wired and/or wireless private networks, and the network 104 may be a public network (e.g., the Internet) via which the clinical environment 102 and the cloud environment 106 communicate with each other.
- the cloud environment 106 may be a cloud-based platform configured to communicate with multiple clinical environments.
- the cloud environment 106 may include a collection of services, which are delivered via the network 104 as web services. The components of the cloud environment 106 are described in greater detail below with reference to FIG. 4 .
- FIG. 2 illustrates the clinical environment 102 , which includes one or more clinical IT systems 202 , one or more infusion pumps 204 , and one or more connectivity adapters 206 . Further, the clinical environment 102 may be configured to provide cloud user interfaces 208 (e.g., generated and provided by the cloud environment 106 ).
- the clinical IT system 202 may include a hospital information system (HIS) designed to manage the facilities' operation, such as medical, administrative, financial, and legal issues and the corresponding processing of services.
- the HIS can include one or more electronic medical record (EMR) or electronic health record (EHR) systems, as well.
- EMR electronic medical record
- EHR electronic health record
- the infusion pump 204 is a medical device configured to deliver medication to a patient.
- the connectivity adapter 206 is a network component configured to communicate with other components of the clinical environment 102 and also communicate with the cloud environment 106 on behalf of the other components of the clinical environment 102 . In one embodiment, all messages communicated between the clinical environment 102 and the cloud environment 106 pass through the connectivity adapter 206 . In some cases, the connectivity adapter 206 is a network appliance with limited storage space (e.g., memory and/or persistent storage).
- the cloud user interfaces 208 may be provided to a user in the clinical environment 102 via a browser application, desktop application, mobile application, and the like. The user may access status reports and other data stored in the cloud environment 106 via the cloud user interfaces 208 .
- the components 202 - 208 illustrated in FIG. 2 may communicate with one or more of the other components in the clinical environment 102 .
- each of the clinical IT system 202 and the infusion pump 204 may communicate with the connectivity adapter 206 via physical local area network (LAN) and/or virtual LAN (VLAN).
- LAN local area network
- VLAN virtual LAN
- the clinical environment 102 may include other medical devices and non-medical devices that facilitate the operation of the clinical environment 102 .
- FIG. 3 illustrates the messages and data received, stored, and transmitted by the connectivity adapter 206 in the clinical environment 102 .
- the infusion pump 204 may include motor controller unit (MCU) 320 and communications engine (CE) 322 , and memory 324 storing drug library data 326 and operational software 328 .
- the drug library data 324 includes boundaries for drug delivery for various medications that can be delivered to patients by infusion pumps.
- the operational software 328 can include the operating system of the infusion pump 204 , as well as other software for performing various functions. Each type of infusion pump and even different versions of the same type of infusion pump may operate with a different operating system.
- the MCU 320 uses a less powerful processor (e.g., 12 MHz) and the CE 322 uses a more powerful processor (e.g., 400 MHz).
- the MCU 320 may generate and send pump messages to the CE 322 for storage and transmission to the connectivity adapter 206 .
- the pump messages may include clinical information.
- the CE 322 may send such pump messages to the connectivity adapter 206 .
- Pump messages sent to the connectivity adapter 206 via the CE 322 and generated by the MCU 320 may be transformed by the transformation worker 330 into a standardized dataset message (e.g., message format used by the connectivity adapter 206 to communicate with the cloud environment 106 , sometimes referred herein as simply a message).
- the transformation worker 330 may use drug library data 342 , described below, to transform a pump message into a standardized dataset message.
- the CE 322 may also receive messages from the connectivity adapter 206 indicating that updates, such as updates to the drug library or updates to the operational software are available and may send messages to the connectivity adapter 206 requesting the updates (e.g., update data).
- the CE 322 may also receive the update data from the connectivity adapter 206 for storage in the memory 324 .
- the update data may be drug library update data or may be operational software update data.
- the update data may be provided over a different communication channel than the communication channel(s) used to send or receive messages.
- the connectivity adapter 206 may include transformation worker 330 , device status manager 332 , cache 334 , an inbound queue 336 , an outbound queue 338 , and a data store 340 .
- the transformation worker 330 may transform the messages sent to the connectivity adapter 206 from the infusion pump 204 into the standardized dataset message.
- the transformation worker 330 may also transform messages sent from the connectivity adapter 206 to the infusion pump 204 into a message format usable by the infusion pump 204 .
- the inbound queue 336 receives and stores messages from the cloud environment 106 for processing by the connectivity adapter 206 .
- the inbound queue 332 may receive a drug library update message from the cloud environment 106 .
- the drug library update message may be notification that a drug library update is available for a least a portion of the infusion pumps 204 associated with the connectivity adapter 206 .
- the connectivity adapter 206 may comprise more than one inbound queue such that, for example, there is at least an inbound queue 336 for messages received from the cloud environment 106 over the network 104 and at least another inbound queue for messages received from one or more infusion pumps 204 over the local network.
- the messages stored in the inbound queue 336 may be associated with one or more sequence identifiers (IDs).
- IDs sequence identifiers
- the outbound queue 338 receives and stores messages to be sent from the connectivity adapter 206 .
- the outbound queue 338 may receive a drug library update message to be sent to one more infusion pumps over the local network.
- the drug library update message may be a notification to one or more infusion pumps 204 that a drug library update is available.
- the connectivity adapter 206 may comprise more than one outbound queue such that, for example, there is at least an outbound queue 338 for messages to be sent to the cloud environment 106 over the network 104 and at least another outbound queue for messages to be sent to one or more infusion pumps 204 over the local network.
- the messages stored in the outbound queue 338 may be associated with one or more sequence identifiers (IDs).
- IDs sequence identifiers
- the device status manager 332 receives the drug library and operational software updates from the cloud environment 106 and caches blocks of the update data in the cache 302 .
- the device status manager 332 processes the received messages from the inbound queue 336 and sends messages to the outbound queue 338 for transmission to the cloud environment 106 or to the infusion pumps 204 .
- the data received from the cloud environment 106 may be sent over a data channel associated with the network 104 and separate from the message channel of the network 104 . Because the data channel in the cloud environment is separate from the message channel in the cloud environment, the data transfer does not interfere with the clinical messaging from the connectivity adapter to the cloud environment.
- the data sent from the cache 302 to the infusion pumps 204 may be sent over a data channel associated with the local network and separate from the message channel associated with the local network. Because the data channel in the local network is separate from the message channel in the local network, the data transfer does not interfere with the clinical messaging from infusion pumps to the connectivity adapter. Thus, congestion on both the message channel of the cloud environment and the message channel of the local network is reduced.
- the device status manager 332 also processes transformed messages provided by the transformation worker 330 and merges the data included in the transformed messages into the cache 334 to update the current state of the infusion pump 204 stored in the cache 334 .
- the data store 340 may store, among other things, drug library data 342 .
- the drug library data 342 may be a generalized version of pump-specific drug library data that is stored on a pump 204 .
- the drug library data 342 may be used to process messages received from a pump 204 .
- the pump 204 may send a message to the connectivity adapter 206 regarding a drug infusion process that has been initiated on the pump 204 .
- the message may include a subset of information about the medication being infused or the infusion process, and the connectivity adapter 206 may derive information from the message.
- the message may include an identifier of the medication that is being infused, but the message may not include the name of the medication.
- the connectivity adapter 206 can access the drug library data 342 and obtain the name of the medication that corresponds to the identifier received from the pump.
- the message may include an identifier for a clinical care area, but the message may not include the name of the clinical care area.
- the connectivity adapter 206 can access the drug library data 342 and obtain the name of the medication that corresponds to the identifier of the clinical care area.
- the message may include a channel identifier for a particular channel of the infusion pump, a line identifier for a particular line of the infusion pump, an auto-program reference ID for a particular order number, other identifier information, some combination thereof, etc.
- the connectivity adapter 206 may determine a corresponding name, description, or other human-readable form from the message data using the drug library data 342 . The use of the drug library data 342 to process messaged received from an infusion pump 204 is described in greater detail below.
- FIG. 4 illustrates the cloud environment 106 , which includes drug library manager (DLM) 402 , report manager 404 , device manager 406 , data flow manager (DFM) 408 , cloud manager (CM) 410 , data analyzer (DA) 412 , a drug library database (DLDB) 414 , and a drug library archive 416 .
- DLM drug library manager
- DDM data flow manager
- CM cloud manager
- DA data analyzer
- DLDB drug library database
- DLDB drug library database
- the DLM 402 may provide a set of features and functions involved in the creation and management of drug libraries for use with infusion pumps, as described in greater detail below.
- the drug libraries may provide user-defined settings for pump configuration and drug infusion error reduction.
- the drug libraries may be used as part of a dose error reduction system (DERS).[0033]
- the report manager 404 may provide various reporting capabilities for clinically relevant infusion data which users can choose to use for further analysis, such as tracking and trending of clinical practices.
- the device manager 406 may oversee and manage the maintenance of infusion pumps, providing users the capability to view and manage asset and operational data. For example, the device manager 406 may schedule drug library and software updates for infusion pumps.
- the DFM 408 may facilitate storing, caching, and routing of data between compatible infusion pumps, compatible external systems, and the like.
- the DFM 408 may store infusion and operational data received from infusion pumps, store and cache infusion pump drug libraries and software images, convert and route network messaging between the cloud environment 106 and the clinical environment 102 , convert and route medication order information from a hospital information system to an infusion pump (e.g., auto-programming or smart-pump programming), and/or convert and route alert information and infusion events from infusion pumps to hospital information systems (e.g., alarm/alert forwarding, and auto-documentation, or infusion documentation).
- infusion pump e.g., auto-programming or smart-pump programming
- alert information and infusion events from infusion pumps to hospital information systems (e.g., alarm/alert forwarding, and auto-documentation, or infusion documentation).
- the CM 410 may serve as a general-purpose computing platform for the other modules illustrated in FIG. 4 .
- the CM 410 may be similar to Microsoft Windows or Linux operating systems as it provides the following services: networking, computation, user administration and security, storage, and monitoring.
- the DA 412 may provide data analytics tools for generating user interfaces and reports based on the data generated and/or received by the other modules illustrated in FIG. 4 .
- the DLDB 414 may store data regarding medications, medication administration rules, clinical care areas, and other data maintained and used by the drug library manager 402 to generate drug library data for infusion pumps and other systems or components.
- the drug library archive 416 may store generalized drug library data that has been generated by the drug library manager 402 .
- the drug library archive 416 may store a copy of every generalized drug library data set generated by the drug library management, or some subset thereof, for use in record keeping, reporting, etc. Use of archived generalized drug library data is described in greater detail below.
- the cloud environment 106 may provide other resources such as processors, memory, disk space, network, etc.
- the modules 402 - 412 may be hardware components configured to perform one or more of the techniques described herein. Alternatively, the modules 402 - 412 may be implemented using software instructions stored in physical storage and executed by one or more processors. Although illustrated as separate components, the modules 402 - 412 may be implemented as one or more hardware components (e.g., a single component, individual components, or any number of components), one or more software components (e.g., a single component, individual components, or any number of components), or any combination thereof.
- hardware components e.g., a single component, individual components, or any number of components
- software components e.g., a single component, individual components, or any number of components
- the cloud environment 106 can be implemented using a commercial cloud services provider (e.g., Amazon Web Services®, Microsoft Azure®, Google Cloud®, and the like). In other embodiments, the cloud environment 106 can be implemented using network infrastructure managed by the provider and/or developer of the modules 402 - 412 shown in FIG. 4 . In some embodiments, the features and services provided by one of more of the modules 402 - 412 may be implemented on one or more hardware computing devices as web services consumable via one or more communication networks. In further embodiments, one of more of the modules 402 - 412 are provided by one or more virtual machines implemented in a hosted computing environment. The hosted computing environment may include one or more rapidly provisioned and released computing resources, such as computing devices, networking devices, and/or storage devices
- FIG. 5 shows a network environment in which aspects of drug library management may be implemented.
- a DLM 402 may include a DLM editor 500 component.
- the DLM editor 500 may include executable instructions that generate a user interface 512 for display on an end-user computing device 510 .
- the DLM may include, or be associated with, a web server that generates web pages, sends the web pages to the end-user computing device 510 , and processes user inputs and interactions with the web pages.
- the DLM editor 500 may be used to manage data stored in the DLDB 414 , and to generate drug library data for use by various devices and systems, such as infusion pumps 204 A, 204 B, and the connectivity adapter 206 .
- the data to be stored in the DLDB 414 may include data regarding medications 506 , administration rules 508 regarding use of the medications 506 , clinical care areas (CCAs) 504 in which medications are used, and other data related to the management of drug libraries.
- CCAs clinical care areas
- the DLDB 414 may include data related to the management of all drug libraries associated with the cloud environment 106 . In other embodiments, the DLDB 414 may include data related to a subset of drug libraries associated with the cloud environment 106 (e.g., drug libraries for a particular clinical environment 102 or group of clinical environments, drug libraries for a particular customer or other entity, etc.). For example, there may be multiple DLDBs that are physically or logically separate from each other.
- Medications 506 are data entities that represent medications that can be administered via an infusion pump.
- a medication 506 data entity may include data regarding a name of a medication, an identifier of the medication (e.g., a unique identifier used by an HIS), an indication of whether the medication is a high-risk medication, and/or other information.
- Administration rules 508 are data entities that represent the parameters by which a medication may be administered.
- an administration rule 508 for a particular medication may include data representing various medication administration parameters such as a dosing unit, a clinical use, and/or other information.
- an administration rule 508 for a particular medication 506 may include medication administration parameter data regarding an absolute or “hard” minimum and/or maximum limit to the administration of the medication (e.g., minimum or maximum amount that may be administered overall or in a period of time, minimum or maximum rate at which the medication may be administered, etc.). Such hard limits typically cannot be overridden.
- the administration rule 508 may also or alternatively include data regarding a recommended or “soft” minimum and/or maximum limit to administration of the medication.
- Such soft limits may be overridden (e.g., by users with the proper level of authority, after generation of an alert such as an audible and/or visual notification, etc.).
- administration rules 508 for a single medication 506 .
- different administration rules 508 may be separately maintained for different clinical uses of the same medication 506 , different infusion pumps 204 through which the medication is to be administered, and/or different CCAs 504 in which the medication is to be administered.
- a medication 506 may be associated with zero or more administration rules 508 .
- an administration rule may only be associated with a single medication 506 .
- CCAs 504 are data entities that represent organizational units of health care enterprises. For example, CCAs may represent hospitals, individual hospital facilities, departments, or lines of care. In some embodiments, a CCA corresponds to a unit of similar clinical uses, patient types, other characteristics, some combination thereof, etc. CCAs 504 may be associated with various medications 506 and administrative rules 508 .
- FIG. 6 shows an example of a medication 506 A associated with multiple administration rules 508 A and 508 B.
- the administration rules 508 A and 508 B are associated with different CCAs 504 A and 504 B respectively.
- CCA 504 A may correspond to a pediatric unit of a hospital
- CCA 504 B may correspond to an ICU of the hospital.
- the pediatric CCA 504 A and ICU 504 B may each have various data elements, any or all of which may correspond to medication administration settings.
- pediatric CCA 504 A may include a data element specifying a maximum dose rate of 200 mL/hr.
- ICU CCA 504 B may include a data element specifying a maximum dose rate of 999 mL/hr.
- Pediatric CCA 504 A may be associated with an administration rule 508 A for medication 506 A, and that administration rule 508 A is more restrictive (e.g., smaller maximum doses) than the administration rule 506 B—for the same medication 506 A—that is associated with ICU CCA 504 B, which is for an adult population.
- settings for the pediatric CCA 504 A may prevent or override a less restrictive administration rule 508 A when the medication 506 A is used within the pediatric CCA 504 A.
- the administration rule 508 A for the medication 506 A is more restrictive than a setting of the pediatric CCA 504 A, the setting of the CCA 504 A will not override the administration rule 508 A.
- a user may use the DLM editor 500 to organize medications, administration rules, and CCAs into drug libraries that are distributed to infusion pumps and other system components.
- the organizational mechanism may be referred to as a worksheet 502 .
- a worksheet 502 is a dataset that includes references to the individual medications and administration rules to be made available to infusion pumps.
- the worksheet 502 can be directed to a particular infusion pump 204 or group of infusion pumps 204 that share the same customized drug library data format. Rather than providing data to the infusion pump 204 regarding every medication 506 and administration rule 508 available in the DLDB 414 , a worksheet 502 may be used to specify a subset of medications 506 and administration rules 508 .
- a CCA 504 may be added to a worksheet 502 , and all of the medications 506 and administration rules 508 associated with the CCA 504 and the target infusion pump 204 are automatically added.
- individual medications may optionally be added to a worksheet separately from any CCA that may be added.
- the worksheet 502 dataset may be stored in the DLDB 414 .
- the worksheet 502 dataset may include data representing various properties of the worksheet, such as a name, infusion pump type and/or version targeted by the worksheet, creator of the worksheet, creation and/or edit date, approval status, version, and the like.
- the worksheet 502 dataset may include a collection of pointers or other references to the data entities representing the various CCAs, medications, and administration rules that are associated with the worksheet 502 . Creation of worksheets 502 and other associated operations are discussed in greater detail below.
- the DLM editor 500 or some other component of the DLM 402 can generate drug library data using a worksheet 502 .
- the worksheet 502 may be in a “pending” status, awaiting approval.
- the DLM 402 can generate customized drug library data 520 that represents the CCAs, medications, administration rules, and other data in the format that is required for operation of the target pump 204 .
- the DLM 402 can generate generalized drug library data 522 for use by a middleware component such as the connectivity adapter 206 , for reporting and archival purposes, etc.
- the DLM 402 can send the customized drug library data 520 and generalized drug library data 522 to a connectivity adapter 206 that is in communication with multiple infusion pumps 204 A, 204 B.
- the connectivity adapter 206 can store the generalized drug library data 522 in the data store 340 .
- the generalized drug library data 522 may be incorporated into the drug library data 342 as the generalized drug library data that corresponds to the customized drug library data 520 that has also been or soon will be received.
- the CA 206 can provide the customized drug library data 520 to the appropriate infusion pump 204 A, or instruct the appropriate infusion pump 204 A to obtain the customized drug library data 520 .
- the infusion pump 204 A can store the customized drug library data 520 in memory 324 for use in future operation. For example, the infusion pump 204 A may replace customized drug library data 326 currently in memory with the newly-received customized drug library data 520 .
- infusion pump 204 B may be a different type of infusion pump than infusion pump 204 A, or may be a different version of infusion pump 204 A that is not compatible with the customized drug library data 520 . In this example, infusion pump 204 B is not provided with the customized drug library data 520 . As another example, infusion pump 204 B may be located in a location that is associated with a different CCA than infusion pump 204 A. The customized drug library data 520 may be targeted at the CCA with which infusion pump 204 A is associated, but not the CCA with which infusion pump 204 B is associated.
- infusion pump 204 B is not provided with the customized drug library data 520 .
- Details and examples of the drug library update process are described in greater detail in a co-pending international patent application no. PCT/______, attorney docket number ICUH.223WO, titled “UPDATING INFUSION PUMP DRUG LIBRARIES AND OPERATIONAL SOFTWARE IN A NETWORKED ENVIRONMENT” and filed ______, which is incorporated by reference herein.
- the worksheet structure allows for comparison among different versions of drug library data selected for a particular subset of CCAs and infusion pumps. For example, a worksheet that is being edited can be compared to a current version of the worksheet and/or one or more historical versions of the worksheet.
- JSON files JavaScript Object Notation
- These storage and comparison methods are generally more efficient than storing multiple versions of each individual record of drug library data in the DLDB along with corresponding effective dates, indicators of active/inactive status, and the like.
- the worksheet structure also allows users to build specific drug libraries for specific purposes from a shared dataset. For example, a first worksheet designed for a cancer center utilizes a first subset of the overall DLDB, while a second worksheet designed for a pediatric center utilizes a second subset of the overall DLDB that is different than the first subset.
- the individual records for the CCAs, medications, and administration rules may be maintained in the DLDB without being changed for the different worksheets.
- the worksheet datasets for the different worksheets may be modified in the DLDB, and may reference data for the CCAs, medications, and administration rules.
- the worksheet structure facilitates maintaining and viewing lifecycle of a particular set of drug library data.
- a particular set of drug library data corresponding to a particular worksheet, may progress through various stages, including: editable, in review, active, and archived. Data regarding each of the states may be included in the worksheet dataset. Accordingly, the worksheet structure provides revision control for each set of drug library data independently from other sets of drug library data (as managed using other worksheets).
- the worksheet structure also facilitates identification and implementation of global changes that are to be cascaded to all worksheets. For example, when two worksheets contain a particular CCA and that CCA is updated (e.g., a new administration rule is added, a limit is changed, etc.), then both worksheets may automatically incorporate the changes made to CCA by virtue of the worksheets referencing the CCA data that has been changed rather than including a copy of CCA as it previously existed. As another example, when a worksheet's dataset has been updated, the system can notify health care professionals that new drug library data may need to be finalized to incorporate the changes for use on infusion pumps.
- CCA e.g., a new administration rule is added, a limit is changed, etc.
- FIG. 7 is a flow diagram of an illustrative process 700 that may be executed by a DLM Editor 500 or some other component of the DLM 402 to manage the creation and maintenance of data in the DLDB 414 , and the creation and maintenance of drug libraries for use by infusion pumps 204 , connectivity adaptors 206 , reporting systems, archival systems, and the like.
- the process 700 facilitates the maintenance of DLDB data in a streamlined manner, such that data regarding, medications, administration rules, CCAs, and the like needs to be created or edited only once, and the changes will be reflected across all associated drug libraries.
- the process 700 provides the creation of generalized drug library data that may be archived in addition to being used by other systems or components.
- a repository of archived generalized drug library data files can provide snapshots of the state of drug libraries at various points in time, without requiring the maintenance of out-of-date data in the DLDB. Portions of the process 700 will be described with reference to the diagram of illustrative data flows and interactions shown in FIG. 5 , and the diagrams of illustrative user interfaces shown in FIGS. 8 and 9 .
- the process 700 shown in FIG. 7 begins at block 702 .
- the process 700 may begin in response to an event, such as when the DLM editor 500 begins execution.
- a set of executable program instructions stored on one or more non-transitory computer-readable media e.g., hard drive, flash memory, removable media, etc.
- memory e.g., random access memory or “RAM”
- the executable instructions may then be executed by a hardware-based computer processor (e.g., a central processing unit or “CPU”) of the computing device.
- a hardware-based computer processor e.g., a central processing unit or “CPU”
- the process 700 or portions thereof may be implemented on multiple processors, serially or in parallel.
- the DLM editor 500 or some other component of the DLM 402 can manage medications in the DLDB 414 .
- Management of medications may include creating, viewing, updating, and/or deleting medication 506 data entities.
- a user may use an end-user computing device 510 to access the DLM editor 500 , as shown in FIG. 5 .
- the end-user computing device 510 may present an interface for management of medications in the DLDB 414 .
- the DLM editor 500 may provide interface 800 , shown in FIG. 8 , to manage a particular medication 506 .
- Interface 800 includes an infusion pump selection area 802 , a medication information entry area 804 , a dosing limitations entry area 806 , and a clinical care area selection control 808 .
- the user may use the infusion pump selection area 802 to select the infusion pump(s) and/or pump version(s) which may be used to administer the medication.
- the user may use the medication information entry area 804 to manage properties of the medication. For example, identification-related properties such as a generic drug name 840 and display name 841 may be entered. A clinical use 842 may also be entered. Medication amount 843 , volume amount 844 , medication unit 845 , and concentration type may also be entered.
- a single medication may be associated with different display names.
- an infusion pump may only support a limited number of characters for display of medication names. Because the length of some medication names may exceed the character limit, a shortened name, such as a brand name, abbreviation, or the like may be used. Additionally, or alternatively, emphasis may be applied to portions of medication names for display to help avoid errors in the administration of the medications.
- the display name may be entered using “tall man” lettering in which part of a medication's name is displayed in upper case letters to help distinguish it from other medication names that may look and/or sound similar (e.g., “prednisone” and “prednisolone” may be displayed as “predniSONE” and “predniSOLONE”).
- a subset of the information in the various entry areas may corresponds to an administration rule for the medication, indicated by administration rule data entry group 810 .
- additional and/or alternative information in the various entry areas may be part of a particular administration rule.
- an administration rule may be assigned to a single infusion pump and/or pump type, and therefore the infusion pump selection area 802 may be included in the administration rule data entry group 810 .
- an administration rule may not include a specific display name for the medication, and therefore administration rule data entry group 810 may not include display name 841 , or display name 841 may be optional.
- a single medication may also or alternatively be associated with different clinical uses, amounts, volumes, units, and/or concentration types.
- Additional medication entries corresponding to different database records, different presentations of the interface 800 , etc.—may be used to capture these different combinations of properties.
- each of the medication entries can be linked to the top-level medication (e.g., as identified by a generic medication name and a unique identifier). In this way, the medication and all of its different available combinations of properties can be treated as a single unit when desired, or as separate medication entities when desired.
- the DLM editor 500 or some other component of the DLM 402 can manage administration rules in the DLDB 414 .
- Management of administration rules may include viewing and/or updating deleting medication 506 data entities.
- a user may use interface 800 , shown in FIG. 8 , to manage administration rules for a particular medication 506 .
- the interface 800 includes a dosing limitations entry area 806 .
- the dosing limitations entry area 806 may be used to specify various administration limits, permissions, and the like.
- the data provided in these fields is then incorporated into the drug library for the selected infusion pump, and serves to constrain the manner in which the medication is permitted to be administered by the infusion pump.
- a user may enter a lower hard limit 861 , lower soft limit 862 , upper soft limit 863 , and/or upper hard limit 864 , all in terms of the selected dosing unit.
- An infusion pump that is administering the medication subject to this administration rule will not be permitted to administer an amount outside the hard lower and upper limits.
- the infusion pump may be permitted to administer an amount outside the soft lower and upper limits, but before doing so the infusion pump may be required to perform various procedures, such as initiating alerts, prompting for authorization, or the like.
- Additional administration techniques 865 such as bolus administration, piggyback delivery, piggyback interruption, and the like may be permitted or blocked. Some administration techniques may be associated with their own properties, and permission of such techniques may cause display of additional data entry areas or interfaces. For example, if bolus administration is permitted in the additional administration techniques 865 section, then additional fields for dosing unit, upper and lower hard/soft limits, and the like may be shown.
- multiple administration rules 508 may be associated with a single medication 506 .
- different administration rules may be used for different infusion pumps.
- different administration rules may be associated with different clinical uses or concentrations of the medication. In these cases, additional medication entries may be added for the medications, and the different administration rules may be created accordingly.
- each of the separate medication entries and corresponding administration rules may be associated with a single top-level medication 506 data entity.
- the DLM editor 500 or some other component of the DLM 402 can manage CCAs in the DLDB 414 .
- Management of CCAs may include creating, viewing, updating, and/or deleting CCA 504 data entities.
- a user may use a remote computing device 510 that presents an interface for management of CCAs in the DLDB 414 .
- the DLM editor 500 may provide interface 900 , shown in FIG. 9 , to manage a particular CCA 504 .
- Interface 900 includes an infusion pump selection area 902 , a CCA information entry area 904 , a pump settings entry area 906 , and a medication selection control 908 .
- a user may use the infusion pump selection area 902 to select the infusion pump(s) and/or pump version(s) which may be used to administer medication in the CCA.
- the user may use the CCA information entry area 904 to manage properties of the CCA. For example, identification-related properties such as a CCA name 940 , service line 941 , and CCA description 942 may be entered.
- the user may use the pump settings entry area 906 to manage CCA-specific settings for the selected pump(s), such as pump limits and other operational settings of the pump(s) in the CCA.
- the user may provide a maximum dose rate 960 , permit or prohibit additional administration functions 961 such as delayed start or standby, and set occlusion alarm settings 962 .
- the user may enter CCA-specific patient limits used to constrain which patients are permitted to be treated using the infusion pump on the CCA.
- patient limits may include minimum body surface area (BSA) 963 , maximum BSA 964 , minimum height 965 , maximum height 966 , minimum weight 967 , maximum weight 968 , and the like.
- FIG. 7 illustrates blocks 704 and 706 occurring in a sequential manner on one execution path, and block 608 occurring in a parallel execution path, this example is illustrative only. In some embodiments, the operations that correspond to blocks 704 , 706 , and 708 may be performed sequentially, asynchronously, in parallel, or individual blocks may be repeated as needed.
- the DLM editor 500 or some other component of the DLM 402 can manage the medications available to the CCAs in the DLDB 414 .
- interface 800 for a particular medication 506 includes a clinical care area selection control 808 .
- a user can activate this control 808 to access an interface that facilitates selection of CCAs in which the medication 506 is permitted to be administered.
- interface 900 for a particular CCA 504 includes a medication selection control 908 .
- a user can activate this control 908 to access an interface that facilitates selection of medications that are permitted to be administered in the CCA 504 .
- the DLM editor 500 or some other component of the DLM 402 can generate a worksheet 502 for management of a drug library.
- the worksheet 502 provides the mechanism by which a drug library is generated for use by an infusion pump. Separate drug libraries may be generated and maintained for different infusion pumps and/or infusion pumps in different facilities, CCAs, and the like.
- a user may use a remote computing device 510 that presents an interface for management of worksheets in the DLDB 414 .
- the user may enter worksheet-specific information, such as a name for the worksheet, an infusion pump type and/or version targeted by the worksheet, and the like. Data representing the worksheet-specific information may be stored in the DLDB 414 .
- the DLM editor 500 or some other component of the DLM 402 can add one or more CCAs 504 to the worksheet 502 .
- Addition of CCAs 504 also has the effect of adding the various medications 506 and administration rules 508 , associated with the CCAs 504 , to the worksheet 502 .
- the CCAs provide the organizational means by which groups of medications may be added to a particular worksheet and therefore to a particular drug library.
- the DLM editor 500 or some other component of the DLM 402 can add one or more medications 506 to the worksheet 502 . Addition of medications 506 to the worksheet 502 may also have the effect of adding various administration rules 508 , associated with the medications 506 , to the worksheet 502 . In some embodiments, medications may be added in addition to CCAs, or medications may be added individually without the addition of CCAs to the worksheet. [0077]
- the DLM editor 500 or some other component of the DLM 402 can finalize the worksheet 502 .
- the worksheet 502 may be finalized on-demand (e.g., immediately upon request by a user of the DLM editor 500 ), or it may be subject to an authorization workflow. For example, the use may request finalization of a worksheet after various changes have been made. Other users may then access the worksheet, view the changes if desired, and approve or reject the worksheet. Once the changes to the worksheet are approved, the worksheet may be finalized.
- the DLM editor 500 or some other component of the DLM 402 can generate customized drug library data using the worksheet 502 .
- the worksheet may specify a particular pump type or version to which the worksheet applies.
- the DLM 402 can use drug library specification data for the particular infusion pump type or version to generate customized drug library data of the pump.
- Drug library specification data may include rules for generating customized drug library data required by the infusion pump, such as the data structure and format in which the drug library data is expected to be delivered, functions or other transformations to be applied to data from DLDB 414 to produce data that is able to be used by the infusion pump, etc.
- a first type of infusion pump may expect data fields a, b, c, d, and e to be present, in that sequence, for each medication record.
- a second type of infusion pump may also expect fields a, b, and c, to be present, together with data that corresponds to field d with a mathematical transformation applied, and also a different field f instead of field e.
- the second type of infusion pump may expect the fields to be in a different sequence than the first type of infusion pump.
- the drug library specification data for the two different types of infusion pumps can provide data regarding these expected data fields, formats, transformations, sequences, and the like.
- the DLM 402 can determine which infusion pump type and/or version is specified in the worksheet 502 data set. The DLM 402 can then generate customized drug library data 520 for the infusion pump using the worksheet 502 data in the DLDB 414 and the drug library specification data for the infusion pump.
- the DLM editor 500 or some other component of the DLM 402 can generate generalized drug library data using the worksheet 502 .
- the generalized drug library data is data used by middleware components (e.g., connectivity adapters 206 ), reporting systems, archival systems, and the like. Each of these different devices and components may be configured to operate using the same generalized drug library data.
- the generalized drug library data may be created in a standardized data format, such as JavaScript Object Notation (JSON), eXtensible Markup Language (XML), or the like.
- JSON JavaScript Object Notation
- XML eXtensible Markup Language
- generalized drug library specification data may be used to generate the generalized drug library data.
- Generalized drug library specification data may include rules for generating the generalized drug library data, such as the data structure and format in which the generalized drug library data is to be delivered, the functions or other transformations to be applied to data from the DLDB 414 to produce the generalized drug library data, etc.
- the DLM 402 can generate the generalized drug library data using the worksheet 502 data in the DLDB 414 and the generalized drug library specification data.
- FIG. 7 illustrates blocks 718 and 720 occurring in a sequential manner on one execution path, this example is illustrative only. In some embodiments, the operations that correspond to blocks 718 and 720 may be performed in a different sequence, asynchronously, or in parallel.
- the DLM editor 500 or some other component of the DLM 402 can distribute the drug library data generated above.
- the DLM 402 can provide the generalized drug library data 520 and customized drug library data 522 to a connectivity adapter 206 .
- the DLM may also or alternatively store the generalized drug library data in a drug library archive 416 .
- Storage of generalized drug library data 520 in the drug library archive 416 can provide certain benefits, such as the ability to access the drug library, as it existed when generated, at some future time even after other intervening versions of the drug library have been generated.
- the size and complexity of the DLDB 414 may be controlled because it is not necessary to store records for every prior version of data in the DLDB 414 .
- the process 700 may terminate. In some embodiments, the process 700 may return to prior blocks. For example, a user may return to block 712 to generate additional worksheets for other CCAs, infusion pumps, etc.
- FIG. 10 is a diagram of data flows and interactions between components of the networked clinical environment 102 and cloud environment 106 during use of drug library data.
- an infusion pump 204 may send a message at [A] to a connectivity adapter 206 .
- the message may indicate the start of a medication infusion process for a particular medication.
- the customized drug library data used by the infusion pump 204 may use an identifier of “13BSF68X” for the medication. Therefore, the message may include the identifier “13BSF68X” instead of the name of the medication, in order to reduce the size of the message.
- the message may include other information about the infusion, such as a timestamp for the start of the infusion, a dosage amount, etc.
- the message may include identifiers for other data regarding the infusion, or other information from which human-readable forms can be derived.
- the message may include a patient identifier, an infusion type identifier, a CCA identifier, a channel identifier, a line identifier, an auto-program reference identifier, other identifiers, some combination thereof, etc.
- the connectivity adapter 206 may receive the message from the infusion pump, and process the message at [B]. For example, the connectivity adapter 206 may process the message into a standardized dataset message using generalized drug library data in the data store 340 .
- the generalized drug library data may include the name of the drug that corresponds to the identifier “13BSF68X,” the name of the CCA that corresponds to a CCA identifier, etc.
- the connectivity adapter 206 may therefore include the drug name, CCA name, etc. in the standardized dataset message without receiving the drug name, CCA name, and the like from the infusion pump 204 .
- the connectivity adapter 206 may send the standardized dataset message to the cloud environment 106 at [C].
- the infusion pump 204 may send a second message to the connectivity adapter 206 at [D].
- the second message may relate to a past event at the infusion pump 204 , such as an infusion occurring days earlier when a different version of customized drug library data was being used by the infusion pump 204 .
- a prior message had not been received (e.g., by inspecting a sequential message identifier in the message).
- the cloud environment 106 may then have initiated a process to obtain the missing message, and as a result the infusion pump 204 re-sent (or sent for the first time) the message to the connectivity adapter 206 at [D].
- the connectivity adapter 206 can begin processing the second message at [E].
- the message may include information (e.g., an identifier) that the connectivity adapter 206 is unable to resolve by referencing the generalized drug library data currently present in the data store 340 , because generalized drug library data currently present in the data store 340 corresponds to the current customized drug library data used by the infusion pump 204 .
- the connectivity adapter 206 may retrieve, from the cloud environment 106 at [F], an archived version of the generalized drug library data that corresponds to the customized drug library data used by the infusion pump 204 when the second message was originally generated.
- the connectivity adapter 206 may proceed with processing the second message at [G] into a standardized dataset message using the archived version of generalized drug library data. For example, the connectivity adapter 206 may determine the drug name using the identifier and the archived version of the generalized drug library data and proceed with processing the second message at [G] into a standardized dataset message that includes the drug name. The connectivity adapter 206 may then send a second standardized dataset message to the cloud environment 106 at [H].
- Clause 1 A system configured to manage a drug library within a clinical environment, the system comprising:
- Clause 2 The system of Clause 1, wherein the first infusion pump is configured to replace, in memory of the first infusion pump, a prior version of customized drug library data with the customized drug library data.
- Clause 3 The system of Clause 1, wherein the first infusion pump is configured to:
- Clause 4 The system of Clause 3, wherein the connectivity adapter is configured to at least:
- Clause 5 The system of Clause 4, wherein the connectivity adapter is further configured to at least:
- Clause 6 The system of Clause 1, wherein:
- Clause 7 The system of Clause 1, wherein:
- Clause 8 The system of Clause 1, wherein the drug library manager is further configured to at least:
- Clause 9 The system of Clause 1, wherein the connectivity adapter is configured to at least:
- Clause 10 The system of Clause 1, wherein the drug library manager is further configured to at least:
- Clause 11 The system of Clause 1, further comprising a drug library archive, wherein the drug library manager is further configured to provide the generalized drug library data to the drug library archive, and wherein the drug library archive is configured to store a plurality of versions of generalized drug library data for each of a plurality of different drug libraries.
- Clause 12 The system of Clause 11, wherein the drug library manager is further configured to:
- a computer-implemented method comprising:
- Clause 14 The computer-implemented method of Clause 13, further comprising:
- Clause 15 The computer-implemented method of Clause 13, further comprising:
- Clause 16 The computer-implemented method of Clause 13, further comprising:
- Clause 17 The computer-implemented method of Clause 13, further comprising providing the generalized drug library data to a drug library archive configured to store a plurality of versions generalized drug library data for each of a plurality of different drug libraries.
- Clause 18 The computer-implemented method of Clause 13, wherein generating the generalized drug library data comprises formatting the generalized drug library data using JavaScript Object Notation.
- Clause 20 The system of Clause 19, further comprising the connectivity adapter, wherein the connectivity adapter is configured to at least:
- Clause 22 The system of Clause 21, further comprising the infusion pump, wherein the infusion pump is configured to replace, in memory of the infusion pump, a prior version of customized drug library data with the customized drug library data.
- Clause 23 The system of Clause 22, wherein the infusion pump is configured to:
- Clause 24 The system of Clause 22, wherein the infusion pump is configured to:
- Clause 25 The system of Clause 21, wherein the one or more processors are further configured to at least:
- Clause 26 The system of Clause 21, wherein:
- Clause 27 The system of Clause 21, wherein:
- Clause 28 A computer-implemented method comprising:
- Clause 29 The computer-implemented method of Clause 28, wherein processing the first infusion message comprises determining a first medication name using the first medication identifier and the generalized drug library data.
- Clause 30 The computer-implemented method of Clause 28, wherein processing the second infusion message comprises determining a second medication name using the second medication identifier and the generalized drug library data.
- Clause 31 The computer-implemented method of Clause 28, wherein sending the customized drug library data to the infusion pump cases the infusion pump to replace, in memory of the infusion pump, a prior version of customized drug library data with the customized drug library data.
- Clause 32 The computer-implemented method of Clause 31, further comprising:
- Clause 33 The computer-implemented method of Clause 28, further comprising:
- Clause 34 The computer-implemented method of Clause 28, wherein:
- Clause 35 The computer-implemented method of Clause 28, wherein:
- Clause 36 A non-transitory computer storage medium that stores an executable component that directs a computing system to perform a process comprising:
- Clause 37 The non-transitory computer storage medium of Clause 36, wherein processing the first infusion message comprises determining a first medication name using the first medication identifier and the generalized drug library data, and wherein processing the second infusion message comprises determining a second medication name using the second medication identifier and the generalized drug library data.
- Clause 38 The non-transitory computer storage medium of Clause 36, the process further comprising:
- Clause 39 The non-transitory computer storage medium of Clause 36, wherein:
- Clause 40 The non-transitory computer storage medium of Clause 36, wherein:
- a general-purpose processor can be a microprocessor, but in the alternative, the processor can be a controller, microcontroller, or state machine, combinations of the same, or the like.
- a processor can include electrical circuitry configured to process computer-executable instructions.
- a processor in another embodiment, includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions.
- a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
- a processor may also include primarily analog components. For example, some or all of the signal processing algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry.
- a computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
- a software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art.
- An example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium.
- the storage medium can be integral to the processor.
- the storage medium can be volatile or nonvolatile.
- the processor and the storage medium can reside in an ASIC.
- the ASIC can reside in a user terminal.
- the processor and the storage medium can reside as discrete components in a user terminal.
- Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.
- a device configured to are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations.
- a processor configured to carry out recitations A, B, and C can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.
Abstract
A drug library management system generates versions of drug library data that can be used by infusion pumps, and version of drug library data that can be used by systems or components in a clinical environment other than infusion pumps. One version of the drug library data may be customized for a particular infusion pump, while another version may be a generalized version that can be used by middleware systems that process messages received from various infusion pumps that are using a different version of the drug library data. The generalized version may be archived separately from a drug library database used by the drug library management system to generate the various versions.
Description
- The present application is a continuation of U.S. patent application Ser. No. 16/908,539, filed on Jun. 22, 2020 and titled “Drug Library Dynamic Version Management,” which is a continuation of U.S. patent application Ser. No. 16/512,266, filed on Jul. 15, 2019 and titled “Drug Library Dynamic Version Management,” which is a continuation of International Patent Application No. PCT/US2019/041715, filed on Jul. 12, 2019 and titled “Drug Library Management System,” which claims priority to U.S. Provisional Patent Application No. 62/703,772, filed on Jul. 26, 2018 and titled “Drug Library Management System.” Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet, or any correction thereto, are hereby incorporated by reference under 37 C.F.R. § 1.57.
- This disclosure relates to the field of clinical management, and particularly to systems and methods for efficient management of drug libraries in a networked clinical environment.
- Modern medical care often involves the use of medical infusion pumps to deliver fluids and/or fluid medicine to patients. Infusion pumps permit the controlled delivery of fluids to a patient and provide flexible yet controlled delivery schedules. Drug libraries within the infusion pumps provide some limits pertaining to the delivery of fluids. Infusion pumps can communicate with a server configured to manage drug library updates and operational software updates of the individual infusion pumps.
- Various techniques for managing drug libraries across a clinical environment and a cloud environment are described herein. These techniques may include creating and maintaining medication and administration data in a drug library database, using the data to create and maintain drug libraries, and distributing the drug libraries to various systems and components. For example, customized drug library data may be provided to infusion pumps for use in administration of medication, while generalized drug library data is proved to middleware, archives, etc. for use in system management, reporting, backup, etc. These and other embodiments are described in greater detail below with reference to
FIGS. 1-10 . Although many of the examples are described in the context of a hospital environment including particular infusion pumps, data formats, and the like, the techniques described herein can be applied to other types of infusion pumps, data formats, etc. - Some aspects of the present disclosure relate to a drug library management system that facilitates centralized management of the drug libraries that are used by various infusion pumps, including in clinical environments that have different types and/or versions of infusion pumps. Medications, administration rules, critical care area rules, and the like are maintained using the drug library management system, also referred to herein as the “drug library manager.” The drug library manager generates and distributes drug library data in pump-specific formats or other customized formats as needed. Therefore, different types and versions of infusion pumps, even those that use drug library data in different formats or that use different drug library data altogether, may be used in a clinical environment and managed using a single drug library management system.
- Additional aspects of the present disclosure relate to generating versions of drug library data that can be used by systems or components in the clinical environment other than infusion pumps. For example, drug library data may be used by middleware systems, reporting systems, archival systems, and the like. When a drug library is to be finalized, the drug library management system may generate a version of drug library data that is standardized or otherwise generalized, in addition to a version that is customized for the specific infusion pump(s) that use the drug library data. The generalized version of the drug library data can be used by middleware systems that process messages received from various infusion pumps, reporting systems that report data generated by or otherwise associated with various infusion pumps, etc. In addition, or alternatively, the generalized version can be archived so that historical versions of the drug library data may be available when needed (e.g., for historical reporting, for troubleshooting problems with infusion pumps when a prior version of the drug library was used, etc.). Advantageously, the generalized version may be archived separately from the drug library database used by the drug library manager, and therefore the drug library database does not need to store historical drug library data.
- Throughout the drawings, reference numbers may be re-used to indicate correspondence between referenced elements. The drawings are provided to illustrate example embodiments described herein and are not intended to limit the scope of the disclosure.
-
FIG. 1 is a block diagram of an example clinical environment and an example cloud environment according to some embodiments. -
FIG. 2 is a block diagram illustrating components of a clinical environment according to some embodiments. -
FIG. 3 is a schematic diagram illustrating components of an infusion pump and a connectivity adapter of a clinical environment according to some embodiments. -
FIG. 4 is a block diagram illustrating components of a cloud environment according to some embodiments. -
FIG. 5 is a block diagram of various data flows and interactions between a drug library manager, an end user device, an infusion pump, and various other system components during the creation and distribution of drug libraries according to some embodiments. -
FIG. 6 is a block diagram of illustrative components of a drug library according to some embodiments. -
FIG. 7 is a flow diagram of an illustrative process for managing the creation, maintenance, and distribution of drug libraries according to some embodiments. -
FIG. 8 is a user interface diagram of an illustrative interface for creating and maintaining medication and administration data according to some embodiments. -
FIG. 9 is a user interface diagram of an illustrative interface for creating and maintaining organizational information according to some embodiments. -
FIG. 10 is a block diagram of various data flows and interactions between drug library manager, an infusion pump, and various other system components during the use of drug libraries according to some embodiments. - The present disclosure is directed to management and use of drug libraries in a networked clinical environment. The clinical environment may include various types and/or versions of infusion pumps. An infusion pump operates using a drug library that describes the medications available for administration, rules for administration of the medications, clinical care areas in which the pump may operate, and the like. Different types or versions of infusion pumps may be configured to use different formats of drug library data. In addition, it may be necessary or desirable to maintain a history of changes to the drug library data.
- Some aspects of the present disclosure relate to a drug library management system that facilitates centralized management of the drug libraries that are used by various infusion pumps, including in clinical environments that have different types and/or versions of infusion pumps. Medications, administration rules, critical care area rules, and the like are maintained using the drug library management system, also referred to herein as the “drug library manager.” The drug library manager generates and distributes drug library data in pump-specific formats or other customized formats as needed. Therefore, different types and versions of infusion pumps, even those that use drug library data in different formats or that use different drug library data altogether, may be used in a clinical environment and managed using a single drug library management system.
- Additional aspects of the present disclosure relate to generating versions of drug library data that can be used by systems or components in the clinical environment other than infusion pumps. For example, drug library data may be used by middleware systems, reporting systems, archival systems, and the like. When a drug library is to be finalized, the drug library management system may generate a version of drug library data that is standardized or otherwise generalized, in addition to a version that is customized for the specific infusion pump(s) that use the drug library data. The generalized version of the drug library data can be used by middleware systems that process messages received from various infusion pumps, reporting systems that report data generated by or otherwise associated with various infusion pumps, etc. In addition, or alternatively, the generalized version can be archived so that historical versions of the drug library data may be available when needed (e.g., for historical reporting, for troubleshooting problems with infusion pumps when a prior version of the drug library was used, etc.). Advantageously, the generalized version may be archived separately from the drug library database used by the drug library manager, and therefore the drug library database does not need to store historical drug library data.
- Although aspects of some embodiments described in the disclosure will focus, for the purpose of illustration, on particular examples of infusion pumps, mediation administration rules, formats of drug library data, and the like, the examples are illustrative only and are not intended to be limiting. In some embodiments, the systems and methods described herein may be applied to additional or alternative infusion pumps, mediation administration rules, drug library data formats, etc. Various aspects of the disclosure will now be described with regard to certain examples and embodiments, which are intended to illustrate but not limit the disclosure.
-
FIG. 1 illustratesnetwork environment 100 in whichclinical environment 102 communicates withcloud environment 106 vianetwork 104. Theclinical environment 102 may include one or more healthcare facilities (e.g., hospitals). The components of theclinical environment 102 are described in greater detail below with reference toFIG. 2 . Thenetwork 104 may be any wired network, wireless network, or combination thereof. In addition, thenetwork 104 may be a personal area network, local area network, wide area network, over-the-air broadcast network (e.g., for radio or television), cable network, satellite network, cellular telephone network, or combination thereof. For example, thenetwork 104 may be a publicly accessible network of linked networks such as the Internet. In some embodiments, theclinical environment 102 and thecloud environment 106 may each be implemented on one or more wired and/or wireless private networks, and thenetwork 104 may be a public network (e.g., the Internet) via which theclinical environment 102 and thecloud environment 106 communicate with each other. Thecloud environment 106 may be a cloud-based platform configured to communicate with multiple clinical environments. Thecloud environment 106 may include a collection of services, which are delivered via thenetwork 104 as web services. The components of thecloud environment 106 are described in greater detail below with reference toFIG. 4 . -
FIG. 2 illustrates theclinical environment 102, which includes one or moreclinical IT systems 202, one or more infusion pumps 204, and one ormore connectivity adapters 206. Further, theclinical environment 102 may be configured to provide cloud user interfaces 208 (e.g., generated and provided by the cloud environment 106). Theclinical IT system 202 may include a hospital information system (HIS) designed to manage the facilities' operation, such as medical, administrative, financial, and legal issues and the corresponding processing of services. The HIS can include one or more electronic medical record (EMR) or electronic health record (EHR) systems, as well. Theinfusion pump 204 is a medical device configured to deliver medication to a patient. Theconnectivity adapter 206 is a network component configured to communicate with other components of theclinical environment 102 and also communicate with thecloud environment 106 on behalf of the other components of theclinical environment 102. In one embodiment, all messages communicated between theclinical environment 102 and thecloud environment 106 pass through theconnectivity adapter 206. In some cases, theconnectivity adapter 206 is a network appliance with limited storage space (e.g., memory and/or persistent storage). Thecloud user interfaces 208 may be provided to a user in theclinical environment 102 via a browser application, desktop application, mobile application, and the like. The user may access status reports and other data stored in thecloud environment 106 via thecloud user interfaces 208. - The components 202-208 illustrated in
FIG. 2 may communicate with one or more of the other components in theclinical environment 102. For example, each of theclinical IT system 202 and theinfusion pump 204 may communicate with theconnectivity adapter 206 via physical local area network (LAN) and/or virtual LAN (VLAN). Although not shown inFIG. 2 , theclinical environment 102 may include other medical devices and non-medical devices that facilitate the operation of theclinical environment 102. -
FIG. 3 illustrates the messages and data received, stored, and transmitted by theconnectivity adapter 206 in theclinical environment 102. As shown inFIG. 3 , theinfusion pump 204 may include motor controller unit (MCU) 320 and communications engine (CE) 322, andmemory 324 storingdrug library data 326 andoperational software 328. Thedrug library data 324 includes boundaries for drug delivery for various medications that can be delivered to patients by infusion pumps. Theoperational software 328 can include the operating system of theinfusion pump 204, as well as other software for performing various functions. Each type of infusion pump and even different versions of the same type of infusion pump may operate with a different operating system. In some embodiments, theMCU 320 uses a less powerful processor (e.g., 12 MHz) and theCE 322 uses a more powerful processor (e.g., 400 MHz). - The
MCU 320 may generate and send pump messages to theCE 322 for storage and transmission to theconnectivity adapter 206. The pump messages may include clinical information. TheCE 322 may send such pump messages to theconnectivity adapter 206. Pump messages sent to theconnectivity adapter 206 via theCE 322 and generated by theMCU 320 may be transformed by thetransformation worker 330 into a standardized dataset message (e.g., message format used by theconnectivity adapter 206 to communicate with thecloud environment 106, sometimes referred herein as simply a message). For example, thetransformation worker 330 may usedrug library data 342, described below, to transform a pump message into a standardized dataset message. - The
CE 322 may also receive messages from theconnectivity adapter 206 indicating that updates, such as updates to the drug library or updates to the operational software are available and may send messages to theconnectivity adapter 206 requesting the updates (e.g., update data). TheCE 322 may also receive the update data from theconnectivity adapter 206 for storage in thememory 324. The update data may be drug library update data or may be operational software update data. The update data may be provided over a different communication channel than the communication channel(s) used to send or receive messages. - As also shown in
FIG. 3 , theconnectivity adapter 206 may includetransformation worker 330,device status manager 332,cache 334, aninbound queue 336, anoutbound queue 338, and adata store 340. Thetransformation worker 330 may transform the messages sent to theconnectivity adapter 206 from theinfusion pump 204 into the standardized dataset message. Thetransformation worker 330 may also transform messages sent from theconnectivity adapter 206 to theinfusion pump 204 into a message format usable by theinfusion pump 204. - The
inbound queue 336 receives and stores messages from thecloud environment 106 for processing by theconnectivity adapter 206. For example, theinbound queue 332 may receive a drug library update message from thecloud environment 106. The drug library update message may be notification that a drug library update is available for a least a portion of the infusion pumps 204 associated with theconnectivity adapter 206. In an embodiment, theconnectivity adapter 206 may comprise more than one inbound queue such that, for example, there is at least aninbound queue 336 for messages received from thecloud environment 106 over thenetwork 104 and at least another inbound queue for messages received from one or more infusion pumps 204 over the local network. The messages stored in theinbound queue 336 may be associated with one or more sequence identifiers (IDs). The messages received from thecloud environment 106 may be sent over a message channel associated with thenetwork 104. - The
outbound queue 338 receives and stores messages to be sent from theconnectivity adapter 206. For example, theoutbound queue 338 may receive a drug library update message to be sent to one more infusion pumps over the local network. The drug library update message may be a notification to one or more infusion pumps 204 that a drug library update is available. In an embodiment, theconnectivity adapter 206 may comprise more than one outbound queue such that, for example, there is at least anoutbound queue 338 for messages to be sent to thecloud environment 106 over thenetwork 104 and at least another outbound queue for messages to be sent to one or more infusion pumps 204 over the local network. The messages stored in theoutbound queue 338 may be associated with one or more sequence identifiers (IDs). The messages sent from theconnectivity adapter 206 to the infusion pumps 204 may be sent over a message channel associated with the local network. - The
device status manager 332 receives the drug library and operational software updates from thecloud environment 106 and caches blocks of the update data in the cache 302. Thedevice status manager 332 processes the received messages from theinbound queue 336 and sends messages to theoutbound queue 338 for transmission to thecloud environment 106 or to the infusion pumps 204. The data received from thecloud environment 106 may be sent over a data channel associated with thenetwork 104 and separate from the message channel of thenetwork 104. Because the data channel in the cloud environment is separate from the message channel in the cloud environment, the data transfer does not interfere with the clinical messaging from the connectivity adapter to the cloud environment. The data sent from the cache 302 to the infusion pumps 204 may be sent over a data channel associated with the local network and separate from the message channel associated with the local network. Because the data channel in the local network is separate from the message channel in the local network, the data transfer does not interfere with the clinical messaging from infusion pumps to the connectivity adapter. Thus, congestion on both the message channel of the cloud environment and the message channel of the local network is reduced. - The
device status manager 332 also processes transformed messages provided by thetransformation worker 330 and merges the data included in the transformed messages into thecache 334 to update the current state of theinfusion pump 204 stored in thecache 334. - The
data store 340 may store, among other things,drug library data 342. Thedrug library data 342 may be a generalized version of pump-specific drug library data that is stored on apump 204. Thedrug library data 342 may be used to process messages received from apump 204. For example, thepump 204 may send a message to theconnectivity adapter 206 regarding a drug infusion process that has been initiated on thepump 204. The message may include a subset of information about the medication being infused or the infusion process, and theconnectivity adapter 206 may derive information from the message. For example, the message may include an identifier of the medication that is being infused, but the message may not include the name of the medication. Theconnectivity adapter 206 can access thedrug library data 342 and obtain the name of the medication that corresponds to the identifier received from the pump. As another example, the message may include an identifier for a clinical care area, but the message may not include the name of the clinical care area. Theconnectivity adapter 206 can access thedrug library data 342 and obtain the name of the medication that corresponds to the identifier of the clinical care area. As a further example, the message may include a channel identifier for a particular channel of the infusion pump, a line identifier for a particular line of the infusion pump, an auto-program reference ID for a particular order number, other identifier information, some combination thereof, etc. Theconnectivity adapter 206 may determine a corresponding name, description, or other human-readable form from the message data using thedrug library data 342. The use of thedrug library data 342 to process messaged received from aninfusion pump 204 is described in greater detail below. -
FIG. 4 illustrates thecloud environment 106, which includes drug library manager (DLM) 402,report manager 404,device manager 406, data flow manager (DFM) 408, cloud manager (CM) 410, data analyzer (DA) 412, a drug library database (DLDB) 414, and adrug library archive 416. - The
DLM 402 may provide a set of features and functions involved in the creation and management of drug libraries for use with infusion pumps, as described in greater detail below. The drug libraries may provide user-defined settings for pump configuration and drug infusion error reduction. For example, the drug libraries may be used as part of a dose error reduction system (DERS).[0033] Thereport manager 404 may provide various reporting capabilities for clinically relevant infusion data which users can choose to use for further analysis, such as tracking and trending of clinical practices. - The
device manager 406 may oversee and manage the maintenance of infusion pumps, providing users the capability to view and manage asset and operational data. For example, thedevice manager 406 may schedule drug library and software updates for infusion pumps. - The
DFM 408 may facilitate storing, caching, and routing of data between compatible infusion pumps, compatible external systems, and the like. For example, theDFM 408 may store infusion and operational data received from infusion pumps, store and cache infusion pump drug libraries and software images, convert and route network messaging between thecloud environment 106 and theclinical environment 102, convert and route medication order information from a hospital information system to an infusion pump (e.g., auto-programming or smart-pump programming), and/or convert and route alert information and infusion events from infusion pumps to hospital information systems (e.g., alarm/alert forwarding, and auto-documentation, or infusion documentation). - The
CM 410 may serve as a general-purpose computing platform for the other modules illustrated inFIG. 4 . Functionally, theCM 410 may be similar to Microsoft Windows or Linux operating systems as it provides the following services: networking, computation, user administration and security, storage, and monitoring. - The
DA 412 may provide data analytics tools for generating user interfaces and reports based on the data generated and/or received by the other modules illustrated inFIG. 4 . - The
DLDB 414 may store data regarding medications, medication administration rules, clinical care areas, and other data maintained and used by thedrug library manager 402 to generate drug library data for infusion pumps and other systems or components. - The
drug library archive 416 may store generalized drug library data that has been generated by thedrug library manager 402. Thedrug library archive 416 may store a copy of every generalized drug library data set generated by the drug library management, or some subset thereof, for use in record keeping, reporting, etc. Use of archived generalized drug library data is described in greater detail below. - Although not illustrated in
FIG. 4 , thecloud environment 106 may provide other resources such as processors, memory, disk space, network, etc. The modules 402-412 may be hardware components configured to perform one or more of the techniques described herein. Alternatively, the modules 402-412 may be implemented using software instructions stored in physical storage and executed by one or more processors. Although illustrated as separate components, the modules 402-412 may be implemented as one or more hardware components (e.g., a single component, individual components, or any number of components), one or more software components (e.g., a single component, individual components, or any number of components), or any combination thereof. - In some embodiments, the
cloud environment 106 can be implemented using a commercial cloud services provider (e.g., Amazon Web Services®, Microsoft Azure®, Google Cloud®, and the like). In other embodiments, thecloud environment 106 can be implemented using network infrastructure managed by the provider and/or developer of the modules 402-412 shown inFIG. 4 . In some embodiments, the features and services provided by one of more of the modules 402-412 may be implemented on one or more hardware computing devices as web services consumable via one or more communication networks. In further embodiments, one of more of the modules 402-412 are provided by one or more virtual machines implemented in a hosted computing environment. The hosted computing environment may include one or more rapidly provisioned and released computing resources, such as computing devices, networking devices, and/or storage devices - With reference to an illustrative embodiment,
FIG. 5 shows a network environment in which aspects of drug library management may be implemented. As shown, aDLM 402 may include aDLM editor 500 component. TheDLM editor 500 may include executable instructions that generate auser interface 512 for display on an end-user computing device 510. For example, the DLM may include, or be associated with, a web server that generates web pages, sends the web pages to the end-user computing device 510, and processes user inputs and interactions with the web pages. - The
DLM editor 500 may be used to manage data stored in theDLDB 414, and to generate drug library data for use by various devices and systems, such as infusion pumps 204A, 204B, and theconnectivity adapter 206. The data to be stored in theDLDB 414 may includedata regarding medications 506, administration rules 508 regarding use of themedications 506, clinical care areas (CCAs) 504 in which medications are used, and other data related to the management of drug libraries. - In some embodiments, the
DLDB 414 may include data related to the management of all drug libraries associated with thecloud environment 106. In other embodiments, theDLDB 414 may include data related to a subset of drug libraries associated with the cloud environment 106 (e.g., drug libraries for a particularclinical environment 102 or group of clinical environments, drug libraries for a particular customer or other entity, etc.). For example, there may be multiple DLDBs that are physically or logically separate from each other. -
Medications 506 are data entities that represent medications that can be administered via an infusion pump. In some embodiments, amedication 506 data entity may include data regarding a name of a medication, an identifier of the medication (e.g., a unique identifier used by an HIS), an indication of whether the medication is a high-risk medication, and/or other information. - Administration rules 508 are data entities that represent the parameters by which a medication may be administered. For example, an
administration rule 508 for a particular medication may include data representing various medication administration parameters such as a dosing unit, a clinical use, and/or other information. In some embodiments, anadministration rule 508 for aparticular medication 506 may include medication administration parameter data regarding an absolute or “hard” minimum and/or maximum limit to the administration of the medication (e.g., minimum or maximum amount that may be administered overall or in a period of time, minimum or maximum rate at which the medication may be administered, etc.). Such hard limits typically cannot be overridden. In some embodiments, theadministration rule 508 may also or alternatively include data regarding a recommended or “soft” minimum and/or maximum limit to administration of the medication. Such soft limits may be overridden (e.g., by users with the proper level of authority, after generation of an alert such as an audible and/or visual notification, etc.). There may be any number of administration rules 508 for asingle medication 506. For example,different administration rules 508 may be separately maintained for different clinical uses of thesame medication 506, different infusion pumps 204 through which the medication is to be administered, and/ordifferent CCAs 504 in which the medication is to be administered. In some embodiments, amedication 506 may be associated with zero or more administration rules 508. In some embodiments, an administration rule may only be associated with asingle medication 506. -
CCAs 504 are data entities that represent organizational units of health care enterprises. For example, CCAs may represent hospitals, individual hospital facilities, departments, or lines of care. In some embodiments, a CCA corresponds to a unit of similar clinical uses, patient types, other characteristics, some combination thereof, etc.CCAs 504 may be associated withvarious medications 506 andadministrative rules 508. -
FIG. 6 shows an example of amedication 506A associated withmultiple administration rules different CCAs CCA 504A may correspond to a pediatric unit of a hospital, andCCA 504B may correspond to an ICU of the hospital. Thepediatric CCA 504A andICU 504B may each have various data elements, any or all of which may correspond to medication administration settings. For example, as shown,pediatric CCA 504A may include a data element specifying a maximum dose rate of 200 mL/hr.ICU CCA 504B may include a data element specifying a maximum dose rate of 999 mL/hr.Pediatric CCA 504A may be associated with anadministration rule 508A formedication 506A, and thatadministration rule 508A is more restrictive (e.g., smaller maximum doses) than the administration rule 506B—for thesame medication 506A—that is associated withICU CCA 504B, which is for an adult population. In some embodiments, settings for thepediatric CCA 504A may prevent or override a lessrestrictive administration rule 508A when themedication 506A is used within thepediatric CCA 504A. However, if theadministration rule 508A for themedication 506A is more restrictive than a setting of thepediatric CCA 504A, the setting of theCCA 504A will not override theadministration rule 508A. - Returning to
FIG. 5 , a user may use theDLM editor 500 to organize medications, administration rules, and CCAs into drug libraries that are distributed to infusion pumps and other system components. In some embodiments, the organizational mechanism may be referred to as aworksheet 502. Aworksheet 502 is a dataset that includes references to the individual medications and administration rules to be made available to infusion pumps. In addition, theworksheet 502 can be directed to a particular infusion pump 204 or group of infusion pumps 204 that share the same customized drug library data format. Rather than providing data to theinfusion pump 204 regarding everymedication 506 andadministration rule 508 available in theDLDB 414, aworksheet 502 may be used to specify a subset ofmedications 506 and administration rules 508. For example, aCCA 504 may be added to aworksheet 502, and all of themedications 506 andadministration rules 508 associated with theCCA 504 and thetarget infusion pump 204 are automatically added. In some embodiments, individual medications may optionally be added to a worksheet separately from any CCA that may be added. - The
worksheet 502 dataset may be stored in theDLDB 414. Theworksheet 502 dataset may include data representing various properties of the worksheet, such as a name, infusion pump type and/or version targeted by the worksheet, creator of the worksheet, creation and/or edit date, approval status, version, and the like. In addition, theworksheet 502 dataset may include a collection of pointers or other references to the data entities representing the various CCAs, medications, and administration rules that are associated with theworksheet 502. Creation ofworksheets 502 and other associated operations are discussed in greater detail below. - The
DLM editor 500 or some other component of theDLM 402 can generate drug library data using aworksheet 502. For example, once aworksheet 502 has been created or edited, theworksheet 502 may be in a “pending” status, awaiting approval. After the appropriate approval has been granted, theDLM 402 can generate customizeddrug library data 520 that represents the CCAs, medications, administration rules, and other data in the format that is required for operation of thetarget pump 204. In addition, theDLM 402 can generate generalizeddrug library data 522 for use by a middleware component such as theconnectivity adapter 206, for reporting and archival purposes, etc. - As shown in
FIG. 5 , theDLM 402 can send the customizeddrug library data 520 and generalizeddrug library data 522 to aconnectivity adapter 206 that is in communication with multiple infusion pumps 204A, 204B. Theconnectivity adapter 206 can store the generalizeddrug library data 522 in thedata store 340. The generalizeddrug library data 522 may be incorporated into thedrug library data 342 as the generalized drug library data that corresponds to the customizeddrug library data 520 that has also been or soon will be received. - The
CA 206 can provide the customizeddrug library data 520 to the appropriate infusion pump 204A, or instruct the appropriate infusion pump 204A to obtain the customizeddrug library data 520. Theinfusion pump 204A can store the customizeddrug library data 520 inmemory 324 for use in future operation. For example, the infusion pump 204A may replace customizeddrug library data 326 currently in memory with the newly-received customizeddrug library data 520. - Other infusion pumps, such as those that do not operate using the same format of customized drug library data, are not provided with or instructed to obtain the customized
drug library data 520. For example,infusion pump 204B may be a different type of infusion pump than infusion pump 204A, or may be a different version ofinfusion pump 204A that is not compatible with the customizeddrug library data 520. In this example,infusion pump 204B is not provided with the customizeddrug library data 520. As another example,infusion pump 204B may be located in a location that is associated with a different CCA than infusion pump 204A. The customizeddrug library data 520 may be targeted at the CCA with which infusion pump 204A is associated, but not the CCA with whichinfusion pump 204B is associated. In this example,infusion pump 204B is not provided with the customizeddrug library data 520. Details and examples of the drug library update process are described in greater detail in a co-pending international patent application no. PCT/______, attorney docket number ICUH.223WO, titled “UPDATING INFUSION PUMP DRUG LIBRARIES AND OPERATIONAL SOFTWARE IN A NETWORKED ENVIRONMENT” and filed ______, which is incorporated by reference herein. - The worksheet structure allows for comparison among different versions of drug library data selected for a particular subset of CCAs and infusion pumps. For example, a worksheet that is being edited can be compared to a current version of the worksheet and/or one or more historical versions of the worksheet. The various versions of the worksheet—and therefore the various versions of the corresponding drug library data—may be stored as generalized drug library data (e.g., JavaScript Object Notation or JSON files) and may be compared to each other (e.g., using text-based comparison methods) to determine any differences between the files. Differences between the files may be presented to a user so that the user can see what is different between the versions of the drug library data. These storage and comparison methods are generally more efficient than storing multiple versions of each individual record of drug library data in the DLDB along with corresponding effective dates, indicators of active/inactive status, and the like.
- The worksheet structure also allows users to build specific drug libraries for specific purposes from a shared dataset. For example, a first worksheet designed for a cancer center utilizes a first subset of the overall DLDB, while a second worksheet designed for a pediatric center utilizes a second subset of the overall DLDB that is different than the first subset. The individual records for the CCAs, medications, and administration rules may be maintained in the DLDB without being changed for the different worksheets. The worksheet datasets for the different worksheets may be modified in the DLDB, and may reference data for the CCAs, medications, and administration rules.
- The worksheet structure facilitates maintaining and viewing lifecycle of a particular set of drug library data. For example, a particular set of drug library data, corresponding to a particular worksheet, may progress through various stages, including: editable, in review, active, and archived. Data regarding each of the states may be included in the worksheet dataset. Accordingly, the worksheet structure provides revision control for each set of drug library data independently from other sets of drug library data (as managed using other worksheets).
- The worksheet structure also facilitates identification and implementation of global changes that are to be cascaded to all worksheets. For example, when two worksheets contain a particular CCA and that CCA is updated (e.g., a new administration rule is added, a limit is changed, etc.), then both worksheets may automatically incorporate the changes made to CCA by virtue of the worksheets referencing the CCA data that has been changed rather than including a copy of CCA as it previously existed. As another example, when a worksheet's dataset has been updated, the system can notify health care professionals that new drug library data may need to be finalized to incorporate the changes for use on infusion pumps.
-
FIG. 7 is a flow diagram of anillustrative process 700 that may be executed by aDLM Editor 500 or some other component of theDLM 402 to manage the creation and maintenance of data in theDLDB 414, and the creation and maintenance of drug libraries for use byinfusion pumps 204,connectivity adaptors 206, reporting systems, archival systems, and the like. Advantageously, theprocess 700 facilitates the maintenance of DLDB data in a streamlined manner, such that data regarding, medications, administration rules, CCAs, and the like needs to be created or edited only once, and the changes will be reflected across all associated drug libraries. Moreover, theprocess 700 provides the creation of generalized drug library data that may be archived in addition to being used by other systems or components. Thus, a repository of archived generalized drug library data files can provide snapshots of the state of drug libraries at various points in time, without requiring the maintenance of out-of-date data in the DLDB. Portions of theprocess 700 will be described with reference to the diagram of illustrative data flows and interactions shown inFIG. 5 , and the diagrams of illustrative user interfaces shown inFIGS. 8 and 9 . - The
process 700 shown inFIG. 7 begins atblock 702. Theprocess 700 may begin in response to an event, such as when theDLM editor 500 begins execution. When theprocess 700 is initiated, a set of executable program instructions stored on one or more non-transitory computer-readable media (e.g., hard drive, flash memory, removable media, etc.) may be loaded into memory (e.g., random access memory or “RAM”) of a computing device of thecloud environment 106. The executable instructions may then be executed by a hardware-based computer processor (e.g., a central processing unit or “CPU”) of the computing device. In some embodiments, theprocess 700 or portions thereof may be implemented on multiple processors, serially or in parallel. - At
block 704, theDLM editor 500 or some other component of theDLM 402 can manage medications in theDLDB 414. Management of medications may include creating, viewing, updating, and/or deletingmedication 506 data entities. - In some embodiments, a user may use an end-
user computing device 510 to access theDLM editor 500, as shown inFIG. 5 . The end-user computing device 510 may present an interface for management of medications in theDLDB 414. For example, theDLM editor 500 may provideinterface 800, shown inFIG. 8 , to manage aparticular medication 506.Interface 800 includes an infusionpump selection area 802, a medicationinformation entry area 804, a dosinglimitations entry area 806, and a clinical carearea selection control 808. - The user may use the infusion
pump selection area 802 to select the infusion pump(s) and/or pump version(s) which may be used to administer the medication. The user may use the medicationinformation entry area 804 to manage properties of the medication. For example, identification-related properties such as ageneric drug name 840 anddisplay name 841 may be entered. Aclinical use 842 may also be entered.Medication amount 843,volume amount 844,medication unit 845, and concentration type may also be entered. - In some embodiments, a single medication may be associated with different display names. For example, an infusion pump may only support a limited number of characters for display of medication names. Because the length of some medication names may exceed the character limit, a shortened name, such as a brand name, abbreviation, or the like may be used. Additionally, or alternatively, emphasis may be applied to portions of medication names for display to help avoid errors in the administration of the medications. Illustratively, the display name may be entered using “tall man” lettering in which part of a medication's name is displayed in upper case letters to help distinguish it from other medication names that may look and/or sound similar (e.g., “prednisone” and “prednisolone” may be displayed as “predniSONE” and “predniSOLONE”).
- A subset of the information in the various entry areas may corresponds to an administration rule for the medication, indicated by administration rule
data entry group 810. In some embodiments, additional and/or alternative information in the various entry areas may be part of a particular administration rule. For example, an administration rule may be assigned to a single infusion pump and/or pump type, and therefore the infusionpump selection area 802 may be included in the administration ruledata entry group 810. As another example, an administration rule may not include a specific display name for the medication, and therefore administration ruledata entry group 810 may not includedisplay name 841, ordisplay name 841 may be optional. - In some embodiments, a single medication may also or alternatively be associated with different clinical uses, amounts, volumes, units, and/or concentration types. Additional medication entries—corresponding to different database records, different presentations of the
interface 800, etc.—may be used to capture these different combinations of properties. However, each of the medication entries can be linked to the top-level medication (e.g., as identified by a generic medication name and a unique identifier). In this way, the medication and all of its different available combinations of properties can be treated as a single unit when desired, or as separate medication entities when desired. - Returning to
FIG. 7 , atblock 706 theDLM editor 500 or some other component of theDLM 402 can manage administration rules in theDLDB 414. Management of administration rules may include viewing and/or updating deletingmedication 506 data entities. - In some embodiments, a user may use
interface 800, shown inFIG. 8 , to manage administration rules for aparticular medication 506. In addition to identification and other properties of amedication 506 as described above, theinterface 800 includes a dosinglimitations entry area 806. The dosinglimitations entry area 806 may be used to specify various administration limits, permissions, and the like. The data provided in these fields is then incorporated into the drug library for the selected infusion pump, and serves to constrain the manner in which the medication is permitted to be administered by the infusion pump. For example, after specifying adosing unit 860, a user may enter a lowerhard limit 861, lowersoft limit 862, uppersoft limit 863, and/or upperhard limit 864, all in terms of the selected dosing unit. An infusion pump that is administering the medication subject to this administration rule will not be permitted to administer an amount outside the hard lower and upper limits. The infusion pump may be permitted to administer an amount outside the soft lower and upper limits, but before doing so the infusion pump may be required to perform various procedures, such as initiating alerts, prompting for authorization, or the like. -
Additional administration techniques 865, such as bolus administration, piggyback delivery, piggyback interruption, and the like may be permitted or blocked. Some administration techniques may be associated with their own properties, and permission of such techniques may cause display of additional data entry areas or interfaces. For example, if bolus administration is permitted in theadditional administration techniques 865 section, then additional fields for dosing unit, upper and lower hard/soft limits, and the like may be shown. - In some embodiments,
multiple administration rules 508 may be associated with asingle medication 506. For example, different administration rules may be used for different infusion pumps. As another example, different administration rules may be associated with different clinical uses or concentrations of the medication. In these cases, additional medication entries may be added for the medications, and the different administration rules may be created accordingly. However, each of the separate medication entries and corresponding administration rules may be associated with a single top-level medication 506 data entity. - Returning to
FIG. 7 , atblock 708 theDLM editor 500 or some other component of theDLM 402 can manage CCAs in theDLDB 414. Management of CCAs may include creating, viewing, updating, and/or deletingCCA 504 data entities. In some embodiments, a user may use aremote computing device 510 that presents an interface for management of CCAs in theDLDB 414. For example, theDLM editor 500 may provideinterface 900, shown inFIG. 9 , to manage aparticular CCA 504. -
Interface 900 includes an infusionpump selection area 902, a CCAinformation entry area 904, a pumpsettings entry area 906, and amedication selection control 908. A user may use the infusionpump selection area 902 to select the infusion pump(s) and/or pump version(s) which may be used to administer medication in the CCA. The user may use the CCAinformation entry area 904 to manage properties of the CCA. For example, identification-related properties such as aCCA name 940,service line 941, andCCA description 942 may be entered. The user may use the pumpsettings entry area 906 to manage CCA-specific settings for the selected pump(s), such as pump limits and other operational settings of the pump(s) in the CCA. For example, the user may provide amaximum dose rate 960, permit or prohibit additional administration functions 961 such as delayed start or standby, and setocclusion alarm settings 962. In some embodiments, the user may enter CCA-specific patient limits used to constrain which patients are permitted to be treated using the infusion pump on the CCA. For example, patient limits may include minimum body surface area (BSA) 963,maximum BSA 964,minimum height 965,maximum height 966,minimum weight 967,maximum weight 968, and the like. - Although
FIG. 7 illustratesblocks blocks - At block 710, the
DLM editor 500 or some other component of theDLM 402 can manage the medications available to the CCAs in theDLDB 414. For example,interface 800 for aparticular medication 506 includes a clinical carearea selection control 808. A user can activate thiscontrol 808 to access an interface that facilitates selection of CCAs in which themedication 506 is permitted to be administered. As another example,interface 900 for aparticular CCA 504 includes amedication selection control 908. A user can activate thiscontrol 908 to access an interface that facilitates selection of medications that are permitted to be administered in theCCA 504. - At block 712, the
DLM editor 500 or some other component of theDLM 402 can generate aworksheet 502 for management of a drug library. Theworksheet 502 provides the mechanism by which a drug library is generated for use by an infusion pump. Separate drug libraries may be generated and maintained for different infusion pumps and/or infusion pumps in different facilities, CCAs, and the like. In some embodiments, a user may use aremote computing device 510 that presents an interface for management of worksheets in theDLDB 414. The user may enter worksheet-specific information, such as a name for the worksheet, an infusion pump type and/or version targeted by the worksheet, and the like. Data representing the worksheet-specific information may be stored in theDLDB 414. - At block 714, the
DLM editor 500 or some other component of theDLM 402 can add one or more CCAs 504 to theworksheet 502. Addition ofCCAs 504 also has the effect of adding thevarious medications 506 andadministration rules 508, associated with theCCAs 504, to theworksheet 502. In this example, the CCAs provide the organizational means by which groups of medications may be added to a particular worksheet and therefore to a particular drug library. - In some embodiments, the
DLM editor 500 or some other component of theDLM 402 can add one ormore medications 506 to theworksheet 502. Addition ofmedications 506 to theworksheet 502 may also have the effect of addingvarious administration rules 508, associated with themedications 506, to theworksheet 502. In some embodiments, medications may be added in addition to CCAs, or medications may be added individually without the addition of CCAs to the worksheet. [0077] Atblock 716, theDLM editor 500 or some other component of theDLM 402 can finalize theworksheet 502. Theworksheet 502 may be finalized on-demand (e.g., immediately upon request by a user of the DLM editor 500), or it may be subject to an authorization workflow. For example, the use may request finalization of a worksheet after various changes have been made. Other users may then access the worksheet, view the changes if desired, and approve or reject the worksheet. Once the changes to the worksheet are approved, the worksheet may be finalized. - At
block 718, theDLM editor 500 or some other component of theDLM 402 can generate customized drug library data using theworksheet 502. As described above, the worksheet may specify a particular pump type or version to which the worksheet applies. TheDLM 402 can use drug library specification data for the particular infusion pump type or version to generate customized drug library data of the pump. - Drug library specification data may include rules for generating customized drug library data required by the infusion pump, such as the data structure and format in which the drug library data is expected to be delivered, functions or other transformations to be applied to data from
DLDB 414 to produce data that is able to be used by the infusion pump, etc. For example, a first type of infusion pump may expect data fields a, b, c, d, and e to be present, in that sequence, for each medication record. A second type of infusion pump may also expect fields a, b, and c, to be present, together with data that corresponds to field d with a mathematical transformation applied, and also a different field f instead of field e. In addition, the second type of infusion pump may expect the fields to be in a different sequence than the first type of infusion pump. The drug library specification data for the two different types of infusion pumps can provide data regarding these expected data fields, formats, transformations, sequences, and the like. - The
DLM 402 can determine which infusion pump type and/or version is specified in theworksheet 502 data set. TheDLM 402 can then generate customizeddrug library data 520 for the infusion pump using theworksheet 502 data in theDLDB 414 and the drug library specification data for the infusion pump. - At
block 720, theDLM editor 500 or some other component of theDLM 402 can generate generalized drug library data using theworksheet 502. As described above, the generalized drug library data is data used by middleware components (e.g., connectivity adapters 206), reporting systems, archival systems, and the like. Each of these different devices and components may be configured to operate using the same generalized drug library data. Illustratively, the generalized drug library data may be created in a standardized data format, such as JavaScript Object Notation (JSON), eXtensible Markup Language (XML), or the like. In some embodiments, generalized drug library specification data may be used to generate the generalized drug library data. Generalized drug library specification data may include rules for generating the generalized drug library data, such as the data structure and format in which the generalized drug library data is to be delivered, the functions or other transformations to be applied to data from theDLDB 414 to produce the generalized drug library data, etc. TheDLM 402 can generate the generalized drug library data using theworksheet 502 data in theDLDB 414 and the generalized drug library specification data. - Although
FIG. 7 illustratesblocks blocks - At
block 722, theDLM editor 500 or some other component of theDLM 402 can distribute the drug library data generated above. For example, as shown inFIG. 5 , theDLM 402 can provide the generalizeddrug library data 520 and customizeddrug library data 522 to aconnectivity adapter 206. In some embodiments, the DLM may also or alternatively store the generalized drug library data in adrug library archive 416. Storage of generalizeddrug library data 520 in thedrug library archive 416 can provide certain benefits, such as the ability to access the drug library, as it existed when generated, at some future time even after other intervening versions of the drug library have been generated. In addition, by maintaining prior versions of drug libraries in theseparate archive 416, the size and complexity of theDLDB 414 may be controlled because it is not necessary to store records for every prior version of data in theDLDB 414. - At
block 724, theprocess 700 may terminate. In some embodiments, theprocess 700 may return to prior blocks. For example, a user may return to block 712 to generate additional worksheets for other CCAs, infusion pumps, etc. - Example Drug Library Use
-
FIG. 10 is a diagram of data flows and interactions between components of the networkedclinical environment 102 andcloud environment 106 during use of drug library data. As shown, aninfusion pump 204 may send a message at [A] to aconnectivity adapter 206. For example, the message may indicate the start of a medication infusion process for a particular medication. The customized drug library data used by theinfusion pump 204 may use an identifier of “13BSF68X” for the medication. Therefore, the message may include the identifier “13BSF68X” instead of the name of the medication, in order to reduce the size of the message. The message may include other information about the infusion, such as a timestamp for the start of the infusion, a dosage amount, etc. Alternatively or in addition, to reduce the overall size of the message, the message may include identifiers for other data regarding the infusion, or other information from which human-readable forms can be derived. For example, the message may include a patient identifier, an infusion type identifier, a CCA identifier, a channel identifier, a line identifier, an auto-program reference identifier, other identifiers, some combination thereof, etc. - The
connectivity adapter 206 may receive the message from the infusion pump, and process the message at [B]. For example, theconnectivity adapter 206 may process the message into a standardized dataset message using generalized drug library data in thedata store 340. The generalized drug library data may include the name of the drug that corresponds to the identifier “13BSF68X,” the name of the CCA that corresponds to a CCA identifier, etc. - The
connectivity adapter 206 may therefore include the drug name, CCA name, etc. in the standardized dataset message without receiving the drug name, CCA name, and the like from theinfusion pump 204. Theconnectivity adapter 206 may send the standardized dataset message to thecloud environment 106 at [C]. - The
infusion pump 204 may send a second message to theconnectivity adapter 206 at [D]. The second message may relate to a past event at theinfusion pump 204, such as an infusion occurring days earlier when a different version of customized drug library data was being used by theinfusion pump 204. For example, when thecloud environment 106 received the standardized dataset message at [C], it may have determined that a prior message had not been received (e.g., by inspecting a sequential message identifier in the message). Thecloud environment 106 may then have initiated a process to obtain the missing message, and as a result theinfusion pump 204 re-sent (or sent for the first time) the message to theconnectivity adapter 206 at [D]. - The
connectivity adapter 206 can begin processing the second message at [E]. However, the infusion that is the subject of the message occurred when theinfusion pump 204 was using an older version of the customized drug library data. Therefore, the message may include information (e.g., an identifier) that theconnectivity adapter 206 is unable to resolve by referencing the generalized drug library data currently present in thedata store 340, because generalized drug library data currently present in thedata store 340 corresponds to the current customized drug library data used by theinfusion pump 204. In this instance, theconnectivity adapter 206 may retrieve, from thecloud environment 106 at [F], an archived version of the generalized drug library data that corresponds to the customized drug library data used by theinfusion pump 204 when the second message was originally generated. - The
connectivity adapter 206 may proceed with processing the second message at [G] into a standardized dataset message using the archived version of generalized drug library data. For example, theconnectivity adapter 206 may determine the drug name using the identifier and the archived version of the generalized drug library data and proceed with processing the second message at [G] into a standardized dataset message that includes the drug name. Theconnectivity adapter 206 may then send a second standardized dataset message to thecloud environment 106 at [H]. - Embodiments of the present disclosure can be defined by the following non-limiting clauses:
- Clause 1: A system configured to manage a drug library within a clinical environment, the system comprising:
-
- a plurality of infusion pumps configured to deliver medication to one or more patients, each respective infusion pump of the plurality of infusion pumps comprising a memory configured to store drug library data;
- a drug library manager comprising one or more computer processors and memory, the drug library manager configured to:
- receive, from a user device, first input data representing one or more medications;
- receive, from the user device, second input data representing one or more administration rules, wherein the second input data comprises:
- data representing a medication of the one or more medications;
- data representing an infusion pump type of a plurality of infusion pump types; and
- data representing one or more medication administration parameters;
- receive, from the user device, third input data representing one or more clinical care areas, wherein the third input data comprises:
- data representing one or more clinical care area settings; and
- data representing an association of a clinical care area with zero or more administration rules
- receive, from the user device, fourth input data representing selection of a first clinical care area of the one or more clinical care areas; store, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
- a first reference to infusion pump data in the drug library database, the infusion pump data representing the first infusion pump type; and
- a second reference to clinical care area data in the drug library database, the clinical care area data representing the first clinical care area;
- generate customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules of the subset of administration rules are associated with individual medications of the subset of medications;
- generate generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules;
- provide, to a first infusion pump of the plurality of infusion pumps, the customized drug library data, wherein the first infusion pump is associated with the first infusion pump type, and wherein a second infusion pump of the plurality of infusion pumps is not provided with the customized drug library data, the second infusion pump associated with a second infusion pump type; and
- provide, to a connectivity adapter in communication with the first infusion pump and the second infusion pump, the generalized drug library data.
- Clause 2: The system of Clause 1, wherein the first infusion pump is configured to replace, in memory of the first infusion pump, a prior version of customized drug library data with the customized drug library data.
- Clause 3: The system of Clause 1, wherein the first infusion pump is configured to:
-
- display infusion data comprising a medication name; and
- transmit an infusion message to the connectivity adapter, wherein the infusion message comprises a medication identifier and does not comprise the medication name.
- Clause 4: The system of Clause 3, wherein the connectivity adapter is configured to at least:
-
- receive, from the first infusion pump, the infusion message; and
- determine the medication name using the medication identifier and the generalized drug library data.
- Clause 5: The system of Clause 4, wherein the connectivity adapter is further configured to at least:
-
- receive, from the second infusion pump, a second infusion message comprising a second mediation identifier; and
- determine a second medication name using the second medication identifier and second generalized drug library data associated with the second infusion pump.
- Clause 6: The system of Clause 1, wherein:
-
- an administration rule of the subset of administration rules is associated with a medication of the subset of medications;
- the administration rule is associated with a first upper dosing limit;
- the first clinical care area is associated with a second upper dosing limit that is lower than the first upper dosing limit; and
- the second upper dosing limit overrides the first upper dosing limit during administration of the medication by the first infusion pump.
- Clause 7: The system of Clause 1, wherein:
-
- an administration rule of the subset of administration rules is associated with a medication of the subset of medications;
- the administration rule is associated with a first upper dosing limit;
- the first clinical care area is associated with a second upper dosing limit that is higher than the first upper dosing limit; and
- the first upper dosing limit is implemented during administration of the medication by the first infusion pump.
- Clause 8: The system of Clause 1, wherein the drug library manager is further configured to at least:
-
- receive, from the user device, input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and
- store, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.
- Clause 9: The system of Clause 1, wherein the connectivity adapter is configured to at least:
-
- receive, from the first infusion pump, an infusion message associated with a prior version of customized drug library data;
- obtain a prior version of generalized drug library data that corresponds to the prior version of customized drug library data; and
- process the infusion message using the prior version of generalized drug library data.
- Clause 10: The system of Clause 1, wherein the drug library manager is further configured to at least:
-
- store status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and
- receive, from the user device, input indicating a change in status of the worksheet data, wherein the customized drug library data and generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.
- Clause 11: The system of Clause 1, further comprising a drug library archive, wherein the drug library manager is further configured to provide the generalized drug library data to the drug library archive, and wherein the drug library archive is configured to store a plurality of versions of generalized drug library data for each of a plurality of different drug libraries.
- Clause 12: The system of Clause 11, wherein the drug library manager is further configured to:
-
- compare the generalized drug library data to one of: second generalized drug library data or second worksheet data; and
- generate user interface data for displaying a difference based on comparing the generalized drug library data.
- Clause 13: A computer-implemented method comprising:
-
- under control of one or more computing devices configured with specific computer-executable instructions,
- storing, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
- a first reference to infusion pump data in the drug library database, the infusion pump data representing a first infusion pump type of a plurality of infusion pump types; and
- a second reference to clinical care area data in the drug library database, the clinical care area data representing a first clinical care area of a plurality of clinical care areas;
- generating customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules of the subset of administration rules are associated with individual medications of the subset of medications;
- generating generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules;
- providing the customized drug library data to an infusion pump associated with the first infusion pump type; and
- providing the generalized drug library data to a computing system in communication with the infusion pump.
- storing, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
- under control of one or more computing devices configured with specific computer-executable instructions,
- Clause 14: The computer-implemented method of Clause 13, further comprising:
-
- accessing archived generalized drug library data corresponding to a prior version of the worksheet data;
- comparing the generalized drug library data to the archived generalized drug library data; and
- presenting a user interface displaying a difference between the generalized drug library data and the archived generalized drug library data.
- Clause 15: The computer-implemented method of Clause 13, further comprising:
-
- receiving input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and
- storing, in the drug library database, administration rule data representing the selection, wherein the administration rule references medication data representing the medication.
- Clause 16: The computer-implemented method of Clause 13, further comprising:
-
- storing status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and
- receiving input indicating a change in status of the worksheet data, wherein the customized drug library data and generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.
- Clause 17: The computer-implemented method of Clause 13, further comprising providing the generalized drug library data to a drug library archive configured to store a plurality of versions generalized drug library data for each of a plurality of different drug libraries.
- Clause 18: The computer-implemented method of Clause 13, wherein generating the generalized drug library data comprises formatting the generalized drug library data using JavaScript Object Notation.
- Clause 19: A system comprising:
-
- a computer-readable memory storing executable instructions; and
- one or more processors in communication with the computer-readable memory, wherein the one or more processors are programmed by the executable instructions to at least:
- store, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
- a first reference to infusion pump data in the drug library database, the infusion pump data representing a first infusion pump type of a plurality of infusion pump types; and
- a second reference to clinical care area data in the drug library database, the clinical care area data representing a first clinical care area of a plurality of clinical care areas;
- generate customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules of the subset of administration rules are associated with individual medications of the subset of medications;
- generate generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules;
- provide the customized drug library data to an infusion pump associated with the first infusion pump type; and
- provide the generalized drug library data to a connectivity adapter in communication with the infusion pump.
- store, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
- Clause 20: The system of Clause 19, further comprising the connectivity adapter, wherein the connectivity adapter is configured to at least:
-
- receive, from the infusion pump, a first infusion message comprising a medication identifier that corresponds to a medication infused by the infusion pump;
- determine a medication name using the medication identifier and the generalized drug library data;
- receive, from the infusion pump, a second infusion message associated with a prior version of customized drug library data;
- obtain a prior version of generalized drug library data that corresponds to the prior version of customized drug library data; and process the second infusion message using the prior version of generalized drug library data.
- Clause 21: A system comprising:
-
- computer-readable storage; and
- one or more computer processors configured to at least:
- receive customized drug library data formatted according to a pump-specific format associated with a first infusion pump type, wherein the customized drug library data represents a plurality of medications and a plurality of administration rules, and wherein individual administration rules of the plurality of administration rules are associated with individual medications of the plurality of medications;
- receive generalized drug library data, wherein the generalized drug library data represents the plurality of medications and the plurality of administration rules;
- send the customized drug library data to an infusion pump associated with the first infusion pump type;
- store the generalized drug library data in the computer-readable storage, wherein a prior version of the generalized drug library data is stored in the computer-readable storage;
- receive, from the infusion pump, a first infusion message comprising a first medication identifier that corresponds to a first medication infused by the infusion pump;
- determine a first medication name using the first medication identifier and the generalized drug library data;
- receive, from the infusion pump, a second infusion message associated with a prior version of customized drug library data, the second infusion message comprising a second medication identifier that corresponds to a second medication infused by the infusion pump; and
- determine a second medication name using the second medication identifier and the prior version of generalized drug library data.
- Clause 22: The system of Clause 21, further comprising the infusion pump, wherein the infusion pump is configured to replace, in memory of the infusion pump, a prior version of customized drug library data with the customized drug library data.
- Clause 23: The system of Clause 22, wherein the infusion pump is configured to:
-
- display infusion data comprising the first medication name; and
- transmit the first infusion message to a connectivity adapter comprising the one or more processors, wherein the first infusion message comprises the first medication identifier and does not comprise the first medication name.
- Clause 24: The system of Clause 22, wherein the infusion pump is configured to:
-
- display infusion data comprising a clinical care area name; and
- transmit the first infusion message to a connectivity adapter comprising the one or more processors, wherein the first infusion message comprises a clinical care area identifier and does not comprise the clinical care area name.
- Clause 25: The system of Clause 21, wherein the one or more processors are further configured to at least:
-
- receive, from a second infusion pump, a third infusion message comprising a third mediation identifier, wherein the second infusion pump is associated with a second infusion pump type; and
- determine a third medication name using the third medication identifier and second generalized drug library data.
- Clause 26: The system of Clause 21, wherein:
-
- an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
- the administration rule comprises a first upper dosing limit;
- the clinical care area is associated with a second upper dosing limit that is lower than the first upper dosing limit; and
- the second upper dosing limit overrides the first upper dosing limit during administration of the first medication by the infusion pump.
- Clause 27: The system of Clause 21, wherein:
-
- an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
- the administration rule comprises a first upper dosing limit;
- the clinical care area is associated with a second upper dosing limit that is higher than the first upper dosing limit; and
- the first upper dosing limit is implemented during administration of the first medication by the infusion pump.
- Clause 28: A computer-implemented method comprising:
-
- under control of one or more computing devices configured with specific computer-executable instructions,
- receiving customized drug library data formatted according to a pump-specific format associated with a first infusion pump type, wherein the customized drug library data represents a plurality of medications and a plurality of administration rules, and wherein individual administration rules of the plurality of administration rules are associated with individual medications of the plurality of medications;
- receiving generalized drug library data, wherein the generalized drug library data represents the plurality of medications and the plurality of administration rules;
- sending the customized drug library data to an infusion pump associated with the first infusion pump type;
- storing the generalized drug library data in a computer-readable storage, wherein a prior version of the generalized drug library data is stored in the computer-readable storage;
- receiving, from the infusion pump, a first infusion message comprising a first medication identifier that corresponds to a first medication infused by the infusion pump;
- processing the first infusion message using the first medication identifier and the generalized drug library data;
- receiving, from the infusion pump, a second infusion message associated with a prior version of customized drug library data, the second infusion message comprising a second medication identifier that corresponds to a second medication infused by the infusion pump; and
- processing the second infusion message using the second medication identifier and the prior version of generalized drug library data.
- under control of one or more computing devices configured with specific computer-executable instructions,
- Clause 29: The computer-implemented method of Clause 28, wherein processing the first infusion message comprises determining a first medication name using the first medication identifier and the generalized drug library data.
- Clause 30: The computer-implemented method of Clause 28, wherein processing the second infusion message comprises determining a second medication name using the second medication identifier and the generalized drug library data.
- Clause 31: The computer-implemented method of Clause 28, wherein sending the customized drug library data to the infusion pump cases the infusion pump to replace, in memory of the infusion pump, a prior version of customized drug library data with the customized drug library data.
- Clause 32: The computer-implemented method of Clause 31, further comprising:
-
- displaying, by the infusion pump, infusion data comprising the first medication name; and
- generating, by the infusion pump, the first infusion message, wherein the first infusion message comprises the first medication identifier and does not comprise the first medication name.
- Clause 33: The computer-implemented method of Clause 28, further comprising:
-
- receiving, from a second infusion pump, a third infusion message comprising a third mediation identifier, wherein the second infusion pump is associated with a second infusion pump type; and
- processing the third medication identifier and second generalized drug library data.
- Clause 34: The computer-implemented method of Clause 28, wherein:
-
- an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
- the administration rule comprises a first upper dosing limit;
- the clinical care area is associated with a second upper dosing limit that is lower than the first upper dosing limit; and
- the second upper dosing limit overrides the first upper dosing limit during administration of the first medication by the infusion pump.
- Clause 35: The computer-implemented method of Clause 28, wherein:
-
- an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
- the administration rule comprises a first upper dosing limit;
- the clinical care area is associated with a second upper dosing limit that is higher than the first upper dosing limit; and
- the first upper dosing limit is implemented during administration of the first medication by the infusion pump.
- Clause 36: A non-transitory computer storage medium that stores an executable component that directs a computing system to perform a process comprising:
-
- receiving customized drug library data formatted according to a pump-specific format associated with a first infusion pump type, wherein the customized drug library data represents a plurality of medications and a plurality of administration rules, and wherein individual administration rules of the plurality of administration rules are associated with individual medications of the plurality of medications;
- receiving generalized drug library data, wherein the generalized drug library data represents the plurality of medications and the plurality of administration rules;
- sending the customized drug library data to an infusion pump associated with the first infusion pump type;
- storing the generalized drug library data in a computer-readable storage, wherein a prior version of the generalized drug library data is stored in the computer-readable storage;
- receiving, from the infusion pump, a first infusion message comprising a first medication identifier that corresponds to a first medication infused by the infusion pump;
- processing the first infusion message using the first medication identifier and the generalized drug library data;
- receiving, from the infusion pump, a second infusion message associated with a prior version of customized drug library data, the second infusion message comprising a second medication identifier that corresponds to a second medication infused by the infusion pump; and
- processing the second infusion message using the second medication identifier and the prior version of generalized drug library data.
- Clause 37: The non-transitory computer storage medium of Clause 36, wherein processing the first infusion message comprises determining a first medication name using the first medication identifier and the generalized drug library data, and wherein processing the second infusion message comprises determining a second medication name using the second medication identifier and the generalized drug library data.
- Clause 38: The non-transitory computer storage medium of Clause 36, the process further comprising:
-
- receiving, from a second infusion pump, a third infusion message comprising a third mediation identifier, wherein the second infusion pump is associated with a second infusion pump type; and
- processing the third medication identifier and second generalized drug library data.
- Clause 39: The non-transitory computer storage medium of Clause 36, wherein:
-
- an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
- the administration rule comprises a first upper dosing limit;
- the clinical care area is associated with a second upper dosing limit that is lower than the first upper dosing limit; and
- the second upper dosing limit overrides the first upper dosing limit during administration of the first medication by the infusion pump.
- Clause 40: The non-transitory computer storage medium of Clause 36, wherein:
-
- an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
- the administration rule comprises a first upper dosing limit;
- the clinical care area is associated with a second upper dosing limit that is higher than the first upper dosing limit; and
- the first upper dosing limit is implemented during administration of the first medication by the infusion pump.
- It is to be understood that not necessarily all objects or advantages may be achieved in accordance with any particular embodiment described herein. Thus, for example, those skilled in the art will recognize that certain embodiments may be configured to operate in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other objects or advantages as may be taught or suggested herein.
- Many other variations than those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. In addition, different tasks or processes can be performed by different machines and/or computing systems that can function together.
- The various illustrative logical blocks, modules, and algorithm elements described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and elements have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
- The various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a processor includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor may also include primarily analog components. For example, some or all of the signal processing algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
- The elements of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module stored in one or more memory devices and executed by one or more processors, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art. An example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The storage medium can be volatile or nonvolatile. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.
- Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Further, the term “each,” as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term “each” is applied.
- Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.
- Unless otherwise explicitly stated, articles such as “a”, “an”, or “the” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B, and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.
- While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain embodiments described herein can be implemented within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. All such modifications and variations are intended to be included herein within the scope of this disclosure. Further, additional embodiments created by combining any two or more features or techniques of one or more embodiments described herein are also intended to be included herein within the scope of this disclosure.
Claims (21)
1-20. (canceled)
21. A computer-implemented method comprising:
under control of one or more computing devices configured with specific computer-executable instructions,
storing, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
a first reference to infusion pump data in the drug library database representing a first infusion pump type of a plurality of infusion pump types; and
a second reference to clinical care area data in the drug library database representing a first clinical care area of a plurality of clinical care areas;
generating customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules are associated with individual medications;
generating generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules, and wherein the generalized drug library data is different from the customized drug library data;
providing the customized drug library data to an infusion pump associated with the first infusion pump type; and
providing the generalized drug library data to a computing system in communication with the infusion pump.
22. The computer-implemented method of claim 21 , further comprising:
receiving an infusion message from the infusion pump, wherein the infusion pump is configured to display infusion data comprising a medication name, and transmit the infusion message comprising a medication identifier and not comprising the medication name; and
determining the medication name using the medication identifier and the generalized drug library data.
23. The computer-implemented method of claim 22 , further comprising:
receiving, from a second infusion pump, a second infusion message comprising a second medication identifier; and
determining a second medication name using the second medication identifier and second generalized drug library data associated with the second infusion pump, wherein the second infusion pump is associated with a second infusion pump type of the plurality of infusion pump types.
24. The computer-implemented method of claim 21 , further comprising:
receiving, from a user device, input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and
storing, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.
25. The computer-implemented method of claim 21 , further comprising:
storing status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and
receiving, from a user device, input indicating a change in status of the worksheet data, wherein the customized drug library data and the generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.
26. The computer-implemented method of claim 21 , further comprising providing the generalized drug library data to a drug library archive, wherein the drug library archive is configured to store a plurality of versions of generalized drug library data for each of a plurality of different drug libraries.
27. The computer-implemented method of claim 21 , further comprising:
accessing archived generalized drug library data corresponding to a prior version of the worksheet data;
comparing the generalized drug library data to the archived generalized drug library data; and
presenting a user interface displaying a difference between the generalized drug library data and the archived generalized drug library data.
28. The computer-implemented method of claim 21 , further comprising:
receiving input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and
storing, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.
29. The computer-implemented method of claim 21 , further comprising:
storing status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and
receiving input indicating a change in status of the worksheet data, wherein the customized drug library data and the generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.
30. The computer-implemented method of claim 21 , wherein generating the generalized drug library data comprises formatting the generalized drug library data using JavaScript Object Notation.
31. A system comprising:
a computer-readable memory storing executable instructions; and
one or more processors in communication with the computer-readable memory and programmed by the executable instructions to:
store, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
a first reference to infusion pump data in the drug library database representing a first infusion pump type of a plurality of infusion pump types; and
a second reference to clinical care area data in the drug library database representing a first clinical care area of a plurality of clinical care areas;
generate customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules are associated with individual medications;
generate generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules, and wherein the generalized drug library data is different from the customized drug library data;
provide the customized drug library data to an infusion pump associated with the first infusion pump type; and
provide the generalized drug library data to a computing system in communication with the infusion pump.
32. The system of claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
receive an infusion message from the infusion pump, wherein the infusion pump is configured to display infusion data comprising a medication name, and transmit the infusion message comprising a medication identifier and not comprising the medication name; and
determine the medication name using the medication identifier and the generalized drug library data.
33. The system of claim 32 , wherein the one or more processors are further programmed by the executable instructions to:
receive, from a second infusion pump, a second infusion message comprising a second medication identifier; and
determine a second medication name using the second medication identifier and second generalized drug library data associated with the second infusion pump, wherein the second infusion pump is associated with a second infusion pump type of the plurality of infusion pump types.
34. The system of claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
receive, from a user device, input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and
store, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.
35. The system of claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
store status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and
receive, from a user device, input indicating a change in status of the worksheet data, wherein the customized drug library data and the generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.
36. The system of claim 31 , wherein the one or more processors are further programmed by the executable instructions to provide the generalized drug library data to a drug library archive, wherein the drug library archive is configured to store a plurality of versions of generalized drug library data for each of a plurality of different drug libraries.
37. The system of claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
access archived generalized drug library data corresponding to a prior version of the worksheet data;
compare the generalized drug library data to the archived generalized drug library data; and
present a user interface displaying a difference between the generalized drug library data and the archived generalized drug library data.
38. The system of claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
receive input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and
store, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.
39. The system of claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
store status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and
receiving input indicating a change in status of the worksheet data, wherein the customized drug library data and the generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.
40. The system of claim 31 , wherein the generalized drug library data comprises JavaScript Object Notation data.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/929,654 US20230009417A1 (en) | 2018-07-26 | 2022-09-02 | Drug library dynamic version management |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862703772P | 2018-07-26 | 2018-07-26 | |
PCT/US2019/041715 WO2020023231A1 (en) | 2018-07-26 | 2019-07-12 | Drug library management system |
US16/512,266 US10692595B2 (en) | 2018-07-26 | 2019-07-15 | Drug library dynamic version management |
US16/908,539 US11437132B2 (en) | 2018-07-26 | 2020-06-22 | Drug library dynamic version management |
US17/929,654 US20230009417A1 (en) | 2018-07-26 | 2022-09-02 | Drug library dynamic version management |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/908,539 Continuation US11437132B2 (en) | 2018-07-26 | 2020-06-22 | Drug library dynamic version management |
Publications (1)
Publication Number | Publication Date |
---|---|
US20230009417A1 true US20230009417A1 (en) | 2023-01-12 |
Family
ID=69182389
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/512,243 Active US11309070B2 (en) | 2018-07-26 | 2019-07-15 | Drug library manager with customized worksheets |
US17/659,454 Pending US20220384059A1 (en) | 2018-07-26 | 2022-04-15 | Drug library manager with customized worksheets |
US17/929,654 Pending US20230009417A1 (en) | 2018-07-26 | 2022-09-02 | Drug library dynamic version management |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/512,243 Active US11309070B2 (en) | 2018-07-26 | 2019-07-15 | Drug library manager with customized worksheets |
US17/659,454 Pending US20220384059A1 (en) | 2018-07-26 | 2022-04-15 | Drug library manager with customized worksheets |
Country Status (8)
Country | Link |
---|---|
US (3) | US11309070B2 (en) |
EP (1) | EP3827337A4 (en) |
AU (1) | AU2019309766A1 (en) |
CA (1) | CA3107315C (en) |
CO (1) | CO2021000838A2 (en) |
TW (1) | TWI821335B (en) |
WO (1) | WO2020023231A1 (en) |
ZA (1) | ZA202100262B (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11881297B2 (en) | 2018-07-17 | 2024-01-23 | Icu Medical, Inc. | Reducing infusion pump network congestion by staggering updates |
US11923076B2 (en) | 2018-07-17 | 2024-03-05 | Icu Medical, Inc. | Converting pump messages in new pump protocol to standardized dataset messages |
Families Citing this family (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8065161B2 (en) | 2003-11-13 | 2011-11-22 | Hospira, Inc. | System for maintaining drug information and communicating with medication delivery devices |
DK1762259T3 (en) | 2005-09-12 | 2011-01-03 | Unomedical As | Infusion set insertion device with a first and a second spring assembly |
JP2010507176A (en) | 2006-10-16 | 2010-03-04 | ホスピラ・インコーポレイテツド | System and method for comparing and utilizing dynamic information and configuration information from multiple device management systems |
US8271106B2 (en) | 2009-04-17 | 2012-09-18 | Hospira, Inc. | System and method for configuring a rule set for medical event management and responses |
US10194938B2 (en) | 2011-03-14 | 2019-02-05 | UnoMedical, AS | Inserter system with transport protection |
WO2013059615A1 (en) | 2011-10-21 | 2013-04-25 | Hospira, Inc. | Medical device update system |
EP2964079B1 (en) | 2013-03-06 | 2022-02-16 | ICU Medical, Inc. | Medical device communication method |
CA2922425C (en) | 2013-08-30 | 2023-05-16 | Hospira, Inc. | System and method of monitoring and managing a remote infusion regimen |
US10311972B2 (en) | 2013-11-11 | 2019-06-04 | Icu Medical, Inc. | Medical device system performance index |
EP3071253B1 (en) | 2013-11-19 | 2019-05-22 | ICU Medical, Inc. | Infusion pump automation system and method |
WO2015168427A1 (en) | 2014-04-30 | 2015-11-05 | Hospira, Inc. | Patient care system with conditional alarm forwarding |
US9724470B2 (en) | 2014-06-16 | 2017-08-08 | Icu Medical, Inc. | System for monitoring and delivering medication to a patient and method of using the same to minimize the risks associated with automated therapy |
US9539383B2 (en) | 2014-09-15 | 2017-01-10 | Hospira, Inc. | System and method that matches delayed infusion auto-programs with manually entered infusion programs and analyzes differences therein |
ES2845725T3 (en) | 2015-05-26 | 2021-07-27 | Icu Medical Inc | Infusion pump system and method with multiple drug library editor source capability |
EP3484541A4 (en) | 2016-07-14 | 2020-03-25 | ICU Medical, Inc. | Multi-communication path selection and security system for a medical device |
JP7346309B2 (en) * | 2017-08-31 | 2023-09-19 | バイエル・ヘルスケア・エルエルシー | Fluid path impedance assessment to improve fluid delivery performance |
US10741280B2 (en) | 2018-07-17 | 2020-08-11 | Icu Medical, Inc. | Tagging pump messages with identifiers that facilitate restructuring |
US10861592B2 (en) | 2018-07-17 | 2020-12-08 | Icu Medical, Inc. | Reducing infusion pump network congestion by staggering updates |
US10692595B2 (en) | 2018-07-26 | 2020-06-23 | Icu Medical, Inc. | Drug library dynamic version management |
EP3972672A4 (en) | 2019-05-20 | 2023-06-21 | Unomedical A/S | Rotatable infusion device and methods thereof |
EP4107745A1 (en) * | 2020-02-20 | 2022-12-28 | Fresenius Vial SAS | System for administering a medical fluid to a patient |
US20230061020A1 (en) * | 2021-08-26 | 2023-03-02 | Evernorth Strategic Development, Inc. | Systems and methods for transforming an interactive graphical user interface according to dynamically generated data structures |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060026205A1 (en) * | 2004-07-30 | 2006-02-02 | Butterfield Robert D | System and method for managing medical databases for patient care devices |
US20080091466A1 (en) * | 2006-10-16 | 2008-04-17 | Hospira, Inc. | System and method for comparing and utilizing activity information and configuration information from multiple device management systems |
US20120066609A1 (en) * | 2003-11-13 | 2012-03-15 | Hospira, Inc. | System for maintaining drug information and communicating with medication delivery devices |
US8486019B2 (en) * | 1999-12-01 | 2013-07-16 | B. Braun Medical, Inc. | Patient medication IV delivery pump with wireless communication to a hospital information management system |
US20140180711A1 (en) * | 2010-01-22 | 2014-06-26 | Deka Products Limited Partnership | Computer-Implemented Method, System, and Apparatus for Electronic Patient Care |
US20170258986A1 (en) * | 2016-03-11 | 2017-09-14 | Micrel Medical Devices S.A. | Pump Infusion System |
Family Cites Families (1044)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6241704B1 (en) | 1901-11-22 | 2001-06-05 | Sims Deltec, Inc. | Drug pump systems and methods |
US5935099A (en) | 1992-09-09 | 1999-08-10 | Sims Deltec, Inc. | Drug pump systems and methods |
US5669877A (en) | 1994-03-07 | 1997-09-23 | Sims Deltec, Inc. | Systems and methods for automated testing of medical equipment |
US5338157B1 (en) | 1992-09-09 | 1999-11-02 | Sims Deltec Inc | Systems and methods for communicating with ambulat |
US4370983A (en) | 1971-01-20 | 1983-02-01 | Lichtenstein Eric Stefan | Computer-control medical care system |
US4024864A (en) | 1975-09-05 | 1977-05-24 | Cordis Corporation | Injector with overspeed protector |
US4055175A (en) | 1976-05-07 | 1977-10-25 | Miles Laboratories, Inc. | Blood glucose control apparatus |
US4151845A (en) | 1977-11-25 | 1979-05-01 | Miles Laboratories, Inc. | Blood glucose control apparatus |
US4213454A (en) | 1977-12-02 | 1980-07-22 | Baxter Travenol Laboratories, Inc. | Control system for metering apparatus for a fluid infusion system |
US4559037A (en) | 1977-12-28 | 1985-12-17 | Siemens Aktiengesellschaft | Device for the pre-programmable infusion of liquids |
US4240438A (en) | 1978-10-02 | 1980-12-23 | Wisconsin Alumni Research Foundation | Method for monitoring blood glucose levels and elements |
US4308866A (en) | 1978-11-02 | 1982-01-05 | University Of Southern California | Infusion controlling apparatus and method |
US4731051A (en) | 1979-04-27 | 1988-03-15 | The Johns Hopkins University | Programmable control means for providing safe and controlled medication infusion |
US4373527B1 (en) | 1979-04-27 | 1995-06-27 | Univ Johns Hopkins | Implantable programmable medication infusion system |
US4619653A (en) | 1979-04-27 | 1986-10-28 | The Johns Hopkins University | Apparatus for detecting at least one predetermined condition and providing an informational signal in response thereto in a medication infusion system |
US4280494A (en) | 1979-06-26 | 1981-07-28 | Cosgrove Robert J Jun | System for automatic feedback-controlled administration of drugs |
DE3018641C2 (en) | 1980-05-16 | 1986-05-28 | Hans 8228 Freilassing Rodler | Automatic infusion pump |
AU546785B2 (en) | 1980-07-23 | 1985-09-19 | Commonwealth Of Australia, The | Open-loop controlled infusion of diabetics |
DE3035670A1 (en) | 1980-09-22 | 1982-04-29 | Siemens AG, 1000 Berlin und 8000 München | DEVICE FOR INFUSING LIQUIDS IN HUMAN OR ANIMAL BODIES |
DE3112762A1 (en) | 1981-03-31 | 1983-01-13 | Jürgen Dr.med. 8700 Würzburg Schrezenmeir | Double-lumen blood sampling, single-lumen infusion, subclavian catheter set |
JPS57211361A (en) | 1981-06-23 | 1982-12-25 | Terumo Corp | Liquid injecting apparatus |
US4392849A (en) | 1981-07-27 | 1983-07-12 | The Cleveland Clinic Foundation | Infusion pump controller |
US4529401A (en) | 1982-01-11 | 1985-07-16 | Cardiac Pacemakers, Inc. | Ambulatory infusion pump having programmable parameters |
US4494950A (en) | 1982-01-19 | 1985-01-22 | The Johns Hopkins University | Plural module medication delivery system |
US4515584A (en) | 1982-07-06 | 1985-05-07 | Fujisawa Pharmaceutical Co., Ltd. | Artificial pancreas |
US4498843A (en) | 1982-08-02 | 1985-02-12 | Schneider Philip H | Insulin infusion pump |
US4464170A (en) | 1982-09-29 | 1984-08-07 | Miles Laboratories, Inc. | Blood glucose control apparatus and method |
US4526568A (en) | 1982-09-29 | 1985-07-02 | Miles Laboratories, Inc. | Diagnostic method and apparatus for clamping blood glucose concentration |
EP0107150B2 (en) | 1982-10-18 | 1992-04-15 | Siemens Aktiengesellschaft | Medicine-delivering apparatus |
US4624661A (en) | 1982-11-16 | 1986-11-25 | Surgidev Corp. | Drug dispensing system |
US4553958A (en) | 1983-02-04 | 1985-11-19 | Quest Medical, Inc. | IV Delivery controller |
US4679562A (en) | 1983-02-16 | 1987-07-14 | Cardiac Pacemakers, Inc. | Glucose sensor |
IT1170375B (en) | 1983-04-19 | 1987-06-03 | Giuseppe Bombardieri | Implantable device for measuring body fluid parameters |
US4543955A (en) | 1983-08-01 | 1985-10-01 | Cordis Corporation | System for controlling body implantable action device |
US4953745A (en) | 1983-09-19 | 1990-09-04 | James R. Rowlett, Jr. | Medication dispensing apparatus |
DD230730A3 (en) | 1984-01-02 | 1985-12-11 | Zentralinstitut Fuer Diabetes | DEVICE FOR THE PROSPECTIVE AUTOMATIC DETERMINATION OF INDIVIDUAL-SPECIFIC GLUCOSE REGULATION PARAMETERS |
US4685903A (en) | 1984-01-06 | 1987-08-11 | Pacesetter Infusion, Ltd. | External infusion pump apparatus |
US4854324A (en) | 1984-01-31 | 1989-08-08 | Medrad, Inc. | Processor-controlled angiographic injector device |
CA1257165A (en) | 1984-02-08 | 1989-07-11 | Paul Epstein | Infusion system having plural fluid input ports and at least one patient output port |
US5100380A (en) | 1984-02-08 | 1992-03-31 | Abbott Laboratories | Remotely programmable infusion system |
US4613937A (en) | 1984-02-22 | 1986-09-23 | Cordis Corporation | Method for externally programming a device implanted in a patient |
ATE37661T1 (en) | 1984-04-14 | 1988-10-15 | Ferring Biotechnik | DEVICE FOR INTERMITTENT APPLICATION OF LIQUID MEDICATIONS. |
US4551133A (en) | 1984-04-16 | 1985-11-05 | American Hospital Supply Corporation | Patient controlled medication infusion system |
US4741732A (en) | 1984-05-10 | 1988-05-03 | The University Of Melbourne | Open-loop control of drug infusion |
US4634427A (en) | 1984-09-04 | 1987-01-06 | American Hospital Supply Company | Implantable demand medication delivery assembly |
US4695954A (en) | 1984-10-31 | 1987-09-22 | Rose Robert J | Modular medication dispensing system and apparatus utilizing portable memory device |
US4885778A (en) | 1984-11-30 | 1989-12-05 | Weiss Kenneth P | Method and apparatus for synchronizing generation of separate, free running, time dependent equipment |
US4634426A (en) | 1984-12-11 | 1987-01-06 | Baxter Travenol Laboratories | Medical infusion controller and user interface |
US5088981A (en) | 1985-01-18 | 1992-02-18 | Howson David C | Safety enhanced device and method for effecting application of a therapeutic agent |
US4676776A (en) | 1985-01-18 | 1987-06-30 | Intelligent Medicine, Inc. | Device and method for effecting application of a therapeutic agent |
US4756706A (en) | 1985-01-23 | 1988-07-12 | American Hospital Supply Corporation | Centrally managed modular infusion pump system |
US4674652A (en) | 1985-04-11 | 1987-06-23 | Aten Edward M | Controlled dispensing device |
US4908017A (en) | 1985-05-14 | 1990-03-13 | Ivion Corporation | Failsafe apparatus and method for effecting syringe drive |
US4838857A (en) | 1985-05-29 | 1989-06-13 | Becton, Dickinson And Company | Medical infusion device |
US4835372A (en) | 1985-07-19 | 1989-05-30 | Clincom Incorporated | Patient care system |
US4838275A (en) | 1985-11-29 | 1989-06-13 | Lee Arnold St J | Home medical surveillance system |
US5364346A (en) | 1985-12-20 | 1994-11-15 | Schrezenmeir Juergen | Process for the continuous and discontinuous administration of insulin to the human body |
US4714462A (en) | 1986-02-03 | 1987-12-22 | Intermedics Infusaid, Inc. | Positive pressure programmable infusion pump |
US4858154A (en) | 1986-04-07 | 1989-08-15 | Coulter Electronics, Inc. | Interlaboratory quality assurance program |
US4857716A (en) | 1986-05-12 | 1989-08-15 | Clinicom Incorporated | Patient identification and verification system and method |
US4803625A (en) | 1986-06-30 | 1989-02-07 | Buddy Systems, Inc. | Personal health monitor |
US4785969A (en) | 1986-11-10 | 1988-11-22 | Pyxis Corporation | Medication dispensing system |
US5216597A (en) | 1987-05-01 | 1993-06-01 | Diva Medical Systems Bv | Diabetes therapy management system, apparatus and method |
EP0434672B1 (en) | 1987-06-19 | 1994-12-14 | The University Of Melbourne | Infusion pump |
US4838856A (en) | 1987-07-02 | 1989-06-13 | Truckee Meadows Research & Development | Fluid infusion flow control system |
US5014698A (en) | 1987-10-06 | 1991-05-14 | Leonard Bloom | Method of and system for monitoring and treating a malfunctioning heart |
US5041086A (en) | 1987-12-04 | 1991-08-20 | Pacesetter Infusion, Ltd. | Clinical configuration of multimode medication infusion system |
CA1324935C (en) | 1987-12-04 | 1993-12-07 | James L. Henke | Fluid delivery control and monitoring apparatus for a medication infusion system |
US4898578A (en) | 1988-01-26 | 1990-02-06 | Baxter International Inc. | Drug infusion system with calculator |
US4933873A (en) | 1988-05-12 | 1990-06-12 | Healthtech Services Corp. | Interactive patient assistance device |
US5142484A (en) | 1988-05-12 | 1992-08-25 | Health Tech Services Corporation | An interactive patient assistance device for storing and dispensing prescribed medication and physical device |
US5131816A (en) | 1988-07-08 | 1992-07-21 | I-Flow Corporation | Cartridge fed programmable ambulatory infusion pumps powered by DC electric motors |
US5000739A (en) | 1988-07-12 | 1991-03-19 | Pinewood Medical, Inc. | Programmable infusion pump |
US5249260A (en) | 1988-08-12 | 1993-09-28 | Hitachi, Ltd. | Data input system |
US4946439A (en) | 1988-08-15 | 1990-08-07 | Critikon, Inc. | Dual source parenteral infusion system with secondary infusion module |
US4943279A (en) | 1988-09-30 | 1990-07-24 | C. R. Bard, Inc. | Medical pump with infusion controlled by a detachable coded label |
US5190522A (en) | 1989-01-20 | 1993-03-02 | Institute Of Biocybernetics And Biomedical Engineering P.A.S. | Device for monitoring the operation of a delivery system and the method of use thereof |
CA2008243C (en) | 1989-01-25 | 2002-05-28 | Morris H. Shamos | Patient identification system |
US5193855A (en) | 1989-01-25 | 1993-03-16 | Shamos Morris H | Patient and healthcare provider identification system |
US5153827A (en) | 1989-01-30 | 1992-10-06 | Omni-Flow, Inc. | An infusion management and pumping system having an alarm handling system |
DE3905350A1 (en) | 1989-02-22 | 1990-09-06 | Braun Melsungen Ag | MEDICAL DEVICE WITH REDUNDANTLY CONTROLLED CONTROL UNIT FOR INFUSION THERAPY OR BLOOD TREATMENT |
JPH061152Y2 (en) | 1989-04-28 | 1994-01-12 | シャープ株式会社 | Infusion pump air detector |
US5016172A (en) | 1989-06-14 | 1991-05-14 | Ramp Comsystems, Inc. | Patient compliance and status monitoring system |
US5010473A (en) | 1989-08-31 | 1991-04-23 | Duke University | Method and apparatus for model-based control of an open-loop process |
US5084828A (en) | 1989-09-29 | 1992-01-28 | Healthtech Services Corp. | Interactive medication delivery system |
US4978335A (en) | 1989-09-29 | 1990-12-18 | Medex, Inc. | Infusion pump with bar code input to computer |
US5097505A (en) | 1989-10-31 | 1992-03-17 | Securities Dynamics Technologies, Inc. | Method and apparatus for secure identification and verification |
US5199439A (en) | 1990-01-16 | 1993-04-06 | Stanley Zimmerman | Medical statistical analyzing method |
US5104374A (en) | 1990-01-16 | 1992-04-14 | Bishko Jay R | Electronic fluid flow rate controller for controlling the infusion of intravenous drugs into a patient |
US5200891A (en) | 1990-01-17 | 1993-04-06 | Bruce A. Kehr | Electronic medication dispensing method |
US5109850A (en) | 1990-02-09 | 1992-05-05 | Massachusetts Institute Of Technology | Automatic blood monitoring for medication delivery method and apparatus |
WO1991016416A1 (en) | 1990-04-26 | 1991-10-31 | Markwell Medical Institute, Inc. | Wearable blood glucose monitor |
US5078683A (en) | 1990-05-04 | 1992-01-07 | Block Medical, Inc. | Programmable infusion system |
IT1246349B (en) | 1990-07-11 | 1994-11-17 | Healtech Sa | EQUIPMENT FOR THE DISPENSING OF CONTAINERS FOR MEDICAL USE PROVIDED WITH INDICATIONS FOR THE PERMANENT COMBINATION WITH A CERTAIN PATIENT |
US5157640A (en) | 1990-07-11 | 1992-10-20 | Backner Brian P | Medication alert watch and system |
AT398694B (en) | 1990-07-19 | 1995-01-25 | Avl Verbrennungskraft Messtech | DEVICE FOR DETERMINING THE CONCENTRATION OF AT LEAST ONE SUBSTANCE IN ORGANIC TISSUE |
US5465082A (en) | 1990-07-27 | 1995-11-07 | Executone Information Systems, Inc. | Apparatus for automating routine communication in a facility |
US5822544A (en) | 1990-07-27 | 1998-10-13 | Executone Information Systems, Inc. | Patient care and communication system |
US5594786A (en) | 1990-07-27 | 1997-01-14 | Executone Information Systems, Inc. | Patient care and communication system |
US6958706B2 (en) | 1990-07-27 | 2005-10-25 | Hill-Rom Services, Inc. | Patient care and communication system |
US5455851A (en) | 1993-07-02 | 1995-10-03 | Executone Information Systems, Inc. | System for identifying object locations |
US5161222A (en) | 1990-08-20 | 1992-11-03 | Human Microprocessing, Inc. | Software engine having an adaptable driver for interpreting variables produced by a plurality of sensors |
ATE175068T1 (en) | 1990-08-31 | 1999-01-15 | Gen Hospital Corp | SYSTEM FOR MANAGING MULTIPLE DEVICES, FOR EXAMPLE PORTABLE PATIENT MONITORING DEVICES IN A NETWORK |
US5261702A (en) | 1990-08-31 | 1993-11-16 | M M & K, Inc. | Daily medication management system |
US5026084A (en) | 1990-09-14 | 1991-06-25 | Gail Pasfield | Color care coded patient identification system |
JP2520047B2 (en) | 1990-10-25 | 1996-07-31 | 康裕 福井 | Patient monitoring system |
IT1244884B (en) | 1990-12-21 | 1994-09-13 | Healtech Sa | PROCEDURE AND EQUIPMENT FOR THE UNIQUE COMBINATION OF DRUGS CORRESPONDING TO A THERAPY PREDICTED TO A CERTAIN PATIENT |
US5373454A (en) | 1991-01-16 | 1994-12-13 | Honda Giken Kogyo Kabushiki Kaisha | Problem diagnosis system in pressure device control apparatus |
FR2673476B1 (en) | 1991-01-18 | 1996-04-12 | Gemplus Card Int | SECURE METHOD FOR LOADING MULTIPLE APPLICATIONS INTO A MICROPROCESSOR MEMORY CARD. |
US5256157A (en) | 1991-01-31 | 1993-10-26 | Baxter International Inc. | Automated infusion pump with replaceable memory cartridges |
DE69124083T2 (en) | 1991-01-31 | 1997-05-15 | Baxter Int | Automatic infusion pump with interchangeable data module |
US5256156A (en) | 1991-01-31 | 1993-10-26 | Baxter International Inc. | Physician closed-loop neuromuscular blocking agent system |
US5181910A (en) | 1991-02-28 | 1993-01-26 | Pharmacia Deltec, Inc. | Method and apparatus for a fluid infusion system with linearized flow rate change |
US5319355A (en) | 1991-03-06 | 1994-06-07 | Russek Linda G | Alarm for patient monitor and life support equipment system |
US5486286A (en) | 1991-04-19 | 1996-01-23 | Althin Medical, Inc. | Apparatus for performing a self-test of kidney dialysis membrane |
US5177993A (en) | 1991-07-22 | 1993-01-12 | Ivac Corporation | Air-in-line sensor |
DE69132536T2 (en) | 1991-08-21 | 2001-10-04 | Ibm | Connectionless ATM data services |
GB2260966B (en) | 1991-11-04 | 1994-12-21 | Danby Medical Ltd | Improvements in or relating to electronically controlled infusion devices and arrangements |
US5221268A (en) | 1991-12-06 | 1993-06-22 | Block Medical, Inc. | Multiple dose control apparatus |
US5244463A (en) | 1991-12-06 | 1993-09-14 | Block Medical, Inc. | Programmable infusion pump |
WO1993012828A1 (en) | 1991-12-20 | 1993-07-08 | Abbott Laboratories | Drug channel identification and security system for infusion and pumping systems |
AU3415893A (en) | 1991-12-20 | 1993-07-28 | Abbott Laboratories | Automated drug infusion system with autopriming |
US6850252B1 (en) | 1999-10-05 | 2005-02-01 | Steven M. Hoffberg | Intelligent electronic appliance system and method |
US5230061A (en) | 1992-01-02 | 1993-07-20 | The University Of Akron | Clause counter map inference engine |
IL104365A0 (en) | 1992-01-31 | 1993-05-13 | Gensia Pharma | Method and apparatus for closed loop drug delivery |
JP3071929B2 (en) | 1992-02-21 | 2000-07-31 | 株式会社東芝 | Medical support system and medical support method |
JPH0669992A (en) | 1992-03-30 | 1994-03-11 | American Teleph & Telegr Co <Att> | Housing unit capable of being discolored |
JPH05277181A (en) | 1992-04-03 | 1993-10-26 | Sharp Corp | Infusion device |
FR2690622B1 (en) | 1992-04-29 | 1995-01-20 | Chronotec | Programmable ambulatory infusion pump system. |
US5554013A (en) | 1992-05-01 | 1996-09-10 | Mcgaw, Inc. | Disposable cassette with negative head height fluid supply |
SE500122C2 (en) | 1992-08-27 | 1994-04-18 | Rudolf Valentin Sillen | Method and apparatus for individually controlled, adaptive medication |
US5330634A (en) | 1992-08-28 | 1994-07-19 | Via Medical Corporation | Calibration solutions useful for analyses of biological fluids and methods employing same |
US6283761B1 (en) | 1992-09-08 | 2001-09-04 | Raymond Anthony Joao | Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information |
US5788669A (en) | 1995-11-22 | 1998-08-04 | Sims Deltec, Inc. | Pump tracking system |
US5376070A (en) | 1992-09-29 | 1994-12-27 | Minimed Inc. | Data transfer system for an infusion pump |
ES2154651T3 (en) | 1992-10-15 | 2001-04-16 | Gen Hospital Corp | INFUSION PUMP WITH ELECTRONICALLY CHARGABLE MEDICATIONS LIBRARY. |
US5997476A (en) | 1997-03-28 | 1999-12-07 | Health Hero Network, Inc. | Networked system for interactive communication and remote monitoring of individuals |
US5956501A (en) | 1997-01-10 | 1999-09-21 | Health Hero Network, Inc. | Disease simulation system and method |
US5897493A (en) | 1997-03-28 | 1999-04-27 | Health Hero Network, Inc. | Monitoring system for remotely querying individuals |
US20010011224A1 (en) | 1995-06-07 | 2001-08-02 | Stephen James Brown | Modular microprocessor-based health monitoring system |
US5832448A (en) | 1996-10-16 | 1998-11-03 | Health Hero Network | Multiple patient monitoring system for proactive health management |
US5378231A (en) | 1992-11-25 | 1995-01-03 | Abbott Laboratories | Automated drug infusion system |
US5341476A (en) | 1992-12-23 | 1994-08-23 | Abbott Laboratories | Dynamic data distribution network with sink and source files for particular data types |
US5719761A (en) | 1993-01-15 | 1998-02-17 | Alaris Medical Systems, Inc. | Configuration control system for configuring multiple biomedical devices |
US5912818A (en) | 1993-01-25 | 1999-06-15 | Diebold, Incorporated | System for tracking and dispensing medical items |
US5910252A (en) | 1993-02-12 | 1999-06-08 | Cobe Laboratories, Inc. | Technique for extracorporeal treatment of blood |
CA2158947A1 (en) | 1993-03-24 | 1994-09-29 | Paul V. Darbee | Infrared remote control device for a personal digital assistant |
DE4320365C2 (en) | 1993-06-19 | 2000-07-13 | Uvo Hoelscher | Multi-channel dosing system |
AU7323994A (en) | 1993-07-13 | 1995-02-13 | Sims Deltec, Inc. | Medical pump and method of programming |
US5368562A (en) | 1993-07-30 | 1994-11-29 | Pharmacia Deltec, Inc. | Systems and methods for operating ambulatory medical devices such as drug delivery devices |
US5423748A (en) | 1993-08-16 | 1995-06-13 | Uhala; Dominic | Pain comforter system |
FR2710538B1 (en) | 1993-09-30 | 1995-12-01 | Becton Dickinson Co | Method and device for detecting bubbles in an infusion line. |
US5389078A (en) | 1993-10-06 | 1995-02-14 | Sims Deltec, Inc. | Programmable infusion pump for administering medication to patients |
CA2131077A1 (en) | 1993-11-05 | 1995-05-06 | Syed Vickar Ahamed | Integrated medical computer system and method |
US5447164A (en) | 1993-11-08 | 1995-09-05 | Hewlett-Packard Company | Interactive medical information display system and method for displaying user-definable patient events |
US5431627A (en) | 1993-11-12 | 1995-07-11 | Abbott Laboratories | Cassette identification system for use with a multi-program drug infusion pump |
JP3409399B2 (en) | 1993-11-30 | 2003-05-26 | セイコーエプソン株式会社 | Medication control device |
DE4441907A1 (en) | 1993-12-16 | 1995-06-22 | Hewlett Packard Co | Patient emergency response system |
US5417222A (en) | 1994-01-21 | 1995-05-23 | Hewlett-Packard Company | Patient monitoring system |
US5867688A (en) | 1994-02-14 | 1999-02-02 | Reliable Transaction Processing, Inc. | Data acquisition and retrieval system with wireless handheld user interface |
FR2716286A1 (en) | 1994-02-16 | 1995-08-18 | Debiotech Sa | Installation of remote monitoring of controllable equipment. |
US5562615A (en) | 1994-02-28 | 1996-10-08 | Corpak, Inc. | Free flow detector for an enternal feeding pump |
US5630710A (en) | 1994-03-09 | 1997-05-20 | Baxter International Inc. | Ambulatory infusion pump |
JP2973076B2 (en) | 1994-03-16 | 1999-11-08 | 本田技研工業株式会社 | Electric pump control device |
EP0672427A1 (en) | 1994-03-17 | 1995-09-20 | Siemens-Elema AB | System for infusion of medicine into the body of a patient |
FR2717919B1 (en) | 1994-03-28 | 1996-06-21 | Ensyma Sa | Medical decision support system and device for administering at least one drug. |
US5738102A (en) | 1994-03-31 | 1998-04-14 | Lemelson; Jerome H. | Patient monitoring system |
US5507786A (en) | 1994-04-14 | 1996-04-16 | Pacesetter, Inc. | System and method for measuring and storing parametric data pertaining to operating characteristics of an implantable medical device |
US5577169A (en) | 1994-04-29 | 1996-11-19 | International Business Machines Corporation | Fuzzy logic entity behavior profiler |
DE4415896A1 (en) | 1994-05-05 | 1995-11-09 | Boehringer Mannheim Gmbh | Analysis system for monitoring the concentration of an analyte in the blood of a patient |
CA2125300C (en) | 1994-05-11 | 1999-10-12 | Douglas J. Ballantyne | Method and apparatus for the electronic distribution of medical information and patient services |
JPH07319971A (en) | 1994-05-19 | 1995-12-08 | At & T Global Inf Solutions Internatl Inc | Remotely accessible medical treatment network |
EP0692766B1 (en) | 1994-07-12 | 2002-05-08 | Medrad, Inc. | Closed loop information path for medical fluid delivery systems |
US5582593A (en) | 1994-07-21 | 1996-12-10 | Hultman; Barry W. | Ambulatory medication delivery system |
US5695473A (en) | 1994-07-27 | 1997-12-09 | Sims Deltec, Inc. | Occlusion detection system for an infusion pump |
US5493430A (en) | 1994-08-03 | 1996-02-20 | Kent Display Systems, L.P. | Color, reflective liquid crystal displays |
ATE163235T1 (en) | 1994-09-13 | 1998-02-15 | Irmgard Rost | DATA ARCHIVING SYSTEM |
US5636044A (en) | 1994-10-14 | 1997-06-03 | Kent Displays, Inc. | Segmented polymer stabilized and polymer free cholesteric texture liquid crystal displays and driving method for same |
US5522798A (en) | 1994-10-17 | 1996-06-04 | Abbott Laboratories | Control of a multi-channel drug infusion pump using a pharmacokinetic model |
US5461365A (en) | 1994-10-27 | 1995-10-24 | Schlager; Dan | Multi-hazard alarm system using selectable power-level transmission and localization |
US5598519A (en) | 1994-11-08 | 1997-01-28 | Microsoft Corporation | Method and system for direct cell formatting in a spreadsheet |
US5582323A (en) | 1994-11-16 | 1996-12-10 | United Home Technologies, Inc. | Medication dispenser and monitor |
US6749586B2 (en) | 1994-11-25 | 2004-06-15 | I-Flow Corporation | Remotely programmable infusion system |
US5573506A (en) | 1994-11-25 | 1996-11-12 | Block Medical, Inc. | Remotely programmable infusion system |
US5685844A (en) | 1995-01-06 | 1997-11-11 | Abbott Laboratories | Medicinal fluid pump having multiple stored protocols |
US5520637A (en) | 1995-01-31 | 1996-05-28 | Pager; David | Closed-loop system for infusing oxytocin |
US5697899A (en) | 1995-02-07 | 1997-12-16 | Gensia | Feedback controlled drug delivery system |
WO1996025186A2 (en) | 1995-02-07 | 1996-08-22 | Gensia, Inc. | Feedback controlled drug delivery system |
US5814015A (en) | 1995-02-24 | 1998-09-29 | Harvard Clinical Technology, Inc. | Infusion pump for at least one syringe |
US5713856A (en) | 1995-03-13 | 1998-02-03 | Alaris Medical Systems, Inc. | Modular patient care system |
US5941846A (en) | 1995-03-13 | 1999-08-24 | Alaris Medical Systems, Inc. | Method and apparatus for power connection in a modular patient care system |
US7384410B2 (en) | 1995-03-13 | 2008-06-10 | Cardinal Health 303, Inc. | System and method for managing patient care |
US5836910A (en) | 1995-03-13 | 1998-11-17 | Alaris Medical Systems, Inc. | Method and apparatus for logical addressing in a modular patient care system |
US5752621A (en) | 1995-03-20 | 1998-05-19 | Eigen Technology Inc. | Smart automatic medication dispenser |
US6223440B1 (en) | 1995-03-27 | 2001-05-01 | Richard Rashman | Autoclavable stainless steel medical instruments with polypropylene injected color handles |
US6333690B1 (en) | 1995-03-29 | 2001-12-25 | Medical Tracking Systems | Wide area multipurpose tracking system |
US7267666B1 (en) | 1995-04-20 | 2007-09-11 | Acist Medical Systems, Inc. | Angiographic injector system with multiple processor redundancy |
US8082018B2 (en) | 1995-04-20 | 2011-12-20 | Acist Medical Systems, Inc. | System and method for multiple injection procedures on heart vessels |
US5772635A (en) | 1995-05-15 | 1998-06-30 | Alaris Medical Systems, Inc. | Automated infusion system with dose rate calculator |
US6671563B1 (en) | 1995-05-15 | 2003-12-30 | Alaris Medical Systems, Inc. | System and method for collecting data and managing patient care |
US5781442A (en) | 1995-05-15 | 1998-07-14 | Alaris Medical Systems, Inc. | System and method for collecting data and managing patient care |
US5665065A (en) | 1995-05-26 | 1997-09-09 | Minimed Inc. | Medication infusion device with blood glucose data input |
DE69623013T2 (en) | 1995-06-02 | 2002-12-12 | Airspan Networks Inc | CONTROL MESSAGE TRANSMISSION IN TELECOMMUNICATION SYSTEMS |
US5623925A (en) | 1995-06-05 | 1997-04-29 | Cmed, Inc. | Virtual medical instrument for performing medical diagnostic testing on patients |
US5699509A (en) | 1995-06-07 | 1997-12-16 | Abbott Laboratories | Method and system for using inverted data to detect corrupt data |
US5620608A (en) | 1995-06-07 | 1997-04-15 | Cobe Laboratories, Inc. | Information entry validation system and method for a dialysis machine |
US5995860A (en) | 1995-07-06 | 1999-11-30 | Thomas Jefferson University | Implantable sensor and system for measurement and control of blood constituent levels |
US5651775A (en) | 1995-07-12 | 1997-07-29 | Walker; Richard Bradley | Medication delivery and monitoring system and methods |
US5850344A (en) | 1995-08-14 | 1998-12-15 | Profile Systems, Llc | Medication dispensing and timing system |
JP3083465B2 (en) | 1995-09-06 | 2000-09-04 | フクダ電子株式会社 | Patient information analysis management system and method |
US5754111A (en) | 1995-09-20 | 1998-05-19 | Garcia; Alfredo | Medical alerting system |
US5797515A (en) | 1995-10-18 | 1998-08-25 | Adds, Inc. | Method for controlling a drug dispensing system |
US5873731A (en) | 1995-10-20 | 1999-02-23 | Eagle Simulation, Inc. | Patient drug recognition system |
US5718562A (en) | 1995-11-02 | 1998-02-17 | Abbott Laboratories | Interface module for use with an NCT-based pumping mechanism and NCT-based cassette |
US5944659A (en) | 1995-11-13 | 1999-08-31 | Vitalcom Inc. | Architecture for TDMA medical telemetry system |
US5836312A (en) | 1996-01-02 | 1998-11-17 | Moore; Steven Jerome | Computer-assisted system and method for adjudging the effect of consumable intakes on physiological parameters |
US6112182A (en) | 1996-01-16 | 2000-08-29 | Healthcare Computer Corporation | Method and apparatus for integrated management of pharmaceutical and healthcare services |
US5778345A (en) | 1996-01-16 | 1998-07-07 | Mccartney; Michael J. | Health data processing system |
US5782805A (en) | 1996-04-10 | 1998-07-21 | Meinzer; Randolph | Medical infusion pump |
US5764034A (en) | 1996-04-10 | 1998-06-09 | Baxter International Inc. | Battery gauge for a battery operated infusion pump |
US5774865A (en) | 1996-04-19 | 1998-06-30 | Ideal Ideas, Inc. | Patient compliance and monitoring system for multiple regimens using a movable bar code reader |
US6517482B1 (en) | 1996-04-23 | 2003-02-11 | Dermal Therapy (Barbados) Inc. | Method and apparatus for non-invasive determination of glucose in body fluids |
US6151643A (en) | 1996-06-07 | 2000-11-21 | Networks Associates, Inc. | Automatic updating of diverse software products on multiple client computer systems by downloading scanning application to client computer and generating software list on client computer |
US5990838A (en) | 1996-06-12 | 1999-11-23 | 3Com Corporation | Dual orthogonal monopole antenna system |
US5870733A (en) | 1996-06-14 | 1999-02-09 | Electronic Data Systems Corporation | Automated system and method for providing access data concerning an item of business property |
US6182667B1 (en) | 1996-06-21 | 2001-02-06 | Integrated Medical Systems, Inc. | Display for transportable life support system |
US6234176B1 (en) | 1996-06-21 | 2001-05-22 | Integrated Medical Systems, Inc. | Data logger for transportable life support system |
US5975081A (en) | 1996-06-21 | 1999-11-02 | Northrop Grumman Corporation | Self-contained transportable life support system |
US5807336A (en) | 1996-08-02 | 1998-09-15 | Sabratek Corporation | Apparatus for monitoring and/or controlling a medical device |
US6689091B2 (en) | 1996-08-02 | 2004-02-10 | Tuan Bui | Medical apparatus with remote control |
US5885245A (en) | 1996-08-02 | 1999-03-23 | Sabratek Corporation | Medical apparatus with remote virtual input device |
US5687717A (en) | 1996-08-06 | 1997-11-18 | Tremont Medical, Inc. | Patient monitoring system with chassis mounted or remotely operable modules and portable computer |
US6271813B1 (en) | 1996-08-30 | 2001-08-07 | Lear Automotive Dearborn, Inc. | Voltage control for adjusting the brightness of a screen display |
CA2233942A1 (en) | 1996-09-18 | 1998-03-26 | Dew Engineering And Development Limited | Biometric identification system for providing secure access |
US5897498A (en) | 1996-09-25 | 1999-04-27 | Atl Ultrasound, Inc. | Ultrasonic diagnostic imaging system with electronic message communications capability |
US5924074A (en) | 1996-09-27 | 1999-07-13 | Azron Incorporated | Electronic medical records system |
US5800387A (en) | 1996-10-04 | 1998-09-01 | Alaris Medical Systems, Inc. | Safety monitoring apparatus for a patient care system |
IL119523A0 (en) | 1996-10-30 | 1997-01-10 | Algotec Systems Ltd | Data distribution system |
US5957885A (en) | 1996-11-06 | 1999-09-28 | Alaris Medical Systems, Inc. | Oximetry monitored, patient controlled analgesia system |
US6335927B1 (en) | 1996-11-18 | 2002-01-01 | Mci Communications Corporation | System and method for providing requested quality of service in a hybrid network |
US6021392A (en) | 1996-12-09 | 2000-02-01 | Pyxis Corporation | System and method for drug management |
US6003006A (en) | 1996-12-09 | 1999-12-14 | Pyxis Corporation | System of drug distribution to health care providers |
US8734339B2 (en) | 1996-12-16 | 2014-05-27 | Ip Holdings, Inc. | Electronic skin patch for real time monitoring of cardiac activity and personal health management |
US6346886B1 (en) | 1996-12-20 | 2002-02-12 | Carlos De La Huerga | Electronic identification apparatus |
US6032155A (en) | 1997-04-14 | 2000-02-29 | De La Huerga; Carlos | System and apparatus for administering prescribed medication to a patient |
US6330008B1 (en) | 1997-02-24 | 2001-12-11 | Torrent Systems, Inc. | Apparatuses and methods for monitoring performance of parallel computing |
US5827179A (en) | 1997-02-28 | 1998-10-27 | Qrs Diagnostic, Llc | Personal computer card for collection for real-time biological data |
US6159147A (en) | 1997-02-28 | 2000-12-12 | Qrs Diagnostics, Llc | Personal computer card for collection of real-time biological data |
US6270455B1 (en) | 1997-03-28 | 2001-08-07 | Health Hero Network, Inc. | Networked system for interactive communications and remote monitoring of drug delivery |
US5960085A (en) | 1997-04-14 | 1999-09-28 | De La Huerga; Carlos | Security badge for automated access control and secure data gathering |
DE69835314T2 (en) | 1997-04-15 | 2007-05-10 | Hewlett-Packard Development Co., L.P., Houston | Method and device for format-controlled interaction between devices |
TW357517B (en) | 1997-05-29 | 1999-05-01 | Koji Akai | Monitoring system |
US7267665B2 (en) | 1999-06-03 | 2007-09-11 | Medtronic Minimed, Inc. | Closed loop system for controlling insulin infusion |
US5954643A (en) | 1997-06-09 | 1999-09-21 | Minimid Inc. | Insertion set for a transcutaneous sensor |
US6558351B1 (en) | 1999-06-03 | 2003-05-06 | Medtronic Minimed, Inc. | Closed loop system for controlling insulin infusion |
US6628809B1 (en) | 1999-10-08 | 2003-09-30 | Lumidigm, Inc. | Apparatus and method for identification of individuals by near-infrared spectrum |
US5915240A (en) | 1997-06-12 | 1999-06-22 | Karpf; Ronald S. | Computer system and method for accessing medical information over a network |
US6012034A (en) | 1997-08-18 | 2000-01-04 | Becton, Dickinson And Company | System and method for selecting an intravenous device |
US6000828A (en) | 1997-08-22 | 1999-12-14 | Power Med Incorporated | Method of improving drug treatment |
US6070761A (en) | 1997-08-22 | 2000-06-06 | Deka Products Limited Partnership | Vial loading method and apparatus for intelligent admixture and delivery of intravenous drugs |
US6888322B2 (en) | 1997-08-26 | 2005-05-03 | Color Kinetics Incorporated | Systems and methods for color changing device and enclosure |
US20050040226A1 (en) | 1997-10-01 | 2005-02-24 | Zaher Al-Sheikh | User authorization system containing a user image |
US6567416B1 (en) | 1997-10-14 | 2003-05-20 | Lucent Technologies Inc. | Method for access control in a multiple access system for communications networks |
US6377548B1 (en) | 1997-10-14 | 2002-04-23 | Lucent Technologies Inc. | Method for admitting new connections based on measured quantities in a multiple access system for communications networks |
US6285665B1 (en) | 1997-10-14 | 2001-09-04 | Lucent Technologies Inc. | Method for establishment of the power level for uplink data transmission in a multiple access system for communications networks |
US7017293B2 (en) | 2002-09-27 | 2006-03-28 | Laser Band, Llc | Wristband/cinch with label assembly business form and method |
US6469991B1 (en) | 1997-10-14 | 2002-10-22 | Lucent Technologies Inc. | Method for overload control in a multiple access system for communication networks |
US6115390A (en) | 1997-10-14 | 2000-09-05 | Lucent Technologies, Inc. | Bandwidth reservation and collision resolution method for multiple access communication networks where remote hosts send reservation requests to a base station for randomly chosen minislots |
US6327254B1 (en) | 1997-10-14 | 2001-12-04 | Lucent Technologies Inc. | Method for bandwidth sharing in a multiple access system for communications networks |
US6226277B1 (en) | 1997-10-14 | 2001-05-01 | Lucent Technologies Inc. | Method for admitting new connections based on usage priorities in a multiple access system for communications networks |
US7216802B1 (en) | 1997-10-21 | 2007-05-15 | Carlos De La Huerga | Method and apparatus for verifying information |
US6292860B1 (en) | 1997-12-16 | 2001-09-18 | Ncr Corporation | Method for preventing deadlock by suspending operation of processors, bridges, and devices |
US6208974B1 (en) | 1997-12-30 | 2001-03-27 | Medical Management International, Inc. | Method and system for managing wellness plans for a medical care practice |
US6859134B1 (en) | 1998-01-05 | 2005-02-22 | Symbol Technologies, Inc. | Data communication device |
US20040015132A1 (en) | 1998-01-06 | 2004-01-22 | Eric Brown | Method for improving patient compliance with a medical program |
US5967559A (en) | 1998-01-09 | 1999-10-19 | Abramowitz; Joseph M. | Rapid visual impact patient identifier and method |
US6189105B1 (en) | 1998-02-20 | 2001-02-13 | Lucent Technologies, Inc. | Proximity detection of valid computer user |
US20020010595A1 (en) | 1998-02-27 | 2002-01-24 | Kapp Thomas L. | Web-based medication management system |
US6195589B1 (en) | 1998-03-09 | 2001-02-27 | 3Com Corporation | Personal data assistant with remote control capabilities |
US6024699A (en) | 1998-03-13 | 2000-02-15 | Healthware Corporation | Systems, methods and computer program products for monitoring, diagnosing and treating medical conditions of remotely located patients |
US5971594A (en) | 1998-03-24 | 1999-10-26 | Innovative Medical Devices, Inc. | Medication dispensing system |
SE9801151L (en) | 1998-04-01 | 1999-10-02 | Telia Ab | Improvements to, or with regard to, electronic nameplates |
US6083007A (en) | 1998-04-02 | 2000-07-04 | Hewlett-Packard Company | Apparatus and method for configuring training for a product and the product |
US7899518B2 (en) | 1998-04-06 | 2011-03-01 | Masimo Laboratories, Inc. | Non-invasive tissue glucose level monitoring |
US6721582B2 (en) | 1999-04-06 | 2004-04-13 | Argose, Inc. | Non-invasive tissue glucose level monitoring |
US6200289B1 (en) | 1998-04-10 | 2001-03-13 | Milestone Scientific, Inc. | Pressure/force computer controlled drug delivery system and the like |
US6126637A (en) | 1998-04-15 | 2000-10-03 | Science Incorporated | Fluid delivery device with collapsible needle cover |
US6039251A (en) | 1998-04-16 | 2000-03-21 | Holowko; Paul L. | Method and system for secure control of a medical device |
DE19850122A1 (en) | 1998-04-17 | 1999-10-28 | Siemens Ag | Automatic configuration arrangement for technical object testing arrangement e.g. for electric motors |
US7647237B2 (en) | 1998-04-29 | 2010-01-12 | Minimed, Inc. | Communication station and software for interfacing with an infusion pump, analyte monitor, analyte meter, or the like |
US6175752B1 (en) | 1998-04-30 | 2001-01-16 | Therasense, Inc. | Analyte monitoring device and methods of use |
US6167567A (en) | 1998-05-05 | 2000-12-26 | 3Com Corporation | Technique for automatically updating software stored on a client computer in a networked client-server environment |
DE69937558T2 (en) | 1998-06-03 | 2008-03-06 | Scott Laboratories, Inc., Lubbock | APPARATUS FOR AFFECTING PAIN IN AWARENESS AND FEARING STATE IN CONNECTION WITH MEDICAL AND SURGICAL PROCEDURES |
US7308894B2 (en) | 1998-06-03 | 2007-12-18 | Scott Laboratories, Inc. | Apparatuses and methods for providing a conscious patient relief from pain and anxiety associated with medical or surgical procedures according to appropriate clinical heuristics |
US5920263A (en) | 1998-06-11 | 1999-07-06 | Ohmeda, Inc. | De-escalation of alarm priorities in medical devices |
US5931764A (en) | 1998-06-24 | 1999-08-03 | Viztec, Inc. | Wearable device with flexible display |
US6112323A (en) | 1998-06-29 | 2000-08-29 | Microsoft Corporation | Method and computer program product for efficiently and reliably sending small data messages from a sending system to a large number of receiving systems |
US5963136A (en) | 1998-07-15 | 1999-10-05 | O'brien; Charles Terrence | Interactive prescription compliance and life safety system |
US6104295A (en) | 1998-07-20 | 2000-08-15 | Versus Technology, Inc. | Electronic band tag and method of storing ID information therein |
US6558320B1 (en) | 2000-01-20 | 2003-05-06 | Medtronic Minimed, Inc. | Handheld personal data assistant (PDA) with a medical device and method of using the same |
US6554798B1 (en) | 1998-08-18 | 2003-04-29 | Medtronic Minimed, Inc. | External infusion device with remote programming, bolus estimator and/or vibration alarm capabilities |
US6248067B1 (en) | 1999-02-05 | 2001-06-19 | Minimed Inc. | Analyte sensor and holter-type monitor system and method of using the same |
DE19840965A1 (en) | 1998-09-08 | 2000-03-09 | Disetronic Licensing Ag | Device for self-administration of a product fluid |
US6753830B2 (en) | 1998-09-11 | 2004-06-22 | Visible Tech-Knowledgy, Inc. | Smart electronic label employing electronic ink |
WO2000013580A1 (en) | 1998-09-11 | 2000-03-16 | Amira Medical | Device for determination of an analyte in a body fluid intergrated with an insulin pump |
US6924781B1 (en) | 1998-09-11 | 2005-08-02 | Visible Tech-Knowledgy, Inc. | Smart electronic label employing electronic ink |
JP3729658B2 (en) | 1998-09-18 | 2005-12-21 | パイオニア株式会社 | Audio equipment |
US7931642B2 (en) | 1998-09-18 | 2011-04-26 | Codman Neuro Sciences Sarl | Infusion pump comprising a computer for calculating the respective maximum permissible dosage |
DE19844252A1 (en) | 1998-09-26 | 2000-03-30 | Hendrik Lehnert | Modular unit for infusing insulin and glucose uses commercially-available computing systems to control automatic analysis and dosing, with upgradability and data exchange functions |
ATE514372T1 (en) | 1998-10-08 | 2011-07-15 | Medtronic Minimed Inc | LICENSE PLATE MONITORING SYSTEM WITH REMOTE MEASUREMENT |
US7293107B1 (en) | 1998-10-09 | 2007-11-06 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US7136645B2 (en) | 1998-10-09 | 2006-11-14 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
US7766873B2 (en) | 1998-10-29 | 2010-08-03 | Medtronic Minimed, Inc. | Method and apparatus for detecting occlusions in an ambulatory infusion pump |
US6073106A (en) | 1998-10-30 | 2000-06-06 | Nehdc, Inc. | Method of managing and controlling access to personal information |
JP2000200067A (en) | 1998-11-06 | 2000-07-18 | Matsushita Electric Ind Co Ltd | Display device driving method and display device |
US6578002B1 (en) | 1998-11-25 | 2003-06-10 | Gregory John Derzay | Medical diagnostic system service platform |
DE69939344D1 (en) | 1998-11-30 | 2008-09-25 | Novo Nordisk As | Method of supporting a medical self-treatment |
IL143122A0 (en) | 1998-11-30 | 2002-04-21 | Novo Nordisk As | A method and a system for assisting a user in a medical self treatment, said self treatment comprising a plurality of actions |
US6540672B1 (en) | 1998-12-09 | 2003-04-01 | Novo Nordisk A/S | Medical system and a method of controlling the system for use by a patient for medical self treatment |
DE19904090C2 (en) | 1999-02-02 | 2003-06-05 | Wolf Gmbh Richard | Method and device for the automatic control and management of medical devices and systems |
US6774786B1 (en) | 2000-11-07 | 2004-08-10 | Fisher-Rosemount Systems, Inc. | Integrated alarm display in a process control network |
WO2000053243A1 (en) | 1999-03-09 | 2000-09-14 | Ball Semiconductor, Inc. | Implantable drug delivery system |
TW537880B (en) | 1999-03-11 | 2003-06-21 | Remote Medical Corp | Method for improving patient compliance with a medical program |
US20040139004A1 (en) | 1999-04-08 | 2004-07-15 | Aceinc Pty Ltd. | Secure online commerce transactions |
US6796956B2 (en) | 1999-04-30 | 2004-09-28 | Medtronic, Inc. | Method and apparatus to control drug therapy dosages in an implantable pump |
US6635048B1 (en) | 1999-04-30 | 2003-10-21 | Medtronic, Inc. | Implantable medical pump with multi-layer back-up memory |
IL130371A (en) | 1999-06-08 | 2004-06-01 | Oridion Medical Ltd | Capnography waveform interpreter |
US6928490B1 (en) | 1999-05-20 | 2005-08-09 | St. Louis University | Networking infrastructure for an operating room |
US7134996B2 (en) | 1999-06-03 | 2006-11-14 | Cardiac Intelligence Corporation | System and method for collection and analysis of patient information for automated remote patient care |
US7806886B2 (en) | 1999-06-03 | 2010-10-05 | Medtronic Minimed, Inc. | Apparatus and method for controlling insulin infusion with state variable feedback |
US6312378B1 (en) | 1999-06-03 | 2001-11-06 | Cardiac Intelligence Corporation | System and method for automated collection and analysis of patient information retrieved from an implantable medical device for remote patient care |
US6752787B1 (en) | 1999-06-08 | 2004-06-22 | Medtronic Minimed, Inc., | Cost-sensitive application infusion device |
US6631353B1 (en) | 1999-06-10 | 2003-10-07 | Hologic, Inc. | Sonometry and densitometry medical diagnostic devices enabled for per-use patient examinations charged via internet connections to financial cards |
US6969352B2 (en) | 1999-06-22 | 2005-11-29 | Teratech Corporation | Ultrasound probe with integrated electronics |
US7315825B2 (en) | 1999-06-23 | 2008-01-01 | Visicu, Inc. | Rules-based patient care system for use in healthcare locations |
IL130818A (en) | 1999-07-06 | 2005-07-25 | Intercure Ltd | Interventive-diagnostic device |
US7149773B2 (en) | 1999-07-07 | 2006-12-12 | Medtronic, Inc. | System and method of automated invoicing for communications between an implantable medical device and a remote computer system or health care provider |
EP1194069B1 (en) | 1999-07-08 | 2006-03-22 | Steffen Dr.-Ing. Leonhardt | Device for measuring the blood-sugar level in humans |
DE19932147A1 (en) | 1999-07-12 | 2001-01-25 | Insys Ges Fuer Microcontroller | Electronic system for detecting, monitoring patient data has transponders with stored identification codes, polling device for connection to central or non-central hospital computer |
US6221011B1 (en) | 1999-07-26 | 2001-04-24 | Cardiac Intelligence Corporation | System and method for determining a reference baseline of individual patient status for use in an automated collection and analysis patient care system |
US6514460B1 (en) | 1999-07-28 | 2003-02-04 | Abbott Laboratories | Luminous glucose monitoring device |
US6339718B1 (en) | 1999-07-30 | 2002-01-15 | Medrad, Inc. | Programmable injector control |
WO2001013317A2 (en) | 1999-08-13 | 2001-02-22 | Kocher Jean Pierre | Method and apparatus for scanning of food and medicine to provide outputs relative to a user profile |
US20030013959A1 (en) | 1999-08-20 | 2003-01-16 | Sorin Grunwald | User interface for handheld imaging devices |
AU6796600A (en) | 1999-08-23 | 2001-03-19 | Presideo, Inc. | System, method, and article of manufacture for identifying an individual and managing an individual's health records |
US6923763B1 (en) | 1999-08-23 | 2005-08-02 | University Of Virginia Patent Foundation | Method and apparatus for predicting the risk of hypoglycemia |
US6494831B1 (en) | 1999-09-03 | 2002-12-17 | Ge Medical Technology Services, Inc. | Medical diagnostic system service connectivity method and apparatus |
US6464136B2 (en) | 1999-12-28 | 2002-10-15 | Christopher S. Walsh | Record and verification method, apparatus and system |
US6640246B1 (en) | 1999-09-17 | 2003-10-28 | Ge Medical Systems Global Technology Company, Llc | Integrated computerized materials management system |
US6564121B1 (en) | 1999-09-22 | 2003-05-13 | Telepharmacy Solutions, Inc. | Systems and methods for drug dispensing |
WO2001024690A2 (en) | 1999-10-01 | 2001-04-12 | Glaxo Group Limited | Medicament delivery system |
US6681003B2 (en) | 1999-10-05 | 2004-01-20 | Lifecor, Inc. | Data collection and system management for patient-worn medical devices |
US7636718B1 (en) | 1999-10-07 | 2009-12-22 | B. Braun Medical Inc. | Pharmaceutical administrative system for ordering and receiving prescribed medication |
US6816605B2 (en) | 1999-10-08 | 2004-11-09 | Lumidigm, Inc. | Methods and systems for biometric identification of individuals using linear optical spectroscopy |
US7519905B2 (en) | 1999-10-12 | 2009-04-14 | Webmd Corp. | Automatic formatting and validating of text for a markup language graphical user interface |
US6418334B1 (en) | 1999-10-19 | 2002-07-09 | General Electric Company | Method and apparatus for logging and dynamically configuring performance analysis of a medical diagnostic imaging system |
US6249705B1 (en) | 1999-10-21 | 2001-06-19 | Pacesetter, Inc. | Distributed network system for use with implantable medical devices |
US7933780B2 (en) | 1999-10-22 | 2011-04-26 | Telaric, Llc | Method and apparatus for controlling an infusion pump or the like |
US6257265B1 (en) | 1999-10-26 | 2001-07-10 | Sims Level 1 Inc. | Apparatus for connecting a heat exchanger with a fluid temperature regulation device |
US6363282B1 (en) | 1999-10-29 | 2002-03-26 | Medtronic, Inc. | Apparatus and method to automatic remote software updates of medical device systems |
US20040078236A1 (en) | 1999-10-30 | 2004-04-22 | Medtamic Holdings | Storage and access of aggregate patient data for analysis |
US6406426B1 (en) | 1999-11-03 | 2002-06-18 | Criticare Systems | Medical monitoring and alert system for use with therapeutic devices |
CA2776989A1 (en) | 1999-11-04 | 2001-05-10 | Health Resources And Technology, Inc. | A health care management system |
US6673033B1 (en) | 1999-11-24 | 2004-01-06 | Medrad, Inc. | Injectors, injector systems and injector control |
US6520930B2 (en) | 1999-11-24 | 2003-02-18 | Medrad, Inc. | Injectors, injector systems and injector control |
US20020103675A1 (en) | 1999-11-29 | 2002-08-01 | John Vanelli | Apparatus and method for providing consolidated medical information |
US6751651B2 (en) | 1999-11-30 | 2004-06-15 | David A. Crockett | Web-site consistency administration among inconsistent software-object libraries of remote distributed health-care providers |
US6519569B1 (en) | 1999-12-01 | 2003-02-11 | B. Braun Medical, Inc. | Security infusion pump with bar code reader |
US6790198B1 (en) | 1999-12-01 | 2004-09-14 | B-Braun Medical, Inc. | Patient medication IV delivery pump with wireless communication to a hospital information management system |
EP1238489B1 (en) | 1999-12-13 | 2008-03-05 | Broadcom Corporation | Voice gateway with downstream voice synchronization |
US7060031B2 (en) | 1999-12-17 | 2006-06-13 | Medtronic, Inc. | Method and apparatus for remotely programming implantable medical devices |
US6602191B2 (en) | 1999-12-17 | 2003-08-05 | Q-Tec Systems Llp | Method and apparatus for health and disease management combining patient data monitoring with wireless internet connectivity |
US6497680B1 (en) | 1999-12-17 | 2002-12-24 | Abbott Laboratories | Method for compensating for pressure differences across valves in cassette type IV pump |
US7490048B2 (en) | 1999-12-18 | 2009-02-10 | Raymond Anthony Joao | Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information |
US7464040B2 (en) | 1999-12-18 | 2008-12-09 | Raymond Anthony Joao | Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information |
US6734886B1 (en) | 1999-12-21 | 2004-05-11 | Personalpath Systems, Inc. | Method of customizing a browsing experience on a world-wide-web site |
US6442432B2 (en) | 1999-12-21 | 2002-08-27 | Medtronic, Inc. | Instrumentation and software for remote monitoring and programming of implantable medical devices (IMDs) |
DE29922736U1 (en) | 1999-12-24 | 2001-05-03 | Braun Melsungen Ag | Infusion device with several infusion pumps |
WO2001049369A1 (en) | 1999-12-30 | 2001-07-12 | Medtronic, Inc. | User authentication in medical device systems |
US6980958B1 (en) | 2000-01-11 | 2005-12-27 | Zycare, Inc. | Apparatus and methods for monitoring and modifying anticoagulation therapy of remotely located patients |
US6371719B1 (en) | 2000-01-13 | 2002-04-16 | Leroy J. Hildebrandt | Recreation vehicle carrier for a truck |
US6813519B2 (en) | 2000-01-21 | 2004-11-02 | Medtronic Minimed, Inc. | Ambulatory medical apparatus and method using a robust communication protocol |
JP3438693B2 (en) | 2000-02-03 | 2003-08-18 | 日本電気株式会社 | Electronic device with display |
US20010037060A1 (en) | 2000-02-08 | 2001-11-01 | Thompson Richard P. | Web site for glucose monitoring |
DE10006044A1 (en) | 2000-02-10 | 2001-08-16 | Roche Diagnostics Gmbh | System, useful for administering hormone for blood glucose regulation of patient, comprises regulation unit with controller for processing measured data, and device for administering hormone |
DE20003469U1 (en) | 2000-02-23 | 2000-08-17 | Medical Communications Soft Un | Hand-held computer |
US7171492B1 (en) | 2000-02-24 | 2007-01-30 | Utstarcom, Inc. | Method and application programming interface for assigning multiple network addresses |
US6893396B2 (en) | 2000-03-01 | 2005-05-17 | I-Medik, Inc. | Wireless internet bio-telemetry monitoring system and interface |
US6572542B1 (en) | 2000-03-03 | 2003-06-03 | Medtronic, Inc. | System and method for monitoring and controlling the glycemic state of a patient |
JP2001258858A (en) | 2000-03-17 | 2001-09-25 | Pioneer Electronic Corp | Health monitoring system |
US20020040282A1 (en) | 2000-03-22 | 2002-04-04 | Bailey Thomas C. | Drug monitoring and alerting system |
US20010056358A1 (en) | 2000-03-24 | 2001-12-27 | Bridge Medical, Inc., | Method and apparatus for providing medication administration warnings |
US6542902B2 (en) | 2000-03-24 | 2003-04-01 | Bridge Medical, Inc. | Method and apparatus for displaying medication information |
US6871211B2 (en) | 2000-03-28 | 2005-03-22 | Ge Medical Systems Information Technologies, Inc. | Intranet-based medical data distribution system |
US6958677B1 (en) | 2000-03-31 | 2005-10-25 | Ge Medical Systems Information Technologies, Inc. | Object location monitoring system |
US7038584B2 (en) | 2000-03-31 | 2006-05-02 | Ge Medical Systems Information Technologies, Inc. | Object location monitoring within buildings |
WO2001077952A1 (en) | 2000-04-06 | 2001-10-18 | Bindler Paul R | Automated and intelligent networked-based psychological services |
FR2807542B1 (en) | 2000-04-06 | 2006-09-29 | Capsule Technologie | METHOD AND SYSTEM FOR COLLECTING AND DISSEMINATING DATA FROM DEVICES, IN PARTICULAR MEDICAL DEVICES |
US8510468B2 (en) | 2000-04-17 | 2013-08-13 | Ciradence Corporation | Route aware network link acceleration |
US20030036683A1 (en) | 2000-05-01 | 2003-02-20 | Kehr Bruce A. | Method, system and computer program product for internet-enabled, patient monitoring system |
US6599281B1 (en) | 2000-05-03 | 2003-07-29 | Aspect Medical Systems, Inc. | System and method for adaptive drug delivery |
US7099809B2 (en) | 2000-05-04 | 2006-08-29 | Dov Dori | Modeling system |
EP1290652A2 (en) | 2000-05-05 | 2003-03-12 | Hill-Rom Services, Inc. | Hospital monitoring and control system and method |
US6227371B1 (en) | 2000-05-12 | 2001-05-08 | Julie Song | Medical container and system |
US7657887B2 (en) | 2000-05-17 | 2010-02-02 | Interwoven, Inc. | System for transactionally deploying content across multiple machines |
US20050171815A1 (en) | 2003-12-31 | 2005-08-04 | Vanderveen Timothy W. | Centralized medication management system |
US9069887B2 (en) | 2000-05-18 | 2015-06-30 | Carefusion 303, Inc. | Patient-specific medication management system |
US20040172283A1 (en) | 2003-02-09 | 2004-09-02 | Vanderveen Timothy W. | Medication management and event logger and analysis system |
US7860583B2 (en) | 2004-08-25 | 2010-12-28 | Carefusion 303, Inc. | System and method for dynamically adjusting patient therapy |
US9427520B2 (en) | 2005-02-11 | 2016-08-30 | Carefusion 303, Inc. | Management of pending medication orders |
NZ522631A (en) | 2000-05-18 | 2004-07-30 | Alaris Medical Inc | Distributed remote asset and medication management drug delivery system |
US6482158B2 (en) | 2000-05-19 | 2002-11-19 | Healthetech, Inc. | System and method of ultrasonic mammography |
DE60134191D1 (en) | 2000-05-26 | 2008-07-10 | Terumo Corp | Control arrangement for a medical pump |
EP1294441A2 (en) | 2000-06-14 | 2003-03-26 | Medtronic, Inc. | Deep computing applications in medical device systems |
JP2002084338A (en) | 2000-07-07 | 2002-03-22 | Matsushita Electric Ind Co Ltd | Data transmitter, data receiver and data communication system |
US6659947B1 (en) | 2000-07-13 | 2003-12-09 | Ge Medical Systems Information Technologies, Inc. | Wireless LAN architecture for integrated time-critical and non-time-critical services within medical facilities |
WO2002005702A2 (en) | 2000-07-18 | 2002-01-24 | Healthetech, Inc. | Closed loop glycemic index system |
EP1174817A3 (en) | 2000-07-20 | 2005-01-26 | GE Medical Technology Services | Centralized biomedical service data repository |
JP2002044079A (en) | 2000-07-25 | 2002-02-08 | Matsushita Electric Works Ltd | Client service supporting system for service provider utilizing communication network and method for supporting provision of client service from service provider while using the same |
JP2002047694A (en) | 2000-07-31 | 2002-02-15 | Komatsu Ltd | Display device for construction machine |
US6589229B1 (en) | 2000-07-31 | 2003-07-08 | Becton, Dickinson And Company | Wearable, self-contained drug infusion device |
US9135393B1 (en) | 2000-08-02 | 2015-09-15 | Smiths Medical Asd, Inc. | Processing program data for medical pumps |
JP4055926B2 (en) | 2000-08-14 | 2008-03-05 | テルモ株式会社 | Infusion pump |
EP1315533A4 (en) | 2000-08-15 | 2007-06-27 | Univ Kentucky Res Found | Programmable multi-dose intranasal drug delivery device |
JP3590949B2 (en) | 2000-08-17 | 2004-11-17 | 松下電器産業株式会社 | Data transmission device and data transmission method |
JP2004521667A (en) | 2000-09-08 | 2004-07-22 | インシュレット コーポレイション | Device, system and method for patient infusion |
AU2001275020A1 (en) | 2000-09-21 | 2002-04-02 | Theradoc.Com, Inc. | Systems and methods for manipulating medical data via a decision support system |
US7447643B1 (en) | 2000-09-21 | 2008-11-04 | Theradoc.Com, Inc. | Systems and methods for communicating between a decision-support system and one or more mobile information devices |
WO2002024065A1 (en) | 2000-09-22 | 2002-03-28 | Knobbe, Lim & Buckingham | Method and apparatus for real-time estimation and control of pysiological parameters |
EP1332440B1 (en) | 2000-10-04 | 2012-04-11 | Insulet Corporation | Data collection assembly for patient infusion system |
DE10049393A1 (en) | 2000-10-05 | 2002-04-25 | Braun Melsungen Ag | Extracorporeal blood treatment system |
US7114002B1 (en) | 2000-10-05 | 2006-09-26 | Mitsubishi Denki Kabushiki Kaisha | Packet retransmission system, packet transmission device, packet reception device, packet retransmission method, packet transmission method and packet reception method |
EP1197178B1 (en) | 2000-10-12 | 2008-07-09 | GE Medical Systems Information Technologies, Inc. | Mobile clinical information system |
US6636780B1 (en) | 2000-11-07 | 2003-10-21 | Mdg Medical Inc. | Medication dispensing system including medicine cabinet and tray therefor |
US8862656B2 (en) | 2000-11-21 | 2014-10-14 | Chironet, Llc | Performance outcomes benchmarking |
AU2002222456A1 (en) | 2000-12-07 | 2002-06-18 | Children's Medical Center Corporation | Automated interpretive medical care system and methodology |
US7028092B2 (en) | 2000-12-11 | 2006-04-11 | Acme Packet, Inc. | System and method for assisting in controlling real-time transport protocol flow through multiple networks via media flow routing |
US20020123905A1 (en) | 2000-12-13 | 2002-09-05 | Joane Goodroe | Clinical operational and gainsharing information management system |
US6456245B1 (en) | 2000-12-13 | 2002-09-24 | Magis Networks, Inc. | Card-based diversity antenna structure for wireless communications |
JP4276834B2 (en) | 2000-12-27 | 2009-06-10 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | Biological information and blood processing apparatus information management system |
US20020087116A1 (en) | 2000-12-29 | 2002-07-04 | Medtronic, Inc. | Patient scheduling techniques for an implantable medical device |
US7054782B2 (en) | 2000-12-29 | 2006-05-30 | Medtronic, Inc. | Non-conformance monitoring and control techniques for an implantable medical device |
US6799149B2 (en) | 2000-12-29 | 2004-09-28 | Medtronic, Inc. | Therapy management techniques for an implantable medical device |
US7133909B2 (en) | 2001-01-12 | 2006-11-07 | Microsoft Corporation | Systems and methods for locating mobile computer users in a wireless network |
AU2002234258A1 (en) | 2001-01-22 | 2002-07-30 | Sun Microsystems, Inc. | Peer-to-peer network computing platform |
FR2820235B1 (en) | 2001-01-26 | 2003-06-13 | Thomson Csf | BACKLIGHT DEVICE FOR VIEWING SCREEN BY TRANSMISSION COMPATIBLE WITH NIGHT VISION |
US7776029B2 (en) | 2001-01-30 | 2010-08-17 | The Alfred E. Mann Foundation For Scientific Research | Microminiature infusion pump |
WO2002065114A2 (en) | 2001-02-15 | 2002-08-22 | Acist Medical Systems, Inc. | Systems and methods for detection and measurement of elements in a medium |
CN1556716A (en) | 2001-02-22 | 2004-12-22 | ���Ͽع�����˾ | Modular infusion device and method |
US6839753B2 (en) | 2001-02-23 | 2005-01-04 | Cardiopulmonary Corporation | Network monitoring systems for medical devices |
US20030014222A1 (en) | 2001-02-28 | 2003-01-16 | Klass David B. | Method and system for monitoring patient care |
US7072725B2 (en) | 2001-03-26 | 2006-07-04 | Medtronic, Inc. | Implantable therapeutic substance infusion device configuration system |
GB0108213D0 (en) | 2001-04-02 | 2001-05-23 | Glaxo Group Ltd | Medicament dispenser |
US7000008B2 (en) | 2001-04-16 | 2006-02-14 | Sun Microsystems, Inc. | Method, system, and program for providing data updates to a page including multiple regions of dynamic content |
GR1003802B (en) | 2001-04-17 | 2002-02-08 | Micrel �.�.�. ������� ��������� ��������������� ��������� | Tele-medicine system |
US7369897B2 (en) | 2001-04-19 | 2008-05-06 | Neuro And Cardiac Technologies, Llc | Method and system of remotely controlling electrical pulses provided to nerve tissue(s) by an implanted stimulator system for neuromodulation therapies |
US6664893B1 (en) | 2001-04-23 | 2003-12-16 | Cardionet, Inc. | Method for controlling access to medical monitoring device service |
US6494694B2 (en) | 2001-04-25 | 2002-12-17 | Abbott Laboratories | Disposable infusion cassette with low air bubble retention and improved valves |
WO2002088981A1 (en) | 2001-04-27 | 2002-11-07 | The Boeing Company | Analysis of incoming data transmissions |
US20020194329A1 (en) | 2001-05-02 | 2002-12-19 | Shipley Company, L.L.C. | Method and system for facilitating multi-enterprise benchmarking activities and performance analysis |
US7224979B2 (en) | 2001-05-03 | 2007-05-29 | Symantec Corporation | Location-aware service proxies in a short-range wireless environment |
US8034026B2 (en) | 2001-05-18 | 2011-10-11 | Deka Products Limited Partnership | Infusion pump assembly |
US7103578B2 (en) | 2001-05-25 | 2006-09-05 | Roche Diagnostics Operations, Inc. | Remote medical device access |
AU2002309987A1 (en) | 2001-05-25 | 2002-12-09 | Hill-Rom Services, Inc. | Modular patient room |
US7308300B2 (en) | 2001-05-30 | 2007-12-11 | Acist Medical Systems, Inc. | Medical injection system |
JP2003016183A (en) | 2001-06-15 | 2003-01-17 | Ge Medical Systems Global Technology Co Llc | Medical information providing system |
US20040243438A1 (en) | 2001-06-28 | 2004-12-02 | Ilan Mintz | Method and system for cost analysis and benchmarking in the healthcare industry |
AUPR632301A0 (en) | 2001-07-11 | 2001-08-02 | Chee, Frederick Howe-Hui | Infusion apparatus for regulating blood glucose levels |
US6775577B2 (en) | 2001-07-18 | 2004-08-10 | Fresenius Usa, Inc. | Method and system for controlling a medical device |
US6998984B1 (en) | 2001-07-24 | 2006-02-14 | Jonathan Zittrain | State adaptation devices and methods for wireless communications |
US6747556B2 (en) | 2001-07-31 | 2004-06-08 | Medtronic Physio-Control Corp. | Method and system for locating a portable medical device |
US6544212B2 (en) | 2001-07-31 | 2003-04-08 | Roche Diagnostics Corporation | Diabetes management system |
US6648823B2 (en) | 2001-07-31 | 2003-11-18 | Medtronic, Inc. | Method and system of follow-up support for a medical device |
CN1561241B (en) | 2001-07-31 | 2013-07-10 | 斯科特实验室公司 | Apparatuses and methods for titrating drug delivery |
EP2244200A3 (en) | 2001-08-03 | 2011-04-27 | Hill-Rom Services, Inc. | Patient point-of-care computer system |
US6928338B1 (en) | 2001-08-10 | 2005-08-09 | Medtronic, Inc. | Decision information system for drug delivery devices |
US20040147034A1 (en) | 2001-08-14 | 2004-07-29 | Gore Jay Prabhakar | Method and apparatus for measuring a substance in a biological sample |
SE0102918D0 (en) | 2001-08-30 | 2001-08-30 | St Jude Medical | Method of providing software to an implantable medical device system |
US20030115358A1 (en) | 2001-09-04 | 2003-06-19 | Yeong-Hyun Yun | Unified interprocess communication |
AU2002335697A1 (en) | 2001-09-05 | 2003-03-18 | Newbury Networks, Inc. | Position detection and location tracking in a wireless network |
US8152789B2 (en) | 2001-10-23 | 2012-04-10 | Medtronic Minimed, Inc. | System and method for providing closed loop infusion formulation delivery |
US6740072B2 (en) | 2001-09-07 | 2004-05-25 | Medtronic Minimed, Inc. | System and method for providing closed loop infusion formulation delivery |
US6827702B2 (en) | 2001-09-07 | 2004-12-07 | Medtronic Minimed, Inc. | Safety limits for closed-loop infusion pump control |
US20030047126A1 (en) | 2001-09-12 | 2003-03-13 | Tomaschko Daniel K. | System for identifying medical devices |
US7158030B2 (en) | 2001-09-19 | 2007-01-02 | Avante International Technology | Medical assistance and tracking system and method employing smart tags |
US6802810B2 (en) | 2001-09-21 | 2004-10-12 | Active Health Management | Care engine |
US6647299B2 (en) | 2001-09-21 | 2003-11-11 | Medtronic, Inc. | Patient programmer for implantable medical device with audio locator signal |
EP1436029A4 (en) | 2001-09-24 | 2009-12-30 | Scott Lab Inc | Methods and apparatuses for assuring quality and safety of drug administration and medical products and kits |
US20030069963A1 (en) | 2001-09-27 | 2003-04-10 | Nikil Jayant | System and method of quality of service signaling between client and server devices |
US6785774B2 (en) | 2001-10-16 | 2004-08-31 | International Business Machines Corporation | High performance symmetric multiprocessing systems via super-coherent data mechanisms |
CA2465625C (en) | 2001-11-01 | 2007-07-10 | Scott Laboratories, Inc. | User interface for sedation and analgesia delivery systems and methods |
US7383088B2 (en) | 2001-11-07 | 2008-06-03 | Cardiac Pacemakers, Inc. | Centralized management system for programmable medical devices |
US7430608B2 (en) | 2001-12-04 | 2008-09-30 | Siemens Medical Solutions Usa, Inc. | System for processing data acquired from multiple medical devices |
US20050216479A1 (en) | 2001-12-05 | 2005-09-29 | Marcus Wefers | Method, software application and system for incorporating benchmark data into a business software application |
RU2295361C2 (en) | 2001-12-06 | 2007-03-20 | Кардинал Хелс Зоз, Инк | System for performing medical product infusion and carbon dioxide monitoring |
AU2002353064A1 (en) | 2001-12-07 | 2003-06-23 | Skycross, Inc. | Multiple antenna diversity for wireless lan applications |
US7204823B2 (en) | 2001-12-19 | 2007-04-17 | Medtronic Minimed, Inc. | Medication delivery system and monitor |
US7399277B2 (en) | 2001-12-27 | 2008-07-15 | Medtronic Minimed, Inc. | System for monitoring physiological characteristics |
US7343224B2 (en) | 2001-12-31 | 2008-03-11 | B. Braun Medical Inc. | Pharmaceutical compounding systems and methods and information management system for same |
US20030125662A1 (en) | 2002-01-03 | 2003-07-03 | Tuan Bui | Method and apparatus for providing medical treatment therapy based on calculated demand |
US7289948B1 (en) | 2002-01-07 | 2007-10-30 | At&T Corp. | Systems and methods for regularly approximating context-free grammars through transformation |
US6985870B2 (en) | 2002-01-11 | 2006-01-10 | Baxter International Inc. | Medication delivery system |
US10173008B2 (en) * | 2002-01-29 | 2019-01-08 | Baxter International Inc. | System and method for communicating with a dialysis machine through a network |
US8775196B2 (en) | 2002-01-29 | 2014-07-08 | Baxter International Inc. | System and method for notification and escalation of medical data |
US8489427B2 (en) | 2002-01-29 | 2013-07-16 | Baxter International Inc. | Wireless medical data communication system and method |
US20030140928A1 (en) | 2002-01-29 | 2003-07-31 | Tuan Bui | Medical treatment verification system and method |
US20030141981A1 (en) | 2002-01-29 | 2003-07-31 | Tuan Bui | System and method for operating medical devices |
US20030144878A1 (en) | 2002-01-29 | 2003-07-31 | Wilkes Gordon J. | System and method for providing multiple units of measure |
US20030140929A1 (en) | 2002-01-29 | 2003-07-31 | Wilkes Gordon J. | Infusion therapy bar coding system and method |
US20030143746A1 (en) | 2002-01-31 | 2003-07-31 | Sage Burton H. | Self-calibrating body anayte monitoring system |
US20060074920A1 (en) | 2002-02-13 | 2006-04-06 | Marcus Wefers | Method, software application and system for providing benchmarks |
US20050216480A1 (en) | 2002-02-13 | 2005-09-29 | Marcus Wefers | Method, software application and system for providing benchmark data |
AU2003208846A1 (en) | 2002-02-13 | 2003-09-04 | Sap Ag | Method, software application and system for providing benchmark data |
US7024214B2 (en) | 2002-02-26 | 2006-04-04 | Microsoft Corporation | Synchronizing over a number of synchronization mechanisms using flexible rules |
US20030212379A1 (en) | 2002-02-26 | 2003-11-13 | Bylund Adam David | Systems and methods for remotely controlling medication infusion and analyte monitoring |
US8504179B2 (en) | 2002-02-28 | 2013-08-06 | Smiths Medical Asd, Inc. | Programmable medical infusion pump |
US6852104B2 (en) | 2002-02-28 | 2005-02-08 | Smiths Medical Md, Inc. | Programmable insulin pump |
US7142190B2 (en) | 2002-02-28 | 2006-11-28 | Motorola, Inc. | Cellular communication handsets having variable appearance housings and methods therefor |
US7092943B2 (en) | 2002-03-01 | 2006-08-15 | Enterasys Networks, Inc. | Location based data |
US6892278B2 (en) | 2002-03-05 | 2005-05-10 | Sun Microsystems, Inc. | Method and apparatus for efficiently implementing a last-in first-out buffer |
US7108680B2 (en) | 2002-03-06 | 2006-09-19 | Codman & Shurtleff, Inc. | Closed-loop drug delivery system |
GB0206792D0 (en) | 2002-03-22 | 2002-05-01 | Leuven K U Res & Dev | Normoglycemia |
GB0207890D0 (en) | 2002-04-05 | 2002-05-15 | Ritson Peter A | Child resistant closure cap |
US8620677B2 (en) | 2002-04-09 | 2013-12-31 | Pcrs, Inc. | Online, interactive evaluation of research performance |
US20080041942A1 (en) | 2002-04-17 | 2008-02-21 | Aissa Nebil B | Biometric Multi-Purpose Terminal, Payroll and Work Management System and Related Methods |
US8239780B2 (en) | 2002-04-23 | 2012-08-07 | Draeger Medical Systems, Inc. | System and user interface supporting trend indicative display of patient medical parameters |
US20040167804A1 (en) | 2002-04-30 | 2004-08-26 | Simpson Thomas L.C. | Medical data communication notification and messaging system and method |
US20040167465A1 (en) | 2002-04-30 | 2004-08-26 | Mihai Dan M. | System and method for medical device authentication |
US20050065817A1 (en) | 2002-04-30 | 2005-03-24 | Mihai Dan M. | Separation of validated information and functions in a healthcare system |
US20040172301A1 (en) | 2002-04-30 | 2004-09-02 | Mihai Dan M. | Remote multi-purpose user interface for a healthcare system |
US20040176667A1 (en) | 2002-04-30 | 2004-09-09 | Mihai Dan M. | Method and system for medical device connectivity |
US20030204416A1 (en) | 2002-04-30 | 2003-10-30 | Sayeh Radpay | System and method for facilitating time-based infusion orders |
US20030204781A1 (en) | 2002-04-30 | 2003-10-30 | International Business Machines Corporation | Method and apparatus for displaying diagnostic recommendations for monitored processes |
US8234128B2 (en) | 2002-04-30 | 2012-07-31 | Baxter International, Inc. | System and method for verifying medical device operational parameters |
US20050055242A1 (en) | 2002-04-30 | 2005-03-10 | Bryan Bello | System and method for medical data tracking, analysis and reporting for healthcare system |
US7457804B2 (en) | 2002-05-10 | 2008-11-25 | Medrad, Inc. | System and method for automated benchmarking for the recognition of best medical practices and products and for establishing standards for medical procedures |
US20030212821A1 (en) | 2002-05-13 | 2003-11-13 | Kiyon, Inc. | System and method for routing packets in a wired or wireless network |
CN1669036A (en) | 2002-05-16 | 2005-09-14 | 斯科特实验室公司 | User authorization system and method for a sedation and analgesia system |
FR2839650B1 (en) | 2002-05-17 | 2005-04-01 | Ela Medical Sa | TELEASSISTANCE SYSTEM FOR PROGRAMMING ACTIVE IMPLANTABLE MEDICAL DEVICES SUCH AS CARDIAC STIMULATORS, DEFIBRILLATORS, CARDIOVERTERS OR MULTISITE DEVICES |
US6869538B2 (en) | 2002-05-24 | 2005-03-22 | Baxter International, Inc. | Method and apparatus for controlling a medical fluid heater |
US20040078231A1 (en) | 2002-05-31 | 2004-04-22 | Wilkes Gordon J. | System and method for facilitating and administering treatment to a patient, including clinical decision making, order workflow and integration of clinical documentation |
US20040128163A1 (en) | 2002-06-05 | 2004-07-01 | Goodman Philip Holden | Health care information management apparatus, system and method of use and doing business |
DE60221905T2 (en) | 2002-06-07 | 2008-05-15 | Nokia Corp. | METHOD FOR SENDING CONNECTION-ORIENTED OR CONNECTED DATA |
US20040225252A1 (en) | 2002-06-14 | 2004-11-11 | John Gillespie | System and method for operating an infusion pump |
US7398279B2 (en) | 2002-06-28 | 2008-07-08 | Francis J. Muno, Jr. | Method, routines and system for identification of imprints on dosage forms |
US7327705B2 (en) | 2002-07-03 | 2008-02-05 | Massachusetts Institute Of Technology | Hybrid wireless network for data collection and distribution |
US20040008123A1 (en) | 2002-07-15 | 2004-01-15 | Battelle Memorial Institute | System and method for tracking medical devices |
US7238164B2 (en) | 2002-07-19 | 2007-07-03 | Baxter International Inc. | Systems, methods and apparatuses for pumping cassette-based therapies |
US20040068230A1 (en) | 2002-07-24 | 2004-04-08 | Medtronic Minimed, Inc. | System for providing blood glucose measurements to an infusion device |
US7278983B2 (en) | 2002-07-24 | 2007-10-09 | Medtronic Minimed, Inc. | Physiological monitoring device for controlling a medication infusion device |
US20040064435A1 (en) | 2002-07-26 | 2004-04-01 | Ahmad-Maher Moubayed | Clinical assessment and diagnostic tool for use with peristaltic pump |
US7565301B2 (en) | 2002-07-26 | 2009-07-21 | Curlin Medical Inc. | System and method for remotely operating a peristaltic pump |
US7289815B2 (en) | 2002-08-15 | 2007-10-30 | International Business Machines Corporation | Transponder subsystem for supporting location awareness in wireless networks |
US7275156B2 (en) | 2002-08-30 | 2007-09-25 | Xerox Corporation | Method and apparatus for establishing and using a secure credential infrastructure |
US20040133441A1 (en) | 2002-09-04 | 2004-07-08 | Jeffrey Brady | Method and program for transferring information from an application |
DE10242003A1 (en) | 2002-09-11 | 2004-03-25 | Siemens Ag | Medical knowledge accessibility device for giving expert knowledge to a user of examination equipment like a physician has a device to transfer a patient's case images to the user's own equipment |
US7150741B2 (en) | 2002-09-20 | 2006-12-19 | Advanced Neuromodulation Systems, Inc. | Programmable dose control module |
US20040064341A1 (en) | 2002-09-27 | 2004-04-01 | Langan Pete F. | Systems and methods for healthcare risk solutions |
US20040122530A1 (en) | 2002-09-30 | 2004-06-24 | Steffen Hansen | Indicating device with estimating feature |
US20040064342A1 (en) | 2002-09-30 | 2004-04-01 | Browne David W. | Health care protocols |
AU2003287073B2 (en) | 2002-10-11 | 2009-01-08 | Becton, Dickinson And Company | System and method for initiating and maintaining continuous, long-term control of a concentration of a substance in a patient using a feedback or model-based controller coupled to a single-needle or multi-needle intradermal (ID) delivery device |
EP1553870A2 (en) | 2002-10-15 | 2005-07-20 | Philips Intellectual Property & Standards GmbH | Method for the presentation of information concerning variations of the perfusion |
US20040073811A1 (en) | 2002-10-15 | 2004-04-15 | Aleksey Sanin | Web service security filter |
DE60307882T2 (en) | 2002-10-31 | 2007-03-15 | Medtronic, Inc., Minneapolis | FAILSAFE PROGRAMMING OF AN IMPLANTABLE MEDICAL DEVICE |
US20050038680A1 (en) | 2002-12-19 | 2005-02-17 | Mcmahon Kevin Lee | System and method for glucose monitoring |
AU2003287926A1 (en) | 2002-12-23 | 2004-07-14 | M2 Medical A/S | A disposable, wearable insulin dispensing device, a combination of such a device and a programming controller and a method of controlling the operation of such a device |
US7835927B2 (en) | 2002-12-27 | 2010-11-16 | Carefusion 303, Inc. | Medication management system |
US7295119B2 (en) | 2003-01-22 | 2007-11-13 | Wireless Valley Communications, Inc. | System and method for indicating the presence or physical location of persons or devices in a site specific representation of a physical environment |
US6922148B2 (en) | 2003-01-29 | 2005-07-26 | George J. Despotis | Patient identification system |
TW200426656A (en) * | 2003-02-01 | 2004-12-01 | Baxter Int | Separation of validated information and functions in a healthcare system |
AR042989A1 (en) | 2003-02-01 | 2005-07-13 | Baxter Int | SYSTEM AND METHOD OF WIRELESS MEDICAL DATA COMMUNICATION |
IL154243A0 (en) | 2003-02-02 | 2003-09-17 | Silex Projectors Ltd | Stable infusion device |
US7230529B2 (en) | 2003-02-07 | 2007-06-12 | Theradoc, Inc. | System, method, and computer program for interfacing an expert system to a clinical information system |
AU2003900854A0 (en) | 2003-02-26 | 2003-03-13 | Sesay, Sahid | General purpose electronic controller software |
US7346025B2 (en) | 2003-02-28 | 2008-03-18 | Lucent Technologies Inc. | Portable wireless gateway |
MXPA05009455A (en) | 2003-03-04 | 2006-04-07 | Johnson & Johnson | Patient monitoring and drug delivery system and method of use. |
US20040176980A1 (en) | 2003-03-07 | 2004-09-09 | Clemens Bulitta | Comprehensive standardized process change management model framework and method for creating customized process model for a healthcare organization using the framework |
US7300418B2 (en) | 2003-03-10 | 2007-11-27 | Siemens Medical Solutions Health Services Corporation | Healthcare system supporting multiple network connected fluid administration pumps |
US8090590B2 (en) | 2003-03-10 | 2012-01-03 | Intuit Inc. | Electronic personal health record system |
US20040193325A1 (en) | 2003-03-25 | 2004-09-30 | David Bonderud | Method and apparatus to prevent medication error in a networked infusion system |
US7913159B2 (en) | 2003-03-28 | 2011-03-22 | Microsoft Corporation | System and method for real-time validation of structured data files |
CA2519955C (en) | 2003-03-28 | 2013-08-13 | Alaris Medical Systems, Inc. | Infusion data communication system |
CA2520880A1 (en) | 2003-04-18 | 2004-11-04 | Insulet Corporation | User interface for infusion pump remote controller and method of using the same |
BRPI0409658A (en) | 2003-04-23 | 2006-04-18 | Vasogen Ireland Ltd | distribution systems |
US20040215278A1 (en) | 2003-04-25 | 2004-10-28 | Wim Stegink | Method and apparatus for locally upgrading implanted reprogrammable medical devices |
US20060074381A1 (en) | 2003-04-30 | 2006-04-06 | Luis Malave | Medical device initialization method & system |
US20050038669A1 (en) | 2003-05-02 | 2005-02-17 | Orametrix, Inc. | Interactive unified workstation for benchmarking and care planning |
JP2007503282A (en) | 2003-05-16 | 2007-02-22 | オドリバク、アンドリュー | System and method for automatic processing of endoscopic images |
US7079035B2 (en) | 2003-05-19 | 2006-07-18 | Ge Medical Systems Information Technologies, Inc. | Method and apparatus for controlling an alarm while monitoring |
US8460243B2 (en) | 2003-06-10 | 2013-06-11 | Abbott Diabetes Care Inc. | Glucose measuring module and insulin pump combination |
US20090057399A1 (en) | 2003-06-17 | 2009-03-05 | United Security Applications Id, Inc. | Electronic security system for monitoring and recording activity and data relating to institutions and clients thereof |
WO2004112603A1 (en) | 2003-06-19 | 2004-12-29 | Wayne State University | System for identifying patient response to anesthesia infusion |
JP4583733B2 (en) | 2003-07-04 | 2010-11-17 | テルモ株式会社 | Syringe pump |
WO2005007223A2 (en) | 2003-07-16 | 2005-01-27 | Sasha John | Programmable medical drug delivery systems and methods for delivery of multiple fluids and concentrations |
US7185288B2 (en) | 2003-07-18 | 2007-02-27 | Dade Behring Inc. | Operator interface module segmented by function in an automatic clinical analyzer |
US20050055244A1 (en) | 2003-07-18 | 2005-03-10 | Janet Mullan | Wireless medical communication system and method |
US7967749B2 (en) | 2003-07-23 | 2011-06-28 | Ge Medical Systems Information Technologies, Inc. | Monitoring system and method using rules |
US20050027560A1 (en) | 2003-07-28 | 2005-02-03 | Deborah Cook | Interactive multi-user medication and medical history management method |
US20050027567A1 (en) | 2003-07-29 | 2005-02-03 | Taha Amer Jamil | System and method for health care data collection and management |
US7591801B2 (en) | 2004-02-26 | 2009-09-22 | Dexcom, Inc. | Integrated delivery device for continuous glucose sensor |
US8060173B2 (en) | 2003-08-01 | 2011-11-15 | Dexcom, Inc. | System and methods for processing analyte sensor data |
US8200775B2 (en) | 2005-02-01 | 2012-06-12 | Newsilike Media Group, Inc | Enhanced syndication |
US6899695B2 (en) | 2003-08-08 | 2005-05-31 | Hector J. Herrera | Medication security apparatus and method |
US20050043620A1 (en) | 2003-08-20 | 2005-02-24 | Siemens Medical Solutions Usa, Inc. | Diagnostic medical ultrasound system communication network architecture and method |
US20050049910A1 (en) | 2003-08-28 | 2005-03-03 | Cemer Innovation, Inc. | System and method for management interface for clinical environments |
US7523401B1 (en) | 2003-09-03 | 2009-04-21 | Theoris Software, Llc | System and method for providing a browser-based user interface |
US7258534B2 (en) | 2003-09-22 | 2007-08-21 | Hospira, Inc. | Fluid delivery device identification and loading system |
US20050108057A1 (en) | 2003-09-24 | 2005-05-19 | Michal Cohen | Medical device management system including a clinical system interface |
US8180802B2 (en) | 2003-09-30 | 2012-05-15 | International Business Machines Corporation | Extensible decimal identification system for ordered nodes |
US20060089855A1 (en) | 2003-10-07 | 2006-04-27 | Holland Geoffrey N | Medication management system |
US20060089854A1 (en) | 2003-10-07 | 2006-04-27 | Holland Geoffrey N | Medication management system |
US20060100907A1 (en) | 2003-10-07 | 2006-05-11 | Holland Geoffrey N | Medication management system |
US7490021B2 (en) | 2003-10-07 | 2009-02-10 | Hospira, Inc. | Method for adjusting pump screen brightness |
US20050278194A1 (en) | 2003-10-07 | 2005-12-15 | Holland Geoffrey N | Medication management system |
US20070214003A1 (en) | 2003-10-07 | 2007-09-13 | Holland Geoffrey N | Medication management system |
US7895053B2 (en) * | 2003-10-07 | 2011-02-22 | Hospira, Inc. | Medication management system |
US9123077B2 (en) * | 2003-10-07 | 2015-09-01 | Hospira, Inc. | Medication management system |
EP1704501A2 (en) | 2003-10-07 | 2006-09-27 | Hospira, Inc. | Medication management system |
US7029456B2 (en) | 2003-10-15 | 2006-04-18 | Baxter International Inc. | Medical fluid therapy flow balancing and synchronization system |
US20050102669A1 (en) | 2003-10-15 | 2005-05-12 | Siemens Medical Solutions Usa, Inc. | Software installation file verification media and methods for medical equipment |
US20050251418A1 (en) | 2003-10-15 | 2005-11-10 | Cerner Innovation, Inc. | System and method for processing ad hoc orders in an automated patient care environment |
US20050086071A1 (en) | 2003-10-15 | 2005-04-21 | Fox Charles S.Jr. | System and method for managing patient care |
US20050086072A1 (en) | 2003-10-15 | 2005-04-21 | Fox Charles S.Jr. | Task-based system and method for managing patient care through automated recognition |
KR100567837B1 (en) | 2003-10-24 | 2006-04-05 | 케이제이헬스케어 주식회사 | Insulin pump combined with mobile which detects a blood glucose, network system for transmitting control imformation of the insulin pump |
DE10352456A1 (en) | 2003-11-07 | 2005-07-28 | Basibüyük, Halil | Method for administering a pharmaceutical, especially insulin, where the amount administered is calculated from measurements of a blood parameter, stored in a data processor |
US7256888B2 (en) | 2003-11-07 | 2007-08-14 | Cardial Health 303, Inc. | Fluid verification system and method for infusions |
US20050102167A1 (en) | 2003-11-12 | 2005-05-12 | Kapoor Ashok K. | Provisioning and controlling medical instruments using wireless data communication |
US7092796B2 (en) | 2003-11-14 | 2006-08-15 | Cardinal Health 303, Inc. | System and method for verifying connection of correct fluid supply to an infusion pump |
US20080052704A1 (en) | 2006-06-02 | 2008-02-28 | Apple Computer, Inc. | Media management system for management of games acquired from a media server |
WO2005054993A2 (en) | 2003-11-25 | 2005-06-16 | Computer Associates Think, Inc. | Web service performance index |
US8020564B2 (en) * | 2003-12-01 | 2011-09-20 | Carefusion 303, Inc. | System and method for analyzing medical treatment data |
ITPR20030105A1 (en) | 2003-12-03 | 2005-06-04 | Alberto Rizzo | SELF-LOCKING SYRINGE SELF-LOCKING SAFETY WITH |
EP1704505A2 (en) | 2003-12-04 | 2006-09-27 | Smiths Medical MD, Inc. | Programming medical pumps with electronic standing order template |
EP1709778A1 (en) | 2003-12-05 | 2006-10-11 | Cardinal Health 303, Inc. | Discovery and connection management with mobile systems manager |
JP5255770B2 (en) | 2003-12-05 | 2013-08-07 | ケアフュージョン 303、インコーポレイテッド | System and method for network monitoring of multiple medical devices |
EP1694386B1 (en) | 2003-12-05 | 2017-05-03 | CareFusion 303, Inc. | Patient-controlled analgesia with patient monitoring system |
EP2329763B1 (en) | 2003-12-09 | 2017-06-21 | DexCom, Inc. | Signal processing for continuous analyte sensor |
US7263213B2 (en) | 2003-12-11 | 2007-08-28 | Lumidigm, Inc. | Methods and systems for estimation of personal characteristics from biometric measurements |
WO2005059804A2 (en) | 2003-12-16 | 2005-06-30 | Alexza Pharmaceuticals, Inc. | Methods for monitoring severity of panic attacks and other rapidly evolving medical events in real-time |
US20050137522A1 (en) | 2003-12-17 | 2005-06-23 | Thomas Aoki | System for infusing insulin to a subject to improve impaired hepatic glucose processing |
US7657443B2 (en) | 2003-12-19 | 2010-02-02 | Carefusion 303, Inc. | Intravenous medication harm index system |
US20050137573A1 (en) | 2003-12-19 | 2005-06-23 | Animas Corporation | System, method, and communication hub for controlling external infusion device |
US7181493B2 (en) | 2003-12-23 | 2007-02-20 | Unisys Corporation | Platform independent model-based framework for exchanging information in the justice system |
US7255683B2 (en) | 2003-12-31 | 2007-08-14 | Cardinal Health 303, Inc. | System for detecting the status of a vent associated with a fluid supply upstream of an infusion pump |
US7301451B2 (en) | 2003-12-31 | 2007-11-27 | Ge Medical Systems Information Technologies, Inc. | Notification alarm transfer methods, system, and device |
US20050154769A1 (en) | 2004-01-13 | 2005-07-14 | Llumen, Inc. | Systems and methods for benchmarking business performance data against aggregated business performance data |
DE102004006842A1 (en) | 2004-02-12 | 2005-09-15 | Dräger Medical AG & Co. KGaA | Method and device for activating a medical device |
EP1718198A4 (en) | 2004-02-17 | 2008-06-04 | Therasense Inc | Method and system for providing data communication in continuous glucose monitoring and management system |
US8954336B2 (en) | 2004-02-23 | 2015-02-10 | Smiths Medical Asd, Inc. | Server for medical device |
US20050197554A1 (en) | 2004-02-26 | 2005-09-08 | Michael Polcha | Composite thin-film glucose sensor |
US8808228B2 (en) | 2004-02-26 | 2014-08-19 | Dexcom, Inc. | Integrated medicament delivery device for use with continuous analyte sensor |
US7739126B1 (en) | 2004-03-02 | 2010-06-15 | Cave Consulting Group | Method, system, and computer program product for physician efficiency measurement and patient health risk stratification |
JP2005275999A (en) | 2004-03-26 | 2005-10-06 | Fuji Photo Film Co Ltd | Medical information providing method, and terminal and server to be used for the same |
US7905710B2 (en) | 2004-03-26 | 2011-03-15 | Hospira, Inc. | System and method for improved low flow medical pump delivery |
JP2005284846A (en) | 2004-03-30 | 2005-10-13 | Fuji Photo Film Co Ltd | Diagnostic support system, method for use in the same, and server |
US20060009727A1 (en) | 2004-04-08 | 2006-01-12 | Chf Solutions Inc. | Method and apparatus for an extracorporeal control of blood glucose |
WO2005109119A2 (en) | 2004-04-24 | 2005-11-17 | Inrange Systems, Inc. | Integrated, non-sequential, remote medication management and compliance system |
US20050273367A1 (en) | 2004-05-14 | 2005-12-08 | Accelere, Inc. | Secure health information connectivity system |
US20050261660A1 (en) | 2004-05-24 | 2005-11-24 | Choi Soo B | Method for controlling insulin pump using Bluetooth protocol |
US8518021B2 (en) | 2004-05-27 | 2013-08-27 | Baxter International Inc. | Apparatus and method for therapeutic delivery of medication |
US20050277873A1 (en) | 2004-05-27 | 2005-12-15 | Janice Stewart | Identification information recognition system for a medical device |
US7927313B2 (en) | 2004-05-27 | 2011-04-19 | Baxter International Inc. | Medical device configuration based on recognition of identification information |
WO2005119524A2 (en) | 2004-06-04 | 2005-12-15 | Therasense, Inc. | Diabetes care host-client architecture and data management system |
US7697994B2 (en) | 2004-06-18 | 2010-04-13 | Medtronic, Inc. | Remote scheduling for management of an implantable medical device |
US7565197B2 (en) | 2004-06-18 | 2009-07-21 | Medtronic, Inc. | Conditional requirements for remote medical device programming |
US20060009734A1 (en) | 2004-07-07 | 2006-01-12 | Martin James F | Dosage control for drug delivery system |
US7319386B2 (en) | 2004-08-02 | 2008-01-15 | Hill-Rom Services, Inc. | Configurable system for alerting caregivers |
US20060079831A1 (en) | 2004-08-18 | 2006-04-13 | Gilbert Gregory F | Quantitative chronological medical infusion device |
US20060042139A1 (en) | 2004-08-25 | 2006-03-02 | John Mendes | Athletic medical bracelet |
US20060047270A1 (en) | 2004-08-27 | 2006-03-02 | Shelton Brian M | Drug delivery apparatus and method for automatically reducing drug dosage |
US8398592B2 (en) | 2004-09-07 | 2013-03-19 | Thomas Leibner-Druska | Medication data transfer system and method for patient infusions |
US7758562B2 (en) | 2004-09-09 | 2010-07-20 | Plc Medical Systems, Inc. | Patient hydration system with a redundant monitoring of hydration fluid infusion |
US9820658B2 (en) | 2006-06-30 | 2017-11-21 | Bao Q. Tran | Systems and methods for providing interoperability among healthcare devices |
US20060064020A1 (en) | 2004-09-20 | 2006-03-23 | Medtronic, Inc. | Clinic dashboard monitor |
US20060116904A1 (en) | 2004-10-01 | 2006-06-01 | Harold Brem | Wound electronic medical record system |
US8099296B2 (en) | 2004-10-01 | 2012-01-17 | General Electric Company | System and method for rules-based context management in a medical environment |
US7167755B2 (en) | 2004-10-05 | 2007-01-23 | Cardiac Pacemakers, Inc. | Adaptive software configuration for a medical device |
US20060111943A1 (en) | 2004-11-15 | 2006-05-25 | Wu Harry C | Method and system to edit and analyze longitudinal personal health data using a web-based application |
US20060122481A1 (en) | 2004-11-22 | 2006-06-08 | Crispian Lee Sievenpiper | System and method for location based remote services |
US20060116907A1 (en) | 2004-11-30 | 2006-06-01 | Rhodes Neal A | System and method for improving performance of authorization for prescription drugs |
US20060129435A1 (en) | 2004-12-15 | 2006-06-15 | Critical Connection Inc. | System and method for providing community health data services |
US7568619B2 (en) | 2004-12-15 | 2009-08-04 | Alcon, Inc. | System and method for identifying and controlling ophthalmic surgical devices and components |
US20060129434A1 (en) | 2004-12-15 | 2006-06-15 | Critical Connection Inc. | System and method for disseminating healthcare data from a database |
DE102004060930B4 (en) | 2004-12-17 | 2014-09-18 | Siemens Aktiengesellschaft | Securing a medical device |
US20060136266A1 (en) | 2004-12-20 | 2006-06-22 | E-San Limited | Medicinal product order processing system |
FR2880451B1 (en) | 2005-01-04 | 2007-08-17 | Gred Sa | SERVER, METHOD AND INTERMEDIATION NETWORK FOR CONSULTING AND REFERENCING MEDICAL INFORMATION |
US20060173260A1 (en) | 2005-01-31 | 2006-08-03 | Gmms Ltd | System, device and method for diabetes treatment and monitoring |
US7547281B2 (en) | 2005-02-01 | 2009-06-16 | Medtronic Minimed, Inc. | Algorithm sensor augmented bolus estimator for semi-closed loop infusion system |
US20060173715A1 (en) | 2005-02-01 | 2006-08-03 | Hao Wang | Health information system and method |
JP4991574B2 (en) | 2005-02-11 | 2012-08-01 | ケアフュージョン 303、インコーポレイテッド | Drug management identification system and method |
US8956292B2 (en) | 2005-03-02 | 2015-02-17 | Spacelabs Healthcare Llc | Trending display of patient wellness |
US8740789B2 (en) | 2005-03-03 | 2014-06-03 | Cardiac Pacemakers, Inc. | Automatic etiology sequencing system and method |
WO2006094291A1 (en) | 2005-03-03 | 2006-09-08 | Raytheon Company | Incident command system |
CN101180093B (en) | 2005-03-21 | 2012-07-18 | 雅培糖尿病护理公司 | Method and system for providing integrated medication infusion and analyte monitoring system |
US7656810B2 (en) | 2005-03-25 | 2010-02-02 | Microsoft Corporation | System and method for monitoring and reacting to peer-to-peer network metrics |
US20090054754A1 (en) | 2007-08-21 | 2009-02-26 | Mcmahon Dave | Clinician-controlled semi-automated medication management |
US7896842B2 (en) | 2005-04-11 | 2011-03-01 | Hospira, Inc. | System for guiding a user during programming of a medical device |
US7945452B2 (en) | 2005-04-11 | 2011-05-17 | Hospira, Inc. | User interface improvements for medical devices |
WO2006122167A2 (en) | 2005-05-10 | 2006-11-16 | Cardinal Health 303, Inc | Medication safety system featuring a multiplexed rfid interrogator panel |
JP2008541280A (en) | 2005-05-11 | 2008-11-20 | カーディナル ヘルス 303 インコーポレイテッド | Drug administration data setting analyzer |
US20060258985A1 (en) | 2005-05-11 | 2006-11-16 | Russell Claudia J | Graphical display of medication limits and delivery program |
US7509156B2 (en) | 2005-05-18 | 2009-03-24 | Clarian Health Partners, Inc. | System for managing glucose levels in patients with diabetes or hyperglycemia |
US7613118B2 (en) | 2005-05-19 | 2009-11-03 | Cisco Technology, Inc. | Detecting change in a transport protocol window size without data transmission |
US7849620B2 (en) | 2005-05-31 | 2010-12-14 | Hand Held Products, Inc. | Bar coded wristband |
US7309001B2 (en) | 2005-05-31 | 2007-12-18 | Catalina Marketing Corporation | System to provide specific messages to patients |
US20060277206A1 (en) | 2005-06-02 | 2006-12-07 | Bailey Philip G | Automated reporting of computer system metrics |
US20060287885A1 (en) | 2005-06-21 | 2006-12-21 | Frick W V | Treatment management system |
CN101238464A (en) | 2005-06-27 | 2008-08-06 | 诺沃-诺迪斯克有限公司 | User interface for delivery system providing shortcut navigation |
US20070016443A1 (en) | 2005-07-13 | 2007-01-18 | Vitality, Inc. | Medication compliance systems, methods and devices with configurable and adaptable escalation engine |
US7908594B2 (en) | 2005-07-29 | 2011-03-15 | Cisco Technology, Inc. | External programmatic interface for IOS CLI compliant routers |
US20070083870A1 (en) | 2005-07-29 | 2007-04-12 | Tomochika Kanakogi | Methods and apparatus for task sharing among a plurality of processors |
US8051414B2 (en) | 2005-08-01 | 2011-11-01 | Siemens Aktiengesellschaft | Method and system for remote software updating of a medical device |
US20070093786A1 (en) | 2005-08-16 | 2007-04-26 | Medtronic Minimed, Inc. | Watch controller for a medical device |
US20070060870A1 (en) | 2005-08-16 | 2007-03-15 | Tolle Mike Charles V | Controller device for an infusion pump |
EP1933929A4 (en) | 2005-09-12 | 2011-03-09 | Ethicon Endo Surgery Inc | Apparatus and methods for controlling and automating fluid infusion activities |
US7713240B2 (en) | 2005-09-13 | 2010-05-11 | Medtronic Minimed, Inc. | Modular external infusion device |
US7927284B2 (en) | 2005-09-16 | 2011-04-19 | Cardiac Pacemakers, Inc. | Quantifying hemodynamic response to drug therapy using implantable sensor |
JP4103910B2 (en) | 2005-09-26 | 2008-06-18 | 株式会社日立製作所 | Analysis result management method and apparatus |
US20070078314A1 (en) | 2005-09-30 | 2007-04-05 | Grounsell Richard L | System and method for measuring and predicting insulin dosing rates |
US20070106126A1 (en) | 2005-09-30 | 2007-05-10 | Mannheimer Paul D | Patient monitoring alarm escalation system and method |
US20070088333A1 (en) | 2005-10-13 | 2007-04-19 | G&L Consulting, Llc | Method and system for infusing an osmotic solute into a patient and providing feedback control of the infusing rate |
US7420472B2 (en) | 2005-10-16 | 2008-09-02 | Bao Tran | Patient monitoring apparatus |
US7621009B2 (en) | 2005-11-16 | 2009-11-24 | Basim Elhabashy | Surgical coordinator for anesthesiologist and methods of use |
US7704226B2 (en) | 2005-11-17 | 2010-04-27 | Medtronic Minimed, Inc. | External infusion device with programmable capabilities to time-shift basal insulin and method of using the same |
US9259526B2 (en) | 2005-11-21 | 2016-02-16 | Acist Medical Systems, Inc. | Medical fluid injection system and method for guided setup |
US20070136098A1 (en) | 2005-12-12 | 2007-06-14 | Smythe Alan H | System and method for providing a secure feature set distribution infrastructure for medical device management |
AU2006325783B2 (en) | 2005-12-14 | 2011-09-08 | Welch Allyn, Inc. | Medical device wireless adapter |
EP1801718A1 (en) | 2005-12-21 | 2007-06-27 | F. Hoffmann-La Roche AG | Method for operating a computer controlled dosing device for liquid medicine in situations of travel time shift |
US8666760B2 (en) | 2005-12-30 | 2014-03-04 | Carefusion 303, Inc. | Medication order processing and reconciliation |
US7885725B2 (en) | 2006-01-05 | 2011-02-08 | Dunn Lawrence A | Devices, systems and methods for point-of-use medication control |
US8357114B2 (en) | 2006-01-06 | 2013-01-22 | Acelrx Pharmaceuticals, Inc. | Drug dispensing device with flexible push rod |
TW200806292A (en) | 2006-01-25 | 2008-02-01 | Synta Pharmaceuticals Corp | Vinyl-phenyl derivatives for inflammation and immune-related uses |
US8579884B2 (en) | 2006-02-09 | 2013-11-12 | Deka Products Limited Partnership | Infusion pump assembly |
US20070191973A1 (en) | 2006-02-10 | 2007-08-16 | General Electric Company | Apparatus and method for configuring, processing and viewing state based data |
US8133194B2 (en) | 2006-02-22 | 2012-03-13 | Henry Ford Health System | System and method for delivery of regional citrate anticoagulation to extracorporeal blood circuits |
US7981034B2 (en) | 2006-02-28 | 2011-07-19 | Abbott Diabetes Care Inc. | Smart messages and alerts for an infusion delivery and management system |
US7785463B2 (en) | 2006-03-17 | 2010-08-31 | Children's Hospital Medical Center | Extracorporeal renal replacement modeling system |
US7671733B2 (en) | 2006-03-17 | 2010-03-02 | Koninklijke Philips Electronics N.V. | Method and system for medical alarm monitoring, reporting and normalization |
WO2007126948A2 (en) | 2006-03-28 | 2007-11-08 | Hospira, Inc. | Medication administration and management system and method |
EP1839566A1 (en) | 2006-03-29 | 2007-10-03 | F. Hoffmann-La Roche AG | Method and assembly for the observation of a medical instrument. |
DE102006015291B4 (en) | 2006-04-01 | 2015-10-29 | Drägerwerk AG & Co. KGaA | Procedure for setting a patient monitor |
US7806852B1 (en) | 2006-04-03 | 2010-10-05 | Jurson Phillip A | Method and apparatus for patient-controlled medical therapeutics |
WO2007117705A2 (en) | 2006-04-08 | 2007-10-18 | Vialogy Corp. | Software enabled video and sensor interoperability system and method |
WO2007126360A1 (en) | 2006-04-27 | 2007-11-08 | Gambro Lundia Ab | Remote controlled medical apparatus |
US8348885B2 (en) | 2006-04-28 | 2013-01-08 | Medtronic Minimed, Inc. | Remote monitoring for networked fluid infusion systems |
US20070255126A1 (en) | 2006-04-28 | 2007-11-01 | Moberg Sheldon B | Data communication in networked fluid infusion systems |
US8073008B2 (en) | 2006-04-28 | 2011-12-06 | Medtronic Minimed, Inc. | Subnetwork synchronization and variable transmit synchronization techniques for a wireless medical device network |
US20070258395A1 (en) | 2006-04-28 | 2007-11-08 | Medtronic Minimed, Inc. | Wireless data communication protocols for a medical device network |
US20070253021A1 (en) | 2006-04-28 | 2007-11-01 | Medtronic Minimed, Inc. | Identification of devices in a medical device network and wireless data communication techniques utilizing device identifiers |
US20070254593A1 (en) | 2006-04-28 | 2007-11-01 | Medtronic Minimed, Inc. | Wireless data communication for a medical device network that supports a plurality of data communication modes |
US7942844B2 (en) | 2006-04-28 | 2011-05-17 | Medtronic Minimed, Inc. | Remote monitoring for networked fluid infusion systems |
US7551078B2 (en) | 2006-05-08 | 2009-06-23 | Ihc Intellectual Asset Management, Llc | Device alert system and method |
EP2015804B1 (en) | 2006-05-10 | 2019-02-13 | F. Hoffmann-La Roche AG | Infusion apparatus with a data storage device |
US20090209938A1 (en) | 2006-05-29 | 2009-08-20 | Wristop Technologies Oy | Apparatus and method for dosing drug and wireless remote control of a drug pump |
US8979753B2 (en) | 2006-05-31 | 2015-03-17 | University Of Rochester | Identifying risk of a medical event |
ATE553695T1 (en) | 2006-06-13 | 2012-05-15 | Carefusion 303 Inc | SYSTEM AND METHOD FOR OPTIMIZED CONTROL OF PCA AND PCEA SYSTEMS |
WO2007149533A2 (en) | 2006-06-19 | 2007-12-27 | Dose Safety | System, method and article for controlling the dispensing of insulin |
US20070299695A1 (en) | 2006-06-23 | 2007-12-27 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Customized visual marking for medication labeling |
US20070299687A1 (en) | 2006-06-23 | 2007-12-27 | Pamela Palmer | Inpatient system for patient-controlled delivery of oral transmucosal medications dosed as needed |
US8417547B2 (en) | 2006-06-29 | 2013-04-09 | The Invention Science Fund I, Llc | Verification technique for patient diagnosis and treatment |
US7724147B2 (en) | 2006-07-13 | 2010-05-25 | Cardinal Health 303, Inc. | Medical notification apparatus and method |
US20080126969A1 (en) | 2006-08-03 | 2008-05-29 | Blomquist Michael L | Interface for medical infusion pump |
US8149131B2 (en) | 2006-08-03 | 2012-04-03 | Smiths Medical Asd, Inc. | Interface for medical infusion pump |
US8858526B2 (en) | 2006-08-03 | 2014-10-14 | Smiths Medical Asd, Inc. | Interface for medical infusion pump |
US8435206B2 (en) | 2006-08-03 | 2013-05-07 | Smiths Medical Asd, Inc. | Interface for medical infusion pump |
US8965707B2 (en) * | 2006-08-03 | 2015-02-24 | Smiths Medical Asd, Inc. | Interface for medical infusion pump |
US20080033966A1 (en) | 2006-08-04 | 2008-02-07 | Mark Frederick Wahl | System and method for recovery detection in a distributed directory service |
US7836314B2 (en) | 2006-08-21 | 2010-11-16 | International Business Machines Corporation | Computer system performance estimator and layout configurator |
US9056165B2 (en) | 2006-09-06 | 2015-06-16 | Medtronic Minimed, Inc. | Intelligent therapy recommendation algorithm and method of using the same |
US8025634B1 (en) | 2006-09-18 | 2011-09-27 | Baxter International Inc. | Method and system for controlled infusion of therapeutic substances |
US7784461B2 (en) | 2006-09-26 | 2010-08-31 | Nellcor Puritan Bennett Llc | Three-dimensional waveform display for a breathing assistance system |
JP2008080036A (en) | 2006-09-29 | 2008-04-10 | Terumo Corp | Pump for medical use |
DE102006047770A1 (en) | 2006-10-10 | 2008-04-24 | Dräger Medical AG & Co. KG | System for controlling and monitoring therapy modules of a medical workstation |
US8126728B2 (en) | 2006-10-24 | 2012-02-28 | Medapps, Inc. | Systems and methods for processing and transmittal of medical data through an intermediary device |
US7369948B1 (en) | 2006-11-07 | 2008-05-06 | International Business Machines Corporation | System and methods for predicting failures in a fluid delivery system |
BRPI0719107A2 (en) | 2006-11-21 | 2013-12-03 | Baxter Int | REMOTE MONITORING AND / OR HANDLING THERAPY MANAGEMENT SYSTEM AND METHOD |
WO2008067245A2 (en) | 2006-11-29 | 2008-06-05 | University Of Maryland, Baltimore | Determining insulin pump rate for tight glycemic control |
US20080149117A1 (en) | 2006-12-21 | 2008-06-26 | Akhil Raghuram | Method of increasing medical hygiene using color coded medical devices |
JP2008158622A (en) | 2006-12-21 | 2008-07-10 | Matsushita Electric Ind Co Ltd | Home health care system |
US20080214919A1 (en) | 2006-12-26 | 2008-09-04 | Lifescan, Inc. | System and method for implementation of glycemic control protocols |
US20080161754A1 (en) | 2006-12-29 | 2008-07-03 | Medsolve Technologies, Inc. | Method and apparatus for infusing liquid to a body |
JP2008186294A (en) | 2007-01-30 | 2008-08-14 | Toshiba Corp | Software updating device, and software updating system |
EP2132678B2 (en) | 2007-02-05 | 2018-04-04 | Medtronic MiniMed, Inc. | Wireless data communication protocols and techniques for a wireless medical device network |
US8121857B2 (en) | 2007-02-15 | 2012-02-21 | Abbott Diabetes Care Inc. | Device and method for automatic data acquisition and/or detection |
US20080228045A1 (en) | 2007-02-23 | 2008-09-18 | Tia Gao | Multiprotocol Wireless Medical Monitors and Systems |
US8231578B2 (en) | 2007-02-28 | 2012-07-31 | Hospira, Inc. | System and method for sequencing channels in a multi-channel infusion pump |
US8195478B2 (en) | 2007-03-07 | 2012-06-05 | Welch Allyn, Inc. | Network performance monitor |
US20080246748A1 (en) | 2007-03-21 | 2008-10-09 | Micheal Cassidy | Laminated and tilled displays and methods of manufacturing the same |
WO2008124478A1 (en) | 2007-04-04 | 2008-10-16 | Pronia Medical Systems, Llc | Systems, methods, and computer program product for improved management of medical procedures for patients on medical protocols |
CA2684807A1 (en) | 2007-04-05 | 2008-10-16 | Velomedix, Inc. | Automated therapy system and method |
KR100887417B1 (en) | 2007-04-11 | 2009-03-06 | 삼성전자주식회사 | Multi-path accessible semiconductor memory device for providing multi processor system with shared use of non volatile memory |
US7864771B2 (en) | 2007-04-20 | 2011-01-04 | Cisco Technology, Inc. | Parsing out of order data packets at a content gateway of a network |
US20080269723A1 (en) | 2007-04-25 | 2008-10-30 | Medtronic Minimed, Inc. | Closed loop/semi-closed loop therapy modification system |
US20080269714A1 (en) | 2007-04-25 | 2008-10-30 | Medtronic Minimed, Inc. | Closed loop/semi-closed loop therapy modification system |
US7687678B2 (en) | 2007-05-10 | 2010-03-30 | Cisco Technology, Inc. | Electronic bandage with flexible electronic controller |
US7972296B2 (en) | 2007-10-10 | 2011-07-05 | Optiscan Biomedical Corporation | Fluid component analysis system and method for glucose monitoring and control |
US8417311B2 (en) | 2008-09-12 | 2013-04-09 | Optiscan Biomedical Corporation | Fluid component analysis system and method for glucose monitoring and control |
US20080300572A1 (en) | 2007-06-01 | 2008-12-04 | Medtronic Minimed, Inc. | Wireless monitor for a personal medical device system |
US8449523B2 (en) | 2007-06-15 | 2013-05-28 | Animas Corporation | Method of operating a medical device and at least a remote controller for such medical device |
US8006241B2 (en) | 2007-06-20 | 2011-08-23 | International Business Machines Corporation | Automatic software installation and cleanup |
US20100274218A1 (en) | 2007-06-22 | 2010-10-28 | Medingo Ltd | Communications for medicinal fluid delivery system |
JP2009003802A (en) | 2007-06-22 | 2009-01-08 | Mitsubishi Electric Corp | Information display device and information display method |
CN101730501A (en) | 2007-06-27 | 2010-06-09 | 霍夫曼-拉罗奇有限公司 | Patient information input interface for a therapy system |
WO2009002627A1 (en) | 2007-06-27 | 2008-12-31 | Roche Diagnostics Gmbh | Therapy delivery system having an open architecture and a method thereof |
US10702174B2 (en) | 2007-06-27 | 2020-07-07 | Integra Lifesciences Corporation | Medical monitor user interface |
KR101423807B1 (en) | 2007-06-27 | 2014-07-30 | 에프. 호프만-라 로슈 아게 | System and method for developing patient specific therapies based on modeling of patient physiology |
ES2733350T3 (en) | 2007-06-27 | 2019-11-28 | Hoffmann La Roche | System for medical diagnosis, treatment and prognosis for requested events and procedure |
US8180029B2 (en) | 2007-06-28 | 2012-05-15 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
DK3460644T3 (en) | 2007-06-29 | 2021-03-22 | Hoffmann La Roche | Electronic blood glucose meter |
US8105282B2 (en) | 2007-07-13 | 2012-01-31 | Iradimed Corporation | System and method for communication with an infusion device |
JP2010534085A (en) | 2007-07-20 | 2010-11-04 | メディンゴ・リミテッド | Hand operated portable injection device |
US8138939B2 (en) | 2007-07-24 | 2012-03-20 | Manning Ventures, Inc. | Drug dispenser/container display |
JP5341891B2 (en) | 2007-08-10 | 2013-11-13 | スミス・メディカル・エイエスディ・インコーポレーテッド | Medical device control method |
US9848058B2 (en) * | 2007-08-31 | 2017-12-19 | Cardiac Pacemakers, Inc. | Medical data transport over wireless life critical network employing dynamic communication link mapping |
US8032226B2 (en) | 2007-09-07 | 2011-10-04 | Asante Solutions, Inc. | User profile backup system for an infusion pump device |
US8048040B2 (en) | 2007-09-13 | 2011-11-01 | Masimo Corporation | Fluid titration system |
US8249686B2 (en) | 2007-09-14 | 2012-08-21 | Corventis, Inc. | Adherent device for sleep disordered breathing |
US8147447B2 (en) | 2007-09-17 | 2012-04-03 | Satish Sundar | High precision infusion pump controller |
US7868754B2 (en) | 2007-09-26 | 2011-01-11 | S.I.P. Holdings, Llc | Medical system and tracking device |
US8660860B2 (en) | 2007-11-09 | 2014-02-25 | Hospira, Inc. | System and method for synchronizing medication configuration information among systems containing medication configuration information |
US20090150439A1 (en) * | 2007-12-07 | 2009-06-11 | Roche Diagnostics Operations, Inc. | Common extensible data exchange format |
US20090150174A1 (en) | 2007-12-07 | 2009-06-11 | Roche Diagnostics Operations, Inc. | Healthcare management system having improved printing of display screen information |
US8266260B2 (en) | 2007-12-11 | 2012-09-11 | Sharp Laboratories Of America, Inc. | Method and system for updating the software of multiple network nodes |
US8403908B2 (en) | 2007-12-17 | 2013-03-26 | Hospira, Inc. | Differential pressure based flow sensor assembly for medication delivery monitoring and method of using the same |
US9026370B2 (en) | 2007-12-18 | 2015-05-05 | Hospira, Inc. | User interface improvements for medical devices |
US9393362B2 (en) | 2007-12-18 | 2016-07-19 | Hospira, Inc. | Infusion pump with configurable screen settings |
JP5496912B2 (en) | 2007-12-27 | 2014-05-21 | シーメンス・ヘルスケア・ダイアグノスティックス・インコーポレーテッド | Method and apparatus for graphical remote multi-process monitoring |
MX2010007324A (en) | 2007-12-31 | 2010-09-30 | Deka Products Lp | Infusion pump assembly. |
JP2009163534A (en) | 2008-01-08 | 2009-07-23 | Carecom:Kk | Dosing management system and dosing management device |
US20090221890A1 (en) | 2008-02-28 | 2009-09-03 | Daniel Saffer | Diabetes Management System |
TW200938926A (en) | 2008-03-11 | 2009-09-16 | Wintek Corp | Electronic device and mounting device having wavelength-tunable color-changing component |
US8069135B2 (en) | 2008-03-20 | 2011-11-29 | General Electric Company | Systems and methods for a predictive notification engine |
CN102172419A (en) | 2008-04-01 | 2011-09-07 | 史密斯医疗Asd公司 | Security features for a medical infusion pump |
CA2723448C (en) | 2008-04-01 | 2017-11-21 | David Debelser | Medical infusion pump having different alarm settings |
US8010846B1 (en) | 2008-04-30 | 2011-08-30 | Honeywell International Inc. | Scalable self-checking processing platform including processors executing both coupled and uncoupled applications within a frame |
US8133197B2 (en) | 2008-05-02 | 2012-03-13 | Smiths Medical Asd, Inc. | Display for pump |
US7996241B2 (en) | 2008-05-12 | 2011-08-09 | Solomon Zak | Process, knowledge, and intelligence management through integrated medical management system for better health outcomes, utilization cost reduction and provider reward programs |
US8310630B2 (en) | 2008-05-16 | 2012-11-13 | Manning Ventures, Inc. | Electronic skin having uniform gray scale reflectivity |
US8103346B2 (en) | 2008-05-22 | 2012-01-24 | Cardiac Pacemakers, Inc. | Regulatory compliant transmission of medical data employing a patient implantable medical device and a generic network access device |
US20090326516A1 (en) | 2008-06-30 | 2009-12-31 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Preparatory dispensation systems and methods |
US20090326340A1 (en) | 2008-06-30 | 2009-12-31 | Hui Wang | Patient Monitor Alarm System And Method |
US8644945B2 (en) | 2008-07-11 | 2014-02-04 | Medtronic, Inc. | Patient interaction with posture-responsive therapy |
US20100036310A1 (en) | 2008-08-05 | 2010-02-11 | Hillman Robert S | Integrated patient management and control system for medication delivery |
US8622988B2 (en) | 2008-08-31 | 2014-01-07 | Abbott Diabetes Care Inc. | Variable rate closed loop control and methods |
US8452953B2 (en) | 2008-09-05 | 2013-05-28 | Roche Diagnostics Operations, Inc. | Insulin pump programming software for selectively modifying configuration data |
US20100095229A1 (en) | 2008-09-18 | 2010-04-15 | Abbott Diabetes Care, Inc. | Graphical user interface for glucose monitoring system |
CN102224751A (en) | 2008-09-22 | 2011-10-19 | 迅速启动无限公司 | System and method for dynamic automatic communication path selection, distributed device synchronization and task delegation |
US7984342B2 (en) | 2008-09-30 | 2011-07-19 | At&T Intellectual Property I, L.P. | System and method for MPEG CRC error based video network fault detection |
US8262616B2 (en) | 2008-10-10 | 2012-09-11 | Deka Products Limited Partnership | Infusion pump assembly |
US8267892B2 (en) | 2008-10-10 | 2012-09-18 | Deka Products Limited Partnership | Multi-language / multi-processor infusion pump assembly |
US8066672B2 (en) | 2008-10-10 | 2011-11-29 | Deka Products Limited Partnership | Infusion pump assembly with a backup power supply |
CA2740990A1 (en) | 2008-10-17 | 2010-04-22 | Thomas Hemmerling | Automatic control system and method for the control of anesthesia |
US8387112B1 (en) | 2008-10-29 | 2013-02-26 | Juniper Networks, Inc. | Automatic software update on network devices |
US8298167B2 (en) | 2008-11-03 | 2012-10-30 | B. Braun Avitum Ag | Modular hemofiltration apparatus with interactive operator instructions and control system |
US8597570B2 (en) | 2008-11-04 | 2013-12-03 | Panasonic Corporation | Measurement device, insulin infusion device, measurement method, method for controlling insulin infusion device, and program |
US20110264043A1 (en) | 2008-11-07 | 2011-10-27 | Curlin Medical Inc. | Method of loading a drug library into an infusion pump |
US8352290B2 (en) | 2008-11-07 | 2013-01-08 | Curlin Medical Inc. | Method of automatically programming an infusion pump |
WO2010053704A1 (en) * | 2008-11-10 | 2010-05-14 | Delphi Technologies, Inc. | Tool for interfacing with an infusion pump |
US20130191770A1 (en) | 2008-11-10 | 2013-07-25 | Curlin Medical Inc. | Method of inputting data into an infusion pump |
US20100121752A1 (en) | 2008-11-12 | 2010-05-13 | Banigan Michael H | Web-Based Bid Analysis, Award, and Contract Management System |
US9501619B2 (en) | 2008-11-13 | 2016-11-22 | Cerner Innovation, Inc. | Integrated medication and infusion monitoring system |
US20100131434A1 (en) | 2008-11-24 | 2010-05-27 | Air Products And Chemicals, Inc. | Automated patient-management system for presenting patient-health data to clinicians, and methods of operation thereor |
US7920061B2 (en) | 2008-11-26 | 2011-04-05 | General Electric Company | Controlling an alarm state based on the presence or absence of a caregiver in a patient's room |
US20100138523A1 (en) | 2008-12-03 | 2010-06-03 | General Electric Company | Automatic configuration method and system for medical devices |
US8082356B2 (en) | 2008-12-09 | 2011-12-20 | Hong Kong Applied Science And Technology Research Institute Co., Ltd. | Synchronizing buffer map offset in peer-to-peer live media streaming systems |
US8082312B2 (en) | 2008-12-12 | 2011-12-20 | Event Medical, Inc. | System and method for communicating over a network with a medical device |
US20100160854A1 (en) | 2008-12-22 | 2010-06-24 | Gauthier Robert T | Integrated patient management and control system for medication delivery |
CN102265279B (en) | 2008-12-23 | 2019-08-23 | 霍夫曼-拉罗奇有限公司 | The Structural Testing Method and its equipment that diagnosis or treatment for chronic are supported |
US8974439B2 (en) | 2009-01-02 | 2015-03-10 | Asante Solutions, Inc. | Infusion pump system and methods |
US8777895B2 (en) | 2009-01-06 | 2014-07-15 | Hospira, Inc. | System and method for authorized medication delivery |
FR2940913B1 (en) | 2009-01-15 | 2013-07-19 | Hopital Foch | SYSTEM FOR CONTROLLING INJECTION MEANS OF ANESTHESIA OR SEDATION AGENTS |
US20100198196A1 (en) | 2009-01-30 | 2010-08-05 | Abbott Diabetes Care, Inc. | Therapy Delivery Device Programming Tool |
US9402544B2 (en) | 2009-02-03 | 2016-08-02 | Abbott Diabetes Care Inc. | Analyte sensor and apparatus for insertion of the sensor |
US8353864B2 (en) | 2009-02-18 | 2013-01-15 | Davis David L | Low cost disposable infusion pump |
JP5661651B2 (en) | 2009-02-25 | 2015-01-28 | ユニバーシティ オブ ヴァージニア パテント ファウンデーション | Prevention of hypoglycemia based on CGM by assessing risk of hypoglycemia and reducing gentle insulin release |
US20100217623A1 (en) | 2009-02-26 | 2010-08-26 | Ido Schoenberg | Decision Support |
EP2404253B1 (en) | 2009-03-04 | 2019-09-18 | Masimo Corporation | Medical monitoring system |
GR1007310B (en) | 2009-03-09 | 2011-06-10 | Αχιλλεας Τσουκαλης | Implantable biosensor with automatic calibration |
US8169914B2 (en) | 2009-03-16 | 2012-05-01 | Sling Media Pvt. Ltd. | Method and node for transmitting data over a communication network using negative acknowledgment |
US20100234708A1 (en) | 2009-03-16 | 2010-09-16 | Harvey Buck | Wirelessly configurable medical device for a broadcast network system |
US20120066501A1 (en) | 2009-03-17 | 2012-03-15 | Chuyu Xiong | Multi-factor and multi-channel id authentication and transaction control |
US8301761B2 (en) | 2009-03-31 | 2012-10-30 | International Business Machines Corporation | Determining server load capacity with virtual users |
EP2413781B1 (en) | 2009-03-31 | 2019-07-24 | Abbott Diabetes Care Inc. | Overnight closed-loop insulin delivery with model predictive control and glucose measurement error model |
US8271106B2 (en) | 2009-04-17 | 2012-09-18 | Hospira, Inc. | System and method for configuring a rule set for medical event management and responses |
WO2010119409A1 (en) | 2009-04-17 | 2010-10-21 | Sensile Pat Ag | Medical device for glucose monitoring or regulation |
WO2010124127A1 (en) | 2009-04-23 | 2010-10-28 | Automedics Medical Systems, Inc. | Integrated patient management and control system for medication delivery |
US20100280486A1 (en) | 2009-04-29 | 2010-11-04 | Hospira, Inc. | System and method for delivering and monitoring medication |
GB0908038D0 (en) | 2009-05-11 | 2009-06-24 | Bluebox Avionics Ltd | A content distribution system and method |
US8172798B2 (en) | 2009-05-12 | 2012-05-08 | Sigma International General Medical Apparatus LLC | System and method for managing infusion therapies |
US8597274B2 (en) | 2009-05-22 | 2013-12-03 | Abbott Diabetes Care Inc. | Usability features for integrated insulin delivery system |
WO2010135654A2 (en) | 2009-05-22 | 2010-11-25 | Abbott Diabetes Care Inc. | Safety features for integrated insulin delivery system |
EP2433233A1 (en) | 2009-05-22 | 2012-03-28 | Abbott Diabetes Care, Inc. | Adaptive insulin delivery system |
WO2010144533A1 (en) | 2009-06-09 | 2010-12-16 | Jacobson Technologies, Llc | Controlled delivery of substances system and method |
US8312272B1 (en) | 2009-06-26 | 2012-11-13 | Symantec Corporation | Secure authentication token management |
USD606533S1 (en) | 2009-07-02 | 2009-12-22 | Research In Motion Limited | Handheld electronic device skin |
US20110009725A1 (en) | 2009-07-09 | 2011-01-13 | Medtronic Minimed, Inc. | Providing contextually relevant advertisements and e-commerce features in a personal medical device system |
US8344847B2 (en) | 2009-07-09 | 2013-01-01 | Medtronic Minimed, Inc. | Coordination of control commands in a medical device system having at least one therapy delivery device and at least one wireless controller device |
ES2888427T3 (en) | 2009-07-23 | 2022-01-04 | Abbott Diabetes Care Inc | Real-time management of data related to the physiological control of glucose levels |
CA2769030C (en) | 2009-07-30 | 2016-05-10 | Tandem Diabetes Care, Inc. | Infusion pump system with disposable cartridge having pressure venting and pressure feedback |
US8072272B2 (en) | 2009-08-19 | 2011-12-06 | Qualcomm, Incorporated | Digital tunable inter-stage matching circuit |
US9077544B2 (en) | 2009-09-15 | 2015-07-07 | Welch Allyn, Inc. | Automatic provisioning of authentication credentials |
US20110071844A1 (en) | 2009-09-22 | 2011-03-24 | Cerner Innovation, Inc. | Pharmacy infusion management |
US8990722B2 (en) | 2009-09-22 | 2015-03-24 | Cerner Innovation, Inc. | Integrating protocols for infusion management |
US9712498B2 (en) | 2009-10-14 | 2017-07-18 | Trice Imaging, Inc. | Systems and devices for encrypting, converting and interacting with medical images |
US8356131B2 (en) | 2009-10-25 | 2013-01-15 | Sony Mobile Communications Ab | System and method for controlling interruption of a process in electronic equipment based on priority of the process, and program |
KR20110064697A (en) | 2009-12-08 | 2011-06-15 | 삼성전자주식회사 | Method and apparatus for updating information |
CN102656584B (en) | 2009-12-16 | 2016-01-27 | 皇家飞利浦电子股份有限公司 | universal medical device driver adapter |
US20120070045A1 (en) | 2009-12-17 | 2012-03-22 | Gregory Vesper | Global medical imaging repository |
US8771251B2 (en) | 2009-12-17 | 2014-07-08 | Hospira, Inc. | Systems and methods for managing and delivering patient therapy through electronic drug delivery systems |
US8171094B2 (en) | 2010-01-19 | 2012-05-01 | Event Medical, Inc. | System and method for communicating over a network with a medical device |
US8400290B2 (en) | 2010-01-19 | 2013-03-19 | Covidien Lp | Nuisance alarm reduction method for therapeutic parameters |
US10911515B2 (en) | 2012-05-24 | 2021-02-02 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US20110313789A1 (en) | 2010-01-22 | 2011-12-22 | Deka Products Limited Partnership | Electronic patient monitoring system |
US10453157B2 (en) | 2010-01-22 | 2019-10-22 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US9636455B2 (en) | 2011-12-21 | 2017-05-02 | Deka Products Limited Partnership | System, method, and apparatus for estimating liquid delivery |
US10242159B2 (en) | 2010-01-22 | 2019-03-26 | Deka Products Limited Partnership | System and apparatus for electronic patient care |
US20110196748A1 (en) | 2010-02-05 | 2011-08-11 | Ilan Caron | Generating Advertising Account Entries Using Variables |
CA2789141C (en) | 2010-02-05 | 2018-06-12 | Deka Products Limited Partnership | Infusion pump apparatus, method and system |
US10238794B2 (en) | 2010-02-05 | 2019-03-26 | Deka Products Limited Partnership | Devices, methods and systems for wireless control of medical devices |
US20110231216A1 (en) | 2010-03-17 | 2011-09-22 | Research In Motion Limited | System and method for controlling event reminders |
US8612055B2 (en) | 2010-04-16 | 2013-12-17 | Medtronic, Inc. | System and method for delivering a therapeutic agent according to default infusion schedule |
US9491085B2 (en) | 2010-05-24 | 2016-11-08 | At&T Intellectual Property I, L.P. | Methods and apparatus to route control packets based on address partitioning |
US8726266B2 (en) | 2010-05-24 | 2014-05-13 | Abbott Diabetes Care Inc. | Method and system for updating a medical device |
CN102262557B (en) | 2010-05-25 | 2015-01-21 | 运软网络科技(上海)有限公司 | Method for constructing virtual machine monitor by bus architecture and performance service framework |
EP2575933B1 (en) | 2010-05-25 | 2017-09-27 | The General Hospital Corporation | Prediction, visualization, and control of drug delivery by infusion pumps |
US9953138B2 (en) | 2010-06-29 | 2018-04-24 | Codman Neuro Sciences Sarl | Drug component admixture library for a drug infusion delivery system |
CN102971711B (en) | 2010-07-02 | 2016-06-01 | 国际商业机器公司 | For processing the Apparatus for () and method therefor of batch working cell |
US8551038B2 (en) | 2010-07-19 | 2013-10-08 | Micrel Medical Devices S.A. | Pump infusion system |
US8676600B2 (en) | 2010-08-12 | 2014-03-18 | Fenwal, Inc | Mobile applications for blood centers |
EP2605813B1 (en) | 2010-08-17 | 2018-08-01 | University of Florida Research Foundation, Inc. | Intelligent drug delivery system to optimizing medical treatment or therapy. |
US8626530B1 (en) | 2010-08-27 | 2014-01-07 | Walgreen Co. | System and method for express refill |
JP5707078B2 (en) | 2010-09-29 | 2015-04-22 | テルモ株式会社 | Medical pump system |
US8876793B2 (en) | 2010-10-01 | 2014-11-04 | Smiths Medical Asd, Inc. | Flushing a fluid line from a medical pump |
US20120096451A1 (en) | 2010-10-15 | 2012-04-19 | Roche Diagnostics Operations, Inc. | Firmware update in a medical device with multiple processors |
US8401194B2 (en) | 2010-10-15 | 2013-03-19 | Roche Diagnostics Operations, Inc. | Diabetes care kit that is preconfigured to establish a secure bidirectional communication link between a blood glucose meter and insulin pump |
US8454554B2 (en) | 2010-10-15 | 2013-06-04 | Roche Diagnostics Operations, Inc. | Use of a handheld medical device as a communications mediator between a personal computer-based configurator and another networked medical device |
US9937355B2 (en) | 2010-11-08 | 2018-04-10 | Zoll Medical Corporation | Remote medical device alarm |
US8662388B2 (en) | 2010-11-09 | 2014-03-04 | Hospira, Inc. | Medical identification system and method of identifying individuals, medical items, and associations therebetween using same |
US20120130198A1 (en) | 2010-11-23 | 2012-05-24 | Beaule Jean-Francois | Systems and method for determining and managing an individual and portable health score |
US20120157920A1 (en) | 2010-12-16 | 2012-06-21 | Numia Medical Technology, Llc | Distributed processor configuration for use in infusion pumps |
CN103380603B (en) | 2011-01-05 | 2016-12-14 | 皇家飞利浦电子股份有限公司 | For distributing the system and method for significant clinical alert |
WO2012097138A1 (en) | 2011-01-12 | 2012-07-19 | The Regents Of The University Of California | System and method for closed-loop patient-adaptive hemodynamic management |
US9578081B2 (en) | 2011-02-02 | 2017-02-21 | Imvu, Inc. | System and method for providing an actively invalidated client-side network resource cache |
US9860302B2 (en) | 2011-03-08 | 2018-01-02 | Gambro Lundia Ab | Method, control module, apparatus and system for transferring data |
US8454581B2 (en) | 2011-03-16 | 2013-06-04 | Asante Solutions, Inc. | Infusion pump systems and methods |
US20120245554A1 (en) | 2011-03-17 | 2012-09-27 | K & Y Corporation | Micro-Infusion System |
WO2012140547A1 (en) | 2011-04-14 | 2012-10-18 | Koninklijke Philips Electronics N.V. | Stepped alarm method for patient monitors |
US8308680B1 (en) | 2011-04-26 | 2012-11-13 | Medtronic Minimed, Inc. | Selective alarms for an infusion device |
US20130006702A1 (en) | 2011-04-27 | 2013-01-03 | Fubin Wu | System for collecting and managing risk management file and safety assurance case data |
US9940440B2 (en) | 2011-04-28 | 2018-04-10 | Medtronic, Inc. | Detecting and responding to software and hardware anomalies in a fluid delivery system |
US9707340B2 (en) | 2011-05-06 | 2017-07-18 | Zyno Medical Llc | Flow control line management apparatus |
US20140213976A1 (en) | 2011-05-30 | 2014-07-31 | Insuline Medical Ltd | Drug Delivery Infusion Set with Manual Pump |
US9636454B2 (en) | 2011-06-08 | 2017-05-02 | Nxstage Medical, Inc. | Electrical safety methods, devices, and systems for medical treatment devices |
AU2012272984B2 (en) | 2011-06-20 | 2016-02-18 | Renaudia Medical, Llc | Distributed medication delivery system and method having autonomous delivery devices |
CN103782299A (en) | 2011-07-01 | 2014-05-07 | 百特恩格伍德公司 | Systems and methods for intelligent patient interface device |
US8893109B2 (en) | 2011-08-02 | 2014-11-18 | Roche Diagnostics Operations, Inc. | Software distribution amongst medical devices taking into account dependencies between devices |
US9645913B2 (en) | 2011-08-03 | 2017-05-09 | Daniel Geist | Method and apparatus for debugging programs |
AU2012299169B2 (en) * | 2011-08-19 | 2017-08-24 | Icu Medical, Inc. | Systems and methods for a graphical interface including a graphical representation of medical data |
CA2845278C (en) | 2011-08-19 | 2020-06-02 | Hospira, Inc. | Detecting air in the fluid delivery line despite stuck fluid droplets |
CN103826679A (en) | 2011-09-27 | 2014-05-28 | 诺沃—诺迪斯克有限公司 | Medical system configured to collect and transfer data |
AU2012315820B2 (en) | 2011-09-30 | 2016-09-29 | Icu Medical, Inc. | Froth detection system and method |
US9943269B2 (en) | 2011-10-13 | 2018-04-17 | Masimo Corporation | System for displaying medical monitoring data |
US9446252B2 (en) | 2011-10-18 | 2016-09-20 | Advanced Neuromodulation Systems, Inc. | System and method for resetting an implantable medical device |
US20130102963A1 (en) | 2011-10-19 | 2013-04-25 | Qualcomm Incorporated | Secure automatic configuration of equipment through replication |
WO2013059615A1 (en) | 2011-10-21 | 2013-04-25 | Hospira, Inc. | Medical device update system |
GB2497079A (en) | 2011-11-25 | 2013-06-05 | Netscientific Ltd | Medical monitoring and control systems for healthcare |
US8945043B2 (en) | 2011-12-01 | 2015-02-03 | Zyno Medical, LLC. | Medical device with contextual awareness |
WO2013090709A1 (en) | 2011-12-16 | 2013-06-20 | Hospira, Inc. | System for monitoring and delivering medication to a patient and method of using the same to minimize the risks associated with automated therapy |
US8719945B2 (en) | 2011-12-22 | 2014-05-06 | Roche Diagnostics Operations, Inc. | Customer error screen capture |
US20130173473A1 (en) | 2011-12-28 | 2013-07-04 | Roche Diagnostics Operations Inc. | Data sychronization systems and methods |
US10484335B2 (en) | 2012-02-09 | 2019-11-19 | Connectify, Inc. | Secure remote computer network |
ES2741725T3 (en) | 2012-03-30 | 2020-02-12 | Icu Medical Inc | Air detection system and method to detect air in a pump of an infusion system |
US9675753B2 (en) | 2012-04-16 | 2017-06-13 | Atlanta Biomedical Corp. | Safe drug delivery system |
US9208290B2 (en) | 2012-04-27 | 2015-12-08 | Gregg S. Homer | External storage of medical device treatment parameters |
US9886550B2 (en) | 2012-06-06 | 2018-02-06 | Zyno Medical, Llc | Medical pump with operator-authorization awareness |
US20140025392A1 (en) | 2012-07-18 | 2014-01-23 | Curlin Medical Inc. | Systems and Methods for Validating Treatment Instructions |
US10463788B2 (en) | 2012-07-31 | 2019-11-05 | Icu Medical, Inc. | Patient care system for critical medications |
US9364609B2 (en) | 2012-08-30 | 2016-06-14 | Medtronic Minimed, Inc. | Insulin on board compensation for a closed-loop insulin infusion system |
JP5767617B2 (en) | 2012-09-27 | 2015-08-19 | 日本電信電話株式会社 | Network failure detection system and network failure detection device |
US9486578B2 (en) | 2012-12-07 | 2016-11-08 | Animas Corporation | Method and system for tuning a closed-loop controller for an artificial pancreas |
EP2742961A1 (en) | 2012-12-13 | 2014-06-18 | Stephen Palletti | Modular drug infusion system with central control and multiple infusion pumps comprising touch screens |
AU2013364039B2 (en) | 2012-12-21 | 2019-09-26 | Deka Products Limited Partnership | Computer-implemented method, system, and apparatus for electronic patient care |
US9056166B2 (en) | 2013-01-21 | 2015-06-16 | Baxter International Inc. | Infusion pump and method to enhance long term medication delivery accuracy |
CA3111631C (en) | 2013-01-28 | 2022-12-13 | Smiths Medical Asd, Inc. | Medication safety devices and methods |
WO2014123854A1 (en) | 2013-02-05 | 2014-08-14 | Fluidnet Corporation | Automated programming of infusion therapy |
CN105074707A (en) | 2013-02-27 | 2015-11-18 | 费森尤斯维尔公司 | Method for transferring operational data to a medical device located within a healthcare environment |
US11049600B2 (en) | 2013-02-27 | 2021-06-29 | Fresenius Vial Sas | System and method for providing drug library data to a medical device located within a healthcare environment |
EP2964079B1 (en) | 2013-03-06 | 2022-02-16 | ICU Medical, Inc. | Medical device communication method |
US10811129B2 (en) | 2013-03-11 | 2020-10-20 | Roche Diabetes Care, Inc. | Customizing names of insulin delivery profiles for improved patient safety |
US9965946B2 (en) | 2013-03-13 | 2018-05-08 | Masimo Corporation | Systems and methods for monitoring a patient health network |
US20140269643A1 (en) | 2013-03-13 | 2014-09-18 | Google Inc. | Systems and methods for geo-fencing |
CN105190631A (en) | 2013-03-15 | 2015-12-23 | 卓尔医学产品公司 | Patient monitor screen aggregation |
US9242043B2 (en) | 2013-03-15 | 2016-01-26 | Tandem Diabetes Care, Inc. | Field update of an ambulatory infusion pump system |
US20140297329A1 (en) | 2013-03-26 | 2014-10-02 | Eric Rock | Medication reconciliation system and method |
WO2014190264A1 (en) | 2013-05-24 | 2014-11-27 | Hospira, Inc. | Multi-sensor infusion system for detecting air or an occlusion in the infusion system |
EP3003442B1 (en) | 2013-05-29 | 2020-12-30 | ICU Medical, Inc. | Infusion system and method of use which prevents over-saturation of an analog-to-digital converter |
CA2913915C (en) | 2013-05-29 | 2022-03-29 | Hospira, Inc. | Infusion system which utilizes one or more sensors and additional information to make an air determination regarding the infusion system |
US11183287B2 (en) * | 2013-06-13 | 2021-11-23 | Carefusion 303, Inc. | Analytics regarding patient care |
US8998100B2 (en) | 2013-06-26 | 2015-04-07 | Carefusion 303, Inc. | Infusion system configured for transfer of data |
KR101526494B1 (en) | 2013-06-28 | 2015-06-05 | 주식회사 인포피아 | Central Dispensing System |
CA2922425C (en) | 2013-08-30 | 2023-05-16 | Hospira, Inc. | System and method of monitoring and managing a remote infusion regimen |
US9662436B2 (en) | 2013-09-20 | 2017-05-30 | Icu Medical, Inc. | Fail-safe drug infusion therapy system |
US20160228633A1 (en) | 2013-09-27 | 2016-08-11 | Smiths Medical Asd, Inc. | Infusion pump with touchless user interface and related methods |
US9474855B2 (en) | 2013-10-04 | 2016-10-25 | Animas Corporation | Method and system for controlling a tuning factor due to sensor replacement for closed-loop controller in an artificial pancreas |
US9438496B2 (en) | 2013-10-31 | 2016-09-06 | Aruba Networks, Inc. | Monitoring link quality between network devices |
US10311972B2 (en) | 2013-11-11 | 2019-06-04 | Icu Medical, Inc. | Medical device system performance index |
EP3071253B1 (en) | 2013-11-19 | 2019-05-22 | ICU Medical, Inc. | Infusion pump automation system and method |
US10874796B2 (en) | 2013-12-03 | 2020-12-29 | Micrel Medical Devices, S.A. | Device and system for locating and operating a medical device |
US9424020B2 (en) | 2014-01-13 | 2016-08-23 | Carefusion 303, Inc. | Remote flashing during infusion |
US20150230760A1 (en) | 2014-02-19 | 2015-08-20 | Q-Core Medical Ltd. | Methods, circuits, devices, systems and computer executable code for operating a medical device using a hybrid communication path |
AU2015220948A1 (en) | 2014-02-21 | 2016-06-30 | Nestec S.A. | Infusion pump with graphic user interface |
US9203814B2 (en) | 2014-02-24 | 2015-12-01 | HCA Holdings, Inc. | Providing notifications to authorized users |
WO2015168427A1 (en) | 2014-04-30 | 2015-11-05 | Hospira, Inc. | Patient care system with conditional alarm forwarding |
US9724470B2 (en) | 2014-06-16 | 2017-08-08 | Icu Medical, Inc. | System for monitoring and delivering medication to a patient and method of using the same to minimize the risks associated with automated therapy |
US20150379237A1 (en) | 2014-06-30 | 2015-12-31 | Gary Mills | Infusion pump error display |
US10532150B2 (en) | 2014-07-21 | 2020-01-14 | Medtronic Minimed, Inc. | Smart connection interface |
US10025909B2 (en) * | 2014-08-04 | 2018-07-17 | Ivenix, Inc. | Medical devices and configuration update management |
US10002235B2 (en) | 2014-08-13 | 2018-06-19 | Ivenix, Inc. | Medical device management and theft inhibitor techniques |
US9717845B2 (en) | 2014-08-19 | 2017-08-01 | Medtronic Minimed, Inc. | Geofencing for medical devices |
US9539383B2 (en) | 2014-09-15 | 2017-01-10 | Hospira, Inc. | System and method that matches delayed infusion auto-programs with manually entered infusion programs and analyzes differences therein |
CN107251478A (en) | 2015-02-12 | 2017-10-13 | 卡米纳利欧技术有限公司 | The computerized system and method for privacy key management |
BR112017022875A2 (en) * | 2015-04-27 | 2018-07-17 | Fresenius Vial Sas | system and method for controlling the administration of a drug to a patient, and software product |
CA2985103A1 (en) | 2015-05-07 | 2016-11-10 | Smiths Medical Asd, Inc. | Systems and methods for coordinating and controlling infusion pumps |
ES2845725T3 (en) | 2015-05-26 | 2021-07-27 | Icu Medical Inc | Infusion pump system and method with multiple drug library editor source capability |
WO2017083054A1 (en) | 2015-11-09 | 2017-05-18 | Smiths Medical Asd, Inc. | Infusion push alerts |
US10306012B2 (en) | 2015-11-25 | 2019-05-28 | Fenwal, Inc. | Secure network access to infusion pump |
US10740436B2 (en) * | 2015-11-25 | 2020-08-11 | Fenwal, Inc. | Data set distribution during medical device operation |
EP3220297B1 (en) * | 2016-03-14 | 2019-06-26 | Fenwal, Inc. | Default data set distribution for medical devices |
NZ746427A (en) | 2016-04-08 | 2020-03-27 | Icu Medical Inc | Control of a drug infusion device |
EP3484541A4 (en) | 2016-07-14 | 2020-03-25 | ICU Medical, Inc. | Multi-communication path selection and security system for a medical device |
US10360997B2 (en) | 2016-10-27 | 2019-07-23 | Snaps Solutions, Llc | Systems and methods for automatically detecting electronic access of files and surfacing contextually relevant content in response thereto |
US10964417B2 (en) | 2016-12-21 | 2021-03-30 | Baxter International Inc. | Medical fluid delivery system including a mobile platform for patient engagement and treatment compliance |
US20180181712A1 (en) | 2016-12-27 | 2018-06-28 | General Electric Company | Systems and Methods for Patient-Provider Engagement |
US20180247712A1 (en) | 2017-02-24 | 2018-08-30 | Masimo Corporation | System for displaying medical monitoring data |
EP3422355B1 (en) | 2017-06-28 | 2021-08-18 | Fenwal, Inc. | System and method of synchronizing medical device databases |
US10833923B2 (en) | 2017-10-26 | 2020-11-10 | Skylo Technologies Inc. | Dynamic multiple access for distributed device communication networks with scheduled and unscheduled transmissions |
JP6988511B2 (en) | 2018-01-24 | 2022-01-05 | 富士通株式会社 | Failure detection method, node device, communication system |
MX2020012007A (en) | 2018-05-11 | 2021-02-09 | Baxter Int | Medical device data back-association, system, apparatuses, and methods. |
EP3794609A1 (en) * | 2018-05-14 | 2021-03-24 | Fresenius Vial SAS | Drug library compiler for patient devices |
EP3824386B1 (en) | 2018-07-17 | 2024-02-21 | ICU Medical, Inc. | Updating infusion pump drug libraries and operational software in a networked environment |
US10861592B2 (en) | 2018-07-17 | 2020-12-08 | Icu Medical, Inc. | Reducing infusion pump network congestion by staggering updates |
US10741280B2 (en) | 2018-07-17 | 2020-08-11 | Icu Medical, Inc. | Tagging pump messages with identifiers that facilitate restructuring |
WO2020018389A1 (en) | 2018-07-17 | 2020-01-23 | Icu Medical, Inc. | Systems and methods for facilitating clinical messaging in a network environment |
US10692595B2 (en) | 2018-07-26 | 2020-06-23 | Icu Medical, Inc. | Drug library dynamic version management |
-
2019
- 2019-07-12 EP EP19841800.6A patent/EP3827337A4/en active Pending
- 2019-07-12 CA CA3107315A patent/CA3107315C/en active Active
- 2019-07-12 AU AU2019309766A patent/AU2019309766A1/en active Pending
- 2019-07-12 WO PCT/US2019/041715 patent/WO2020023231A1/en active Application Filing
- 2019-07-15 US US16/512,243 patent/US11309070B2/en active Active
- 2019-07-17 TW TW108125228A patent/TWI821335B/en active
-
2021
- 2021-01-14 ZA ZA2021/00262A patent/ZA202100262B/en unknown
- 2021-01-26 CO CONC2021/0000838A patent/CO2021000838A2/en unknown
-
2022
- 2022-04-15 US US17/659,454 patent/US20220384059A1/en active Pending
- 2022-09-02 US US17/929,654 patent/US20230009417A1/en active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8486019B2 (en) * | 1999-12-01 | 2013-07-16 | B. Braun Medical, Inc. | Patient medication IV delivery pump with wireless communication to a hospital information management system |
US20120066609A1 (en) * | 2003-11-13 | 2012-03-15 | Hospira, Inc. | System for maintaining drug information and communicating with medication delivery devices |
US20060026205A1 (en) * | 2004-07-30 | 2006-02-02 | Butterfield Robert D | System and method for managing medical databases for patient care devices |
US20080091466A1 (en) * | 2006-10-16 | 2008-04-17 | Hospira, Inc. | System and method for comparing and utilizing activity information and configuration information from multiple device management systems |
US20140180711A1 (en) * | 2010-01-22 | 2014-06-26 | Deka Products Limited Partnership | Computer-Implemented Method, System, and Apparatus for Electronic Patient Care |
US20170258986A1 (en) * | 2016-03-11 | 2017-09-14 | Micrel Medical Devices S.A. | Pump Infusion System |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11881297B2 (en) | 2018-07-17 | 2024-01-23 | Icu Medical, Inc. | Reducing infusion pump network congestion by staggering updates |
US11923076B2 (en) | 2018-07-17 | 2024-03-05 | Icu Medical, Inc. | Converting pump messages in new pump protocol to standardized dataset messages |
Also Published As
Publication number | Publication date |
---|---|
CA3107315A1 (en) | 2020-01-30 |
EP3827337A1 (en) | 2021-06-02 |
US20220384059A1 (en) | 2022-12-01 |
TW202018729A (en) | 2020-05-16 |
WO2020023231A1 (en) | 2020-01-30 |
TWI821335B (en) | 2023-11-11 |
EP3827337A4 (en) | 2022-04-13 |
US20200035355A1 (en) | 2020-01-30 |
CO2021000838A2 (en) | 2021-02-08 |
US11309070B2 (en) | 2022-04-19 |
CA3107315C (en) | 2023-01-03 |
AU2019309766A1 (en) | 2021-03-18 |
ZA202100262B (en) | 2023-07-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20230009417A1 (en) | Drug library dynamic version management | |
US11437132B2 (en) | Drug library dynamic version management | |
US20200319766A1 (en) | Systems and Methods for Displaying and Updating an Electronic Medical Record for a Patient | |
US10470739B2 (en) | Imaging protocol manager pulling system and methods | |
US10986059B2 (en) | System event notification | |
US10242060B2 (en) | System and method for comparing and utilizing activity information and configuration information from multiple medical device management systems | |
US20170136176A1 (en) | Fluid delivery management in a fluid delivery network | |
US20230230687A1 (en) | Systems and methods for centralized buffering and interactive routing of electronic data messages over a computer network | |
US20130204637A1 (en) | Pharmacy workflow management system | |
US20130197927A1 (en) | Healthcare validation system | |
US8380809B2 (en) | Providing a number of web services for imaging optional medical applications | |
US20170017758A1 (en) | Integrated system for obtaining information from electronic medical records and method of use | |
US20150154530A1 (en) | Method and computer program product for task management on late clinical information | |
US8560337B2 (en) | User interface for generating and managing medication tapers | |
US11087862B2 (en) | Clinical case creation and routing automation | |
US20160188844A1 (en) | Cloud based emr manager | |
US20200219596A1 (en) | Systems and methods for managing protected information access and consent to access | |
US8352284B2 (en) | Generating and managing medication tapers | |
US20240104663A1 (en) | Systems and methods for decentralized contract management | |
US20140122094A1 (en) | Intravenous fluid and medication administration system | |
Gupta et al. | Integrating Health Care Technologies: Challenges and Lessons Learned from One Medical Center’s Experience | |
CA2947792A1 (en) | System and method for comparing and utilizing activity information and configuration information from multiple medical device management systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |