US20240021283A1 - Barcode safety and control of a medical device - Google Patents
Barcode safety and control of a medical device Download PDFInfo
- Publication number
- US20240021283A1 US20240021283A1 US18/358,380 US202318358380A US2024021283A1 US 20240021283 A1 US20240021283 A1 US 20240021283A1 US 202318358380 A US202318358380 A US 202318358380A US 2024021283 A1 US2024021283 A1 US 2024021283A1
- Authority
- US
- United States
- Prior art keywords
- information
- infusion pump
- infusion
- medication
- medical device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000001802 infusion Methods 0.000 claims description 70
- 239000003814 drug Substances 0.000 claims description 34
- 229940079593 drug Drugs 0.000 claims description 30
- 238000004891 communication Methods 0.000 claims description 9
- 230000003068 static effect Effects 0.000 claims description 4
- 230000008878 coupling Effects 0.000 claims description 3
- 238000010168 coupling process Methods 0.000 claims description 3
- 238000005859 coupling reaction Methods 0.000 claims description 3
- 238000004590 computer program Methods 0.000 claims 10
- 239000012530 fluid Substances 0.000 claims 2
- 239000003795 chemical substances by application Substances 0.000 description 42
- 230000004044 response Effects 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 7
- 238000000034 method Methods 0.000 description 7
- 238000007667 floating Methods 0.000 description 3
- BGFTWECWAICPDG-UHFFFAOYSA-N 2-[bis(4-chlorophenyl)methyl]-4-n-[3-[bis(4-chlorophenyl)methyl]-4-(dimethylamino)phenyl]-1-n,1-n-dimethylbenzene-1,4-diamine Chemical compound C1=C(C(C=2C=CC(Cl)=CC=2)C=2C=CC(Cl)=CC=2)C(N(C)C)=CC=C1NC(C=1)=CC=C(N(C)C)C=1C(C=1C=CC(Cl)=CC=1)C1=CC=C(Cl)C=C1 BGFTWECWAICPDG-UHFFFAOYSA-N 0.000 description 2
- 102000006942 B-Cell Maturation Antigen Human genes 0.000 description 2
- 108010008014 B-Cell Maturation Antigen Proteins 0.000 description 2
- 235000014510 cooky Nutrition 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9554—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL] by using bar codes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
- G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
- G06K7/10009—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation sensing by radiation using wavelengths larger than 0.1 mm, e.g. radio-waves or microwaves
- G06K7/10366—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation sensing by radiation using wavelengths larger than 0.1 mm, e.g. radio-waves or microwaves the interrogation device being adapted for miscellaneous applications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
- G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
- G06K7/14—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
- G06K7/1404—Methods for optical code recognition
- G06K7/1408—Methods for optical code recognition the method being specifically adapted for the type of code
- G06K7/1413—1D bar codes
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/40—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- 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
- G16Z—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
- G16Z99/00—Subject matter not provided for in other main groups of this subclass
Definitions
- Barcode systems are often used in medical environments to ensure safety. For example, a barcode system can ensure that correct drugs are given to the proper patient or only authorized personnel can administer the proper medical protocol to a patient.
- a barcode scanner is permanently associated with a single medical device.
- the barcode scanner is physically attached to the medical device.
- the flexibility of a medical environment is limited because it is difficult to share barcode scanners with other medical devices.
- a floating barcode is utilized in BCMA systems.
- barcode scans are sent to a centralized system. The scanning is only done to get information (e.g., device id, similar to when you scan a badge), and the information is used in backend systems to perform some general work.
- information e.g., device id, similar to when you scan a badge
- backend systems to perform some general work.
- the intent and workflow, regarding the floating barcode in a BCMA system is not for directing subsequent barcode scans to a particular device.
- a barcode scanner may be unable to directly communicate with a medical device because of limited communication capabilities.
- FIGS. 1 - 3 illustrate embodiments of a medical system.
- FIG. 4 illustrates an embodiment of displayed information.
- FIG. 5 illustrates an embodiment a method for associating an information reader and medical device.
- information readers are associated with medical devices to ensure safety in a medical environment.
- the discussion below will describe a variety of means to associate an information reader with medical device(s). In particular, the discussion will first describe the components in a medical environment. Then the discussion will describe functionality of the components during use of the medical environment.
- association for example, the association between an information reader and a medical device, generally describes the communicative coupling between the devices. As a result of the association, information, obtained by the information reader, is able to be routed to the associated device(s).
- FIG. 1 depicts an embodiment of medical environment 100 .
- Medical environment 100 includes medical device 110 , information reader 130 and device agent 140 .
- Information reader 130 is any device that is capable of reading information and also able to be associated with a medical device.
- information reader 130 can be, but is not limited to, a barcode scanner, a radio-frequency identification (RFID) reader.
- RFID radio-frequency identification
- information reader 130 can be any device (e.g., a mobile device) with barcode scanning and/or RFID reading capabilities.
- Medical device 110 can be any medical device(s) that is able to be associated with an information reader.
- medical device is a ventilator, infusion pump, etc.
- association information 122 is utilized to facilitate in the association between information reader 130 and medical device 110 .
- Association information 122 includes medical device information 124 , device agent information 126 and optionally, additional command information 128 .
- association information 122 includes a cookie (data element) that appends to any consecutive scan after an association generated.
- the cookie allows the destination device (and/or routing devices) to uniquely identify scans intended for the destination device.
- Medical device information 124 includes any information or signature that uniquely identifies medical device 110 and/or any other medical devices.
- medical device information 124 can be, but is not limited to, model number, serial number, Media Access Control address (MAC) address, Internet Protocol (IP) address, etc.
- MAC Media Access Control address
- IP Internet Protocol
- Device agent information 126 includes any information that can be utilized by device agent 140 (or any other device agent) to properly route information, obtained by information reader 130 , to medical device 110 .
- device agent information 126 can include, but is not limited to, agent name, connectivity parameters (e.g., IP/Bluetooth parameters), commands for routing information to a specific device (e.g., medical device 110 ), and authentication information.
- Additional command information 128 can be any additional information (other than medical device information 124 and device agent information 126 ) that provides commands for routing information obtained by information reader 130 .
- additional command information 128 can provide commands to device agent 140 to route information to other devices.
- command information 128 can include disassociation information (e.g., disassociate immediately, or after X seconds).
- Association information 122 is able to be read or obtained by information reader 130 via information device 120 .
- information device 120 is a barcode (static or dynamic) or an RFID tag. Accordingly, association information 122 is presented as a static barcode, a dynamic barcode or an RFID tag.
- information reader 130 e.g., a barcode reader or an RFID reader
- association information 122 is able to read or obtain association information 122 via information device 120 .
- information device 120 is attached to medical device 110 .
- a barcode or an RFID tag is physically attached (e.g., adhered) to an infusion pump.
- information device 120 is a display for rendering a scannable barcode.
- association information 122 is dynamically displayed on information device 120 .
- the display can be integrated within medical device 110 or can be separate, but proximate to, medical device 110 . It should be understood that the rendered barcode (displayed on the display) contains the association information 122 describe above.
- Device agent 140 is an agent or proxy for medical device 110 and is utilized to facilitate in the association between information reader 130 and medical device 110 .
- Device agent 140 includes information accessor 142 , router 144 , associator 146 , disassociator 148 , and optionally, proximity estimator 149 .
- Information accessor 142 is for accessing association information 122 via information reader 130 .
- Associator 146 is configured for associating medical device 110 and information reader 130 based on association information 122 .
- Disassociator 148 is for disassociating an established association between information reader 130 and medical device 110 .
- Proximity estimator 146 is for estimating a proximity or distance between medical device 110 and information reader 130 .
- Router 144 is for routing subsequent information (e.g., information from a scanned barcode on a bottle of medicine) to medical device 110 .
- information reader 130 and medical device 110 are initially unassociated. As such, any information obtained by information reader 130 would not necessarily be routed to medical device 110 .
- information reader 130 reads association information 122 .
- medical device information 124 and device agent information 126 For example, a handheld barcode scanner scans a barcode that includes the serial number of medical device 110 and the MAC address for device agent 140 .
- Information reader 130 communicates with device agent 140 in a variety of ways. In various examples, information reader 130 communicates with device agent 140 by Universal Serial Bus (USB), internet, Wi-Fi, Bluetooth, etc.
- USB Universal Serial Bus
- Information reader 130 communicates with device agent 140 by Universal Serial Bus (USB), internet, Wi-Fi, Bluetooth, etc.
- Information accessor 142 accesses association information 122 .
- Associator 150 obtains association information 122 and associates information reader 130 and medical device 110 based on association information 122 . For example, associator 150 generates an association based on the received serial number of medical device 110 and the MAC address for device agent 140 .
- associator 146 automatically generates an association in response to the obtained association information 122 . In another embodiment, associator 146 automatically generates an association in response to user input, which will be described in detail below.
- router 144 routes subsequent information obtained by information reader 130 to medical device 110 .
- batches of medication are intended to be infused into Patient A.
- Barcodes on the batches of medication are scanned by information reader 130 .
- the information from the scanned barcodes are then routed to medical device 110 (e.g., an infusion pump) to facilitate in the infusion of the drugs into Patient A.
- medical device 110 e.g., an infusion pump
- information reader 130 obtains information prior to an established association with medical device 110 .
- information reader 130 obtains information by scanning barcodes on batches of medicine for Patient A.
- the information is stored in memory 135 .
- Memory 135 can be located within information reader 130 or other locations, such as a server, within medical environment 100 .
- the association is a logical peer-to-peer association between information reader 130 and medical device 110 .
- FIG. 1 depicts an association through device agent 140 .
- the association can utilize point-to-point radio technology on a network (e.g., a local area network (LAN), a wireless LAN (WLAN), or a personal area network (PAN) (e.g., Bluetooth or Zigbee)).
- a network e.g., a local area network (LAN), a wireless LAN (WLAN), or a personal area network (PAN) (e.g., Bluetooth or Zigbee)
- PAN personal area network
- direct communication between information reader 130 and medical device 110 is established without requiring any network infrastructure.
- an acknowledgment dialog 400 is displayed on user interface 112 of medical device 110 .
- a user is prompted to accept the attempted association. If the user chooses to deny the association attempt, medical device 110 will not accept subsequent information (e.g., subsequent barcode scans) from information reader 130 , unless a new authentication is performed and accepted.
- subsequent information e.g., subsequent barcode scans
- disassociator 148 terminates or disassociates the association between information reader 130 and medical device 110 .
- provisions are added to limit the duration that the association is effective.
- a disassociation of an information reader from a medical device can be accomplished via a user interface of the information reader and/or medical device.
- Disassociation can automatically occur after a pre-determined amount of time from association. For example, a disassociation automatically occurs after four hour from the time of association.
- Disassociation can occur after a pre-determined amount of time from the last scan. For example, a disassociation automatically occurs after one hour from the last scan of the information reader.
- Disassociation can occur in response to the devices exceeding a pre-determined maximum distance.
- proximity estimator 149 estimates the proximity between information reader 130 and medical device 110 .
- medical device 110 and information reader 130 are disassociated.
- Disassociation can automatically occur in response if a connection (e.g., wireless) between the devices is lost.
- a connection e.g., wireless
- Disassociation can automatically occur in response to completed work flow. For example, disassociation occurs after successful drug scanning, and patient ID and/or clinician ID are associated with the medical device.
- Disassociation can occur if information reader reads/obtains association information of another medical device.
- medical environment 200 includes network 205 , wireless access points 207 and 208 , device agents 140 and 240 , information reader 130 , and medical devices 110 and 210 .
- Medical device 110 also includes wireless module 214 .
- Wireless module 214 allows for medical device 110 to wirelessly connect to network 205 via wireless access points 207 and/or 208 .
- medical device 110 is connected to or associated with other medical devices, such as medical device 210 .
- medical device 110 is a first Large Volume Parenterals (LVP) device and medical device 210 is a second LVP device.
- LVP Large Volume Parenterals
- medical device 210 does not have the capability to directly communicate with information reader 130 . Although two medical devices are depicted in FIG. 2 , it should be appreciated that any number of medical devices can be connected to or associated with one another.
- information reader 130 can be associated with medical device 110 in the same manner as described above.
- information 130 can also be associated with medical device 210 .
- information reader 130 reads association information 122 which is presented by medical device 110 .
- information reader 130 reads medical device information 124 which uniquely identifies medical device 210 .
- Information accessor 142 accesses association information 122 .
- Associator 150 obtains association information 122 and subsequently associates information reader 130 and medical device 210 based on association information 122 .
- router 144 routes subsequent information obtained by information reader 130 to medical device 210 .
- information reader 130 can be concurrently associated with medical devices 110 and 210 .
- medical devices 110 and 210 are to utilize device agent 240 rather than device agent 140 .
- medical devices 110 and 210 initially utilize device agent 140 .
- device agent 240 e.g., a testing device agent
- information reader 130 reads association information 122 .
- information reader 130 reads device agent information 126 which identifies device agent 240 .
- subsequent information obtained by information reader 130 is routed to medical device 110 and/or 210 via router 240 (rather than device agent 140 ).
- a device agent can optionally add functionality to the system.
- the device agent can be a physical device or virtual device agent, which has close communication with the medical devices.
- the device agent can manage the scan workflows and rules such as valid scan, valid sequence of scans, association and disassociation of barcode.
- a valid scan can include valid data in the scan, a scan supported by a medical device such as intermittent infusion or PCA infusion not supported by the device.
- a valid sequence may include scanning patient ID, clinical ID and a drug scan.
- a device agent can determine when to associate the barcode and when to disassociate the barcode.
- a device agent may perform preprocessing of the scan before sending to medical device such as mapping the drug entry ID to drug name or order ID to order details.
- the device agent will store drug library and order information.
- Medical environment 300 includes information reader 130 and medical devices 110 , 310 and 312 .
- medical device 110 includes device agent 140 .
- medical device 110 also functions as device agent 140 .
- medical device 110 , 310 and 312 are devices in a medical device rack system.
- medical device 110 acts as a proxy or device agent for medical devices 311 and 312 because medical devices 311 and 312 do not have the capability to directly communicate with information reader 130 .
- information reader 130 can be associated with medical device 310 in the same manner as described above.
- information 130 can also be associated with medical devices 311 and 312 .
- information reader 130 reads association information 122 which is presented by medical device 310 .
- information reader 130 reads medical device information 124 which uniquely identifies medical devices 311 and/or 312 .
- Information accessor 142 accesses association information 122 .
- Associator 150 obtains association information 122 and subsequently associates information reader 130 and medical devices 311 and/or 312 based on association information 122 .
- router 144 routes subsequent information obtained by information reader 130 to medical devices 311 and/or 312 .
- FIG. 5 depicts an embodiment of a method 500 for associating an information reader and a medical device.
- method 500 is carried out by processors and electrical components under the control of computer readable and computer executable instructions.
- the computer readable and computer executable instructions reside, for example, in a data storage medium such as computer usable volatile and non-volatile memory. However, the computer readable and computer executable instructions may reside in any type of computer readable storage medium.
- method 500 is performed at least by device agent 140 and/or medical device 110 , as depicted in FIG. 1 .
- association information is accessed via the information reader, wherein the information comprises medical device information for uniquely identifying the medical device, and device agent information for facilitating in an association between the medical device and the information reader.
- association information 122 is scanned by information reader 130 (e.g., barcode scanner).
- association information 122 includes medical device information 124 which is a unique signature of medical device 110 and device agent information 126 which can include agent name, connectivity parameters (e.g., IP/Bluetooth parameters), and/or commands for routing information to a specific device.
- medical device information 124 which is a unique signature of medical device 110
- device agent information 126 which can include agent name, connectivity parameters (e.g., IP/Bluetooth parameters), and/or commands for routing information to a specific device.
- association information displayed proximate the medical device is accessed.
- association information 122 is presented by information device 120 (e.g., dynamic barcode) which is physically attached to medical device 110 .
- the medical device and the information reader are associated based on the association information.
- associator 146 associates information reader 130 and medical device 110 based on association information 122 .
- a proximity is estimated between the medical device and the information reader. For example, information reader 130 and medical device 110 are disassociated in response to the devices exceeding a maximum distance. It should be understood that the proximity estimation utilized for disassociation is just one embodiment for managing disassociation. In particular, the proximity estimation is not required in all embodiments.
- subsequent information obtained via the information reader is routed to the medical device.
- router 144 routes information obtained by scanning barcodes on batches of medicine to medical device 110 .
- subsequent information obtained via the information reader is routed to another medical device, wherein the another medical device is associated with the medical device.
- router 144 routes information obtained by scanning barcodes on batches of medicine to medical devices 311 and/or 312 .
- information reader 130 obtains information and the information is stored in memory 135 .
- associator 146 establishing an association between information reader 130 and medical device 110 , the information stored in memory 135 is routed to medical device 110 .
- a disassociation occurs between the medical device and the information reader. For example, disassociation occurs in response to a lost wireless connection between medical device 110 and information reader 130 .
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Biomedical Technology (AREA)
- Primary Health Care (AREA)
- Medical Informatics (AREA)
- Epidemiology (AREA)
- Public Health (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Toxicology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Artificial Intelligence (AREA)
- Electromagnetism (AREA)
- Medicinal Chemistry (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Chemical & Material Sciences (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Tourism & Hospitality (AREA)
- Medical Treatment And Welfare Office Work (AREA)
- Accommodation For Nursing Or Treatment Tables (AREA)
- Infusion, Injection, And Reservoir Apparatuses (AREA)
- Child & Adolescent Psychology (AREA)
- Economics (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Information Transfer Between Computers (AREA)
Abstract
A device agent including an information accessor for accessing association information obtained via an information reader. The association information includes medical device information for uniquely identifying the medical device, and device agent information for facilitating in an association between the medical device and the information reader. The device agent also includes an associator for associating the medical device and the information reader based on the association information.
Description
- This application is a continuation of U.S. patent application Ser. No. 15/404,503, filed Jan. 12, 2017, which is a continuation of U.S. patent application Ser. No. 14/733,885 (now issued as U.S. Pat. No. 9,547,751), filed Jun. 8, 2015, which is a continuation of U.S. patent application Ser. No. 13/275,005 (now issued as U.S. Pat. No. 9,053,520), filed Oct. 17, 2011, each entitled “Associating An Information Reader and A Medical Device”, the contents of which are herein incorporated by reference in their entirety.
- Barcode systems are often used in medical environments to ensure safety. For example, a barcode system can ensure that correct drugs are given to the proper patient or only authorized personnel can administer the proper medical protocol to a patient.
- Oftentimes, a barcode scanner is permanently associated with a single medical device. For example, the barcode scanner is physically attached to the medical device. As a result, the flexibility of a medical environment is limited because it is difficult to share barcode scanners with other medical devices.
- Also, a floating barcode is utilized in BCMA systems. For floating barcode devices, barcode scans are sent to a centralized system. The scanning is only done to get information (e.g., device id, similar to when you scan a badge), and the information is used in backend systems to perform some general work. However, the intent and workflow, regarding the floating barcode in a BCMA system, is not for directing subsequent barcode scans to a particular device.
- Moreover, a barcode scanner may be unable to directly communicate with a medical device because of limited communication capabilities.
-
FIGS. 1-3 illustrate embodiments of a medical system. -
FIG. 4 illustrates an embodiment of displayed information. -
FIG. 5 illustrates an embodiment a method for associating an information reader and medical device. - The drawings referred to in this description should be understood as not being drawn to scale except if specifically noted.
- Reference will now be made in detail to embodiments of the present technology, examples of which are illustrated in the accompanying drawings. While the technology will be described in conjunction with various embodiment(s), it will be understood that they are not intended to limit the present technology to these embodiments. On the contrary, the present technology is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the various embodiments as defined by the appended claims.
- Furthermore, in the following description of embodiments, numerous specific details are set forth in order to provide a thorough understanding of the present technology. However, the present technology may be practiced without these specific details. In other instances, well known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present embodiments.
- In general, information readers are associated with medical devices to ensure safety in a medical environment. The discussion below will describe a variety of means to associate an information reader with medical device(s). In particular, the discussion will first describe the components in a medical environment. Then the discussion will describe functionality of the components during use of the medical environment.
- It is understood that “association,” as used herein, for example, the association between an information reader and a medical device, generally describes the communicative coupling between the devices. As a result of the association, information, obtained by the information reader, is able to be routed to the associated device(s).
-
FIG. 1 depicts an embodiment ofmedical environment 100.Medical environment 100 includesmedical device 110,information reader 130 anddevice agent 140. -
Information reader 130 is any device that is capable of reading information and also able to be associated with a medical device. For example,information reader 130 can be, but is not limited to, a barcode scanner, a radio-frequency identification (RFID) reader. Moreover,information reader 130 can be any device (e.g., a mobile device) with barcode scanning and/or RFID reading capabilities. -
Medical device 110 can be any medical device(s) that is able to be associated with an information reader. For example, medical device is a ventilator, infusion pump, etc. - In general,
association information 122 is utilized to facilitate in the association betweeninformation reader 130 andmedical device 110.Association information 122 includes medical device information 124, device agent information 126 and optionally,additional command information 128. - Also, in various embodiments,
association information 122 includes a cookie (data element) that appends to any consecutive scan after an association generated. The cookie allows the destination device (and/or routing devices) to uniquely identify scans intended for the destination device. - Medical device information 124 includes any information or signature that uniquely identifies
medical device 110 and/or any other medical devices. For example, medical device information 124 can be, but is not limited to, model number, serial number, Media Access Control address (MAC) address, Internet Protocol (IP) address, etc. - Device agent information 126 includes any information that can be utilized by device agent 140 (or any other device agent) to properly route information, obtained by
information reader 130, tomedical device 110. For example, device agent information 126 can include, but is not limited to, agent name, connectivity parameters (e.g., IP/Bluetooth parameters), commands for routing information to a specific device (e.g., medical device 110), and authentication information. -
Additional command information 128 can be any additional information (other than medical device information 124 and device agent information 126) that provides commands for routing information obtained byinformation reader 130. For example,additional command information 128 can provide commands todevice agent 140 to route information to other devices. In another example,command information 128 can include disassociation information (e.g., disassociate immediately, or after X seconds). -
Association information 122 is able to be read or obtained byinformation reader 130 viainformation device 120. In various embodiments,information device 120 is a barcode (static or dynamic) or an RFID tag. Accordingly,association information 122 is presented as a static barcode, a dynamic barcode or an RFID tag. As such, information reader 130 (e.g., a barcode reader or an RFID reader) is able to read or obtainassociation information 122 viainformation device 120. - In one embodiment,
information device 120 is attached tomedical device 110. For instance, a barcode or an RFID tag is physically attached (e.g., adhered) to an infusion pump. - In another embodiment,
information device 120 is a display for rendering a scannable barcode. In such an embodiment,association information 122 is dynamically displayed oninformation device 120. Also, the display can be integrated withinmedical device 110 or can be separate, but proximate to,medical device 110. It should be understood that the rendered barcode (displayed on the display) contains theassociation information 122 describe above. -
Device agent 140 is an agent or proxy formedical device 110 and is utilized to facilitate in the association betweeninformation reader 130 andmedical device 110.Device agent 140 includesinformation accessor 142,router 144,associator 146,disassociator 148, and optionally,proximity estimator 149. -
Information accessor 142 is for accessingassociation information 122 viainformation reader 130. -
Associator 146 is configured for associatingmedical device 110 andinformation reader 130 based onassociation information 122.Disassociator 148 is for disassociating an established association betweeninformation reader 130 andmedical device 110. -
Proximity estimator 146 is for estimating a proximity or distance betweenmedical device 110 andinformation reader 130. -
Router 144 is for routing subsequent information (e.g., information from a scanned barcode on a bottle of medicine) tomedical device 110. - During use of
medical environment 100,information reader 130 andmedical device 110 are initially unassociated. As such, any information obtained byinformation reader 130 would not necessarily be routed tomedical device 110. - In order to associate
information reader 130 andmedical device 110,information reader 130 readsassociation information 122. In particular, medical device information 124 and device agent information 126. For example, a handheld barcode scanner scans a barcode that includes the serial number ofmedical device 110 and the MAC address fordevice agent 140. -
Information reader 130 communicates withdevice agent 140 in a variety of ways. In various examples,information reader 130 communicates withdevice agent 140 by Universal Serial Bus (USB), internet, Wi-Fi, Bluetooth, etc. -
Information accessor 142accesses association information 122. Associator 150 obtainsassociation information 122 andassociates information reader 130 andmedical device 110 based onassociation information 122. For example, associator 150 generates an association based on the received serial number ofmedical device 110 and the MAC address fordevice agent 140. - In one embodiment,
associator 146 automatically generates an association in response to the obtainedassociation information 122. In another embodiment,associator 146 automatically generates an association in response to user input, which will be described in detail below. - As a result of the generated association,
router 144 routes subsequent information obtained byinformation reader 130 tomedical device 110. For example, batches of medication are intended to be infused into Patient A. Barcodes on the batches of medication are scanned byinformation reader 130. The information from the scanned barcodes are then routed to medical device 110 (e.g., an infusion pump) to facilitate in the infusion of the drugs into Patient A. - In one embodiment,
information reader 130 obtains information prior to an established association withmedical device 110. For example,information reader 130 obtains information by scanning barcodes on batches of medicine for Patient A. The information is stored inmemory 135.Memory 135 can be located withininformation reader 130 or other locations, such as a server, withinmedical environment 100. - In response to an association between
information reader 130 and medical device 110 (established by associator 146), the information (obtained prior to association) stored inmemory 135 is routed tomedical device 110. - In various embodiments, the association is a logical peer-to-peer association between
information reader 130 andmedical device 110.FIG. 1 depicts an association throughdevice agent 140. However, in various other embodiments, the association can utilize point-to-point radio technology on a network (e.g., a local area network (LAN), a wireless LAN (WLAN), or a personal area network (PAN) (e.g., Bluetooth or Zigbee)). In an embodiment of a PAN, direct communication betweeninformation reader 130 andmedical device 110 is established without requiring any network infrastructure. - Referring now to
FIG. 4 , to enhance safety and control (enabled or disabled through device configuration) anacknowledgment dialog 400 is displayed onuser interface 112 ofmedical device 110. - A user is prompted to accept the attempted association. If the user chooses to deny the association attempt,
medical device 110 will not accept subsequent information (e.g., subsequent barcode scans) frominformation reader 130, unless a new authentication is performed and accepted. - Referring again to
FIG. 1 ,disassociator 148 terminates or disassociates the association betweeninformation reader 130 andmedical device 110. In order to reduce the likelihood of undesired information to be routed to a medical device, provisions are added to limit the duration that the association is effective. - For example, a disassociation of an information reader from a medical device can be accomplished via a user interface of the information reader and/or medical device.
- Disassociation can automatically occur after a pre-determined amount of time from association. For example, a disassociation automatically occurs after four hour from the time of association.
- Disassociation can occur after a pre-determined amount of time from the last scan. For example, a disassociation automatically occurs after one hour from the last scan of the information reader.
- Disassociation can occur in response to the devices exceeding a pre-determined maximum distance. For example,
proximity estimator 149 estimates the proximity betweeninformation reader 130 andmedical device 110. In response tomedical device 110 andinformation reader 130 exceeding a pre-determined maximum distance (e.g., 40 feet),medical device 110 andinformation reader 130 are disassociated. - Disassociation can automatically occur in response if a connection (e.g., wireless) between the devices is lost.
- Disassociation can automatically occur in response to completed work flow. For example, disassociation occurs after successful drug scanning, and patient ID and/or clinician ID are associated with the medical device.
- Disassociation can occur if information reader reads/obtains association information of another medical device.
- Referring to
FIG. 2 ,medical environment 200 includesnetwork 205,wireless access points device agents information reader 130, andmedical devices -
Medical device 110 also includes wireless module 214. Wireless module 214 allows formedical device 110 to wirelessly connect to network 205 viawireless access points 207 and/or 208. - Also,
medical device 110 is connected to or associated with other medical devices, such asmedical device 210. For example,medical device 110 is a first Large Volume Parenterals (LVP) device andmedical device 210 is a second LVP device. - Moreover,
medical device 210 does not have the capability to directly communicate withinformation reader 130. Although two medical devices are depicted inFIG. 2 , it should be appreciated that any number of medical devices can be connected to or associated with one another. - During use of
medical environment 200,information reader 130 can be associated withmedical device 110 in the same manner as described above. - In one embodiment,
information 130 can also be associated withmedical device 210. In order to associateinformation reader 130 andmedical device 210,information reader 130 readsassociation information 122 which is presented bymedical device 110. In particular,information reader 130 reads medical device information 124 which uniquely identifiesmedical device 210. -
Information accessor 142accesses association information 122. Associator 150 obtainsassociation information 122 and subsequently associatesinformation reader 130 andmedical device 210 based onassociation information 122. As a result of the generated association,router 144 routes subsequent information obtained byinformation reader 130 tomedical device 210. - It should be appreciated that
information reader 130 can be concurrently associated withmedical devices - It may be desired that
medical devices device agent 240 rather thandevice agent 140. For example,medical devices device agent 140. However, for purposes of testing the medical devices, device agent 240 (e.g., a testing device agent) is utilized. - Accordingly,
information reader 130 readsassociation information 122. In particular,information reader 130 reads device agent information 126 which identifiesdevice agent 240. As a result, subsequent information obtained byinformation reader 130 is routed tomedical device 110 and/or 210 via router 240 (rather than device agent 140). - A device agent (e.g., device agent 140) can optionally add functionality to the system. The device agent can be a physical device or virtual device agent, which has close communication with the medical devices. The device agent can manage the scan workflows and rules such as valid scan, valid sequence of scans, association and disassociation of barcode. A valid scan can include valid data in the scan, a scan supported by a medical device such as intermittent infusion or PCA infusion not supported by the device. A valid sequence may include scanning patient ID, clinical ID and a drug scan.
- A device agent can determine when to associate the barcode and when to disassociate the barcode. A device agent may perform preprocessing of the scan before sending to medical device such as mapping the drug entry ID to drug name or order ID to order details. In this case, the device agent will store drug library and order information.
- Referring to
FIG. 3 , an embodiment ofmedical environment 300 is depicted.Medical environment 300 includesinformation reader 130 andmedical devices - In such an embodiment,
medical device 110 includesdevice agent 140. In other words,medical device 110 also functions asdevice agent 140. For example,medical device medical device 110 acts as a proxy or device agent formedical devices medical devices information reader 130. - During use of
medical environment 300,information reader 130 can be associated with medical device 310 in the same manner as described above. - In another embodiment,
information 130 can also be associated withmedical devices information reader 130 andmedical devices 311 and/or 312,information reader 130 readsassociation information 122 which is presented by medical device 310. In particular,information reader 130 reads medical device information 124 which uniquely identifiesmedical devices 311 and/or 312. -
Information accessor 142accesses association information 122. Associator 150 obtainsassociation information 122 and subsequently associatesinformation reader 130 andmedical devices 311 and/or 312 based onassociation information 122. As a result of the generated association,router 144 routes subsequent information obtained byinformation reader 130 tomedical devices 311 and/or 312. -
FIG. 5 depicts an embodiment of amethod 500 for associating an information reader and a medical device. In various embodiments,method 500 is carried out by processors and electrical components under the control of computer readable and computer executable instructions. The computer readable and computer executable instructions reside, for example, in a data storage medium such as computer usable volatile and non-volatile memory. However, the computer readable and computer executable instructions may reside in any type of computer readable storage medium. In some embodiments,method 500 is performed at least bydevice agent 140 and/ormedical device 110, as depicted inFIG. 1 . - At 510 of
method 500, association information is accessed via the information reader, wherein the information comprises medical device information for uniquely identifying the medical device, and device agent information for facilitating in an association between the medical device and the information reader. - For example,
association information 122 is scanned by information reader 130 (e.g., barcode scanner). In particular,association information 122 includes medical device information 124 which is a unique signature ofmedical device 110 and device agent information 126 which can include agent name, connectivity parameters (e.g., IP/Bluetooth parameters), and/or commands for routing information to a specific device. - In one embodiment, at 512, association information displayed proximate the medical device is accessed. For example,
association information 122 is presented by information device 120 (e.g., dynamic barcode) which is physically attached tomedical device 110. - At 520, the medical device and the information reader are associated based on the association information. For example, associator 146
associates information reader 130 andmedical device 110 based onassociation information 122. - At 530, a proximity is estimated between the medical device and the information reader. For example,
information reader 130 andmedical device 110 are disassociated in response to the devices exceeding a maximum distance. It should be understood that the proximity estimation utilized for disassociation is just one embodiment for managing disassociation. In particular, the proximity estimation is not required in all embodiments. - At 540, subsequent information obtained via the information reader is routed to the medical device. For example,
router 144 routes information obtained by scanning barcodes on batches of medicine tomedical device 110. - At 550, subsequent information obtained via the information reader is routed to another medical device, wherein the another medical device is associated with the medical device. For example,
router 144 routes information obtained by scanning barcodes on batches of medicine tomedical devices 311 and/or 312. - At 560, in response to the association, route previously obtained information to the medical device. For example, prior to association,
information reader 130 obtains information and the information is stored inmemory 135. Inresponse associator 146 establishing an association betweeninformation reader 130 andmedical device 110, the information stored inmemory 135 is routed tomedical device 110. - At 570, a disassociation occurs between the medical device and the information reader. For example, disassociation occurs in response to a lost wireless connection between
medical device 110 andinformation reader 130. - Various embodiments of the present invention are thus described. While the present invention has been described in particular embodiments, it should be appreciated that the present invention should not be construed as limited by such embodiments, but rather construed according to the following claims.
Claims (29)
1-20. (canceled)
21. An apparatus comprising:
at least one data processor; and
at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one data processor, cause the apparatus to at least:
receive, during a scan sequence, patient information after an information reader scans a patient identifier associated with a patient, wherein the patient information identifies the patient;
receive, during the scan sequence, medication information after the information reader scans a medication barcode on medication to be administered to the patient by an infusion pump;
cause, during the scan sequence, a scannable tag to be displayed on a display of an infusion pump, wherein scanning of the scannable tag is configured to enable the infusion pump to receive the patient information and the medication information after the information reader scans the patient identifier and the medication barcode; and
cause, after completion of the scan sequence, operation of the infusion pump based on at least one of the patient information and the medication information.
22. The apparatus of claim 21 , wherein the at least one memory and the computer program code are further configured to, with the at least one data processor, cause the infusion pump to:
store the medication information in the at least one memory; and
render, on the display of the infusion pump, at least a portion of the medication information.
23. The apparatus of claim 21 , wherein the scannable tag further comprises routing information defining parameters for routing the medication information to the infusion pump.
24. The apparatus of claim 23 , wherein the routing information comprises at least one of: connectivity parameters of the infusion pump or authentication information of the infusion pump.
25. The apparatus of claim 21 , wherein the scannable tag is configured to provide medical device information uniquely identifying the infusion pump.
26. The apparatus of claim 25 , wherein the medical device information uniquely identifying the infusion pump comprises at least one of: a model number of the infusion pump, a serial number of the infusion pump, a media access control address of the infusion pump, or an internet protocol address of the infusion pump.
27. The apparatus of claim 21 , wherein the scannable tag comprises a barcode.
28. The apparatus of claim 27 , wherein the barcode is at least one of a static barcode and a dynamic barcode.
29. The apparatus of claim 21 , wherein the at least one memory and the computer program code are further configured to, with the at least one data processor, cause the infusion pump to:
connect to a communication network;
receive, from a server connected to the communication network and after scanning of the scannable tag, a request for communicative coupling with the infusion pump; and
render, on the display, a dialog to acknowledge the request.
30. The apparatus of claim 29 , further comprising a wireless module, and wherein causing the infusion pump to connect to the communication network comprises communicating, via the wireless module, with a wireless network.
31. The apparatus of claim 21 , wherein the at least one memory and the computer program code are further configured to, with the at least one data processor, cause the infusion pump to administer a parenteral infusion of at least 100 mL of fluid from a container.
32. The apparatus of claim 21 , wherein the apparatus receives operational information related to operation of the apparatus from a processing unit coupled to the apparatus based on the information reader obtaining the operational information and the processing unit verifying an association between the apparatus and the information reader.
33. The apparatus of claim 32 , wherein the operational information comprises an identifier for the apparatus.
34. The apparatus of claim 32 , wherein the operational information comprises medication and/or infusion instructions.
35. The apparatus of claim 21 , wherein the apparatus comprises the infusion pump.
36. An infusion system for medication infusion within a medical environment, the infusion system comprising:
a display;
an infusion pump;
a scannable tag presentable via the display;
at least one data processor; and
at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one data processor, cause the infusion system to at least:
receive, during a scan sequence, the patient information after an information reader scans a patient identifier associated with a patient, wherein the patient information identifies the patient;
receive, during the scan sequence, the medication information after the information reader scans a medication barcode on medication to be administered to the patient by the infusion pump;
cause, during the scan sequence after the information reader scans the patient identifier and the medication barcode, the scannable tag to be displayed on the display, wherein scanning of the scannable tag is configured to enable the infusion pump to receive the patient information and the medication information; and
cause, after completion of the scan sequence, operation of the infusion pump based on at least one of the patient information and the medication information.
37. The infusion system of claim 36 , wherein the at least one memory and the computer program code are further configured to, with the at least one data processor, cause the infusion system to:
store the medication information in the at least one memory; and
render, on the display, at least a portion of the medication information.
38. The infusion system of claim 36 , wherein scanning of the scannable tag configures the infusion pump with routing information defining parameters for routing the medication information to the infusion pump.
39. The infusion system of claim 38 , wherein the routing information comprises at least one of: connectivity parameters of the infusion pump or authentication information of the infusion pump.
40. The infusion system of claim 36 , wherein scanning of the scannable tag causes unique identification of the infusion pump based on medical device information.
41. The infusion system of claim 40 , wherein the medical device information uniquely identifying the infusion pump comprises at least one of: a model number of the infusion pump, a serial number of the infusion pump, a media access control address of the infusion pump, or an internet protocol address of the infusion pump.
42. The infusion system of claim 36 , wherein the scannable tag comprises a barcode.
43. The infusion system of claim 42 , wherein the barcode is at least one of a static barcode and a dynamic barcode.
44. The infusion system of claim 36 , wherein the at least one memory and the computer program code are further configured to, with the at least one data processor, cause the infusion pump to:
connect to a communication network;
receive, from a server connected to the communication network and after scanning of the scannable tag, a request for communicative coupling with the infusion pump; and
render, on the display, a dialog to acknowledge the request.
45. The infusion system of claim 44 , further comprising a wireless module, and wherein causing the infusion pump to connect to the communication network comprises communicating, via the wireless module, with a wireless network.
46. The infusion system of claim 36 , wherein the at least one memory and the computer program code are further configured to, with the at least one data processor, cause the infusion pump to administer a parenteral infusion of at least 100 mL of fluid from a container.
47. The infusion system of claim 36 , wherein the infusion system receives operational information related to operation of the infusion pump from a processing unit coupled to the infusion system based on the information reader obtaining the operational information and the processing unit verifying an association between the infusion pump and the information reader.
48. The infusion system of claim 47 , wherein the operational information comprises at least one of an identifier for the infusion pump, medication instructions, and infusion instructions.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/358,380 US20240021283A1 (en) | 2011-10-17 | 2023-07-25 | Barcode safety and control of a medical device |
Applications Claiming Priority (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/275,005 US9053520B2 (en) | 2011-10-17 | 2011-10-17 | Associating an information reader and a medical device |
US14/733,885 US9547751B2 (en) | 2011-10-17 | 2015-06-08 | Associating an information reader and a medical device |
US15/404,503 US9996676B2 (en) | 2011-10-17 | 2017-01-12 | Associating an information reader and a medical device |
US15/979,184 US10418130B2 (en) | 2011-10-17 | 2018-05-14 | Associating an information reader and a medical device |
US16/570,604 US11581078B2 (en) | 2011-10-17 | 2019-09-13 | Associating an information reader and a medical device |
US18/109,202 US11901058B2 (en) | 2011-10-17 | 2023-02-13 | Associating an information reader and a medical device |
US18/358,380 US20240021283A1 (en) | 2011-10-17 | 2023-07-25 | Barcode safety and control of a medical device |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/109,202 Continuation US11901058B2 (en) | 2011-10-17 | 2023-02-13 | Associating an information reader and a medical device |
Publications (1)
Publication Number | Publication Date |
---|---|
US20240021283A1 true US20240021283A1 (en) | 2024-01-18 |
Family
ID=48085325
Family Applications (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/275,005 Active US9053520B2 (en) | 2011-10-17 | 2011-10-17 | Associating an information reader and a medical device |
US14/733,885 Active US9547751B2 (en) | 2011-10-17 | 2015-06-08 | Associating an information reader and a medical device |
US15/404,503 Active US9996676B2 (en) | 2011-10-17 | 2017-01-12 | Associating an information reader and a medical device |
US15/979,184 Active US10418130B2 (en) | 2011-10-17 | 2018-05-14 | Associating an information reader and a medical device |
US16/570,604 Active US11581078B2 (en) | 2011-10-17 | 2019-09-13 | Associating an information reader and a medical device |
US17/400,734 Active US11289180B2 (en) | 2011-10-17 | 2021-08-12 | Medical device with information reader |
US18/109,202 Active US11901058B2 (en) | 2011-10-17 | 2023-02-13 | Associating an information reader and a medical device |
US18/358,380 Pending US20240021283A1 (en) | 2011-10-17 | 2023-07-25 | Barcode safety and control of a medical device |
Family Applications Before (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/275,005 Active US9053520B2 (en) | 2011-10-17 | 2011-10-17 | Associating an information reader and a medical device |
US14/733,885 Active US9547751B2 (en) | 2011-10-17 | 2015-06-08 | Associating an information reader and a medical device |
US15/404,503 Active US9996676B2 (en) | 2011-10-17 | 2017-01-12 | Associating an information reader and a medical device |
US15/979,184 Active US10418130B2 (en) | 2011-10-17 | 2018-05-14 | Associating an information reader and a medical device |
US16/570,604 Active US11581078B2 (en) | 2011-10-17 | 2019-09-13 | Associating an information reader and a medical device |
US17/400,734 Active US11289180B2 (en) | 2011-10-17 | 2021-08-12 | Medical device with information reader |
US18/109,202 Active US11901058B2 (en) | 2011-10-17 | 2023-02-13 | Associating an information reader and a medical device |
Country Status (5)
Country | Link |
---|---|
US (8) | US9053520B2 (en) |
EP (1) | EP2769338A4 (en) |
AU (1) | AU2012326376B2 (en) |
CA (1) | CA2851629C (en) |
WO (1) | WO2013059139A1 (en) |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10089443B2 (en) | 2012-05-15 | 2018-10-02 | Baxter International Inc. | Home medical device systems and methods for therapy prescription and tracking, servicing and inventory |
US20140155827A1 (en) * | 2012-12-03 | 2014-06-05 | Mylan, Inc. | Medicament information system and method |
US9692829B2 (en) | 2012-12-03 | 2017-06-27 | Mylan Inc. | Medication delivery system and method |
US9179260B2 (en) | 2012-12-03 | 2015-11-03 | Mylan Inc. | Medicament information system and method |
GB2523512A (en) | 2012-12-27 | 2015-08-26 | Kaleo Inc | Devices, systems and methods for locating and interacting with medicament delivery systems |
US9968739B2 (en) | 2013-03-14 | 2018-05-15 | Carefusion 303, Inc. | Rotary valve for a disposable infusion set |
US9522224B2 (en) * | 2013-03-14 | 2016-12-20 | Carefusion 303, Inc. | Inductively powered modular medical device system |
US10226571B2 (en) | 2013-03-14 | 2019-03-12 | Carefusion 303, Inc. | Pump segment placement |
US9468714B2 (en) | 2013-03-14 | 2016-10-18 | Carefusion 303, Inc. | Memory and identification associated with IV set |
US9962485B2 (en) * | 2013-12-30 | 2018-05-08 | Cerner Innovation, Inc. | Automatically disassociating medical devices from patients |
ES2780929T3 (en) | 2014-01-29 | 2020-08-27 | Mary Reaston | System for establishing a wireless connection |
US20150223278A1 (en) * | 2014-02-03 | 2015-08-06 | Mary Reaston | System and Method for Establishing a Wireless Connection |
US11074632B2 (en) * | 2016-04-20 | 2021-07-27 | Toshiba Global Commerce Solutions Holdings Corporation | Method and system for associating multiple persons with a virtual transaction in an environment |
US10318714B2 (en) * | 2016-11-01 | 2019-06-11 | Cerner Innovation, Inc. | Insulin pen smart administration and teaching device |
US11177026B2 (en) | 2018-05-11 | 2021-11-16 | Baxter International Inc. | Medical device data back-association system, apparatuses, and methods |
US11335452B2 (en) | 2019-12-19 | 2022-05-17 | Cerner Innovation, Inc. | Enabling the use of multiple picture archiving communication systems by one or more facilities on a shared domain |
Family Cites Families (46)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4476381A (en) * | 1982-02-24 | 1984-10-09 | Rubin Martin I | Patient treatment method |
US6850252B1 (en) * | 1999-10-05 | 2005-02-01 | Steven M. Hoffberg | Intelligent electronic appliance system and method |
US20030173405A1 (en) | 2000-01-12 | 2003-09-18 | Metrologic Instruments, Inc. | Bar code symbol driven systems for accessing information resources on the internet |
IL141941A0 (en) | 1998-09-11 | 2002-03-10 | Digital Convergence Corp | Method for interfacing scanned product information with a source for the product over a global network |
US6519569B1 (en) * | 1999-12-01 | 2003-02-11 | B. Braun Medical, Inc. | Security infusion pump with bar code reader |
US6877661B2 (en) | 2000-08-16 | 2005-04-12 | Richard M. Webb | Scannable barcode display and methods for using the same |
US7262685B2 (en) | 2000-12-11 | 2007-08-28 | Asap Automation, Llc | Inventory system with barcode display |
US6985870B2 (en) | 2002-01-11 | 2006-01-10 | Baxter International Inc. | Medication delivery system |
US8775196B2 (en) | 2002-01-29 | 2014-07-08 | Baxter International Inc. | System and method for notification and escalation of medical data |
US20030140928A1 (en) | 2002-01-29 | 2003-07-31 | Tuan Bui | Medical treatment verification system and method |
US20030144878A1 (en) | 2002-01-29 | 2003-07-31 | Wilkes Gordon J. | System and method for providing multiple units of measure |
US20030140929A1 (en) | 2002-01-29 | 2003-07-31 | Wilkes Gordon J. | Infusion therapy bar coding system and method |
US7698156B2 (en) | 2002-01-29 | 2010-04-13 | Baxter International Inc. | System and method for identifying data streams associated with medical equipment |
US20030141981A1 (en) | 2002-01-29 | 2003-07-31 | Tuan Bui | System and method for operating medical devices |
US20040176667A1 (en) | 2002-04-30 | 2004-09-09 | Mihai Dan M. | Method and system for medical device connectivity |
US20040172301A1 (en) | 2002-04-30 | 2004-09-02 | Mihai Dan M. | Remote multi-purpose user interface for a healthcare system |
US20050065817A1 (en) | 2002-04-30 | 2005-03-24 | Mihai Dan M. | Separation of validated information and functions in a healthcare system |
US8234128B2 (en) | 2002-04-30 | 2012-07-31 | Baxter International, Inc. | System and method for verifying medical device operational parameters |
US20040167804A1 (en) | 2002-04-30 | 2004-08-26 | Simpson Thomas L.C. | Medical data communication notification and messaging system and method |
US20050055242A1 (en) | 2002-04-30 | 2005-03-10 | Bryan Bello | System and method for medical data tracking, analysis and reporting for healthcare system |
US20040167465A1 (en) | 2002-04-30 | 2004-08-26 | Mihai Dan M. | System and method for medical device authentication |
AU2004225145B2 (en) * | 2003-03-28 | 2010-05-20 | Carefusion 303, Inc. | Infusion data communication system |
US6994249B2 (en) * | 2003-05-27 | 2006-02-07 | Cardinal Health Technologies, Llc | System and method for drug management utilizing transferable labels |
US20050055244A1 (en) | 2003-07-18 | 2005-03-10 | Janet Mullan | Wireless medical communication system and method |
US20050108057A1 (en) | 2003-09-24 | 2005-05-19 | Michal Cohen | Medical device management system including a clinical system interface |
US20050149350A1 (en) * | 2003-12-24 | 2005-07-07 | Kerr Roger S. | Patient information management system and method |
US8185411B2 (en) * | 2004-02-17 | 2012-05-22 | International Business Machines Corporation | Method, system, and apparatus for patient controlled access of medical records |
US8961461B2 (en) | 2004-05-27 | 2015-02-24 | Baxter International Inc. | Multi-state alarm system for a medical pump |
US8058986B2 (en) * | 2004-11-12 | 2011-11-15 | Koninklijke Philips Electronics N.V. | Method for automatic association devices to a patient and concurrent creation of a patient record |
US7945452B2 (en) * | 2005-04-11 | 2011-05-17 | Hospira, Inc. | User interface improvements for medical devices |
US20070145137A1 (en) | 2005-12-27 | 2007-06-28 | Mrowiec Zbigniew R | Systems and methods for processing measurement data |
US7839266B2 (en) * | 2006-05-15 | 2010-11-23 | Linksense, Inc. | System and method for managing point of care assignments |
JP2007310759A (en) | 2006-05-22 | 2007-11-29 | Daikoku:Kk | Medical equipment management device and medical equipment management method |
US20070300063A1 (en) * | 2006-06-23 | 2007-12-27 | Research In Motion Limited | Pairing to a Wireless Peripheral Device at the Lock-Screen |
US8025634B1 (en) | 2006-09-18 | 2011-09-27 | Baxter International Inc. | Method and system for controlled infusion of therapeutic substances |
CA2571666A1 (en) | 2006-12-12 | 2008-06-12 | Diversinet Corp. | Secure identity and personal information storage and transfer |
US7434724B2 (en) | 2006-12-22 | 2008-10-14 | Welch Allyn, Inc. | Dynamic barcode for displaying medical data |
US20080221930A1 (en) * | 2007-03-09 | 2008-09-11 | Spacelabs Medical, Inc. | Health data collection tool |
US20080303638A1 (en) * | 2007-03-24 | 2008-12-11 | Hap Nguyen | Portable patient devices, systems, and methods for providing patient aid and preventing medical errors, for monitoring patient use of ingestible medications, and for preventing distribution of counterfeit drugs |
US8257337B2 (en) * | 2007-05-02 | 2012-09-04 | Carefusion 303, Inc. | Intravenous fluid container |
US20100169120A1 (en) | 2008-12-31 | 2010-07-01 | Cerner Innovation, Inc. | Patient to device association |
US8172798B2 (en) | 2009-05-12 | 2012-05-08 | Sigma International General Medical Apparatus LLC | System and method for managing infusion therapies |
JP2011065481A (en) | 2009-09-17 | 2011-03-31 | Terumo Corp | Medical device communication management system |
US8894631B2 (en) | 2010-03-24 | 2014-11-25 | Baxter International Inc. | Multiple drug infusion system and method |
US9561322B2 (en) * | 2011-01-06 | 2017-02-07 | Carefusion 303, Inc. | Integrated infusion pump and container |
US9213928B2 (en) | 2011-10-19 | 2015-12-15 | Cerner Innovation, Inc. | Bar-code assignment system for medical and other uses |
-
2011
- 2011-10-17 US US13/275,005 patent/US9053520B2/en active Active
-
2012
- 2012-10-15 EP EP12842373.8A patent/EP2769338A4/en not_active Ceased
- 2012-10-15 CA CA2851629A patent/CA2851629C/en active Active
- 2012-10-15 WO PCT/US2012/060303 patent/WO2013059139A1/en active Application Filing
- 2012-10-15 AU AU2012326376A patent/AU2012326376B2/en active Active
-
2015
- 2015-06-08 US US14/733,885 patent/US9547751B2/en active Active
-
2017
- 2017-01-12 US US15/404,503 patent/US9996676B2/en active Active
-
2018
- 2018-05-14 US US15/979,184 patent/US10418130B2/en active Active
-
2019
- 2019-09-13 US US16/570,604 patent/US11581078B2/en active Active
-
2021
- 2021-08-12 US US17/400,734 patent/US11289180B2/en active Active
-
2023
- 2023-02-13 US US18/109,202 patent/US11901058B2/en active Active
- 2023-07-25 US US18/358,380 patent/US20240021283A1/en active Pending
Also Published As
Publication number | Publication date |
---|---|
US20230360757A1 (en) | 2023-11-09 |
US9996676B2 (en) | 2018-06-12 |
EP2769338A4 (en) | 2015-05-20 |
WO2013059139A1 (en) | 2013-04-25 |
AU2012326376A1 (en) | 2014-04-24 |
US9547751B2 (en) | 2017-01-17 |
US11901058B2 (en) | 2024-02-13 |
US20180330809A1 (en) | 2018-11-15 |
US20170193188A1 (en) | 2017-07-06 |
US20130092728A1 (en) | 2013-04-18 |
US10418130B2 (en) | 2019-09-17 |
US20200005923A1 (en) | 2020-01-02 |
EP2769338A1 (en) | 2014-08-27 |
US11581078B2 (en) | 2023-02-14 |
US20210375417A1 (en) | 2021-12-02 |
US20150269333A1 (en) | 2015-09-24 |
US11289180B2 (en) | 2022-03-29 |
AU2012326376B2 (en) | 2017-06-29 |
CA2851629A1 (en) | 2013-04-25 |
US9053520B2 (en) | 2015-06-09 |
CA2851629C (en) | 2020-04-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20240021283A1 (en) | Barcode safety and control of a medical device | |
CN105308646B (en) | Utilize the system and method for associated medical device management | |
US20220037011A1 (en) | Location-based reconfiguration of infusion pump settings | |
EP2767951B1 (en) | Information processing device, method and program | |
US20140089011A1 (en) | Medication Management System | |
US20160162705A1 (en) | Apparatus and method for managing health data | |
KR20100122978A (en) | Apparatus and method for providing service based on location in mibile communication system | |
JP2009110421A (en) | Information providing system | |
GB2547453A (en) | Secure data access | |
KR101743914B1 (en) | Method for delivering prescription using mobile device and mobile device | |
CN106330933A (en) | Intelligent medicine fetching method and system | |
KR20150134555A (en) | System and method for patient medical treatment | |
US20240107312A1 (en) | Reader initiated provisioning | |
KR20220002077A (en) | Reception application for prescription based on identification code, system and method for managing phamacy | |
JP2002163365A (en) | Prescription receiving system, medical institution server, prescription receiving method and recording medium with prescription receiving program recorded thereon | |
KR20200013166A (en) | Prescription delivery system using two-channel in cloud computing environment and the control method thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |