Patent Application
20240358935
The present invention relates generally to drug delivery devices and components therefor, and in particular, to components allowing for detection and communication of the injection status of drug delivery devices.
The present invention also relates generally to systems for detecting initiation and cessation of drug delivery with a drug delivery device, communicating such drug delivery information to a mobile device associated with a user of the drug delivery device.
Drug delivery devices have traditionally lacked features that would allow a healthcare provider to automatically record or capture confirm appropriate administration of medicaments. Ensuring timely, appropriate administration of some medicaments can be critical, particularly, for example, in the instance of the evaluation of new drugs in clinical trials, where accurate information is essential.
While some devices provide the ability to communicate certain types of information, for example as described in International Patent Application Publication Nos. WO 2016/087512, WO 2017/070391, WO 2018/111969, WO 2018/213837, and WO 2021/094797, and in U.S. Patent Application Publication Nos. 2019/0083708, 2019/0321555, 2019/0344019, and 2021/046247 which discloses a drug delivery device for recording administration of a drug dose, a need exists in the art for a cost-effective device that accurately detects both initiation and cessation of drug delivery, and can communicate this drug delivery information to appropriate stakeholders, in a timely fashion.
Provided herein is a plunger device for a drug delivery device, including a plunger rod having a proximal end and a distal end configured to be attached to a stopper, a first switch and a second switch arranged at the proximal end, at least one processor in communication with the first switch and the second switch, and at least one communication interface, wherein the at least one processor is programmed or configured to receive a first signal when the first switch is activated, generate first time data, transmit, with the at least one communication interface, the first timestamp, receive a second signal when the second switch is activated, generate a second time data, and transmit, with the at least one communication interface, the second time data.
Also provided herein is a drug delivery device including a proximal end, a distal end, and a barrel therebetween defining an interior configured to receive a medicament, and a plunger device as described herein.
Also provided herein is a method of monitoring timing of medicament delivery, including steps of providing a syringe having a syringe proximal end having one or more finger flanges extending radially outward, a syringe distal end a syringe sidewall therebetween defining a syringe interior configured to receive a medicament, and a plunger device received at least partially within the syringe interior, the plunger device having a proximal end, a distal end configured to be attached to or to be in contact with a stopper, a housing arranged at the proximal end of the plunger device, comprising a displaceable proximal end, a housing distal end comprising a displaceable element, and a housing sidewall therebetween defining a housing interior, a first switch and a second switch arranged in the housing interior, at least one processor arranged in the housing interior and in communication with the first switch and the second switch, at least one communication interface arrange in the housing interior and in communication with the at least one processor, receiving, with the at least one processor, a first signal indicating that the first switch has been activated, generating, with the at least one processor, first time data, transmitting, with the at least one communication interface, the first time data, receiving, with the at least one processor a second signal indicating that the second switch has been activated, generating, with the at least one processor, second time data, and transmitting, with the at least one communication interface, the second time data.
Other exemplary embodiments or aspects are set forth in the following numbered clauses:
Clause 1. A plunger device for a drug delivery device, comprising: a plunger rod having a proximal end and a distal end configured to be attached to a stopper; a first switch and a second switch arranged at the proximal end; at least one processor in communication with the first switch and the second switch; and at least one communication interface, wherein the at least one processor is programmed or configured to: receive a first signal when the first switch is activated; generate first time data; transmit, with the at least one communication interface, the first timestamp; receive a second signal when the second switch is activated; generate a second time data; and transmit, with the at least one communication interface, the second time data.
Clause 2. The plunger device of clause 1, wherein the plunger rod is configured to be used with a manual syringe.
Clause 3. The plunger device of clause 1 or clause 2, wherein the proximal end of the plunger rod comprises a housing comprising a proximal end configured to be contacted by a user's thumb during drug delivery, a distal end attached to the proximal end of the plunger rod, and a sidewall therebetween defining an interior.
Clause 4. The plunger device of any of clauses 1-3, wherein the proximal end of the housing is displaceable relative to the distal end of the housing when a distally-directed force is applied by a user during drug delivery.
Clause 5. The plunger device of any of clauses 1-4, wherein the first switch, the second switch, the at least one processor, and at the least one communication interface are arranged in the interior of the housing.
Clause 6. The plunger device of any of clauses 1-5, wherein the first switch and the second switch are mechanical switches
Clause 7. The plunger device of any of clauses 1-6, wherein the first switch is arranged in the housing such that the proximal end of the housing, when displaced during drug delivery, activates the first switch.
Clause 8. The plunger device of any of clauses 1-7, wherein the second switch is arranged in the housing such that the second switch is activated upon completion of drug delivery.
Clause 9. The plunger device of any of clauses 1-8, wherein the distal end of the housing comprises a displaceable element configured to move proximally and activate the second switch upon completion of drug delivery.
Clause 10. The plunger device of any of clauses 1-9, wherein the communication interface is a BLUETOOTH transmitter.
Clause 11. A drug delivery device comprising: a proximal end; a distal end; and a barrel therebetween defining an interior configured to receive a medicament, and the plunger device of any of clauses 1-10 received at least partially within the interior.
Clause 12. The drug delivery device of clause 11, wherein the drug delivery device comprises, at the proximal end, one or more finger flanges extending radially outward.
Clause 13. The drug delivery device of clause 11 or clause 12, wherein the displaceable element arranged at the distal end of the housing is configured to move proximally by contacting the flange.
Clause 14. A method of monitoring timing of medicament delivery, comprising: providing a syringe, comprising: a syringe proximal end having one or more finger flanges extending radially outward; a syringe distal end; a syringe sidewall therebetween defining a syringe interior configured to receive a medicament; and a plunger device received at least partially within the syringe interior, the plunger device comprising: a proximal end; a distal end configured to be attached to or to be in contact with a stopper; a housing arranged at the proximal end of the plunger device, comprising a displaceable proximal end, a housing distal end comprising a displaceable element, and a housing sidewall therebetween defining a housing interior; a first switch and a second switch arranged in the housing interior; at least one processor arranged in the housing interior and in communication with the first switch and the second switch; and at least one communication interface arrange in the housing interior and in communication with the at least one processor; receiving, with the at least one processor, a first signal indicating that the first switch has been activated; generating, with the at least one processor, first time data; transmitting, with the at least one communication interface, the first time data; receiving, with the at least one processor a second signal indicating that the second switch has been activated; generating, with the at least one processor, second time data; and transmitting, with the at least one communication interface, the second time data.
Clause 15. The method of clause 14, wherein the first switch is activated by displacement of the proximal end of the housing and the second switch is activated by displacement of the displaceable element.
The following description is provided to enable those skilled in the art to make and use the described embodiments contemplated for carrying out the invention. Various modifications, equivalents, variations, and alternatives, however, will remain readily apparent to those skilled in the art. Any and all such modifications, variations, equivalents, and alternatives are intended to fall within the spirit and scope of the present invention.
For purposes of the description hereinafter, the terms “upper”, “lower”, “right”, “left”, “vertical”, “horizontal”, “top”, “bottom”, “lateral”, “longitudinal”, and derivatives thereof shall relate to the invention as it is oriented in the drawing figures. However, it is to be understood that the invention may assume various alternative variations, except where expressly specified to the contrary. It is also to be understood that the specific devices illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments of the invention. Hence, specific dimensions and other physical characteristics related to the embodiments disclosed herein are not to be considered as limiting.
It should be understood that any numerical range recited herein is intended to include all values and sub-ranges subsumed therein. For example, a range of “1 to 10” is intended to include all sub-ranges between (and including) the recited minimum value of 1 and the recited maximum value of 10, that is, having a minimum value equal to or greater than 1 and a maximum value of equal to or less than 10.
As used herein, the terms “communication” and “communicate” refer to the receipt or transfer of one or more signals, messages, commands, or other type of data. For one unit (e.g., any device, system, or component thereof) to be in communication with another unit means that the one unit is able to directly or indirectly receive data from and/or transmit data to the other unit. This may refer to a direct or indirect connection that is wired and/or wireless in nature. Additionally, two units may be in communication with each other even though the data transmitted may be modified, processed, relayed, and/or routed between the first and second unit. For example, a first unit may be in communication with a second unit even though the first unit passively receives data and does not actively transmit data to the second unit. As another example, a first unit may be in communication with a second unit if an intermediary unit processes data from one unit and transmits processed data to the second unit. It will be appreciated that numerous other arrangements are possible. Any known electronic communication protocols and/or algorithms can be used such as, for example, TCP/IP (including HTTP and other protocols), WLAN (including 902.11a/b/g/n and other radio frequency-based protocols and methods), analog transmissions, Global System for Mobile Communications (GSM), 3G/4G/LTE, BLUETOOTH, NFC, RFID, ZigBee, EnOcean, TransferJet, Wireless USB, and the like known to those of skill in the art. In some non-limiting embodiments, a message may refer to a network packet (e.g., a data packet and/or the like) that includes data.
As used herein, the term “computing device” may refer to one or more electronic devices configured to process data. A computing device may, in some examples, include the necessary components to receive, process, and output data, such as a processor, a display, a memory, an input device, a network interface, and/or the like. A computing device may be a mobile device. As an example, a mobile device may include a cellular phone (e.g., a smartphone or standard cellular phone), a portable computer, a wearable device (e.g., watches, glasses, lenses, clothing, and/or the like), a personal digital assistant (PDA), and/or other like devices. A computing device may also be a desktop computer or other form of non-mobile computer.
Provided herein are a plunger for a drug delivery device, a drug delivery device including such a plunger, and systems and methods including use of such a plunger, for monitoring delivery of a medicament with the drug delivery device. The devices, systems, and methods described herein improve upon traditional devices and methods of determining administration of medicaments, by enabling timely and accurate monitoring of drug delivery by relevant stakeholders in a cost-effective manner, improving, for example, clinical trials for newly-developed medicaments.
Referring to
Drug delivery device 100 can be formed of any suitable material, including glass or plastics. Barrel 110 can be coated with any known coating(s), as appropriate to decrease friction between components and/or reduce interactions between the material of barrel 110 and any medicaments held within drug delivery device 100, including polydimethylsiloxane-based coatings that are optionally crosslinked. Coatings for decreasing friction between a stopper and sidewall and/or for reducing interactions between the sidewall and the medicament, for example siloxane-based coatings, are known to those of skill in the art, and are described in, for example, U.S. Patent Application Publication Nos. 2014/0221934 and 2014/0110297, the contents of which are incorporated herein by reference in their entirety.
In non-limiting embodiments or aspects, drug delivery device 100 includes a needle (not shown) at a distal end thereof. Suitable needles can be of any useful gauge, can be formed of any suitable material, and can be fixed to distal end 112 of drug delivery device 100, or can be removable. Drug delivery device 100 can include any number of suitable safety features, including a rigid needle shield (RNS) for protecting any needles that may be included, a cap 115, and/or a safety device 118, such as that shown in
Returning to
Referring to
Stopper 205 can optionally be coated with any known coating(s), as appropriate, including polydimethylsiloxane-based coatings that are optionally crosslinked. Coatings for decreasing friction between a stopper and sidewall and/or for reducing interactions between the material of the stopper and the medicament, for example siloxane-based coatings, are known to those of skill in the art, and are described in, for example, U.S. Patent Application Publication Nos. 2014/0221934 and 2014/0110297, the contents of which are incorporated herein by reference in their entirety.
Plunger device 200 can include at proximal end 206 thereof a connection module 250, having a housing 252 having a proximal end 254 and a distal end 256 defining an interior. Connection module housing 252 can be formed of any suitable material, including plastics. In non-limiting embodiments or aspects, proximal end 254 of housing 252 includes a displaceable thumb pad 258, such that when a user applies a distally-directed force thereto during a drug delivery procedure, thumb pad 258 and/or proximal end 254 of housing 252 is displaced distally. As will be described, proximal end 254 of housing 252 can interact with a switch within housing 252 to indicate initiation of drug delivery.
In non-limiting embodiments or aspects, plunger device 200 can include a case 251, to protect connection module 250 and, for example, prevent a force from acting on thumb pad 258 and/or proximal end 254 of housing 252 and inadvertently displacing proximal end 254 of housing 252.
Referring to
One or more circuit boards 264, 266 can be supported in interior of housing 252 with a carrier 262, which in non-limiting embodiments or aspects is secured to, and/or is a part of, housing 252. In non-limiting embodiments or aspects, connection module 250 includes an energy source, such as a battery 282. In non-limiting embodiments or aspects, battery 282 can be disposable or rechargeable, depending on whether plunger device 200 is a single-use device, or is reusable. In non-limiting embodiments in which the plunger device 200 is a single-use device, housing 252 can be configured to prevent separation of any portions of housing 252, to prevent a user from accessing interior of housing 252. In non-limiting embodiments or aspects in which plunger device 200 is a single-use device, housing 252 may be openable to allow for a user to remove one or more components (e.g., battery 282 and/or circuit boards 262, 266) for appropriate disposal. In non-limiting embodiments in which plunger device 200 is a reusable device, housing 252 can be configured to be openable to allow for maintenance and/or replacement of battery 282. In non-limiting embodiments, housing 252 is openable only with use of a particular tool. In non-limiting embodiments or aspects in which plunger device 200 is a reusable device, battery 282 may be a rechargeable battery, and housing 252 may include one or more ports to allow for the battery 282 to be recharged.
At distal end 254 of housing 252, communication module 250 can include a displaceable element 270. Displaceable element 270 can include one or more legs 272, one or more arms 274, and a body connecting the leg(s) 272 and arm(s) 274. Displaceable element 270 is maintained in a position where arm(s) 274 are spaced from second switch 268 by resilient biasing element 280. Resilient biasing element 280 can be a spring, such as a compression spring, or other resilient material, such an elastomer and/or a foam.
With reference to
Following receipt of a signal from first switch 260, a processor may then generate first time data, such as a timestamp, and transmit the first time data to a computing device, such as a user's smartphone, smartwatch, tablet, laptop computer, desktop computer, or other computing device as described in greater detail below. In non-limiting embodiments or aspects, a processor enables storing data (e.g., time data) locally (e.g., on circuit board(s) 264 and/or 266), for later retrieval and transmission. In non-limiting embodiments or aspects, processor also transmits one or more unique identifiers, for example an identifier associated with drug delivery device 100 and/or plunger device 200. In non-limiting embodiments or aspects, the identifier is a unique identifier for each drug delivery device 100 and/or plunger device 200 that is manufactured. In non-limiting embodiments or aspects, the identifier is an identifier that is unique to a particular type of device (e.g., a syringe, an autoinjector, a wearable injector, a pump, etc.).
With reference to
For increased accuracy in reporting, during drug delivery the processor must receive both a signal from first switch and from second switch, to provide time data sufficient to allow determination of at least duration of drug delivery. As noted above, devices are known that merely provide an indication of the end of a drug dose, but such devices are insufficient in terms of providing complete information that is critical in, for example, clinical trials.
Referring now to
Drug delivery device 800, which can be a syringe, autoinjector, wearable injector, and/or pump as described herein, can include, as described above, plunger rod 810 including first switch 820, second switch 830, processor 840, and communication interface 850. As described above, drug delivery device 800 can be configured to communicate with a user device 802, such as a computing device as described herein.
Communication network 806 may include one or more wired and/or wireless networks. For example, communication network 806 may include a BLUETOOTH connection (e.g., between drug delivery device 800 and user device 802), a cellular network (e.g., a long-term evolution (LTE) network, a third generation (3G) network, a fourth generation (4G) network, a fifth generation (5G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the public switched telephone network (PSTN) and/or the like), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, and/or the like, and/or a combination of some or all of these or other types of networks.
User device 802 can be a computing device as described herein, in some non-limiting embodiments or aspects, a smartphone. User device 802 can be programmed or configured to communicate, for example through communication network 806, with a healthcare system 804, for example through a mobile application executable on user device 802.
Healthcare system 804 may include a server, a group of servers, and/or other like devices. More than one healthcare system 804 can be provided, for example, a system associated with a device manufacturer, a system associated with a pharmaceutical manufacturer, a system associated with a healthcare provider, a system associated with clinical research, a system associated with a government agency, and/or a system associated with a study sponsor, for example a sponsor of a clinical trial.
Referring now to
Bus 902 may include a component that permits communication among the components of computing device 900. In some non-limiting embodiments, processor 904 may be implemented in hardware, software, or a combination of hardware and software. For example, processor 904 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), and/or the like), a microprocessor, a digital signal processor (DSP), and/or any processing component (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and/or the like) that can be programmed to perform a function. Memory 906 may include random access memory (RAM), read-only memory (ROM), and/or another type of dynamic or static storage memory (e.g., flash memory, magnetic memory, optical memory, and/or the like) that stores information and/or instructions for use by processor 904.
Storage component 908 may store information and/or software related to the operation and use of computing device 900. For example, storage component 908 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, and/or the like), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of computer-readable medium, along with a corresponding drive.
Input component 910 may include a component that permits computing device 900 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, and/or the like). Additionally or alternatively, input component 910 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, and/or the like). Output component 912 may include a component that provides output information from a computing device (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), and/or the like).
Communication interface 914 may include a transceiver-like component (e.g., a transceiver, a separate receiver, and transmitter, etc.) that enables device to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 914 may permit computing device 900 to transmit and/or receive information from another device. For example, communication interface 914 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi® interface, a cellular network interface, BLUETOOTH interface, and/or the like. In non-limiting embodiments or aspects, communication interface 914 does not operate through near field communication. Suitable communication protocols and methods for securing communications between communication interface 914 and a communication interface of another device, such as a computing device (e.g., desktop computer, laptop computer, smartphone, smart watch, PDA, tablet, etc.,) can include encryption, e.g., using a secure socket layer (SSL) (e.g., by using public/private key pairs as are known in the art). Additional security protocols are disclosed in, for example, U.S. Pat. Nos. 9,445,264 and 9,463,325, the contents of which are hereby incorporated by reference in their entirety. In non-limiting embodiments described herein, a communication interface 914 is provided on the plunger rod. In non-limiting embodiments or aspects, communication interface 914 is configured to transmit data, but is not configured to receive data transmitted by a computing device, for example a user's smartphone.
A computing device may perform one or more processes described herein. A computing device may perform these processes based on processor 904 executing software instructions stored by a computer-readable medium, such as memory 906 and/or storage component 908, and/or being instructed by a separate computing device. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A non-transitory memory device includes memory space located inside of a single physical storage device or memory space spread across multiple physical storage devices.
Software instructions may be read into memory 906 and/or storage component 908 from another computer-readable medium or from another device via communication interface 914. When executed, software instructions stored in memory 906 and/or storage component 908 may cause processor 904 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, embodiments described herein are not limited to any specific combination of hardware circuitry and software.
With reference to
In non-limiting embodiments or aspects, plunger device 810 is in one-way communication with a user's computing device 802, e.g., the plunger device 810 can only transmit data to the user device 802, and cannot receive data from the user device 802. In non-limiting embodiments or aspects, a processor associated with user device 802 can be programmed or configured, for example based on a mobile application stored in memory and/or storage component, to place communication interface associated with user device 802 in a sleep mode, until communication interface 850 transmits data from plunger device 810.
As described above, in non-limiting embodiments or aspects, upon a user depressing the thumb pad at proximal end of plunger device 810, first switch 820 is activated. As first switch 820 is in communication with processor 840, processor 840 receives a first signal from first switch 820, generates first time data, and transmits, with communication interface 850, first time data, optionally with one or more identifiers (e.g., a device identifier and/or an identifier associated with the communication interface 850), to user device 802. In non-limiting embodiments or aspects, additional data, such as data relating to power level of the battery, a counter value, and/or other data relating to the functioning of drug delivery device 800. In non-limiting embodiments or aspects, first time data and/or one or more identifiers are encrypted before being transmitted to user device 802. In non-limiting embodiments or aspects, processor accepts the data transmitted by communication interface 850 of drug delivery device 800 only if certain conditions are met. In non-limiting embodiments or aspects, the one or more conditions can include that any message received from drug delivery device 800 includes one or more of an identifier associated with the communication interface 850, an identifier associated with the drug delivery device 800, and/or a first identifier (associated, for example, with first signal), associated with activation of the first switch 820. In non-limiting embodiments, the message received from drug delivery device upon activation of first switch 820 is accepted by user device 802 if, following a check, the message is the first transmitted message including the first identifier, indicating that the message has not previously been transmitted by drug delivery device 800. In non-limiting embodiments or aspects, the message is accepted by user device 802 if, following a check, the combination of the first identifier and an identifier associated with the drug delivery device 800 and/or communication interface 850 has not previously been transmitted to user device 802.
In non-limiting embodiments or aspects, drug delivery device 800 continuously transmits data during a drug delivery process. In non-limiting embodiments or aspects, because each message transmitted during the drug delivery process would include the first identifier associated with activation of the first switch 820, user device 802 can be programmed or configured to not accept subsequent message(s) that include the first identifier. In non-limiting embodiments or aspects, once first identifier has been received, user device 802 terminates any connection with plunger device 810, and connection is not reestablished until a second identifier is included in a transmitted message, as described below. In non-limiting embodiments or aspects, user device 802 can, with a processor (e.g, processor 904), generate a first timestamp from the first time data, and may transmit the first timestamp (optionally with one or more identifiers associated with drug delivery device 800 as described herein) to healthcare system 804. In non-limiting embodiments or aspects, when first timestamp is transmitted to healthcare system 804, user device 802 terminates any connection with plunger device 810.
As also described above, upon reaching the end of the drug delivery process, the second switch 830 is activated. As second switch 830 is in communication with processor 840, processor 840 receives a signal from second switch 830 generates second time data, and transmits, with communication interface 850, second time data, optionally with one or more identifiers (e.g., a device identifier and/or an identifier associated with the communication interface 850), to user device 802. In non-limiting embodiments or aspects, second time data and/or one or more identifiers are encrypted before being transmitted to user device 802. As discussed above, in non-limiting embodiments or aspects, processor accepts the data transmitted by drug delivery device 800 only if certain conditions are met. In non-limiting embodiments or aspects, the one or more conditions can include that any message received from drug delivery device 800 includes one or more of an identifier associated with the communication interface 850, an identifier associated with the drug delivery device 800, and/or a second identifier associated with activation of second switch 830. In non-limiting embodiments, the message received from drug delivery device upon activation of second switch 830 is accepted by user device 802 (and, in non-limiting embodiments, communication is reestablished between drug delivery device 800 and user device 802) because such message is the first transmitted message including the second identifier, indicating that the message has not previously been transmitted by drug delivery device 800. In non-limiting embodiments or aspects, user device 802 can, with a processor (e.g, processor 904), generate a second timestamp from the second time data, and may transmit the second timestamp (optionally with one or more identifiers associated with drug delivery device 800 as described herein) to healthcare system 804. In non-limiting embodiments or aspects, when second timestamp is transmitted to healthcare system 804, user device 802 terminates any connection with plunger device 810.
In non-limiting embodiments or aspects, based at least partially on and at least partially in response to receipt of the data (first time data and/or second time data), user device 802 can, with a processor (e.g, processor 904), generate a final timestamp. For example, first time data and second time data generated by drug delivery device 800 may include only absolute time information, from which user device 802 may generate final timestamp data (e.g., a time at which the drug delivery process began and ended) and/or duration data (e.g., a duration of the drug delivery process).
In non-limiting embodiments or aspects, user device 802 transmits final timestamp and/or duration data to healthcare system 804 (optionally with one or more identifiers associated with drug delivery device 810 as described herein). In non-limiting embodiments or aspects, healthcare system can verify the timestamp data and/or duration data, for example by comparing the timestamp data and/or duration data to predetermined ranges/values for each. In non-limiting embodiments or aspects, data falling outside of the predetermined ranges can be marked for follow up, or a message can be sent to user device 802 noting the issue.
In non-limiting embodiments or aspects, healthcare system 804 may be in communication with one or more additional healthcare systems 804. For example, one healthcare system may be maintained by the device manufacturer, and may be in communication with a healthcare system maintained by a study sponsor, pharmaceutical manufacturer, or the like. In non-limiting embodiments or aspects, timestamp (first timestamp, second timestamp, and/or final timestamp) and/or duration data, together with one or more identifiers (e.g., a device identifier and/or an identifier associated with the communication interface 850), may be transmitted from device manufacturer system to study sponsor or pharmaceutical manufacturer system, where one or more databases may store data associating the one or more identifiers (e.g., a device identifier and/or an identifier associated with the communication interface 850) with a patient identifier, allowing for association of timestamp and/or duration data with the patient.
Although the present disclosure has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred embodiments or aspects, it is to be understood that such detail is solely for that purpose and that the present disclosure is not limited to the disclosed embodiments or aspects, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present disclosure contemplates that, to the extent possible, one or more features of any embodiment can be combined with one or more features of any other embodiment.
| Number | Date | Country | Kind |
|---|---|---|---|
| 21306140.1 | Aug 2021 | EP | regional |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2022/073551 | 8/24/2022 | WO |
