US20200188587A1 - Assemblies, Systems and Methods for Programming Medical Devices - Google Patents

Assemblies, Systems and Methods for Programming Medical Devices Download PDF

Info

Publication number
US20200188587A1
US20200188587A1 US16/630,464 US201816630464A US2020188587A1 US 20200188587 A1 US20200188587 A1 US 20200188587A1 US 201816630464 A US201816630464 A US 201816630464A US 2020188587 A1 US2020188587 A1 US 2020188587A1
Authority
US
United States
Prior art keywords
medical device
data
data connector
medical
programming
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US16/630,464
Other languages
English (en)
Inventor
Andrew Sluggett
Danny Djurasevich
Paul Crockett
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.)
Infusion Innovations Pty Ltd
Original Assignee
Infusion Innovations Pty Ltd
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
Priority claimed from AU2017902740A external-priority patent/AU2017902740A0/en
Application filed by Infusion Innovations Pty Ltd filed Critical Infusion Innovations Pty Ltd
Publication of US20200188587A1 publication Critical patent/US20200188587A1/en
Assigned to INFUSION INNOVATIONS PTY LTD reassignment INFUSION INNOVATIONS PTY LTD ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CROCKETT, PAUL, DJURASEVICH, Danny, SLUGGETT, Andrew
Abandoned legal-status Critical Current

Links

Images

Classifications

    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
    • A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
    • A61M5/168—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body
    • A61M5/172—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body electrical or electronic
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
    • A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
    • A61M5/142—Pressure infusion, e.g. using pumps
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
    • A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
    • A61M5/142—Pressure infusion, e.g. using pumps
    • A61M5/14244—Pressure infusion, e.g. using pumps adapted to be carried by the patient, e.g. portable on the body
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
    • A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
    • A61M5/168—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body
    • A61M5/16877—Adjusting flow; Devices for setting a flow rate
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • 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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0894—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
    • H04L9/0897—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage involving additional devices, e.g. trusted platform module [TPM], smartcard or USB
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
    • A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
    • A61M5/142—Pressure infusion, e.g. using pumps
    • A61M2005/14208—Pressure infusion, e.g. using pumps with a programmable infusion control system, characterised by the infusion program
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00—General characteristics of the apparatus
    • A61M2205/18—General characteristics of the apparatus with alarm
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00—General characteristics of the apparatus
    • A61M2205/35—Communication
    • A61M2205/3546—Range
    • A61M2205/3561—Range local, e.g. within room or hospital
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00—General characteristics of the apparatus
    • A61M2205/35—Communication
    • A61M2205/3546—Range
    • A61M2205/3569—Range sublocal, e.g. between console and disposable
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00—General characteristics of the apparatus
    • A61M2205/35—Communication
    • A61M2205/3576—Communication with non implanted data transmission devices, e.g. using external transmitter or receiver
    • A61M2205/3584—Communication with non implanted data transmission devices, e.g. using external transmitter or receiver using modem, internet or bluetooth
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00—General characteristics of the apparatus
    • A61M2205/50—General characteristics of the apparatus with microprocessors or computers
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00—General characteristics of the apparatus
    • A61M2205/50—General characteristics of the apparatus with microprocessors or computers
    • A61M2205/52—General characteristics of the apparatus with microprocessors or computers with memories providing a history of measured variating parameters of apparatus or patient
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00—General characteristics of the apparatus
    • A61M2205/60—General characteristics of the apparatus with identification means
    • A61M2205/6009—General characteristics of the apparatus with identification means for matching patient with his treatment, e.g. to improve transfusion security
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2207/00—Methods of manufacture, assembly or production
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/80—Wireless
    • H04L2209/805—Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/88—Medical equipments

