Medicament information system and method

This application claims the benefit of <patcit id="pcit0001" dnum="US61732753" dnum-type="L"><text>U.S. Provisional Application No. 61/732,753 filed on Dec. 3, 2012</text></patcit>.

TECHNICAL FIELD

The invention disclosed herein relates to the usage of an emergency medicament device.

BACKGROUND

Some people suffer from medical conditions such as severe allergies that may result in anaphylaxis. Anaphylaxis may be treated by administration of epinephrine. Patients may be prescribed an auto-injector of epinephrine to treat sudden anaphylaxis.

Anaphylaxis, however, often leads to an emergency situation wherein epinephrine or other medication should be administered as soon as possible to prevent loss of life or other complications. Proper use of the auto-injector to treat anaphylaxis is therefore important. Patients with medical conditions that may result in anaphylaxis are often inexperienced at providing medical treatment. Use of an auto-injector may also be intimidating for some patients. Moreover, an emergency situation requiring treatment may arise at unexpected times or after a significant time from receiving the auto-injector and instructions for use from a doctor or pharmacist. Additionally, due to the unpredictable use of the auto-injector, the medicament may expire before the auto-injector is used. An expired medicament may not effectively treat anaphylaxis in an emergency situation. <patcit id="pcit0002" dnum="US20100062748A"><text>US2010/0062748</text></patcit> discloses a device, method and computer software product that are provided for communicating medicine dosage and intake instructions to a user.

SUMMARY

In light of the present need for various contingency planning in the administration of epinephrine and other medications, a brief summary of various exemplary embodiments is presented. Some simplifications and omissions may be made in the following summary, which is intended to highlight and introduce some aspects of the various exemplary embodiments. Detailed descriptions of a preferred exemplary embodiment adequate to allow those of ordinary skill in the art to make and use the inventive concepts will follow in later sections.

Various aspects and embodiments of the invention are set out in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to better understand various exemplary embodiments, reference is made to the accompanying drawings, wherein: <ul id="ul0001" list-style="none"><li><figref idref="f0001">FIG. 1</figref> illustrates an exemplary electronic medicament device;</li><li><figref idref="f0002">FIG. 2</figref> illustrates an exemplary network environment for an electronic medicament device;</li><li><figref idref="f0003">FIG. 3</figref> illustrates a flowchart showing an exemplary method performed by a mobile device; and</li><li><figref idref="f0004">FIG. 4</figref> illustrates a flowchart showing an exemplary method of monitoring a medicament.</li></ul>

DETAILED DESCRIPTION

Referring now to the drawings, in which like numerals refer to like components or steps, there are disclosed broad aspects of various exemplary embodiments.

<figref idref="f0001">FIG. 1</figref> illustrates an exemplary electronic medicament device 100. The electronic medicament device 100 may include a medication for treating a condition, the medication being stored in a reservoir. The electronic medicament device 100 includes an auto-injector for epinephrine or other administration component such as a non-auto-injector needle or controlled access panel for providing access to a solid medication stored in the reservoir. Medicaments 120 may include one or more medicaments for treating emergency or other medical conditions. Medicament device 120 may be auto-injectors for administering a dose of epinephrine. Suitable auto-injectors and associated devices and method are described by <patcit id="pcit0003" dnum="US4031893A"><text>U.S. Pat. Nos. 4,031,893</text></patcit>; <patcit id="pcit0004" dnum="US4394863A"><text>4,394,863</text></patcit>, <patcit id="pcit0005" dnum="US4484910A"><text>4,484,910</text></patcit>; <patcit id="pcit0006" dnum="US4640686A"><text>4,640,686</text></patcit>; <patcit id="pcit0007" dnum="US4678461A"><text>4,678,461</text></patcit>; <patcit id="pcit0008" dnum="US4795433A"><text>4,795,433</text></patcit>; <patcit id="pcit0009" dnum="US4832682A"><text>4,832,682</text></patcit>; <patcit id="pcit0010" dnum="US5085641A"><text>5,085,641</text></patcit>; <patcit id="pcit0011" dnum="US5092843A"><text>5,092,843</text></patcit>; <patcit id="pcit0012" dnum="US5102393A"><text>5,102,393</text></patcit>; <patcit id="pcit0013" dnum="US5354286A"><text>5,354,286</text></patcit>; <patcit id="pcit0014" dnum="US7449012B"><text>7,449,012</text></patcit>; and <patcit id="pcit0015" dnum="US8048035B"><text>8,048,035</text></patcit>.

