Assemblies, Systems and Methods for Programming Medical Devices

Abstract

The present invention relates to medical device programming assemblies, systems and methods for programming a medical treatment parameter on a medical device, via a programming key. The programming key may be adapted to mate with the medical device which comprises a programmable, non-transitory, computer readable storage device. The storage device comprises a data connector which is configured to mate with a corresponding data connector on the medical device. The storage device may be 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. 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 of the medical device.

Claims

1. A medical device programming assembly 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.

2. A medical device programming assembly according to claim 1 wherein the fastener coupling comprises a tongue and groove sliding fastener.

3. A medical device programming assembly according to claim 2 wherein the sliding fastener comprises 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.

4. A medical device programming assembly according to claim 3 wherein the sliding fastener comprises 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.

5. A medical device programming assembly according to any one of claims 1 to 4 wherein the data connector comprises a unique data connector configured to impede mating with commonly available data connectors.

6. A medical device programming assembly according to claim 5 wherein the data connector is configured to impede mating with USB, micro USB, ethernet ports, HDMI, micro HDMI, modular plugs, modular jacks, or firewire connectors.

7. A medical device programming assembly according to any one of claims 1 to 6 wherein the programmable, non-transitory, computer readable storage device encodes one or more medical treatment parameter for operating the medical device.

8. A medical device programming assembly according to any one of claims 1 to 7 comprising 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.

9. A medical device programming assembly according to any one of claims 1 to 8 comprising; 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.

10. A medical device programming assembly according to claim 8 or 9 wherein the data hub device comprises a server or a router.

11. A method of manufacturing a medical device programming assembly according to any one of claims 1 to 7.

12. A method of manufacturing a medical device programming assembly according to claim 7 wherein the method comprises 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.

13. A method of manufacturing a medical device programming assembly according to claim 12 wherein the step of programming the programmable, non-transitory, computer readable storage device comprises the subsequent step of rendering the medical treatment parameter substantially non-editable.

14. A system 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.

15. The system of claim 14 comprising; 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.

16. The system of claim 14 or 15 comprising; 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.

17. A method 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.

18. A method according to claim 17 wherein; the step of communicating the medical treatment parameter to the medical device is 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 comprises the step of communicating the sensed medical treatment parameter to the data hub device.

Description

BRIEF DESCRIPTION OF THE FIGURES

[0100] FIG. 1a provides a detailed flow diagram showing the transfer of data from the infusion pump to the infusion pump hub. FIG. 1b provides a detailed flow diagram showing the transfer of data across the user journey; from the infusion pump to the infusion pump hub.

[0101] FIGS. 2a and 2b illustrate an infusion pump programming assembly according to embodiments of the invention; including a flow key and an infusion pump.

[0102] FIG. 3 shows a cabled data transfer system between an infusion device and a data hub.

[0103] FIG. 4a illustrates embodiments including a cabled data transfer system from the infusion pump to the data hub, via cabled ports. FIG. 4b illustrates different types of flow keys for cabled data transfer from the flow key to the data hub.

[0104] FIG. 5 illustrates a wireless system for data transfer from the infusion device to the data hub.

[0105] FIG. 6 shows a flow key having a wireless connection for data transfer.

EXAMPLES

[0106] Several embodiments of the assemblies, systems and methods according to the invention are described in the following examples. The embodiments described herein have been illustrated by way of data flows involving medical devices such as infusion pumps, and data storage componentry. Thus, the following embodiments are exemplary in nature only and are not intended to be limited to execution using the exemplified hardware or components.

Example 1

Data Flow Model

Data Flow Model for Medical Devices

[0107] A programming key is a portable storage device carrying a computer readable program providing instructions for the operation of a medical device. The programming key is typically non-editable to maintain a unidirectional flow of data from the programming key to the medical device, when required to maintain patient safety. The programming key is physically transferred to the medical device providing an interface with the electronic componentry of the medical device. The medical device comprises corresponding electronic componentry to receive the program from the portable storage device and to decipher the operating instructions for the medical device.

[0108] The data generated during the operation of the medical device (for instance, records relating to the treatment delivered, parameters sensed by the medical device or the like) is transferred to the medical device hub where it is then stored. In certain embodiments of the invention the medical device hub may be coupled with the medical device to augment the functioning of the medical device. For instance, the medical device hub may sense and record the temperature of the treatment delivered, it may provide capacity for recharging the fuel source of the medical device or it may process data locally for communicating to other devices. The medical device hub may receive or transfer data as a real-time process or as a batch process.

[0109] The medical device hub comprises a data store together with the corresponding electronic components to enable the transfer of data from the medical device; to augment the functioning of the medical device and to transfer stored data to another device.

[0110] In an alternative embodiment, 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. Further, the physical form of the medical device hub and programming key is altered. For instance, 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. Alternatively, 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.

Data Flow Model for Infusion Pumps

[0111] In the embodiments of the invention wherein the medical device is an infusion pump, the programming key is a flow key providing a medical treatment parameter for a medical treatment. The infusion pump receives parameters relating to the medical treatment parameter (for example the flow rate of administration of the treatment); and it performs an infusion in accordance with the medical treatment parameter. The infusion pump hub receives data from the infusion pump on parameters that reflect the actual treatment performed on the patient. The infusion pump hub stores the infusion history and transfers the data captured in batch form to another device. The data flow in this instance is unidirectional therefore, the pre-programmed data cannot be deleted or overwritten but a log data can be written if any changes are required in the treatment regime of the patient.

Data Sequence for an Infusion Pump Hub

[0112] A detailed data flow sequence for an infusion pump is shown in FIG. 1a. 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.

