Systems, methods, media, and devices for capturing medication and medication use

Abstract

A system, method, non-transitory computer-readable medium, and / or device for determining medications used by a patient is provided. Label information for the medication may be determined. A source National Drug Code (NDC) associated with the medication may be determined. The source NDC may be verified. A product NDC and normalized identifier may be determined. A brand name associated with the medication may be determined. One or more active ingredients associated with the brand name may be determined. A drug display name may be determined. Active ingredient information for the drug display name and one or more active ingredients may be displayed. A summary showing the amounts of the active ingredients may be displayed, for example, based on a medication diary.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 422,824, filed November 4, 2022, the disclosure of which is incorporated herein by reference in its entirety. [Background technology]

[0002] Medications play a role (e.g., a critical role) for the treatment and management of diseases and symptoms. Patient medication records (e.g., complete and accurate records) can be important for the safe and effective use of medications. However, discrepancies between both recorded and reported medications can be common. Such discrepancies can lead to medication errors. Reducing medication discrepancies and medication errors can be important to achieving medication safety (e.g., greater medication safety). Summary of the Invention [Means for solving the problem]

[0003] A system, method, non-transitory computer-readable medium, and / or apparatus for capturing medications and / or medication use may be provided. For example, a device and / or device-implemented method for determining medications used by a patient may be provided. Label information for the medication may be determined. A first message may be sent to a first server. The first message may indicate a request for a first medication identifier, such as a first national drug code (NDC), that may be associated with the medication. The first message may indicate the label information. The first NDC may be in a first format. A second message may be received from the first server. The second message may indicate the first NDC and may indicate an RxNorm concept unique identifier (RxCUI). The second NDC may be determined using the first NDC. The second NDC may be in a second format. The second format may differ from the first format. A brand name may be determined using the second NDC. One or more active ingredients may be determined using RxCUI. The one or more active ingredients may be associated with a brand name. A drug display name may be determined using the brand name and the one or more active ingredients. Active ingredient information may be determined for the one or more active ingredients. The drug display name and active ingredient information may be displayed to a user, such as a patient.

[0004] A system, method, non-transitory computer-readable medium, and / or apparatus for capturing medications and / or medication use may be provided. For example, a device and / or a method implemented by a device for determining medications and medication use associated with a patient may be provided. Label information for the medication may be determined. A first message may be sent to a first server. The first message may indicate a request for a first medication identifier, such as a first National Drug Code (NDC), that may be associated with the medication. The first message may indicate the label information. The first NDC may be in a first format. A second message may be received from the first server. The second message may indicate the first NDC and may indicate an RxNorm Concept Unique Identifier (RxCUI). The second NDC may be determined using the first NDC. The second NDC may be in a second format. The second format may differ from the first format. The brand name may be determined using the second NDC. One or more active ingredients may be determined using the RxCUI. One or more active ingredients may be associated with a brand name. A drug display name may be determined using the brand name and one or more active ingredients. A use associated with the drug and a user may be determined. The user may be a patient. Active ingredient information may be determined for one or more active ingredients. The drug display name, use, and active ingredient information may be displayed to a user, such as a patient.

[0005] A system, method, non-transitory computer-readable medium, and / or device for capturing medications and / or medication use may be provided. Label information for the medication may be determined. A source National Drug Code (NDC) may be determined using the label information. The source NDC may be associated with the medication. A first message may be sent to a first server. The first message may indicate a request for validation of the source NDC. A second message may be received from the first server. The second message may indicate that the source NDC is valid, may indicate a product NDC, and may indicate a normalized identifier. A brand name associated with the medication may be determined using the product NDC. One or more active ingredients associated with the brand name may be determined using the normalized identifier. A drug display name may be determined using the brand name and one or more active ingredients. Active ingredient information may be determined for the one or more active ingredients. The drug display name and active ingredient information may be displayed to a user.

[0006] A system, method, non-transitory computer-readable medium, and / or device for summarizing medication use associated with a patient may be provided. A first normalized identifier may be determined using a first National Drug Code (NDC). The first normalized identifier may be associated with a first medication. A second normalized identifier may be determined using a second NDC. The second normalized identifier may be associated with a second medication. The first normalized identifier may be used to determine that the first medication includes a first amount of an active ingredient. The second normalized identifier may be used to determine that the second medication includes a second amount of the active ingredient. A medication summary may be displayed. The medication summary may include a drug name associated with the active ingredient and a sum of the first and second amounts of the active ingredient. In an example, the medication summary may be referred to as a dosage summary per active ingredient. [Brief explanation of the drawings]

[0007] [Figure 1] 1 depicts an example functional block diagram of electrical components of an example smart device for capturing medications and / or medication use. [Figure 2A] 1 depicts an example architecture diagram of an example system supporting smart devices. [Figure 2B] FIG. 2 is a messaging flow diagram of an exemplary system. [Figure 3] 1 depicts a block diagram of a system that may include one or more modules (e.g., software modules such as medication information, medication list, and dosage summary) for capturing medications and / or medication use. [Figure 4] 1 depicts an exemplary format for a National Drug Code (NDC). [Figure 5] 1 depicts an exemplary method for capturing medication and / or medication use. [Figure 6] 10 depicts another exemplary method for capturing medication and / or medication use. [Figure 7] 1 depicts an example of information about a medication that may be displayed to a user. [Figure 8] 1 depicts an exemplary method for determining the amount of active ingredient in a medicament. [Figure 9A] 1 depicts an exemplary user interface listing one or more identified medications. [Figure 9B] 1 depicts an exemplary user interface summarizing one or more active ingredients associated with one or more medications. [Figure 9C] 1 depicts an exemplary user interface summarizing one or more active ingredients associated with one or more medications. [Figure 9D] 1 depicts an exemplary user interface that provides a summary of daily dosages of one or more active ingredients associated with one or more medications. [Figure 10] 1 depicts an exemplary user interface listing one or more medications associated with a patient. [Figure 11] 1 depicts an exemplary user interface for capturing medications and / or medication usage. [Figure 12]10 depicts an exemplary user interface for capturing medications and / or medication usage for a medication list. [Figure 13] 10 depicts an exemplary user interface for capturing medications and / or medication usage for drug interactions. [Figure 14] 1 depicts exemplary medication information. [Figure 15] 1 depicts an exemplary user interface for capturing medications and / or medication usage for a medication diary. [Figure 16] 1 depicts an exemplary user interface for capturing medications and / or medication usage for a medication diary. [Figure 17] 1 depicts an exemplary user interface for capturing medications and / or medication use for dose or exposure assessment. [Figure 18] 10 depicts an exemplary user interface for capturing medications and / or medication usage for a medication watchlist. [Figure 19] 10 depicts an exemplary user interface for capturing medications and / or medication usage for drug interactions. [Figure 20] 10 depicts an exemplary user interface for capturing medications and / or medication usage for a medication watchlist. DETAILED DESCRIPTION OF THE INVENTION

[0008] Features described herein may include developing patient-centric mobile applications to improve medication and usage capture.

[0009] A system, method, non-transitory computer-readable medium, and / or apparatus for capturing medications and / or medication use may be provided. For example, a device and / or a method implemented by a device for determining medications used by a patient may be provided. Label information for the medication may be determined. A first message may be sent to a first server. The first message may indicate a request for a first medication identifier, such as a first National Drug Code (NDC) associated with the medication. The first message may indicate the label information. The first NDC may be in a first format. A second message may be received from the first server. The second message may indicate the first NDC and may indicate an RxNorm Concept Unique Identifier (RxCUI). The second NDC may be determined using the first NDC. The second NDC may be in a second format. The second format may differ from the first format. The brand name may be determined using the second NDC. One or more active ingredients may be determined using the RxCUI. One or more active ingredients may be associated with a brand name. A drug display name may be determined using the brand name and the one or more active ingredients. Active ingredient information may be determined for the one or more active ingredients. The drug display name and active ingredient information may be displayed to a user, such as a patient.

[0010] A system, method, non-transitory computer-readable medium, and / or apparatus for capturing medications and / or medication use may be provided. For example, a device and / or a method implemented by a device for determining medications and medication use associated with a patient may be provided. Label information for the medication may be determined. A first message may be sent to a first server. The first message may indicate a request for a first medication identifier, such as a first National Drug Code (NDC), that may be associated with the medication. The first message may indicate the label information. The first NDC may be in a first format. A second message may be received from the first server. The second message may indicate the first NDC and may indicate an RxNorm Concept Unique Identifier (RxCUI). The second NDC may be determined using the first NDC. The second NDC may be in a second format. The second format may differ from the first format. The brand name may be determined using the second NDC. One or more active ingredients may be determined using the RxCUI. One or more active ingredients may be associated with a brand name. A drug display name may be determined using the brand name and one or more active ingredients. A use associated with the drug and a user may be determined. The user may be a patient. Active ingredient information may be determined for one or more active ingredients. The drug display name, use, and active ingredient information may be displayed to a user, such as a patient.

[0011] A system, method, non-transitory computer-readable medium, and / or device for capturing medications and / or medication use may be provided. Label information for the medication may be determined. A source National Drug Code (NDC) may be determined using the label information. The source NDC may be associated with the medication. A first message may be sent to a first server. The first message may indicate a request for validation of the source NDC. A second message may be received from the first server. The second message may indicate that the source NDC may be valid, may indicate a product NDC, and may indicate a normalized identifier. A brand name associated with the medication may be determined using the product NDC. One or more active ingredients associated with the brand name may be determined using the normalized identifier. A drug display name may be determined using the brand name and one or more active ingredients. Active ingredient information may be determined for the one or more active ingredients. The drug display name and active ingredient information may be displayed to a user.

[0012] In one example, the normalized identifier may be an RxNorm Concept Unique Identifier (RxCUI).

[0013] In one example, the product NDC may include a labeler code and a product code.

[0014] In one example, the source NDC may be a package NDC, which may include a labeler code, a product code, and a package code.

[0015] In one example, the source NDC may be in a 10-digit format or an 11-digit format, and the product NDC may be in a 9-digit format.

[0016] In one example, the label information for the medication may be determined by receiving data from a user, which may include at least one of a source NDC, an active ingredient, a brand name, an image, or a video.

[0017] In one example, the drug label information can be determined by determining an image or video of the drug label, and at least one of the source NDC, active ingredient, or brand name can be determined from the image using optical character recognition.

[0018] In one example, a brand name may be determined using the product NDC by sending a brand name request message to a second server. The brand name request message may indicate a request for a brand name associated with the product NDC. A brand name response message may be received from the second server. The brand name response message may indicate the brand name.

[0019] In one example, one or more active ingredients associated with a brand name can be determined by sending an ingredient request message to a first server. The ingredient request message can indicate a request for one or more active ingredients associated with a normalized identifier. An ingredient response message can be received from the first server. The ingredient response message can indicate the normalized identifier and the one or more active ingredients. The one or more active ingredients can be in a database such that the one or more active ingredients are associated with the brand name.

[0020] In one example, a drug label may be determined using the brand name and one or more active ingredients by determining a prescribable synonym name for at least one of the one or more active ingredients. The drug label may be determined by combining the brand name with the prescribable synonym name.

[0021] In one example, active ingredient information for one or more active ingredients can be determined by sending an active ingredient information request to a third server. The active ingredient information request can indicate at least one of a structured product labeling identification (SPL ID) or a normalized identifier. An active ingredient information response can be received. The active ingredient information response can indicate the active ingredients. The active ingredient information response can indicate at least a warning, instructions regarding the active ingredient, usage instructions, or a drug interaction warning.

[0022] In one example, the active ingredient information may include at least one active ingredient from one or more active ingredients, a dose and / or strength associated with the active ingredient, a dosage unit associated with the active ingredient, or a unit type associated with the medication. As used herein, the term dosage may be used interchangeably with the term strength.

[0023] A system, method, non-transitory computer-readable medium, and / or device may be provided for summarizing medication use associated with a patient. A first normalized identifier may be determined using a first National Drug Code (NDC). The first normalized identifier may be associated with a first medication. A second normalized identifier may be determined using a second NDC. The second normalized identifier may be associated with a second medication. The first normalized identifier may be used to determine that the first medication includes a first amount of an active ingredient. The second normalized identifier may be used to determine that the second medication includes a second amount of the active ingredient. A medication summary may be displayed. The medication summary may include a drug name associated with the active ingredient and a sum of the first and second amounts of the active ingredient.

[0024] In one example, the minimum amount of active ingredient to be consumed by the patient can be determined using the first amount and the second amount.

[0025] In one example, the maximum amount of active ingredient to be consumed by the patient can be determined using the first amount and the second amount.

[0026] In one example, the average amount of the active ingredient consumed by the patient can be determined using the first amount and the second amount.

[0027] In one example, the drug name may be a first drug name and the active ingredient may be a first active ingredient. The first drug may include a third amount of a second active ingredient that may be identified using the first normalized identifier.

[0028] In one example, a first use of a first medication can be determined. The first use can indicate when a patient consumed the first medication.

[0029] In one example, the dosing regimen can further include a first use and a second total, which can be a third amount of a second active ingredient.

[0030] In one example, the dosing summary may further include first dosing information associated with the first active ingredient and second dosing information associated with the second active ingredient.

[0031] In one example, the drug name may be a first drug name, the active ingredient may be a first active ingredient, and the total may be a first total. The first normalized identifier may be used to determine that the first drug includes a third amount of a second active ingredient. The second normalized identifier may be used to determine that the second drug includes a fourth amount. The second normalized identifier may be used to determine that the second drug includes a fifth amount of a third active ingredient.

[0032] In one example, a first use of a first medication can be determined. The first use can indicate when a patient consumed the first medication. A second use of a second medication can be determined. The second use can indicate when a patient consumed the second medication.

[0033] In one example, the total can be a first total, and the dosing schedule can further include a first use, a second use, a second total, and a third total. The second total can be a third amount of the second active ingredient and a fourth amount of the second active ingredient. The third total can be a fifth amount of the third active ingredient.

[0034] FIG. 1 depicts an exemplary functional block diagram of the electrical components of an exemplary smart device for capturing medications and / or medication use. For example, FIG. 1 may depict an exemplary functional block diagram of the electrical components of an exemplary smart device for capturing medications associated with a patient and how the patient may use those medications. The smart device may be a smartphone (e.g., iOS®, Android®, etc.), a tablet (e.g., iPad, Galaxy Tablet®, etc.), a smartwatch (e.g., Apple Watch®, Google Pixel Watch, etc.), a wearable device, a mobile phone, a computer, a server, etc. Component 120 may be incorporated into a smart device such as devices 204 and 206 (shown with reference to FIG. 2) and / or into a computing resource such as 212 (also shown with reference to FIG. 2). Referring again to FIG. 1, component 120 may integrate sensing, electromechanical drive, communication, and digital processing capabilities into the device's structure and operation. In the example, components 120 may include a controller 122 , a communication interface 124 , sensors 126 , electrical and electromechanical drivers 128 , and a power management subsystem 130 .

[0035] Controller 122 may include, for example, a processor 132, a memory 134, and one or more input / output devices 136. Controller 122 may be any suitable microcontroller, microprocessor, field programmable gate array (FPGA), application specific integrated circuit (ASIC), etc. suitable for receiving, processing, storing, and directing output data and / or signals. Controller 122 may be a device suitable for embedded applications. For example, controller 122 may include a system on a chip (SOC).

[0036] Processor 132 may include one or more processing units. Processor 132 may be a processor of any suitable depth to perform the digital processing requirements disclosed herein. For example, processor 132 may include a 4-bit processor, a 16-bit processor, a 32-bit processor, a 64-bit processor, etc. The processor may be or include a graphics processing unit (GPU), an artificial intelligence (AI) processing unit, a machine learning processing unit, and / or another processor that may be suitable for graphics processing, AI, and / or machine learning.

[0037] Memory 134 may include any component or collection of components suitable for storing data. For example, memory 134 may include volatile and / or non-volatile memory. Memory 134 may include random-access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, etc.

[0038] Input / output devices 136 may include any devices suitable for receiving and / or transmitting information. This information may be in the form of digitally encoded data (e.g., from other digital components) and / or analog data (e.g., from analog sensors). Input / output devices 136 may include serial input / output ports, parallel input / output ports, universal asynchronous receiver transmitters (UARTs), discrete logic input / output pins, analog-to-digital converters, and digital-to-analog converters. Input / output devices 136 may include specific interfaces with computing peripherals and support circuits, such as timers, event counters, pulse width modulation (PWM) generators, watchdog circuits, clock generators, etc. Input / output devices 136 may provide communication within and between components 120, for example, between controller 122 and sensors 126, between controller 122 and drivers 128, between controller 122 and communications interface 124, and between controller 122 and power management subsystem 130, as well as serving as a conduit for any other combination of components 120. Components 120 may also support direct communication between sensors 126 and power management subsystem 130, for example.

[0039] Communication interface 124 may include a transmitter 138 and / or a receiver 140. Communication interface 124 may include one or more transmitters 138 and / or receivers 140. Transmitter 138 and receiver 140 may include any electrical components suitable for communication to and from electrical component 120. For example, transmitter 138 and receiver 140 may provide wired and / or wireless communication to devices external to component 120 and / or to devices external to the device within which component 120 is integrated.

[0040] The transmitter 138 and receiver 140 may enable wired communication using any suitable communication protocol, such as a protocol suitable for the embedded application. For example, the transmitter 138 and receiver 140 may be configured to enable universal serial bus (USB) communication, Ethernet local-area networking (LAN) communication, etc.

[0041] Transmitter 138 and receiver 140 may enable wireless communication using any suitable communication protocol, e.g., a protocol suitable for the embedded application. For example, transmitter 138 and receiver 140 may be configured to enable a wireless personal area network (PAN) communication protocol, a wireless LAN communication protocol, a wide area network (WAN) communication protocol, etc. Transmitter 138 and receiver 140 may be configured to communicate via Bluetooth using any supported or custom Bluetooth version and / or any supported or custom protocol, including, e.g., A / V Control Transport Protocol (AVCTP), A / V Distribution Transport (AVDTP), Bluetooth Network Encapsulation Protocol (BNEP), IrDA Interoperability (IrDA), Multi-Channel Adaptation Protocol (MCAP), and RF Communications Protocol (RFCOMM). In examples, transmitter 138 and receiver 140 may be configured to communicate via Bluetooth Low Energy (LE) and / or Bluetooth Internet of Things (IoT) protocols. Transmitter 138 and receiver 140 may be configured to communicate via a local mesh network protocol, such as ZigBee, Z-Wave, Thread, etc. Such protocols may enable transmitter 138 and receiver 140 to communicate with nearby devices, such as a user's cellphone and / or smartwatch.Communication with local network devices such as mobile phones may further enable communication with other devices over a wide area network (WAN), communication with remote devices, communication over the Internet, communication over a corporate network, etc.

[0042] The transmitter 138 and receiver 140 may be configured to communicate via a LAN protocol, such as an 802.11 wireless protocol like Wi-Fi, including, but not limited to, communications in the 2.4 GHz, 5 GHz, and 60 GHz frequency bands. Such protocols may enable the transmitter 138 and receiver 140 to communicate with a local network access point, such as a wireless router in a user's home or office. Communication with the local network access point may also enable communication with other devices present on the local network, or with remote devices over a WAN, over the Internet, over a corporate network, etc.

[0043] Transmitter 138 and receiver 140 may be configured to communicate via a mobile wireless protocol, such as global system for mobile communication (GSM), 4G long-term evolution protocol (LTE), 5G, and 5G new radio (NR), as well as any of various mobile Internet of Things (IoT) protocols. Such protocols may enable transmitter 138 and receiver 140 to communicate more easily without manual configuration, for example, when a user is mobile and traveling away from home or the office.

[0044] The sensors 126 may include any device suitable for sensing aspects of its environment, such as physical, chemical, mechanical, electrical, encoded, etc. The controller 122 may interact with one or more sensors 126. The sensors 126 may include, for example, a camera sensor 142, an information sensor 146, a motion sensor 148, etc. Although not shown, the sensors 126 may include one or more biometric sensors, such as a heart rate sensor, a blood oxygen sensor, a blood pressure sensor, or a combination thereof.

[0045] The camera sensor 142 may include any sensor suitable for capturing and / or recording images and / or video. The camera sensor 142 may be a charged-couple device (CCD), an active pixel sensor, a complementary metal-oxide-semiconductor (CMOS) sensor, an N-type metal-oxide-semiconductor (NMOS) sensor, etc. In an example, the camera sensor 142 may be used to capture images and / or video of information that may be encoded on a medication container (e.g., a medication label). The information may be encoded on the medication container using text, letters, numbers, a quick read (QR) code, a readable integrated circuit (e.g., a one-wire identification chip), a near-field communication (NFC) tag, physical / mechanical keying, a Subscriber Identification Module (SIM), etc. For example, a user may use camera sensor 142 to take an image of a medication label, and the text of the medication label may be processed by device 120.

[0046] The information sensor 146 may include any sensor suitable for reading stored information. In embedded applications with a physical platform, information may be encoded and stored on various media, which may be incorporated into aspects of the physical design. For example, information regarding medication authenticity, concentration, volume, etc., which may be consumed by a user and / or associated with the device. In examples, information may be encoded on a medication container (e.g., a medication label) using text, letters, numbers, a Quick Read (QR) code, a data matrix, a readable integrated circuit (e.g., a one-wire identification chip), a near-field communication (NFC) tag, radio frequency identification (RFID), physical / mechanical keying, a subscriber identity module (SIM), etc. A user may use the device to scan the QR code, and the device may communicate the information to the controller 122 via the communication interface 124. In examples, the information sensor 146 may also be suitable for rewriting information to a medium associated with a readable code, such as with a readable / writeable NFC tag.

[0047] The motion sensor 148 may include any sensor suitable for determining the device's relative movement, acceleration, velocity, orientation, etc. The motion sensor 148 may include piezoelectric, piezoresistive, and / or capacitive components that convert physical movement into electrical signals. For example, the motion sensor 148 may include an accelerometer. The motion sensor 148 may include a microelectromechanical system (MEMS) device, such as a MEMS thermal accelerometer. The motion sensor 148 may be suitable for detecting repetitive or periodic movements, such as restlessness, by a user holding or wearing the device. The motion sensor 148 may communicate this information via the input / output device 136 to the processor 132 for processing.

[0048] The device may include one or more drivers 128 for communicating feedback to the user and / or directing mechanical actions. Drivers 128 may include light-emitting diode (LED) drivers 152, stepper drivers 154, etc. Other drivers 128 may include haptic feedback drivers, audio output drivers, heating element drivers, etc.

[0049] The LED driver 152 may include any circuitry suitable for illuminating an LED. The LED driver 152 may be controllable by the processor 132 via the input / output devices 136. The LED driver 152 may be used to indicate status information to a user. The LED driver 152 may include a multi-color LED driver.

[0050] The stepper driver 154 may include any circuitry suitable for controlling a stepper motor. The stepper driver 154 may be controllable by the processor 132 via the input / output driver 136. The stepper driver 154 may be used to control a stepper motor associated with a medical device. In one example, the stepper driver 154 may be used to control a stepper motor of an insulin pump. In one example, the stepper driver 154 may be used to control a motor of a prosthetic arm.

[0051] The power management subsystem 130 may include circuitry suitable for managing and delivering power to the smart device components 120. The power management subsystem 130 may include a battery, a battery charger, a direct current (DC) power distribution system, etc. The power management subsystem 130 may communicate with the processor 132 via input / output devices 136 to provide information such as battery charge status. The power management subsystem 130 may include a replaceable battery and / or a physical connector to enable external charging of the battery.

[0052] 2A depicts an example architecture diagram of an example system supporting devices such as smart devices. System 200 may include a smartphone 204 with corresponding applications (e.g., apps), a smartwatch 206 with corresponding apps, a wireless access network 208, a communications network 210, and computing resources 212.

[0053] The smart device may be a smartphone, a tablet (e.g., iPad), a smartwatch, a wearable device, a mobile phone, a computer, a server, etc. The smart device may be the smart device shown with respect to FIG. 1, which may be a smartwatch 206 (e.g., Apple Watch®, Google Pixel Watch®, etc.), a smartphone 204 (e.g., iPhone®, Samsung Galaxy S23®, etc.), and / or a computing resource 212 shown with respect to FIGS. 2A-2B.

[0054] 2A , the smartphone 204 may include an app for capturing medications and / or medication use. The smartphone 204 may provide passive or active tracking and / or location services. The smartphone 204 may collect data about the user, process data about the user, and / or share data about the user. For example, the smartphone 204 may be able to collect information about medications using one of its sensors and share that data with the smartwatch 206 and / or computing resource 212. As another example, the smartphone 204 may be able to determine that the user has used medication and share that data with the smartwatch 206 and / or computing resource 212.

[0055] The smartwatch 206 may be capable of providing the user with a list of medications. The list of medications may be a list of medications that the user may use and / or has used. The list of medications may be a list of active ingredients found in medications used by the user. The smartwatch 206 may provide biometric feedback and data, such as heart rate and / or heart rate variability. The smartwatch 206 may perform activity tracking and provide activity information. The smartwatch 206 may be used by the user to add medications to and remove medications from the list of medications.

[0056] The computing resources 212 may provide data storage and processing capabilities. The computing resources 212 may receive and analyze medication data and / or medication usage data. For example, the computing resources 212 may receive and analyze medications used by a user to determine the active ingredients contained in the medications and the amounts of those active ingredients consumed.

[0057] The components of system 200 may communicate with each other via various communication protocols. Smartwatch 206 may communicate with smartphone 204 via a link such as Bluetooth wireless link 216. Smartphone 204 may communicate with wireless access network 208 via a link such as wireless link 218. Smartwatch 206 may communicate with wireless access network 208 via a link such as wireless link 220. Wireless link 218 and / or wireless link 220 may include any suitable wireless protocol such as Wi-Fi, GSM, 802.11 wireless protocols such as 4G LTE, 5G, and 5G NR, any mobile IoT protocol, etc.

[0058] The communications network 210 may include long-distance data networks such as private corporate networks, virtual private networks (VPNs), public commercial networks, interconnections of networks such as the Internet, etc. The communications network 210 may provide connectivity to computing resources 212.

[0059] Computing resources 212 may include any server resources suitable for remote processing and / or storage of information. For example, computing resources 212 may include servers, cloud servers, data centers, virtual machine servers, etc. In an example, smartwatch 206 may communicate with computing resources 212 via its wireless link 220, and smartwatch 206 may communicate with computing resources 212 via its wireless link 218.

[0060] System 200 may enable the collection and processing of information related to medications associated with a user (e.g., a patient). For example, system 200 may capture medications the user may be using, when the medications are being used by the user, the amount of medications the user may be consuming, combinations thereof, etc. System 200 may enable a user to track which medications the user may be taking. System 200 may determine how much of an active ingredient the user may be consuming, which may be a component of a medication.

[0061] For example, a user may consume a medication that consists of three active ingredients. System 200 may determine that the user has consumed the medication and that the user has consumed 10 mg of a first active ingredient, 5 mg of a second active ingredient, and 4 mg of a third active ingredient.

[0062] As another example, a user may consume a first medication and a second medication. The first medication may be comprised of three active ingredients: 10 mg of the first active ingredient, 5 mg of the second active ingredient, and 4 mg of the third active ingredient. The second medication may be comprised of two active ingredients: 2 mg of the first active ingredient and 4 mg of the second active ingredient. The system 200 may provide a summary of the active ingredients consumed by the user (e.g., patient). For example, the system 200 may calculate that the user consumed 12 mg of the first active ingredient, 9 mg of the second active ingredient, and 4 mg of the third active ingredient.

[0063] 2B is an example messaging flow diagram for example system 200. System 200 may include communications and processing for functions such as smartphone 204 and / or medication app initialization and authentication, data collection from smartwatch 206 and / or smartphone 204, cloud-based control, triggers, notification messaging, etc., app-based control, messaging, and notifications.

[0064] Initialization and authentication messaging 222 may be exchanged between one or more of the smartwatch 206, the smartphone 204, or the computing resource 212. For example, a user may create a user account via the smartphone 204. The account information may be processed by the computing resource 212. A new user may initialize the smartwatch 206 to authenticate the smartwatch 206. Information may be communicated to the smartphone 204 via messaging 202 and then to the computing resource 212 via initialization and authentication messaging 224. Information may be communicated to the computing resource 212 via initialization and authentication messaging 222. Response information regarding the user account, medication usage, medication consumption, medications associated with the user, etc. may be messaged back to the smartwatch 206 and / or the smartphone 204.

[0065] Data collection functionality may be provided and may include messaging 226 from the smartwatch 206, the smartphone 204, and / or the computing resource 212. This messaging may include information such as activity information, heart rate, heart rate variability, medication consumption, medication information, electronic medication records, medical data about the patient, prescriptions, etc. The data collection functionality may include messaging 228 from the smartwatch 206 to the smartphone 204. In examples, the smartphone 204 may aggregate the messaging 228, process the messaging 228 locally, and / or communicate the messaging 228 or related information to the computing resource 212 via messaging 230.

[0066] System 200 enables cloud-based, app-based, and local-based control functions. For example, personalized medication data, drug data, medication consumption data, active ingredient data, status, and / or reports may be provided from computing resource 212 to smartphone 204 via messaging 232, and, if appropriate, from smartphone 204 to smartwatch 206 via messaging 234. Computing resource 212 may communicate directly with smartwatch 206 by using messaging 235.

[0067] For example, personalized medication data, status, and / or reports may be generated from an application and displayed on the smartphone 204 and smartwatch 206. The application may be on the computing resource 212, the smartphone 206, and / or the smartwatch 206. The personalized medication data, status, and / or reports may be communicated to the smartwatch 206 via messaging 236.

[0068] In an example, the smartwatch 206 may provide local control via its own local processor. Internal system calls and / or local messaging are illustrated as local loop 238. For example, the smartwatch 206 may provide personalized medication data, status, and / or reports.

[0069] Features and examples described herein may include developing patient-centric mobile applications to improve medication and usage capture.

[0070] Medications may play a role in the treatment and management of diseases and symptoms, and safe use of medications requires knowledge and consideration of one or more of the medications a patient is taking or receiving to avoid, among other things, omissions, duplications, administration errors, and potential harmful interactions with new medications being prescribed. However, discrepancies between both recorded and reported medications can be common. Discrepancies can occur regardless of medication class or care setting. Such discrepancies can lead to medication errors. Reducing medication discrepancies and medication errors can improve medication safety.

[0071] Discrepancies between recorded medications and reported medications are common and can involve all classes of medications and care settings. Discrepancies can occur globally across geographic regions. In an example, patients in a primary care clinic in the United States may experience discrepancies. In an example, patients in a primary care center in Sweden may experience discrepancies. Reported medication discrepancies can occur for patients in a cardiologist's practice. Discrepancies can occur when patients do not report taking their medications. In an example, between 30% and 70% of patients may experience errors or unintended medication changes when transferring from one care setting to another. Common reasons for these discrepancies can include omitted medications (e.g., over-the-counter, OTC), blank prescriptions, incorrect dosages, etc. Medication discrepancies can result in medication errors and adverse outcomes and can contribute to global healthcare costs.

[0072] Medication reconciliation has been recognized by several international patient safety organizations, such as The Joint Commission (TJC), the Institute for Healthcare Improvement (IHI), and the World Health Organization (WHO), for its potential to achieve better medication safety and optimize transitions of care. In one example, a medication history may involve capturing and / or determining the medications a patient is taking, which may include prescription, over-the-counter, and complementary medications. In one example, a medication list may be created and / or determined, which may include prescribed, over-the-counter, and complementary medications. In one example, medication reconciliation may be implemented in a manner that reduces the time and resources required to ensure that patients are able and willing to accurately provide medication information.

[0073] Examples provided herein may provide software (e.g., a mobile application) for identifying and / or capturing medications, some of which may be associated with diseases or products, to help patients capture their medications, track their use, and track adherence. The software may avoid requiring tedious manual entry of medications. The software may include features beyond pill reminders and adherence tracking. The software may help standardize medication capture given the large number of medications approved in the U.S. (e.g., >20,000 Rx, >300,000 OTC) with various active ingredients, strengths, and formulations. The software may help patients track their personal use of medications. The software may capture accurate drug information, such as ingredients, strengths, and formulations. The software may allow medication information to be shared with healthcare providers or aggregated for research purposes.

[0074] Confirmation of medication exposure can be a component (e.g., a critical component) in the generation of real-world evidence (e.g., for regulatory and clinical decision-making). Some healthcare systems may enable (e.g., only enable) the capture of prescription (Rx) medications that may be entered by healthcare providers. However, many existing healthcare systems may not enable the capture of over-the-counter (OTC) medications. For example, healthcare systems often capture prescription medications as medication orders or dispensing records, which may serve as proxies (e.g., medication exposure / patient adherence).

[0075] A self-care model and patient-centered approach to health care may be provided. Self-care may be the ability of individuals, families, and / or communities to promote health, prevent disease, maintain health, and / or cope with illness or disability, with or without the assistance of a health care provider. Guidelines for self-care interventions for health may include recommendations for safe and effective interventions that can be used within an enabling environment (e.g., a supportive enabling environment).

[0076] Many patients who are mobile and capable of self-medicating may play a role (e.g., a central role) in creating and maintaining the patient's medication list (e.g., so the patient knows which medications they are taking each day).

[0077] Self-care interventions can support (e.g., empower) individuals and communities to manage their health and well-being, strengthen national institutions (e.g., through efficient use of national resources for health), improve primary health care, and contribute to achieving universal health coverage. Supporting (e.g., empowering) individuals to manage their health can be a priority (e.g., important) because self-care (e.g., better self-care) can be an aspect of preventing global epidemics (e.g., chronic non-communicable diseases). Self-care interventions can provide users with greater choice, access, control, satisfaction, and affordable options for managing their health care needs. Self-care can recognize individuals' strengths as active agents in their health care, rather than passive recipients of health services (e.g., not merely passive recipients).

[0078] The healthcare market may change (e.g., changing) to adjust (e.g., keep pace) with modern needs (e.g., including self-medication). Self-medication may involve a patient diagnosing a condition, selecting an appropriate medication from a pharmacy, and treating each patient's symptoms. Self-medication may involve enabling consumers to actively engage in their health. When patients self-medicate, access to OTC medications may be relevant (e.g., paramount). Medications available today as OTC (e.g., many medications) may have previously been labeled as prescription medications. Safety studies and testing may be conducted on drugs deemed appropriate for use without a prescription.

[0079] Person / patient-generated health data (PGHD) can provide data on exposures, outcomes, and covariates that can provide indications of a patient's background risk (e.g., for an event of interest), more relevant endpoints (e.g., steps walked, hours slept), and real-time exposure measurements (e.g., sensors on inhalers that record dose and / or strength, geographic location, and date and time of use).

[0080] As disclosed herein, embodiments may improve and / or simplify medication reconciliation for safer use of pharmaceuticals. Medical interventions may be intended to benefit patients, but may also cause harm. The combination (e.g., complex combination) of processes, technologies, and human interactions that may comprise modern healthcare delivery systems may be beneficial. This combination of techniques, technologies, and human interactions may carry unavoidable risks of patient harm that may result in actual harm. Medication safety may (e.g., should) begin with appropriate prescribing and risk-benefit analysis (e.g., a thorough risk-benefit analysis) of medications (e.g., each medication).

[0081] Identifying medications may be provided. Creating and maintaining medication lists for patients may be provided. Creating and maintaining medication lists for all patients may represent the fulfillment of a responsibility (e.g., of a physician). Developing (e.g., properly developing) and maintaining medication lists (e.g., correct medication lists) for one or more patients may include delegation (e.g., appropriate delegation), implementation of related information technology, creation of systems to support the work of maintaining the lists, and development of payment mechanisms and performance measures.

[0082] Medication reconciliation can be a process by which a medical professional can partner with a patient to ensure that medication information can be accurate.

[0083] The medication reconciliation process can assist (e.g., can be important) in promoting medication and patient safety during transitions of care. Medication reconciliation can improve medication safety by identifying unintentional medication discrepancies, particularly during transitions of care.

[0084] The features described herein may include extensibility and / or integration with an Electronic Health Record (EHR). The EHR (e.g., many EHRs) may be a single-site EHR or an inpatient record (e.g., limited to inpatient records only). To improve medication safety during transitions, the EHR or summary care record may reflect the patient's medication use across transitions, may be accessible (e.g., to the patient and treating healthcare professionals), and may be editable by one or more parties to improve completeness and accuracy.

[0085] A medical condition (e.g., multiple medical conditions) may be (e.g., typically) treated with multiple medications (polypharmacy), which, if not used appropriately, may expose patients to the risk of adverse drug events and drug interactions. Multiple medications or polypharmacy (e.g., use of multiple medications or polypharmacy) may be clinically appropriate. For example, patients with inappropriate polypharmacy may be at increased risk of adverse events and may be identified as having poor health outcomes.

[0086] Capture (e.g., robust capture) of Rx / OTC exposures for real-world data (RWD) and real-world evidence (RWE) may be provided. RWD (real-world data) may be data that may be collected from a variety of sources and may be related to a patient's health status and / or healthcare delivery. RWE may be evidence, such as clinical evidence, about the use, potential benefits, and / or risks of a medical product. RWE may be derived from an analysis of RWD. Examples of RWD may include data derived from EHRs, medical claims data, data from product and disease registries, patient-generated data from home use, and / or data collected from other sources that may inform health status.

[0087] The potential use of RWE in healthcare decisions for prescribed medicines may have attracted significant attention among industry, regulators, and professional societies. Comparatively, little focus has been placed on the potential role of RWE for non-prescription medicines. Some differences may exist between prescription and non-prescription medicines with regard to sources of RWD and requirements for evidence such as RWE. Given that consumers can play a key role in managing their own conditions without the oversight of healthcare professionals and may also be central to the generation and distribution of patient-generated health data, the potential use of patient-generated health data may be relevant to non-prescription medicines.

[0088] Improved adverse event reporting may be provided. For example, improved adverse event reporting using NDC codes, photographs, and diary information may be provided. Drug identifiers such as NDC codes may be useful because NDC codes may be relevant to pharmacovigilance and drug safety. In one example, embodiments disclosed herein may be used to determine and / or report adverse events for brand-name, prescription, generic, active ingredients, etc.

[0089] A medical identifier (which may be referred to as a regulatory identifier) ​​may be a code provided by a regulatory agency such that the medical identifier may identify a medication. The medical identifier may be a National Drug Code. For example, a National Drug Code database may identify medications using a medical identifier, which may be a National Drug Code (NDC). The NDC may enable tracking of products such as medications (e.g., at a granular level). For example, the NDC may enable tracking of medications based on active ingredient, strength, packaging, manufacturer, combinations thereof, etc. An adverse event may be associated with an active ingredient having a particular strength (e.g., Vioxx 50 mg) that was quarantined to an individual manufacturer due to excipients, quality control, or contamination.

[0090] In one example, the features described herein may be extended outside the United States. Products may be identified differently in different regions. For example, medication identifiers such as NDC and / or RxCUI may vary by country. For example, medication identifiers may be provided by an agency that regulates medications in a country and therefore may be referred to as regulatory identifiers. Table 1 describes identifier fields for supported regions that may be used as medication identifiers.

[0091] [Table 1]

[0092] As disclosed herein, a medical identifier may be an identifier provided by a regulatory authority to identify a drug, a prescription drug, an over-the-counter drug, an active ingredient, a combination thereof, or the like.

[0093] Medication errors in hospitals can occur in clinical wards or upon admission to or discharge from the hospital. Approximately 30% of these errors can result in patient harm. Such errors can occur when obtaining a list of medications that a patient may be using or have used. For example, a patient may take a medication and forget to notify the hospital of the medication.

[0094] A medication module as part of a mobile application (e.g., software on a smartphone) may enable medication capture and medication usage. The medication module may include a medication list and a medication diary. The mobile application may provide health portal connectivity (e.g., patients import medical records including prescribed medication data from their respective healthcare providers). Patients may add, edit, and / or delete entries to the medication list (e.g., within the medication module) (e.g., via RxNorm and openFDA application programming interfaces (APIs)). The medication diary may capture daily medication use (e.g., in real time or retrospectively) based at least in part on one or more entries in the medication list.

[0095] The medication module may provide capabilities (e.g., robust capabilities) to help patients capture one or more (e.g., all) of their respective medications (e.g., both Rx and OTC). Patients may select medication entry based on one or more of the National Drug Code (NDC), active ingredient, or brand name. Text-based searches may be assisted by one or more auto-prompt or auto-complete features (e.g., so that medication logging may be minimally burdensome). Text-based searches may be assisted with software that may provide suggestions, lists, and / or other software to minimize the burden of entering medications. Medications may be entered directly and / or identified using, for example, optical character recognition (OCR) and / or dynamic scanning. Medications may be captured using database identifiers (e.g., RxCUI) and / or medication identifiers (e.g., NDC). In examples, the medication identifier may be linked to a database identifier (e.g., an NDC with a link to RxCUI), which may facilitate sharing with healthcare providers (e.g., sharing interoperability, aggregation, and / or analysis of medication utilization data for research purposes).

[0096] Creating and maintaining medication records can be challenging for patients and healthcare providers, but may improve medication safety and robust real-world evidence generation. Rx and OTC medications and their respective use can be captured (e.g., easily and reliably) via a medication module (e.g., through a patient-centric approach). Records within the medication module can be stored as standardized concepts (e.g., RxNorm and NDC), which can facilitate interoperability and / or aggregation. Mobile apps can help (e.g., assist) in linking medication use with clinical context and outcomes of such use. In one example, patients can play a role (e.g., a central role) in creating medication records for their patients.

[0097] The medication module may allow for setting one or more profiles. The profiles may be associated with a user. For example, one or more profiles may be set to accommodate care of a child, an elderly person, and / or other dependents. The medication module may allow for monitoring one or more profiles. In one example, an adult profile may be monitored. In one example, a child profile may be monitored. In one example, a child profile may be monitored by a caregiver, who may be an adult.

[0098] The medication module may provide users with the ability to capture both prescription and over-the-counter medications. Medications may be entered via NDC, active ingredient, or brand name. NDC may be entered directly or identified by dynamic OCR without taking a still image. Medications names may be prompted for confirmation.

[0099] In one example, text-based searches can be supported with auto-suggestion and / or picklist functionality, which can ensure medication logging is minimally burdensome. Medications can be explicitly captured as either RxCUIs or NDC (e.g., with a connection to an RxCUI) to facilitate interoperability and aggregation.

[0100] In one example, the medication module may provide a system usability scale (SUS) survey. The SUS survey may be used to determine the ease and / or effectiveness of the medication module. For example, the SUS may be a 10-item scale for rating the medication module using descriptions of ease of use.

[0101] As disclosed herein, the medication module may include a medication list and a medication diary. The mobile app may provide health portal connectivity for patients to import their medical records, including prescribed medication data, from their healthcare provider to build the medication list. Patients may add, edit, and / or delete Rx and OTC entries to the medication list through integration with RxNorm and the openFDA Application Programming Interface (API). Patients may include a photo of the bottle (e.g., prescription bottle) or packaging as part of their medication details. A photo may be displayed along with the medication name to help patients (e.g., a single patient) identify the medication. The medication diary may capture daily medication use (e.g., amount or units) in real time or retrospectively (e.g., based on entries in the medication list). Users (e.g., patients) may edit and / or modify the medication diary.

[0102] Semantic interoperability can present challenges when using real-world data for evidence generation. Differences in source data captured using different standards and / or terminology to represent semantically similar (e.g., equivalent) concepts can challenge researchers' ability to replicate real-world studies. A standardized terminology for biomedical information can be beneficial to biomedical applications and research. Embodiments described herein may utilize a standardized terminology for biomedical data.

[0103] Standardized terminology systems may include standardized representations of pharmaceutical products, such as the Unique Ingredient Identifier (UNII) thesaurus, the National Drug Code (NDC) coding system, the Systematized Nomenclature of Medicine-Clinical Terms (SNOMED CT) system, and / or the RxNorm system. In standardized terminology systems, medication information may include drug components such as trade name (if applicable), generic name, active ingredient, drug strength and unit of measure, dosage form, route of administration, chemical entity, drug class, mechanism of action, physiological effect, manufacturer details, and package type and size.

[0104] Embodiments described herein may involve using RxNorm as a drug dictionary. RxNorm may be a hierarchical terminology system. For example, differences in source data may be captured regionally and globally using different standards, terminologies, and interchange formats for representing the same or similar data elements. RxNorm may provide normalized names for clinical drugs, generic drugs, active ingredients, etc. For example, drug names from RxNorm may be linked and / or mapped to drug narrative vocabularies used in pharmacy management and / or drug interaction software (including, for example, those of First Databank, Micromedex, and Gold Standard Drug Database).

[0105] Standardized terminology systems for biomedical information have been instrumental in biomedical applications and research. The actual use of biomedical information may (e.g., often) require (e.g., require) mapping across terminology systems (e.g., mapping may be a complex and time-consuming process). Embodiments described herein may use standardized terminology systems for biomedical information.

[0106] In examples, applications provided by embodiments described herein may use standardized nomenclature for biomedical information. For example, standard nomenclature may include medication information.

[0107] Medication information may include drug components such as trade name (e.g., if any), brand name, generic name, active ingredient, drug strength, unit of measure, dosage form, route of administration, chemical entity, drug class, mechanism of action, physiological effect, manufacturer details, package type, size, and combinations thereof.

[0108] One or more terminology systems for standardized representation of medications may be used. These may include the Unique Component Identifier (UNII) Thesaurus, the National Drug Code (NDC) coding system, the SNOMED CT system, the RxNorm system, combinations thereof, etc. There may be differences in source data captured regionally and globally using different standards, terminology, and exchange formats to represent the same or similar data elements. In an example, software may be provided to unify and / or standardize drug information.

[0109] RxNorm is a hierarchical terminology system that provides normalized names for clinical drug entities organized through RxNorm Concept Unique Identifiers (RxCUIs). These concepts may be linked to one or more of the source drug narrative vocabularies used. In an example, pharmaceutical concepts covered by the RxNorm nomenclature may be used. Embodiments described herein may use RxNorm and / or term types (TTYs) to capture drugs or ingredients such as active ingredient, multiple active ingredients, brand name, branded drug, branded drug component, clinical drug, and clinical drug component. In an example, pharmaceutical concepts within RxNorm may be represented through term types (TTYs), with TTYs (e.g., each TTY) encapsulating drug concepts at different levels of granularity. TTYs may be assigned RxCUIs. For example, a clinical drug component (SCDC) TTY can consist of ingredients combined with ingredient strengths (e.g., "Lisinopril 10MG" [RxCUI316151]), a clinical drug dose form (SCDF) TTY can consist of ingredients combined with dosage forms (e.g., "Lisinopril Oral Product" [RxCUI1164689]), etc. Table 2 provides examples of TTY entities.

[0110] [Table 2]

[0111] Embodiments described herein may use and / or provide a standardized terminology dictionary and / or controlled terminology. When RxNorm is an ontology system, TTY concepts in the system may be linked to each other through relationships defined in the RxNorm ontology, which may allow for different levels of abstraction. As an example, the RxNorm clinical drug "lisinopril 10MG oral tablet" [RxCUI314076] "consists of" the clinical drug component "lisinopril 10MG," which "has" the ingredient "lisinopril" [RxCUI29046]. These relationships defined in the RxNorm ontology can be traversed to achieve any desired level of abstraction, starting from a particular TTY.

[0112] In one example, brand and clinical drugs may be selected as the basis for text-based medication entry. Brand and clinical drugs may capture important medication details regarding ingredients, strength, and formulation, and may match medication data imported from an EMR account (e.g., an Epic or Cerner account), but may also distinguish between brand and generic names. For example, a user may enter either "Lipitor 40MG Oral Tablet" (brand drug) or "Atorvastatin 40MG Oral Tablet" (clinical drug). In an example, database hierarchies may be leveraged. For example, RxNorm relationships and hierarchies may be leveraged to map brand drugs to clinical drugs. Clinical drugs may be mapped to the clinical drug component "Atorvastatin 40MG" and further mapped to the component "Atorvastatin."

[0113] In an example, branded drugs (e.g., SBD) and clinical drugs (e.g., SCD) may be selected as the basis for text-based medication entry. These two options may be consistent with the recommendations of the National Council for Prescription Drug Plans (NCPDP), and the drug product description may consist of three components: drug name (e.g., drug ingredient or brand name), drug strength, and dosage form.

[0114] The embodiments described herein may use standardized and / or controlled terminology. Table 3 shows an example of a standardized terminology dictionary or controlled terminology. In one example, drugs may be recorded using NDC, GPI, or Multilex, while conditions may be documented as ICD-9, ICD-10, SNOMED, ​​MedDRA, READ-OXMIS, or other local codes. In one example, related drugs and conditions (e.g., for a particular analysis) may be aggregated to enable query, search, and analysis of observational data.

[0115] [Table 3]

[0116] Embodiments described herein may provide computer and / or mobile applications that may use National Library of Medicine (NLM) resources, including APIs such as RxNorm, RxTerms, prescribable RxNorm, RxClass, interactions, combinations thereof, etc. Embodiments described herein may utilize medication information available online or locally. For example, embodiments may use installable versions of NLM resources such as RxNav-in-a-Box.

[0117] In one example, NLM may provide one or more resources through an API, such as RxTerms, MED-RT, or RxNorm. The API may be used by the software described herein to leverage NLM resources. For example, a software application may use the RxNorm API to facilitate the capture of medication data in a medication list. In one example, free-text searches for medications within the application may be supported with auto-suggestion and picklist functionality to populate clinical drug or brand name concepts, including strengths and formulations.

[0118] The embodiments described herein may leverage the RxNorm API to facilitate the capture of medication data in a medication list. In one example, a free-text search for medications within an application may be complemented with an autocomplete feature, and entries in the autocomplete list may be populated with RxNorm branded and clinical drug TTYs retrieved via the RxNorm API. The RxNorm API may be used to resolve entered medications to RxCUIs. Table 4 shows some examples of RxNorm API resources that may be used.

[0119] [Table 4]

[0120] The embodiments described herein may utilize one or more mechanisms for capturing drug data. In one example, drug data may be captured with input of brand (e.g., SBD) or clinical drug component (e.g., SCD) TTY from RxNorm. The embodiments provided herein may capture drug data by using Clinical Drug (SCD) concept input from RxNorm, which may be used to address multi-component products that may pose challenges to users. The embodiments may provide users with the ability to explicitly log drug entries to their medication list, enabling the entry and logging of multi-component products. For example, the RxNorm terminology set may have over 22,000 SCD concepts. A search for clinical drug concepts containing the active ingredient “acetaminophen” [RxCUI161] may return over 400 SCD terms, with approximately 89% being multi-component concepts. Capturing multi-component products may be beneficial because the public's general understanding of pharmacological ingredients may have a limited understanding of the active ingredients in drug products. In embodiments herein, using a delimiter, such as the " / " delimiter, to search for multiple-ingredient products may simplify the search. For example, "acetaminophen / codeine" may be used as a search term for TTY concepts containing both the ingredients "acetaminophen" and "codeine." In an example, the absence of the " / " delimiter in a search may result in SCD and SBD concepts containing a single ingredient.

[0121] In one example, single-component drug searches and multi-component drug searches (e.g., single-component drugs vs. multi-component drugs) may be performed at or near the same time to improve performance (e.g., of RxNorm API calls). In one example, single-component drug searches and multi-component drug searches (e.g., single-component drugs vs. multi-component drugs) may be separated to improve performance (e.g., of RxNorm API calls). For example, a search for "acetaminophen" may return 440 possible entries (e.g., both single and multi-component) at the clinical drug level. Embodiments described herein may simplify the search so that patients may more easily select a drug from an entry (e.g., a list of entries). In one example, the use of " / " may allow a user to search for multi-component drugs when entering text such as "acetaminophen / codeine." In one example, an embodiment may detect when " / " is not used and process the search as a single-component search, reducing the number of single acetaminophen entries to 40.

[0122] A National Drug Code (NDC) may be a drug identifier and / or product identifier used in the United States for drugs intended for human use. The NDC allows the Food and Drug Administration (FDA) to maintain a list of drugs manufactured, prepared, distributed, compounded, and / or processed by drug establishments for commercial distribution. Drug products may be identified and reported using a 10-digit, 3-segment number. The 10-digit, 3-segment number may be referred to as a National Drug Code (e.g., most often referred to as an NDC number). The 3-segment number may be in the format 4-4-2 (e.g., 4 numbers, 4 numbers, 2 numbers), 5-3-2, 5-4-1, etc. The FDA may assign a labeler code to the first segment. The labeler code may be the company that manufactures or distributes the drug (e.g., including a drug repackager or relabeler). The labeler code may contain 4 or 5 digits. The second segment, the product code, may identify the drug (e.g., including the specific strength, dosage form, and formulation). The second segment code may contain three or four digits. The third segment, a product and package code (e.g., product code), may identify the package size and type. The third segment may contain one or two digits. The company may assign the third segment (e.g., product and package code).

[0123] Drugs entering U.S. commerce may be listed with the FDA. Companies may submit NDC numbers assigned to drugs manufactured or distributed by the company (e.g., as part of the company's listing requirements). The FDA may publish the NDC numbers (e.g., NDC numbers) and other information submitted by labelers in an online NDC directory or database.

[0124] Under HIPAA-covered transactions, the NDC may be reported (e.g., required to be reported) in 11-digit format. Government agencies and private payers may request (e.g., require) the NDC to be in 11-digit format and printed on the patient's prescription.

[0125] In one example, an 11-digit NDC (e.g., NDC11) may be used. For example, an 11-digit NDC may be used for billing drug products. The Centers for Medicare & Medicaid Services (CMS) and other government agencies may use an 11-digit NDC (e.g., as part of billing documents). Government agencies, including HIPAA, may require the NDC in an 11-digit format with leading zeros.

[0126] An NDC may be mapped to an RxNorm (e.g., many-to-one). There may be multiple RxCUI returns for a single NDC depending on the API call.

[0127] The embodiments described herein may use OCR for medication identification. For example, OCR may be implemented using one or more cloud-based services, such as Amazon Textract, Google Vision AI, and / or Azure Computer Vision. OCR may be used to identify medication information, such as NDC-formatted entities (e.g., 10-digit and / or 11-digit). OCR may be used to capture image text, brand names, and / or generic names. For example, OCR may be used to capture data that can be used to make an API call to retrieve brand names and / or generic names from OpenFDA. OCR may be provided via a cloud-based service, a device-based service (e.g., dynamically), a combination thereof, etc. Mobile-based OCR services (including, for example, Google ML) may be used in conjunction with the OCR service for medication identification (e.g., NDC identification).

[0128] Cloud-based OCR services may include Amazon Web Services' Textract, Google's Vision AI service, etc. In one example, the data extraction task may be performed server-side, and the user may be asked to submit one or more images to be processed via a web service request. In the event that text is not successfully captured from the server-side OCR solution, additional image capture, web service request, and processing may occur.

[0129] In examples, OCR services may be exposed through software development kits (SDKs) or language-specific programming libraries that can be deployed on-device. When the service is deployed locally on a client's device, these SDKs and libraries enable interaction with the service in real time, allowing the service to be consumed without requiring a photograph or network connection. The OCR service may include one or more mobile-based OCR services, such as Tesseract, Apple's Vision framework, Google's ML Kit Vision capabilities, or combinations thereof.

[0130] In one example, the OCR service may be deployed on smart devices, such as both iOS and Android platforms. Compared to text entry via RxNorm API calls, using NDC via dynamic OCR may appear faster, easier, and more relevant. The OCR service may enable improved capture and / or determination of medications containing multiple ingredients.

[0131] The embodiments described herein may include feedback from the pharmacist.

[0132] The embodiments described herein may provide instructions to help patients navigate applications such as medication lists and medication diaries.

[0133] The embodiments described herein may perform OCR by allowing the user to focus on the text of the medication label using a zoom function.

[0134] The embodiments described herein may allow for a delay between when an image may be captured and when scanning of the image may be activated, for example, to reduce the effects of motion.

[0135] The embodiments described herein may perform multiple scans on labels with reflective backgrounds (eg, gold), or where lower light conditions may exist.

[0136] The embodiments described herein may include in-application calculations of compliance and dosage.

[0137] In one example, an NDC number may be required, but the NDC number may not be available on the drug label. Embodiments described herein may determine the NDC number using information retrieved from the drug label. In one example, a universal product code (UPC) may be used for OTC medications that may not have an NDC on the medication label. The UPC may be used to determine the NDC. A medication module may be used to determine the text entry of the name and / or NDC number.

[0138] OTC drugs sold in the United States (e.g., the majority of OTC drugs sold in the United States) may have an NDC number. For example, an OTC drug may have an NDC number on the box or package. The availability of NDC numbers for prescription drugs may vary depending on repackaging and pharmacy leaflets.

[0139] FIG. 3 depicts a block diagram of a system that may include one or more modules (e.g., software modules) for capturing medications and / or medication use. As shown in FIG. 3, the system 300 may include a database 302, an API 304, and a smart device 306. The smart device 306 may be a smartphone, a tablet (e.g., an iPad), a smart watch, a wearable device, a mobile phone, a computer, a server, etc. For example, the smart device 306 may include the components 120 shown with respect to FIG. 1. As another example, the smart device 306 may be the smart watch 206, the smartphone 204, or the computing resource 212 shown with respect to FIGS. 2A-2B.

[0140] Referring again to FIG. 3, the smart device 306 may include one or more software modules, such as dynamic capture 308, optical character recognition (OCR) 310, artificial intelligence / machine learning (AI / ML) 312, and / or medication module 314.

[0141] The medication module 314 may include a medication identification 316, a medication list 317, medication information 318, a medication diary 320, a dosage summary 321, interactions 332, and / or a watch list 323. The medication identification 316 may enable the smart device 306 to determine the identity of a medication. For example, the medication identification 316 may receive images and / or videos. The medication identification 316 may process the images and / or videos and request the OCR 310 to extract text from the images and / or videos. The text may be used by the medication identification 316 to determine a medication identifier, which may include one or more of an identification number (e.g., NDC), an active ingredient (e.g., generic drug name, or brand name).

[0142] As described herein, a user may capture medications and / or medication use using medication module 314. In one example, medication identification 316 may assist a user in identifying medications. Medication list 317 may determine a list of medications the user is using, and the list of medications may include the identified medication. For example, the identified medication may be added to the list of medications by medication list 317. Medication list 317 may allow a user to capture a photo and assign the photo to the identified medication. Medication information 318 may provide medication information for the identified medication. Medication diary 320 may record when the user consumed the identified medication. And, dosage summary 321 may determine and / or display a summary of how much of the active ingredient the user consumed, if the identified medication may contain an active ingredient.

[0143] As another example, medication identification 316 may receive data, such as text input, from a user (e.g., a patient). The text may indicate a medication identification. The text may indicate an NDC, and medication identification 316 may perform a lookup and / or validation of the NDC using API 304. The text may indicate an active ingredient of the medication, and medication identification 316 may determine a medication identifier associated with the active ingredient. The text may indicate a brand name (e.g., manufacturer name, store name, etc.). Medication identification 316 may determine a medication identifier associated with the brand name.

[0144] The medication identification 316 may validate the medication identifier by using the API 304. For example, the medication identification 316 may use the RxNorm API to send a request to validate the NDC. The medication identification 316 may use the API 304 to send a request for information about the identified medication. For example, the medication identification 316 may use openFDA to send a request for information about the medication identified in the RxCUI and / or NDC.

[0145] Medication identification 316 may determine whether a medication contains one or more active ingredients. For example, many medications, such as cold medicines, contain one or more active ingredients that can be used to address a patient's symptoms. Medication identification 316 may identify one or more of the active ingredients and provide a list of those ingredients to the user. Medication identification 316 may identify one or more active ingredients and provide the ingredients to another module, such as medication list 317, medication information 318, medication diary, and / or summary 321.

[0146] In one example, medication identification 316 may allow a user to perform a free-text search for medications. Medication identification 316 may provide an auto-complete feature, and entries in the auto-complete list may be populated with RxNorm branded drug TTYs and / or clinical drug TTYs retrieved via the RxNorm API. The RxNorm API may be used to resolve medications entered by a user using the RxCUI. Medication list 317 may provide a list of medications that a user, such as a patient, may be taking. For example, medication list 317 may provide a list of one or more medications consumed by the user. Medication list 317 may include or be a self-reported list. For example, a user may use device 306 to record medications they are taking, such that medication list 317 may provide a list of current medications used by the user.

[0147] The medication list 317 may allow a user, such as a patient, to add, edit, and / or delete prescription (e.g., Rx) and OTC entries to the medication list. The medication list 317 may include integration with one or more APIs, such as RxNorm and openFDA, which may allow the medication list 317 to identify medications provided by the user. The user may include a photo of the bottle (e.g., prescription bottle) or packaging and / or the actual medication as part of the medication details. The medication list 317 may store this photo so that it can be displayed along with the medication name to help the user (e.g., patient) identify the medication.

[0148] Medication information 318 may provide the user with information regarding medication. An example of medication information can be seen at 700 in FIG.

[0149] Referring again to FIG. 3 , the medication information 318 module may provide medication information, which may include details about the medication, such as the drug name and strength (e.g., dosage). For example, the user may be informed that the medication's identification is Tylenol Extra Strength 500 mg Oral Tablets. The medication information may include an NDC code. For example, the user may be informed that the NDC code is in the 10-digit or 11-digit format of the NDC and may be provided with the NDC. The medication information may include a photo of the medication from the manufacturer, the FDA, a regulatory agency, a combination thereof, etc. The medication information may include instructions, administration, and / or reminders. For example, the user may be informed about how the medication may be used. The medication information may include links and / or information from external sources, such as MedlinePlus's DailyMed.

[0150] The embodiments described herein may provide medication reminders. For example, a user may be provided with a daily reminder to record their medication. The reminders may be specific to one or more medications. For example, a first reminder may be set and / or provided for a first medication, and a second reminder may be set and / or provided for a second medication. In one example, reminders may be provided for a group of medications (e.g., all medications).

[0151] The medication information may include potential drug interactions with the user's other medications. Potential drug interaction alerts may be received and / or determined from the National Library of Medicine, the FDA, regulatory agencies, etc.

[0152] The medication diary 320 may allow the user to enter medications the user has consumed along with the time and / or date the medication was consumed. The medication diary 320 may log when the user may have consumed a medication along with the identity of the medication. The medication diary 320 may use the API 304 to retrieve data from the database 302 regarding medications the user may have previously consumed, the dates those medications were consumed, the time those medications were consumed, etc. The medication diary 320 may capture daily medication usage (e.g., amounts or units) in real time or retrospectively (e.g., based on entries in the medication list 317).

[0153] The dosage summary 321 may provide the smart device 306 with the ability to determine how much medication and / or how much active ingredient a user may have consumed within a certain period of time. For example, the dosage summary 321 may determine hourly dosages (e.g., 8-hour, 12-hour, 23-hour, 48-hour, etc.), daily dosages, weekly dosages, monthly dosages, combinations thereof, etc. The dosages may be for the active ingredient. For example, the dosage summary 321 may determine the daily dosage of acetaminophen.

[0154] Dosage summary 321 may determine how many active ingredients the user may have consumed and how many of those active ingredients the user may have consumed. For example, if the user consumes a cold medicine with three active ingredients and a headache medicine with two active ingredients, dosage summary 321 may provide a summary of five active ingredients.

[0155] As another example, a user may consume a first medication containing 100 mg of caffeine, 500 mg of aspirin, and 500 mg of acetaminophen. The user may consume a second medication containing 600 mg of acetaminophen and 30 mg of codeine. Medication identification 316 may identify the first medication, the second medication, and the active ingredients of the first medication and the second medication. Dosage summary 321 may summarize the active ingredients such that the user may be informed that they have consumed 100 milligrams of caffeine, 500 mg of aspirin, 1100 mg of acetaminophen, and 30 mg of codeine.

[0156] Dosage summary 321 may include information about one or more medications. For example, dosage summary 321 may include information about one or more medications in association with or in communication with medication information 318. The information may include the name of the medication, NDC, medication image and / or video, label information, a link to the label information, ingredient information, a link to the ingredient information, drug interactions, side effect reports, combinations thereof, etc. Dosage summary 321 may, for example, be associated with or in communication with medication information 318 to implement the method illustrated with respect to FIG. 8 and / or provide the information illustrated with respect to FIGS. 9A-9C.

[0157] 3, interactions 322 may analyze one or more medications consumed or that may be consumed by the user. Interactions 322 may determine whether interactions between medications may occur. Interactions may include interactions between medications, interactions between medications and food, interactions between medications and substances (e.g., alcohol, illegal drugs, legal drugs, etc.), combinations thereof, etc.

[0158] Interactions, such as drug interactions, can be classified into several types, depending, for example, on their effect on the patient's health.

[0159] One type of drug interaction may be a synergistic effect that can occur when two or more drugs are taken together, where their combined effect is greater than the sum of their individual effects. For example, some combinations of drugs may enhance the overall therapeutic effect, potentially resulting in more effective treatment of a health condition.

[0160] One type of drug interaction can be an adverse drug interaction, which can occur when the combination of drugs produces harmful effects. These can include an increased risk of side effects, a decrease in the effectiveness of one or both drugs, and / or the development of health problems that were not present before the drugs were combined.

[0161] One type of drug interaction can be an antagonistic interaction, which can occur when one drug reduces the effectiveness of another. For example, one or more antibiotics can interfere with the absorption of oral contraceptives, potentially reducing their effectiveness.

[0162] One type of drug interaction can be a pharmacokinetic interaction, which can occur when one drug affects the body's ability to process another drug, possibly altering its absorption, distribution, metabolism, and / or excretion.

[0163] Interactions 322 may monitor one or more medications that a user may consume and may evaluate possible interactions between these medications. Interactions 322 may predict and / or prevent possible drug interactions. For example, interactions 322 may determine that a first medication consumed by a user may have an interaction with a second medication consumed by the user.

[0164] Interaction 322 may inform the user of the interaction and / or possible interaction. In one example, interaction 3222 may generate an alert or reminder, potentially allowing the user to adjust their medication intake or consult with a medical professional.

[0165] Interaction 322 may learn from a user's medication history. For example, over a period of time, interaction 322 may identify patterns or trends, which may help improve its interaction analysis and predictive capabilities.

[0166] The watchlist 323 may monitor a list of medications provided by a healthcare provider (HCP). The HCP may be a pharmacist, physician, surgeon, etc. In one example, a physician may want to ensure that a patient is avoiding a particular class of medications that may interact with medications the physician has prescribed for the patient.

[0167] The watchlist 323 may monitor medications and maintain a record of medications that pose a risk to the patient due to potential interactions with other drugs, combinations thereof, etc. The watchlist 323 may provide a safeguard for the patient by alerting the patient or healthcare provider to potential risks.

[0168] In one example, a surgeon may want to ensure that a patient avoids one or more medications before surgery. The watch list 323 may function by alerting the surgeon or patient if a potentially harmful medication is detected in the patient's current list of medications.

[0169] The watchlist 323 may receive updates from the HCP or the HCP's system about changes to a patient's medication regimen. The watchlist 323 may receive updates about drug interaction studies. This may help keep the watchlist current and improve the accuracy of its monitoring function.

[0170] The watchlist 323 may allow for manual input from a healthcare provider or the patient themselves, which may provide a layer of customization that may allow for the inclusion of one or more medications that may be relevant to the patient due to their health condition or status.

[0171] The watchlist 323 may provide an interface that allows a user to view and understand the information it contains. This may include a list of medications to avoid, the reasons for their inclusion on the list, and the potential consequences of ignoring these warnings. The dynamic capture 308 may be used to capture images, videos, etc. The dynamic capture 308 may also provide image and / or video processing. For example, the smart device 306 may use the dynamic capture 308 to capture an image of a medication label, which may be used to determine the medication's identity and / or other information about the medication. As another example, the dynamic capture 308 may allow a user to point the camera of the smart device 306 at the label to capture information about the medication without the user having to record an image or video.

[0172] The OCR 310 may determine text and / or other information from the image or video. For example, the OCR 310 may be used to determine the text on a label. The text may be used to determine information about the medication. The text may include a National Drug Code (NDC). For example, the OCR 310 may detect the NDC, active ingredients, brand name, combinations thereof, etc. The detected information may be used by the smart device 306 to determine the identity of the medication and / or the active ingredients associated with the medication.

[0173] The AI / ML 312 module may be used to analyze and / or capture personalized medication data, medication usage data, medication consumption data, and medication data associated with a user (e.g., a patient). For example, an image or video of a medication label may be analyzed by the AI / ML 312 to determine the identity of the medication. As another example, an image or video of a medication may be used to determine the NDC associated with the medication and may be used to determine the active ingredients contained in the medication.

[0174] AI / ML 312 may include machine learning, a branch of artificial intelligence that seeks to build computer systems that can learn from data without human intervention. These techniques may rely on creating analytical models that can be trained to recognize patterns in datasets such as collections of medication labels, medication images, etc. These models may be deployed to apply these patterns to data such as medication labels to improve medication identification. AI / ML 312 may include supervised machine learning, unsupervised machine learning, reinforcement learning, and / or cognitive computing (CC). For example, AI / ML 312 may employ one or more self-teaching algorithms that may use cognitive computing (CC) to identify medications and / or active ingredients associated with medications using data mining, visual recognition, and / or natural language processing.

[0175] The API 304 may enable the smart device 306 to send and / or retrieve data from the database 302. For example, the smart device 306 may use the API 304 to retrieve data about medications from a drug dictionary, an electronic medical record (EMR), the National Library of Medicine, the National Institutes of Health (NIH), the Federal Drug Administration (FDA), combinations thereof, etc. Although the API 304 may be illustrated as including RxNorm, openFDA, and drug dictionary APIs, the API 304 may include additional APIs that may be provided by regulatory agencies, private companies, pharmaceutical companies, hospitals, EMR providers, machine learning providers, cloud software providers, combinations thereof, etc. For example, the drug dictionary API may be an API that may enable the device 306 to send and / or receive data from commercial drug dictionaries such as REDBOOK and / or the Gold Standard Drug Database.

[0176] The API 304 may include RxNorm. RxNorm is an API provided by the National Library of Medicine. RxNorm may use and / or provide a unified medical language system. RxNorm may provide normalized names for clinical drugs and link drug names to many of the drug narrative vocabularies used in pharmacy management and drug interaction software, including those of First Databank, Micromedex, and the Gold Standard Drug Database. By providing links between these vocabularies, RxNorm can broker messages between systems that do not use the same software and vocabulary. RxNorm may enable access to data and / or databases that use the United States Pharmacopeia (USP) Compendium nomenclature from the United States Pharmacopeial Convention. For example, RxNorm may enable access to a cumulative dataset of active pharmaceutical ingredients that the USP may provide.

[0177] In one example, RxNorm may provide the brand name, generic name, and / or active ingredient of a drug or medication. The brand names recognized by RxNorm may be similar to trade names, such as Zocor or Lipitor, which may be the original drug. Products that follow the original drug (e.g., when patent protection for those drugs may have expired) may be referred to as generic drugs. For example, drugs whose active ingredients are equivalent to those of brand-name drugs may be referred to as generic drugs.

[0178] The API 304 may include openFDA, an Elasticsearch-based API provided by the FDA that may include (e.g., serve) public FDA data regarding drugs, devices, and foods. OpenFDA may allow access to data regarding recall enforcement reports, adverse events, drug information, drug reaction information, combinations thereof, etc. OpenFDA may allow access to one or more databases provided by the FDA.

[0179] OpenFDA may provide the brand name and / or generic name of a drug or medication. A brand name may be a name provided by a store or manufacturer, such as "up and up allergy relief" from Target. A generic drug may be a medicine or medication that contains the chemical or active ingredient of a drug that was originally protected by patent. OpenFDA may be used to retrieve product-level details, which may include the product's structured product label (SPL) identification (ID). The product-level details may be used to identify the product.

[0180] Database 302 may include medical data, medication data, data regarding medication identities, data regarding medication effects, data regarding medication side effects, patient information, prescriptions, physician's orders, combinations thereof, etc. Database 302 may include private, public, commercial, regulatory, and / or similar databases. For example, database 302 may include data from Apple Watch, iCloud, etc. Although databases of U.S.-based regulatory agencies are shown with respect to FIG. 3, databases of other regulatory agencies outside the U.S. may be used. Database 302 is not limited to the databases shown with respect to FIG. 3, and other databases that may have data regarding medications and / or medication identities may be used.

[0181] The database 302 may include or may contain data from a drug dictionary, an EMR, a government agency, a health agency, a regulatory agency, a hospital, a research institution, a consumer database, combinations thereof, etc. The drug dictionary may include information about one or more medications (e.g., drugs). For example, the drug dictionary may include information about the NDC associated with the drug, the RxCUI associated with the drug, the active ingredient associated with the drug, the brand name, the OTC name, the generic name, prescribable synonyms, combinations thereof, etc. The drug dictionary may be public or private. For example, the drug dictionary may be a commercially available drug dictionary such as REDBOOK and / or the Gold Standard Drug Database.

[0182] Database 302 may be shown as incorporating data and / or databases from the National Library of Medicine, the National Institutes of Health (NIH), and the Federal Drug Administration (FDA), although other databases and / or regulatory agencies (e.g., regulatory databases) may be used. For example, embodiments described herein may use nationally provided medical identifiers such as those shown in Table 1.

[0183] 3, database 302 may include data from or be a database provided by the National Library of Medicine (NLM) and / or the National Institutes of Health (NIH), such as DailyMed and Medline Plus. Database 302 may include data from or be a database provided by the FDA, such as the NDC database and registered drug database.

[0184] Database 302 may include data from or may include DailyMed, a website and / or database operated by NLM for publishing drug labels (which may be referred to as packet inserts). The content of DailyMed may be updated by the FDA using information that may be received from the pharmaceutical industry (e.g., information obtained from manufacturers).

[0185] Database 302 may include or contain data from MedlinePlus, an online information service produced by the U.S. National Library of Medicine. MedlinePlus provides information from the National Library of Medicine (NLM), the National Institutes of Health (NIH), other U.S. government agencies, and health-related organizations. MedlinePlus provides encyclopedic information on health and drug issues as well as a directory of medical services. MedlinePlus may provide information on medications.

[0186] The database 302 may include or contain data from a drug database provided by the FDA. The drug database may include identification of drug products that may be approved by the FDA (e.g., the Orange Book) based on safety and effectiveness. The drug database may include data regarding therapeutic equivalence evaluations of prescription drugs, such as generic drugs. The drug database may include prescription brand-name drug products, generic drug products, therapeutic biological products, over-the-counter (OTC) brand-name products, OTC generic drugs, combinations thereof, etc. The drug database may include complementary medicines, such as vitamins, herbal medicines, and / or alternative therapies. The drug database may include patient information, product labels, drug approval letters, drug reviews, and / or other drug-related information.

[0187] Database 302 may include data from or may include an NDC database. The NDC database may track products (e.g., at a granular level) including active ingredients, strengths, packaging, manufacturers, and / or adverse events. An adverse event may be associated with an active ingredient with a particular strength (e.g., Vioxx 50 mg) that was quarantined to an individual manufacturer due to excipients, quality control, or contamination.

[0188] The NDC database provides drugs to be listed according to the National Drug Code (NDC). The National Drug Code (NDC) is a product identifier used in the United States for drugs intended for human use. For example, the Drug Listing Act of 1972 requires registered drug establishments to provide the Food and Drug Administration (FDA) with a list of drugs manufactured, prepared, distributed, compounded, or processed for commercial distribution. The NDC may be used to identify and report drug products. While the embodiments shown herein may use the NDC, other drug identifiers, such as a Generic Product Identifier (GPI), may be used.

[0189] 4 depicts an example format of a National Drug Code (NDC). The NDC can be in a format. For example, the NDC can be in a 9-digit format, a 10-digit format, an 11-digit format, or a 12-digit format. Although embodiments described herein may be described with reference to 9-digit, 10-digit, 11-digit, and / or 12-digit formats, other formats, such as formats including various digits, characters, and / or lengths, can be used.

[0190] The NDC format may include one or more portions. The format may include at least one of a labeler code, a product code, or a package code. For example, the NDC format may include a first portion that is a labeler code and a second portion that is a product code. As another example, the NDC format may include a first portion that may be a labeler code, a second portion that may be a product code, and a third portion that may be a package code.

[0191] 4, the NDC 402 may be a three-segment numeric identifier that may be assigned to a drug listed under the Federal Food, Drug, and Cosmetic Act. The segments may identify the labeler or vendor, the product, and / or the trade package (e.g., of the product).

[0192] The labeler code 404 may be assigned by the Food and Drug Administration (FDA) upon submission of a labeler code request. A labeler may be any company that manufactures, repacks, or distributes drug products. The labeler code 404 may be four, five, or six digits in length.

[0193] The product code 406 may be three or four digits long and may identify a company's particular strength, dosage form, and formulation.

[0194] The package code 408 may be one or two digits long and may identify the type and size of the package. In some instances, the product and package segments may include characters other than numbers.

[0195] The FDA may assign a labeler code, but both the product segment and package segment may be assigned by the labeler. In the past, labelers may have had the opportunity to reassign old product codes that were no longer in use to new products. Currently, under FDA validation procedures, when an NDC code is assigned to a product (defined by key characteristics including, for example, active ingredient, strength, and dosage form), it may not be later reassigned to a different product.

[0196] NDC codes may exist in one or more of the following groupings of digits into segments: 5-4, 4-4-2, 5-3-2, 5-4-1, 6-3-2, or 6-4-1. For example, an NDC code may be in a nine-digit format that may include labeler and product code groupings. For example, NDC 402 may be composed of labeler code 404 and product code 405 (5-4), which may be used to identify a product regardless of its packaging.

[0197] In an example, the NDC construction rules may depend on the length of a particular segment. The following rules may apply to 10 or 11 digit formats: If the labeler code can be 5 or 6 digits long, the labeler code can be combined with: A 4-digit product code and a 1-digit package code, with a total NDC length of 10 or 11 digits (5-4-1 or 6-4-1), or A 3-digit product code and a 2-digit package code, with a total NDC length of 10 or 11 digits (5-3-2 or 6-3-2). If the labeler code is 4 digits long, it can be combined with a 4-digit product code and a 2-digit package code for a total NDC length of 10 digits (4-4-2). A registrant or private label distributor with a given labeler code may use a product package code configuration (e.g., a three-digit product code combined with a two-digit package code, or a four-digit product code combined with a one-digit package code).

[0198] The NDC may be printed on the box and / or bottle of the medication, which may be prescription, OTC, etc. In the case of prescription medications that may be repackaged without the original packing, the NDC may be available on the medication instructions, which may be provided to the patient. In examples, the NDC may not appear on the medication label, and embodiments described herein may take one or more actions to identify the medication and / or the NDC.

[0199] The NDC can be a source NDC, a package NDC, and / or a product NDC. The source NDC can be an NDC determined from the product label and / or dosing information. The package NDC can be an NDC in 10-digit or 11-digit format. The package NDC can include a labeler code, a product code, and a package code. The product NDC can be in 9-digit format. The product NDC can include a labeler code and a product code. Although numbers are referenced in reference to the NDC, the NDC can also be in character format, such as a 9-, 10-, 11-, or 12-character format.

[0200] 5 depicts an exemplary method for capturing medications and / or medication usage. Medications may be over-the-counter (OTC) medications, prescription medications, brand-name medications, generic medications, combinations thereof, etc. As shown in FIG. 5 , method 500 may implement one or more of 502, 504, 505, 506, 508, 510, 512, 514, 516, 518, 520, and 522 to capture medications and / or medication usage. Method 500 may be implemented by a smart device that may include one or more of the components shown in FIG. 1.

[0201] 5, at 502, a first medication identifier associated with a medication may be determined. In identifying the medication, it may be determined whether the medication is a prescription or over-the-counter medication. In one example, different methods may be implemented to determine the first medication identifier based on whether the medication is a prescription or over-the-counter medication.

[0202] The first medication identifier may be an NDC, a regulatory identifier, a brand name, a generic name, an active ingredient, etc. In an example, the active ingredient may be the generic name or vice versa. The first medication identifier may be a source NDC.

[0203] In one example, at 502, it may be determined whether an NDC associated with a medication is available. A user may use a smart device camera to take an image and / or video of the medication. The smart device may determine whether the NDC is included in the image and / or video of the medication. The smart device may determine that the NDC may not be included in the image and / or video.

[0204] If the smart device determines that the NDC is available, it may attempt to verify the NDC at 508. The NDC may be determined to be the source NDC. For example, if the NDC is verified, the NDC may be assigned as the source NDC. If the smart device determines that the NDC is unavailable, it may attempt to determine a second medication identifier at 504.

[0205] At 504, a second medication identifier may be determined. The second medication identifier may be an NDC, a regulatory identifier, an RxCUI, a brand name, a generic name, and / or an active ingredient. The second medication identifier may be determined by receiving a medication description from a user and performing a medication search using a database such as RxNorm. In one example, a user may enter a medication description, such as the medication's brand name, generic name, and / or active ingredient. The smart device may query the database using an API such as RxNorm and receive a database identifier for the medication, such as a conceptually unique identifier (RxCUI), a structured product label identifier (SPL ID), or a combination thereof. The database identifier may be assigned as the second medication identifier.

[0206] A validation may be performed at 505. For example, the device may request that the user validate the second medication identifier. The embodiments described herein may leverage the RxNorm API to capture medication data in the medication list.

[0207] The user may provide a medication identifier for the medication. In one example, the user may type in the NDC. In one example, the NDC may not be available to the user and the user may provide the name of the medication. Free-text searches for medications within the application may be complemented with autocomplete and / or confirmation functionality. For example, for autocomplete entries, the list may be populated with RxNorm branded and clinical drug TTYs retrieved via the RxNorm API. The RxNorm API may be used to resolve medications entered by the user using the RxCUI.

[0208] At 506, one or more databases may be queried using the second medication identifier, and the query results may, for example, map the second medication identifier to an associated NDC. In one example, the associated NDC may be mapped to the second medication identifier, and the associated NDC may be assigned as the first medication identifier. In one example, the NDC may be discovered, and an additional database identifier (e.g., SPL ID) may be determined.

[0209] At 507, it may be determined whether the NDC is verified. If the NDC is not verified, the NDC may be verified at 508. If the NDC is verified, the NDC may be used to retrieve additional information and / or identifiers (e.g., SPL ID) at 510.

[0210] At 508, the NDC may be validated. For example, if the first medication identifier indicates it is an NDC, the NDC may be validated against a regulatory database, such as an NDC database provided by the FDA. This may be done, for example, to validate the NDC determined from the medication label to ensure accurate detection of the medication. In an example, the NDC to be validated may be converted into one or more formats to enable validation against one or more databases.

[0211] At 510, for example, the first medication identifier and / or the second medication identifier may be used to determine dosing information associated with the medication. For example, the first medication identifier and / or the second medication identifier may be used to retrieve data from one or more databases. Data from one or more databases may be combined. In an example, the first medication identifier and / or the second medication identifier may be used to determine a database identifier, such as an RxCUI, and a product identifier, such as an SPL ID.

[0212] At 512, one or more active ingredients associated with the medication may be determined. In one example, the first medication identifier and / or the second medication identifier may be used to query one or more databases to determine the active ingredients and / or prescribable synonyms of the medication. In one example, the prescribable synonyms of the medication may be the generic name of the medication.

[0213] In one example, the active ingredient may be associated with a prescription drug, an over-the-counter drug, a complementary drug, a combination thereof, etc. A complementary drug may include vitamins, herbal medicines, and / or alternative therapies.

[0214] A medication may be composed of one or more active ingredients. For example, a cold medicine may contain three active ingredients. By using the first medication identifier and / or the second medication identifier, the active ingredients may be identified and information about those ingredients may be determined. For example, warnings, recalls, patient information, side effect information, dosage information, medication strength, interactions with other medications, etc. may be retrieved.

[0215] At 514, a drug label may be determined. The drug label may be a brand name and / or a combination of one or more active ingredients. For example, the drug label may be "Tylenol (acetaminophen)." The drug label may be determined to indicate the active ingredient, the dosage of the active ingredient, a generic drug name, a combination thereof, etc. For example, the drug label may be determined to clarify which active ingredients a patient may be consuming.

[0216] Drug display names may be selected to prevent user confusion. Drug display names may be selected to indicate common names that may be known to users. For example, the display name may indicate that the drug is similar or equivalent to a brand name such as Tylenol.

[0217] At 516, drug information related to the active ingredient and / or prescribable synonym name may be determined. For example, the drug may be an over-the-counter drug comprised of one or more active ingredients. Prescribable synonyms of the over-the-counter drug may be determined. For example, acetaminophen medication may be determined for the over-the-counter drug Tylenol. In one example, the drug may be determined to be an over-the-counter drug comprised of one or more active ingredients, such as a cold medicine. Information related to the active ingredient and / or prescribable synonym name may be retrieved. In an example, the prescribable synonym name may be the active ingredient name. As described herein, drug information related to the active ingredient and / or prescribable synonym may include side effects, patient information, morning, recall, dosage information, dosage strength, active ingredient strength, interactions with other medications, etc.

[0218] At 518, the drug display name and / or drug information may be presented to the user. For example, the user may be asked to confirm that the drug display name is accurate. In one example, the user may be presented with information indicating how to use the drug identification. In one example, the user may be presented with information indicating side effects that may be associated with the identified drug. In one example, the user may be presented with information indicating potential interactions with another drug.

[0219] The user may be presented with a summary of the active ingredients that the user has consumed. For example, it may be determined that the user has consumed two medications and that five active ingredients are associated with those two medications. It may be determined how many of the five active ingredients the user has consumed from the two medications, and the user may be presented with the total amount consumed for each of the five active ingredients.

[0220] It may be determined that the user has confirmed the identification of the medication is accurate at 520. If the user may not have confirmed the identification of the medication, another attempt to identify the medication may be performed at 502. If the user has confirmed the identification of the medication, the user may be asked to capture an image of the medication at 522.

[0221] At 522, the user may capture an image of the medication so that the image may assist the user in remembering the medication. As described herein, a photo of the medication the user is using may allow the user to better remember which medications to record in the medication diary.

[0222]

[0023] Figure 6 depicts another exemplary method for capturing medications and / or medication usage. As shown in Figure 6, method 600 may include one or more of 610, 612, 614, 616, 618, 620, 622, 624, and 626 for capturing medications and / or medication usage. As shown in Figure 6, method 600 may be performed by device 601, which may be any of the devices disclosed herein, such as device 204 shown with respect to Figure 6. Device 601 may include components 120 shown with respect to Figure 1.

[0223] Referring again to FIG. 6 , at 610, the device 601 may determine the identity of a medication. The identity may include at least one of an NDC, a regulatory identifier, an active ingredient, a brand name, a generic name, a combination thereof, or the like. The medication may be an over-the-counter medication or a prescription medication. The device 601 may determine the identity of the medication by performing a dynamic capture of the medication so that information (e.g., text) can be extracted from an image or video. The device 601 may determine the identity by using artificial intelligence to identify the medication. The device 601 may determine the NDC associated with the medication.

[0224] At 612, the device 601 may verify the NDC number if an NDC is available. For example, if the NDC number is identified, the device 601 may query a database using RxNorm 602 to determine whether the NDC is valid. If the NDC is determined to be valid, the device 601 may assign the NDC as a source NDC.

[0225] The device 601 may use RxNorm 602 to retrieve information about a medication using the NDC. The information may include another medication identifier, a database identifier, dosing information, information about side effects, medication strength, etc. The information may include an RxCUI, which may be a database identifier and / or a medication identifier.

[0226] At 614, the first NDC may be used to determine a second NDC. The device 601 may convert the NDC from one NDC format to another. This may be done, for example, to retrieve data from one or more databases that may use different NDC formats. For example, the NDC may be a source NDC in a 10- or 11-digit format. The source NDC may be converted to a 9-digit format, and the 9-digit format may be used to retrieve information from one or more databases.

[0227] To retrieve available information from one or more databases, the device 601 may use a first NDC (e.g., NDC10 or NDC11) to determine a second NDC (NDC9), where the first NDC may be in a different format than the second NDC. For example, the source NDC may generate a second NDC that may be one of a 9-digit NDC format, a 10-digit NDC format, or an 11-digit NDC format. The NDC format may be any number of character formats, such as a 12-character format.

[0228] The device 601 may use the first NDC and / or the second NDC to retrieve medication information using RxNorm 602. For example, the device 601 may use a 9-digit format NDC to determine an SPL ID (e.g., SPL_SetID). As another example, the device 601 may use an SPL ID that may be associated with the NDC to retrieve medication information using RxNorm.

[0229] At 616, the device 601 may determine the brand name. For example, the device 601 may determine the brand name using an NDC in a 9-digit NDC format (e.g., NDC9). The device 601 may use RxNorm 602 to determine data regarding the brand name of the NDC (e.g., NDC9) associated with the medication. The device 601 may receive the data using RxNorm 602 and analyze the data to determine the brand name associated with the NDC.

[0230] At 618, the active ingredient and / or prescribable synonym name, clinical drug (SCD), and / or branded drug (SBD) may be determined. The device 601 may determine one or more active ingredients used in the medication using a medication identifier and / or database identifier associated with the medication, such as RxCUI. For example, the device 601 may use RxNorm 602 to query and / or retrieve the active ingredient, prescribable synonym name, clinical drug, and / or branded drug. One or more active ingredients may have prescribable synonym names. The device 601 may determine the prescribable synonym names and retrieve information related to the prescribable synonym names. The information about the active ingredient and / or prescribable synonym name may include warnings, recalls, benefits provided by the medication, side effects that may be caused by the medication, diseases that may be treated by the medication, patient information, prescribing information, treatment information, combinations thereof, etc.

[0231] At 620, a drug display name may be determined using the brand name and / or prescribable synonym name. The drug display name may indicate to the user which active ingredients may be included in the medication. The drug display name may indicate the brand name and one or more active ingredients. The drug display name may indicate the brand name, the active ingredient, and the amount of the active ingredient. The drug display name may indicate the brand name, the generic name, the prescribable synonym name, the active ingredient, the amount of the active ingredient, the amount of the brand name medication, a combination thereof, etc. In one example, the device 601 may interact with RxNorm 602 and / or OpenFDA 604 to query and / or retrieve the drug display name or data associated with the drug display name.

[0232] At 622, drug information can be determined using identifying information from the medication. The device 601 may have determined one or more medication identifiers, such as an NDC, RxCUI, SPL ID, etc. The device 601 can query OpenFDA 604 to retrieve information about the identified medication, such as the SPL ID. The device 601 can query DailyMed 606 to retrieve information about the identified medication. For example, the device 601 can retrieve prescribing information, boxed warning information, medication directions and uses, medication dosage and administration, medication contraindications, medication warnings and precautions, adverse reactions to the medication, drug interactions for the medication, overdose information, medication description, clinical pharmacology information, nonclinical toxicology, clinical studies, storage and handling information, SPL information, display panel information, ingredient and appearance information, manufacturing information, marketing status, Drug Enforcement Agency (DEA) schedule, packager information, combinations thereof, etc.

[0233] At 624, the drug's identification information, such as the RxCUI, may be used to determine active ingredient and / or prescribable synonym information. The active ingredient and / or prescribable synonym information may be received from databases associated with the National Library of Medicine (e.g., DailyMed 606 and Medline Plus 608). For example, the device 601 may send a query to retrieve information from OpenFDA 604, DailyMed 606, and / or Medline Plus 608. The information may include articles about the active ingredient and / or prescribable synonym name. Examples of the information can be seen in FIG. 7.

[0234] Referring again to FIG. 6, at 626, information may be displayed to the user and / or the user may be requested to confirm the identification of the medication. For example, the device 601 may present the identification of the medication to the user and request that the user confirm that the identification of the medication is correct. The device 601 may present the user with information retrieved from one or more databases. The device 601 may provide the user with a summary of the medication and the amount of active ingredient contained in the medication. Example information can be seen in FIG. 7.

[0235] FIG. 7 depicts example information about a medication that may be displayed to a user. The information may be medication information 700. The medication information 702 may include medication details 702 and / or drug interactions 704. The medication details 702 may include medication details, such as the drug name and strength, at 710. For example, at 710, the user may be informed that the medication's identification is Tylenol Extra Strength 500 mg Oral Tablets. At 710, the information may include the NDC code. For example, the user may be informed that the NDC code may be in an 11-digit format in the NDC and may be provided with the NDC. The information may include a photo of the medication from the manufacturer, the FDA, a regulatory agency, a combination thereof, etc. The photo may help the user verify that the medication has been identified. The information may include dosing and reminders, at 710. For example, the user may be informed about how the medication may be used. The information may include links and / or information from DailyMed at 706 and / or information from MedlinePlus at 708 .

[0236] The information may include potential drug interactions with other medications that the device may have determined the user may be taking, such as drug interaction 704. Alerts about potential drug interactions may have been received and determined by the National Library of Medicine, the FDA, regulatory agencies, etc.

[0237] 8 depicts an exemplary method for determining the amount of an active ingredient included in a pharmaceutical product. As shown in FIG. 8, method 800 may include one or more of 808, 810, 814, and / or 816 for determining the amount of the active ingredient that may be included in the pharmaceutical product. As shown in FIG. 8, method 800 may be performed by device 801, which may be any of the devices disclosed herein, such as device 204 shown with respect to FIG. 6. Furthermore, device 601 may include component 120 shown with respect to FIG. 1.

[0238] In one example, the device may be used to determine a summary of one or more active ingredients that a user, such as a patient, may have consumed. The summary may be referred to as a dosage summary, a medication summary, an ingredient summary, and / or a dosage summary per active ingredient. The user may use the device to take an image or video of the medication. A medication label may be determined from the image or video of the medication. The medication label may include information about the medication, such as a medication identifier.

[0239] Referring again to FIG. 8 , at 808, a first medication identifier may be determined. The first medication identifier may be an NDC. The first medication identifier may be determined from an image and / or video of the medication, which may include a medication label. For example, the medication label may indicate an NDC. The first medication identifier may be verified against a database and assigned as a source NDC and / or source medication identifier. For example, the first medication identifier may be identified and / or verified by sending a request at 809 using RxNorm 802. At 811, RxNorm 802 may respond by sending a response to device 801. In one example, the response may indicate that the identification was verified. In one example, the response may indicate that the identification could not be verified.

[0240] At 808, an API such as RxNorm 802 may be used to send a request to one or more databases. The request may indicate a request for information associated with a first medication identifier (e.g., an NDC) from one or more databases. The one or more databases may include databases such as a database from the National Institutes of Health and / or a database from the National Library of Medicine. In response to the request, the device 801 may receive the requested information, which may include a second medication identifier, such as an NDC, an RxCUI, etc. The requested information may include a mapping of the first medication identifier to the second medication identifier.

[0241] At 810, the device 801 may determine a second medication identifier for the medication. The device 801 may determine the second medication identifier using the first medication identifier. The device 801 may determine the second medication identifier by analyzing the data received at 808.

[0242] For example, at 809, the device 801 may send a request to a database using an API such as RxNorm. The request may include the NDC. At 811, the database may send a response to the device 801. The response may include a second medication identifier, such as an RxCUI. At 810, the device 801 may determine that the second medication identifier is an RxCUI and at 812, send a request to the database using an API such as RxNorm 802. The database may send a response at 813 to the device 801. The response may include dosing information associated with RxNorm. The dosing information may include a brand name, a clinical drug designation, a brand drug designation, one or more active ingredients associated with the medication, and / or a second medication identifier (e.g., RxCUI), a strength factor, a drug pack designation, a brand pack designation, a name associated with the active ingredient, a unit strength, a combination thereof, or the like.

[0243] At 817, the device 801 may verify the second medication identifier, such as the RxCUI, by sending a request to one or more databases using an API, such as RxNorm 802. At 818, the device 801 may receive a response from the one or more databases. The response may include dosing information and may include confirmation that the RxCUI is associated with the medication. For example, the response may indicate that the RxCUI is valid and / or is valid for the medication.

[0244] At 814, the active ingredients associated with the medication may be determined. A medication may be comprised of one or more active ingredients. Using the first medication identifier and / or the second medication identifier, the device 801 may determine the one or more medication ingredients. The device 801 may determine the amount of the active ingredient that may be included in the medication. The device 801 may do this for one or more (e.g., each active ingredient) associated with the medication so that the device 801 may have an overview of how much of the active ingredient (e.g., each active ingredient) is included in the medication.

[0245] The device 801 may determine whether the medication may be a single-component medication, a multi-component medication, and / or a medication provided in a drug pack. The device 801 may determine the strength associated with the medication and / or the active ingredients in the medication.

[0246] At 816, the device 801 may display a summary to the user. The summary may include a list of the active ingredients in the medication. The summary may indicate the amount of the active ingredients in the medication.

[0247] 9A depicts an exemplary user interface listing one or more identified medications. The data shown in FIG. 9A may be determined, calculated, and / or displayed by the device. The data may include subject id at 902, date at 904, NDC at 906, amount at 908, units at 910, display name at 912, one or more ingredients at 914, dosage at 916, dosage units at 918, combinations thereof, etc. For example, the device may determine one or more active ingredients of the medication, concentrations associated with the one or more active ingredients, amounts of the one or more active ingredients, combinations thereof, etc.

[0248] In one example, the user interface may display a summary, which may be referred to as a dosage summary, a dosing summary, an ingredient summary, and / or a dosage summary by active ingredient.

[0249] 9A, a display name for the medication may be determined at 912. The display name for the medication may include the brand name of the medication, the generic name of the medication, the active ingredient associated with the medication, the strength of the medication, the strength of the active ingredient associated with the medication, combinations thereof, etc.

[0250] 9A, one or more active ingredients of the medication may be determined at 914. The dosage and / or strength of the one or more active ingredients may be determined at 916. The units of the one or more active ingredients may be determined at 918. For example, an extra-strength headache relief medication may be determined to contain 130 mg of caffeine, 500 mg of aspirin, and 500 mg of acetaminophen.

[0251] The date the medication was consumed may be recorded at 904. The NDC of the identified medication may be recorded at 906. The amount of medication and units of medication may be provided at 908. For example, an extra strength headache relief medication may be a tablet and it may be determined that two tablets were consumed.

[0252] 9B depicts an exemplary user interface summarizing one or more active ingredients associated with one or more medications. The data shown in FIG. 9B may be determined, calculated, and / or displayed by the device. The data may include subject identification at 920, date at 922, one or more ingredients at 924, count at 926, average at 928, total at 930, minimum at 932, maximum at 934, combinations thereof, etc. The summaries may be referred to as dosage summaries, dosing summaries, ingredient summaries, and / or dosage summaries by active ingredient.

[0253] In one example, a user may consume one or more medications throughout the day. The medications (e.g., of one or more medications) may be comprised of one or more active ingredients. To help the user understand how much of the active ingredients they are consuming, at 924, the one or more medications may be broken down into one or more active ingredients, and the amount of each active ingredient in the one or more medications may be determined. At 930, a total of the active ingredients may be presented to the user so that they may understand how much of the active ingredient they have consumed within a time frame. The time frame may be a day, month, week, year, etc.

[0254] As shown in FIG. 9B, at 922, the active ingredients may be listed according to a time frame, such as date. Information about the active ingredients may be shown. At 926, a count of how many times the active ingredient was consumed per day may be provided. An average of the amount of the active ingredient may be provided at 928. This may show the user the average amount of active ingredient consumed per count. At 930, a total of the amounts of the active ingredients may be provided to the user. At 932, the minimum amount of active ingredient from the medication consumed by the user may be provided to the user. At 934, the maximum amount of active ingredient from the medication consumed by the user may be provided to the user.

[0255]

[0013] Embodiments herein may provide for medication data aggregation and analysis. Figure 9C depicts an exemplary user interface summarizing one or more active ingredients associated with one or more medications. For example, the data shown in Figure 9C may include a sample of medication diary data, which may include subject identification at 936, date at 938, NDC at 940, RxCUI at 942, amount at 944, units at 946, medication name at 948, one or more ingredients at 950, one or more doses at 952, one or more dosage units at 954, combinations thereof, etc.

[0256] In one example, NDC can be mapped to RxCUIs, which provide detailed information about ingredients, doses (known as strengths), and dosage units. Data can be mapped to various drug classes, such as Anatomical Therapeutic Chemical (ATC) classifications, to address analytical requirements. Aggregation and analysis at the patient or study level can be performed by drug, ingredient, or class using linkages to RxNorm and other drug dictionaries. Medications entered as free text can be mapped using algorithms that can be incorporated as endpoints in the RxNorm API.

[0257] 9D depicts an exemplary user interface providing a summary of daily dosages of one or more active ingredients associated with one or more medications. The data shown in FIG. 9D may include subject identification at 956, date at 958, NDC at 960, RxCUI at 962, amount at 964, units at 966, medication name at 968, one or more ingredients at 970, one or more doses at 972, one or more dosage units at 974, combinations thereof, etc.

[0258] As shown in Figure 9D, embodiments herein may determine how much medication and / or how much active ingredient a user may have consumed within a certain period of time. For example, a summary may be determined for hourly dosages (e.g., 8-hour, 12-hour, 23-hour, 48-hour, etc.), daily dosages, weekly dosages, monthly dosages, combinations thereof, etc. The dosage may be for the active ingredient. For example, a daily dosage of acetaminophen may be determined.

[0259] It may be determined how many active ingredients the user has consumed. It may be determined how many of these active ingredients the user has consumed. For example, if a user consumes a cold medicine with three active ingredients and a headache medicine with two active ingredients, a summary of the five active ingredients may be provided.

[0260] 10 depicts an exemplary user interface listing one or more medications associated with a patient. As shown in FIG. 10, interface 1000 may be an interface that may list medications that a patient may be consuming or may have consumed. For example, interface 1000 may display medications that a user may have used in the past. As another example, at 1002, interface 1000 may display medications that a user may be using or may have been prescribed. At 1006, a user may add a medication to the list of medications.

[0261] In one example, at 1004, the list of one or more medications may include photographs of one or more medications, such as 1008 and 1010. For example, a user may take a photo of a medication and add the photo to the list of one or more medications. The photo may help the user remember the medication. The photo may be a photo of the medication packaging, a label on the medication, a photo of the medication, a photo of the bottle containing the medication, etc. A photo of the medication may be easier for the user to remember than the name of the medication. The photo may be of an item and / or object that may help the user identify the medication. For example, the photo may be a photo of a note the user associates with the medication. As another example, the photo may be a photo of where the user stores the medication.

[0262] 11 depicts an exemplary user interface for capturing medications and / or medication use. At 1100, a user may initiate the initiation of a program for capturing medications and / or medication use. As shown in 1100, a user may have the ability to record their medications (e.g., a medication diary), identify medications, provide and / or review patient information, provide and / or review information about medical conditions, provide and / or review information about allergies, combinations of these, and the like.

[0263] At 1102, a user may be presented with one or more identified medications. The identified medications, such as the list shown at 1108, may include a photo, such as 1110, that the user may have captured. The photo may assist the user in remembering the medication. For example, a photo of the medication's packaging or medication label may be easier for the user to remember than the medication's name. The user may add a new medication, as shown at 1112.

[0264] At 1104, the user may be presented with an interface for adding a medication. The user interface may allow the user to identify the medication using a medication identifier such as NDC, brand name, and / or active ingredient. In one example, the user may enter the medication identifier at 1114 and / or 1116. For example, at 1118, the user may take a photo and / or video of the medication label, and the medication may be identified using information from the photo and / or video, as described herein.

[0265] At 1106, the user may be presented with an interface to indicate which medications the user may have consumed. The user interface may provide the user with the ability to know when the medication was taken. For example, the user interface may indicate that the medication was consumed in the morning at 1122, in the evening at 1120, or in the afternoon at 1124. The user interface may show the display name of the medication. The display name of the medication may include the brand name of the medication, the generic name of the medication, the active ingredient associated with the medication, the strength of the medication, the strength of the active ingredient associated with the medication, combinations thereof, etc.

[0266] 12 depicts an exemplary user interface for capturing medications and / or medication use for a medication list. Interface 1200 may include a medication list module at 1202, a medication diary at 1204, a dose / exposure module at 1206, an interactions module at 1208, a watchlist module at 1210, and a frequently asked questions module at 1212.

[0267] The interface 1200 may include a medication list module 1202. The medication list module 1202 may be an interface for the medication list 317 described with respect to Figure 3. Referring again to Figure 12, the medication list module 1202 may provide a repository of one or more medications that a user is taking or has taken in the past. This may provide a view of the user's medication history, which may be useful to a healthcare provider in understanding the user's health status and planning future treatment.

[0268] At 1214, the user may take a photo or upload an existing photo to identify the medication for the medication list module 1202. This may provide a visually intuitive way for the user to add medications to their list and may be helpful when dealing with multiple medications with complex names.

[0269] At 1216, the user may have the ability to search for medications by their name, active ingredient, or brand name. This search function assists the user in finding medication information and allows for quick and accurate updates to the medication list in module 1202. The search function may help the user learn more about their medications, including potential interactions, side effects, and dosages.

[0270] The interface 1200 may include a medication diary module 1204. The medication diary module 1204 may be an interface for the medication diary 320 described with respect to FIG. 3. Referring again to FIG. 12, the medication diary module 1204 may allow a user to record their medication use over a period of time. For example, a user may record when a medication is taken, the dosage, and any side effects the user experiences. This may provide information about the effectiveness of the medications and their impact on the user's health.

[0271] The interface 1200 may include a dose / exposure module 1206. The dose / exposure module 1206 may be the interface for the dosage summary 322 described with respect to FIG. 3. Referring again to FIG. 12, the dose / exposure module 1206 may allow a user to monitor the amount of medication to which the user is exposed. It may calculate dosage based on information provided by the user or a healthcare provider. This may help ensure that the user is not over- or under-exposed to any medication, which may help prevent adverse drug reactions or ineffective treatment.

[0272] The interface 1200 may include an interaction module 1208. The interaction module 1208 may be the interface for the interaction 322 described with respect to Figure 3. Referring again to Figure 12, the interaction module 1208 may allow the user to analyze potential interactions between the medications the user is taking. It may flag any possible negative interactions or synergies. This may help prevent adverse drug interactions and optimize the benefits of the medication regimen.

[0273] The interface 1200 may include a watchlist module 1210. The watchlist module 1210 may be an interface for the watchlist 323 described with respect to FIG. 3. Referring again to FIG. 12, the watchlist module 1210 may provide the user with a list of medications that the user should avoid and / or monitor. These may be medications that have been identified by a healthcare provider as potentially harmful to the user due to interactions with other medications the user may be taking. This module may help protect the user from harmful drug interactions.

[0274] The interface 1200 may include a frequently asked question (FAQ) module 1212. The FAQ module 1212 may retrieve information from the medication information 318 shown in connection with FIG. 3. Referring again to FIG. 12, the FAQ module 1212 may provide the user with answers to questions about the user's medications. This may include information about side effects, dosage, timing, and potential interactions. The FAQ module 1212 may provide reference for the user and help the user understand and manage their medications more effectively.

[0275] FIG. 13 depicts an exemplary user interface for capturing medications and / or medication use for drug interactions. As described herein, interface 1200 may include a watchlist module 1210. In one example, data may be provided at 1302, which may include various important information about one or more medications. This may include a drug name at 1304, which may allow a user to identify the medication. At 1306, one or more ingredients may be listed, which may inform the user about the active and inactive substances in the medication. At 1308, a link to the product label may be provided. This link may provide the user with access to information about the medication, including its manufacturer, instructions for use, warnings, etc. At 1310, a link to drug information may be provided. This link may direct the user to further detailed information about the medication, including its pharmacological class, common uses, potential side effects, drug interactions, etc.

[0276] 14 depicts exemplary medication information. At 1402, product label information may be provided to the user. The product label information may be the medication information described herein. The product label information may be from a database such as DailyMed. The product label information may be the product label information provided by the link at 1308 shown with respect to FIG. 13.

[0277] Referring again to Figure 14, drug information can be provided at 1404. The product label information can be the dosing information described herein. The drug information can be from a database such as MedlinePlus. The drug information can be the drug information provided by the link at 1310 shown with respect to Figure 13.

[0278] 15 depicts an exemplary user interface for capturing medications and / or medication use for the medication diary. For example, FIG. 15 illustrates one example of a user interface for documenting medications and their use in medication diary module 1204. At 1504, user-provided data may be incorporated, which may include details such as the date and time of medication, the name of the medication, the amount taken, the unit of measure, one or more active ingredients, the dosage, and the unit of the dosage.

[0279] For example, a user may enter a medication name at 1506, enter an amount at 1508, select associated units at 1510, and record the date and time of consumption at 1512 and 1513, respectively. This approach may assist in maintaining a record of medication use, which may be beneficial to both the user and their healthcare provider in some cases.

[0280] At 1502, a dosage alert may be provided that may signal that the user is approaching a threshold for a particular medication. For example, the user may be approaching the maximum recommended dosage of acetaminophen. The ability to flag such an instance may help prevent an overdose or adverse reaction from taking too much medication.

[0281] 16 depicts an exemplary user interface for capturing medications and / or medication use for a medication diary. At 1602, interface 1200 may alert the user that a threshold has been exceeded for a particular medication. For example, the user may have exceeded the maximum recommended amount of acetaminophen for a given period of time.

[0282] In one example, the interface may generate warnings and instructions for the user. The warning may include a message such as, "Warning: You have exceeded the recommended daily limit of acetaminophen. Overdose may result in liver damage." The system may provide instructions such as, "Discontinue use and consult your healthcare provider."

[0283] In addition to these user-responsive alerts, the system may notify a medical professional associated with the user. This may occur automatically or upon user confirmation. The medical provider may take appropriate action, such as contacting the patient for an examination, adjusting a medication regimen, and / or arranging for immediate medical intervention.

[0284] 17 depicts an exemplary user interface for capturing medications and / or medication use for dose or exposure assessment. At 1702, a user of interface 1200 may provide the user with a notification indicating that the user may have exceeded a medication threshold. For example, the user may have exceeded the maximum recommended dose of acetaminophen for a given period of time. This warning may be accompanied by instructions suggesting immediate action, such as discontinuing further intake of the medication, drinking plenty of fluids to help flush out excess medication, or seeking prompt medical attention.

[0285] Interface 1200 may provide recommendations for future actions, such as advice on how to avoid similar incidents in the future. For example, the user may be advised to double-check dosages before taking medications, avoid taking multiple products containing the active ingredient, consult with a healthcare provider before starting new medications, combinations thereof, etc.

[0286] At 1704, the interface 1200 may present a graph plotting cumulative dose or exposure over a period of time, such as a 24-hour cycle. This visual representation may allow the user to understand their drug use patterns and identify any periods of overdose.

[0287] At 1706, interface 1200 may provide a graph that may illustrate the amount of medication taken (e.g., displayed on the y-axis) against a period (e.g., shown on the x-axis), such as the date of a diary entry. This may help a user visualize their medication intake over time, which may be beneficial for managing their medication schedule and adhering to prescribed dosages.

[0288] At 1708, the user may be provided with data detailing exposure to the drug over a period of time. This data may include details such as date, time, ingredient, amount, unit, dosage, total exposure over a period of time, combinations thereof, etc.

[0289] At 1710, the interface 1200 may present a summary of daily drug ingredient dosages. This data may include the date, one or more ingredients, number of intakes, units, average, minimum, maximum, total, combinations thereof, etc.

[0290] 18 depicts an exemplary user interface for capturing medications and / or medication usage for a medication watchlist. In one example, interface 1200 may display data associated with watchlist module 1210, which may include displaying the data in 1800. The data in 1800 may include the name of the medication, one or more active ingredients, and dosing information. The dosing information may further include a product label, a link to the product label, drug information, a link to drug information, combinations thereof, etc. The data in 1800 may provide the user with a view of the user's medication watchlist and provide information about one or more medications that the healthcare provider wants the user to monitor.

[0291] 19 depicts an exemplary user interface for capturing medications and / or medication use for drug interactions. An interaction module 1208 as part of interface 1200 can analyze the list of medications the user is taking and identify potential interactions between them. This can include both positive and negative interactions and can involve assessing the effects of different combinations of medications on the user's health.

[0292] The interface 1200 may display data at 1900 that may include the source of information, the names of the first and second agents, one or more interacting components, a description of the interaction, combinations thereof, and the like.

[0293] This data may be organized based on priority. For example, interactions considered to be of high priority may be listed before interactions classified as lower priority in 1902. This prioritization may help users and healthcare providers quickly identify and address interactions.

[0294] The data presented in 1900 may indicate an interaction between a first drug and a second drug. Interacting components may be involved in this interaction and may be identified in 1904. Information about these interactions may be provided in 1904 and may include the nature of the interaction, the potential impact on the patient, recommended actions for the user or the user's healthcare provider, combinations thereof, etc.

[0295] 20 depicts an exemplary user interface for capturing medications and / or medication usage for a medication watchlist. Interface 1200 may provide data generated by watchlist module 1210. In 2002, this data may include ingredients and / or drug classes on the watchlist.

[0296] A drug class refers to a group of drugs that act in a similar way or have a similar chemical structure. Grouping drugs into classes may allow for better monitoring of drugs that may have interactions. Drug classes may be provided using a classification system such as the Anatomical Therapeutic Chemical (ATC) classification system. The ATC classification system may be used to classify active ingredients of drugs based on the organs or systems they act on, their therapeutic and pharmacological properties, and / or their chemical characteristics. The ATC classification system may be used as a tool for drug utilization research and may aid in the monitoring and analysis of drug use and trends. In one example, a classification system such as the ATC classification system may organize drugs (e.g., drugs) into different hierarchical levels or classes, starting with anatomical groups and then progressing through therapeutic, pharmacological, and chemical subdivisions. This hierarchical structure may enable efficient classification and facilitate comparison of drug use, research, and / or monitoring.

[0297] In 2004, drug classes or drug types may be listed, which may provide the user with an understanding of the category their medication falls into. In 2006, information such as dosing information and / or links to dosing information may be provided for one or more drug classes, which may assist the user in understanding the nature of medications they are advised to avoid.

[0298] In 2008, a list of medications may be provided by a healthcare provider. These may be medications that the user has been instructed to avoid due to potential adverse reactions or interactions with other medications the user is taking.

[0299] In 2010, a list of other medications to avoid may be provided. This may be based on the user's history of potential interactions or other individual health considerations. For example, if the user has previously experienced an adverse reaction to a particular class of medication, medications from that class may be included on this list.

[0300] The above detailed description has set forth various forms of devices and / or processes using block diagrams, flow diagrams, examples, and / or embodiments. To the extent that such block diagrams, flow diagrams, examples, and / or embodiments contain one or more functions and / or operations, those skilled in the art will understand that each function and / or operation in such block diagrams, flow diagrams, and / or examples can be individually and / or collectively implemented by various hardware, software, firmware, or combinations thereof. Those skilled in the art will recognize that all or a portion of some aspects of the embodiments disclosed herein can be equivalently implemented as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or on an integrated circuit, as a combination thereof. Those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed as one or more program products in a variety of forms, and that particular forms of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to effect the distribution.

[0301] The instructions used to program the logic to implement various disclosed aspects may be stored in memory in the system, such as dynamic random-access memory (DRAM), cache, flash memory, or other storage. The instructions may be distributed over a network or by other computer-readable medium. For example, the instructions may be transmitted via messages and / or signals. A computer-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including, but not limited to, a floppy diskette, an optical disk, a compact disc, a read-only memory (CD-ROM), a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic or optical card, a flash memory, or tangible computer-readable storage used in transmitting information over a network (e.g., the Internet) via an electrical, optical, acoustic, or other form of propagated signal (e.g., carrier wave, infrared signal, digital signal, etc.). Non-transitory computer-readable media may include any type of tangible computer-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a device (e.g., a computer).

[0302] As used herein, terms such as "component," "system," "subsystem," "module," and the like may refer to a computer-related entity, device, hardware, software, software in execution, combinations thereof, and the like. The application may refer to "determining" various information. Determining information may include, for example, one or more of estimating information, calculating information, predicting information, or retrieving information from memory.

[0303] Additionally, the application may refer to "receiving" various information. Receiving, like "accessing," is intended to be a broad term. Receiving information may include, for example, one or more of accessing information or retrieving information (e.g., from memory). Furthermore, "receiving" typically involves operating in some way, such as, for example, storing information, processing information, transmitting information, moving information, copying information, erasing information, calculating information, determining information, predicting information, or estimating information.

[0304] For example, in the case of "A / B," "A and / or B," and "at least one of A and B," it should be understood that the use of any of the following " / ," "and / or," and "at least one of" is intended to encompass the selection of only the first enumerated option (A), or the selection of only the second enumerated option (B), or the selection of both options (A and B). As a further example, in the case of "A, B, and / or C" and "at least one of A, B, and C," such language is intended to encompass the selection of only the first enumerated option (A), or the selection of only the second enumerated option (B), or the selection of only the third enumerated option (C), or the selection of only the first and second enumerated options (A and B), or the selection of only the first and third enumerated options (A and C), or the selection of only the second and third enumerated options (B and C), or the selection of all three options (A, B, and C). This can be expanded to many items such as those listed, as will be apparent to those skilled in this and related arts.

[0305] Several examples are described. Features of these examples may be provided alone or in any combination across various claim classes and types. Furthermore, embodiments may include one or more of the following features, devices, or aspects, alone or in any combination across various claim classes and types.

[0306] [Embodiment] (1) A device for determining medication use by a patient, said device comprising: a processor, the processor comprising: determining label information for the medication; using the label information to determine a source national drug code (NDC) associated with the medication; sending a first message to a first server, the first message indicating a request for verification of the source NDC; receiving a second message from the first server, the second message indicating that the source NDC is valid, indicating a product NDC, and indicating a normalized identifier; determining a brand name associated with the drug using the product NDC; using the normalized identifier to determine one or more active ingredients associated with the brand name; and determining a drug label name using the brand name and the one or more active ingredients; determining active ingredient information for the one or more active ingredients; and displaying the drug display name and the active ingredient information to a user. (2) The device of embodiment 1, wherein the normalized identifier is an RxNorm Conceptual Unique Identifier (RxCUI). (3) The device of claim 1, wherein the product NDC includes a labeler code and a product code. (4) The device of embodiment 1, wherein the source NDC is a package NDC, and the package NDC includes a labeler code, a product code, and a package code. (5) The device of embodiment 1, wherein the source NDC includes a labeler code, a product code, and a package code, and the product NDC includes the labeler code and the product code.

[0307] (6) The device of embodiment 1, wherein the processor is configured to determine the label information of the medication by receiving data from a user, the data including at least one of the source NDC, active ingredient, brand name, image, or video. (7) The processor: sending a brand name request message to a second server, the brand name request message indicating a request for a brand name associated with the product NDC; and receiving a brand name response message from the second server, the brand name response message indicating the brand name; 2. The device of claim 1, configured to use the product NDC to determine the brand name. (8) The processor: sending an ingredient request message to the first server, the ingredient request message indicating a request for one or more active ingredients associated with the normalized identifier; receiving an ingredient response message from the first server, the ingredient response message indicating the normalized identifier and indicating one or more active ingredients; and storing said one or more active ingredients in a database so that said one or more active ingredients are associated with said brand name; 2. The device of embodiment 1, configured to determine the one or more active ingredients associated with the brand name. (9) A method implemented by a device for determining medication use by a patient, the method comprising: determining label information for the medication; using the label information to determine a source National Drug Code (NDC) associated with the medication; sending a first message to a first server, the first message indicating a request for verification of the source NDC; receiving a second message from the first server, the second message indicating that the source NDC is valid, indicating a product NDC, and indicating a normalized identifier; determining a brand name associated with the drug using the product NDC; using the normalized identifier to determine one or more active ingredients associated with the brand name; and determining a drug label name using the brand name and the one or more active ingredients; determining active ingredient information for the one or more active ingredients; and displaying the drug display name and the active ingredient information to a user. (10) The method of embodiment 9, wherein the normalized identifier is an RxNorm Conceptual Unique Identifier (RxCUI).

[0308] (11) The method of claim 9, wherein the product NDC includes a labeler code and a product code. (12) The method of embodiment 9, wherein the source NDC is a package NDC, and the package NDC includes a labeler code, a product code, and a package code. (13) The method of claim 9, wherein the source NDC includes a labeler code, a product code, and a package code, and the product NDC includes the labeler code and the product code. (14) The method of embodiment 9, wherein determining the label information for the medication includes receiving data from a user, the data including at least one of the source NDC, active ingredients, brand name, image, or video. (15) A non-transitory computer-readable medium storing processor-executable instructions, the processor-executable instructions comprising: determining an image or video of a medication label; determining a source National Drug Code (NDC) from the image, the source NDC being associated with the medication label; and sending a first message to a first server, the first message indicating a request for verification of the source NDC; receiving a second message from the first server, the second message indicating that the source NDC is valid, indicating a product NDC, and indicating a normalized identifier; determining a brand name associated with the drug using the product NDC; using the normalized identifier to determine one or more active ingredients associated with the brand name; and determining a drug label name using the brand name and the one or more active ingredients; determining active ingredient information for the one or more active ingredients; and displaying the drug display name and the active ingredient information to a user.

[0309] (16) Processor-executable instructions for determining the drug label name using the brand name and the one or more active ingredients, comprising: determining a prescribable synonym name for at least one active ingredient of the one or more active ingredients; and generating the drug display name by combining the brand name with the prescribable synonym name. (17) The processor-executable instructions for determining the active ingredient information for the one or more active ingredients further comprise: sending an active ingredient information request to a third server, wherein the active ingredient information request indicates at least one of a Structured Product Labeling Identification (SPL ID) or the normalized identifier; 16. The non-transitory computer-readable medium of embodiment 15, comprising receiving an active ingredient information response, wherein the active ingredient information response indicates an active ingredient and indicates at least one of a warning, instructions for the active ingredient, or instructions for use, or a drug interaction warning. (18) The non-transitory computer-readable medium of embodiment 15, wherein the normalized identifier is an RxNorm Conceptual Unique Identifier (RxCUI). (19) The non-transitory computer-readable medium of embodiment 15, wherein the product NDC includes a labeler code and a product code. (20) The non-transitory computer-readable medium of embodiment 15, wherein the source NDC is a package NDC, and the package NDC includes a labeler code, a product code, and a package code.

Claims

1. 1. A device for determining a medication used by a patient, said device comprising: a processor, the processor comprising: determining label information for the medication; using the label information to determine a source National Drug Code (NDC) associated with the medication; sending a first message to a first server, the first message indicating a request for verification of the source NDC; receiving a second message from the first server, the second message indicating that the source NDC is valid, indicating a product NDC, and indicating a normalized identifier; determining a brand name associated with the drug using the product NDC; using the normalized identifier to determine one or more active ingredients associated with the brand name; and determining a drug label name using the brand name and the one or more active ingredients; determining active ingredient information for the one or more active ingredients; and displaying the drug display name and the active ingredient information to a user.

2. The device of claim 1 , wherein the normalized identifier is an RxNorm Conceptual Unique Identifier (RxCUI).

3. The device of claim 1 , wherein the product NDC includes a labeler code and a product code.

4. The device of claim 1 , wherein the source NDC is a package NDC, the package NDC including a labeler code, a product code, and a package code.

5. The device of claim 1 , wherein the source NDC includes a labeler code, a product code, and a package code, and the product NDC includes the labeler code and the product code.

6. 10. The device of claim 1, wherein the processor is configured to determine the label information of the medication by receiving data from a user, the data including at least one of the source NDC, active ingredient, brand name, image, or video.

7. the processor: sending a brand name request message to a second server, the brand name request message indicating a request for a brand name associated with the product NDC; and receiving a brand name response message from the second server, the brand name response message indicating the brand name; The device of claim 1 , configured to use the product NDC to determine the brand name.

8. the processor: sending an ingredient request message to the first server, the ingredient request message indicating a request for one or more active ingredients associated with the normalized identifier; receiving an ingredient response message from the first server, the ingredient response message indicating the normalized identifier and indicating one or more active ingredients; and storing said one or more active ingredients in a database such that said one or more active ingredients are associated with said brand name; The device of claim 1 configured to determine the one or more active ingredients associated with the brand name.

9. 1. A method implemented by a device for determining medications used by a patient, said method comprising: determining label information for the medication; using the label information to determine a source National Drug Code (NDC) associated with the medication; sending a first message to a first server, the first message indicating a request for verification of the source NDC; receiving a second message from the first server, the second message indicating that the source NDC is valid, indicating a product NDC, and indicating a normalized identifier; determining a brand name associated with the drug using the product NDC; using the normalized identifier to determine one or more active ingredients associated with the brand name; and determining a drug label name using the brand name and the one or more active ingredients; determining active ingredient information for the one or more active ingredients; and displaying the drug display name and the active ingredient information to a user.

10. 10. The method of claim 9, wherein the normalized identifier is an RxNorm Conceptual Unique Identifier (RxCUI).

11. The method of claim 9 , wherein the product NDC includes a labeler code and a product code.

12. 10. The method of claim 9, wherein the source NDC is a package NDC, the package NDC including a labeler code, a product code, and a package code.

13. 10. The method of claim 9, wherein the source NDC includes a labeler code, a product code, and a package code, and the product NDC includes the labeler code and the product code.

14. 10. The method of claim 9, wherein determining the label information for the medication includes receiving data from a user, the data including at least one of the source NDC, active ingredients, brand name, image, or video.

15. A non-transitory computer-readable medium storing processor-executable instructions, the processor-executable instructions comprising: determining an image or video of a medication label; determining a source National Drug Code (NDC) from the image, the source NDC being associated with the medication label; and sending a first message to a first server, the first message indicating a request for verification of the source NDC; receiving a second message from the first server, the second message indicating that the source NDC is valid, indicating a product NDC, and indicating a normalized identifier; determining a brand name associated with the drug using the product NDC; using the normalized identifier to determine one or more active ingredients associated with the brand name; and determining a drug label name using the brand name and the one or more active ingredients; determining active ingredient information for the one or more active ingredients; and displaying the drug display name and the active ingredient information to a user.

16. processor-executable instructions for determining the drug label name using the brand name and the one or more active ingredients, determining a prescribable synonym name for at least one active ingredient of the one or more active ingredients; and generating the drug display name by combining the brand name with the prescribable synonym name.

17. the processor-executable instructions for determining the active ingredient information for the one or more active ingredients include: sending an active ingredient information request to a third server, the active ingredient information request indicating at least one of a Structured Product Labeling Identification (SPL ID) or the normalized identifier; 16. The non-transitory computer-readable medium of claim 15, comprising receiving an active ingredient information response, the active ingredient information response indicating an active ingredient and indicating at least one of a warning, instructions for the active ingredient, or usage instructions, or a drug interaction warning.

18. 16. The non-transitory computer-readable medium of claim 15, wherein the normalized identifier is an RxNorm Conceptual Unique Identifier (RxCUI).

19. 16. The non-transitory computer-readable medium of claim 15, wherein the product NDC includes a labeler code and a product code.

20. 16. The non-transitory computer-readable medium of claim 15, wherein the source NDC is a package NDC, the package NDC including a labeler code, a product code, and a package code.

Images