Medicament device 100 or packaging 160 is imprinted with various medicament information. For example, medicament device 100 may include the name of the medicament, active ingredients, dosage, expiration date, lot ID, and product serialization number. The medicament information may be printed in a manner that is machine-readable. For example, the medicament information may be printed as a quick response (QR) code 170. The medicament information may also be printed as text that is easily recognized using optical character recognition (OCR). Packaging 160 may include a container such as a box or tube as well as any inserts or cards included within the packaging. It should be apparent that any information included on the medicament device 100 may instead be located on packaging 150. As will be discussed in further detail below, the medicament information may also be digitally encoded in a memory 130 of the medicament device.

The electronic medicament device 100 further includes sensor 110, ID tag 120, memory 130, display 140, and speaker 150. Although not illustrated, the electronic medicament device may include additional hardware such as, for example, a processor and/or additional communication interfaces. A processor may interconnect one or more of those components illustrated in <figref idref="f0001">FIG. 1</figref>. Such additional communication interface may include, for example, an interface for communication via wifi, a mobile carrier network, or satellite. Alternatively, the additional communication interface may include a wired communication interface.

Sensor 110 detects activation of electronic medicament device 100. Sensor 110 may include a frangible element that completes or breaks an electronic circuit when electronic medicament device 100 is activated. Sensor 110 provides a signal to ID tag 120 to perform an action in response to use of the medicament. Sensor 110 may alter memory 130 to indicate that the medicament device 100 is used and may log a time of use.

In various embodiments sensor 110 may include a temperature sensor. The temperature sensor may continuously measure the current temperature of the medication. The temperature sensor may provide the current temperature to a processor to compare to approved temperatures. In embodiments where the medication is epinephrine, the approved temperature range may be 15-30° C. An alarm may be generated by display 140 or speaker 150 if the current temperature is outside of the approved temperature range.

In various embodiments, sensor 110 may include a colorimetric sensor capable of determining the color of the medicament. For example, sensor 110 may be a spectrophotometer. The color of the medicament may be indicative of the quality of the medicament. For example, a medicament may turn from clear to pink or brown if the medicament becomes degraded.

ID tag 120 may include an RFID, NFC, or other tag for short range wireless communications. Such tags may be powered by passive energy and not require a battery. In various embodiments, ID tag 120 may include a battery powered wireless transmitter using, for example, Bluetooth. ID tag 120 may provide information from electronic medicament device 100 to a wireless reader such as, for example, wireless reader 140 or a NFC enabled mobile device. ID tag 120 may be connected to or include memory 130. ID tag 120 may be located on packaging 160 rather than medicament device 100.

Memory 130 may store information regarding electronic medicament device 100. Memory 130 may include a non-volatile memory such as a read-only memory (ROM) or an electronically erasable programmable read only memory (EEPROM). Information stored by memory 130 may include manufacture date, expiration date, medication, dose size, audio instructions, text instructions, other instructions, prescription information, re-order information, and emergency contact information.

Display 140 may include a display such as a LCD, LED array, or a single LED. Display 140 may display information about electronic medicament device 100. Display 140 may read and display any information stored in memory 130. For example, display 140 may display the expiration date of the medication. Display 140 may also display instructions for a user. Display 140 may illuminate, flash, or display a particular message in response to particular events such as the expiration of the medication, use of the medicament, or separation from another device such as case or a mobile device 220.