Definitions

  • Assistive and diagnostic medical devices such as prostheses, electrocardiographs, blood pressure monitors, MRI scanners, catheters, pacemakers, and dialysis machines have been used for decades to diagnose and alleviate various medical conditions.
  • These medical conditions may include acute medical conditions such as infections, myocardial infarction and the like, as well as chronic medical conditions such as diabetes, arthritis, cancer and others.
  • ambulatory infusion pumps provide the added advantage of patient treatment in specialised clinics, in home or as hospital outpatients.
  • Ambulatory infusion pumps are generally smaller than stationary infusion pumps and are either mechanically driven pumps or battery fuelled, electrically driven pumps, with mechanical elastomeric pump still the most common choice for ambulatory infusions.
  • a number of variables can alter the flow rate administered via elastomeric pumps. Hypobaric conditions can decrease infusion rate (Mizuuchi, M and Namiki, A, 2003), variations in temperature, viscosity, duration of storage, back pressure, atmospheric pressure and partial filling can affect flow rate (Skryabina, E A and Dunn, T S, 2006; Irish Medicines Board, 2008) and overfilling or underfilling the balloon can also vary the infusion rate. Indeed, the partial filling of elastomerics results in reported delivery rate inaccuracies of up to 34% (Skryabina, E A and Dunn, T S, 2006).
  • elastomeric infusion pumps are still widely used as they are simple to operate and therefore offer reliability of functioning over accuracy or consistency of dosage. They are simple, inexpensive, single use, disposable devices.
  • Infusion pumps offer much greater accuracy than elastomeric infusion pumps. They have been estimated to have a general accuracy of +/ ⁇ 3-6%. They generally comprise a pump mechanism, such as a peristaltic pump. Peristaltic mechanisms may be linear or rotary and comprise a set of moving fingers, rollers or cams which section off a volume of fluid and propel it through the patient's administration set. The rate of delivery of fluid to the patient is controlled by the size of the fingers, rollers or cams, by restrictors or other flow rate adjustors added to the system, and the speed at which the fingers, rollers or cams move.
  • a pump mechanism such as a peristaltic pump.
  • Peristaltic mechanisms may be linear or rotary and comprise a set of moving fingers, rollers or cams which section off a volume of fluid and propel it through the patient's administration set. The rate of delivery of fluid to the patient is controlled by the size of the fingers, rollers or cams, by restrictors or other flow rate adjustors added to the system, and
  • Smart pumps are not being programmed to provide hard alerts, therefore, it has been easy for carers to override alerts or bypass a drug library. In many cases, poor carer compliance arising from the complexity of smart pump operation overrides the many advantages offered by smart pump decision support.
  • detected data streams may offer the ability to better monitor patient outcomes and if required, adapt treatment regimes.
  • embodiments of the invention relate to medical device programming assemblies for programming a medical treatment parameter on a medical device configured to receive a programming key comprising; a programming key adapted to mate with the medical device further comprising, a programmable, non-transitory, computer readable storage device comprising a data connector wherein the data connector is configured to mate with a corresponding data connector on the medical device, the storage device affixed to a fastener coupling configured to mate with a corresponding coupling on the medical device when the data connector is brought into proximity with the corresponding data connector on the medical device, wherein the programming key is configured to occupy a space formed within the medical device when the data connector and fastener coupling are mated with the corresponding data connector and fastener coupling on the medical device.
  • Medical device programming assemblies may comprise a data hub device adapted to receive data transmitted from the medical device, and adapted to store the data, process the data or communicate the data to the same or another electronic device.
  • Medical device programming assemblies may further comprise; a medical device comprising, a central processing unit, and a storage device reader wherein the medical device is configured to define a space for receiving the programming key when the data connector and fastener coupling on the medical device are mated with the corresponding data connector and fastener coupling of the programming key.
  • the data hub device may comprise a server or a router.
  • Certain embodiments may relate to methods of manufacturing medical device programming assemblies. Such methods may comprise the steps of; obtaining a programmable, non-transitory, computer readable storage device comprising a data connector wherein the data connector is configured to mate with a corresponding data connector on the medical device, programming the programmable, non-transitory, computer readable storage device to encode one or more medical treatment parameters for operating the medical device, and affixing the storage device to a fastener coupling configured to mate with a corresponding coupling on the medical device when the data connector is brought into proximity with the corresponding data connector on the medical device.
  • Certain methods may also comprise the step of programming the programmable, non-transitory, computer readable storage device and the subsequent step of rendering the medical treatment parameter substantially non-editable.
  • embodiments of the invention may relate to systems for programming a medical treatment parameter on a medical device configured to receive a programming key comprising; a programming key adapted to mate with the medical device further comprising, a programmable, non-transitory, computer readable storage device comprising a data connector wherein the data connector is configured to mate with a corresponding data connector on the medical device, the storage device affixed to a fastener coupling configured to mate with a corresponding coupling on the medical device when the data connector is brought into proximity with the corresponding data connector on the medical device, wherein the programming key is configured to occupy a space formed within the medical device when the data connector and fastener coupling are mated with the corresponding data connector and fastener coupling on the medical device.
  • Certain systems may comprise a data hub device adapted to receive data transmitted from the medical device, and store the data, process the data or communicate the data to the same or another electronic device.
  • Others may comprise; a medical device comprising, a central processing unit, and a storage device reader wherein the medical device is configured to define a space for receiving the programming key when the data connector and fastener coupling on the medical device are mated with the corresponding data connector and fastener coupling of the programming key.
  • systems may be characterised wherein; the programmable, non-transitory, computer readable storage device is affixed to a fastener coupling, and the medical device comprises, an opening adapted to receive the programmable, non-transitory, computer readable storage device, and a fastener coupling adapted to receive and secure to the fastener coupling.
  • embodiments of the invention may relate to methods for the transfer of data from a programmable, non-transitory, computer readable storage device to a data hub device comprising the steps of; obtaining a programming key further comprising, a programmable, non-transitory, computer readable storage device encoding a medical treatment parameter for operating a medical device, further comprising a data connector wherein the data connector is configured to mate with a corresponding data connector on the medical device, obtaining the medical device further comprising, a central processing unit, and a storage device reader comprising a data connector wherein the data connector is configured to mate with a corresponding data connector on the storage device, mating the storage device data connector with the medical device data connector, communicating the medical treatment parameter to the medical device, and communicating the medical treatment parameter from the medical device to the data hub device.
  • Methods may comprise the further step of communicating the medical treatment parameter to the medical device, followed by the step of sensing a medical treatment parameter during or following the medical treatment, and the step of communicating the medical treatment parameter from the medical device to the data hub device further comprising the step of communicating the sensed medical treatment parameter to the data hub device.
  • Other embodiments may relate to methods for the transfer of data from a programmable, non-transitory, computer readable storage device to a data hub device comprising the steps of; obtaining a programmable, non-transitory, computer readable storage device wherein the storage device comprises, a substantially non-editable, computer readable program encoding a medical treatment parameter for a medical treatment, obtaining a medical device comprising, a central processing unit, and a storage device reader for receiving the substantially non-editable program, communicating the program to the storage device reader, decoding the medical treatment parameter for a medical treatment from the substantially non-editable program using the central processing unit, conducting the medical treatment in accordance with the set parameters using the medical device, monitoring a medical treatment parameter, communicating data arising from the monitoring of the medical treatment parameter from the medical device to a data hub device, receiving the data transmitted from the medical device at the data hub device, and storing the data at the data hub device or communicating the data from the data hub device to other electronic devices.
  • the storage device comprises, a substantially non
  • the fastener coupling affixed to the computer readable storage device may comprise one or more clips or catches at the perimeter of the fastener coupling.
  • the fastener coupling may be composed of a polymeric material, preferably a moulded plastic or a silicon composite material, and may present in the form of a sliding fastener, a fixed clip or a threaded screw that may be used to secure the computer readable storage device in position.
  • the fastener coupling may be shaped to form a handle or gripping surface to aid the insertion of the computer readable storage device into the space formed within the medical device. It may additionally comprise a surface for printing information relating to the computer readable storage device, for instance, the flow rate of the medical treatment parameter.
  • a fastener formed by bringing together corresponding mating portions of the programming key fastener coupling and the medical device fastener coupling, may protect the internal components of the medical device from damage (for example, damage caused by dust or moisture).
  • the fastener may create a seal between the mating portions of the programming key fastener coupling and the medical device fastener coupling.
  • the seal is preferably splash proof, allowing the user to wear the medical device in wet environments, when the programming key is engaged with the medical device.
  • the medical device is preferably a wearable medical device thus, the exterior surface of the programming key is preferably continuous with the exterior surface of the medical device when the programming key is engaged with the medical device. This may occur, for instance, while inserting the computer readable storage device in the opening within the infusion pump, that receives the computer readable storage device. This creates an aesthetically appealing finish to the medical device, as well as providing comfort to the user.
  • the fastener may form a substantially non-releasable fastening. This may render the assemblies or systems described herein substantially non-tamperable. It may help to secure the programming of the medical treatment parameter by ensuring that the encoded medical treatment parameter for the medical treatment cannot be unintentionally ceased or altered by removing the storage device.
  • a substantially non-releasable mating arrangement may be formed between the storage device data connector and the medical device data connector. Such an engagement may also establish a non-tamperable engagement between the programming key and the medical device, presenting an alternative to the non-tamperable feature of the non-releasable fastener couplings.
  • a substantially non-releasable fastening may also comprise a fracturable or breakable portion of the computer readable storage device.
  • the fastening may be rendered non-releasable by fracturing the fracturable or breakable portion of the computer readable storage device once the storage device has been inserted in the medical device opening, such that the storage device remains stuck in the medical device and cannot be grasped to be removed.
  • the fracturable or breakable portion may be defined by a weakening in the storage device or fastener coupling.
  • the fracturable or breakable portion provides a gripping portion of the computer readable storage device such that it can be manipulated using the gripping portion until the gripping portion is fractured and removed.
  • embodiments may comprise a programming key comprising a printed circuit board, a data connector, a storage device and a fastener coupling.
  • the programming key takes the form of a resistor-based device which simply completes a broken circuit within the medical device.
  • an external power source is typically not required, as the programmed parameter is passively received by the medical device or may utilise the power source provided by the medical device.
  • infusions are limited in the duration of infusion and the viscosity of the liquid that can be infused.
  • the fastener coupling may comprise a tongue and groove sliding fastener.
  • the sliding fastener may comprise a substantially planar portion and a tongue or groove portioned formed at one or more edges of the planar portion, wherein the tongue or groove is configured to mate with a corresponding tongue or groove partially defining the space within the medical device.
  • Embodiments may comprise a substantially planar portion formed of the same material as the medical device, for instance polymeric materials or silicone composite materials.
  • the planar portion may be formed in the shape of a corresponding opening or ‘cut-out’ through an exterior housing of the medical device.
  • the substantially planar portion and opening are preferably rectangular in shape with two substantially parallel edges of the planar portion having a tongue formed therein.
  • a corresponding pair of substantially parallel grooves may be formed in two substantially parallel edges formed in the opening of the medical device housing.
  • a priming sequence or an infusion is initiated once the programming key is engaged with the medical device.
  • the sliding fastener may comprise a locking means configured to engage with a corresponding means on the medical device to secure the sliding fastener in position when the data connector and fastener coupling are mated with the corresponding data connector and fastener coupling on the medical device.
  • the pair of substantially parallel tongues on the sliding fastener may terminate in a hook corresponding with the pair of substantially parallel grooves on the medical device which terminate in a pair of wider openings, such that, when engaged the terminal hooks are locked in position in the wider openings of the grooves.
  • Data connectors of some embodiments may comprise a unique data connector configured to impede mating with commonly available data connectors.
  • data connectors may be configured to impede mating with USB, micro USB, ethernet ports, HDMI, micro HDMI, modular plugs, modular jacks, or firewire connectors.
  • the fastening may comprise a releasable fastening.
  • a releasable fastening may enable the user to vary the medical treatment parameter by removing the computer readable storage device and replacing the computer readable storage device with a further storage device comprising an alternative medical treatment parameter. This will prevent the need for disposal of the medical device, enabling the continued use of the medical device throughout a complex or prolonged infusion treatment.
  • a medical professional may monitor a patient during a medical treatment, and if the patient is not responding to the treatment as the medical professional had anticipated, the medical professional may seek to alter the medical treatment parameter. This may occur during surgery, during emergency situations or as a result of an accident. In these situations, the medical professional may remove the computer readable storage device comprising the substantially releasable fastening. The medical professional may then obtain an alternative computer readable storage device encoding the desired medical treatment parameter and place it in the medical device.
  • the medical device may be programmed to continue to operate at the programmed medical treatment parameter after the computer readable storage device has been removed, until the alternative computer readable storage device is received by the medical device.
  • the programmable, non-transitory, computer readable storage device of certain embodiments may encode one or more medical treatment parameters for operating the medical device. However, more than one medical treatment parameters may be encoded on the device.
  • the computer readable storage device may comprise a digital key.
  • a digital key may be configured to encode any one of a number of instructions for the operation of a medical device.
  • the digital key may comprise a digital flow key configured to encode a flow rate for the administration of liquid infusions.
  • the priming sequence may be pre-programmed in the infusion pump whereby engagement of the digital flow key may initiate or enable operation of a user priming sequence.
  • a user priming sequence may comprise the steps of connecting an intravenous bag, activating the infusion pump, pressing and holding a priming button, priming of the line (which may occur over five seconds to remove air from the line, for instance by pumping about 1 ml of fluid through the line), inserting a programming key, and pressing the start button.
  • More complex embodiments of the programming key may draw auxiliary power or higher voltages.
  • high viscosity liquids such as blood products
  • certain embodiments of the programming key may comprise an auxiliary power source, such as a battery.
  • Such embodiments enable a single use infusion pump to be used for extended infusions and/or for the infusion of viscous liquids.
  • priming cannot proceed once the flow key has been inserted into the infusion pump; this may prevent accidental activation by the patient.
  • an infusion may switch from a priming sequence to an infusion sequence once the flow key has been introduced into the medical device.
  • the maximum limit of priming attempts may be set at, for instance, three attempts.
  • the flow key is pre-programmed to a fixed flow rate.
  • Preferred flow rates comprise 0.5 ml/hour, 1 ml/hour, 2 ml/hour, 4 ml/hour, 5 ml/hour, 10 ml/hour, 20 ml/hour, 25 ml/hour, 40 ml/hour, 50 ml/hour, 60 ml/hour, 75 ml/hour, 80 ml/hour, 100 ml/hour, 120 ml/hour and 150 ml/hour.
  • typical liquids such rates may be delivered by a resistor-based programming key.
  • Preferred embodiments may comprise a programming key providing the medical treatment parameter of a flow rate. Such embodiments may be provided as resistor-based programming keys. Typically, programming of multiple parameters may be provided by programming keys comprising an auxiliary power source.
  • the computer readable storage device may take the form of a memory card, a smart card, an electrically erasable programmable read only memory (EEPROM) tag, a radio frequency identification data (RFID) tag, or a similar portable device comprising an embedded integrated circuit.
  • the computer readable storage device may be encrypted.
  • the computed readable storage device may store any quantity of data deliverable by a suitable compact device.
  • the programming key may also store a large amount of information about the patient and their treatment such as an authentication key, a security key, a patient's identity, the identity of the drug and diluent being infused, the flow rate of a drug being infused, the volume of the drug being infused, the temperature of the infusion solution, a schedule of the treatment regime for a patient or an instruction manual.
  • the infusion pump may continue to operate at the programmed flow rate after the flow key has been removed. That is, until an alternative flow key encoding a different flow rate is received by the infusion pump. This enables the user to continue using the same bag of fluid containing the medicament.
  • the infusion pump may preferably receive information, for example sensed information, relating to the volume of fluid that has been infused, the volume of fluid within the bag at the commencement of the infusion, or the remaining volume of fluid in the bag. This information may be entered directly or calculated by the infusion pump based on other parameters. Other sensed parameters, such as temperature of the fluid, may also be communicated back to the infusion pump.
  • information for example sensed information, relating to the volume of fluid that has been infused, the volume of fluid within the bag at the commencement of the infusion, or the remaining volume of fluid in the bag.
  • This information may be entered directly or calculated by the infusion pump based on other parameters.
  • Other sensed parameters such as temperature of the fluid, may also be communicated back to the infusion pump.
  • the programming key may comprise an electrically erasable programmable read only memory (EEPROM) device, radio frequency identification data (RFID) tag, a central processing unit (CPU), a memory reader, a card reader, a port connected to a cable or all of the above.
  • EEPROM electrically erasable programmable read only memory
  • RFID radio frequency identification data
  • CPU central processing unit
  • memory reader a card reader
  • port connected to a cable or all of the above.
  • the programming key may be used to store confidential data such as an authentication key, a security key, a patient's identity, an access rule reference, a doctor or nurse's identity, the patient's infusion and/or administrative data, the infusion flow rate, the volume of infusion, a schedule and setting information.
  • An EEPROM may also comprise a RFID tag to process, store and monitor the drug to be infused, infusion flow rates, temperature of the drug, and the like.
  • the programming key is preferably pre-programmed.
  • the flow rate is preferably pre-programmed during manufacture of the programming key.
  • the flow rate is programmed such that it is decipherable by an infusion pump.
  • the flow rate may be tested during the manufacturing process to ensure the accuracy of the flow rate and/or to ensure that the flow rate has been rendered non-editable.
  • the programming key may be pre-programmed to have a fixed flow rate such as 0.5 ml/hour, 1 ml/hour, and so on, to avoid any overdosing or underdosing.
  • the programming key may be disposed of after use and a new programming key may be used for a further infusion.
  • the computer readable storage device may further comprise a port or a cable to form an electronic connection with a second storage device, a data hub device, a battery charger or to communicate or transfer the data received from the first storage device.
  • the second storage device may be present in the form of sim card, an electrically erasable programmable read only memory (EEPROM) device, radio frequency identification data (RFID) tag, a central processing unit (CPU), a memory reader, a card reader, a wireless connection and the like.
  • the computer readable storage device may store a computer readable program encoding the information or data describing a medical treatment.
  • the computer readable storage device may also encode a unique identifier.
  • the unique identifier is preferably applied during the manufacturing of the computer readable storage device.
  • the unique identifier may identify the authenticity of the computer readable storage device and/or it may identify the make, model or other information relating to the computer readable storage device.
  • the unique identifier may be read by the medical device as a further safety measure to ensure the computer readable storage device encodes an authentic medical treatment or a treatment approved by a drug library.
  • the unique identifier of the computer readable storage device may be communicated to the data hub.
  • the data hub may undertake one or more further safety measures. For instance, it may match a sensed flow rate with the flow rate applied to the unique identifier during manufacture. This also provides a further quality assurance measure to identify any product failures. Also, any counterfeit products may be identified, located and destroyed.
  • the process of transferring the information relating to the treatment via a computer readable storage device may be unidirectional. Unidirectional data flow may secure the data, in particular by ensuring that the data cannot be overwritten.
  • the information relating to the treatment may be unidirectional, other information transferred between the computer readable storage device and the medical device may be communicated bidirectionally. It is envisaged, also that data may be added to the computer readable storage device without overwriting the program, via secure mechanisms commonly known to those skilled in the art.
  • the substantially non-editable, computer readable program may be secured for accidental or deliberate tampering by encryption of the program.
  • the encrypted program may be decoded by the medical device.
  • decryption may be carried out by a second program located on the computer readable storage device which is triggered when the computer readable storage device is connected with or brought into contact with the medical device or the data hub.
  • Embodiments comprising the medical device may take the form of an infusion pump, a dialysis machine or any other medical device that can deliver a drug or blood product into a patient's body at a prescribed rate and volume over a certain period.
  • the medical device may comprise an opening adapted to receive the computer readable storage device affixed to a fastener coupling.
  • the opening may take the form of a mounting cavity within which the computer readable storage device may be inserted.
  • the mounting cavity may comprise a locking mechanism such as a sliding fastener, a clip, a screw or a sliding lock to slide and optionally lock the computer readable storage device into the mounting cavity. This preferably prevents the removal or tampering of the computer readable storage device.
  • the space formed within the medical device may be partially occupied by a storage device reader.
  • the storage device reader may be positioned to contact the computer readable storage device when the storage device is placed within the space formed within the medical device.
  • the storage device reader may read the encoded data or information (which may be the treatment parameter for a patient) stored in the computer readable storage device.
  • the storage device reader comprises a bar code reader, an optical character recognition device, a laser, an RFID antenna, a reader circuit and the like. The reader reads the information encoded on the computer readable storage device which may be decoded and received by the central processing unit (CPU) within the medical device.
  • CPU central processing unit
  • the reader may be a bar code reader, an optical character recognition device, a laser, an RFID antenna, a radio communication receiver or a reader circuit.
  • An infusion pump may have one or several readers to receive information from one or more programming keys.
  • the information decoded by the central processing unit of the infusion pump may be transferred, received or stored. This may take place via a cabled, wireless or other data connection to a data hub device.
  • the data hub device may comprise a medical device hub or an infusion pump hub.
  • the device may further comprise a central processing unit (CPU), a port to form a cabled connection with another electronic device, componentry capable of establishing at least one form of wireless connectivity (e.g. to establish a Bluetooth, Wifi or other communication signal) to communicate with the medical device.
  • CPU central processing unit
  • a port to form a cabled connection with another electronic device
  • componentry capable of establishing at least one form of wireless connectivity (e.g. to establish a Bluetooth, Wifi or other communication signal) to communicate with the medical device.
  • connection may be configured to ensure the unidirectional transfer of data, for instance, from the medical device to the data hub device. This may be preferred to ensure the security or safety of the medical device. However, the connection may also be configured to permit two way data transfer. This may be preferred where the data hub receives data from multiple devices or sensors.
  • the data hub may aggregate and processes data, in particular complex data or data from multiple sources, for display on a smart device, for feedback to the medical device, or for monitoring by health monitoring services.
  • Sensors may be integrated into the medical device, an infusion line, an infusion bag or the data hub device to detect any one of a number of parameters, for instance sensors may detect infectious agent (for aseptic condition compliance), they may perform a rapid identification of a medication or rapid identification of the concentration of medication.
  • infectious agent for aseptic condition compliance
  • the data hub device may be pre-programmed to display the time and location.
  • Embodiments wherein the programming key is coupled with the data hub preferably enable the programming key to be written.
  • a program parameter may be written onto a key for setting an infusion administration for an infusion device.
  • the data hub will collect programmed and/or sensed data generated through the use of the infusion device.
  • the coupled hub and programming key may provide feedback to the medical device on sensed parameters during the infusion.
  • the medical device hub may comprise a programming key that makes physical contact with the medical device. Alternatively, it can be located elsewhere (either within the medical device or external to the medical device) and may be connected to the medical device via a cabled or wireless network.
  • the data hub device may comprise a smart device such as a mobile phone, a smart watch, smart headphones etcetera.
  • the smart device may comprise an opening to receive a cable plug connected to the medical device, and a central processing unit (CPU) for receiving and storing the information from the central processing unit (CPU) present within the medical device.
  • CPU central processing unit
  • the smart device may be connected via a wireless network, such as Bluetooth or Wifi, for receiving and storing information from the central processing unit (CPU) within the medical device.
  • Wireless connectivity may eliminate the need for a cable that may interfere with the patient's care. It may also provide for mobile connectivity solutions for hospitals and outpatient care.
  • the data hub is coupled with the programming key and is wirelessly connected to a server, computer or router.
  • Wireless connectivity may enable the downloading of data collected during the treatment of a patient and/or transportation of a patient during emergency treatment.
  • the data hub may be used to aggregate medical device data in a specific area.
  • Such devices are preferably not wearable but may be located in a monitoring station. For instance, they may cover a geography such as a home, a residential care facility, or a ward in a hospital. This may enable a carer to monitor a patient such that the carer receives alarms and other information relating to the medical treatment (or any other sensed data triggered by the wireless sensor).
  • a master data hub may be located at a monitoring station and the slave may be a wearable held by the patient or a carer.
  • the master data hub may be located in the home, at a residential care facility, in the ward of a hospital or at a third party monitoring facility.
  • the master data hub may be located on a physical network connected to the slave via a cabled connection (for example ethernet cabling), it may be connected to the slave via a local wireless network, or it may be connected to the slave via a cellular network.
  • the master data hub may form a cloud based service, which may be particularly advantageous if a carer, medical practitioner or monitoring facility is not co-located with the patient.
  • the hub may be carried in a carrier, for example a carrier bag or strap. It may be stored, secured and/or protected in a housing, for instance a bag or safety pouch.
  • the safety pouch may comprise a belt or a band, one or more storage sections, optionally with a safety zip to ensure the safety of the components.
  • a band, independent of or combined with a safety pouch, could be used to tie and secure the safety pouch around the waist or arm of the patient so that infusion may be conducted anywhere within the hospital or even at home.
  • FIG. 1 a provides a detailed flow diagram showing the transfer of data from the infusion pump to the infusion pump hub.
  • FIG. 1 b provides a detailed flow diagram showing the transfer of data across the user journey; from the infusion pump to the infusion pump hub.
  • FIGS. 2 a and 2 b illustrate an infusion pump programming assembly according to embodiments of the invention; including a flow key and an infusion pump.
  • FIG. 4 a illustrates embodiments including a cabled data transfer system from the infusion pump to the data hub, via cabled ports.
  • FIG. 4 b illustrates different types of flow keys for cabled data transfer from the flow key to the data hub.
  • the programming key forms a component of the medical device hub.
  • the data flow model for such embodiments does not necessitate unidirectional data flows as mentioned above.
  • the physical form of the medical device hub and programming key is altered.
  • the programming key may be connected to the medical device hub prior to use and thereafter removed and physically placed within the medical device for use.
  • the programming key may be embedded in or connected to the medical device hub whereby communication and data transfer to the medical device is established via a cabled or wireless connection. In this instance, data flows from the programming key to the medical device hub via the medical device may be transferred in two directions.
  • FIG. 1 a A detailed data flow sequence for an infusion pump is shown in FIG. 1 a .
  • Individual infusion pump flow keys are pre-programmed to 0.5 ml/hour, 1 ml/hour, 2 ml/hour, 5 ml/hour, 10 ml/hour and 20 ml/hour.
  • the user selects a flow key of the desired flow rate and an infusion pump described according to PCT/AU2017/050019.
  • the flow key is inserted into the infusion pump housing and locked in place to prevent removal and tampering of the flow key.
  • An opening or ‘cut-out’ in the wall of the infusion pump forms a mounting cavity to receive the flow key.
  • the periphery of the mounting cavity comprises a locking mechanism or a sliding lock to slide the flow key into the mounting cavity.
  • the flow key mounting cavity is formed adjacent to a flow key reader built into the infusion pump, to read the data input from the flow key.
  • the input data is then uploaded to the infusion pump's CPU and the infusion sequence is initiated. Once the sequence is initiated, the infusion commences into the patient's body.
  • the data output is then received and stored in the infusion pump hub. The data output is received and stored in the infusion pump hub.
  • the infusion process may be administered by a medical professional, carer or it may be self-administered.
  • FIG. 1 b shows a user journey for embodiments of the invention involving a pre-determined pharmaceutical treatment regime.
  • the user selects a treatment regime as prescribed by a medical professional.
  • the user obtains a pre-sterilised and pre-programmed flow key set to the prescribed flow rate desired for the drug being infused into the patient's body, and a pre-sterilised infusion pump (described in PCT/AU2017/050019).
  • the user obtains all other necessary materials and equipment for performing the desired infusion (for example, picc line, leur lock fitting, sterile swabs, intravenous bag and the like) and prepares the patient to receive a picc line in accordance with clinically accepted aseptic techniques, commonly known to persons skilled in the art.
  • picc line for example, picc line, leur lock fitting, sterile swabs, intravenous bag and the like
  • the patient, infusion bag and infusion pump are then prepared for the infusion in accordance with local clinical practice.
  • the user activates the infusion pump and initiates the priming sequence by pressing and holding the priming button on the infusion device.
  • the line is primed by pumping about 1 ml of fluid through the line over five seconds to remove air from the line.
  • the flow key is inserted into the infusion pump to transfer the data relating to the treatment regime, which also activates the infusion pump. Once the pump is initiated, an administration sequence is initiated to administer the patient's treatment regime pre-set in the flow key described above.
  • the flow key and infusion pump are disposed of and the output data is received and stored in the infusion pump hub.
  • the infusion pump hub can be used for an extended infusion in cases where the pre-set flow key completes the infusion and a further infusion is required for an extended period of time.
  • the infusion pump hub can be pre-programmed to display the time and location.
  • the embodiment of the invention ensures a safe mechanism for administering a predetermined infusion treatment and recording a patient's infusion history.
  • FIG. 2 a shows an infusion pump programming assembly comprising an infusion pump 011 and a sliding fastener 009 wherein the infusion pump 011 defines a planar shell-like structure with a small opening moulded onto the upper portion of the infusion pump 011 for receiving a sliding fastener 009 .
  • the opening comprises a pair of grooves 008 to hold the fastener 009 in place.
  • the grooves 008 are located at opposite lengthwise edges of the opening parallel to one another.
  • the opening may also comprise a data connector 005 for forming a connection with a data connector on a flow key 006 .
  • the fastener 009 is formed of a planar cover moulded with the same material forming the infusion pump shell.
  • the outer perimeter of the fastener comprises a pair of tongues 007 at opposite lengthwise edges of the fastener 009 wherein the tongues 007 are formed to slide into the grooves 008 of the infusion pump opening.
  • the tongue 007 on the fastener 009 may terminate in a hook to correspond with an enlargement of the groove 008 formed at the end of the groove 008 in the infusion pump 011 as shown in FIG. 2 b . In certain embodiments, this may be formed to render the infusion pump 011 a single use device; thereby avoiding safety issues arising from reprogramming errors.
  • the fastener 009 comprises a programming flow key 006 which is a unique connector, formed to impede connection with other commonly known data connectors such as USB, micro USB, ethernet ports, HDMI, micro HDMI, modular plugs, modular jacks, firewire connectors and so on.
  • a programming flow key 006 which is a unique connector, formed to impede connection with other commonly known data connectors such as USB, micro USB, ethernet ports, HDMI, micro HDMI, modular plugs, modular jacks, firewire connectors and so on.
  • the flow key 006 comprises a pair of internal, curved, resistant flanges (not shown) to provide a locking mechanism to lock the flow key 006 into the opening of the infusion pump 011 .
  • the size and shape of the flow key 006 is formed such that the flow key 006 slides into the opening and locks well when the fastener slides within the grooves 008 , forming a connection with the data connector 005 .
  • the fastener 009 completes the exterior of the infusion pump and forms a smooth finish as shown in FIG. 2 b .
  • FIG. 3 shows a cabled system comprising a pre-programmed flow key 010 which is inserted in the infusion pump 011 to transfer data from the infusion pump 011 to the infusion pump hub 024 .
  • the infusion pump 011 in this example, further comprises a fixed cable 012 to connect to the infusion pump hub 024 .
  • the infusion pump hub 024 comprises a standard data port 013 that connects to the fixed cable 012 of the infusion pump 011 , and a CPU that receives and stores the output data.
  • the infusion pump hub 024 mentioned above is protected in a safety pouch 014 .
  • the safety pouch 014 comprises a belt or band 015 , two padded storage sections along with a safety zip to maintain the safety of the components.
  • the band 015 of the safety pouch 014 can be used to tie and secure the safety pouch 014 around the waist or arm of the patient so that an infusion can be conducted anywhere; within the hospital or even in home.
  • the safety pouch 014 can also house a thermometer to measure the infusion temperature of the treatment, a pressure sensor to sense the volume of solution infused into the patient and the rate of infusion, and a recharging station to recharge the infusion pump energy source.
  • the safety pouch 014 can store both the infusion pump 011 and the infusion pump hub 024 (not shown), such that the infusion can be carried out into the patient's body even when the components are present in the safety pouch 014 .
  • the data output from the infusion pump 011 (and any additional sensors and devices external to the infusion pump 011 ) is received by the infusion pump hub 024 by connecting the infusion pump 011 and infusion pump hub 024 via a cable 012 .
  • the embodiment of present invention ensures the safety of the components. This is particularly useful if the patient wishes to receive the infusion at home or in hospital.
  • FIG. 4 a shows an infusion pump comprising a reader to receive a pre-programmed flow key 100 .
  • the infusion pump further comprises a port or socket 110 to receive a cable plug 120 connected to the safety pouch 140 via cable 130 .
  • the safety pouch comprises an infusion pump hub and a CPU (not shown) to receive and store the data output.
  • a patient controlled analgesia (PCA) button 160 is connected to the safety pouch 140 via a second cable 150 to call or alarm the medical professional or use in case of an emergency.
  • PCA patient controlled analgesia
  • the infusion pump hub may include a headphone socket comprising a fixed cable. This embodiment of the invention allows the patient to perform multiple tasks at the same time to receive an infusion, transfer the data input, receive and store data output, and to access a PCA button 160 .
  • the flow key 104 has a fixed cable 130 with a cable plug 120 at the free end.
  • the cable plug 120 is connected to the safety pouch 140 or a PCA button 160 .
  • the infusion may be commenced once the flow key 104 is inserted into the infusion pump and brought into contact with the flow key reader of the infusion pump.
  • This embodiment also allows multiple tasks to be performed at the same time; such as receiving an infusion, transferring the data input, receiving and storing data output, and maintaining access to a PCA button 160 .
  • the infusion pump may receive the flow key which is then brought into contact with the infusion pump reader.
  • a wireless connection 022 such as a Wifi connection, may be established between the infusion pump 023 and the infusion pump hub 024 to transfer data from the infusion pump 023 to the infusion pump hub 024 .
  • the data input is transferred by the flow key 021 and the data output is transferred via wireless 022 to the infusion pump hub 024 .
  • the infusion pump hub 024 may then share the data to other devices via a cable or wireless signal such as a Bluetooth or WiFi signal.
  • a cable or wireless signal such as a Bluetooth or WiFi signal.
  • Wireless communication is preferred for sharing data with smart devices and wearables such as smart watches, mobile phones or the like, which connect to wireless networks and carry a wireless receiver.
  • the infusion pump hub 024 is stored in the safety pouch 025 .
  • both the infusion pump 023 and the infusion pump hub 024 are placed in the safety pouch 025 , and data is shared via wireless connectivity (not shown).
  • a magnetic clasp may be integrated into the safety pouch to ensure the secure connection of the infusion pump 023 and the infusion pump hub 024 to the safety pouch 025 .
  • the safety pouch 025 may comprise a reader to establish a contactless connection via Bluetooth or Wifi.
  • the safety pouch 025 can also comprise a magnetic flow key to ensure a contactless connection with the reader.
  • a magnetic flow key to ensure a contactless connection with the reader.
  • FIG. 6 illustrates an infusion pump configured to operate in a wireless environment.
  • the infusion pump comprises an opening to receive the pre-programmed flow key 100 for transferring data sensed during treatment.
  • a port within the infusion pump is further configured to receive a Wifi antenna 180 (in the form of screw-in aerial) configured to transfer the output data to the infusion pump hub.
  • the infusion pump hub has corresponding wireless componentry to receive and store the data output over a wireless network.
  • the infusion pump hub may in turn connect to a smart phone or smart watch.

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Public Health (AREA)
  • General Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Veterinary Medicine (AREA)
  • Animal Behavior & Ethology (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Vascular Medicine (AREA)
  • Hematology (AREA)
  • Heart & Thoracic Surgery (AREA)
  • Anesthesiology (AREA)
  • Computer Security & Cryptography (AREA)
  • Primary Health Care (AREA)
  • Medical Informatics (AREA)
  • Epidemiology (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Medicinal Chemistry (AREA)
  • Chemical & Material Sciences (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Fluid Mechanics (AREA)
  • General Physics & Mathematics (AREA)
  • Infusion, Injection, And Reservoir Apparatuses (AREA)
  • Medical Treatment And Welfare Office Work (AREA)
  • Electrotherapy Devices (AREA)
US16/630,464 2017-07-12 2018-07-12 Assemblies, Systems and Methods for Programming Medical Devices Abandoned US20200188587A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
AU2017902740A AU2017902740A0 (en) 2017-07-12 Data hub
AU2017902740 2017-07-12
PCT/AU2018/050721 WO2019010537A1 (en) 2017-07-12 2018-07-12 ASSEMBLIES, SYSTEMS AND METHODS FOR PROGRAMMING MEDICAL DEVICES

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2018/050721 A-371-Of-International WO2019010537A1 (en) 2017-07-12 2018-07-12 ASSEMBLIES, SYSTEMS AND METHODS FOR PROGRAMMING MEDICAL DEVICES

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/114,961 Continuation US20230355873A1 (en) 2017-07-12 2023-02-27 Assemblies, systems and methods for programming medical devices

Publications (1)

Publication Number Publication Date
US20200188587A1 true US20200188587A1 (en) 2020-06-18

Family

ID=65000944

Family Applications (2)

Application Number Title Priority Date Filing Date
US16/630,464 Abandoned US20200188587A1 (en) 2017-07-12 2018-07-12 Assemblies, Systems and Methods for Programming Medical Devices
US18/114,961 Pending US20230355873A1 (en) 2017-07-12 2023-02-27 Assemblies, systems and methods for programming medical devices

Family Applications After (1)

Application Number Title Priority Date Filing Date
US18/114,961 Pending US20230355873A1 (en) 2017-07-12 2023-02-27 Assemblies, systems and methods for programming medical devices

Country Status (9)

Country Link
US (2) US20200188587A1 (zh)
EP (1) EP3651834A4 (zh)
KR (2) KR20200034740A (zh)
CN (1) CN110891632B (zh)
AU (1) AU2018299206A1 (zh)
CA (1) CA3069471A1 (zh)
MY (1) MY197997A (zh)
SG (1) SG11202000277UA (zh)
WO (1) WO2019010537A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11317944B2 (en) 2011-03-14 2022-05-03 Unomedical A/S Inserter system with transport protection
US11458292B2 (en) 2019-05-20 2022-10-04 Unomedical A/S Rotatable infusion device and methods thereof
US11617827B2 (en) 2005-09-12 2023-04-04 Unomedical A/S Invisible needle

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010041869A1 (en) * 2000-03-23 2001-11-15 Causey James D. Control tabs for infusion devices and methods of using the same
US7553294B2 (en) * 2002-05-30 2009-06-30 Medrad, Inc. Syringe plunger sensing mechanism for a medical injector
US7727180B2 (en) * 2006-05-17 2010-06-01 Sterling Investments Lc Method and apparatus for presetting device operating levels with display
US8398616B2 (en) * 2009-05-22 2013-03-19 Abbott Diabetes Care Inc. Safety layer for integrated insulin delivery system
TWI400103B (zh) * 2009-12-03 2013-07-01 Leader Machine Co Ltd Drug delivery device
EP2544736B1 (en) * 2010-03-10 2018-05-09 Dripmate A/S A combination of a portable monitoring device and a medical device and a method of monitoring a medical device
US9561322B2 (en) * 2011-01-06 2017-02-07 Carefusion 303, Inc. Integrated infusion pump and container
US10537472B2 (en) * 2013-11-28 2020-01-21 Alcon Pharmaceuticals Ltd. Ophthalmic surgical systems, methods, and devices
ES2924813T3 (es) * 2014-02-24 2022-10-11 Becton Dickinson Co Bomba de infusión con llave de programa
US10532155B2 (en) * 2014-09-15 2020-01-14 Sanofi Injection devices triggered by mechanical key
EP3088021A1 (en) * 2015-04-27 2016-11-02 Fresenius Vial SAS Infusion pump base module with plurality of attachable control modules
JP2018532473A (ja) * 2015-09-23 2018-11-08 コーニンクレッカ フィリップス エヌ ヴェＫｏｎｉｎｋｌｉｊｋｅ Ｐｈｉｌｉｐｓ Ｎ．Ｖ． スマートシリンジ：医療介入情報のモニタリング

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11617827B2 (en) 2005-09-12 2023-04-04 Unomedical A/S Invisible needle
US11317944B2 (en) 2011-03-14 2022-05-03 Unomedical A/S Inserter system with transport protection
US11458292B2 (en) 2019-05-20 2022-10-04 Unomedical A/S Rotatable infusion device and methods thereof
US11944775B2 (en) 2019-05-20 2024-04-02 Unomedical A/S Rotatable infusion device and methods thereof

Also Published As

Publication number Publication date
CN110891632A (zh) 2020-03-17
MY197997A (en) 2023-07-25
CN110891632B (zh) 2022-05-13
KR20240026523A (ko) 2024-02-28
EP3651834A1 (en) 2020-05-20
CA3069471A1 (en) 2019-01-17
SG11202000277UA (en) 2020-02-27
US20230355873A1 (en) 2023-11-09
WO2019010537A1 (en) 2019-01-17
AU2018299206A1 (en) 2020-02-20
KR20200034740A (ko) 2020-03-31
EP3651834A4 (en) 2021-03-03

Similar Documents

Publication Publication Date Title
US11690958B2 (en) Medication injection site and data collection system
US20230355873A1 (en) Assemblies, systems and methods for programming medical devices
US10342921B2 (en) Integrated infusion pump and container
US10293107B2 (en) Selectively Controlling fluid flow through a fluid pathway
US8385972B2 (en) Medication injection site and data collection system
CA2519955C (en) Infusion data communication system
MXPA06011169A (es) Sistema de reconocimiento de informacion de identificacion para un dispositivo medico.
CA2892758C (en) Selectively controlling fluid flow through a fluid pathway
WO2017089615A1 (en) Infusion system
US20210280290A1 (en) System and device to monitor multiple infusions
US20230302224A1 (en) Medication Injection Site and Data Collection System
US20240165324A1 (en) Infusion management system
US20200335195A1 (en) System for onboard electronic encoding of the contents and administration parameters of iv containers and the secure use and disposal thereof
ES2839092T3 (es) Sistema de infusión y bomba con recuperación de tasa de suministro de bucle cerrado configurable
WO2023122514A1 (en) Dual mode and hybrid pump and container systems

Legal Events

Date Code Title Description
STPP Information on status: patent application and granting procedure in general

Free format text: APPLICATION DISPATCHED FROM PREEXAM, NOT YET DOCKETED

AS Assignment

Owner name: INFUSION INNOVATIONS PTY LTD, AUSTRALIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SLUGGETT, ANDREW;DJURASEVICH, DANNY;CROCKETT, PAUL;SIGNING DATES FROM 20200929 TO 20200930;REEL/FRAME:055097/0836

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

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

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION