Patent Grant
11883260
Priority is claimed from Australian provisional patent application no. 2014905258 filed on 23 Dec. 2014, the contents of which are incorporated by reference.
The invention relates to a medication or substance delivery apparatus, system and associated methods.
Livestock, such as cattle, often need to be administered medication substances such as vaccinations or vitamins. Typically, such medication substances are administered to the animal via a drench gun or injection gun having a needle to inject the medication substance into the animal.
The livestock industry is currently struggling with medication compliance including inaccurate dosage of medication substances, over-medication, incorrect medication and failure to adequately record delivered medication.
One reason for this struggle with medication compliance is the conditions in which medication substances are delivered to the animals where semi-skilled operators operate simple drench or injection guns to administer the medication substances. For example, the operator may incorrectly operate the drench or injection gun and may over-medicate or incorrectly the animal. Over-medication or incorrect medication may cause serious illness in the animal or at the very least may result in waste of the medication that may be expensive.
Another problem with simple drench or injection guns is that the same gun may be re-used many times with different medications which each require different dose rates and administrative procedures. Most problematically, use of the same gun with different medications may cause cross contamination which may poison or otherwise harm the animal.
In an attempt to address part of this problem semi-automatic delivery devices or guns have been proposed which, to some extent, attempt to measure and record doses of medication delivered to an animal. Typically, these devices include a gun that is configured to deliver a pre-determined dose of a medication substance to an animal. The gun may include a computer system or the like to record the delivered dose.
However, similarly to the simple drench or injection guns, these semi-automatic delivery devices or guns are still subject to medication compliance issues, in particular, the cross-contamination of medication.
The invention disclosed herein seeks to overcome one or more of the above-identified problems or at least provide a useful alternative.
In accordance with a first main aspect there is provided, a hand held apparatus for delivering a substance to an animal, the apparatus including: a removable delivery section including a delivery arrangement adapted to deliver the substance to the animal; and a drive section including a drive arrangement adapted to actuate the delivery arrangement in a coupled condition in which the removable delivery section is coupled to the drive section, wherein the delivery section includes an electronic device adapted to communicate with a control system associated with at least the drive section in the coupled condition, the electronic device being configurable so to be readable by the control system such that the control system is able to identify and operate the removable delivery section.
In an aspect, the electronic device is configurable to store at least one of configuration information and substance type information.
In another aspect, the electronic device includes memory configurable to store the at least one of the configuration information and substance type information.
In yet another aspect, the control system includes a processor carried by at least one of the drive section and an external computing device, the processor being configurable to read the at least one of configuration information and substance type information thereby enabling the drive section, in association with the control system, to identify and operate the delivery section.
In yet another aspect, the control system includes a processor carried the drive section, the processor being configurable to read the at least one of configuration information and substance type information thereby enabling the drive section to identify and operate the delivery section.
In yet another aspect, the delivery section and drive section include corresponding electrical terminals arranged to electrically communicate the memory of the electronic device with the processor carried by the drive section.
In yet another aspect, the delivery arrangement includes a substance plunger and the drive arrangement includes a driving part adapted to move the substance plunger in the coupled condition.
In yet another aspect, the delivery arrangement includes a delivery coupling part coupled to the substance plunger and the drive arrangement includes a drive coupling part coupled to the driving part, wherein the delivery coupling part and driving coupling part are arranged to be releasably coupled in the coupled condition such that movement of the driving part causes like-wise movement of the substance plunger.
In yet another aspect, the delivery arrangement includes a substance reservoir and a substance piston received within the substance reservoir, and wherein the drive arrangement includes a driving part adapted to couple with the substance piston in the coupled condition so as to move the substance piston thereby moving the substance reservoir between an expanded state, in which the substance is locatable within the substance reservoir, and a contracted state in which the substance is at least partially expellable from the substance reservoir.
In accordance with a second main aspect there is provided, delivery section for removable coupling with a drive section to form a hand held apparatus for delivering a substance to an animal, the delivery section including a delivery arrangement adapted to deliver the substance to the animal and the drive section including a drive arrangement adapted to actuate the delivery arrangement in a coupled condition in which the removable delivery section is coupled to the drive section, wherein the delivery section includes an electronic identifier adapted to communicate with a control system associated with at least the drive section in the coupled condition, the electronic identifier adapted to be readable by the control system such that the control system is able to identify and operate the removable delivery section.
In an aspect, the electronic identifier includes memory configurable to store at least one of the configuration data and substance type data.
In another aspect, the delivery section includes electrical terminals arranged to electrically communicate the memory of the electronic device with a processor carried by the drive section.
In yet another aspect, the memory is electrically erasable programmable read-only memory.
In yet another aspect, the electronic identifier includes memory configurable to store data readable by the control system to determine if the delivery section is in one of a substance configured state and a non-substance configured state.
In yet another aspect, the delivery section includes: a substance cylinder in which a substance plunger is received, the substance plunger being coupled in the coupled condition with the drive arrangement; a substance inlet in fluid communication with the delivery cylinder through which the substance is selectively introducible into the delivery cylinder; and a delivery part through which the substance is selectively dischargeable to the animal.
In yet another aspect, the delivery section includes an antenna configured to read an associated identification device of the animal.
In accordance with a third main aspect there is provided, a system for delivering a dose of a substance to an animal, the system including: an interchangeable delivery section including a delivery arrangement adapted to deliver the substance to the animal and an electronic device; a drive section including a drive arrangement adapted to actuate the delivery arrangement in a coupled condition in which the interchangeable delivery section is coupled to the drive section, and a control system adapted to communicate with the electronic device and selectively operate the drive arrangement in the coupled condition, the electronic device being readable by the control system so as to enable the control system to identify and operate the interchangeable delivery section.
In an aspect, the electronic device is adapted to store delivery information and the control system is configured to receive and process the delivery information.
In another aspect, the delivery information includes data indicating if the delivery section is in one of a substance configured state and a substance non-configured state, and wherein the control system is configured to read the data and determine if the delivery section is in one of the substance configured state and the substance non-configured state.
In yet another aspect, in the substance non-configured state, the system is adapted to receive selected substance type data and determine if the selected substance type data and the delivery section are in one of a medication compatible state and a medication incompatible state.
In yet another aspect, in the medication compatible state, the control system is configured to write substance type data indicative of the selected substance to the electronic device carried by the delivery section thereby configuring the delivery section to the substance configured state.
In yet another aspect, the control system is configured to receive substance type selection data and wherein the delivery information includes delivery substance type data associated with the interchangeable delivery section, wherein the system is configured to determine if the substance type selection data and delivery substance type data represent compatible substances, and restrict operation of the system if the substances are incompatible.
In yet another aspect, the control system is configured to receive substance type selection data and wherein the delivery information includes delivery section type data indicating the type of coupled interchangeable delivery section, wherein the control system is configured to determine if the substance type selection data and delivery section type data represent a compatible combination, and restrict operation of the system if the combination is not compatible.
In accordance with a fourth main aspect there is provided, a method for determining medication compatibility of a delivery section adapted to couple in a coupled condition with a drive section to form a hand held medication delivery apparatus, the method including the steps, in a processing system associated with the hand held medication delivery apparatus, of: Receiving, from an electronic device carried by the delivery section, delivery medication type data representing a delivery medication type associated with the delivery section; Receiving, selected medication type data representing a selected medication type selected for use; Determining, compatibility of the delivery medication type and the selected medication type to provide compatibility data representing at least one of a compatible medication state and an incompatible medication state; and wherein, in the incompatible medication state, the processing system is configured to at least partially disable operation of the medication delivery apparatus so as to inhibit delivery of medication.
In accordance with a fifth main aspect there is provided, a method for configuring a delivery section adapted to couple in a coupled condition with a drive section to form a hand held medication delivery apparatus, the method including the steps, in a system associated with the hand held medication delivery apparatus, of: Receiving, from an electronic device carried by the delivery section, delivery data; Determining, if the delivery data indicates the delivery section is in one of a medication configured state and a medication non-configured state; wherein, in the medication non-configured state, the system is adapted to receive selected medication type data and determine if the selected medication type data and the delivery section are in one of a medication compatible state and a medication incompatible state.
In an aspect, in the medication compatible state, the method includes the step of writing medication type data indicative of the selected medication to the electronic device carried by the delivery section thereby configuring the delivery section to the medication configured state.
In another aspect, the electronic device includes a memory device, and wherein the step of writing medication type data includes writing the medication type data to the memory device and configuring the memory device to a locked state such that the medication type data cannot be normally overwritten.
In yet another aspect, in the medication non-configured state, the system is configured to determine a connected delivery section type associated with the delivery section, and determine if the selected medication type data is compatible with the connected delivery section type.
In yet another aspect, in the medication non-configured state, the system is configured to determine delivery section medication type data associated with the delivery section, and determine if the selected medication type data is compatible with the delivery section medication type data.
In accordance with a sixth main aspect there is provided, a method for determining medication compatibility of a delivery section adapted to couple in a coupled condition with a drive section to form a hand held medication delivery apparatus, the method including the steps of: Reading, delivery medication type data from an electronic device carried by the delivery section, the delivery medication type data representing a delivery medication type associated with the delivery section, Receiving, at a control system in communication with the delivery section, the delivery medication type data; Receiving, at the control system, a selected medication type data representing a selected medication type selected for use; Determining, via the control system, compatibility of the delivery medication type and the selected medication type to provide compatibility data representing at least one of a compatible medication state and an incompatible medication state; and wherein, in the incompatible medication state, the control system is configured to at least partially disable operation of the medication delivery apparatus so as to inhibit delivery of medication.
The invention is described, by way of non-limiting example only, by reference to the accompanying figures, in which;
Referring to
The delivery section 12 includes a body 20 which houses the delivery arrangement 14 and a delivery part 22 which is provided in this example in the form of a needle 24 extending therefrom. However, the delivery part 22 may take other forms such as a drench tube or other suitable medication delivery fitting. The delivery section 12 is an interchangeable and reusable unit or adaptor that may be moved to a de-coupled condition as shown in
The drive section 16 is arranged to couple with and control the delivery section 12 in the coupled condition. The drive section 16 includes a body 28 having a manifold 29 arranged to house the drive arrangement 18, a pressurised gas vessel 30 coupled to the body 28, a battery 32 to power the on-board electronics of the drive section 16 and the delivery section 12, and a trigger 34 arranged to be actuated by a user. The pressurised gas vessel 30 is provided in the form of an interchangeable pre-pressurised Carbon-Dioxide canister 31 which is relesably coupled to the body 28 via a gas regulator 36. It is noted that some examples of the apparatus, such as a second example shown below in
The drive section 16 further includes a display 38 for displaying information to a user, visual indicator lights 40 for indicating the apparatus 10 status as well as a USB data connector 42 and a pressure sensor 44 arranged to measure pressure within or associated with the gas regulator 36 or canister 31.
Referring now more specifically to
The coupling part 50 and the coupling part 52 are arranged to couple with one another in a manner so as to allow the drive arrangement 18 to actuate the delivery arrangement 14 in both a forward and reverse direction as will be further described below with reference to
The delivery coupling part 52 is slidably received by the drive coupling part 50 in a vertical direction (shown by arrow “A” in
The delivery section 12 includes delivery electrical or signal connectors 54 and the drive section 16 include corresponding electrical or signal connectors 56 which are arranged to communicate with the delivery connectors in the coupled condition. In this example, the drive electrical connectors 56 are slide connector pins and the delivery electrical connectors 54 are slide pads arranged align and communicate with the slide connector pins in the coupled condition. Accordingly, the delivery electrical connectors 54 and drive electrical connectors 56 slide into engagement when the coupling parts 50, 52 are slid into engagement with one another. The drive section 16 further includes a position sensor 106 and a flexible circuit connector 109 which interconnects the electrical or signal connectors 56, the display and the position sensor 106.
The delivery section 12 further includes an antenna 70 provided in the form of an Radio Frequency Identification Device (RFID) antenna 72 extending at least partially along an underside of the delivery section 12. The delivery section 12 also carries further electronic and control components, provided in the form of an electronic device or identifier 75 including a memory device 76 connected to a Printed Circuit Board (PCB) 74. The memory device 76 may be provided in the form of an EEPROM (Electrically Erasable Programmable Read-Only Memory Chip) which may be pre-programed with configuration and operational data associated with the type and use of the delivery section 12. The memory device 76 may also be programmed with a medication type code when the delivery section 12 is first coupled to the drive section 16 and configured for use as will be further described below. In other examples, the electronic device or identifier 75 may take other forms to identify the particular delivery section 12 connected or proximate to the drive section 16.
Referring more specifically to
It is noted that
Referring now to
The delivery cylinder 81 provides a medication reservoir 77 that is moved between an expanded condition, in which medication is drawn into the medication reservoir 77 by the substance plunger 80, and a contracted condition in which the medication reservoir 77 is moved to a contracted condition by the substance plunger 80 to expel medication from the medication reservoir 77.
The medication inlet 26 is in fluid communication with the delivery cylinder 81 via an inlet conduit 88 that is connected to a main delivery conduit 90. The inlet conduit 88 includes a one-way valve 92 arranged to allow fluid medication substances to flow into the main delivery conduit 90 and into the delivery cylinder 81. The main delivery conduit 90 also includes a one-way valve 94 between the inlet conduit 88 and the delivery part 22 that is arranged in a reverse configuration relative to the one-way valve 92 so as to allow flow of fluid medication substances from the delivery cylinder 81 to the delivery part 22.
The drive arrangement 18 of the drive section 16 includes a driving part 96 adapted to move the substance plunger 80 in the coupled condition. In this example, the driving part 96 is provided in the form of a drive plunger 98 received by a drive cylinder 100 of the drive arrangement 18. The drive plunger 98 includes a drive piston 102 and a drive shaft 104 extending from the drive piston 102. The free end of the drive shaft 104 includes the drive coupling part 50. Accordingly, in the coupled condition, movement of the drive plunger 98 causes like-wise movement of the substance plunger 80. A spring 103 is concentrically fitted to the drive shaft 104 between the drive piston 102 and an inner front wall 107 of the drive cylinder 100. The spring 103 urging or biasing the drive plunger 98 in a retracted or rearward position as is shown in
The drive section 16 includes the position sensor 106 configured to measure the position of the shaft 104 relative to the fixed sensor 106. In this example, the sensor 106 is a linear encoder through which the shaft 104 passes and the shaft 104 includes encoder readable portions arranged to allow accurate positional measurement of the movement of the shaft 104. The encoder is located between the drive cylinder 100 and the drive coupling part 52 located at the forward end 17 of the drive section 16. The sensor 106 is in communication with the control system 200 as is further described below.
The drive arrangement 18 is powered by a pneumatic system 104 that includes the canister 31 and a pneumatic housing or manifold 108. However, as is detailed below with the second example, the drive arrangement 18 may also include or be powered by an electric motor or the like. Other suitable drive arrangements may also be utilised.
The pneumatic housing 108 includes an inlet coupling 110, a regulator 36, an inlet valve 114 and an exhaust valve 116. The inlet coupling 110 is adapted to releasable receive, attach and pierce the canister 31. The inlet coupling 110 may be a threaded coupling which carries a central pin to pierce a seal of the canister 31. The regulator 36 is located between the inlet coupling 110 and the inlet valve 114 to regulate flow of the pressured gas into the drive cylinder 100. The inlet valve 114 and the exhaust valve 116 are electronic control valves controlled by the control system 200.
The drive cylinder 100 provides a drive reservoir 79 which is moved between an expanded condition, in which pressured gas is introduced into the drive reservoir 79 by the pneumatic system 101 which drives or moves the drive plunger 98 to cause likewise movement of the substance plunger 80, and a contracted condition in which the drive reservoir 79 is moved by the spring 103 which urges the drive plunger 98 rearward in the drive cylinder 100 and expelling the gas via the exhaust valve 116.
Referring now to
This second example of the apparatus 10 is similar to the first example in its overall configuration and operation. Accordingly, all parts and functionalities are not again described here in detail. However, some of the differences are detailed below including differences in the drive arrangement 18 of the drive section 16 that now includes a linear electric drive system rather than a pneumatic drive system.
Turning to firstly the drive section 16 and referring more specifically to
The drive section 16 includes the position sensor 106 configured to measure the position of the shaft 104 relative to the position sensor 106. In this example, the sensor 106 is a linear encoder positioned proximate the shaft 104 and the shaft 104 includes encoder readable portions 105 arranged to allow accurate positional measurement of the movement of the shaft 104. The sensor 106 is in communication with the control system 200, as is further detailed below.
In this example, the linear drive arrangement 900 includes a high torque electric motor 902, located in the handle portion 15 of the drive section 16, that is coupled to the shaft 104 by a coupling arrangement 906. The coupling arrangement 906 includes a gearbox 904, preferably a planetary gearbox, that reduces the speed of the motor 902, and a drive sprocket 910 positioned immediately beneath the front end 903 of the shaft 102 within forward end 907 of the main body 909 of the drive section 16.
The coupling arrangement 906 further includes second or idler sprocket 912 located at an opposing end 911 of the main body 909 of the drive section 16 toward the trailing end 905 of the shaft 104, and a micro-chain 908 that extends around sprockets, 910, 912 and is driven, in a forward and reverse direction by the drive sprocket 910. In some examples, the micro-chain 908 may be replaced with a timing belt or similar part. The coupling arrangement 906 includes adjustment features including a spring tensioner 914 for the idler sprocket 912 and a chain tensioning screw 915.
The shaft 104 is coupled along one side or top of the chain 908 so at to be moveable therewith in a linear forward and reverse direction. In use, the electric motor 902 is operated by the control system 200 to actuate the shaft 104 via the linear drive arrangement 900 and thereby actuating the substance plunger 80 of the delivery section 12 in the coupled condition.
In this example, the drive section 16 also includes a control and interface arrangement 916 provided in the form of a first board arrangement 918 and a second board arrangement 920. The first board arrangement 918 includes a processor 78, RFID control unit & communication circuits 85. The second board arrangement 920 includes a WI-FI module 80, flash memory 84, vibration motor 82, indicator buzzer 83, motor drive 930, voltage regulators 932, zero position switch 934 and maximum position switch 936 (shown in
Referring now more specifically to
The delivery section 12 includes delivery electrical or signal connectors 54 in the form of slide connector pins. The delivery section 12 carries further electronic and control components, provided in this example in the form of the electronic device or identifier 75 connected to or supported by a Printed Circuit Board (PCB) 74. The electronic device or identifier 75 preferably includes a memory device 76 provided in the form of an EEPROM Chip which may be pre-programed or pre-configured with configuration or operational data (also known as “factory settings data”) associated with the type and use of the delivery section 12. For example, the pre-programed data may include delivery section type data that relates to the type of delivery section 12, volume data such as minimum and maximum dose and other parameters that relate to the operation of the delivery section 12.
In other examples, the pre-programed data may simply be a delivery section code unique to a particular delivery section 12 or type of delivery section, the code may then be read by the system 200 as is further described below to load the configuration and operational data. It is also noted that the memory device 76 may also be programmed and locked with a selected medication type code when the delivery section 12 is first coupled to the drive section 16 and configured for use as will be further described below. This, in effect, locks the delivery section 12 to a particular medication type.
In this example, the delivery section 12 also includes a releasable locking arrangement 892 to releasable secure the delivery section 12 to the drive section 16. The releasable locking arrangement 892 includes a lock mechanism 894 and an actuator 896 in the form of a button (shown best in
Turning now to
The control system 200 associated with the apparatus 10 includes components carried by the delivery section 12 and the drive section 16. In this example, the control system 200 may also interface with or include external computing devices 150 which perform some of the data processing, provide inputs and store outputs from the apparatus 10. However, the apparatus 10 may in some examples be provided to integrally include the functionality of such an external computing devices 150 and in these examples such an external computing device 150 may not be required.
In some examples, the computing device 150 may be a mobile computing device, such as a smart phone or tablet, loaded with application software configured to communicate over a network, internet or wireless connection 155 with the apparatus 10. The external computing device 150 may include or communicate with and an external database 160 and, and may be configured to perform many or most of the processing steps of the methods disclosed herein. The external computing device 150 may carry one or more further processors or memory devices. In other examples, external computing device 150 may also be in the form of a web-server or computer system in communication with a database 160 from which the apparatus 10 may retrieve and store information. In some examples, the computing device 150 or the apparatus 10 may communicate with a server system 170 and server database 172. Such computing devices 150 and server systems 170 are well known and are not described here in any detail.
In more detail, and referring now to
The drive section 16 includes drive control components 204 that may be arranged in a of variety configurations on PCB boards within the drive section 16. The drive control components 204 include the processor 78 configured to read the memory device 76, the communication WiFi module 91, the USB data device 42, the battery 32, the trigger read switch 86, the vibration motor 82, an audible buzzer 83, an RFID antenna circuit 85 in electrical communication in the coupled condition with the antenna 70, a position senor 106 which communicates with the processor 78, the display 38 and the indicator lights 40.
The drive control components 204 include as identified by 206 some components that are different between the first and second examples of the apparatus 10. The pressure sensor 44, for example, is replaced with a motor current sensor 934 in the second example, and the pneumatic valves 114, 116 are replaced respectively by the voltage regulator 930 and the current regulator 932 in the second example of the apparatus 10. The first and/or second examples may also be fitted with the zero position switch 935 and the maximum position switch 936.
The reed switch trigger 86, the battery 32 and the inlet pneumatic control valve 114 and the outlet pneumatic control valve 116 (replaced respectively by a voltage regulator 930 and a current regulator 932 in the second example of the apparatus 10) are each in electrical communication with the processor 78. The processor 78 may be in the form of a microcontroller and include multiple processing units and associated memory to store software code executable by the processor 78 to operate the apparatus 10 in accordance with methods of operation and use as are described below.
In use, a user typically firstly couples the delivery section 12 to the hand held drive section 16 to form the apparatus 10. The apparatus 10 is then configured to undertake a number of initialisation or validation steps including prompting of a user to select a medication type, using the external device 150 or an input such as the screen 38 of the apparatus 10, and reading a medication type data from the memory device 76 associated with the delivery section 12. These initialisation or validation steps include checking the compatibility and suitability of the delivery section 12 for the hand held drive section 16 as is further detailed below.
Referring to
At step 304, the system 200 determines if the delivery section 12 is in a medication-configured state or a non-medication configured state. For example, the system 200, preferably the processor 78 of the drive section 16, is configured to determine if the delivery data includes an affirmative or negative medication configuration identifier. In this example, the medication configuration identifier may simply be a “0” or “1” readable from the memory device 76.
At step 306, if the delivery section 12 is in a non-medication configured state, then the system 200, preferably via the external computing device 150, carries out a medication configuration routine including, at step 306 prompting and receiving a selected medication from a user to provide medication type selection data. At step 308, the system 200 then retrieves medication data (such as medication type, does rates etc) from the database 165 and retrieves further delivery data from delivery section 12 or database 165 such as delivery section type, delivery section medication type data and operational parameters of the delivery section 12.
At step 310, the system 200 determines if the selected medication type is suitable for the delivery section 12. This may include the system 200 comparing the selected medication type data to the delivery section medication type data to determine the medication compatibly and therefore determining one of a compatible state and an incompatible state. In the incompatible state, at step 311, the system 200 may provide an error message or return to prompt the user to reselect the medication type. This, in effect, at least partially disables or restricts the system 200, specifically the apparatus 10, from operation and in the incompatible state the apparatus 10 cannot be used to medicate an animal (i.e. the trigger may be disabled or the like).
At step 312, if the delivery section 12 is in the medication compatible state, then the system 200 writes a medication configuration identifier to the delivery section 12. More specifically, this may include writing to the memory device 76 to include medication data including the medication configuration identifier and a medication code or the like. The writing to the memory device 76, that preferably is EEPROM, includes locking the memory device 76 to prevent the memory device 76 from being re-written to different or new medication type. Accordingly, the medication configuration “locks” the delivery section 12 to a particular medication.
At step 318, the system 200 is configured to display data, such as text or images via the external computing device 150 or via the display 38 of the apparatus 10, indicating the apparatus 10 is operational and configured, and the selected or configured medication type. The apparatus 10 and system 200 may then used to deliver mediation to an animal as is described below with reference to
At step 314, in the configured state, the system 200 receives a configured medication code or data from the delivery data, and at step 316 the system 200 retrieves medication data and further delivery section data. Accordingly, the system 200 loads the pre-configured medication settings and is, in effect, locked to these particular medication type settings for the particular identified connected delivery section 12. The system 200 then proceeds to step 318 so as to be operational and display or indicate, in this instance, the pre-configured medication type data. The apparatus 10 and system 200 may then be used to deliver medication to an animal as is described below with reference to
Turning now to
The method is performed by the system 200 configured by software and includes, at step 402 communicating a user interface and input device with the apparatus 10. The user interface and input device may be an associated external computing device 150, which may be a mobile device operating application software. The communication may occur via the WiFi module 80 to allow data communication between the input device 150 and the processor 78 of the apparatus 10. It is noted that in some examples, the display 38 of the apparatus 10 may be a touch screen adapted to interface with and receive user input and, in this case, the apparatus 10 carries or includes the user interface and input device. It is noted that the mobile device operating application software may, in some examples, inturn communicate with the server system 170 that may operate as an application or cloud server and the database 172 may be accessed to store and retrieve data.
At step 404, the delivery section 12 is coupled to the drive section 14 and at step 406, the control system 200 is configured to determine if the delivery section 12 is connected to the drive section 18. This may include, for example, attempting to read the memory device 76 or simply determining a positive electrical connection of the electrical connectors 54, 56.
If no delivery section 12 is connected, at step 408, the user may be prompted, such as by an indicator or message on the display 38 to connect to the delivery section 12. In this example, if the processor 78 identifies that a delivery section 12 is not connected (or may be incorrectly connected) then an error message is sent, at step 408, to the user interface and input device, which in this example, is the external computing device 150. The user may then fit or re-fit the delivery section 12.
Once the delivery section 12 is determined to be coupled or connected to the drive section 16, at step 410, the system 200 then determines if the delivery section 12 is new and in a non-configured state, or if the delivery section 12 has been previously configured and is in a medication configured state. In more detail, the processor 78 reads delivery data from the memory device 76. The delivery data includes identifier data to identify the particular delivery section 12, configuration data associated with the particular delivery section 12 and medication data which may include a medication code of a previously utilised medication used with the delivery section 12. This step is particularly important because the delivery section 12 is interchangeable and reusable, and the drive section 16, in particular, the processor 78 needs to read the delivery data in order to identify and correctly operate the delivery section 12.
If the delivery section 12 has already been used with a particular medication, being in a medication configured state, then the delivery data will typically include medication data that may include a medication code of a previously utilised medication used with the delivery section 12. The system 200, at step 412, then loads the delivery data that then configures the drive section 16 and system 200 for use with the particular attached delivery section 12. The system 200 may also send delivery data to the external computing device 150 such as sending the medication data, history data and other parameters of the particular attached delivery section 12. At steps 415 and 417, the system 200 may indicate to the user that the system 200 is ready for use. This may be displayed or indicated at the apparatus 10 and/or at the external computing device 150.
If the delivery section 12 is not configured to a particular medication, being in a non-medication configured state, the system 200 then undertakes a medication configuration routine including, at step 414 communicating delivery data including delivery section configuration data to the external computing device 150, and at step 416 the external computing device 150 initiates a local routine to guide the user through configuring the particular delivery section 12 to a particular medication.
At step 418, the user selects a medication type using the input device provided by the external computing device 150. The medication type may be entered as a code or the user may select the medication type from a predefined list.
At step 420, selected medication or substance type data is loaded by the system 200 via the computing device 150 either from local memory or from an external database accessible 172 via the server system 170. The selected medication type data includes a code for the medication type and medication values and information such as dose rates (mm/kG).
At step 422, the system 200 then undertakes a compatibility check to determine if the correct type of delivery section 12 is connected for the selected medication. For example, the delivery data may include delivery section type data indicating if the delivery section 12 is suitable for one of injecting, drenching or back lining, and delivery medication type data that may include data indicating the types of medication that are suitable for the particular delivery section. The delivery section type data and/or delivery medication type data may also be loaded from an external database 160 or 172 once the delivery section 12 is identified by the system 200.
The system 200 then conducts comparative operations, via the computer device 150, to determine if the delivery type medication data and selected medication type data are compatible and/or if the delivery section type and the selected medication type data both indicate the same or a compatible delivery section type being, for example, one of injecting, drenching or back lining. If the type of delivery section 12 is not compatible with the selected medication, then the method moves to step 424 in which indications are provided to the user, for example via the display or computer device 150, that the incorrect delivery part 12 is fitted. The system 200 is also configured enter at least partially inoperative state in which the apparatus 10 is unable to deliver medication.
At step 426, the system 200 configures the delivery section 12 to the particular selected medication. This includes the computer device 150 of the system 200 communicating new delivery data including medication type data to the particular delivery section 12. At step 428, the system 200, via the processor 78, is then configured to write specific configuration and medication data to the memory device 76 carried by the particular delivery section 12 and locks the specific configuration data to the memory device 76 which is preferably EEProm memory. The specific configuration data includes the selected medication type data or data to represents the selected medication type data so that when the memory device 76 is again read at a later stage the processor 78 is able to determine the medication history of the particular delivery section 12. Accordingly, once a particular delivery section 12 is utilised with a particular selected medication, the particular delivery section 12 is, in essence, hard coded to always be only usable with the particular selected medication. This assists with inhibiting medication cross-contamination.
At step 430, the processor 78 then undertakes a further medication compatibility check to determine if the connected delivery section 12 is suitable for the selected medication type. During this routine the processor 78 receives delivery data from the now locked memory device 76, in particular data representing or used to determine, delivery medication type data which indicates the particular medication type associated with the connected delivery section 12. The processor 78 also receives, the selected medication type data representing the selected medication type selected for use. The processor 78 then conducts processing operations to determine compatibility of the delivery medication type and the selected medication type to provide compatibility data representing at least one of a compatible medication state and an incompatible medication state.
At step 434, if the compatibility data indicates the compatible medication state, the processor 78 enables the apparatus 10 to a ready to medicate condition, at step 415, in which the user may operate the apparatus 10 in accordance with the method 600 for delivering a substance to an animal as is further described below. The processor 78 may be configured to send a ready signal to the display 38 or to the indicator lights 40. However, if the compatibility data indicates the incompatible medication state, the system 200 is configured to at least partially disable operation of the medication delivery apparatus 10 so as to inhibit delivery of medication. At step 434, the processor 78 may be configured to send an error signal to the computing device 150, to the display 38 or to the indicator lights 40. In the incompatible or error medication state, the particular delivery section 12 may need to be removed and interchanged at step 432.
In more detail, referring to
At step 506, a user selects a medication type using the input device. The medication type may be entered as a code or the user may select the medication type from a predefined list.
At step 508, a medication specification type data is loaded by the processor 78 either from local memory carried by the apparatus 10 or from an external source such as an external mobile device or an external database accessible via a webserver. The selected medication type data includes a code for the medication type and information such as dose rates (mm/kG).
At step 510, the processor 78 is configured, by software, to determine if the delivery section 12 is connected to the drive section 18. This may include, for example, attempting to read the memory device 76 or simply determining a positive electrical connection of the electrical connectors 54, 56. If no delivery section 12 is connected, at step 312, the use may be prompted, such as by an indicator or message on the display 38 to connect to the delivery section 12.
At step 514, if the delivery section 12 is coupled to the drive section 16, and the processor 78 is configured to read delivery data from the memory device 76. The delivery data includes identifier data to identify the particular delivery section 12, configuration data associated with the particular delivery section 12 and medication data which may include a medication code of a previously utilised medication used with the delivery section 12. This step is particularly important because the delivery section 12 is interchangeable and the driver section 16, in particular, the processor 78 needs to read the delivery data in order to identify and correctly operate the delivery section 12.
The configuration data may include variables such as volume of the delivery cylinder 81, volumetric rates such as mL of substance discharged for mm of linear movement of the substance plunger 80. Other variables may include the total stroke length. The identifier data may include data to indicate the type of delivery section 12 which may be for example delivery sections 12 for injecting, drenching or back-lining.
At step 516, the processor 78 then undertakes an initial compatibility check to determine if the correct type of delivery section 12 is connected for the selected medication. For example, the delivery data may include data that the delivery section 12 is suitable for one of injecting, drenching or back lining and selected medication type data may include data indicating the medication is suitable for one of injecting, drenching or back lining. The processor 78 then conducts comparative operations to determine if the delivery data and the selective medication type data both indicated the same delivery type being one of injecting, drenching or back lining. If the type of delivery section 12 is not compatible with the selected medication, then the method moves to steps 528 and 530 in which indications are provided to the user, for example via the display, that the incorrect delivery part 12 is fitted. The processor 78 is also configured an at least partially inoperative state in which the apparatus 10 is unable to deliver medication.
At step 518, the processor 78 then undertakes a further identification step in which the processor 78 determined if the delivery section 12 has been previously utilised and configured. In this step, the processor 78 retrieves or processes retrieved delivery data including the identification data from the memory device 76 carried by the particular delivery section 12. The identification data may include prior use data which indicates if the particular delivery section 12 has been previously configured or used.
At step 520, if the prior use data indicates that the particular delivery section 12 has not been previously used or configured, the processor 78 then writes specific configuration data to the memory device 76 carried by the particular delivery section 12 and locks the specific configuration data on to the memory device 76 which is preferably EEProm memory. The specific configuration data includes the selected medication type data or data to represents the selected medication type data so that when the memory device 76 is again read at a later stage the processor 78 is able to determine the medication history of the particular delivery section 12. Accordingly, once a particular delivery section 12 is utilised with a particular selected medication, the particular delivery section 12 is, in essence, hard coded to always be only usable with the particular selected medication. This assist with inhibiting medication cross-contamination.
At step 522, the processor 78 then undertakes a secondary medication compatibility check to determine if the connected delivery section 12 is suitable for the selected medication type. During this routine the processor 78 receives delivery data from the now locked memory device 76, in particular data representing or used to determine, delivery medication type data which indicates the particular medication type associated with the connected delivery section 12. The processor 78 also receives, the selected medication type data representing the selected medication type selected for use. The processor 78 then conducts processing operations to determine compatibility of the delivery medication type and the selected medication type to provide compatibility data representing at least one of a compatible medication state and an incompatible medication state.
At step 524, if the compatibility data indicates the compatible medication state, the processor 78 enables the apparatus 10 to a ready to medicate condition in which the user may operate the apparatus 10 in accordance with the method 600 for delivering a substance to an animal as is further described below. The processor 78 may be configured to send a ready signal to the display 38 or to the indicator lights 40.
At step 526, if the compatibility data indicates the incompatible medication state, the processing system 78 is configured to at least partially disable operation of the medication delivery apparatus 10 so as to inhibit delivery of medication. At step 526, the processor 78 may be configured to send an error signal to the display 38 or to the indicator lights 40. In the incompatible medication state, the particular delivery section 12 may need to be removed and interchanged at step 530. The routine then proceeds to step 512 where a new delivery section 12 is connected to the drive section 12.
Referring now to
At step 602, a particular animal is selected for medication and at step 604, if the animal includes a identification means such as an animal RFID tag, an animal identification step is undertaken at step 606 in which the animal RFID tag is scanned or read by the RFID reader 70 of the apparatus 10. The RFID reader may be activated by user actuation of the trigger and the animal identification data may be received by and processed by the processor 78.
At step 608, the system 200 is configured to determine if a fixed dose or a calculated dose is to be administered. If the animal does not include an identification means or if the animal is not identifiable the system 200, preferably the processor 78, determines that a fixed or pre-determined dose should be applied to the animal. This pre-determined dose or dose rate may be included in the selected medication type data as was described above in relation to methods 300 or 400. The fixed dose may be inputted by a user or predetermined by the system 200.
However, if the animal information is available, the control system 200 then initiates an animal identification lookup step, at step 610, wherein the identification of the animal is matched to a pre-defined database or stored animal information located in the memory of the control system 200 or an externally accessible device or database such as database 160. This stored information may be pre-loaded or stored in the memory and may include animal parameters such as weight, height, age, sex and/or other similar information.
On matching the animal identification with the stored information the control system 200 retrieves the animal parameters at an animal parameters lookup step. The animal parameters may include the animal weight, type and age as well as related information which is used to calculate the dose rate. In some examples, the dose may be manually inputted by the user or may be a fixed dose. However, in this example, the dose rate is calculated at a dose rate calculation or processing step using animal parameters and medication parameters. The medication parameters may include information such as type of medication and dose rate lookup tables, for example dose in ml/kg for selected medications, which are utilised in the dose rate calculation. The medication parameters may be pre-loaded or stored in the memory and accessed by the processor.
The dose rate calculation includes determining how far to linearly move to shaft 104 and hence the plunger 80 to deliver the dose, or pre-determined quantity, of the medication to the animal. The system 200 receives delivery section data that includes volume parameters such as mL/mm. So, for example, if the determined dose is 5 mL, and the volume parameter, V, of the delivery section 12 is, 1 mL/mm, the system 200 is configured to determine a linear movement parameter, L, that in this case would 5 mm (i.e 5 mm linear plunger movement is required to expel 5 mL to substance to the animal). The linear position sensor 106 continuously monitors or measures this linear distance to provide position feedback for the control system 200.
At step 612, the trigger 34 is actuated to activate the apparatus 10, via the control system 200, to begin delivery of the medication through the application delivery part or tip 22. Turning now to the flow and delivery of the fluid substance in more detail, by way of example only, the process for medication flow into and out of the apparatus 10 may function as follows.
Beginning with the medication reservoir 77 in the expanded state with the delivery plunger 80 located toward the rear end of the delivery cylinder 81. It is assumed here that the apparatus 10 has undergone an initial priming step whereby air is evacuated from the medication reservoir 77 and the medication reservoir 77 is filled with the substance.
In the first example of the apparatus 10, when trigger 34 is activated or pulled the pneumatic control valve 114 is moved to a fill position allowing a pressurised gas, for example, gas from the pressure canister 31, into the drive cylinder 100 to pressurise and urge plunger 98 forward from a first position toward a second position which, in the coupled condition, in turn moves the delivery plunger 80 and hence the medication reservoir 77 toward the contracted state. The fluid pressure inside the medication reservoir 77 thereby opening the valve 94 and maintaining the valve 92 in the ordinarily closed position. It is noted that in the second example of the apparatus 10, the drive arrangement 18 is electrically powered and the electric drive arrangement 900 including the electric motor 902 is activated by the control system 200 to move the plunger 80 in the same manner as described above.
At step 616, during this movement, the measurement or linear position sensor 106 is measuring the distance moved by the rod 104 and hence movement of the delivery plunger 80 coupled thereto. The distance measurement is converted by the control system 200, to a volume of substance administered or a dose. The measurement data provided to the processor 78 allows for feedback control of the delivery plunger 80 and medication delivery therefrom.
At step 614, once the control system 200 determines a pre-determined dose, either the fixed dose or the calculated dose, has been reached, the exhaust pneumatic control valve 116 is moved to an open or re-fill position in which an evacuation or exhaust port is opened between the drive cylinder 100 and the external environment. This allows the return spring 103 to move the drive plunger 98 back to the first position in which the medication reservoir 77 is again in the expanded state. During this movement, the medication inlet valve 92 moves to an open position which allows the flow of the substance into the medication reservoir 77 via the conduit 88. The valve 94 moves to a closed position to prevent air entering the medication reservoir 77 and maintains the vacuum. The drive plunger 80 then reaches its mechanical limits and is retained in the first position until the trigger 34 is next actuated. The couplings 50, 52 between the drive plunger 98 and delivery plunger 80 result in the delivery plunger 80 being actuated in a likewise motion and being controlled by the movement of the drive plunger 98.
Again, it is noted that in the second example of the apparatus 10, the drive arrangement 18 is electrically powered and the electric drive arrangement 900 including the electric motor 902 is activated by the control system 200 to move the plunger 98 in the same manner as described above. In the second example, the micro-chain 908 moves the shaft 104 and hence the drive plunger 80 in both the forward and reverse directions and therefore a return spring 103 is not required in the second example.
At step 618, dose data representing the measured delivered dose is written internal memory 84 carried by the drive section 12, and at step 620 the dose data is written to memory of the external computing device 150, such as a mobile device. The apparatus 10 then enters a ready or stand-by mode awaiting the next actuation of the trigger 34. Preferably, the dose data is also written to the server system 170 and the database 172 thereby enabling synchronising of the dose data between the apparatus 10, external computing device 150 and server system 170. The recorded dose data may include or be associated with the following animal identification data, mediation type data, dose amount, batch number, user ID, farm ID, date, time, apparatus serial number including delivery section serial number and application software version.
Advantageously, there has been described an apparatus having a split arrangement with a removable and interchangeable delivery section and a main drive section which operates and controls the delivery section. The delivery section may be considered an adaptor or interchangeable head which includes a medication reservoir and plunger which when coupled to the main drive section is actuated and controlled by the main drive section. The delivery section having the medication reservoir fully separates any medication carried by or associated with the delivery section from the main drive section. The interchangeable delivery section also allows different types of the delivery section to be coupled with a common main drive section providing the apparatus with a high level of flexibility.
Further advantageously, the delivery section carries an identifier or memory device that uniquely identifies the delivery section such as providing a code or other data to identify the delivery section to the control system. This identifier allows the delivery section to be associated with a particular medication type, such as a previously used medication, and may be associated with operational parameters of the delivery section to enable the main drive section to correctly operate the delivery section. The memory device may also be preferably hard coded on the first use of the delivery section with a particular medication type such that delivery section is, in-effect, locked to be only used with that particular medication type.
Accordingly, the apparatus in conjunction with the control system is able to determine if the delivery section has been previously used and configured to a particular type of medication, and if in a configured state, restrict the delivery section to being used with the particular configured medication. However, if the delivery section is new and in a non-configured state, the system able to receive a user selected medication, check that the connected delivery section is compatible with the user selected medication, and then configure the delivery section for use with the user selected medication. The system then is able to “lock” the memory device to the configured medication and thereby the delivery section being in the configured state.
Furthermore, the memory device of the delivery section may include the operational parameters and these may be stored to the memory device for reading by the processor carried by the delivery section to enable the main drive section to correctly operate the delivery section. Accordingly, when the main drive section is configured to deliver a particular medication type, the control system is able to check that the attached delivery section is medication compliant or compatible, and also have access to operational parameters for operation of the delivery section. This provides highly advantageous medication compliance functionality.
Throughout this specification and the claims which follow, unless the context requires otherwise, the word “comprise”, and variations such as “comprises” and “comprising”, will be understood to imply the inclusion of a stated integer or step or group of integers or steps but not the exclusion of any other integer or step or group of integers or steps.
The reference in this specification to any known matter or any prior publication is not, and should not be taken to be, an acknowledgment or admission or suggestion that the known matter or prior art publication forms part of the common general knowledge in the field to which this specification relates.
While specific examples of the invention have been described, it will be understood that the invention extends to alternative combinations of the features disclosed or evident from the disclosure provided herein.
Many and various modifications will be apparent to those skilled in the art without departing from the scope of the invention disclosed or evident from the disclosure provided herein.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2014905258 | Dec 2014 | AU | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/AU2015/050832 | 12/22/2015 | WO |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2016/101031 | 6/30/2016 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 3941130 | Tibbs | Mar 1976 | A |
| 4073321 | Moskowitz | Feb 1978 | A |
| 4103684 | Ismach | Aug 1978 | A |
| 4106770 | Gray | Aug 1978 | A |
| 4261358 | Vargas et al. | Apr 1981 | A |
| 4275729 | Silver et al. | Jun 1981 | A |
| 4316463 | Schmitz et al. | Feb 1982 | A |
| 4435173 | Siposs | Mar 1984 | A |
| 4475905 | Himmelstrup | Oct 1984 | A |
| 4498904 | Turner et al. | Feb 1985 | A |
| 4547189 | Moore, Jr. | Oct 1985 | A |
| 4592742 | Landau | Jun 1986 | A |
| 4664653 | Sagstetter et al. | May 1987 | A |
| 4710162 | Johnson | Dec 1987 | A |
| 4735611 | Anderson et al. | Apr 1988 | A |
| 4738660 | Lucas | Apr 1988 | A |
| 4852768 | Bartsch | Aug 1989 | A |
| 4858607 | Jordan et al. | Aug 1989 | A |
| 4865591 | Sams | Sep 1989 | A |
| 4902279 | Schmidtz et al. | Feb 1990 | A |
| 4955868 | Klein | Sep 1990 | A |
| 4988339 | Vadher | Jan 1991 | A |
| 4994034 | Botich et al. | Feb 1991 | A |
| 5011476 | Foster | Apr 1991 | A |
| 5026349 | Schmitz et al. | Jun 1991 | A |
| 5127906 | Landry, Jr. et al. | Jul 1992 | A |
| 5151088 | Allison et al. | Sep 1992 | A |
| 5163908 | Lambert | Nov 1992 | A |
| 5176643 | Kramer et al. | Jan 1993 | A |
| 5190526 | Murray et al. | Mar 1993 | A |
| 5201720 | Borgia et al. | Apr 1993 | A |
| 5226896 | Harris | Jul 1993 | A |
| 5232459 | Hjertman | Aug 1993 | A |
| 5267963 | Bachynsky | Dec 1993 | A |
| 5271744 | Kramer et al. | Dec 1993 | A |
| 5298024 | Richmond | Mar 1994 | A |
| 5300041 | Haber et al. | Apr 1994 | A |
| 5304152 | Sams | Apr 1994 | A |
| 5320609 | Haber et al. | Jun 1994 | A |
| 5322511 | Armbruster et al. | Jun 1994 | A |
| 5346480 | Hess et al. | Sep 1994 | A |
| 5358489 | Wyrick | Oct 1994 | A |
| 5364362 | Schulz | Nov 1994 | A |
| 5391157 | Harris et al. | Feb 1995 | A |
| 5411487 | Castagna | May 1995 | A |
| 5451210 | Kramer et al. | Sep 1995 | A |
| 5514097 | Knauer | May 1996 | A |
| 5545147 | Harris | Aug 1996 | A |
| 5560317 | Bunyan et al. | Oct 1996 | A |
| 5562626 | Sanpietro | Oct 1996 | A |
| 5573513 | Wozencroft | Nov 1996 | A |
| 5599309 | Marshall et al. | Feb 1997 | A |
| 5620421 | Schmitz | Apr 1997 | A |
| 5626566 | Petersen et al. | May 1997 | A |
| 5695472 | Wyrick | Dec 1997 | A |
| 5713871 | Stock | Feb 1998 | A |
| 5722956 | Sims et al. | Mar 1998 | A |
| 5769822 | McGary et al. | Jun 1998 | A |
| 5776107 | Cherif-Cheikh | Jul 1998 | A |
| 5779677 | Frezza | Jul 1998 | A |
| 5792117 | Brown | Aug 1998 | A |
| 5800403 | Pressly et al. | Sep 1998 | A |
| 5833669 | Wyrick | Nov 1998 | A |
| 5882342 | Cooper et al. | Mar 1999 | A |
| 5911703 | Slate et al. | Jun 1999 | A |
| 5921959 | McGary et al. | Jul 1999 | A |
| 5984900 | Mikkelsen | Nov 1999 | A |
| 5984906 | Bonnichsen et al. | Nov 1999 | A |
| 5997500 | Cook et al. | Dec 1999 | A |
| 6015438 | Shaw | Jan 2000 | A |
| 6056716 | D'Antonio et al. | May 2000 | A |
| 6068615 | Brown et al. | May 2000 | A |
| 6077247 | Marshall et al. | Jun 2000 | A |
| 6083199 | Thorley et al. | Jul 2000 | A |
| 6086567 | Kirchhofer et al. | Jul 2000 | A |
| 6099504 | Gross et al. | Aug 2000 | A |
| 6102896 | Roser | Aug 2000 | A |
| 6110147 | Perouse | Aug 2000 | A |
| 6171285 | Johnson | Jan 2001 | B1 |
| 6179812 | Botich et al. | Jan 2001 | B1 |
| 6203530 | Stewart | Mar 2001 | B1 |
| 6221044 | Greco | Apr 2001 | B1 |
| 6270479 | Bergens et al. | Aug 2001 | B1 |
| 6277101 | Kirchhofer et al. | Aug 2001 | B1 |
| 6312412 | Saied et al. | Nov 2001 | B1 |
| 6319234 | Restelli et al. | Nov 2001 | B1 |
| 6368303 | Caizza | Apr 2002 | B1 |
| 6387078 | Gillespie, III | May 2002 | B1 |
| 6391003 | Lesch, Jr. | May 2002 | B1 |
| 6398762 | Vetter et al. | Jun 2002 | B1 |
| 6413237 | Caizza et al. | Jul 2002 | B1 |
| 6428528 | Sadowski et al. | Aug 2002 | B2 |
| 6432087 | Hoeck et al. | Aug 2002 | B1 |
| 6461333 | Frezza | Oct 2002 | B1 |
| 6482176 | Wich | Nov 2002 | B1 |
| 6482185 | Hartmann | Nov 2002 | B1 |
| 6511460 | Arnissolle | Jan 2003 | B1 |
| 6530903 | Wang et al. | Mar 2003 | B2 |
| 6547764 | Larsen et al. | Apr 2003 | B2 |
| 6558352 | Hogan | May 2003 | B1 |
| 6558357 | Hoeck | May 2003 | B1 |
| 6569123 | Alchas et al. | May 2003 | B2 |
| 6569143 | Alchas et al. | May 2003 | B2 |
| 6589210 | Rolfe | Jul 2003 | B1 |
| 6599272 | Hjertman et al. | Jul 2003 | B1 |
| 6605058 | Wich | Aug 2003 | B1 |
| 6607508 | Knauer | Aug 2003 | B2 |
| 6610042 | Leon et al. | Aug 2003 | B2 |
| 6638255 | Weber | Oct 2003 | B1 |
| 6648858 | Asbaghi | Nov 2003 | B2 |
| 6656163 | Marshall et al. | Dec 2003 | B1 |
| 6656164 | Smith | Dec 2003 | B1 |
| 6689118 | Alchas et al. | Feb 2004 | B2 |
| 6692463 | Marteau et al. | Feb 2004 | B1 |
| 6692469 | Weekes et al. | Feb 2004 | B1 |
| 6699220 | Rolfe | Mar 2004 | B2 |
| 6726661 | Munk et al. | Apr 2004 | B2 |
| 6776776 | Alchas et al. | Aug 2004 | B2 |
| 6805686 | Fathallah et al. | Oct 2004 | B1 |
| 6808507 | Roser | Oct 2004 | B2 |
| 6817989 | Svendsen et al. | Nov 2004 | B2 |
| 6843781 | Alchas et al. | Jan 2005 | B2 |
| 6890319 | Crocker | May 2005 | B1 |
| 6976976 | Doyle | Dec 2005 | B2 |
| 6979316 | Rubin et al. | Dec 2005 | B1 |
| 7011649 | Serna et al. | Mar 2006 | B2 |
| 7056307 | Smith et al. | Jun 2006 | B2 |
| 7097634 | Gilbert | Aug 2006 | B2 |
| 7104969 | Plessis | Sep 2006 | B2 |
| 7112187 | Karlsson | Sep 2006 | B2 |
| 7229432 | Marshall et al. | Jun 2007 | B2 |
| 7241278 | Møller | Jul 2007 | B2 |
| 7247151 | Slawson | Jul 2007 | B2 |
| 7252651 | Haider et al. | Aug 2007 | B2 |
| 7500963 | Westbye et al. | Mar 2009 | B2 |
| 7500967 | Thorley et al. | Mar 2009 | B2 |
| 7597685 | Olson | Oct 2009 | B2 |
| 7615234 | Potter et al. | Nov 2009 | B2 |
| 7621891 | Wyrick | Nov 2009 | B2 |
| 7637891 | Wall | Dec 2009 | B2 |
| 7645265 | Stamp | Jan 2010 | B2 |
| 7670314 | Wall et al. | Mar 2010 | B2 |
| 7674246 | Gillespie et al. | Mar 2010 | B2 |
| 7727201 | Kirchhofer | Jun 2010 | B2 |
| 7785292 | Harrison | Aug 2010 | B2 |
| RE41956 | Klitgaard et al. | Nov 2010 | E |
| 7896850 | Kronestedt et al. | Mar 2011 | B2 |
| 7905352 | Wyrick | Mar 2011 | B2 |
| 7918824 | Bishop et al. | Apr 2011 | B2 |
| 7935087 | Judd et al. | May 2011 | B2 |
| 7976509 | Moser et al. | Jul 2011 | B2 |
| 7976510 | Janish et al. | Jul 2011 | B2 |
| 7981088 | Westbye et al. | Jul 2011 | B2 |
| 7988675 | Gillespie, III et al. | Aug 2011 | B2 |
| 8002745 | Kaal et al. | Aug 2011 | B2 |
| 8012131 | Moser et al. | Sep 2011 | B2 |
| 8021333 | Kaal et al. | Sep 2011 | B2 |
| 8021335 | Lesch, Jr. | Sep 2011 | B2 |
| 8052645 | Slate et al. | Nov 2011 | B2 |
| 8052655 | Møller et al. | Nov 2011 | B2 |
| 8114050 | Kaal et al. | Feb 2012 | B2 |
| 8172813 | Janish | May 2012 | B2 |
| 8177749 | Slate et al. | May 2012 | B2 |
| 8187226 | Stamp et al. | May 2012 | B2 |
| 8197450 | Glejbol et al. | Jun 2012 | B2 |
| 8267890 | Alchas et al. | Sep 2012 | B2 |
| 8298194 | Møller | Oct 2012 | B2 |
| 8308687 | Carrel et al. | Nov 2012 | B2 |
| 8343103 | Moser | Jan 2013 | B2 |
| 8353878 | Moller et al. | Jan 2013 | B2 |
| 8357120 | Moller et al. | Jan 2013 | B2 |
| 8361036 | Møller et al. | Jan 2013 | B2 |
| 8366682 | Wyrick | Feb 2013 | B2 |
| 8376993 | Cox et al. | Feb 2013 | B2 |
| 8409141 | Johansen et al. | Apr 2013 | B2 |
| 8608708 | Cowe | Dec 2013 | B2 |
| 8636704 | Shang et al. | Jan 2014 | B2 |
| 8734403 | Hirschel et al. | May 2014 | B2 |
| 8784381 | Watanabe et al. | Jul 2014 | B2 |
| 8900197 | Crow | Dec 2014 | B2 |
| 8905970 | Bates et al. | Dec 2014 | B2 |
| 8913123 | Miller | Dec 2014 | B2 |
| 8915886 | Cowe | Dec 2014 | B2 |
| 8920374 | Bokelman et al. | Dec 2014 | B2 |
| 8932254 | Eaton | Jan 2015 | B2 |
| 8932266 | Wozencroft | Jan 2015 | B2 |
| 8945063 | Wotton et al. | Feb 2015 | B2 |
| 8992484 | Radmer et al. | Mar 2015 | B2 |
| 8998855 | Hudson et al. | Apr 2015 | B2 |
| 9011386 | Kronestedt et al. | Apr 2015 | B2 |
| 9017293 | Edhouse et al. | Apr 2015 | B2 |
| 9022989 | Bicknell et al. | May 2015 | B2 |
| 9044378 | Verespej et al. | Jun 2015 | B2 |
| 9044553 | James et al. | Jun 2015 | B2 |
| 9101722 | Moller | Aug 2015 | B2 |
| 9108006 | Jensen et al. | Aug 2015 | B2 |
| 9114212 | Enggaard et al. | Aug 2015 | B2 |
| 9114216 | Sutkin et al. | Aug 2015 | B2 |
| 9138542 | Smith | Sep 2015 | B2 |
| 9144648 | Lesch, Jr. et al. | Sep 2015 | B2 |
| 9155844 | Brereton et al. | Oct 2015 | B2 |
| 9192727 | Møller et al. | Nov 2015 | B2 |
| 9199039 | Moser et al. | Dec 2015 | B2 |
| 9199041 | Edginton | Dec 2015 | B2 |
| 9216256 | Olson et al. | Dec 2015 | B2 |
| 9233213 | Olson et al. | Jan 2016 | B2 |
| 9248245 | Ekman et al. | Feb 2016 | B2 |
| 9333309 | Sadowski et al. | May 2016 | B2 |
| 9339609 | Ekman et al. | May 2016 | B2 |
| 9352089 | Hourmand et al. | May 2016 | B2 |
| 9381308 | Hemmann et al. | Jul 2016 | B2 |
| 9402954 | Slevin | Aug 2016 | B1 |
| 9408973 | Shang et al. | Aug 2016 | B2 |
| 9446204 | Teucher et al. | Sep 2016 | B2 |
| 9457147 | Green | Oct 2016 | B2 |
| 9457149 | Kemp et al. | Oct 2016 | B2 |
| 9457153 | Marano, Jr. et al. | Oct 2016 | B2 |
| 9457154 | Moller et al. | Oct 2016 | B2 |
| 9463282 | Barrow-Williams et al. | Oct 2016 | B2 |
| 9474866 | Hourmand et al. | Oct 2016 | B2 |
| 9486581 | Lovell et al. | Nov 2016 | B2 |
| 9486583 | Lannan et al. | Nov 2016 | B2 |
| 9517311 | Saiki | Dec 2016 | B2 |
| 9539392 | Jennings et al. | Jan 2017 | B2 |
| 9545481 | Rafaat | Jan 2017 | B1 |
| 9579468 | Schoonmaker et al. | Feb 2017 | B2 |
| 9592350 | Roberts et al. | Mar 2017 | B2 |
| 9616178 | Butler et al. | Apr 2017 | B2 |
| 9656025 | Boström et al. | May 2017 | B2 |
| 9724472 | Hourmand et al. | Aug 2017 | B2 |
| 9724479 | Sutkin et al. | Aug 2017 | B2 |
| 9744297 | Cabiri et al. | Aug 2017 | B2 |
| 9750885 | Weaver et al. | Sep 2017 | B2 |
| 9757520 | Corrigan | Sep 2017 | B2 |
| 9757523 | Macdonald et al. | Sep 2017 | B2 |
| 9764089 | Alexandersson | Sep 2017 | B2 |
| 9814836 | Cowe | Nov 2017 | B2 |
| 9821118 | Adlon et al. | Nov 2017 | B2 |
| 9827373 | Roervig et al. | Nov 2017 | B2 |
| 9901680 | Roervig et al. | Feb 2018 | B2 |
| 9901681 | Sweeney et al. | Feb 2018 | B2 |
| 9925333 | Hooven et al. | Mar 2018 | B2 |
| 9931471 | Ekman et al. | Apr 2018 | B2 |
| 9943649 | Shang et al. | Apr 2018 | B2 |
| 9950125 | Wotton et al. | Apr 2018 | B2 |
| 9956344 | Cleathero | May 2018 | B2 |
| 9974904 | Burk et al. | May 2018 | B2 |
| 9974905 | Butler et al. | May 2018 | B2 |
| 10052436 | Högdahl | Aug 2018 | B2 |
| 10052441 | Searle et al. | Aug 2018 | B2 |
| 10076356 | Hadvary et al. | Sep 2018 | B2 |
| 10092708 | Thorley et al. | Oct 2018 | B2 |
| 10117996 | Stefansen | Nov 2018 | B2 |
| 10130768 | Dungar et al. | Nov 2018 | B2 |
| 10143625 | Li et al. | Dec 2018 | B2 |
| 10159796 | Schiff et al. | Dec 2018 | B2 |
| 10179207 | Haupt | Jan 2019 | B2 |
| 10195351 | Allerdings et al. | Feb 2019 | B2 |
| 10226585 | Franklin et al. | Mar 2019 | B2 |
| 10259835 | Siddiqui-Jain et al. | Apr 2019 | B2 |
| 10265471 | Kapas et al. | Apr 2019 | B2 |
| 10265476 | Laiosa et al. | Apr 2019 | B2 |
| 10265478 | Kouyoumjian et al. | Apr 2019 | B2 |
| 10269266 | Rios et al. | Apr 2019 | B2 |
| 10279116 | Plumptre et al. | May 2019 | B2 |
| 10300201 | Lumme et al. | May 2019 | B2 |
| 10300206 | Bergens et al. | May 2019 | B2 |
| 10376641 | Hirschel et al. | Aug 2019 | B2 |
| 10376692 | Mathiesen et al. | Aug 2019 | B2 |
| 10391252 | Haupt | Aug 2019 | B2 |
| 10391259 | Tran et al. | Aug 2019 | B2 |
| 10398842 | Niven et al. | Sep 2019 | B2 |
| 10406291 | Hansen et al. | Sep 2019 | B2 |
| 10413667 | Henderson et al. | Sep 2019 | B2 |
| 10413680 | Shimizu et al. | Sep 2019 | B2 |
| 10512733 | Roberts et al. | Dec 2019 | B2 |
| RE47903 | Hourmand et al. | Mar 2020 | E |
| 10588729 | Moons et al. | Mar 2020 | B2 |
| 10625026 | Creaturo | Apr 2020 | B2 |
| 10653830 | Limaye | May 2020 | B2 |
| 10661014 | Sarkinen et al. | May 2020 | B2 |
| 10675415 | Takabatake et al. | Jun 2020 | B2 |
| 10737030 | Molson et al. | Aug 2020 | B2 |
| 10744269 | Veasey et al. | Aug 2020 | B2 |
| 10751483 | Hatch et al. | Aug 2020 | B2 |
| 10888662 | Cave | Jan 2021 | B2 |
| 10898648 | Taylor et al. | Jan 2021 | B2 |
| 10912892 | Edwards | Feb 2021 | B2 |
| 10960130 | Schiff et al. | Mar 2021 | B2 |
| 10967127 | Murakami et al. | Apr 2021 | B2 |
| 10995125 | Flinspach et al. | May 2021 | B2 |
| RE48593 | Hourmand et al. | Jun 2021 | E |
| 11027056 | Mcmahon | Jun 2021 | B2 |
| 11065386 | Atterbury et al. | Jul 2021 | B2 |
| 11090441 | Tran et al. | Aug 2021 | B2 |
| 11090445 | Diaz et al. | Aug 2021 | B2 |
| 11097053 | Veyrent et al. | Aug 2021 | B2 |
| 11167086 | Cabiri et al. | Nov 2021 | B2 |
| 11278677 | Erbstein et al. | Mar 2022 | B2 |
| 11318252 | Zhang | May 2022 | B2 |
| 11357925 | Dugand et al. | Jun 2022 | B2 |
| 11376364 | Dobson et al. | Jul 2022 | B2 |
| 11376373 | Perot et al. | Jul 2022 | B2 |
| 11419991 | Diaz et al. | Aug 2022 | B2 |
| 11433186 | Ulla | Sep 2022 | B2 |
| 11439762 | Toporek et al. | Sep 2022 | B2 |
| 11565051 | Helmer | Jan 2023 | B2 |
| 11571518 | Flather et al. | Feb 2023 | B2 |
| 11642462 | Stamp | May 2023 | B2 |
| 11660397 | Moeller | May 2023 | B2 |
| 11672904 | Cabiri et al. | Jun 2023 | B2 |
| 20020004652 | Asbaghi | Jan 2002 | A1 |
| 20020107501 | Smith et al. | Aug 2002 | A1 |
| 20020161337 | Shaw et al. | Oct 2002 | A1 |
| 20030023205 | Botich et al. | Jan 2003 | A1 |
| 20030109833 | Sharpe | Jun 2003 | A1 |
| 20030114799 | Cheikh | Jun 2003 | A1 |
| 20040068158 | Bennett | Apr 2004 | A1 |
| 20040133161 | Trocki | Jul 2004 | A1 |
| 20040143224 | Field et al. | Jul 2004 | A1 |
| 20040147875 | Wallace et al. | Jul 2004 | A1 |
| 20050090782 | Marshall et al. | Apr 2005 | A1 |
| 20050171476 | Judson et al. | Aug 2005 | A1 |
| 20050222539 | Gonzales et al. | Oct 2005 | A1 |
| 20060069350 | Buenger et al. | Mar 2006 | A1 |
| 20060069354 | Buenger et al. | Mar 2006 | A1 |
| 20060129122 | Wyrick | Jun 2006 | A1 |
| 20070017533 | Wyrick | Jan 2007 | A1 |
| 20070021720 | Guillermo | Jan 2007 | A1 |
| 20070203247 | Phillips et al. | Aug 2007 | A1 |
| 20070265568 | Tsals et al. | Nov 2007 | A1 |
| 20080071218 | D'Antonio | Mar 2008 | A1 |
| 20080147006 | Brunnberg et al. | Jun 2008 | A1 |
| 20080208142 | Moller | Aug 2008 | A1 |
| 20080228147 | David-Hegerich et al. | Sep 2008 | A1 |
| 20090005737 | Chun | Jan 2009 | A1 |
| 20090204076 | Liversidge | Aug 2009 | A1 |
| 20090240210 | Walton et al. | Sep 2009 | A1 |
| 20100016796 | Derichs | Jan 2010 | A1 |
| 20100049140 | Marsh et al. | Feb 2010 | A1 |
| 20100256554 | Discher, Jr. et al. | Oct 2010 | A1 |
| 20110224613 | D Antonio et al. | Sep 2011 | A1 |
| 20110226646 | Wyrick | Sep 2011 | A1 |
| 20120179132 | Valk | Jul 2012 | A1 |
| 20120233834 | Szechinski et al. | Sep 2012 | A1 |
| 20120296276 | Nicholls et al. | Nov 2012 | A1 |
| 20120316435 | Burg et al. | Dec 2012 | A1 |
| 20130211337 | Hofmann | Aug 2013 | A1 |
| 20130274677 | Ekman et al. | Oct 2013 | A1 |
| 20130331796 | Wozencroft | Dec 2013 | A1 |
| 20140135705 | Hourmand et al. | May 2014 | A1 |
| 20140248605 | Loneragan et al. | Sep 2014 | A1 |
| 20140276583 | Chen | Sep 2014 | A1 |
| 20150001285 | Halbert | Jan 2015 | A1 |
| 20150202373 | Creaturo | Jul 2015 | A1 |
| 20150209515 | Houde | Jul 2015 | A1 |
| 20150209519 | Mernøe | Jul 2015 | A1 |
| 20170000949 | Franklin et al. | Jan 2017 | A1 |
| 20170072130 | Mcmahon | Mar 2017 | A1 |
| 20170348486 | Andersen et al. | Dec 2017 | A1 |
| 20180154082 | Yoh et al. | Jun 2018 | A1 |
| 20190143041 | Gould | May 2019 | A1 |
| 20190175839 | Kwolek et al. | Jun 2019 | A1 |
| 20200188599 | Mandaroux et al. | Jun 2020 | A1 |
| 20210236623 | Georges et al. | Aug 2021 | A1 |
| 20210338402 | Magyar et al. | Nov 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 2267812 | Oct 2000 | CA |
| 2656865 | Oct 2013 | EP |
| 2008091838 | Jul 2008 | WO |
| 2013110624 | Aug 2013 | WO |
| 2014090252 | Jun 2014 | WO |
| 2014107766 | Jul 2014 | WO |
| 2014143815 | Sep 2014 | WO |
| Entry |
|---|
| International-Type Search Report of AU2014905258 dated Nov. 26, 2015, 11 pages. |
| Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration of PCT/AU2015/050832 dated Jun. 1, 2016, 15 pages. |
| International Preliminary Report on Patentabitlity dated Jan. 10, 2014 for International Application No. PCT/AU2014/000014 (7 Pages). |
| International Search Report dated Jun. 2, 2014 for International Application No. PCT/AU2014/000014 (6 Pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20170340424 A1 | Nov 2017 | US |