Speaker 150 may provide audio output. For example, speaker 150 may play pre-recorded instructions stored in memory 130. ID tag 120 or another communication interface (not shown) may download or stream information from another device to be played by speaker 150. For example, the electronic medicament device 100 may stream information from an application server 250 or from a remote operator, either directly or via a mobile device 220

The electronic medicament device 100 may be reusable. As such, the electronic medicament device 100 may receive a disposable cartridge or component set including the medication and/or a clean needle. Such cartridge or component set may include its own RFID tag or other means for communicating an expiration date or other information to the electronic medicament device 100 or mobile device 220.

The processor or other component of the electronic medicament device 100 may alter the operation of the electronic medicament device 100 based on user information or other information. For example, the electronic medicament device 100 may provide different dosages based on a dosage prescribed to an authorized user. As another example, a user may input a patient weight, height, and/or body mass index (BMI) into a keypad of the electronic medicament device 100 or input information into a mobile device 220 and wirelessly transmit the user information to the medicament device 100. The processor may then calculate and administer an appropriate dosage based on the input factors. As another example, the processor may prevent or disable medicine administration when the user is not authorized for such administration.

<figref idref="f0002">FIG. 2</figref> illustrates an exemplary network environment 200 for electronic medicament device 100. Electronic medicament device 100 may interact with various elements of network environment 200 to provide emergency access and enhanced features. Network environment 200 may include network 205, GPS satellites 210, mobile device 220, mobile base station 225, wireless router 230, medical server 240, central control 250, and emergency services 260.

Network 205 may be a digital network for communicating information. For example, network 205 may be the internet. Network 205 may transmit information between various end users and devices. Network 205 may also include telephone networks.

GPS satellites 210 may enable electronic medicament device 100, mobile device 220, and other devices to determine their respective physical locations. GPS satellites 210 may be geosynchronous satellites that broadcast signals. GPS enabled devices may use the signals from multiple satellites to determine their location. GPS satellites 210 may include or be replaced by terrestrial location systems. For example, wi-fi access points may be used to detect the physical location of a device.

Mobile device 220 may be a device such as a smart phone, tablet computer, laptop, or any other computing device capable of executing applications and performing communication. Mobile device 220 is an NFC enabled mobile phone that can communicate using short range wireless protocols as well as local networking and mobile networks. In particular, mobile device 220 may communicate with a mobile network using mobile base station 225. Mobile device 220 may include location detecting services such as GPS.

Mobile device 220 may interact with the electronic medicament device 100 using RFID, NFC, or other wireless communication. Mobile device 220 may read medicament information that is either printed on medicament device 100 or stored in memory 130. For example, mobile device 220 may include a camera and application configured to read a QR code or printed text. Mobile device 220 may also read data from the memory 130 using a short-range wireless protocol such as RFID, NFC or Bluetooth. The short-range wireless communication may also be used by mobile device 220 to determine the presence of a medicament device 100. For example, mobile device 220 may periodically attempt to read the medicament device 100 and determine that the medicament device 100 is not present if the mobile device 220 is unable to read the medicament device 100.

Mobile device 220 may include an application specifically for interacting with electronic medicament device 100. Mobile device 220 may access memory 130 via ID tag 120 and read or write data. Mobile device 220 may detect changes in electronic medicament device 100 and perform actions in response. For example, mobile device 220 may detect that electronic medicament device 100 has been activated. Mobile device 220 may automatically contact emergency services 260 and allow a user to speak with emergency personnel, or mobile device 220 may provide a pre-recorded message to emergency services 260 indicating that the medicament has been activated to treat a condition of the patient. Mobile device 220 may also provide a location based on GPS information so that emergency personnel can locate the patient. The application may also interact with server 250 to provide additional medicament related information and services. For example, the application may provide disease information and news, medicament registration, reminders, product accessory information, medicament insert and patient information, and local allergy information.

ID tag 120 is used to determine whether electronic medicament device 100 is within close proximity to a mobile device 220. ID tag 120 periodically polls or is polled by a wireless reader in the mobile device 220. If the poll does not occur when expected, or the mobile device does not respond, electronic medicament device 100 may generate an alert. For example, electronic medicament device 100 may play a sound through the speaker 150 or flash the display 140 to alert a user. The alert may remind the user to keep the medicament close by in case of emergency. Mobile device 220 generates an alert if electronic medicament device 100 is not detected. Mobile device 220 may be configured to check for the presence of electronic medicament device 100 whenever the user enters or leaves a particular location. For example, mobile device 220 may generate an alert if a user leaves home without the electronic medicament device.

The ID tag 120 is used to actively search for electronic medicament device 100. Mobile device 220 is configured to transmit a signal to ID tag 120 upon activation by a user. The signal is received by ID tag 120 and causes the speaker 150 to produce an audible sound. The volume or pitch of the sound varies depending on the strength of the received signal. Alternatively, mobile device 220 may detect a signal reflected by an ID tag 120 such as a passive RFID tag. Mobile device 220 may play an audible sound and vary the volume or pitch depending on the strength of the reflected signal.

Mobile device 220 may also contact emergency contacts. For example, mobile device 220 may email, message, or call any emergency contacts stored in memory 130 or within mobile device 220 when the electronic medicament device 100 is used or generates some other alert. Mobile device 220 may select contacts based on time of day or other available information.

Upon detection of an expired medicament or activation of the medicament, mobile device 220 may initiate ordering a replacement medicament Mobile device 220 may send an order to either control center 250 or medical server 240. The order may include patient and prescription information. Medical server 240 may determine whether the prescription includes refills, whether replacements are allowed without a prescription, or whether the patient has a valid or perpetual prescription for the medicament. Medical server 240 may automatically fulfill the order if the prescription is authorized. Alternatively, medical server 240 may schedule an appointment with the patient's doctor for a new prescription and to follow-up regarding the deployment of the medicament.

Wireless router 230 may be a wireless router providing connectivity to a local area network (LAN) and the internet. Wireless router 220 may be accessed electronic medicament device 100, and mobile device 220. Accordingly, wireless router 220 may provide these devices with internet access to send and receive data.

Medical server 240 may be a server operated by a health care provider, health insurance provider, or government health agency. Medical server 240 may store patient information. Medical server 240 may provide patient information to authorized devices such as the patient's mobile device 220, control center 250, and emergency services 260. Medical server 240 may be configured to receive and process particular messages from electronic medicament device 100, mobile device 220, and control center 250. For example, medical server 240 may be configured to verify prescriptions and order refills.

Application server 250 may be a computer server operated by a medicament manufacturer or other third party. The application server 250 may provide a downloadable application for execution on a mobile device. The application server 250 may also provide support for the downloadable application and/or a web application. The application server 250 may include a database of registered medicament information provided by patients who opt to register the medicament device 100. The application server 250 may provide various services accessible via the application. The application server 250 may provide audio and/or video instructions that may be downloaded or streamed to a mobile device. The application server 250 may provide information to a mobile device based on a registered medicament device. For example, the application server 250 may track expiration dates and provide notification of approaching expiration dates. The application server 250 may provide a tracking system enabling a registered user to track the last known physical location of registered medicament devices.

The electronic medicament device 100 may provide usage information to the application server 250 which, in turn, may process the data for various uses. For example, the application server 250 may provide the processed usage data to an application executing on a mobile device, such as mobile device 220. Such application may provide, for example a map indicating where the user has administered the electronic medicament device 100 and/or other electronic medicament devices 100. Such application could also present a real-time alert as to when the electronic medicament device 100 has been used, including location information. The application may also provide historical data and analysis of electronic medicament device 100 usage events such as event listings and graphs. As another example, the application server 250 may track disposal and/or recycling of medicament device 100. A disposal or recycling facility may scan medicament information including a lot ID and product serialization number from medicament device 100. The disposal or recycling facility may send the scanned medicament information to application server 250 and/or medical server 240 for reconciliation with registered medicament device 100.

