US20030158746A1 - Method and system for collecting and circulating data derived from medical appliances, useful in particular in intensive care units - Google Patents
Method and system for collecting and circulating data derived from medical appliances, useful in particular in intensive care units Download PDFInfo
- Publication number
- US20030158746A1 US20030158746A1 US10/257,098 US25709803A US2003158746A1 US 20030158746 A1 US20030158746 A1 US 20030158746A1 US 25709803 A US25709803 A US 25709803A US 2003158746 A1 US2003158746 A1 US 2003158746A1
- Authority
- US
- United States
- Prior art keywords
- data
- computer equipment
- sending
- configuration
- analysis software
- 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.)
- Abandoned
Links
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
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/63—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for local operation
-
- 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/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
-
- 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
- G16H80/00—ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F2213/0002—Serial port, e.g. RS232C
Definitions
- This invention relates to a new process and a new system for collecting data originating from sending apparatus that produces the said data and to distribute the data to users.
- Each user has at least one computer equipment, particularly a personal microcomputer, connected to a display screen and/or a printer and/or a loudspeaker.
- Each computer equipment is used with data analysis software.
- the invention relates to a new process and a new system for collecting data originating from medical apparatus, particularly from medical apparatus used in intensive care units, and to distribute the said data to health practitioners.
- Each health practitioner has at least one computer equipment, particularly a personal microcomputer, connected to a display screen and/or a printer and/or a loudspeaker.
- the said computer equipment is associated with a clinical analysis software.
- Medical apparatus is frequently used in intensive care units, including cardiac monitors, ventilators, infusion pumps, etc.
- Most apparatus available on the market at the present time is provided with a communication port, usually an RS232.Therefore, it can be used to distribute all or some of the collected data to clinical analysis software.
- This software uses data collected by medical apparatus for a large number of applications, for example for studying the reaction of the patient to a treatment, or a prescription change. This information is obviously valuable for the entire medical community, including the doctor and nurses and the hospital administration, pharmaceutical companies, and government officials responsible for the national health service.
- the first solution consists of connecting each medical apparatus to a black box specific to it and that is designed to translate received messages into a common language that can be understood by the clinical software. Examples include Device Link made by the HP company, or Octanet made by the Marquette-Hellige company.
- the second solution consists of developing a program specific to each medical apparatus, for each clinical analysis software.
- a program specific to each medical apparatus for each clinical analysis software.
- the process according to the invention to solve this problem collects data from the sending apparatus, particularly from medical apparatus like those used in intensive care units. This process is also designed to distribute the said data to users, particularly to health practitioners.
- Each user has at least one computer equipment, particularly a personal microcomputer, connected to a display screen and/or a printer and/or a loudspeaker.
- This computer equipment is used with a data analysis software, particularly a clinical analysis software.
- the data are output by the sending equipment in specific formats that are different depending on the type of the sending equipment.
- the process according to the invention comprises the following steps:
- the user can use the data sent by a sending apparatus, even if the data were not formatted to the same standard as his own computer equipment and the associated data analysis software.
- the process according to the invention also comprises the following steps:
- the process according to the invention also comprises a step in which the data translated into a common format are stored.
- the configuration for sending or receiving data translated into a common format is done using configuration—equipment—computer data as a function of the specific features of computer equipment and/or the data analysis software. Also advantageously, the said configuration—equipment—computer data are saved.
- This invention also relates to a system to solve the problem that arises.
- This system is designed to collect data produced by sending apparatus, and particularly medical data originating from medical apparatus, for example apparatus located in intensive care units.
- This system is also designed to distribute the said data to users, particularly to health practitioners.
- the system according to the invention comprises at least one data processing device.
- the data processing device comprises reception means, particularly a reception software module, to receive data originating from the sending apparatus.
- the data processing device also comprises data processing means, particularly a data processing software module to translate received data into a common format.
- the data processing device also comprises data sending means, particularly a data sending software module, to distribute the data to users in the common format.
- the system according to the invention is such that the user has his own computer equipment.
- This computer equipment may in particular consist of a personal microcomputer connected to a display screen and/or a printer and/or a loudspeaker.
- Each computer equipment comprises:
- the data analysis software in the computer equipment comprises a conversion module
- the data processing device also comprises conversion means, and particularly a conversion software module.
- These conversion means are used to convert data in the common format into formatted data compatible with the computer equipment and/or its data analysis software.
- the said data processing device is integrated in the said computer equipment. It is applicable to all clinical analysis software that could be used in combination with it.
- the reception means of the said computer equipment are interconnected to the sending means of the said data processing device through a computer communication network, particularly an Internet type network.
- the data processing device comprises a configuration—reception interface, and particularly a configuration—reception module, used to input configuration data for the reception means as a function of the format of the data originating from sending apparatus.
- the data processing device also comprises a register containing the configuration data for the said reception means.
- the data processing device comprises storage means for storing data translated into a common format.
- the data analysis software installed on the computer equipment comprises a configuration—reception module that can be used to input reception means configuration data as a function of the specific features of the computer equipment and/or other data analysis software modules.
- the data analysis software also comprises a save module containing the said configuration—reception data for the reception means.
- the data processing device comprises a configuration—sending interface, and particularly a configuration—sending module.
- This interface is used to input configuration data for the sending means as a function of specific features of the computer equipment and the data analysis software with which they will be used.
- the data processing device also comprises a register containing the said sending means configuration data.
- users can use data sent by a remote sending device, even if they are formatted according to standards other than the standards for their computer equipment and the data analysis software that they use.
- FIG. 1 that diagrammatically shows a variant embodiment of the system according to the invention
- FIG. 2 that diagrammatically shows the six modules forming a variant embodiment of the software for implementation of the invention, in the form of block diagrams.
- the system is designed to collect medical data originating from medical apparatus 1 .
- the medical apparatus may be located in intensive care units 2 .
- the system is also designed to distribute the said data to health practitioners 3 .
- the system comprises at least one data processing device 4 .
- This data processing device 4 comprises reception means 4 a, and particularly a reception software module 4 a′ to receive data originating from sending devices 1 .
- This data processing device 4 comprises data processing means 4 b, particularly a data processing software module 4 b′ , to translate data received into a common format.
- the data processing device 4 also comprises data sending means 4 c, and particularly a data sending software module 4 c′ , to distribute data in the common format to the users 3 .
- the software modules 4 a′ , 4 b′ and 4 c′ are shown symbolically in FIG. 1 by machine instruction lines.
- the user 3 has computer equipment 5 , and particularly a personal microcomputer, connected to a display screen 5 a.
- He may also include a printer 5 b and/or a loudspeaker 5 c.
- Each computer equipment 5 comprises reception means 5 d that receive data sent by the said data processing device 4 , a data analysis software 5 e, shown symbolically in FIG. 1 by machine instruction lines.
- the said data processing device 4 may be included in the computer equipment 5 .
- the reception means 5 d of the said computer equipment 5 are interconnected to the sending means 4 c of the said data processing device 4 through a communication network 6 , and particularly an Internet type network.
- the data analysis software 5 e of the computer equipment 5 comprises a conversion module 5 f to convert the data in a common format into formatted data compatible with the computer equipment 5 and/or other modules 5 g of the said data analysis software.
- the data processing device 4 may also comprise conversion means 4 d, particularly a conversion software module 4 d′ to convert the data in the common format into formatted data compatible with the computer equipment 5 and/or its data analysis software 5 e.
- the data analysis device 4 comprises a configuration—reception interface 4 e, particularly a configuration—reception software module 4 e′, to input configuration data for reception means 4 a as a function of the format of data output from sending apparatus 1 .
- the data processing device 4 comprises a register 4 f containing the said configuration data for the reception means 4 a.
- the data processing device 4 comprises storage means 4 g for storing data translated into a common format.
- the data analysis software 5 e of the said computer equipment 5 comprises a configuration—reception module 5 h for inputting configuration data of the reception means 5 d as a function of the specific features of the computer equipment 5 and/or other modules 5 g of the data analysis software 5 e.
- the analysis software 5 e also comprises a save module 5 i containing the said configuration—reception data of the reception means 5 d.
- the data processing device 4 comprises a configuration—sending interface 4 e, particularly a configuration—sending module 4 e′ , used to input configuration data for sending means 4 c as a function of the specific features of computer equipment 5 and the data analysis software 5 e with which they will be used.
- the register 4 f contains the said configuration data for the sending means 4 c.
- FIG. 2 diagrammatically shows the six modules forming a variant embodiment of the software used to implement the invention, in the form of block diagrams.
- the software referred to in the following as the “DataCaptor” software, is composed of the following seven modules:
- the DataCaptor Service (DS) 21 is the software core. It starts and controls the other modules. It controls correct operation of the entire system. It detects malfunctions and restores nominal operation by correcting any problems. It checks that each DataCaptor Communication Interface (DCI) module 22 ( 4 a, FIG. 1), is activated and is operating correctly. It maintains the integrity and security of the system at all times. It controls the DataCaptor Device Interface (DDI) modules 23 ( 4 a, FIG. 1), through On/Off interfaces and commands (C). It provides interfaces that will be used by the other modules.
- DCI DataCaptor Communication Interface
- the DataCaptor Data Store (DDS) 24 is a Data storage module D, for short and long term. This module receives data acquired by each DDI 23 , stores the data on the disk 25 ( 4 g, FIG. 1) and sends them to DataCaptor ActiveX Controls (DAC) 26 .
- the DDS 24 executes functions known in themselves to manage storage of data. It is optimised so that it can process requests in real time or requests in batch data, without any loss of performance. It provides interfaces enabling use of data D and commands C by other modules. All collected data are stored locally in binary files.
- Each DataCaptor ActiveX Control (DAC) 26 is accessible from all points on the computer communication network 6 , regardless of whether a small NetBEUI network or an Internet network is being used. Each DataCaptor ActiveX Control (DAC) 26 is capable of distributing data D.
- the DataCaptor ActiveX Control (DAC) 26 finds the associated DataCaptor Data Store (DDS) 24 for which it knows the address, and it then registers itself on this DDS as a data receiver.
- the DataCaptor ActiveX Control (DAC) 26 can then receive data D from the associated DataCaptor Data Store (DDS) 24 .
- This DDS may be local or it may be remote.
- the data D are sent through the DataCaptor ActiveX Control (DAC) 26 to the computer equipment 5 (FIG. 1) belonging to the health practitioner, through the DataCaptor Data Portal (DDP) module 40 .
- the clinical software used by a health practitioner can thus access all data related to a patient, collected by any medical apparatus in a health care unit, a hospital, etc.
- the DataCaptor ActiveX Control (DAC) 26 may address C commands to the DataCaptor Data Store (DDS) 24 and/or to the DataCaptor Service (DS) 21 or to any other module.
- DDS DataCaptor Data Store
- DS DataCaptor Service
- the programmer of the clinical analysis application software 5 e can integrate a DataCaptor ActiveX Control (DAC) module 26 , in some variant embodiments.
- the Datacaptor ActiveX Control (DAC) module 26 is the interface that the programmer uses to use the system.
- the C commands addressed by the DataCaptor ActiveX Control (DAC) 26 to the DataCaptor Data Store (DDS) 24 and/or to the DataCaptor Service (DS) 21 and to any other module may be pre-programmed in the application software and activated by the health practitioner.
- DAC DataCaptor ActiveX Control
- the DataCaptor Device Interfaces (DDI) 23 are used to access medical apparatus through DataCaptor Communication Interfaces (DCI) 22 . They are configured as a function of the specific features of the connected medical apparatus, making use of parameters contained in the register 27 ( 4 f, FIG. 1) of the operating system and inserted in the register by the DataCaptor Control Panel (DCP) 28 ( 4 e, FIG. 1).
- the DataCaptor Service (DS) 21 starts these DataCaptor Device Interfaces.
- Each DataCaptor Device Interface (DDI) 23 then connects to the appropriate DataCaptor Communication Interface (DCI) module 22 .
- the DataCaptor Device Interfaces (DDI) 23 then maintain the connection with the connected apparatus and manage detected communication errors.
- Each DataCaptor Device Interface (DDI) 23 controls low level communication through the DataCaptor Communication Interface (DCI) module 22 and the high level interface, using Data Communication protocols for data sent by the medical apparatus concerned.
- the DataCaptor Device Interfaces (DDI) 23 read and translate the protocols of medical apparatus to which they are connected.
- DataCaptor Device Interfaces (DDI) 23 can read and translate sporadic parameters, data curves in real time and any other digital data output from medical apparatus.
- Each DataCaptor Device Interface (DDI) 23 transmits collected data to the DataCaptor Data Store (DDS) 24 .
- DDS DataCaptor Data Store
- DataCaptor Communication Interfaces (DCI) 22 are used to start and control physical communication ports 29 with the computer communication networks to which each medical apparatus 1 is connected. There is a DataCaptor Communication Interface (DCI) 22 for each type of communication port (serial, network, etc.). Each DataCaptor Communication Interface (DCI) 22 is started by the first DataCaptor Device Interface (DDI) 23 that requires this type of communication port. They also monitor any communication errors.
- DCI DataCaptor Communication Interfaces
- the DataCaptor Control Panel (DCP) module 28 ( 4 e, FIG. 1) is the interface used to configure the system. The user specifies (i) physical connections between the medical apparatus and physical communication ports, (ii) communication parameters and (iii) the type of medical apparatus concerned, through the DataCaptor Control Panel (DCP) 28 .
- the DataCaptor Control Panel (DCP) module 28 is used to update the register 27 ( 4 f, FIG. 1).
- the DataCaptor Control Panel (DCP) module 28 supplies information about the configuration of data sources for the system to the DataCaptor Device Interfaces (DDI) 23 and to the DataCaptor Communication Interfaces (DCI) 22 concerned through the register 27 .
- DCI DataCaptor Communication Interfaces
- the DataCaptor Data Portal (DDP) module 40 is the data conversion module D, converting data D from the DataCaptor ActiveX Controls (DAC) 26 , into the communication format of the clinical analysis software 5 e (FIG. 1).
- the DataCaptor Data Portal (DDP) 40 sends data thus converted to the clinical analysis application software 5 e installed on the computer equipment 5 (FIG. 1).
- the DataCaptor Data Portal (DDP) module 40 receives commands C from the clinical analysis application software 5 e (FIG. 1) and sends these data to the DataCaptor ActiveX Control (DAC) 26 .
- a DataCaptor Data Portal (DDP) 40 is designed to receive data D from one or several DataCaptor ActiveX Controls (DAC) 26 .
- the programmer of the clinical analysis application software 5 e (FIG. 1) includes a DataCaptor ActiveX Control (DAC) module 26 into the software, there is no need to provide a DataCaptor Data Portal (DDP) 40 . Also in this case, the programmer of the clinical analysis application software 5 e adapts the proprietary language of the clinical analysis software to the common format.
- DAC DataCaptor ActiveX Control
- DDP DataCaptor Data Portal
- the solution according to the invention provides all data, regardless of the format of the source, in a single and easily useable output format.
- the Microsoft Distributed Component Object Model forms the basic platform that was used for the development of a variant embodiment of the DataCaptor software.
- This variant embodiment of the DataCaptor software is written in Microsoft C++ and Visual Basic. It implements an architecture based on ([D]COM) and operates under WNT, W98 and W95.
- the choice of ([D]COM) solves all inter-module, inter-PC and Internet communication problems and guarantees compatibility with future versions of the Microsoft operating system, while enabling binary compatibility with other operating systems.
- ([D]COM) is a binary standard.
Abstract
This invention relates to a process and system for collecting medical data originating from medical apparatus (1), for example located in intensive care units (2) and to distribute the said data to health practitioners (3);
The system comprises at least one data processing device (4) comprising:
reception means (4 a) to receive data (7) originating from sending apparatus (1),
data processing means (4 b) to translate the received data into a common format,
data sending means (4 c) to distribute the data in a common format to users (3);
The users (3) have computer equipment (5) comprising:
reception means (5 d) for reception of data sent by the said data processing device (4);
a data analysis software (5 e).
Description
- This invention relates to a new process and a new system for collecting data originating from sending apparatus that produces the said data and to distribute the data to users. Each user has at least one computer equipment, particularly a personal microcomputer, connected to a display screen and/or a printer and/or a loudspeaker. Each computer equipment is used with data analysis software.
- More particularly, the invention relates to a new process and a new system for collecting data originating from medical apparatus, particularly from medical apparatus used in intensive care units, and to distribute the said data to health practitioners. Each health practitioner has at least one computer equipment, particularly a personal microcomputer, connected to a display screen and/or a printer and/or a loudspeaker. The said computer equipment is associated with a clinical analysis software.
- Medical apparatus is frequently used in intensive care units, including cardiac monitors, ventilators, infusion pumps, etc. Most apparatus available on the market at the present time is provided with a communication port, usually an RS232.Therefore, it can be used to distribute all or some of the collected data to clinical analysis software. This software uses data collected by medical apparatus for a large number of applications, for example for studying the reaction of the patient to a treatment, or a prescription change. This information is obviously valuable for the entire medical community, including the doctor and nurses and the hospital administration, pharmaceutical companies, and government officials responsible for the national health service.
- However, there is a fundamental problem that needs to be solved in order to retrieve data collected by medical apparatus. This is that there is no common protocol for communications between the apparatus and computers. By using a simple analogy, each medical apparatus could be considered to speak its own specific language. Therefore, each software must speak and understand a large number of languages.
- There are essentially two different ways of solving this problem.
- The first solution consists of connecting each medical apparatus to a black box specific to it and that is designed to translate received messages into a common language that can be understood by the clinical software. Examples include Device Link made by the HP company, or Octanet made by the Marquette-Hellige company.
- The second solution consists of developing a program specific to each medical apparatus, for each clinical analysis software. For example, there is the Clink n link solution produced by the Picis company, and the CareVue solution produced by the HP company.
- In both cases, the diversity of the apparatus and the developed software obliges black boxes designers and/or clinical software developers to continuously modify their products without being able to satisfy needs of users who are already equipped. The solutions described in documents EASTMAN KODAK (WO 99 41691 A), Aug. 19, 1999, WOOD ET AL (U.S. Pat. No. 5,715,823), Feb. 10, 1998, KLEINHOLZ ET AL (XP002083080), June 1996, HASKIN MARVIN E (U.S. Pat. No. 4,764,870 A), Aug. 16, 1998 and PINSKY ET AL (U.S. Pat. No. 5,513,101 A), Apr. 30, 1996 all have the same disadvantages.
- Admittedly, there have been many attempts to standardise output messages from different apparatus. So far, these attempts have not been successful. Thus for example, several years were necessary to produce a first draft standardisation for information output from infusion pumps, which is one of the simplest types of apparatus on the market.
- The process according to the invention to solve this problem collects data from the sending apparatus, particularly from medical apparatus like those used in intensive care units. This process is also designed to distribute the said data to users, particularly to health practitioners. Each user has at least one computer equipment, particularly a personal microcomputer, connected to a display screen and/or a printer and/or a loudspeaker. This computer equipment is used with a data analysis software, particularly a clinical analysis software. The data are output by the sending equipment in specific formats that are different depending on the type of the sending equipment.
- The process according to the invention comprises the following steps:
- a step in which data from sending equipment are collected,
- a step in which the data are translated into a common format,
- step in which the data in the common format are distributed to the computer equipment belonging to the users concerned,
- a step in which the data in the common format are converted (before or after distribution) into formatted data compatible with each computer equipment and/or its data analysis software.
- Thus, the user can use the data sent by a sending apparatus, even if the data were not formatted to the same standard as his own computer equipment and the associated data analysis software.
- Advantageously, the process according to the invention also comprises the following steps:
- a step in which data collection is configured using configuration—collection data, as a function of the format of data originating from sending apparatus,
- a step to record the said configuration—collection data.
- Advantageously, the process according to the invention also comprises a step in which the data translated into a common format are stored.
- Advantageously, the configuration for sending or receiving data translated into a common format is done using configuration—equipment—computer data as a function of the specific features of computer equipment and/or the data analysis software. Also advantageously, the said configuration—equipment—computer data are saved.
- This invention also relates to a system to solve the problem that arises. This system is designed to collect data produced by sending apparatus, and particularly medical data originating from medical apparatus, for example apparatus located in intensive care units. This system is also designed to distribute the said data to users, particularly to health practitioners.
- The system according to the invention comprises at least one data processing device. The data processing device comprises reception means, particularly a reception software module, to receive data originating from the sending apparatus. The data processing device also comprises data processing means, particularly a data processing software module to translate received data into a common format. The data processing device also comprises data sending means, particularly a data sending software module, to distribute the data to users in the common format.
- The system according to the invention is such that the user has his own computer equipment. This computer equipment may in particular consist of a personal microcomputer connected to a display screen and/or a printer and/or a loudspeaker. Each computer equipment comprises:
- means of receiving data sent by the said data processing device,
- a data analysis software.
- Data in the common format are converted into formatted data compatible with the computer equipment and/or other modules of the said data analysis software as follows:
- according to a first variant embodiment, the data analysis software in the computer equipment comprises a conversion module,
- according to another embodiment, the data processing device also comprises conversion means, and particularly a conversion software module.
- These conversion means are used to convert data in the common format into formatted data compatible with the computer equipment and/or its data analysis software.
- Preferably, according to a first embodiment, the said data processing device is integrated in the said computer equipment. It is applicable to all clinical analysis software that could be used in combination with it.
- Preferably, according to another variant embodiment, the reception means of the said computer equipment are interconnected to the sending means of the said data processing device through a computer communication network, particularly an Internet type network.
- Advantageously, the data processing device comprises a configuration—reception interface, and particularly a configuration—reception module, used to input configuration data for the reception means as a function of the format of the data originating from sending apparatus. The data processing device also comprises a register containing the configuration data for the said reception means.
- Also advantageously, the data processing device comprises storage means for storing data translated into a common format.
- Advantageously, the data analysis software installed on the computer equipment comprises a configuration—reception module that can be used to input reception means configuration data as a function of the specific features of the computer equipment and/or other data analysis software modules. The data analysis software also comprises a save module containing the said configuration—reception data for the reception means. Thus, users can access data sent by a remote sending apparatus, even if they are formatted to standards different from the standards for their computer equipment and the data analysis software that they use.
- Advantageously, in another variant embodiment, the data processing device comprises a configuration—sending interface, and particularly a configuration—sending module. This interface is used to input configuration data for the sending means as a function of specific features of the computer equipment and the data analysis software with which they will be used. The data processing device also comprises a register containing the said sending means configuration data. Thus also, in this variant embodiment, users can use data sent by a remote sending device, even if they are formatted according to standards other than the standards for their computer equipment and the data analysis software that they use.
- Other characteristics and advantages of the invention will become clearer after reading the description of variant embodiments of the invention that are given for illustrative purposes and are in no way limitative, and:
- FIG. 1 that diagrammatically shows a variant embodiment of the system according to the invention,
- FIG. 2 that diagrammatically shows the six modules forming a variant embodiment of the software for implementation of the invention, in the form of block diagrams.
- We will now diagrammatically describe the outline of a variant embodiment of the system according to the invention in the case in which the sending devices are medical apparatus.
- The system is designed to collect medical data originating from
medical apparatus 1. For example, the medical apparatus may be located inintensive care units 2. The system is also designed to distribute the said data tohealth practitioners 3. - The system comprises at least one
data processing device 4. Thisdata processing device 4 comprises reception means 4 a, and particularly areception software module 4 a′ to receive data originating from sendingdevices 1. Thisdata processing device 4 comprises data processing means 4 b, particularly a dataprocessing software module 4 b′, to translate data received into a common format. Thedata processing device 4 also comprises data sending means 4 c, and particularly a data sending software module 4 c′, to distribute data in the common format to theusers 3. Thesoftware modules 4 a′, 4 b′ and 4 c′ are shown symbolically in FIG. 1 by machine instruction lines. Theuser 3 hascomputer equipment 5, and particularly a personal microcomputer, connected to adisplay screen 5 a. He may also include aprinter 5 b and/or aloudspeaker 5 c. Eachcomputer equipment 5 comprises reception means 5 d that receive data sent by the saiddata processing device 4, adata analysis software 5 e, shown symbolically in FIG. 1 by machine instruction lines. - For some embodiments not shown in FIG. 1, the said
data processing device 4 may be included in thecomputer equipment 5. - In the case of the variant embodiment shown in FIG. 1, the reception means5 d of the said
computer equipment 5 are interconnected to the sending means 4 c of the saiddata processing device 4 through a communication network 6, and particularly an Internet type network. - The
data analysis software 5 e of thecomputer equipment 5 comprises aconversion module 5 f to convert the data in a common format into formatted data compatible with thecomputer equipment 5 and/orother modules 5 g of the said data analysis software. - In other variant embodiments, the
data processing device 4 may also comprise conversion means 4 d, particularly a conversion software module 4 d′ to convert the data in the common format into formatted data compatible with thecomputer equipment 5 and/or itsdata analysis software 5 e. - The
data analysis device 4 comprises a configuration—reception interface 4 e, particularly a configuration—reception software module 4 e′, to input configuration data for reception means 4 a as a function of the format of data output from sendingapparatus 1. Thedata processing device 4 comprises aregister 4 f containing the said configuration data for the reception means 4 a. - The
data processing device 4 comprises storage means 4 g for storing data translated into a common format. - The
data analysis software 5 e of the saidcomputer equipment 5 comprises a configuration—reception module 5 h for inputting configuration data of the reception means 5 d as a function of the specific features of thecomputer equipment 5 and/orother modules 5 g of thedata analysis software 5 e. - The
analysis software 5 e also comprises asave module 5 i containing the said configuration—reception data of the reception means 5 d. - With this combination of means, users can use data sent by a remote sending device, even if they are formatted in standards other than the standards used on their own computer equipment and the data analysis software that they use. Furthermore, updates are made once only for all apparatus and all software used.
- In another variant embodiment, the
data processing device 4 comprises a configuration—sendinginterface 4 e, particularly a configuration—sendingmodule 4 e′, used to input configuration data for sending means 4 c as a function of the specific features ofcomputer equipment 5 and thedata analysis software 5 e with which they will be used. In this case, theregister 4 f contains the said configuration data for the sending means 4 c. - Thus, in the case of this variant embodiment, as a result of this combination of means, users can also use data sent by a remote sending apparatus, even if they are formatted according to standards other than the standards for their own computer equipment and the data analysis software that they use.
- We will now describe FIG. 2 that diagrammatically shows the six modules forming a variant embodiment of the software used to implement the invention, in the form of block diagrams. The software, referred to in the following as the “DataCaptor” software, is composed of the following seven modules:
- The DataCaptor Service (DS)21 is the software core. It starts and controls the other modules. It controls correct operation of the entire system. It detects malfunctions and restores nominal operation by correcting any problems. It checks that each DataCaptor Communication Interface (DCI) module 22 (4 a, FIG. 1), is activated and is operating correctly. It maintains the integrity and security of the system at all times. It controls the DataCaptor Device Interface (DDI) modules 23 (4 a, FIG. 1), through On/Off interfaces and commands (C). It provides interfaces that will be used by the other modules.
- The DataCaptor Data Store (DDS)24 is a Data storage module D, for short and long term. This module receives data acquired by each
DDI 23, stores the data on the disk 25 (4 g, FIG. 1) and sends them to DataCaptor ActiveX Controls (DAC) 26. TheDDS 24 executes functions known in themselves to manage storage of data. It is optimised so that it can process requests in real time or requests in batch data, without any loss of performance. It provides interfaces enabling use of data D and commands C by other modules. All collected data are stored locally in binary files. - Each DataCaptor ActiveX Control (DAC)26 is accessible from all points on the computer communication network 6, regardless of whether a small NetBEUI network or an Internet network is being used. Each DataCaptor ActiveX Control (DAC) 26 is capable of distributing data D.
- The DataCaptor ActiveX Control (DAC)26 finds the associated DataCaptor Data Store (DDS) 24 for which it knows the address, and it then registers itself on this DDS as a data receiver. The DataCaptor ActiveX Control (DAC) 26 can then receive data D from the associated DataCaptor Data Store (DDS) 24. This DDS may be local or it may be remote. The data D are sent through the DataCaptor ActiveX Control (DAC) 26 to the computer equipment 5 (FIG. 1) belonging to the health practitioner, through the DataCaptor Data Portal (DDP)
module 40. The clinical software used by a health practitioner can thus access all data related to a patient, collected by any medical apparatus in a health care unit, a hospital, etc. - The DataCaptor ActiveX Control (DAC)26 may address C commands to the DataCaptor Data Store (DDS) 24 and/or to the DataCaptor Service (DS) 21 or to any other module.
- The programmer of the clinical
analysis application software 5 e can integrate a DataCaptor ActiveX Control (DAC)module 26, in some variant embodiments. The Datacaptor ActiveX Control (DAC)module 26 is the interface that the programmer uses to use the system. In this variant, the C commands addressed by the DataCaptor ActiveX Control (DAC) 26 to the DataCaptor Data Store (DDS) 24 and/or to the DataCaptor Service (DS) 21 and to any other module, may be pre-programmed in the application software and activated by the health practitioner. By encapsulating one or several DataCaptor ActiveX Control (DAC)modules 26 into the clinical software used by a health practitioner, the health practitioner is able to access all data related to a patient, collected by any medical apparatus in a health care unit, a hospital, etc. - The DataCaptor Device Interfaces (DDI)23 are used to access medical apparatus through DataCaptor Communication Interfaces (DCI) 22. They are configured as a function of the specific features of the connected medical apparatus, making use of parameters contained in the register 27 (4 f, FIG. 1) of the operating system and inserted in the register by the DataCaptor Control Panel (DCP) 28 (4 e, FIG. 1). The DataCaptor Service (DS) 21 starts these DataCaptor Device Interfaces. Each DataCaptor Device Interface (DDI) 23 then connects to the appropriate DataCaptor Communication Interface (DCI)
module 22. The DataCaptor Device Interfaces (DDI) 23 then maintain the connection with the connected apparatus and manage detected communication errors. Each DataCaptor Device Interface (DDI) 23 controls low level communication through the DataCaptor Communication Interface (DCI)module 22 and the high level interface, using Data Communication protocols for data sent by the medical apparatus concerned. The DataCaptor Device Interfaces (DDI) 23 read and translate the protocols of medical apparatus to which they are connected. - DataCaptor Device Interfaces (DDI)23 can read and translate sporadic parameters, data curves in real time and any other digital data output from medical apparatus.
- Each DataCaptor Device Interface (DDI)23 transmits collected data to the DataCaptor Data Store (DDS) 24.
- DataCaptor Communication Interfaces (DCI)22 are used to start and control
physical communication ports 29 with the computer communication networks to which eachmedical apparatus 1 is connected. There is a DataCaptor Communication Interface (DCI) 22 for each type of communication port (serial, network, etc.). Each DataCaptor Communication Interface (DCI) 22 is started by the first DataCaptor Device Interface (DDI) 23 that requires this type of communication port. They also monitor any communication errors. - The DataCaptor Control Panel (DCP) module28 (4 e, FIG. 1) is the interface used to configure the system. The user specifies (i) physical connections between the medical apparatus and physical communication ports, (ii) communication parameters and (iii) the type of medical apparatus concerned, through the DataCaptor Control Panel (DCP) 28.
- The DataCaptor Control Panel (DCP)
module 28 is used to update the register 27 (4 f, FIG. 1). The DataCaptor Control Panel (DCP)module 28 supplies information about the configuration of data sources for the system to the DataCaptor Device Interfaces (DDI) 23 and to the DataCaptor Communication Interfaces (DCI) 22 concerned through theregister 27. - The DataCaptor Data Portal (DDP)
module 40 is the data conversion module D, converting data D from the DataCaptor ActiveX Controls (DAC) 26, into the communication format of theclinical analysis software 5 e (FIG. 1). The DataCaptor Data Portal (DDP) 40 sends data thus converted to the clinicalanalysis application software 5 e installed on the computer equipment 5 (FIG. 1). The DataCaptor Data Portal (DDP)module 40 receives commands C from the clinicalanalysis application software 5 e (FIG. 1) and sends these data to the DataCaptor ActiveX Control (DAC) 26. - A DataCaptor Data Portal (DDP)40 is designed to receive data D from one or several DataCaptor ActiveX Controls (DAC) 26.
- When the programmer of the clinical
analysis application software 5 e (FIG. 1) includes a DataCaptor ActiveX Control (DAC)module 26 into the software, there is no need to provide a DataCaptor Data Portal (DDP) 40. Also in this case, the programmer of the clinicalanalysis application software 5 e adapts the proprietary language of the clinical analysis software to the common format. - Synthesis
- The analysis of the problem and the solution according to the invention shows that the general problem can be split into several problems, each of which is easier to solve:
- Acquire data. Management of communication with the apparatus through its communication protocol.
- Translate input data into an internal format.
- Archive data.
- Distribute data to users.
- Make it possible for application software (particularly clinical analysis software) to access the data.
- Translate from the internal format to the general format.
- Management of the entire system. Perform command functions, history and control.
- The solution according to the invention provides all data, regardless of the format of the source, in a single and easily useable output format.
- The Microsoft Distributed Component Object Model ([D]COM) forms the basic platform that was used for the development of a variant embodiment of the DataCaptor software.
- This variant embodiment of the DataCaptor software is written in Microsoft C++ and Visual Basic. It implements an architecture based on ([D]COM) and operates under WNT, W98 and W95. The choice of ([D]COM) solves all inter-module, inter-PC and Internet communication problems and guarantees compatibility with future versions of the Microsoft operating system, while enabling binary compatibility with other operating systems. ([D]COM) is a binary standard.
- It is possible to write other variant embodiments of the DataCaptor software in CORBA, using Java. Therefore 90% of platforms can use DataCaptor.
Claims (11)
1. Process for collecting data originating from sending apparatus (1), and particularly from medical apparatus like that used in intensive care units (2), and for distributing the said data to users, and particularly to health practitioners (3); each user has at least one computer equipment (5) and particularly a personal microcomputer, connected to a display screen (5 a) and/or to a printer (5 b) and/or to a loudspeaker (5 c); the said computer equipment being associated with a data analysis software (5 e), and particularly a clinical analysis software;
the said data being supplied by the said sending equipment (1), in different specific formats as a function of the different sending equipment;
the said process comprising the following steps:
the data are collected (7, 4 a),
the data are translated (4 b) into a common format,
the data are distributed (4 c, 6, 5 d) in the common format to the user's computer equipment (5),
the data in the common format are converted (4 d, 5 f), before or after being distributed, into formatted data compatible with the computer equipment (5) and/or its data analysis software (5 e),
(such that the user can access data sent by a sending apparatus, even if it these data are formatted according to standards different from the standards in their own computer equipment and the associated data analysis software).
2. Process according to claim 1 , such that it also comprises the following steps:
collection of the data (4 e) is configured using configuration—collection data, as a function of the format of the data originating (7) from sending apparatus,
the said configuration—collection data are saved (4 f).
3. Process according to any one of claims 1 or 2, such that it also comprises the following step:
the data translated to a common format are stored (4 g).
4. Process according to any one of claims 1 to 3 , such that it also comprises the following steps:
sending or reception of the data translated into a common format is configured (4 e, 5 h) using configuration—computer—equipment data means, as a function of the specific features of the computer equipment (5) and/or the data analysis software (5 e),
the said configuration—computer—equipment data are saved (4 f, 5 i).
5. System for collecting data produced by sending apparatus (1), and particularly medical data originating from medical apparatus, for example apparatus located in intensive care units (2), and for distributing the said data to users (3), and particularly to health practitioners;
the said system comprising at least one data processing device (4) comprising:
reception means (4 a), particularly a reception software module, to receive data (7) originating from sending apparatus (1),
data processing means (4 b), and particularly a data processing software module, for translating received data into a common format,
data sending means (4 c), particularly a data sending software module, to distribute the data in a common format to users (3);
the said system being such that the user (3) has computer equipment (5), and particularly a personal microcomputer, connected to a display screen (5 a) and/or a printer (5 b) and/or a loudspeaker (5 c); each computer equipment comprising:
means (5 d) for reception of data sent by the said data processing device (4);
a data analysis software (5 e);
the said system being such that it converts data in a common format into formatted data compatible with the computer equipment (5) and/or other modules (5 g) of the said data analysis software (5 e), using the following procedure:
the said data analysis software (5 e) of the said computer equipment comprises a conversion module (5 f) and/or
the said data processing device (4) also comprises conversion means (4 d), and particularly a conversion software module.
6. System according to claim 5 such that the data processing device (4) is integrated in the said computer equipment (5).
7. System according to claim 5 such that the reception means (5 d) on the said computer equipment (5) are interconnected to the sending means (4 c) of the said data processing device (4) through a computer communication network (6), particularly an Internet type network.
8. System according to any one of claims 5 to 8 , such that the data processing device (4) comprises:
a configuration—reception interface (4 e), and particularly a configuration—reception module, used to input configuration data for the reception means (4 a) as a function of the format of data originating from sending apparatus (1),
a register (4 f) containing the said reception means configuration data (4 a).
9. System according to any one of claims 5 to 9 , such that the data processing device (4) comprises:
means (4 g) to store data translated into a common format.
10. System according to any one of claims 5 to 10 , such that the said data analysis software (5 e) on the said computer equipment (5) comprises:
a configuration—reception module (5 h) used to input configuration data for the reception means (5 d) as a function of the specific features of the computer equipment (5) and/or the other modules (5 g) of the data analysis software (5 e),
a saving module (5 i) containing the said configuration—reception data of the reception means,
(such that users can access data sent by a remote sending apparatus, even if the data are formatted according to standards different from the standards for the computer equipment and the data analysis software that they use).
11. System according to any one of claims 5 to 11 , such that the data processing device 4 comprises:
a configuration—sending interface (4 e), and particularly a configuration—sending module, used to input configuration data for emission means (4 c) as a function of the specific features of computer equipment (5) and the data analysis software (5 e) with which they will be used,
a register (4 f) containing the said sending means configuration data (4 c),
(such that users can access data sent by a remote sending apparatus, even if these data are formatted according to standards different from the standards in their own computer equipment and the data analysis software that they use).
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0004391A FR2807542B1 (en) | 2000-04-06 | 2000-04-06 | METHOD AND SYSTEM FOR COLLECTING AND DISSEMINATING DATA FROM DEVICES, IN PARTICULAR MEDICAL DEVICES |
FR00/04391 | 2000-04-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030158746A1 true US20030158746A1 (en) | 2003-08-21 |
Family
ID=8848931
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/257,098 Abandoned US20030158746A1 (en) | 2000-04-06 | 2001-04-05 | Method and system for collecting and circulating data derived from medical appliances, useful in particular in intensive care units |
US10/258,244 Expired - Fee Related US9436800B2 (en) | 2000-04-06 | 2001-04-05 | Method and system for collecting and disseminating data produced by medical devices, particularly those used in intensive care units |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/258,244 Expired - Fee Related US9436800B2 (en) | 2000-04-06 | 2001-04-05 | Method and system for collecting and disseminating data produced by medical devices, particularly those used in intensive care units |
Country Status (5)
Country | Link |
---|---|
US (2) | US20030158746A1 (en) |
EP (2) | EP1279134A1 (en) |
AU (2) | AU2001248479A1 (en) |
FR (1) | FR2807542B1 (en) |
WO (2) | WO2001077980A1 (en) |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070214010A1 (en) * | 2006-01-09 | 2007-09-13 | Proxymed, Inc., D/B/A Medavant Healthcare Solutions | Systems and methods for utilizing a secure electronic gateway at a physician's office |
US20100106825A1 (en) * | 2007-02-28 | 2010-04-29 | Corporacio Sanitaria Parc Tauli | Method and system for managing related-patient parameters provided by a monitoring device |
US20130197929A1 (en) * | 2000-05-18 | 2013-08-01 | Carefusion 303, Inc. | Healthcare communication system |
US20130227128A1 (en) * | 2010-09-08 | 2013-08-29 | Lantronix, Inc. | Graphical Tools For Obtaining Data From A Medical Device |
US20150142475A1 (en) * | 2013-11-20 | 2015-05-21 | Medical Informatics Corp. | Distributed grid-computing platform for collecting, archiving, and processing arbitrary data in a healthcare environment |
US9427520B2 (en) | 2005-02-11 | 2016-08-30 | Carefusion 303, Inc. | Management of pending medication orders |
US9436800B2 (en) | 2000-04-06 | 2016-09-06 | Capsule Technologie | Method and system for collecting and disseminating data produced by medical devices, particularly those used in intensive care units |
US9600633B2 (en) | 2000-05-18 | 2017-03-21 | Carefusion 303, Inc. | Distributed remote asset and medication management drug delivery system |
US9741001B2 (en) | 2000-05-18 | 2017-08-22 | Carefusion 303, Inc. | Predictive medication safety |
US10029047B2 (en) | 2013-03-13 | 2018-07-24 | Carefusion 303, Inc. | Patient-specific medication management system |
US10062457B2 (en) | 2012-07-26 | 2018-08-28 | Carefusion 303, Inc. | Predictive notifications for adverse patient events |
US10064579B2 (en) | 2004-08-25 | 2018-09-04 | Carefusion 303, Inc. | System and method for dynamically adjusting patient therapy |
US10353856B2 (en) | 2011-03-17 | 2019-07-16 | Carefusion 303, Inc. | Scalable communication system |
US10430554B2 (en) | 2013-05-23 | 2019-10-01 | Carefusion 303, Inc. | Medication preparation queue |
US10867265B2 (en) | 2013-03-13 | 2020-12-15 | Carefusion 303, Inc. | Predictive medication safety |
US11087873B2 (en) | 2000-05-18 | 2021-08-10 | Carefusion 303, Inc. | Context-aware healthcare notification system |
US11182728B2 (en) | 2013-01-30 | 2021-11-23 | Carefusion 303, Inc. | Medication workflow management |
Families Citing this family (58)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050278194A1 (en) * | 2003-10-07 | 2005-12-15 | Holland Geoffrey N | Medication management system |
US7895053B2 (en) * | 2003-10-07 | 2011-02-22 | Hospira, Inc. | Medication management system |
US20060100907A1 (en) * | 2003-10-07 | 2006-05-11 | Holland Geoffrey N | Medication management system |
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 |
US9123077B2 (en) | 2003-10-07 | 2015-09-01 | Hospira, Inc. | Medication management system |
US8065161B2 (en) | 2003-11-13 | 2011-11-22 | Hospira, Inc. | System for maintaining drug information and communicating with medication delivery devices |
US20070214003A1 (en) * | 2003-10-07 | 2007-09-13 | Holland Geoffrey N | Medication management system |
US7490021B2 (en) * | 2003-10-07 | 2009-02-10 | Hospira, Inc. | Method for adjusting pump screen brightness |
EP2092470A2 (en) | 2006-10-16 | 2009-08-26 | Hospira, Inc. | System and method for comparing and utilizing activity information and configuration information from mulitple device management systems |
US9026370B2 (en) | 2007-12-18 | 2015-05-05 | Hospira, Inc. | User interface improvements for medical devices |
CN107256345A (en) * | 2008-09-26 | 2017-10-17 | 皇家飞利浦电子股份有限公司 | System and method for wired and wireless medical equipment and gateway simply to be matched |
US9137312B2 (en) | 2008-09-26 | 2015-09-15 | Koninklijke Philips N.V. | System and method for simple pairing of wired and wireless healthcare devices to a gateway |
US8271106B2 (en) | 2009-04-17 | 2012-09-18 | Hospira, Inc. | System and method for configuring a rule set for medical event management and responses |
JP2014500538A (en) | 2010-10-12 | 2014-01-09 | タニス,ケヴィン ジェイ. | Medical equipment |
EP2724242A4 (en) | 2011-06-27 | 2015-12-02 | Fisher & Paykel Healthcare Ltd | Data capture and routing system and method |
US9240002B2 (en) | 2011-08-19 | 2016-01-19 | Hospira, Inc. | Systems and methods for a graphical interface including a graphical representation of medical data |
ES2959510T3 (en) | 2011-10-21 | 2024-02-26 | Icu Medical Inc | Medical device update system |
US9619496B2 (en) * | 2011-12-16 | 2017-04-11 | Siemens Aktiengesellschaft | Method, computer readable medium and system for using large data sets in virtual applications |
US10022498B2 (en) | 2011-12-16 | 2018-07-17 | 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 |
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 |
ES2743160T3 (en) | 2012-07-31 | 2020-02-18 | Icu Medical Inc | Patient care system for critical medications |
AU2014225658B2 (en) | 2013-03-06 | 2018-05-31 | Icu Medical, Inc. | Medical device communication method |
US9737649B2 (en) | 2013-03-14 | 2017-08-22 | Smith & Nephew, Inc. | Systems and methods for applying reduced pressure therapy |
AU2014268355B2 (en) | 2013-05-24 | 2018-06-14 | Icu Medical, Inc. | Multi-sensor infusion system for detecting air or an occlusion in the infusion system |
AU2014274146B2 (en) | 2013-05-29 | 2019-01-24 | Icu Medical, Inc. | Infusion system which utilizes one or more sensors and additional information to make an air determination regarding the infusion system |
WO2014194065A1 (en) | 2013-05-29 | 2014-12-04 | Hospira, Inc. | Infusion system and method of use which prevents over-saturation of an analog-to-digital converter |
JP6621748B2 (en) | 2013-08-30 | 2019-12-18 | アイシーユー・メディカル・インコーポレーテッド | System and method for monitoring and managing a remote infusion regimen |
US9662436B2 (en) | 2013-09-20 | 2017-05-30 | Icu Medical, Inc. | Fail-safe drug infusion therapy system |
US10311972B2 (en) | 2013-11-11 | 2019-06-04 | Icu Medical, Inc. | Medical device system performance index |
WO2015077320A1 (en) | 2013-11-19 | 2015-05-28 | Hospira, Inc. | Infusion pump automation system and method |
JP6636442B2 (en) | 2014-02-28 | 2020-01-29 | アイシーユー・メディカル・インコーポレーテッド | Infusion systems and methods utilizing dual wavelength optical in-pipe air detection |
JP6853669B2 (en) | 2014-04-30 | 2021-03-31 | アイシーユー・メディカル・インコーポレーテッド | Patient treatment system with conditional alert forwarding |
JP2017517302A (en) | 2014-05-29 | 2017-06-29 | ホスピーラ インコーポレイテッド | Infusion system and pump with configurable closed loop delivery rate catchup |
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 |
US11344668B2 (en) | 2014-12-19 | 2022-05-31 | Icu Medical, Inc. | Infusion system with concurrent TPN/insulin infusion |
US10850024B2 (en) | 2015-03-02 | 2020-12-01 | Icu Medical, Inc. | Infusion system, device, and method having advanced infusion features |
WO2016174901A1 (en) | 2015-04-30 | 2016-11-03 | ソニー・オリンパスメディカルソリューションズ株式会社 | Signal processing device and medical observation system |
WO2016189417A1 (en) | 2015-05-26 | 2016-12-01 | Hospira, Inc. | Infusion pump system and method with multiple drug library editor source capability |
US11315681B2 (en) | 2015-10-07 | 2022-04-26 | Smith & Nephew, Inc. | Reduced pressure therapy device operation and authorization monitoring |
AU2017261814B2 (en) | 2016-05-13 | 2022-05-19 | Smith & Nephew, Inc. | Automatic wound coupling detection in negative pressure wound therapy systems |
EP4085944A1 (en) | 2016-05-13 | 2022-11-09 | ICU Medical, Inc. | Infusion pump system with common line auto flush |
US11324888B2 (en) | 2016-06-10 | 2022-05-10 | Icu Medical, Inc. | Acoustic flow sensor for continuous medication flow measurements and feedback control of infusion |
EP3484541A4 (en) | 2016-07-14 | 2020-03-25 | ICU Medical, Inc. | Multi-communication path selection and security system for a medical device |
AU2017335635B2 (en) | 2016-09-29 | 2023-01-05 | Smith & Nephew, Inc. | Construction and protection of components in negative pressure wound therapy systems |
US11712508B2 (en) | 2017-07-10 | 2023-08-01 | Smith & Nephew, Inc. | Systems and methods for directly interacting with communications module of wound therapy apparatus |
US10089055B1 (en) | 2017-12-27 | 2018-10-02 | Icu Medical, Inc. | Synchronized display of screen content on networked devices |
US10950339B2 (en) | 2018-07-17 | 2021-03-16 | Icu Medical, Inc. | Converting pump messages in new pump protocol to standardized dataset messages |
NZ771914A (en) | 2018-07-17 | 2023-04-28 | Icu Medical Inc | Updating infusion pump drug libraries and operational software in a networked environment |
US11139058B2 (en) | 2018-07-17 | 2021-10-05 | Icu Medical, Inc. | Reducing file transfer between cloud environment and infusion pumps |
EP3824383B1 (en) | 2018-07-17 | 2023-10-11 | ICU Medical, Inc. | Systems and methods for facilitating clinical messaging in a network environment |
AU2019309766A1 (en) | 2018-07-26 | 2021-03-18 | Icu Medical, Inc. | Drug library management system |
US10692595B2 (en) | 2018-07-26 | 2020-06-23 | Icu Medical, Inc. | Drug library dynamic version management |
GB201820668D0 (en) | 2018-12-19 | 2019-01-30 | Smith & Nephew Inc | Systems and methods for delivering prescribed wound therapy |
US11278671B2 (en) | 2019-12-04 | 2022-03-22 | Icu Medical, Inc. | Infusion pump with safety sequence keypad |
CA3189781A1 (en) | 2020-07-21 | 2022-01-27 | Icu Medical, Inc. | Fluid transfer devices and methods of use |
US11135360B1 (en) | 2020-12-07 | 2021-10-05 | Icu Medical, Inc. | Concurrent infusion with common line auto flush |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4653112A (en) * | 1985-02-05 | 1987-03-24 | University Of Connecticut | Image data management system |
US4764870A (en) * | 1987-04-09 | 1988-08-16 | R.A.P.I.D., Inc. | System and method for remote presentation of diagnostic image information |
US5513101A (en) * | 1993-11-26 | 1996-04-30 | Access Radiology Corporation | Radiological image interpretation apparatus and method |
US5664109A (en) * | 1995-06-07 | 1997-09-02 | E-Systems, Inc. | Method for extracting pre-defined data items from medical service records generated by health care providers |
US5715823A (en) * | 1996-02-27 | 1998-02-10 | Atlantis Diagnostics International, L.L.C. | Ultrasonic diagnostic imaging system with universal access to diagnostic information and images |
US5822544A (en) * | 1990-07-27 | 1998-10-13 | Executone Information Systems, Inc. | Patient care and communication system |
US5890129A (en) * | 1997-05-30 | 1999-03-30 | Spurgeon; Loren J. | System for exchanging health care insurance information |
US6018713A (en) * | 1997-04-09 | 2000-01-25 | Coli; Robert D. | Integrated system and method for ordering and cumulative results reporting of medical tests |
US6074345A (en) * | 1998-10-27 | 2000-06-13 | University Of Florida | Patient data acquisition and control system |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5995937A (en) * | 1997-11-07 | 1999-11-30 | Deroyal Industries, Inc. | Modular health-care information management system utilizing reusable software objects |
US6101407A (en) * | 1998-02-13 | 2000-08-08 | Eastman Kodak Company | Method and system for remotely viewing and configuring output from a medical imaging device |
US20100008551A9 (en) * | 1998-08-18 | 2010-01-14 | Ilya Schiller | Using handwritten information |
FR2807542B1 (en) | 2000-04-06 | 2006-09-29 | Capsule Technologie | METHOD AND SYSTEM FOR COLLECTING AND DISSEMINATING DATA FROM DEVICES, IN PARTICULAR MEDICAL DEVICES |
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 |
-
2000
- 2000-04-06 FR FR0004391A patent/FR2807542B1/en not_active Expired - Fee Related
-
2001
- 2001-04-05 US US10/257,098 patent/US20030158746A1/en not_active Abandoned
- 2001-04-05 EP EP01921493A patent/EP1279134A1/en not_active Withdrawn
- 2001-04-05 EP EP01921496A patent/EP1279135A1/en not_active Withdrawn
- 2001-04-05 US US10/258,244 patent/US9436800B2/en not_active Expired - Fee Related
- 2001-04-05 WO PCT/FR2001/001033 patent/WO2001077980A1/en not_active Application Discontinuation
- 2001-04-05 AU AU2001248479A patent/AU2001248479A1/en not_active Abandoned
- 2001-04-05 AU AU48476/01A patent/AU4847601A/en not_active Abandoned
- 2001-04-05 WO PCT/FR2001/001036 patent/WO2001077981A1/en not_active Application Discontinuation
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4653112A (en) * | 1985-02-05 | 1987-03-24 | University Of Connecticut | Image data management system |
US4764870A (en) * | 1987-04-09 | 1988-08-16 | R.A.P.I.D., Inc. | System and method for remote presentation of diagnostic image information |
US5822544A (en) * | 1990-07-27 | 1998-10-13 | Executone Information Systems, Inc. | Patient care and communication system |
US5513101A (en) * | 1993-11-26 | 1996-04-30 | Access Radiology Corporation | Radiological image interpretation apparatus and method |
US5664109A (en) * | 1995-06-07 | 1997-09-02 | E-Systems, Inc. | Method for extracting pre-defined data items from medical service records generated by health care providers |
US5715823A (en) * | 1996-02-27 | 1998-02-10 | Atlantis Diagnostics International, L.L.C. | Ultrasonic diagnostic imaging system with universal access to diagnostic information and images |
US6018713A (en) * | 1997-04-09 | 2000-01-25 | Coli; Robert D. | Integrated system and method for ordering and cumulative results reporting of medical tests |
US5890129A (en) * | 1997-05-30 | 1999-03-30 | Spurgeon; Loren J. | System for exchanging health care insurance information |
US6074345A (en) * | 1998-10-27 | 2000-06-13 | University Of Florida | Patient data acquisition and control system |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9436800B2 (en) | 2000-04-06 | 2016-09-06 | Capsule Technologie | Method and system for collecting and disseminating data produced by medical devices, particularly those used in intensive care units |
US10275571B2 (en) | 2000-05-18 | 2019-04-30 | Carefusion 303, Inc. | Distributed remote asset and medication management drug delivery system |
US11823791B2 (en) | 2000-05-18 | 2023-11-21 | Carefusion 303, Inc. | Context-aware healthcare notification system |
US11087873B2 (en) | 2000-05-18 | 2021-08-10 | Carefusion 303, Inc. | Context-aware healthcare notification system |
US9600633B2 (en) | 2000-05-18 | 2017-03-21 | Carefusion 303, Inc. | Distributed remote asset and medication management drug delivery system |
US9741001B2 (en) | 2000-05-18 | 2017-08-22 | Carefusion 303, Inc. | Predictive medication safety |
US20130197929A1 (en) * | 2000-05-18 | 2013-08-01 | Carefusion 303, Inc. | Healthcare communication system |
US10064579B2 (en) | 2004-08-25 | 2018-09-04 | Carefusion 303, Inc. | System and method for dynamically adjusting patient therapy |
US10668211B2 (en) | 2005-02-11 | 2020-06-02 | Carefusion 303, Inc. | Management of pending medication orders |
US11590281B2 (en) | 2005-02-11 | 2023-02-28 | Carefusion 303, Inc. | Management of pending medication orders |
US9427520B2 (en) | 2005-02-11 | 2016-08-30 | Carefusion 303, Inc. | Management of pending medication orders |
US9981085B2 (en) | 2005-02-11 | 2018-05-29 | Carefusion, 303, Inc. | Management of pending medication orders |
US20070214010A1 (en) * | 2006-01-09 | 2007-09-13 | Proxymed, Inc., D/B/A Medavant Healthcare Solutions | Systems and methods for utilizing a secure electronic gateway at a physician's office |
US20100106825A1 (en) * | 2007-02-28 | 2010-04-29 | Corporacio Sanitaria Parc Tauli | Method and system for managing related-patient parameters provided by a monitoring device |
US8856298B2 (en) * | 2007-02-28 | 2014-10-07 | Corporacia Sanitaria Parc Tauli | Method and system for managing related-patient parameters provided by a monitoring device |
US20130227128A1 (en) * | 2010-09-08 | 2013-08-29 | Lantronix, Inc. | Graphical Tools For Obtaining Data From A Medical Device |
US11734222B2 (en) | 2011-03-17 | 2023-08-22 | Carefusion 303, Inc. | Scalable communication system |
US11366781B2 (en) | 2011-03-17 | 2022-06-21 | Carefusion 303, Inc. | Scalable communication system |
US10353856B2 (en) | 2011-03-17 | 2019-07-16 | Carefusion 303, Inc. | Scalable communication system |
US10983946B2 (en) | 2011-03-17 | 2021-04-20 | Carefusion 303, Inc. | Scalable communication system |
US10062457B2 (en) | 2012-07-26 | 2018-08-28 | Carefusion 303, Inc. | Predictive notifications for adverse patient events |
US11182728B2 (en) | 2013-01-30 | 2021-11-23 | Carefusion 303, Inc. | Medication workflow management |
US11615871B2 (en) | 2013-03-13 | 2023-03-28 | Carefusion 303, Inc. | Patient-specific medication management system |
US10937530B2 (en) | 2013-03-13 | 2021-03-02 | Carefusion 303, Inc. | Patient-specific medication management system |
US10867265B2 (en) | 2013-03-13 | 2020-12-15 | Carefusion 303, Inc. | Predictive medication safety |
US10029047B2 (en) | 2013-03-13 | 2018-07-24 | Carefusion 303, Inc. | Patient-specific medication management system |
US10430554B2 (en) | 2013-05-23 | 2019-10-01 | Carefusion 303, Inc. | Medication preparation queue |
US10892045B2 (en) * | 2013-11-20 | 2021-01-12 | Medical Informatics Corp. | Distributed grid-computing platform for collecting, archiving, and processing arbitrary data in a healthcare environment |
US20150142475A1 (en) * | 2013-11-20 | 2015-05-21 | Medical Informatics Corp. | Distributed grid-computing platform for collecting, archiving, and processing arbitrary data in a healthcare environment |
Also Published As
Publication number | Publication date |
---|---|
EP1279134A1 (en) | 2003-01-29 |
FR2807542A1 (en) | 2001-10-12 |
US20030200116A1 (en) | 2003-10-23 |
EP1279135A1 (en) | 2003-01-29 |
US9436800B2 (en) | 2016-09-06 |
FR2807542B1 (en) | 2006-09-29 |
WO2001077980A1 (en) | 2001-10-18 |
AU4847601A (en) | 2001-10-23 |
WO2001077981A1 (en) | 2001-10-18 |
AU2001248479A1 (en) | 2001-10-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20030158746A1 (en) | Method and system for collecting and circulating data derived from medical appliances, useful in particular in intensive care units | |
CA2432141C (en) | Computer oriented record administration system | |
EP2235906B1 (en) | Method and system for wireless medical device communication | |
US20070288268A1 (en) | Adaptable Electronic Medical Record System and Method | |
US20020038226A1 (en) | System and method for capturing and archiving medical multimedia data | |
KR20070116893A (en) | Communication of information between a plurality of network elements | |
WO2005119563A2 (en) | Generalized approach to structured medical reporting | |
Martíez et al. | Seamless integration of ISO/IEEE11073 personal health devices and ISO/EN13606 electronic health records into an end-to-end interoperable solution | |
US20070083394A1 (en) | Medical data collection for PDA | |
WO2007056323A2 (en) | A context information processing system used for accessing medical data | |
CN108447548A (en) | Patient medical image archiving method and system | |
CA2383453C (en) | System and method for interfacing a radiology information system to a central dictation system | |
Levine et al. | Challenges encountered while implementing a multivendor teleradiology network using DICOM 3.0 | |
Chenhui et al. | An integration approach of healthcare information system | |
US20070033653A1 (en) | System and method for managing sensitive information | |
Katehakis et al. | An open, component-based information infrastructure to support integrated regional healthcare networks | |
Ganguly et al. | Telemedicine over enterprise-wide networks: a case study | |
CN111475449A (en) | HIS system and external program interface adaptation method, system, interface adapter and comprehensive medical system | |
WO2007047588A1 (en) | A healthcare information interfacing system | |
CN115080529A (en) | System and method for sharing DICOM image file in hospital system | |
CN213877603U (en) | Regional medical image remote diagnosis system | |
CN113778560B (en) | Method, system, equipment and medium for custom development and execution of hospital treatment process | |
CN111430009B (en) | Method, device, equipment and storage medium for searching protocol matching | |
CN117708036A (en) | AT instruction processing method and device, terminal and terminal equipment | |
CN116798624A (en) | Health physical examination CIS system based on detection equipment Internet of things |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CAPSULE TECHNOLOGIE, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FORRESTER, STEVEN;REEL/FRAME:013956/0810 Effective date: 20030318 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |