WO2017115237A1 - Données contextuelles pour des pompes à perfusion - Google Patents

Données contextuelles pour des pompes à perfusion Download PDF

Info

Publication number
WO2017115237A1
WO2017115237A1 PCT/IB2016/057913 IB2016057913W WO2017115237A1 WO 2017115237 A1 WO2017115237 A1 WO 2017115237A1 IB 2016057913 W IB2016057913 W IB 2016057913W WO 2017115237 A1 WO2017115237 A1 WO 2017115237A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
infusion pump
communication
processor
patient
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.)
Ceased
Application number
PCT/IB2016/057913
Other languages
English (en)
Inventor
John Cronin
Steven Philbin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Koninklijke Philips NV
Original Assignee
Koninklijke Philips NV
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Koninklijke Philips NV filed Critical Koninklijke Philips NV
Publication of WO2017115237A1 publication Critical patent/WO2017115237A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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/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
    • 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

Definitions

  • the present invention generally relates to infusion pumps. More specifically, the present invention relates to remote device that provides contextual data infusion pumps.
  • Infusion pumps are devices that deliver fluids, nutrients, and/or medication directly into a patient's body in controlled amounts and at controlled rates.
  • Infusion pumps may deliver intravenous, subcutaneous, arterial, or epidural infusions.
  • Presently available infusion systems and pumps currently do not have the ability to intelligently use electronic medical records to adjust treatment in real-time.
  • Magnetic resonance imaging is a procedure generally used to create images of internal organs and structures in the human body by using magnetic fields.
  • MRI-compatible infusion pumps administered by one or more MRI-compatible infusion pumps.
  • Embodiments of the present invention include systems and methods for controlling infusion pump operation based on contextual medical data.
  • Such systems may include a database in memory of a network server. Such a database may store medical information regarding one or more patients.
  • Systems may further include a communication interface that receives infusion pump data from an infusion pump, as well as a processor that executes instructions to identify that the medical information regarding the patient and the received infusion pump data corresponding to one or more rules.
  • the processor may also generate control instructions for the infusion pump based on an action associated with the corresponding rules.
  • the communication interface may then send the control instructions to the infusion pump for execution, and the infusion pump may execute the instructions to perform the action associated with the corresponding rules.
  • FIG. 1 illustrates an exemplary network environment in which a system for providing contextual data for infusion pump operations may be implemented.
  • FIG. 2 illustrates an exemplary context GUI that includes fields for contextual data to be displayed at the remote device.
  • FIG. 3 illustrates an exemplary pump GUI that includes fields for pump data to be displayed at the infusion pump.
  • FIG. 4 is a flowchart illustrating an exemplary method for adjusting infusion pump operations based on contextual data.
  • FIG. 5 illustrates an exemplary computing system that may be used to implement an embodiment of the present invention.
  • Embodiments of the present invention include systems and methods for controlling infusion pump operation based on contextual medical data.
  • a database in memory of a network server may store medical information regarding one or more patients.
  • a remote device may receive infusion pump data from an infusion pump, identify that the medical information regarding the patient and the received infusion pump data correspond to one or more rules, and generate control instructions for the infusion pump based on an action associated with the corresponding rules. The remote device may then send the control instructions to the infusion pump, which then executes the instructions to perform the action associated with the corresponding rules.
  • FIG. 1 illustrates an exemplary network environment 10 in which a system
  • the network environment may include a remote device 102 for MRI-compatible infusion pump (e.g., IV pump), one or more support devices 104, one or more medical network servers 105, and an infusion pump 108.
  • MRI-compatible infusion pump e.g., IV pump
  • support devices 104 e.g., IV pump
  • medical network servers 105 e.g., XPS
  • infusion pump 108 e.g., IV pump
  • Such devices may communicate with each other via hard-wired or wireless communications systems and networks known in the art.
  • Such communication networks 110 may include a local, proprietary network
  • the communications network may be a local area network (LAN), which may be communicatively coupled to a wide area network (WAN) such as the Internet.
  • LAN local area network
  • WAN wide area network
  • IP Internet Protocol
  • Examples of network service providers are the public switched telephone network, a cable service provider, a provider of digital subscriber line (DSL) services, or a satellite service provider.
  • Communications networks 110 allow for communication between the various components of network environment.
  • the remote device 102 may include a communication module 112, display screen (and/or another input/output mechanism) 114, context graphic user interface (GUI) 116, and IV pump context software 118 executable to make decisions on infusion/I V pump operations.
  • the remote device 102 may be in communication with a medical network server 106 and able to access electronic medical records stored at the medical network server 106.
  • Such a remote device 102 can allow a user (e.g., patient, medical care provider, or other authorized personnel) to input and access contextual data regarding a patient directly from the medical records.
  • Such medical data can also be downloaded to the remote device 102, which may use such data to adjust operation parameters of an infusion pump 108 used by the patient.
  • the remote device 102 can be a small computer or a computing device, such as that shown in FIG. 5, able to complete a handshake with a communication network 110 having access to the medical record-keeping servers 106.
  • the remote device 102 may be any number of different electronic user devices, such as general purpose computers, mobile phones, smartphones, personal digital assistants (PDAs), portable computing devices (e.g., laptop, netbook, tablets), desktop computing devices, handheld computing device, or any other type of computing device capable of communicating over communication network (wired or wireless).
  • the remote device 102 may also be configured to access data from other storage media, such as memory cards or disk drives as may be appropriate in the case of downloaded services.
  • the remote device 102 may include standard hardware computing components such as network and media interfaces, non-transitory computer-readable storage (memory), and processors for executing instructions that may be stored in memory.
  • the remote device 102 may receive data from the IV pump 108 and displays it on the display screen 114.
  • the remote device 102 may also access contextual data (e.g., electronic medical records for the patient being treated by the infusion pump 108) from the medical network server 106 and displays via the context GUI 116.
  • Context data can also be collected at the remote device 102 and sent to medical network server 106 for storage (e.g., in the electronic medical record files of the patient).
  • Context data can be collected from hardware in various support devices 104 associated with the patient, including hospital bed data or other medical sensors 105 (e.g., temperature, heart rate).
  • the remote device 102 may use local context software 118 to evaluate context data to determine patient status and if applicable, provide a response.
  • the remote device 102 may identify whether there should be any changes to the operation of the infusion pump 108, as well as provide insights or alerts regarding possible medical conditions. Such alerts may be sent to designated medical personnel or to other remote alert devices (e.g., used to monitor different medical conditions).
  • possible medical conditions that may affect the patient are identified in stored genetic data.
  • stored genetic data may include family histories, results of one or more genetic tests, and full or partial gene sequences.
  • the patient genetic data may be stored in the same database 120 containing the electronic medical records for the patient.
  • the medical network server 106 may include any type of server or other computing device as is known in the art, including standard hardware computing components such as network and media interfaces, non-transitory computer-readable storage (memory), and processors for executing instructions or accessing information that may be stored in memory.
  • the functionalities of multiple servers may be integrated into a single server. Any of the aforementioned servers (or an integrated server) may take on certain client-side, cache, or proxy server characteristics. These characteristics may depend on the particular network placement of the server or certain configurations of the server.
  • Medical network server 106 may include or have access to one or more databases 120-122 storing digital patient medical records.
  • the medical network server 106 may also have access to third party databases and information sources, including various forums, chat rooms, medical personnel, and other medical experts.
  • the medical network server 106 may be able to aggregate information relevant to the patient in real-time from multiple sources (e.g., current support devices 104, sensors 105, various databases), as well as update the patient's electronic medical records regarding the same.
  • a separate database 122 storing genetic data for the patients may be a part of the medical network along with the electronic records database as shown in FIG. 1.
  • the medical network server 106 may further include IV network context software 124, communication software 126, and an artificial intelligence (AI) engine or rules engine 128.
  • the AI/rules engine 128 may be used to evaluate context data (e.g., from the remote device 102 and IV pump), as well as suggest changes or provide calculated context insights (e.g., notifications that "patient may be in danger"). Such evaluations may be based on rules associating certain combinations of contextual data (e.g., whether certain measurements or biometric data fall within ranges or meet thresholds) with one or more conclusions or actions.
  • the infusion pump 108 may also include communications systems 130, an associated IV display 132 (and/or other input-output mechanisms), and a pump GUI 134.
  • FIG. 2 illustrates an exemplary context GUI 116 that includes fields 136 for contextual data to be displayed at the remote device 102.
  • Such contextual data may have been provided to the remote device 102 by various sources, including electronic medical records databases 120, other sources accessible to medical network server 106, support devices 104, infusion pumps 108, and other sensors 105, as well as data that may be entered directly by a user (e.g., the patient themselves or other medical personnel). Some of the data may be updated in real-time as the measurements (e.g., temperature) are taken by the various device sensors 105 associated with the patient.
  • FIG. 3 illustrates an exemplary pump GUI 134 that includes fields 138 for pump data to be displayed at the infusion pump 108.
  • a pump GUI 134 may include pump data fields 138 for type of medication, rate of infusion, and volume of infusion.
  • Such pump GUI 134 may be displayed on a screen 132 associated with the infusion pump 108, as well as be sent to other devices for storage and/or analysis.
  • FIG. 4 is a flowchart illustrating an exemplary method 200 for adjusting infusion pump operations, for example at the infusion pump 108, based on contextual data.
  • the method 200 of FIG. 4 may be embodied as executable instructions in a non-transitory computer readable storage medium including but not limited to a CD, DVD, or non-volatile memory such as a hard drive.
  • the instructions of the storage medium may be executed by a processor (or processors) to cause various hardware components of a computing device hosting or otherwise accessing the storage medium to effectuate the method.
  • the steps 202- 214 identified in FIG. 4 (and the order thereof) are exemplary and may include various alternatives, equivalents, or derivations thereof including but not limited to the order of execution of the same.
  • an infusion pump 108 may send its current infusion pump data to remote device 102 at step 202.
  • the remote device 102 receives data not only from the infusion pump 108, but from various support devices 104/ sensors 105 as well at step 204. Such received data may be stored in a database, as well as displayed at step 206 in a context GUI 116.
  • the remote device 102 also allows a user to enter data into the context GUI 116 via one or more input-output devices known in the art (e.g., touchscreen, keyboard, keypad, other buttons, microphone, camera, and other peripheral devices).
  • the infusion pump data, context data, and patient identifier may be sent to medical network server 106, which stores such data in an electronic medical records database 120. Specifically, such data may be stored in a record associated with the patient (as identified by the patient identifier).
  • the medical network server 106 may also execute IV network context software 124 to process and evaluate such data at step 210 to determine which next steps are to be taken.
  • the Al/rules engine 128 may be executed to evaluate the contextual data against rules stored in memory to derive certain conclusions about the patient.
  • Such conclusions and associated data may be sent by the medical network server 106 to the remote device 102 at step 214.
  • the remote device 102 may perform further analyses, use such data to control operation of the infusion pump 108 (or other support devices 104 or sensors 105), and/or provide to the infusion pump (which may also perform local analyses for use in adjusting operations).
  • FIG. 5 illustrates an exemplary computing system 300 that may be used to implement an embodiment of the present invention.
  • the computing system of FIG. 5 includes one or more processors 302 and memory 304.
  • Main memory 304 stores, in part, instructions and data for execution by the processor 302.
  • Main memory 304 can store the executable code when in operation.
  • the system of FIG. 5 may further include a mass storage device 306, portable storage medium drive(s) 308, output devices 310, user input devices 312, a graphics display 314, and peripheral devices 316.
  • FIG. 5 The components shown in FIG. 5 are depicted as being connected via a single bus 318. However, the components maybe connected through one or more data transport means.
  • the processor unit 302 and main memory 304 may be connected via a local microprocessor bus, and the mass storage device 306, peripheral device(s) 316, portable storage device 308, and display system 314 may be connected via one or more input/output (I/O) buses.
  • I/O input/output
  • the mass storage device 306 which may be implemented with a magnetic disk drive or an optical disk drive, is a non- volatile storage device for storing data and instructions for use by processor unit.
  • the mass storage device 306 can store the system software for implementing embodiments of the present invention and for purposes of loading that software into main memory 304.
  • the portable storage device 308 operates in conjunction with a portable nonvolatile storage medium, such as a floppy disk, compact disk, or Digital video disc, to input and output data and code to and from the computer system of FIG. 5.
  • a portable nonvolatile storage medium such as a floppy disk, compact disk, or Digital video disc
  • the system software for implementing embodiments of the present invention may be stored on such a portable medium and input to the computer system via the portable storage device 308.
  • Input devices 312 provide a portion of a user interface.
  • Input devices 312 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys.
  • the system 300 as shown in FIG. 5 includes output devices 310. Examples of suitable output devices 310 include speakers, printers, network interfaces, and monitors.
  • the display system 314 may include a liquid crystal display (LCD) or other suitable display device.
  • the display system 314 receives textual and graphical information, and processes the information for output to the display device.
  • Peripherals 316 may include any type of computer support device to add additional functionality to the computer system.
  • peripheral device(s) may include a modem or a router.
  • the components contained in the computer system 300 of FIG. 5 are those typically found in computer systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such computer components that are well known in the art.
  • the computer system 300 of FIG. 5 can be a personal computer, hand held computing device, telephone, mobile computing device, workstation, server, minicomputer, mainframe computer, or any other computing device.
  • the computer can also include different bus configurations, networked platforms, multiprocessor platforms, etc.
  • Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Palm OS, and other suitable operating systems.
  • Non-transitory computer-readable storage media refer to any medium or media that participate in providing instructions to a central processing unit (CPU) for execution. Such media can take many forms, including, but not limited to, non-volatile and volatile media such as optical or magnetic disks and dynamic memory, respectively. Common forms of non-transitory computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, RAM, PROM, EPROM, a FLASHEPROM, and any other memory chip or cartridge.
  • a bus carries the data to system RAM, from which a CPU retrieves and executes the instructions.
  • the instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU.
  • Various forms of storage may likewise be implemented as well as the necessary network interfaces and network topologies to implement the same.

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Public Health (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Biomedical Technology (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Chemical & Material Sciences (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Medicinal Chemistry (AREA)
  • Infusion, Injection, And Reservoir Apparatuses (AREA)

Abstract

L'invention concerne des systèmes et des procédés pour commander une opération de pompe à perfusion sur la base de données médicales contextuelles. De tels systèmes peuvent comprendre une base de données dans une mémoire d'un serveur de réseau. Une telle base de données peut stocker des informations médicales concernant un ou plusieurs patients. Les systèmes peuvent en outre comprendre une interface de communication qui reçoit des données de pompe à perfusion à partir d'une pompe à perfusion, ainsi qu'un processeur qui exécute des instructions pour identifier que les informations médicales concernant le patient et les données de pompe à perfusion reçues correspondent à une ou plusieurs règles. Le processeur peut également générer des instructions de commande pour la pompe à perfusion sur la base d'une action associée aux règles correspondantes. L'interface de communication peut ensuite envoyer les instructions de commande à la pompe à perfusion pour une exécution, et la pompe à perfusion peut exécuter les instructions pour réaliser l'action associée aux règles correspondantes.
PCT/IB2016/057913 2015-12-31 2016-12-22 Données contextuelles pour des pompes à perfusion Ceased WO2017115237A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562273955P 2015-12-31 2015-12-31
US62/273,955 2015-12-31

Publications (1)

Publication Number Publication Date
WO2017115237A1 true WO2017115237A1 (fr) 2017-07-06

Family

ID=57796771

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2016/057913 Ceased WO2017115237A1 (fr) 2015-12-31 2016-12-22 Données contextuelles pour des pompes à perfusion

Country Status (1)

Country Link
WO (1) WO2017115237A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111710380A (zh) * 2020-06-10 2020-09-25 深圳市好克医疗仪器股份有限公司 基于医疗泵的医疗方法、装置、设备及可读存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110178462A1 (en) * 2006-04-28 2011-07-21 Medtronic Minimed, Inc. Remote monitoring for networked fluid infusion systems
US20110313789A1 (en) * 2010-01-22 2011-12-22 Deka Products Limited Partnership Electronic patient monitoring system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110178462A1 (en) * 2006-04-28 2011-07-21 Medtronic Minimed, Inc. Remote monitoring for networked fluid infusion systems
US20110313789A1 (en) * 2010-01-22 2011-12-22 Deka Products Limited Partnership Electronic patient monitoring system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111710380A (zh) * 2020-06-10 2020-09-25 深圳市好克医疗仪器股份有限公司 基于医疗泵的医疗方法、装置、设备及可读存储介质

Similar Documents

Publication Publication Date Title
US20230395216A1 (en) Patient-device association system
US20240038382A1 (en) Methods of treatment and diagnosis using enhanced patient-physician communication
US20220238196A1 (en) Systems and methods for integrating, unifying and displaying patient data across healthcare continua
JP7576601B2 (ja) 薬剤投与レジメンの遠隔処方のためのシステムおよび方法
US10103947B2 (en) Processing of portable device data
AU2010224089B2 (en) Systems and methods for viewing patient data
US10402782B2 (en) Systems and methods for and displaying patient data
US10042979B2 (en) Systems and methods for integrating, unifying and displaying patient data across healthcare continua
US20170011182A1 (en) Systems and Methods of Providing Patient Apps
US20170061091A1 (en) Indication of Outreach Options for Healthcare Facility to Facilitate Patient Actions
US20170199972A1 (en) Processing of Portable Device Data
US10572632B2 (en) Using augmented reality interface and real-time glucose data to control insulin delivery device
US11824937B2 (en) System and method for handling the connection of user accounts to other entities
US20220122723A1 (en) System and Method for the Specialized Delivery of Telemedicine Services
US20250087328A1 (en) Methods and systems for analyzing accessing of drug dispensing systems
Martens Roadmap to the effective use of continuous glucose monitoring in primary care
WO2017115237A1 (fr) Données contextuelles pour des pompes à perfusion
US20200265951A1 (en) Virtual infusion pumps
CN108475539B (zh) 磁共振成像(mri)控制

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16826180

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16826180

Country of ref document: EP

Kind code of ref document: A1