[0113] 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.

[0114] The infusion process may be administered by a medical professional, carer or it may be self-administered.

Example 2

User Journey

[0115] FIG. 1b shows a user journey for embodiments of the invention involving a pre-determined pharmaceutical treatment regime. With reference to FIG. 1b, 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).

[0116] 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.

[0117] The patient, infusion bag and infusion pump are then prepared for the infusion in accordance with local clinical practice.

[0118] 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.

[0119] 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.

[0120] Once the infusion is complete, the flow key and infusion pump are disposed of and the output data is received and stored in the infusion pump hub.

[0121] 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.

[0122] In this example, the embodiment of the invention ensures a safe mechanism for administering a predetermined infusion treatment and recording a patient's infusion history.

Example 3

Infusion Pump Programming Assembly

[0123] FIG. 2a 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.

[0124] 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.

[0125] 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. 2b. 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.

[0126] As shown in FIG. 2a, 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.

[0127] 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. Once the flow key 006 is connected, the fastener 009 completes the exterior of the infusion pump and forms a smooth finish as shown in FIG. 2b.

Example 4

Infusion Pump Hub Assembly

Cabled Assembly

[0128] 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. In one embodiment, the infusion pump hub 024 mentioned above is protected in a safety pouch 014.

[0129] 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.

[0130] In another form of this example, 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.

[0131] 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. In this example, 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.

Cabled Pump Ports

[0132] FIG. 4a 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.

[0133] Different forms of the flow key are shown in FIG. 4b. In one form, the flow key 102 has a socket 110 to connect to a cable plug 120. The cable plug 120 is further connected to an infusion pump hub secured in the safety pouch 140 and the PCA button 160. The socket 110 on the flow key 102 is splash proof to avoid significant damage. This flow key 102 is then inserted into the infusion pump and brought into contact with the reader of the infusion pump to initiate and carry out the infusion. The data may then be received and stored in the infusion pump hub.

[0134] 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.

[0135] In another form, 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.

Wireless Assembly

[0136] In wireless embodiments of the invention illustrated in FIG. 5, 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. In this case, 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.

[0137] 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. 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. In this form of the invention, the infusion pump hub 024 is stored in the safety pouch 025.

[0138] In another form of the present invention, 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).

[0139] Additional functional features may be present in the safety pouch, for instance, 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.

[0140] The safety pouch 025 can also comprise a magnetic flow key to ensure a contactless connection with the reader. Thus, physical contact between the flow key and reader is not essential for the above-mentioned embodiments of the present invention to have full effect.

[0141] The safety pouch 025 has a belt or bands to keep the infusion pump 023 and infusion pump hub 024 close to the patient's body to allow for a controlled and effective infusion, and a fast transfer of data. The safety pouch 025 can be tied around the waist of a patient's body or the arm of a patient. The safety pouch 025 can also comprise a hook to safely secure the safety pouch 025 on clothes such as shirt pockets, pants etc of the patient.

Wireless Pump Ports

[0142] 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. In this form of the example, 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.

[0143] Throughout this specification the word comprise, or variations such as comprises or comprising, will be understood to imply the inclusion of a stated element, integer or step, or group of elements, integers or steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps.

[0144] All publications mentioned in this specification are herein incorporated by reference. Any discussion of documents, acts, materials, devices, articles or the like which has been included in the present specification is solely for the purpose of providing a context for the present invention. It is not to be taken as an admission that any or all of these matters form part of the prior art base or were common general knowledge in the field relevant to the present invention as it existed in Australia or elsewhere before the priority date of each claim of this application.

[0145] While the invention has been described above in terms of specific embodiments, it is to be understood that the invention is not limited to these disclosed embodiments. Upon reading the teachings of this disclosure many modifications and other embodiments of the invention will come to the mind of those skilled in the art to which this invention pertains, and which are intended to be and are covered by both this disclosure and the appended claims.

[0146] It is indeed intended that the scope of the invention should be determined by proper interpretation and construction of the appended claims and their legal equivalents, as understood by those skilled in the art relying upon the disclosure in this specification and the attached drawings.

LIST OF REFERENCES

[0147] United States Food and Drug Administration (2010) White Paper: Infusion Pump Improvement Initiative; http://www.fda.gov/medcaldevices/productsandmedicalprocedures/GeneralHospitalDevic esandSupplies/InfusionPumps/ucm205424.htm#types.

[0148] Mizuuchi, M. and A. Namiki (2003) The infusion rate of most disposable, non-electric infusion pumps decreases under hypobaric conditions, Can J Anesth 7 (50).

[0149] Grissinger, M. (2013) Improved Safety Needed in Handling Elastomeric Reservoir Balls Used for Pain Relief, Medication Errors, Vol. 38 No. 5, May 2013.

[0150] Irish Medicines Board (2008) Disposable Infusion Devices IMB Safety Notice: SN2008(06) Medical Device Safety Notice.

[0151] Reston, J. (2013) Making Health Care Safer II: An Updated Critical Analysis of the Evidence for Patient Safety Practices, Chapter 6. Smart Pumps and Other Protocols for Infusion Pumps: Brief Review (NEW), AHRQ Publication No. 13-E001-EF, No. 211, March 2013.

[0152] Kaye, R., and Crowley, J. (2000). Medical device use-safety: Incorporating human factors engineering into risk management, Food and Drug Administration, Center for Devices and Radiological Health. Washington, DC: U.S. Department of Health and Human Services.

[0153] ISMP (2007). Fluorouracil error ends tragically, but application of lessons learned will save lives, Medication Safety Alert. 12: 1-4.