<figref idref="f0003">FIG. 3</figref> illustrates a flowchart showing an exemplary method 300 performed by a mobile device 220. Mobile device 220 may include an application configured to cause the processor and other components of mobile device 220 to perform the steps of the method 300. The method 300 may begin at step 305 and proceed to step 310.

In step 310, the mobile device 220 may read medicament information from the medicament device 100. The mobile device 220 may use a camera take a picture of medicament device 100 or the packaging thereof. For example, a user may take a photograph of the expiration date, lot number, and serialization number, or take a photograph of a QR code. The mobile device 220 may analyze the photograph to determine medicament information. The mobile device 220 may also forward the photograph to an application server 250 for analysis. The mobile device 220 may read the medicament information from the memory 130.

In step 315, the mobile device 220 may determine whether a user wishes to register the medicament device 100. The mobile device 220 may present a user interface providing an explanation of the benefits of registration an option to register. The user interface may also provide the ability for the user to enter contact information or to manually enter medicament information. If the user chooses to register the medicament device 100, the method 300 may proceed to step 320. If the user chooses not to register the medicament device 100, the method 300 may proceed to step 350.

In step 320, the mobile device 220 may send medicament information to the server. The mobile device 220 may send medicament information read from the medicament device 100, packaging, and/or memory 130. The mobile device 220 may also send user information entered by the user. The user may update an existing registration with a new medicament device 100. Accordingly, the server 150 may already have user information and only a user identifier may be sent with the medicament information. The mobile device 220 may send the medicament information to medical server 240 in addition to application server 250. For example, a government health agency may collect medicament information. Application server 250 may also forward the medicament information to medical server 240.

In step 325, the mobile device 220 may determine whether the user wishes to register for a location tracking service. As will be described in further detail below, the location tracking service may monitor the location of the medicament device 100 and help a user find the device 100 if it is lost or activated. The mobile device 220 may prompt a user to enter additional information useful for tracking the location of the medicament device 100 such as a phone number of an additional mobile device 220 that may be used to track the medicament device 100. The additional mobile device 220 may be, for example, a mobile device usually carried by a child who has been prescribed the medicament device 100. If the user enables location tracking, the method 300 may proceed to step 330. If the user opts out of location tracking, the method 300 may proceed to step 340.

In step 330, the mobile device 220 may check for the presence of the medicament device. The mobile device 220 may use a short-range wireless communication protocol such as Bluetooth to poll the medicament device. If the medicament device 100 is present, the mobile device 220 may establish a connection with the medicament device 100 and receive additional information.

In step 335, the mobile device 220 may report the location of the medicament device 100 to the server 150. If the mobile device 220 detected the presence of the medicament device 100 in step 330, the mobile device may report the location of the mobile device 220 as the location of the medicament device 100. If the medicament device 100 is not detected, the mobile device 220 may report a missing medicament device having no known location or report the last known location of the medicament device 100.

In step 340, the mobile device 220 may determine whether a user wishes to receive reminders regarding the medicament device 220. The mobile device 220 may present a user interface displaying information regarding available reminders. The user of the mobile device may select those reminders he or she would like to receive. Exemplary reminders regarding a medicament device may include a reminder to replace an expired medicament device, a reminder to review instructions, a reminder to obtain a new prescription, a reminder to perform a medical test, and a reminder to take a periodic dose from the medicament device. The mobile device 220 may send the selected reminders to server 150, which may monitor for events related to the reminders. In step 345, the mobile device 220 may receive a reminder from the server 150 based on medicament information. In The reminder may be received via simple messaging service (SMS), email, or an application based messaging system.

In step 350, the mobile device 220 may determine whether the user wishes to receive instructions. The user may indicate a desire to receive instructions by selecting a button within the application. The mobile device 220 may automatically request instructions based on the user scanning a QR code or taking a picture of the medicament device. If the user desires to receive instructions, the method 300 may proceed to step 355. If the user does not desire to receive instructions, the method 300 may proceed to step 360. In step 355, the mobile device 220 may request the instructions from the server 250. The request may include information identifying the medicament device 100. The request may include only a name or identifier of the medicament device 100 and not particular information such as a lot number, product serialization number, or expiration date. In step 355, the mobile device 220 may receive instructions from server 250. The instructions may be in the form of a video streamed from the application server 240. The instructions may also include audio or written instructions.

In step 360, the mobile device 220 may determine whether the user wishes to receive news regarding the medicament device 100. The user may indicate a desire to receive news by selecting a button within the application. If the user desires to receive news, the method 300 may proceed to step 365. If the user does not desire to receive news, the method 300 may proceed to step 370. In step 365, the mobile device 220 may receive news updates from the server 250. The news updates may be pushed to the mobile device 220 based on the identified medicament device.

In step 370, the mobile device 220 may determine whether the user desires to track a medicament device 100. The tracking service may require registration of the medicament device with server 250. The user may indicate a desire to track a medicament device by selecting a button within the application. Tracking a medicament device 100 may be initiated by an application server 250 in response to an event concerning the device. For example, use of a registered medicament device 100 may be reported to the application server 250 by a patient's mobile device. The application server 250 may then push a notification to another user device 220, such as a device of a parent or other emergency contact, and provide tracking information. If the user desires to track a medicament device 100, the method 300 may proceed to step 375. If the user does not desire to track a medicament device, the method 300 may proceed to step 390, where the method 300 ends.

In step 375, the mobile device 220 may retrieve information regarding registered medicament devices 100 including location information. The mobile device 220 may require the user to enter a password or perform other security operations to ensure only the registered user has access to the medicament device information. The mobile device 220 may present a list of medicament devices 100 registered to the user or may request information regarding all registered medicament devices. The application server 250 may receive the request and extract medicament device information from a database. The application server 250 may also attempt to update the medicament device locations by polling other mobile devices associated with registered medicament devices for current medicament device information.

The mobile device 220 may receive the medicament information from the server 250. The medicament information may include a location, which may be, for example, longitude and latitude coordinates or a street address. The medicament information may also include information such as the current temperature of the medicament device, the time of the last use of the medicament device, and a number of doses remaining in the medicament device. In step 380, the mobile device 220 may present the medicament device information to the user as a map. The map may indicate the current location of the medicament device 100 as well as the current location of the mobile device 220.

<figref idref="f0004">FIG. 4</figref> illustrates a flowchart showing an exemplary method 400 of monitoring a medicament. The method 400 may be performed by a mobile device 220 in communication with an electronic medicament device 100. The method 400 may be performed as step 330 of method 300 illustrated in <figref idref="f0003">FIG. 3</figref>.

The method 400 may begin at step 405 and proceed to step 410. In step 410, the mobile device 220 may determine its location. Mobile device 220 may use the location to determine whether to proceed with the method. For example, the mobile device 220 may discontinue the method if the mobile device is in a designated location, or the mobile device may delay the method until a change in location is detected.

In step 415, the mobile device 220 may detect any electronic medicament devices nearby. Mobile device 220 may use RFID, NFC, Bluetooth or another close range protocol to poll nearby tags 120 on a medicament device. Mobile device 220 may be configured to poll one or more specific electronic medicament devices with identifiers known by mobile device 220. In step 420, mobile device 220 may determine whether an electronic medicament device 100 is present. If no medicament device is present, the method may proceed to step 425. If a medicament device is detected, the method may proceed to step 430.

In step 425, the mobile device 220 may generate an alarm. The alarm may indicate any particular medicament device that was not detected. The alarm may include a message identifying the medicament device by name or by a condition that it treats. If the mobile device performs method 400 frequently, it may be likely that the medicament device is nearby, although out of range of the short range wireless protocol. Accordingly, a user may be reminded to retrieve the medicament device. The mobile device 220 may also generate a message to another mobile device. For example, the mobile device 220 may send an SMS message or email to a parent, guardian, or other emergency contact indicating that the medicament device 100 has been separated from the mobile device 220. The method 400 may then proceed to step 460, where the method ends.

