Disposable pen syringe for integrated recording using NFC communication
Through the communication coupling between disposable pen syringes and device hosting applications, the use of NFC circuits and conductive pattern detection technology to automatically manage diabetes treatment, solving the cumbersome recording and error risks caused by manual input of data in the prior art, achieving more accurate and Safe insulin injection.
Patent Information
- Application Number
- CN202280094689.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-10
- Publication Date
- 2024-11-19
AI Technical Summary
Existing diabetes treatment options rely on manual data input, resulting in cumbersome recording and error-prone, increasing the risk of injection errors and imbalance in blood sugar control, and inability to effectively manage and control patients' insulin treatment.
Through the communication coupling of disposable pen syringes and device hosting applications, dynamically control and manage patient treatment injections, using NFC circuits and conductive pattern detection technology, automatically capture, store, analyze and transmit drug dose information, providing electronic management and management Control frame.
Reliance on patient logbooks is reduced, the accuracy and safety of injection doses is improved, the risk of errors is reduced, and automated management and control of diabetes treatment is achieved.
Smart Images

Figure CN118985029A_ABST
Abstract
Description
[0001] This application contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure as it appears in the Patent and Trademark Office files or records, but otherwise reserves all copyright rights whatsoever. Technical Field
[0002] The present disclosure relates to disposable pen injectors, and more particularly to disposable pen injectors communicatively coupled to a device-hosted application configured with functionality for dynamically controlling and managing medication infusions for a patient. Background Art
[0003] Diabetes is a group of diseases characterized by high blood sugar levels due to defects in insulin production and / or insulin action. Currently, 37.3 million people in the United States have diabetes, accounting for 11.3% of the total population. Diabetes can lead to serious complications and premature death.
[0004] Treatment options for diabetes include special diets, oral medications, and / or insulin therapy, with the primary goal of controlling a patient's blood glucose (sugar) levels. Summary of the invention
[0005] In accordance with one or more embodiments, a method is disclosed for a disposable pen injector communicatively coupled with a device-hosted application that enables dynamic control, management, and administration of therapeutic injections for a patient.
[0006] According to some embodiments, the method involves a device establishing an electronic connection with an injection pen, wherein the electronic connection enables information to be communicated between the device and the injection pen, and the injection pen is configured to administer an injection of a drug to a patient. The device then receives first state information of the injection pen via the electronic connection, the first state information indicating a current position of a plunger within a pen body of the injection pen and a timestamp. The device analyzes the first state information and then determines a recommended dose of the drug, including a timing for administering a certain amount of the drug in the future. The device then communicates information related to the recommended dose to the patient.
[0007] According to some embodiments, the method further involves the device receiving second status information of the injection pen, wherein the second status information indicates a position of the plunger within the pen body of the injection pen at a time associated with administration of the recommended dose.
[0008] In some embodiments, the method further involves the device analyzing the second status information based on the first status information, and then determining by the device whether the recommended dose is correctly administered via the injection pen.
[0009] In some embodiments, the device outputs a notification to the patient based on determining that the recommended dose was administered.
[0010] In some embodiments, the device monitors communications from the injection pen, wherein the receiving of the second status information is based on the monitoring.
[0011] In some embodiments, the location of the first state information and the second state information is based on the location of the conductive trace detected from the conductive pattern on the plunger.
[0012] In some embodiments, the recommended dosage also includes information related to the type of drug.
[0013] In some embodiments, the method further comprises the device communicating information related to the recommended dose to the injection pen via an electronic connection, and then adjusting the dosage capacity on the injection pen according to the amount of the recommended dose based on the communication.
[0014] In some embodiments, communicating includes displaying the recommended dosage on a display of the device.
[0015] In some embodiments, the information is communicated at a time corresponding to the timing of the recommended dosage.
[0016] In some embodiments, the electronic communication is near field communication (NFC), and the injection pen is configured with NFC circuitry.
[0017] According to one or more embodiments, the present disclosure provides a non-transitory computer-readable storage medium for executing the above-mentioned improved materialized view matching technical steps. The non-transitory computer-readable storage medium has computer-readable instructions tangibly stored thereon or tangibly encoded thereon, which, when executed by a device, causes at least one processor to perform a method that communicatively couples a disposable pen injector with a device-hosted application that enables dynamic control, management, and administration of a patient's therapeutic injection.
[0018] According to one or more embodiments, a system is provided, the system comprising one or more computing devices and / or apparatuses (e.g., disposable pen injectors) configured to provide functionality according to such embodiments. According to one or more embodiments, the functionality is implemented in steps of a method performed by at least one computing device and / or apparatus. According to one or more embodiments, program code (or program logic) executed by (one or more) processors of a computing device to implement functionality according to one or more such embodiments is implemented in, by, and / or on a non-transitory computer-readable medium.
[0019] According to one or more embodiments, an injection pen is disclosed. In some embodiments, the injection pen includes a plunger and a pen body.
[0020] In some embodiments, the plunger includes a printed conductive pattern on at least one side of the plunger.
[0021] In some embodiments, the pen body includes a metal spring, a voltage collection terminal (VCC), an analog-to-digital converter (ADC), and an NFC circuit. According to some embodiments, the metal spring is configured to interact with the printed conductive pattern. In some embodiments, VCC connects the metal spring and the ADC. In some embodiments, the ADC is configured to receive the analog conductive trace from the interaction between the metal spring and the printed conductive pattern via VCC and convert it into digital information. And, in some embodiments, the NFC circuit is configured to receive digital data from the ADC and communicate the digital data to an external device via an NFC connection.
[0022] Additional and / or other aspects and advantages of the present disclosure will be set forth in the description which follows, or will be obvious from the description, or may be learned by practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Features and advantages of the present disclosure will become apparent from the following description of the embodiments shown in the accompanying drawings, in which reference numerals refer to the same parts throughout the various views. The drawings are not necessarily drawn to scale, emphasis instead being placed on illustrating the principles of the present disclosure:
[0024] Figure 1 is a block diagram of an example configuration in which the systems and methods disclosed herein may be implemented according to some embodiments of the present disclosure;
[0025] Figure 2 is a block diagram illustrating components of an exemplary system according to some embodiments of the present disclosure;
[0026] Figure 3A-3C illustrates an exemplary embodiment of a disposable pen injector according to some embodiments of the present disclosure;
[0027] Figure 4 illustrates an exemplary data flow according to some embodiments of the present disclosure; and
[0028] Figure 5 is a block diagram illustrating a computing device, showing an example of the device used in various embodiments of the present disclosure. DETAILED DESCRIPTION
[0029] The present disclosure will be described more fully below with reference to the accompanying drawings, which form a part of the present disclosure and show certain example embodiments by way of non-limiting illustration. However, the subject matter may be implemented in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be construed as not limited to any example embodiment set forth herein; the example embodiments are provided for illustrative purposes only. Likewise, the scope of the subject matter claimed or covered should be quite broad. For example, among other things, the subject matter may be implemented as a method, device, component, or system. Thus, the embodiments may, for example, take the form of hardware, software, firmware, or any combination thereof (except the software itself). Therefore, the following detailed description is not intended to be understood as limiting.
[0030] Throughout the specification and claims, terms may have nuanced meanings that are suggested or implied by the context beyond their explicitly stated meanings. Likewise, the phrase "in one embodiment" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment" as used herein does not necessarily refer to a different embodiment. For example, the claimed subject matter is intended to include combinations of all or part of the example embodiments.
[0031] In general, terms can be understood at least in part from the usage in the context. For example, terms such as "and", "or" or "and / or" as used herein can include multiple meanings, which can depend at least in part on the context in which such terms are used. Usually, if "or" is used for an association list, such as A, B or C, it is intended to represent A, B and C (here used in an inclusive sense), as well as A, B or C (here used in an exclusive sense). In addition, the term "one or more" as used herein, which depends at least in part on the context, can be used to describe features, structures or characteristics in any single sense, or can be used to describe a combination of features, structures or characteristics in a plural sense. Similarly, terms such as "one" or "the" can be understood to express singular usage or plural usage, which depends at least in part on the context. In addition, the term "based on" can be understood to not necessarily be intended to represent a set of exclusive factors, but can allow the presence of additional factors that are not necessarily explicitly expressed, which also depends at least in part on the context.
[0032] Unless otherwise limited, the terms "connected", "coupled", "mounted" and their variations are used broadly herein and cover direct and indirect connections, couplings and mountings. In addition, the terms "connected" and "coupled" and their variations are not limited to physical or mechanical connections or couplings. In addition, terms such as "upper", "lower", "bottom", "top", "front", "rear", "upper", "lower", "upward", "downward" and other orientation descriptors are intended to facilitate the description of the exemplary embodiments of the present disclosure, and are not intended to limit the structure of the exemplary embodiments of the present disclosure to any particular position or orientation. Those skilled in the art understand that degree terms such as "substantially" or "approximately" refer to a reasonable range of ranges around and including a given value and outside a given value, for example, general tolerances associated with the manufacture, assembly and use of an embodiment. When referring to a structure or characteristic, the term "substantially" includes most or all of the characteristics present in the characteristic or structure.
[0033] The present disclosure is described below with reference to the block diagram and operation diagram of method and equipment.It should be understood that each square block of the block diagram or operation diagram, and the combination of the square blocks in the block diagram or operation diagram can be realized by analog or digital hardware and computer program instructions.These computer program instructions can be provided to the processor of a general-purpose computer to change its function, special-purpose computer, ASIC or other programmable data processing device described in detail in this article, so that the instruction execution via the processor of the computer or other programmable data processing device realizes the function / action specified in the block diagram or one or more operation square blocks.In some alternative implementations, the function / action marked in the square block may not occur in the order marked in the operation diagram.For example, depending on the function / action involved, the two square blocks displayed continuously can actually be basically executed concurrently, or these square blocks can sometimes be executed in reverse order.
[0034] For the purposes of this disclosure, a non-transitory computer-readable medium (or one or more computer-readable storage media) stores computer data, which may include computer program code (or computer-executable instructions) in a machine-readable form that can be executed by a computer. As an example and not limitation, a computer-readable medium may include a computer-readable storage medium for tangible or fixed storage of data, or a communication medium for transient interpretation of a signal containing code. As used herein, a computer-readable storage medium refers to physical or tangible storage (as opposed to a signal) and includes, but is not limited to, volatile and non-volatile, removable and non-removable media for tangible storage of information such as computer-readable instructions, data structures, program modules or other data implemented in any method or technology. Computer-readable storage media include, but are not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid-state memory technology, optical storage, cloud storage, magnetic storage devices, or any other physical or material medium that can be used to tangibly store desired information or data or instructions and can be accessed by a computer or processor.
[0035] For purposes of this disclosure, the term "server" should be understood to refer to a service point that provides processing, database, and communication facilities. By way of example and not limitation, the term "server" may refer to a single physical processor with associated communications and data storage and database facilities, or it may refer to a networked or clustered complex of processors and associated network and storage devices, together with operating software and one or more database systems and application software that support the services provided by the server. A cloud server is an example.
[0036] For purposes of this disclosure, a "network" should be understood to refer to a network that can couple devices so that communications can be exchanged, such as between a server and a client device or other types of devices, including, for example, between wireless devices coupled via a wireless network. The network may also include mass storage, such as, for example, a network attached storage (NAS), a storage area network (SAN), a content delivery network (CDN), or other forms of computer or machine-readable media. The network may include the Internet, one or more local area networks (LANs), one or more wide area networks (WANs), wired type connections, wireless type connections, cellular, or any combination thereof. Similarly, subnets that may employ different architectures or may conform to or be compatible with different protocols may also interoperate within a larger network.
[0037] For the purposes of this disclosure, a "wireless network" should be understood as coupling a client device to a network. A wireless network may employ an independent ad hoc network, a mesh network, a wireless LAN (WLAN) network, a cellular network, etc. A wireless network may also employ a variety of network access technologies, including Wi-Fi, Long Term Evolution (LTE), WLAN, wireless router (WR) mesh, or 2nd, 3rd, 4th, or 5th generation (2G, 3G, 4G, or 5G) cellular technology, mobile edge computing (MEC), Bluetooth, 802.11b / g / n, etc. The network access technology may enable wide area coverage for devices such as, for example, client devices with varying degrees of mobility.
[0038] In short, a wireless network may include virtually any type of wireless communication mechanism by which signals may be transmitted between devices, such as client devices or computing devices, between networks or within a network, and so forth.
[0039] The computing device may be capable of sending or receiving signals, such as via a wired or wireless network, or may be capable of processing signals or storing signals as physical memory states, such as in a memory, and thus may operate as a server. Thus, a device capable of operating as a server may include, for example, a dedicated rack-mounted server, a desktop computer, a laptop computer, a set-top box, an integrated device combining various features (such as two or more features of the above devices), etc.
[0040] For purposes of this disclosure, a client (or consumer or user) device, referred to as user equipment (UE), may include a computing device capable of sending or receiving signals, such as via a wired or wireless network. Client devices may include, for example, desktop computers or portable devices such as cellular phones, smart phones, display pagers, radio frequency (RF) devices, infrared (IR) devices, near field communication (NFC) devices, personal digital assistants (PDAs), handheld computers, tablet computers, tablet phones, laptop computers, set-top boxes, wearable computers, smart watches, integrated or distributed devices combining various features (such as those of the aforementioned devices), etc.
[0041] The client devices (UE) may vary in capabilities or features. The claimed subject matter is intended to cover a variety of potential variations, such as a web-enabled client device or the aforementioned device may include a high-resolution screen (e.g., HD or 4K), one or more physical or virtual keyboards, mass storage, one or more accelerometers, one or more gyroscopes, a global positioning system (GPS) or other location recognition type capability, or a display with a high degree of functionality, such as, for example, a touch-sensitive color 2D or 3D display.
[0042] The principles of the disclosed embodiments of the disclosed systems and methods will now be discussed in greater detail.
[0043] As background, diabetes treatments, including multiple daily injections (MDIs), insulin pens (with or without applicable pen injectors), patch pumps, and insulin pumps, are not configured with the ability and / or functionality to automatically determine and record information related to the dosage of medication delivered to a patient. Existing mechanisms for providing diabetes treatment rely on a history of manually entered data, which is typically provided by the patient (and / or in some cases by a healthcare provider (HCP)). That is, for example, daily records of (1) insulin dosage, (2) medication intake and available reservoir, and (3) blood glucose measurements (BGM) are currently available only from limited sources, including settings on the insulin pen, occasional readings from the BGM meter, and estimates of carbohydrates in a meal, all of which are determined by the patient and transferred to a logbook or diary.
[0044] These methods of recording data are cumbersome and prone to errors and omissions. For example, injecting the wrong dose and / or wrong type of prescribed insulin, or not taking the correct dose (if taken at all) can lead to serious health complications (e.g., diabetic coma) or even death.
[0045] Current solutions require third-party software to reconfigure manually entered data to assess trends and support treatment modifications. However, this still relies on the patient's logbook, which, even in an ideal situation, is still prone to human error (e.g., misreading current insulin levels, administering the wrong dose or wrong type of medication, etc.). As a result, such current solutions increase the risk of non-adherence to prescribed therapy and uneven glycemic control, and their reliance on diligent use by patients in managing their prescribed therapy precludes their use as a viable option for managing and controlling the administration of diabetes therapy.
[0046] The systems and methods disclosed herein address these and other shortcomings and provide an improved computerized framework for electronically managing and controlling a patient's therapy. According to some embodiments, the disclosed systems and methods are configured to automatically capture, store, analyze, update, transmit, and enable optimal evaluation of data required to properly administer diabetes therapy.
[0047] As is apparent from the discussion herein, the disclosed framework operates to eliminate strict reliance on a patient logbook via a novel disposable pen injector into which a dose recording capability is integrated for controlling the administration of a prescribed therapy to a patient. In some embodiments, the disclosed systems and methods operate via interaction between a disposable pen injector and an application (e.g., a therapy control application) executed on a patient device (e.g., a smartphone, for example). As discussed below, the disposable pen injector is configured with circuitry in a novel manner that enables electronic connection and communication with the therapy control application. In some embodiments, as discussed below, the circuitry integrated on the disposable pen injector may be, but is not limited to, an NFC circuit.
[0048] In some embodiments, as discussed in more detail below, the disposable pen injector is configured to provide the therapy control application with information related to (but not limited to) the remaining capacity of the disposable pen, information related to the last dose (or a set of previous doses) administered to the patient, the type of dose present in the pen, etc. As discussed in more detail below, upon receiving such data, which may be communicated from the pen to the patient device via NFC functionality, the therapy control application may analyze the information and dynamically determine information related to the next dose, such as (but not limited to) the amount and / or type of the next dose, past, present, and / or future dosage patterns, the timing of prescription refills, the amount of medication available, etc. In some embodiments, the therapy control application may also be configured to provide notifications or alerts to the user to remind them of the timing of the next dose, an incorrect dose, a missed dose, the timing of refilling a certain type of prescription, etc., or some combination thereof.
[0049] Go to Figure 1 , depicts a system (or framework) 100 that includes a UE 500 (e.g., a client device as described above), a network 102, a cloud system 104, and a therapy control engine 200. The UE 500 may be any type of device, such as, but not limited to, a mobile phone, a tablet, a laptop, a personal computer, a sensor, an Internet of Things (IoT) device, an autonomous machine, and any other device equipped with a cellular or wireless or wired transceiver. Figure 5 Let's discuss UE 500 further.
[0050] like Figure 1 As shown in FIG. 1 , UE 500 may be communicatively connected to pen injector 300 (also referred to as injection pen, medication pen, insulin pen, or pen, which may be used interchangeably). Pen 300 may communicate directly with UE 500 via a set of communication protocols that enable two electronic devices to interact within a certain distance. For example, as described below with respect to at least Figure 3A-4As discussed, the pen 300 may be configured with NFC circuitry that enables an NFC connection with the UE 500. According to some embodiments, other forms of distance-based communication (as discussed above) may be used, such as but not limited to RF, IR, or Bluetooth Low Energy (BLE), in addition to any other type of known or to-be-known communication protocol, without departing from the scope of the present disclosure.
[0051] In some embodiments, the pen 300 can communicate with the UE 500 via the network 102 (eg, Figure 1 100 and the network 102). The network 102 may be any type of network, such as, but not limited to, a wireless network, a cellular network, the Internet, etc. (as discussed above). As discussed herein, the network 102 may facilitate the connection of components of the system 100, such as Figure 1 Thus, for example, in some embodiments, the pen 300 may establish a wireless connection with the UE 500 via the network 102 .
[0052] Pen 300 is a device for injecting or administering a drug subcutaneously to a patient (e.g., a human or person). As will be appreciated by those skilled in the art, injection pens (such as pen 300) are typically used for drugs that are injected repeatedly by a person over a relatively short period of time, e.g., insulin and insulin analogs for treating diabetes.
[0053] It should be understood that while the discussion herein will focus on embodiments directed to an insulin pen, it should not be construed as limiting as the pen injector (e.g., pen 300) can be used for any type of drug administration related to, but not limited to, high cholesterol, migraine prevention, and other monoclonal antibodies related to other types of metabolic disorders and prescribed therapies that are known or to become known.
[0054] At least the following Figure 3A-4 Non-limiting examples of configurations and functionality of the pen 300 are discussed.
[0055] The cloud system 104 can be any type of cloud operating platform and / or network-based system on which applications, operations, and / or other forms of network resources can be located. For example, the system 104 can be a service provider, a network provider, and / or a medical provider from which services and / or applications can be accessed, obtained, or executed. In some embodiments, the cloud system 104 can include (one or more) servers and / or information databases accessible via the network 102. In some embodiments, a database (not shown) of the cloud system 104 can store data sets of data and metadata associated with (one or more) users of the UE 500 and the UE 500, as well as services and applications provided by the cloud system 104 and / or the therapy control engine 200.
[0056] As discussed in more detail below, the therapy control engine 200 includes components for communicating information between the UE 500 and the pen 300 and dynamically determining and directing therapeutic control of a patient's prescribed medication. That is, for example, the engine 200 can enable the UE 500 to receive insulin dosage information from the pen 300, determine prescribed compliance and schedule according to the prescription, and effectively manage the patient's use of the pen 300, as discussed below.
[0057] According to some embodiments, therapy control engine 200 may be a dedicated machine or processor and may be hosted by a device on network 102, within cloud system 104, and / or on UE 500. In some embodiments, engine 200 may be hosted by a peripheral device connected to UE 500.
[0058] According to some embodiments, therapy control engine 200 may be provided as an application provided by cloud system 104. In some embodiments, engine 200 may be provided as an application installed on UE 500. In some embodiments, such an application may be a web-based application (e.g., such as a web application) accessed by UE 500 from cloud system 104 via network 102. Figure 1 In some embodiments, the engine 200 may be configured and / or installed as an enhancement script, program, or application (e.g., a plug-in or extension) of another application or program provided by the cloud system 104 and / or executed on the UE 500.
[0059] like Figure 2 As shown in , according to some embodiments, the therapy control engine 200 includes an injection pen module 202, a dosage module 204, a determination module 206, and a communication module 208. It should be understood that the engine(s) and modules discussed herein are not exhaustive, as more or fewer engines and / or modules (or sub-modules) may be applicable to embodiments of the systems and methods discussed.
[0060] The following will refer to Figure 3A-4 Further details of the operation, configuration, and functionality of the engine 200 and each of its modules are discussed, as well as their roles in embodiments of the present disclosure.
[0061] Figures 3A-3C A non-limiting embodiment of a pen 300 is illustrated. For example, the pen 300 may be a pen injector, such as, but not limited to, a BD Vystra™ Pen.
[0062] According to some embodiments, Figure 3A illustrates a view of a pen 300 and the components it includes for performing the capabilities and functions discussed herein; Figure 3Billustrates a non-limiting example of the configuration and operation of the components of the pen 300; and Figure 3C Another non-limiting example of the configuration and operation of the components of pen 300 is illustrated.
[0063] Go to Figure 3A , the pen 300 includes a plunger button 302 , a plunger 304 , a printed (or etched) conductive pattern 306 , a leaf spring 308 (eg, a metal contact), an NFC circuit (or chip or antenna) 310 , a pen body (or chamber) 312 , and a dose selection dial 314 .
[0064] In some embodiments, the plunger button 302 can be configured as a portion of the plunger 304 that is designed to fit and move within the pen body 312. The plunger button 302 can be configured to enable a patient to press the plunger 304 through the pen body 312 and within the pen body 312 to inject a dose (e.g., insulin) into the patient. The plunger 304 can act as a piston configured at the proximal end of the pen body 312, with the dose selection dial 314 located at the distal end. The plunger 304 can enable the capture and output of the drug contained in the pen body 312 through the distal end via a hollow cannula or needle (not shown).
[0065] In some embodiments, plunger 304 may be configured as an automatic injector, which may not require the patient (or user) to press plunger button 302 to inject a dose. As discussed below, such automatic injections may be performed via NFC circuit 310 from a connected device (e.g., UE 500, as discussed above with respect to Figure 1 The therapy control application performed on the device (as discussed) is controlled by information received.
[0066] In some embodiments, the conductive (or resistive) pattern 306 may be printed on the body of the plunger 304, such as Figure 3A In some embodiments, the conductive pattern 306 may include a conductive ink created by injecting graphite or other conductive material into the ink and then printing it onto the plunger 304. Thus, the printed conductive pattern 306 provides a conductive (or resistive) trace that indicates the location or depth of the plunger 304 relative to the pen body 312 (e.g., the degree of depression of the plunger 304 within the pen body 312, and / or an indication of the movement of the plunger 304 within the pen body 312).
[0067] In some embodiments, the conductive pattern 306 may alternatively be the product of etching of a copper or plated substrate, or any other known or to-be-known stamping or etching technique, where a conductivity / resistance measurement or trace may be obtained from a plunger within the body of a disposable pen (e.g., an RFID tag, circuit traces, etc., for example).
[0068] In some embodiments, the conductive pattern 306 can be detected by a metal contact (referred to as a leaf spring 308) positioned with the pen body 312. In some embodiments, the leaf spring 308 can be metal or another material that can interact with the conductive pattern 306 and provide a voltage, current, or other form of conductive / resistive trace that can be read, as discussed in more detail below.
[0069] In some embodiments, the plunger 304 can be configured with a predetermined set of leaf springs 308 to interact with (e.g., via rubbing against) the conductive pattern 306 on the plunger 304 and detect conductive / resistive traces in the conductive pattern 306 on the plunger 304. In some embodiments, the number of leaf springs 308 can correspond to the number of patterns 306 on the plunger 304. For example, if the plunger 304 has two conductive patterns 306 that are 180 degrees apart on the plunger 304, then there can be two (2) leaf springs 308 positioned within the pen body 312 (e.g., Figure 3C ) to interact with pattern 306 positioned on plunger 304.
[0070] In some embodiments, the conductive trace detected by the leaf spring 308 can be fed or transmitted to the NFC circuit 310. Figure 3B and 3C Discuss more details.
[0071] In some embodiments, the pen body 312 can be a chamber, or can include a cartridge (or other type of reservoir) that can contain a medication. As discussed above, by passing the plunger 304 through the pen body 312, the medication can be injected into the patient. In some embodiments, the pen body 312 can be configured to contain medication. In some embodiments, for a reusable version of the pen 300, the pen body 312 can be refillable; and in some embodiments, the pen body 312 can be configured to contain a replaceable cartridge that can be loaded into or removed from the pen body 312 so that the pen 300 itself can be reused.
[0072] In some embodiments, the dose selection dial 314 can be configured to enable accurate dose measurement, such that adjustments can be made via radial adjustment of the dial according to the measurement indicated on the dial 314. In some embodiments, the dial 314 can include an audible click or other known or to-be-known method to confirm dose adjustments.
[0073] Go to Figure 3B, provides a view of the pen 300 , which is a schematic internal view of the pen 300 , which includes a plunger button 302 , a plunger 304 , a printed conductive pattern 306 , a leaf spring 308 , an NFC circuit 310 , an analog-to-digital converter (ADC) 316 , and a voltage collection terminal (VCC) 318 .
[0074] According to some embodiments, as the plunger 304 passes through the pen body 312, the conductive pattern 306 and the leaf spring 308 interact with each other, thereby recording a conductive / resistive trace that is detected by the VCC 318 and communicated to the ADC 316. The VCC 318 communicates the detected conductive / resistive trace to the ADC 316 so that the movement and / or position of the plunger 304 can be detected, which can indicate the amount of drug remaining, the amount of the dose administered, etc., or some combination thereof, as discussed above and discussed in more detail below.
[0075] According to some embodiments, Figure 3B The VCC 318 in the stylus pen 312 can detect and record the conductive / resistive traces and provide voltage information to the ADC 316. The ADC 316, which is configured to act as a digital input / output (DIO) interface of the NFC circuit 310, receives the analog voltage data and converts it into digital data, which is then passed to the NFC circuit 310. In some embodiments, the ADC 316 can be configured as an integrated circuit within the stylus pen 312 that is coupled to the NFC circuit 310 and enables the NFC circuit 310 to understand the analog readings obtained from the movement of the plunger 304.
[0076] As mentioned above, and at least with regard to Figure 4 As discussed in more detail below, the digital data passed to the NFC circuit 310 may then be communicated to a connected device (e.g., UE 500, as described above with respect to Figure 1 In addition, the connected device (e.g., UE 500) can communicate calibration information to the pen 300 via the NFC circuit 300, as discussed below. Further discussion of the conductive / resistive data captured, analyzed, compiled, and utilized will be discussed in more detail below.
[0077] exist Figure 3C , another non-limiting view of the pen 300 is provided, which is a schematic internal view of the pen 300, including the above Figure 3A and 3B Components discussed. Figure 3C Two leaf springs 308 are shown positioned to interact with two conductive patterns 306 along opposite sides of the plunger 304. Each leaf spring 308 has a VCC 318 connected thereto or located near a conductive portion of the spring 308 for detecting the conductive / resistive trace in the leaf spring 308 that interacts with the corresponding conductive pattern 306. Thus, as Figure 3C As shown in , each VCC 318 enables a trace (eg, an analog voltage) to be fed to an ADC 316 , which then provides a digital reading to the NFC circuit 310 .
[0078] Therefore, if Figure 3A-3B As shown in , and below about Figure 4 As discussed in more detail, the disclosed systems and methods can detect the initial position of the plunger 304 (e.g., before a dose is administered), the subsequent position of the plunger 304 (e.g., after a dose is administered), whether a dose is administered (e.g., whether the plunger has moved from a last position), the speed of movement of the plunger 304 (e.g., whether a dose is administered in an appropriate manner—e.g., depressing the plunger 304 at a speed exceeding a threshold speed may indicate that the correct dose of medication was not captured and / or was not delivered to the patient via injection), etc., or some combination thereof. As discussed below, this information can be communicated to and from the injection pen 300 and a therapy control application executing on the patient device (UE 500), thereby enabling accurate and correct administration of the prescribed medication.
[0079] Figure 4 A process 400 is provided that details a non-limiting example embodiment of a disposable pen injector communicatively coupled with a device hosted application to dynamically control and manage patient injections.
[0080] According to some embodiments, steps 402 - 404 and 412 may be performed by the injection pen module 202 of the therapy control engine 200 ; steps 406 and 414 may be performed by the dosage module 204 ; step 410 may be performed by the communication module 208 ; and steps 408 and 416 may be performed by the determination module 206 .
[0081] Process 400 begins at step 402, where the engine 200 receives a request associated with an injection pen to establish an electronic connection with a device. Figure 1-3C As discussed, for example, the engine 200 may correspond to a therapy control application executed on the UE 500 (eg, a patient's smartphone, for example), and the injection pen 300 may communicate with the UE 500 using the internal NFC circuit 300 .
[0082] In step 404, an electronic connection may be established between the injection pen and the device in response to the request from step 402. Thus, for example, step 404 may involve the pen 300 being located at or within a predetermined distance of the UE 500, whereby an NFC connection may be established between the two devices. According to some embodiments, any type of known or to-be-known method for establishing an NFC connection between at least two devices may be performed without departing from the scope of the present disclosure.
[0083] In step 406 , the engine 200 receives information related to the current status of the injection pen. The received status information is sent by the injection pen 300 to the therapy control application executed on the UE 500 via the NFC circuit 310 .
[0084] According to some embodiments, the status information may include, but is not limited to, the current position of the plunger 304 within the pen body 312 and a timestamp. As discussed below, this information may provide an indication of the amount of medication remaining in the pen, as well as the type of medication and the current time associated with the pen / plunger reading.
[0085] According to some embodiments, as described above at least with respect to Figures 3A-3C As discussed, the location within the conductive pattern 306 where the leaf spring 308 interacts can serve as a basis for state information. That is, for example, the location where the leaf spring 308 contacts the conductive pattern 306 provides an indication of the positioning of the plunger 304.
[0086] In some embodiments, the contact of the leaf spring can provide a resistance measurement to the NFC circuit 310 via the VCC 318, which is then communicated to the UE 500. In some embodiments, the ADC 316 can compile a measurement of the plunger 304 based on the information received by the VCC 318. That is, the ADC 316 can output a binary value (e.g., a preset interval) along the plunger, which either indicates that the leaf spring is in contact with the pattern 306 (e.g., 1) or that they are not in contact (e.g., 0). As a non-limiting example, if the pattern 306 on the plunger 304 has 5 detectable locations where the leaf spring 308 can contact, and the contact is in a position where half of the drug has been used, then the ADC can return a string of digital values indicating: 00100, which indicates that the spring 308 interacts with the middle portion of the pattern 306 on the plunger 304.
[0087] Upon receiving the status information of the pen, the engine 200 may analyze the status information and determine a recommended dose to be administered via the injection pen in step 408. The recommended dose includes information indicating how much medication to take (eg, amount) and the timing (in the future) of when to take the dose.
[0088] According to some embodiments, the analysis performed by engine 200 may involve any type of known or to-be-known machine learning (ML) and / or artificial intelligence (AI) analysis, including algorithms, techniques, classifiers and / or mechanisms, such as but not limited to Bayesian network analysis, hidden Markov models, artificial neural network analysis, logical models and / or tree analysis, etc.
[0089] According to some embodiments, the determination of step 408 may not be limited to determining a recommended dose, as the determination may also include other forms of dosage information, such as but not limited to how much drug is remaining in the pen, the type of drug, the dosage administration mode, etc. or some combination thereof, as discussed above.
[0090] Thus, in some embodiments, steps 406-408 may involve the engine 200 receiving pen status information (e.g., the current position of the plunger within the syringe pen) and then determining the time, amount, and / or type of the patient's next dose to be administered via the pen. In some embodiments, the dose information determined at step 408 may also or alternatively be related to the patient's predicted pattern / schedule—that is, rather than simply determining the next dose, step 408 may involve the engine 200 determining the patient's complete schedule that complies with the prescription information (e.g., take X amount of Y drug every 4 hours for 10 days, for example).
[0091] In some embodiments, the determined dosage information may be stored in an associated data storage device for later retrieval and / or communication to a pen and / or other device or display screen for notification to the user. For example, the dosage information may be stored locally on the UE 500 and / or in a database associated with the cloud system 104, as described above with respect to Figure 1 discussed.
[0092] In step 410, once the recommended dosage for the patient has been determined, information related to the recommendation is communicated to the patient for use. In some embodiments, the communication may involve a display on a screen of the UE 500 (and / or associated with an interface of a therapy control application executed thereon) indicating the recommended dosage information (e.g., amount and / or time). In some embodiments, the communication may involve a display on a peripheral device connected to the UE 500 (e.g., a smartwatch connected to the patient's smart phone).
[0093] In some embodiments, the communication may be sent at a determined time, at a time consistent with a recommended dosage, at a time according to settings set by the patient, etc., or some combination thereof.
[0094] According to some embodiments, in addition to displaying information, other forms of notifications may also be conveyed to the patient in addition and / or alternatively, which may include but are not limited to messages (e.g., SMS or email), sounds, vibrations (e.g., haptic effects), etc., or some combination thereof.
[0095] In some embodiments, step 410 may involve communicating the dosage information directly to the injection pen via the NFC connection. According to some embodiments, such communication may enable the injection pen to automatically configure the administration settings for the next dose according to the recommended dose as determined in step 408. For example, for a digitally capable injection pen, such communication may cause the dial 314 to automatically adjust the dosage amount indicated according to the recommended dose.
[0096] In step 412, the engine 200 monitors the administration of the recommended dose (and the communicated dose) via the NFC connection established with the injection pen. According to some embodiments, the engine 200 may analyze the incoming signal of the pen 300 communicated by the NFC circuit 310 and determine whether another dose has been administered. In some embodiments, this may involve determining whether the plunger 304 has changed position (which may be performed in a manner similar to that discussed above with respect to step 406).
[0097] In some embodiments, the NFC circuit 310 may be configured to send a signal to the UE 500 only when the plunger 304 moves (at least a threshold distance to account for collisions and / or other types of involuntary movements). In this case, the absence of a signal received from the pen 300 may indicate to the engine 200 that such a dose has not been administered, and such monitoring of step 412 may continue.
[0098] In some embodiments, the monitoring of step 412 may be performed in accordance with the timing of the recommended next dose. For example, if the next dose is recommended to be administered via the pen 300 in 6 hours, then at a predetermined time close to 6 hours (e.g., 10 minutes before, for example), the engine 200 may begin to periodically monitor the NFC signal from the pen 300.
[0099] In some embodiments, the monitoring in step 412 (and step 414 as discussed below) may require re-establishing the NFC connection so that the process of steps 402-404 may be repeated to achieve the monitoring and information reception discussed herein.
[0100] In step 414, the engine 200 receives information related to the administration of the recommended dose (e.g., an update of status information associated with the injection pen 300). This information is received in a manner similar to that discussed above with respect to step 406. Thus, the information received in step 414 may include, but is not limited to, the current position of the plunger 304 and a timestamp.
[0101] In step 416, the engine 200 compiles information related to a set of next injections (eg, the next dose and / or schedule of doses). This compilation may be performed in a manner similar to that discussed above with respect to steps 406-408.
[0102] In some embodiments, step 416 may also involve determining whether the dose administered was administered correctly. For example, the distance the plunger changes (from steps 406-414) may be analyzed and used to determine whether the correct amount of medication was administered. In some embodiments, the timestamp may also be analyzed and used to determine whether the dose was administered at the correct time.
[0103] In some embodiments, the updated dosage information compiled from the information received in step 414 in step 416 can be used to update the stored information for the patient (which is stored as a subprocess of step 408, as discussed above). In some embodiments, such updating of the patient dosage information can also include updating dosage mode information, as discussed above.
[0104] According to some embodiments, the engine 200 may be configured to periodically update the patient's stored dosage information. That is, in some embodiments, the engine 200 may automatically update the dosage information based on the predicted / expected dosage, rather than updating the dosage information based on the dosage information received from the pen 300. This may account for situations where an NFC connection cannot be enabled (e.g., the patient is not near their smartphone). Thus, the engine 200 is able to track the patient's compliance with the prescription as a safety measure to prevent improper dosage, improper injection, etc.
[0105] Process 400 also involves recursively proceeding from step 416 to step 410 to track the administration of the medication according to the recommended dosage determined by the steps of process 400 .
[0106] Figure 5 is a block diagram illustrating a computing device 500 (eg, UE 500 as discussed above), showing an example of a client device or a server device used in various embodiments of the present disclosure.
[0107] The computing device 500 may include Figure 5 500, depending on the deployment or use case of device 500. For example, a server computing device (such as a rack-mount server) may not include audio interface 552, display 554, keyboard 556, illuminator 558, tactile interface 562, GPS receiver 564, or camera / sensor 566. Some devices may include additional components not shown, such as a graphics processing unit (GPU) device, a cryptographic coprocessor, an artificial intelligence (AI) accelerator, or other peripheral devices.
[0108] like Figure 5As shown in FIG. 5 , the device 500 includes a central processing unit (CPU) 522, which communicates with a mass storage 530 via a bus 524. The computing device 500 also includes one or more network interfaces 550, an audio interface 552, a display 554, a keyboard 556, an illuminator 558, an input / output interface 560, a tactile interface 562, an optional GPS receiver 564 (and / or an interchangeable or additional GNSS receiver), and (one or more) cameras or other optical, thermal or electromagnetic sensors 566. The device 500 may include one camera / sensor 566 or multiple cameras / sensors 566. The positioning of the (one or more) cameras / (one or more) sensors 566 on the device 500 may vary depending on the device 500 model, the device 500 capabilities, etc., or some combination thereof.
[0109] In some embodiments, CPU 522 may include a general-purpose CPU. CPU 522 may include a single-core or multi-core CPU. CPU 522 may include a system on chip (SoC) or a similar embedded system. In some embodiments, a GPU may replace CPU 522 or be used in combination with CPU 522. Mass storage 530 may include a dynamic random access memory (DRAM) device, a static random access memory device (SRAM) or a flash memory (e.g., NAND flash) memory device. In some embodiments, mass storage 530 may include a combination of these memory types. In one embodiment, bus 524 may include a peripheral component interconnect express (PCIe) bus. In some embodiments, bus 524 may include multiple buses instead of a single bus.
[0110] Mass storage 530 illustrates another example of computer storage media for storing information such as computer readable instructions, data structures, program modules or other data. Mass storage 530 stores a basic input / output system (“BIOS”) 540 for controlling low-level operations of computing device 500. Mass storage also stores an operating system 541 for controlling the operation of computing device 500.
[0111] Application 542 may include computer executable instructions that, when executed by computing device 500, perform any of the methods (or portions of methods) described in the description of the previous figures. In some embodiments, software or programs implementing method embodiments may be read by CPU 522 from a hard drive (not shown) and temporarily stored in RAM 532. CPU 522 may then read the software or data from RAM 532, process it, and store it again in RAM 532.
[0112] Computing device 500 may optionally communicate with a base station (not shown) or directly with another computing device.Network interface 550 is sometimes referred to as a transceiver, transceiver device, or network interface card (NIC).
[0113] Audio interface 552 generates and receives audio signals, such as the sound of human speech. For example, audio interface 552 can be coupled to a speaker and microphone (not shown) to enable telephone communication with others or to generate an audio confirmation of an action. Display 554 can be a liquid crystal display (LCD), gas plasma, light emitting diode (LED), or any other type of display used with a computing device. Display 554 can also include a touch screen that is arranged to receive input from an object such as a stylus or a finger of a human hand.
[0114] Keyboard 556 may include any input device arranged to receive user input. Illuminator 558 may provide a status indication or provide light.
[0115] The computing device 500 also includes an input / output interface 560 for communicating with external devices using communication technologies such as USB, infrared, Bluetooth™, etc. A tactile interface 562 provides tactile feedback to a user of the client device.
[0116] The optional GPS transceiver 564 can determine the physical coordinates of the computing device 500 on the surface of the earth, which typically outputs the location as latitude and longitude values. The GPS transceiver 564 can also use other geolocation mechanisms, including but not limited to triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS, etc., to further determine the physical location of the computing device 500 on the surface of the earth. However, in one embodiment, the computing device 500 can communicate through other components and provide other information that can be used to determine the physical location of the device, including, for example, a MAC address, an IP address, etc.
[0117] For purposes of this disclosure, a module is a software, hardware, or firmware (or combination thereof) system, process, or function, or component thereof (with or without human interaction or enhancement) that performs or facilitates the processes, features, and / or functions described herein. A module may include submodules. The software components of a module may be stored on a computer-readable medium for execution by a processor. A module may be integrated into one or more servers, or loaded and executed by one or more servers. One or more modules may be grouped into engines or applications.
[0118] For purposes of this disclosure, the terms "user," "subscriber," "consumer," or "client" should be understood to refer to a user of one or more applications as described herein and / or a consumer of data provided by a data provider. By way of example, and not limitation, the term "user" or "subscriber" may refer to a person who receives data provided by a data or service provider over the Internet in a browser session, or may refer to an automated software application that receives data and stores or processes the data.
[0119] Those skilled in the art will recognize that the methods and systems of the present disclosure can be implemented in a variety of ways and are therefore not limited by the foregoing exemplary embodiments and examples. In other words, in various combinations of hardware and software or firmware, functional elements performed by single or multiple components and individual functions can be distributed in software applications at the client level or the server level or both. In this regard, any number of features of the different embodiments described herein can be combined into a single or multiple embodiments, and alternative embodiments with less than or more than all the features described herein are possible.
[0120] Functionality may also be distributed in whole or in part among multiple components in ways now known or unknown. Thus, a large number of software / hardware / firmware combinations are possible in implementing the functions, features, interfaces, and preferences described herein. Furthermore, the scope of the present disclosure encompasses conventionally known ways to perform the described features and functions and interfaces, as well as those changes and modifications that may be made to the hardware or software or firmware components described herein, as now and later understood by those skilled in the art.
[0121] In addition, the embodiments of the methods presented and described as flow charts in the present disclosure are provided by way of example in order to provide a more complete understanding of the present technology. The disclosed methods are not limited to the operations and logical flows presented herein. Alternative embodiments are contemplated in which the order of the various operations is changed and in which sub-operations described as part of a larger operation are performed independently.
[0122] Although various embodiments have been described for the purposes of this disclosure, such embodiments should not be construed to limit the teachings of this disclosure to those embodiments. Various changes and modifications may be made to the above elements and operations to obtain results that remain within the scope of the systems and processes described in this disclosure.
Claims
1. A method comprising the following steps: establishing, by the device, an electronic connection with an injection pen, the electronic connection enabling communication of information between the device and the injection pen, the injection pen being configured to administer an injection of medication to a patient; receiving, by the device via the electronic connection, first status information of the injection pen, the first status information indicating a current position of the plunger in the body of the injection pen and a timestamp; analyzing, by the device, the first status information, and determining a recommended dosage of the drug based on the analysis, the recommended dosage including a future timing for administering a certain amount of the drug; as well as Communicate information related to recommended dosage to patients via the device.
2. The method of claim 1, further comprising: Second status information of the injection pen is received by the device, the second status information indicating a position of the plunger within the body of the injection pen at a time associated with administration of the recommended dose.
3. The method of claim 2, further comprising: analyzing, by the device, the second status information based on the first status information; The device determines whether the recommended dose has been correctly administered via the pen.
4. The method of claim 3, further comprising: A notification is output to the patient by the device based on the determination that the recommended dosage was administered.
5. The method of claim 2, further comprising: Communications from the injection pen are monitored by the device, wherein the receipt of the second status information is based on said monitoring. 6 . The method of claim 1 , wherein the locations of the first state information and the second state information are based on locations of conductive traces detected from the conductive pattern on the plunger. The method of claim 1 , wherein the recommended dosage further includes information related to the type of drug.
8. The method of claim 1 , further comprising: communicating, by the device via the electronic connection, information relating to the recommended dose to the injection pen; as well as Based on the communication, the dosage capability on the injection pen is adjusted according to the amount of the recommended dose.
9. The method of claim 1, wherein the communicating comprises displaying the recommended dosage on a display of the device.
10. The method of claim 1, wherein the information is communicated at a time corresponding to the timing of a recommended dose.
11. The method of claim 1 , wherein the electronic communication is near field communication (NFC), and wherein the injection pen is configured with NFC circuitry.
12. An injection pen comprising: a plunger comprising a printed conductive pattern on at least one side of the plunger; as well as A pen body, comprising: a metal spring configured to interact with the printed conductive pattern; Connect the metal spring to the voltage acquisition terminal (VCC) of the analog-to-digital converter (ADC); The ADC is configured to receive analog conductive traces from the interaction between the metal spring and the printed conductive pattern via VCC and convert it into digital information; and A near field communication (NFC) circuit is configured to receive the digital data from the ADC and communicate the digital data to an external device via an NFC connection.
13. A non-transitory computer-readable storage medium tangibly encoded with computer-executable instructions that, when executed by a device, perform a method comprising: establishing, by the device, an electronic connection with an injection pen, the electronic connection enabling communication of information between the device and the injection pen, the injection pen being configured to administer an injection of medication to a patient; receiving, by the device via the electronic connection, first status information of the injection pen, the first status information indicating a current position of the plunger in the body of the injection pen and a timestamp; analyzing, by the device, the first status information, and determining a recommended dosage of the drug based on the analysis, the recommended dosage including a future timing for administering a certain amount of the drug; as well as Communicate information related to recommended dosage to patients via the device.
14. The non-transitory computer-readable storage medium of claim 13, further comprising: receiving, by the device, second status information of the injection pen, the second status information indicating a position of the plunger within the body of the injection pen at a time associated with administration of a recommended dose, analyzing, by the device, the second status information based on the first status information; The device determines whether the recommended dose has been correctly administered via the pen; as well as A notification is output to the patient by the device based on the determination that the recommended dosage was administered. 15 . The non-transitory computer-readable storage medium of claim 13 , wherein locations of the first state information and the second state information are based on locations of conductive traces detected from the conductive pattern on the plunger.
16. The non-transitory computer-readable storage medium of claim 13, further comprising: communicating, by the device via the electronic connection, information relating to the recommended dose to the injection pen; as well as Based on the communication, the dosage capability on the injection pen is adjusted according to the amount of the recommended dose.
17. A device comprising: The processor is configured to: establishing an electronic connection with an injection pen, the electronic connection enabling communication of information between the device and the injection pen, the injection pen being configured to administer an injection of medication to a patient; receiving first status information of the injection pen via the electronic connection, the first status information indicating a current position of the plunger in the body of the injection pen and a timestamp; analyzing the first status information and determining a recommended dosage of the drug based on the analysis, the recommended dosage including a future timing for administering a certain amount of the drug; as well as Communicate information to patients regarding recommended dosages.
18. The apparatus of claim 17, further comprising: Second status information of the injection pen is received, the second status information indicating a position of the plunger within the body of the injection pen at a time associated with administration of a recommended dose. analyzing the second state information based on the first state information; Determine whether the recommended dose is administered correctly via the pen; as well as A notification is output to the patient based on the determination that the recommended dosage was administered.
19. The apparatus of claim 17, wherein the locations of the first state information and the second state information are based on locations of the conductive traces detected from the conductive pattern on the plunger.
20. The apparatus of claim 17, further comprising: communicating information related to the recommended dosage to the injection pen via the electronic connection; as well as Based on the communication, the dosage capability on the injection pen is adjusted according to the amount of the recommended dose.