In step 430, the mobile device 220 may receive data from the medicament device. Mobile device 220 may send a read command to read data from memory 130. Mobile device 220 may receive data from the electronic medicament device 100 when sensor 110 determines that the device 100 has been activated. In step 435, mobile device 220 may determine whether the medicament device 100 has been used. Mobile device 220 may determine the status of sensor 110 or parse data received in step 430. If the medicament device has been used, the method may proceed to step 440. If the medicament device has not been used, the method may proceed to step 450.

In step 440, mobile device 220 may document the current location of the mobile device. The location of the mobile device may be used to identify the location of device usage. In step 445, the mobile device may notify emergency contacts. Mobile device 220 may contact emergency services, for example, by dialing 911. The mobile device 220 may turn on a speaker phone to allow a user, who may be suffering from anaphylaxis or another medical condition to speak to an emergency dispatcher. If mobile device 220 does not receive any voice input, mobile device 220 may play a recorded message indicating that the electronic medicament device has been activated at the stored location. Mobile device 220 may also contact other people. For example, mobile device 220 may call, email, or message emergency contacts stored in mobile device 220 or memory 130.

In step 450, mobile device 220 may determine whether the electronic medicament device 100 is expired. Mobile device 220 may compare an expiration date received from the electronic medicament device 100 to the current date. The mobile device 220 may also have the ability to read the quality of the medicament. For example, mobile device 220 may read information from a sensor 110 in medicament device 100. The sensor 110 may determine that the medicament has expired early if, for example, the medicament device 100 was stored at an inappropriate temperature or has changed properties such as colors. The mobile device 220 may be able to determine the quality of the product. For example, the camera of the mobile device may act as a spectrophotometer to measure the color of the medicament. Alternatively, the mobile device 220 may transmit a picture of the medicament device to application server 250 for spectrophotometric analysis. The medicament device 100 may include a transparent window and colored markings to assist with the spectrophotometric analysis. The mobile device 220 may determine that the medicament has expired early if the medicament exhibits a certain property. If the medicament device is expired, the method may proceed to step 455. If the medicament device is not expired, the method may proceed to step 450.

In step 455, the mobile device 455 may initiate an order for a refill or replacement electronic medicament device. Mobile device 220 may send an order to control center 250 and/or medical server 240. The method may then proceed to step 460.

In step 460, the mobile device 220 may update an application server 250 with information regarding the medicament device 220. The application server 250 may use the updated information to provide up to date information to other users associated with a registered medicament device. For example, the updated information may be used to provide the tracking service described above. The updated information may also be used by the application server 250 to generate notifications regarding local conditions such as allergy and asthma alerts. The application server 250 may provide such alerts as news to users who have registered medicament devices for treating the same condition. The method may proceed to step 470, where the method may end.

According to the foregoing, various exemplary embodiments provide for systems and methods for distributing medicaments. In particular, by providing remote access to a medicament storage case, medicaments can be provided to patients in an emergency.

It should be apparent from the foregoing description that various exemplary embodiments of the invention may be implemented in hardware and/or firmware. Furthermore, various exemplary embodiments may be implemented as instructions stored on a machine-readable storage medium, which may be read and executed by at least one processor to perform the operations described in detail herein. A machine-readable storage medium may include any mechanism for storing information in a form readable by a machine, such as a personal or laptop computer, a server, or other computing device. Thus, a machine-readable storage medium may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and similar storage media.

It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative circuitry embodying the principals of the invention. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in machine readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

Although the various exemplary embodiments have been described in detail with particular reference to certain exemplary aspects thereof, it should be understood that the invention is capable of other embodiments and its details are capable of modifications in various obvious respects..