Systems, methods, media and devices for capture of drug and drug use

Abstract

Systems, methods, non-transitory computer-readable media, and / or devices are provided for determining a medicament used by a patient. Label information for the medication may be determined. A source national drug code (NDC) associated with the drug may be determined. The source NDC may be validated. A product NDC and a 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. Drug display names may be determined. The drug display name and the active ingredient information of the one or more active ingredients may be displayed. A summary indicative of the amount of the active ingredient may be displayed, for example, based on a drug diary.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 422,824, filed on November 4, 2022, the disclosure of which is incorporated herein by reference in its entirety. Background Art

[0003] Drugs play a role (e.g., a vital role) in the treatment and management of diseases and symptoms. Records of patient medications (e.g., complete and accurate records) may be important for the safe and effective use of medications. However, deviations between recorded and reported medications may be common. Such deviations may lead to medication errors. Reducing medication deviations and errors may be important for achieving medication safety (e.g., further medication safety). Summary of the Invention

[0004] Systems, methods, non-transitory computer-readable media, and / or devices for capturing medications and / or medication use may be provided. For example, an apparatus for determining medications used by a patient and / or a method performed by the apparatus may be provided. Label information for the medication may be determined. A first message may be transmitted 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 conceptually unique identifier (RxCUI). The first NDC may be used to determine a second NDC. The second NDC may be in a second format. The second format may be different from the first format. The second NDC may be used to determine a brand name. The RxCUI may be used to determine one or more active ingredients. The one or more active ingredients may be associated with the brand name. The brand name and the one or more active ingredients may be used to determine a medication display name. Active ingredient information for the one or more active ingredients may be determined. The drug display name and the active ingredient information may be displayed to a user (such as the patient).

[0005] Systems, methods, non-transitory computer-readable media, and / or devices for capturing medications and / or medication use may be provided. For example, an apparatus and / or method performed by the apparatus may be provided for determining medications and medication use associated with a patient. Label information for the medication may be determined. A first message may be transmitted 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 Conceptual Unique Identifier (RxCUI). The first NDC may be used to determine a second NDC. The second NDC may be in a second format. The second format may be different from the first format. The second NDC may be used to determine a brand name. The RxCUI may be used to determine one or more active ingredients. The one or more active ingredients may be associated with the brand name. The brand name and the one or more active ingredients may be used to determine a medication display name. Use and a user associated with the medication may be determined. The user may be a patient. Active ingredient information of the one or more active ingredients can be determined. The drug display name, the usage, and the active ingredient information can be displayed to a user (such as the patient).

[0006] Systems, methods, non-transitory computer-readable media, and / or devices for capturing medications and / or medication use may be provided. Label information for a medication may be determined. The label information may be used to determine a source national drug code (NDC). The source NDC may be associated with the medication. A first message may be transmitted to a first server. The first message may indicate a request for verification 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. The product NDC may be used to determine a brand name associated with the medication. The normalized identifier may be used to determine one or more active ingredients associated with the brand name. The brand name and the one or more active ingredients may be used to determine a medication display name. Active ingredient information for the one or more active ingredients may be determined. The medication display name and the active ingredient information may be displayed to a user.

[0007] Systems, methods, non-transitory computer-readable media, and / or devices for summarizing medication use associated with a patient may be provided. A first national drug code (NDC) may be used to determine a first normalized identifier. The first normalized identifier may be associated with a first medication. A second NDC may be used to determine a second normalized identifier. 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 an active ingredient. A medication summary may be displayed. The medication summary may include the name of the medication associated with the active ingredient, and the sum of the first amount and the second amount of the active ingredient. In an example, the medication summary may be referred to as a dose summary by active ingredient. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 Depicted is an example functional block diagram of electronic components of an example smart device for capturing medication and / or medication usage.

[0009] Figure 2A An exemplary architectural diagram of an exemplary system for supporting smart devices is depicted.

[0010] Figure 2B is a message flow diagram for an exemplary system.

[0011] Figure 3 Depicted is a block diagram of a system that may include one or more modules for capturing medications and / or medication usage (eg, software modules such as medication information, medication lists, and dosage summaries).

[0012] Figure 4 An exemplary format for a National Drug Code (NDC) is depicted.

[0013] Figure 5 Depicted are exemplary methods for capturing drugs and / or drug use.

[0014] Figure 6 Another exemplary method for capturing drugs and / or drug use is depicted.

[0015] Figure 7 Depicted are examples of information about medications that may be displayed to a user.

[0016] Figure 8 Depicted are exemplary methods for determining the amount of an active ingredient in a medication.

[0017] Figure 9A An exemplary user interface listing one or more identified medications is depicted.

[0018] Figure 9BAn exemplary user interface for aggregating one or more active ingredients associated with one or more medications is depicted.

[0019] Figure 9C An exemplary user interface for aggregating one or more active ingredients associated with one or more medications is depicted.

[0020] Figure 9D An exemplary user interface providing a summary of daily dosages of one or more active ingredients associated with one or more medications is depicted.

[0021] Figure 10 An exemplary user interface listing one or more medications associated with a patient is depicted.

[0022] Figure 11 Depicted are exemplary user interfaces for capturing medications and / or medication usage.

[0023] Figure 12 An exemplary user interface for capturing medications and / or medication usage for a medication list is depicted.

[0024] Figure 13 Depicted are exemplary user interfaces for capturing medications and / or drug usage for drug interactions.

[0025] Figure 14 Exemplary drug information is depicted.

[0026] Figure 15 Depicted are exemplary user interfaces for capturing medications and / or medication usage for a medication diary.

[0027] Figure 16 Depicted are exemplary user interfaces for capturing medications and / or medication usage for a medication diary.

[0028] Figure 17 Depicted are exemplary user interfaces for capturing medications and / or medication usage for dose assessment or exposure assessment.

[0029] Figure 18 Depicted are exemplary user interfaces for capturing medications and / or medication usage for a medication watch list.

[0030] Figure 19 Depicted are exemplary user interfaces for capturing medications and / or drug usage for drug interactions.

[0031] Figure 20 Depicted are exemplary user interfaces for capturing medications and / or medication usage for a medication watch list. DETAILED DESCRIPTION

[0032] Features described herein may include the development of patient-centric mobile applications to improve capture of medications and usage.

[0033] Systems, methods, non-transitory computer-readable media, and / or devices for capturing medications and / or medication use may be provided. For example, an apparatus for determining medications used by a patient and / or a method performed by the apparatus may be provided. Label information for the medication may be determined. A first message may be transmitted 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 conceptual unique identifier (RxCUI). The first NDC may be used to determine a second NDC. The second NDC may be in a second format. The second format may be different from the first format. The second NDC may be used to determine a brand name. The RxCUI may be used to determine one or more active ingredients. The one or more active ingredients may be associated with the brand name. The brand name and the one or more active ingredients may be used to determine a medication display name. Active ingredient information for the one or more active ingredients may be determined. The drug display name and the active ingredient information may be displayed to a user (such as the patient).

[0034] Systems, methods, non-transitory computer-readable media, and / or devices for capturing medications and / or medication use may be provided. For example, an apparatus and / or method performed by the apparatus may be provided for determining medications and medication use associated with a patient. Label information for the medication may be determined. A first message may be transmitted 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 Conceptual Unique Identifier (RxCUI). The first NDC may be used to determine a second NDC. The second NDC may be in a second format. The second format may be different from the first format. The second NDC may be used to determine a brand name. The RxCUI may be used to determine one or more active ingredients. The one or more active ingredients may be associated with the brand name. The brand name and the one or more active ingredients may be used to determine a medication display name. Use and a user associated with the medication may be determined. The user may be a patient. Active ingredient information of the one or more active ingredients can be determined. The drug display name, the usage, and the active ingredient information can be displayed to a user (such as the patient).

[0035] Systems, methods, non-transitory computer-readable media, and / or devices for capturing medications and / or medication use may be provided. Label information for a medication may be determined. The label information may be used to determine a source national drug code (NDC). The source NDC may be associated with the medication. A first message may be transmitted to a first server. The first message may indicate a request for verification 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. The product NDC may be used to determine a brand name associated with the medication. The normalized identifier may be used to determine one or more active ingredients associated with the brand name. The brand name and the one or more active ingredients may be used to determine a medication display name. Active ingredient information for the one or more active ingredients may be determined. The medication display name and the active ingredient information may be displayed to a user.

[0036] In one example, the normalization identifier may be an RxNorm Conceptually Unique Identifier (RxCUI).

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

[0038] In one example, the source NDC may be a packaging NDC, and the packaging NDC may include a labeler code, a product code, and a packaging code.

[0039] In one example, the source NDC may be in a 10-bit format or an 11-bit format. The product NDC may be in a 9-bit format.

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

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

[0042] In one example, a brand name may be determined using the product NDC by transmitting 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.

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

[0044] In one example, a drug display name can be determined using a 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 display name can be determined by combining the brand name with the prescribable synonym name.

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

[0046] In one example, the active ingredient information may include at least an 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 drug. As described herein, the term dose may be used interchangeably with the term strength.

[0047] Systems, methods, non-transitory computer-readable media, and / or devices for summarizing medication use associated with a patient may be provided. A first national drug code (NDC) may be used to determine a first normalized identifier. The first normalized identifier may be associated with a first medication. A second NDC may be used to determine a second normalized identifier. 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 an active ingredient. A medication summary may be displayed. The medication summary may include a medication name associated with the active ingredient and a sum of a first amount and a second amount of the active ingredient.

[0048] In one example, the first amount and the second amount can be used to determine a minimum amount of active ingredient that a patient consumes.

[0049] In one example, the first amount and the second amount can be used to determine a maximum amount of active ingredient consumed by a patient.

[0050] In one example, the first amount and the second amount can be used to determine an average amount of active ingredient consumed by a patient.

[0051] 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, which may be identified using the first normalized identifier.

[0052] 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.

[0053] In one example, the drug summary may further include a first usage and a second total. The second total may be a third amount of the second active ingredient.

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

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

[0056] In one example, a first usage of a first medication may be determined. The first usage may indicate when the patient consumed the first medication. A second usage of a second medication may be determined. The second usage may indicate when the patient consumed the second medication.

[0057] In one example, the sum can be a first sum, and the drug summary can further include a first use, a second use, a second sum, and a third sum. The second sum can be a third amount of the second active ingredient and a fourth amount of the second active ingredient. The third sum can be a fifth amount of the third active ingredient.

[0058] Figure 1 An exemplary functional block diagram of electronic components of an exemplary smart device for capturing medication and / or medication use is depicted. For example, Figure 1 An exemplary functional block diagram of electronic components of an exemplary smart device for capturing medications associated with a patient and how the patient may use those medications may be depicted. The smart device may be a smartphone (e.g., etc.), tablets (e.g., iPad, Galaxy etc.), smart watches (e.g., Apple Google Pixel Watch, etc.), wearable devices, cellular phones, computers, servers, etc. Component 120 may be incorporated into smart devices, such as devices 204 and 206 (shown with reference to FIG2 ), and / or may be incorporated into computing resources, such as 212 (also shown with reference to FIG2 ). Figure 1 Components 120 may integrate sensing, electromechanical drive, communication, and / or digital processing functionality into the structure and operation of the device. In an example, components 120 may include a controller 122, a communication interface 124, a sensor 126, electrical and electromechanical drives 128, and a power management subsystem 130.

[0059] The controller 122 may include, for example, a processor 132, a memory 134, and one or more input / output devices 136. The controller 122 may be any suitable microcontroller, microprocessor, field programmable gate array (FPGA), application specific integrated circuit (ASIC), etc., adapted to receive data, calculate, store, and drive output data and / or signals. The controller 122 may be a device suitable for embedded applications. For example, the controller 122 may include a system on a chip (SOC).

[0060] 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 may include a graphics processing unit (GPU), an artificial intelligence (AI) processing unit, a machine learning processing unit, and / or another processor suitable for graphics processing, AI, and / or machine learning.

[0061] The memory 134 may include any component or collection of components suitable for storing data. For example, the memory 134 may include volatile and / or non-volatile memory. The 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.

[0062] Input / output devices 136 may include any device 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, and the like. Input / output devices 136 may provide communication within and between components 120, such as between controller 122 and sensor 126, between controller 122 and driver 128, between controller 122 and communication interface 124, and between controller 122 and power management subsystem 130, and serve as a conduit for any other combination of components 120. Components 120 may also support direct communication, for example, between sensor 126 and power management subsystem 130.

[0063] 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. Transmitters 138 and receivers 140 may include any electronic components suitable for communicating to and / or from electronic component 120. For example, transmitter 138 and receiver 140 may provide wired and / or wireless communication to devices external to component 120 and / or external to a device in which component 120 is integrated.

[0064] The transmitter 138 and the receiver 140 can enable wired communication using any suitable communication protocol (e.g., a protocol suitable for embedded applications). For example, the transmitter 138 and the receiver 140 can be configured to enable universal serial bus (USB) communication, Ethernet local area network (LAN) communication, etc.

[0065] The transmitter 138 and the receiver 140 can enable wireless communication using any suitable communication protocol (e.g., a protocol suitable for embedded applications). For example, the transmitter 138 and the receiver 140 can 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. The transmitter 138 and the receiver 140 can be configured to communicate via Bluetooth (e.g., using any supported or customized Bluetooth version and / or using any supported or customized protocol), including, for example, 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 Communication Protocol (RFCOMM). In an example, the transmitter 138 and the receiver 140 can be configured to communicate via Bluetooth Low Energy (LE) and / or Bluetooth Internet of Things (IoT) protocols. The transmitter 138 and the receiver 140 can be configured to communicate via a local mesh network protocol such as ZigBee, Z-Wave, Thread, etc. Such protocols can enable the transmitter 138 and the receiver 140 to communicate with nearby devices such as a user's cell phone and / or smartwatch. Communication with a local networked device such as a mobile phone can enable further communication with other devices across a wide area network (WAN) to a remote device, on the Internet, on an enterprise network, etc.

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

[0067] The transmitter 138 and the receiver 140 can be configured to communicate via mobile wireless protocols such as Global System for Mobile Communications (GSM), 4G Long Term Evolution (LTE), 5G and 5G New Radio (NR), and any variety of mobile Internet of Things (IoT) protocols. Such protocols can enable the transmitter 138 and the receiver 140 to communicate more easily, for example, when the user is on the move, traveling away from home or office, and without manual configuration.

[0068] Sensors 126 may include any device suitable for sensing some aspect of its environment (such as physical, chemical, mechanical, electrical, coded information, etc.). Controller 122 may interact with one or more sensors 126. Sensors 126 may include, for example, camera sensors 142, information sensors 146, motion sensors 148, etc. Although not shown, sensors 126 may include one or more biometric sensors, such as a heart rate sensor, a blood oxygen sensor, a blood pressure sensor, combinations thereof, etc.

[0069] 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 charge-coupled device (CCD), an active pixel sensor, a complementary metal oxide semiconductor (CMOS) sensor, an N-type metal oxide semiconductor (NMOS) sensor, or the like. 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, characters, numbers, a quick read (QR) code, a readable integrated circuit (e.g., a single-line identification chip), a near-field communication (NFC) tag, physical / mechanical keying, a subscriber identification module (SIM), or the like. For example, a user may use the camera sensor 142 to capture an image of a medication label, and the text of the medication label may be processed by the device 120.

[0070] The information sensor 146 may include any sensor suitable for reading stored information. In embedded applications with a physical platform, information can be encoded and stored on a variety of media that can be incorporated into various aspects of the physical design. For example, information about the authenticity, concentration, volume, etc. of a medication that can be consumed by a user and / or can be associated with a device. In an example, information can be encoded on a medication container (e.g., a medication label) using text, characters, numbers, a quick read (QR) code, a data matrix, a readable integrated circuit (e.g., a single-line identification chip), a near-field communication (NFC) tag, a radio frequency identification (RFID), physical / mechanical keying, a user identification module (SIM), etc. The user can scan the QR code using the device, and the device can communicate the information to the controller 122 via the communication interface 124. In an example, the information sensor 146 can also be adapted to write information back to a medium associated with the readable code, such as using a read / write NFC tag.

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

[0072] The device may include one or more drivers 128 for conveying feedback to the user and / or driving 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.

[0073] LED driver 152 may include any circuit suitable for illuminating an LED. LED driver 152 may be controlled by processor 132 via input / output device 136. LED driver 152 may be used to indicate status information to a user. LED driver 152 may include a multi-color LED driver.

[0074] The stepper driver 154 may include any circuit suitable for controlling a stepper motor. The stepper driver 154 may be controlled 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 another example, the stepper driver 154 may be used to control a motor of a prosthetic arm.

[0075] The power management subsystem 130 may include circuitry suitable for managing and distributing power to components of the smart device 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 the input / output device 136 to provide information, such as the 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.

[0076] Figure 2A An exemplary architecture diagram of an exemplary system for supporting devices such as smart devices is depicted. System 200 may include a smart phone 204 with a corresponding application (e.g., app), a smart watch 206 with a corresponding app, a wireless access network 208, a communication network 210, and computing resources 212.

[0077] A smart device may be a smart phone, a tablet (e.g., iPad), a smart watch, a wearable device, a cellular phone, a computer, a server, etc. A smart device may be about Figure 1 The smart device shown may be about Figures 2A to 2B The smartwatch 206 shown (e.g., Apple Google Pixel etc.), smart phone 204 (e.g., Samsung Galaxy etc.) and / or computing resources 212.

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

[0079] Smartwatch 206 may be able to provide a medication list to the user. The medication list may be a list of medications that the user can use and / or may have used. The medication list may be a list of active ingredients found in medications used by the user. Smartwatch 206 may also provide biometric feedback and data, such as heart rate and / or heart rate variability. Smartwatch 206 may perform activity tracking and provide activity information. The user may use smartwatch 206 to add medications to and remove medications from the medication list.

[0080] Computing resource 212 may provide data storage and processing functionality. Computing resource 212 may receive and analyze medication data and / or medication usage data. For example, computing resource 212 may receive and analyze medications used by a user and may determine what active ingredients are contained in the medications and how much of those active ingredients have been consumed.

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

[0082] The communication network 210 may include: a long-distance data network, such as a private enterprise network, a virtual private network (VPN), a public business network; a network interconnection, such as the Internet, etc. The communication network 210 may provide connectivity to computing resources 212 .

[0083] The computing resources 212 may include any server resources suitable for telematics processing and / or storage. For example, the computing resources 212 may include servers, cloud servers, data centers, virtual machine servers, etc. In the example, the smartwatch 206 may communicate with the computing resources 212 via its own wireless link 220, and the smartwatch 206 may communicate with the computing resources 212 via its own wireless link 218.

[0084] System 200 can enable the collection and processing of information related to medications associated with a user (e.g., a patient). For example, system 200 can capture what medications a user may be using, when a user is using a medication, how much medication a user may be consuming, a combination thereof, and the like. System 200 can allow a user to track what medications they may be taking. System 200 can determine how much active ingredient a user may be consuming, which may be a component of a medication.

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

[0086] As another example, a user may consume a first medication and a second medication. The first medication may be composed 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 composed of two active ingredients: 2 mg of the first active ingredient and 4 mg of the second active ingredient. The system 200 may provide an overview of the active ingredients consumed by the user (e.g., a patient). For example, the system 200 may calculate that the user has consumed 12 mg of the first active ingredient, 9 mg of the second active ingredient, and 4 mg of the third active ingredient.

[0087] Figure 2B is an exemplary messaging flow diagram of an exemplary system 200. The system 200 may include communications and processing for functions such as initialization and authentication of the smartphone 204 and / or medication application; data collection from the smartwatch 206 and / or smartphone 204; cloud-based control, triggering, notification messaging, etc.; application-based control, messaging, and notifications; and the like.

[0088] Initialization and authentication messaging 222 can be exchanged between one or more of smartwatch 206, smartphone 204, or computing resource 212. For example, a user can create a user account via smartphone 204. Account information can be processed by computing resource 212. The new user can initialize smartwatch 206 to authenticate smartwatch 206. Information can be communicated to smartphone 204 via messaging 202 and then to computing resource 212 via initialization and authentication messaging 224. Information can be communicated to 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. can be messaged back to smartwatch 206 and / or smartphone 204.

[0089] Data collection functionality may be provided and may include messaging 226 from the smartwatch 206, the smartphone 204, and / or the computing resource 212. The 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 an example, the smartphone 204 may aggregate the messaging 228, process the messaging locally, and / or communicate the messaging or related information to the computing resource 212 via messaging 230.

[0090] System 200 implements cloud-based, application-based, and local-based control functions. For example, personalized medication data, medication data, medication consumption data, active ingredient data, status, and / or reports can 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 can communicate directly with smartwatch 206 using messaging 235.

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

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

[0093] Features and examples described herein may include developing a patient-centric mobile application to improve capture of medications and usage.

[0094] Medications can play a role in the treatment and management of diseases and symptoms, and their safe use requires understanding and considering the medications a patient is currently taking or receiving to avoid omissions, duplications, dosage errors, and potential adverse interactions with new medications being prescribed. However, discrepancies between recorded and reported medications can be common. These discrepancies can occur regardless of medication class or care setting, and can lead to medication errors. Reducing medication discrepancies and errors improves medication safety.

[0095] Discrepancies between recorded and reported medications are common and can occur across all categories of medications and care settings. Discrepancies can occur across the globe. For example, patients in primary care clinics in the United States may experience discrepancies. In one example, patients in primary care centers in Sweden may experience discrepancies. Reported medication discrepancies may occur among patients in a cardiologist’s practice. Discrepancies may occur where patients do not report taking their medications. In the examples, between 30% and 70% of patients may experience an erroneous or unintentional change to their medication when moving from one care setting to another. Common causes of these discrepancies may include medication omissions (e.g., over-the-counter [OTC]), unfilled prescriptions, incorrect dosages, etc. Medication discrepancies can lead to medication errors and adverse outcomes, potentially increasing global health spending.

[0096] To potentially achieve better medication safety and optimize care transitions, several international patient safety organizations, such as The Joint Commission (TJC), the Institute for Healthcare Improvement (IHI), and the World Health Organization (WHO), have recognized medication reconciliation. In one example, a medication history can involve capturing and / or determining the medications a patient is taking, which can include prescription, OTC, and refills. In one example, a medication list can be created and / or determined, where the medication list can include prescription medications, OTC medications, and refills. In one example, medication reconciliation can be accomplished in a manner that reduces the time and resources required by a patient to ensure that the patient has the ability and willingness to accurately provide medication information.

[0097] The example provided herein can provide software (e.g., mobile applications) for identifying and / or capturing medications to help patients capture their medications, track usage, and track compliance, some of which can be associated with diseases or products. The software can avoid requesting lengthy manual entries for medications. The software can include features other than pill reminders and compliance tracking. In view of the large number of medications (e.g., >20,000 Rx, >300,000 OTC) with various active ingredients, strengths, and formulas approved in the U.S., software can assist in the standardization of medication capture. The software can help patients track their personal medication use. The software can capture accurate drug information, such as ingredients, strength, and formula. The software can allow sharing of medication information with healthcare providers, or aggregate medication information for research purposes.

[0098] Determination of drug exposure can be an element (e.g., a key element) in generating real-world evidence (e.g., for regulatory and clinical decision-making). Some healthcare systems may allow (e.g., only allow) the capture of prescription (Rx) medications that may have been keyed in by a healthcare provider. However, many existing healthcare systems may not allow the capture of over-the-counter (OTC) medications. In an example, healthcare systems typically capture prescription medications as medication order or dispensing records, which can be used as a proxy (e.g., medication exposure / patient adherence).

[0099] Self-care models and patient-centered approaches to healthcare can be provided. Self-care can 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 support of a healthcare provider. Guidelines for self-care interventions for health can include recommendations for safe and effective interventions that can be used within an enabling environment (e.g., a supportive enabling environment).

[0100] Many patients who may be mobile and self-medicate may play a role (eg, a central role) in creating and maintaining the patient's medication list (eg, because the patient may know the medications the patient takes each day).

[0101] Self-care interventions can assist (e.g., empower) individuals and communities to manage their health and well-being, strengthen national institutions (e.g., use domestic health resources efficiently), improve primary healthcare, and contribute to universal health coverage. Assisting (e.g., empowering) individuals in managing their respective health can be a priority (e.g., important) because self-care (e.g., better self-care) can be an aspect of preventing the global epidemic (e.g., of chronic noncommunicable diseases). Self-care interventions can provide users with greater choice, accessibility, control, satisfaction, and affordable options for managing their respective healthcare needs. Self-care can recognize the advantages of individuals as active agents in their healthcare rather than passive recipients (e.g., not just passive recipients) of health services.

[0102] The healthcare market can change (e.g., is changing) to adjust (e.g., keep pace) to modern needs (e.g., including self-treatment). Self-treatment can include a patient diagnosing a condition and selecting an appropriate medication from a pharmacy to treat the symptoms of the respective patient. Self-treatment can include allowing consumers to actively participate in their health. When a patient self-treats, access to OTC medications may be relevant (e.g., most important). Medications available today as OTC (e.g., many medications) can be pre-labeled as prescription medications. Safety studies and trials can be conducted on drugs that are considered suitable for use without a prescription.

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

[0104] As disclosed herein, embodiments can improve and / or simplify drug reconstitution for safer drug use. Healthcare interventions may be intended to benefit patients, but may also cause harm. Combinations (e.g., complex combinations) of processes, technologies, and human-computer interactions that may comprise modern healthcare delivery systems may be beneficial. Such combinations of processes, technologies, and human-computer interactions may involve unavoidable risks of patient harm, which may result in actual harm. Drug safety can (e.g., should) begin with appropriate prescription and risk-benefit analysis (e.g., a thorough risk-benefit analysis) of drugs (e.g., each drug).

[0105] Identifying medications may be provided. Creating and maintaining a medication list for a patient may be provided. Creating and maintaining a medication list for each patient may represent fulfillment of a responsibility (e.g., of a physician). Developing (e.g., appropriately developing) and maintaining a medication list (e.g., a correct medication list) for one or more patients may include delegation (e.g., appropriate delegation), implementation of relevant information technology, creation of a system to support the work of maintaining the list, and development of a payment mechanism and performance metrics.

[0106] Medication reconciliation can be a process in which healthcare professionals work with patients to ensure medication information is accurate.

[0107] The medication reconciliation process can assist (eg, may be important in) promoting medication and patient safety during transitions of care. Medication reconciliation can improve medication safety, particularly during transitions of care, by identifying unexpected medication deviations.

[0108] Features described herein may include scalability and / or integration with electronic health records (EHRs). The EHR (e.g., many EHRs) may be a single site EHR or an inpatient record (e.g., limited to inpatient records). To improve medication safety during transitions, the EHR or summary care record may reflect the patient's medication use during the transition period, 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.

[0109] Morbidity (e.g., multiple morbidity) can (e.g., is often) treated with multiple drugs (multiple doses), which can put patients at risk for adverse drug events and drug interactions when used inappropriately. Multiple drugs or multiple doses (e.g., using multiple drugs or multiple doses) may be clinically appropriate. For example, patients with inappropriate multiple doses may be at increased risk for adverse events and may identify adverse health outcomes.

[0110] The capture (e.g., robust capture) of Rx / OTC exposure for real-world data (RWD) and real-world evidence (RWE) can be provided. RWD (real world data) can be data related to the delivery of health care that can be collected from various sources and / or a patient's health status. RWE can be evidence about the use, potential benefits, and / or risks of a medical product, such as clinical evidence. RWE can be derived from 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 can inform health status.

[0111] The potential use of RWE in healthcare decision-making for prescription drugs has likely garnered significant attention from industry, regulatory agencies, and professional societies. Comparatively, less attention has been paid to the potential role of RWE for over-the-counter drugs. There may be many differences between prescription and over-the-counter drugs in the sources of RWD and the requests for evidence (such as RWE). Given that consumers may assume a primary role in managing their conditions without the supervision of healthcare professionals and may also be at the center of the generation and distribution of patient-generated health data, the potential use of patient-generated health data may be relevant to over-the-counter drugs.

[0112] Improved adverse event reporting can be provided. For example, improved adverse event reporting can be provided using NDC codes, images, and diary information. Drug identifiers (such as NDC codes) can be helpful because NDC codes can be relevant to pharmacovigilance and drug safety. In one example, embodiments disclosed herein can be used to determine and / or report adverse events for brand names, prescription drugs, generic drugs, active ingredients, and the like.

[0113] A medical identifier (which may be referred to as a regulatory identifier) ​​may be a code that a regulatory agency may provide so that the medical identifier may identify a drug. The medical identifier may be a national drug code. For example, a national drug code database may use a medical identifier, which may be a national drug code (NDC), to identify a drug. The NDC may allow for tracking products, such as drugs, (e.g., at a granular level). For example, the NDC may allow for tracking drugs based on active ingredient, strength, packaging, manufacturer, combinations thereof, and the like. An adverse event may be associated with a specific strength of active ingredient (e.g., Vioxx 50 mg) that is isolated to individual manufacturers due to excipients, quality control, or contamination.

[0114] In one example, the features described herein can be extended beyond the United States. Products can be identified differently in different regions. For example, drug identifiers (such as NDC and / or RxCUI) can vary by country. For example, drug identifiers can be referred to as regulatory identifiers because the identifiers can be provided by the agency that regulates the drug in a country. Table 1 describes the identifier fields for supported regions that can be used as drug identifiers.

[0115] Table 1

[0116] area Area Code Product ID field Local Product ID Example Austria at at_product_id MA Number 16965 Canada ca dpd DIN 2341093 Colombia CO co_product_id InvimaID INVIMA M-012422 European Union eu ema_ma_number EU MA Code EU / 1 / 04 / 276 / 001 European Union eu ema_product_code Product Number EMEA / H / C / 000471 Indonesia idn idn_product_id Nomor registrasi GKL0122234837A1 Italy it it_product_id AIC 38835056 Malaysia my my_product_id Registration Code MAL12715054ACZ Singapore sg sg_product_id License Number SIN11734P Thailand th th_product_id Registration Code 1C 95 / 60(N) Türkiye tr tr_product_id barcode 86995081 50243 USA uS ndc 9-digit NDC 0169-5174 USA uS ndc 10-digit NDC 0169-5174-1 USA us ndc 11-digit NDC 0169-5174-01

[0117] As disclosed herein, a medical identifier may be an identifier provided by a regulatory agency for identifying a medication, a prescription medication, an over-the-counter medication, an active ingredient, a combination thereof, or the like.

[0118] Medication errors in hospitals can occur during admission or discharge from a clinical unit or hospital. Approximately 30% of these errors can result in patient harm. These errors can occur when a patient is given a list of medications they may be taking or have taken. For example, a patient may take a medication and forget to inform the hospital about it.

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

[0120] The medication module can provide capabilities (e.g., robust capabilities) to help patients capture one or more (e.g., all) of the patient's corresponding medications (e.g., both Rx and OTC). Patients can select medication entries based on one or more of the National Drug Code (NDC), active ingredient, or brand name. Text-based searches can be assisted by one or more automatic prompts or auto-complete features (e.g., so that recording medications is minimal burden). Text-based searches can be assisted by software and / or other software that can provide suggestions, lists, to minimize the burden of typing medications. Optical character recognition (OCR) and / or dynamic scanning can be used, for example, to directly type and / or identify medications. A database identifier (e.g., RxCUI) and / or a medication identifier (e.g., NDC) can be used to capture medications. In an example, a medication identifier can be linked to a database identifier (e.g., linked to the NDC of RxCUI), which can facilitate sharing with healthcare providers (e.g., interoperability, aggregation, and / or analysis of shared medication utilization data for research purposes).

[0121] Creating and maintaining medication records can be challenging for patients and healthcare providers, but can improve medication safety and robust real-world evidence generation. Rx and OTC medications and such corresponding usage can be captured (e.g., easily and robustly) 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 promote interoperability and / or aggregation. Mobile apps can help (e.g., also facilitate) linking medication usage to clinical context and outcomes of such usage. In one example, a patient can play a role (e.g., a central role) in creating medication records for the patient.

[0122] The medication module may allow for the setting of one or more profiles. Profiles may be associated with a user. For example, one or more profiles may be established to accommodate the care of children, elderly individuals, and / or other dependents. The medication module may allow for the monitoring of one or more profiles. In one example, an adult's profile may be monitored. In another example, a child's profile may be monitored. In another example, a child's profile may be monitored by a caregiver, who may be an adult.

[0123] The medication module allows users to capture both prescription and OTC medications. Medication names can be entered using the NDC, active ingredient, or brand name. NDCs can be entered directly or recognized using dynamic OCR, eliminating the need to capture a static image. Users can be prompted to confirm the medication name.

[0124] In one example, text-based searches may be assisted with auto-suggest and / or pick list functionality, which may ensure that recording of medications is minimally burdensome. Medications may be explicitly captured as RxCUI or NDC (e.g., linked to RxCUI) to facilitate interoperability and aggregation.

[0125] In one example, a 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 to evaluate medication modules with ease of use claims.

[0126] As disclosed herein, the medication module may include a medication list and a medication diary. The mobile app may provide a health portal connection for the patient to import the patient's medical records from the patient's healthcare provider, including prescription medication data to build a medication list. The patient may add, edit and / or remove Rx and OTC entries of the medication list through integration with RxNorm and openFDA application programming interfaces (APIs). The patient may include a picture of a bottle (e.g., a prescription bottle) or packaging as part of the medication details. A picture may be displayed along with the name of the medication to help the patient (e.g., the patient) identify the medication. The medication diary may capture daily usage (e.g., amount or unit) of the medication in real time or retroactively (e.g., based on entries in the medication list). The user (e.g., the patient) may edit and / or change the intermediary diary.

[0127] Semantic interoperability may bring challenges in evidence generation using real-world data. Differences in source data captured using different standards and / or terminology to represent semantically similar (e.g., equivalent) concepts may challenge researchers' ability to reproduce real-world research. Standardized terminology systems for biomedical information may be beneficial to biomedical applications and research. Embodiments described herein may utilize standardized terminology systems for biomedical data.

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

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

[0130] Standardized terminology systems for biomedical information have benefited biomedical applications and research. Actual uses of biomedical information may (e.g., may often) require (e.g., need) mapping across terminology systems (e.g., mapping can be a complex and time-consuming process). Implementations described herein may utilize standardized terminology systems for biomedical information.

[0131] In an example, the application provided by the embodiments described herein can use a standardized terminology system for biomedical information. For example, the standard nomenclature system can include drug information.

[0132] Drug information may include drug components such as trade name (e.g., if any), brand name, generic name, active ingredient, drug strength, unit of measurement, dosage form, route of administration, chemical substance, drug class, mechanism of action, physiological effect, manufacturer details, packaging type, size, combinations thereof, etc.

[0133] One or more terminology systems for standardized representation of drugs may be used. These may include the Unique Ingredient Identifier (UNII) dictionary, the National Drug Code (NDC) coding system, the Systematized Nomenclature of Medical-Clinical Terminology (SNOMEDCT) system, the RxNorm system, combinations thereof, and the like. Regional and global source data captured using different standards, terminology, and exchange formats to represent the same or similar data elements may differ. In an example, software may be provided to unify and / or standardize drug information.

[0134] RxNorm is a hierarchical terminology system that provides standardized names for clinical drug entities encoded by RxNorm concept unique identifiers (RxCUIs). These concepts can be linked to one or more source drug vocabularies in the source drug vocabulary used. In an example, medical concepts covered by the RxNorm nomenclature can be used. The embodiments described herein can use RxNorm and / or term types (TTYs) to capture drugs or ingredients, such as active ingredients, multiple active ingredients, brand names, brand drugs, brand drug components, clinical drugs, clinical drug components, etc. In an example, medical concepts within RxNorm can be represented by term types (TTYs), where a TTY (e.g., each TTY) encapsulates drug concepts at different levels of granularity. RxCUIs can be assigned to TTYs. For example, a clinical drug component (SCDC) TTY may consist of an ingredient and its ingredient strength (e.g., "Lisinopril 10 MG" [RxCUI 316151]); a clinical drug dosage form (SCDF) TTY may consist of an ingredient and a dosage form (e.g., "Lisinopril Oral Product" [RxCUI 1164689]); etc. Table 2 provides examples of TTY entities.

[0135] Table 2

[0136] Term Type (TTY) describe Example Example RxCUI PIN Precise ingredients Anhydrous lisinopril 1546022 IN Element Lisinopril 29046 SCDC Semantic Clinical Drug Components Lisinopril 10MG 316151 SCDF Semantic Clinical Drug Form Lisinopril oral tablet 372614 SBDC Semantic Branded Pharmaceutical Ingredients Lisinopril 10mg [Prinivil] 567576 SCD Semantic Clinical Drugs Lisinopril 10MG oral tablet 314076 SBD Semantic Branded Pharmaceuticals Lisinopril 10mg oral tablet [Prinivil]* 206765 SBDF Semantic Branded Pharmaceutical Forms Lisinopril oral tablet [Prinivil] 368865

[0137] The embodiments described herein may use and / or provide a standardized terminology dictionary and / or controlled terminology. Where RxNorm is an ontology system, TTY concepts in the system may be linked to each other via relationships defined in the RxNorm ontology, which may allow for different levels of abstraction. As an example, the RxNorm Clinical Drug "Lisinopril 10MG Oral Tablets" [RxCUI 314076] "is composed of Clinical Drug Component "Lisinopril 10MG"" which "has_ingredient" ingredient "Lisinopril" [RxCUI29046]. These relationships defined in the RxNorm ontology may be traversed to start from a specific TTY and achieve any level of desired abstraction.

[0138] In one example, brand name drugs and clinical drugs can be selected as the basis for text-based drug entries. Brand name drugs and clinical drugs can capture important drug details about ingredients, strengths, and formulas, and can be consistent with drug data imported from an EMR account (e.g., an Eipic or Cemer account), and can also distinguish between brand names and generic names. For example, a user can type "Lipitor 40MG Oral Tablets" (brand name drug) or "Atorvastatin 40MG Oral Tablets" (clinical drug). In the example, a database hierarchical structure can be utilized. For example, using RxNorm relationships and hierarchical structures, brand name drugs can be mapped to clinical drugs. Clinical drugs can be mapped to the clinical drug component "Atorvastatin 40MG", and further to the ingredient "Atorvastatin".

[0139] In the example, brand name drugs (e.g., SBD) and clinical drugs (e.g., SCD) can be selected as the basis for text-based drug entries. These two options are consistent with the recommendations of the National Committee on Prescription Drug Programs (NCPDP), where drug product descriptions can consist of three components: drug name (e.g., drug ingredient or brand name), drug strength, and dosage form.

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

[0141] Table 3

[0142] BN-Brand Name SBD-Branded Drugs BPCK-branded bag SBDC-Branded Drug Components GPCK-imitation package SCD-Clinical Drugs IN-ingredients SCDC-Clinical Drug Components MIN-Multiple ingredients PIN - Precise Ingredient

[0143] The embodiments described herein may provide computer and / or mobile applications that can use National Library of Medicine (NLM) resources, including APIs such as RxNorm, RxTerms, Prescriptable RxNorm, RxClass, interactions, combinations thereof, and the like. The embodiments described herein may utilize drug information available online or locally. For example, the embodiments may use installable versions of NLM resources, such as RxName-in-a-Box.

[0144] In one example, the NLM can provide one or more resources through APIs such as RxTerms, MED-RT, and RxNorm. The APIs can be used by the software described herein to utilize NLM resources. For example, a software application can use the RxNorm API to facilitate the capture of medication data in a medication list. In one example, an auto-suggestion and picklist feature can be used to assist in free-text searches for medications within the application to populate clinical drug or brand name concepts, including strength and formulation.

[0145] The embodiments described herein can utilize the RxNorm API to facilitate capturing medication data in medication lists. In one example, a free text search for medications within the application can be supplemented with auto-complete functionality, where entries in the auto-complete list can be populated with RxNorm brand and clinical drug TTYs retrieved via the RxNorm API. The RxNorm API can be used to resolve medications typed into RxCUI. Table 4 shows examples of some RxNorm API resources that can be used.

[0146] Table 4

[0147] Function Resource endpoints Endpoint Description

[0148] The embodiments described herein can utilize one or more mechanisms to capture drug data. In one example, drug data can be captured using entries from RxNorm's brand (e.g., SBD) or clinical drug component (e.g., SCD) TTY. The embodiments provided herein can capture drug data using entries from RxNorm's clinical drug (SCD) concept, which can be used to address multi-ingredient products that may pose a challenge to users. The embodiments can provide users with the ability to explicitly record drug entries to their medication list and allow entries and records of multi-ingredient products. For example, the RxNorm terminology set can have more than 22,000 SCD concepts. A search for clinical drug concepts containing the active ingredient "acetaminophen" [RxCUI 161] may return more than 400 SCD terms, of which approximately 89% are multi-ingredient concepts. Capturing multi-ingredient 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. The embodiments herein can simplify searches by using delimiters (such as the " / " delimiter) for searches of multi-ingredient products. For example, "acetaminophen / codeine" may be used as a search term for a TTY concept containing the ingredients "acetaminophen" and "codeine." In the example, the lack of a " / " separator in the search may render the SCD and SBD concepts containing a single ingredient.

[0149] In one example, searches for single-ingredient drugs and searches for multi-ingredient drugs (e.g., single-ingredient drugs vs. multi-ingredient drugs) can be performed at similar times or nearly similar times to improve performance (e.g., of RxNorm API calls). In one example, searches for single-ingredient drugs and searches for multi-ingredient drugs (e.g., single-ingredient drugs vs. multi-ingredient drugs) can be separated to improve performance (e.g., of RxNorm API calls). For example, a search for "acetaminophen" can return 440 possible entries for clinical drug concentrations (e.g., both single-ingredient and multi-ingredient). The embodiments described herein can simplify searches so that patients can more easily select drugs from entries (e.g., a list of entries). In one example, the use of " / " can allow a user to search for multi-ingredient drugs, such as "acetaminophen / codeine," when typing text. In one example, an embodiment can detect that " / " may not be used and can treat the search as a single-ingredient search, thereby reducing the number of single acetaminophen entries to 40.

[0150] The National Drug Code (NDC) is a drug identifier and / or product identifier for drugs intended for human use in the United States. The NDC allows the Food and Drug Administration (FDA) to maintain a list of drugs manufactured, prepared, disseminated, compounded, and / or processed for commercial distribution by drug commercial establishments. Drugs can be identified and reported using a 10-digit, three-segment number. This 10-digit, three-segment number may be referred to as the National Drug Code (e.g., most commonly referred to as the NDC number). The three-segment number may have a format such as 4-4-2 (e.g., 4 digits, 4 digits, 2 digits), 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 drug repackers or relabelers). The labeler code may contain 4 or 5 digits. The second segment, the product code, identifies the drug (e.g., including specific strength, dosage form, and formulation). The second segment may contain 3 or 4 digits. The third segment, the product and packaging code (e.g., product code), identifies the package size and type. The third segment may contain 1 or 2 digits. Companies may assign a third segment (e.g., product and packaging codes).

[0151] Drugs entering commercial distribution in the United States may be listed with the FDA. A company may submit NDC numbers assigned to drugs manufactured or distributed by the company (e.g., as part of a company's listing request). The FDA may publish NDC numbers (e.g., NDC numbers) and other information submitted by labelers in an online NDC directory or database.

[0152] Under HIPAA covered transactions, the NDC may (e.g., is required to) be reported in 11-digit format. Government agencies and private payers may request (e.g., require) that the NDC be in eleven (11) digit format and printed on patient leaflets.

[0153] In one example, an 11-digit NDC (e.g., NDC11) may be used. For example, an 11-digit NDC may be used for billing of pharmaceutical products. The Centers for Medicare & Medicaid Services (CMS) and other government entities may use the 11-digit NDC (e.g., as part of their billing claim forms). Government agencies, including those compliant with HIPAA, may request an NDC in the 11-digit format with leading zeros.

[0154] NDC can be mapped to RxNorm (eg, multiple to 1). Depending on the API call, there can be multiple RxCUI returns for a single NDC.

[0155] The embodiments described herein may use OCR for drug identification. For example, one or more cloud-based services (such as Amazon Textract, Google Vision AI and / or Azure Computer Vision) may be used to perform OCR. OCR may be used to identify drug information, such as NDC formatted entities (e.g., 10 and / or 11 digits). OCR may be used to capture image text; brand names and / or generic names. For example, OCR may be used to capture data that may be used to make an API call to retrieve brand names and / or generic names from OpenFDA. OCR may be provided via cloud-based services, device-based services (e.g., dynamic), combinations thereof, and the like. Mobile-based OCR services (e.g., including Google ML) may be used in conjunction with OCR services for drug identification (e.g., NDC identification).

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

[0157] In an example, the OCR service can be exposed through a software development kit (SDK) or language-specific programming library that can be deployed on a device. In the case where the service is deployed locally on the client's device, these SDKs and libraries allow real-time interaction with the service, allowing the service to be consumed without requesting an image or a 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, combinations thereof, and the like.

[0158] In one example, the OCR service can 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 can allow for improved capture and / or identification of medications containing multiple ingredients.

[0159] The embodiments described herein may include feedback from a pharmacist.

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

[0161] The embodiments described herein may perform OCR by using a zoom feature to allow a user to focus on the text of a medication label.

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

[0163] The embodiments described herein can perform multiple scans on tags with reflective backgrounds (eg, gold) or when lower lighting conditions may exist.

[0164] Embodiments described herein may include in-app calculations of compliance and dosage.

[0165] In one example, an NDC number may be requested, but the NDC number may not be available on the drug label. Embodiments described herein may use information retrieved from the drug label to determine the NDC number. In one example, a Universal Product Code (UPC) may be used for an OTC drug that may not have an NDC on the drug label. The UPC may be used to determine the NDC. The drug module may be used to determine a text entry for the name and / or NDC number.

[0166] OTC medications sold in the United States (e.g., most OTC medications sold in the United States) may carry an NDC number. For example, an OTC medication may have an NDC number on the box or packaging. The availability of NDC numbers for prescription medications may vary depending on the repackaging and pharmacy leaflet.

[0167] Figure 3 Depicted is a block diagram of a system that may include one or more modules (e.g., software modules) for capturing medications and / or medication usage. Figure 3 As shown, the system 300 may include a database 302, an API 304, and a smart device 306. The smart device 306 may be a smart phone, a tablet (e.g., an iPad), a smart watch, a wearable device, a cellular phone, a computer, a server, etc. For example, the smart device 306 may include information about Figure 1 As another example, the smart device 306 may be a smart device related to the component 120. Figure 2A To the smart watch 206, smart phone 204 or computing resource 212 shown in Figure B.

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

[0169] The medication module 314 may include medication identification 316, medication list 317, medication information 318, medication diary 320, dosage summary 321, interactions 332, and / or watch list 323. Medication identification 316 may allow the smart device 306 to determine the identity of the medication. For example, medication identification 316 may receive an image and / or video. Medication identification 316 may request OCR 310 to process the image and / or video to retrieve text from the image and / or video. Medication identification 316 may use the text to determine a medication identifier, which may include one or more of an identification number (e.g., NDC), an active ingredient (e.g., a generic drug name or a brand name), or a combination thereof.

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

[0171] As another example, medication identification 316 may receive data, such as a text entry, from a user (e.g., a patient). The text may indicate an identification of the medication. The text may indicate an NDC, and medication identification 316 may use API 304 to perform a search and / or verification of the NDC. 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., a manufacturing name, a store name, etc.). Medication identification 316 may determine a medication identifier associated with the brand name.

[0172] Drug identification 316 can verify the drug identifier using API 304. For example, drug identification 316 can use the RxNorm API to transmit a request to verify the NDC. Drug identification 316 can use API 304 to transmit a request for information about the identified drug. For example, drug identification 316 can use OpenFDA to transmit a request for information about the drug identified using RxCUI and / or NDC.

[0173] Medication identification 316 can determine whether a medication includes one or more active ingredients. For example, many medications, such as cold remedies, include one or more active ingredients that can be used to address a patient's symptoms. Medication identification 316 can identify one or more of the active ingredients and provide a list of these ingredients to the user. Medication identification 316 can identify the one or more active ingredients and provide the ingredients to another module, such as medication list 317, medication information 318, medication diary, and / or overview 321.

[0174] In one example, medication identification 316 may allow a user to perform a free text search for medications. Medication identification 316 may provide auto-complete functionality, where entries in the auto-complete list may be populated by RxNorm brands and / or clinical drug TTYs retrieved via the RxNorm API. The RxNorm API may be used to resolve medications typed by a user using the RxCUI. Medication list 317 may provide a list of medications that a user (such as a patient) may be using. For example, medication list 317 may provide a list of one or more medications that a user has consumed. Medication list 317 may include or may be a self-reported list. For example, a user may use device 306 to record the medications they are using so that medication list 317 may provide a list of current medications that the user is using.

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

[0176] Medication information 318 may provide information about medications to the user. Figure 7 An example of drug information can be seen at 700 in .

[0177] Reference again Figure 3, the medication information 318 module may provide medication information, which may include details about the medication, such as the name of the drug and the strength (e.g., dosage). For example, the user may be informed that the identification of the medication 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 a 10 or 11-digit format in the NDC, and the NDC may be provided to the user. The medication information may include pictures of the medication from the manufacturer, FDA, regulatory agency, combinations thereof, etc. The medication information may include instructions, dosage, and / or reminders. For example, the user may be informed how to use the medication. The medication information may include links and / or information from external sources, such as DailyMed from MedlinePlus.

[0178] Embodiments described herein can provide medication reminders. For example, a daily reminder can be provided to a user to keep track of their medications. Reminders can be specific to one or more medications. For example, a first reminder can be set and / or provided for a first medication, and a second reminder can be set and / or provided for a second medication. In one example, reminders can be provided for a group of medications (e.g., all medications).

[0179] Drug information may include potential drug interactions with the user's other medications. Warnings about potential drug interactions may be received and / or determined from the National Library of Medicine, FDA, regulatory agencies, and the like.

[0180] Medication diary 320 may allow a user to enter medications they have consumed and the time and / or date they consumed the medications. Medication diary 320 may record when a user may have consumed medications and the identity of the medications. Medication diary 320 may use API 304 to retrieve data from database 302 regarding medications the user may have previously consumed, the dates those medications were consumed, the times those medications were consumed, and the like. Medication diary 320 may capture daily usage (e.g., amounts or units) of medications in real time or retroactively (e.g., based on entries in medication list 317).

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

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

[0183] As another example, a user may consume a first medication that includes 100 mg of caffeine, 500 mg of aspirin, and 500 mg of acetaminophen. The user may consume a second medication that includes 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 and second medications. Dose summary 321 may summarize the active ingredients, such that the user may be notified that the user consumed 100 mg of caffeine, 500 mg of aspirin, 1100 mg of acetaminophen, and 30 mg of codeine.

[0184] The dose summary 321 may include information about one or more medications. For example, the dose summary 321 may be associated with or communicate with the medication information 318, including information about one or more medications. The information may include the name of the medication, NDC, images and / or videos of the medication, label information, links to label information, ingredient information, links to ingredient information, drug-drug interactions, adverse reaction reports, combinations thereof, and the like. The dose summary 321 may be associated with or communicate with the medication information 318, for example, to perform a Figure 8 The methods shown and / or may provide information on Figures 9A to 9C The information shown.

[0185] Reference again Figure 3 Interactions 322 can analyze one or more drugs that have been or may be consumed by the user. Interactions 322 can determine whether interactions between drugs are likely to occur. Interactions can include interactions between drugs, interactions between drugs and food, interactions between substances (e.g., alcohol, illegal drugs, legal drugs, etc.) and drugs, combinations thereof, and the like.

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

[0187] One type of drug interaction can be a synergistic effect, which can occur when two or more pharmaceutical products are taken together, and their combined effect is greater than the sum of their individual effects. For example, some combinations of drugs can enhance the overall therapeutic effect, potentially leading to more effective treatment of a health condition.

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

[0189] 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 may interfere with the absorption of a birth control pill, potentially reducing its effectiveness.

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

[0191] Interactions 322 can monitor one or more medications that a user may be consuming and can assess potential interactions between these medications. Interactions 322 can anticipate and / or prevent potential drug interactions. For example, interactions 322 can determine that a first medication consumed by a user may interact with a second medication consumed by the user.

[0192] Interaction 322 can notify the user of an interaction and / or a possible interaction. In one example, interaction 3222 can generate an alarm or reminder, potentially enabling the user to adjust their medication intake or consult a healthcare professional.

[0193] Interactions 322 can learn from a user's medication history. For example, over a period of time, interactions 322 can identify patterns or trends that can help refine its interaction analysis and prediction capabilities.

[0194] The watch list 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 the medications the physician has prescribed for the patient.

[0195] The watch list 323 may monitor medications and may maintain a record of medications that pose a risk to the patient due to potential interactions with other drugs, their combinations, etc. The watch list 323 may provide assurance to the patient by alerting the patient or their healthcare provider to potential risks.

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

[0197] The watch list 323 can receive updates from the HCP or the HCP's system regarding changes to the patient's medication regimen. The watch list 323 can also receive updates regarding studies related to drug interactions. This can help keep the watch list up to date and improve the accuracy of its monitoring function.

[0198] The watch list 323 may allow manual input from a healthcare provider or the patient themselves. This may provide a customization layer that may allow the inclusion of one or more medications that may be relevant to the patient due to the patient's health state or condition.

[0199] The watch list 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 why they are included in the list, and the possible consequences of ignoring these warnings. Dynamic capture 308 may be used to capture images, videos, and the like. Dynamic capture 308 may also provide image and / or video processing. For example, the smart device 306 may use dynamic capture 308 to capture an image of a medication label, which may be used to determine the identity of the medication and / or other information about the medication. As another example, 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 requiring the user to record an image or video.

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

[0201] 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, the AI / ML 312 may analyze an image or video of a medication label to determine the medication's identity. 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 ingredient included in the medication.

[0202] AI / ML 312 may include machine learning, a branch of artificial intelligence, which seeks to build computer systems that can learn from data without human intervention. These processes may rely on creating analytical models that can be trained to recognize patterns within data sets, such as collections of drug labels, drug images, etc. These models can be deployed to apply these patterns to data, such as drug labels, to improve drug 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 use cognitive computing (CC) to utilize one or more self-teaching algorithms that may use data mining, visual recognition, and / or natural language processing to identify drugs and / or active ingredients associated with drugs.

[0203] The API 304 may allow the smart device 306 to transmit 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 U.S. Library of Medicine, the National Institutes of Health (NIH), the Federal Drug Administration (FDA), combinations thereof, and the like. Although the API 304 may be illustrated as including RxNorm, openFDA, and a drug dictionary API, 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, and the like. For example, the drug dictionary API may be an API that may allow the device 306 to transmit and / or receive data from a commercial drug dictionary, such as REDBOOK and / or the Gold Standard Drug Database.

[0204] 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 standardized names for clinical drugs and may link drug names to many drug 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 may mediate messages between systems that do not use the same software and vocabularies. RxNorm may allow access to data and / or databases that use the United States Pharmacopeial (USP) nomenclature from the United States Pharmacopeial Convention. For example, RxNorm may allow access to a cumulative data set of active pharmaceutical ingredients available from the USP.

[0205] In one example, RxNorm can provide the brand name, generic name, and / or active ingredient of a drug or medicine. The brand name recognized by RxNorm can be similar to a trademark name, such as Zocor or Lipitor, which can be a first-time-to-market drug. Products that follow the first-time-to-market drug (e.g., when patent protection for those drugs may end) can be referred to as generic drugs. For example, a drug that has an active ingredient that is equivalent to a brand name drug can be referred to as a generic drug.

[0206] API 304 may include openFDA. OpenFDA is an Elasticsearch-based API provided by the FDA that includes (e.g., serves) public FDA data on drugs, devices, and foods. OpenFDA may provide access to data on recall implementation reports, adverse events, drug information, drug reaction information, combinations thereof, and the like. OpenFDA may provide access to one or more databases provided by the FDA.

[0207] OpenFDA can provide the brand name and / or generic name of a drug or medication. The brand name can be a name provided by the store or manufacturer, such as "up and up allergy relief" from Target. Generic drugs can be drugs or medications that contain the chemical or active ingredient of the drug originally intended for patient protection. OpenFDA can be used to retrieve product-level details, which can include the product's structured product label (SPL) identification (ID). Product-level details can be used to identify the product.

[0208] Database 302 may include medical data, drug data, data regarding drug identification, data regarding drug effects, data regarding drug side effects, patient information, prescriptions, doctor instructions, combinations thereof, and the like. Database 302 may include private, public, commercial, regulatory, and / or similar databases. For example, database 302 may include data from Apple Watch, iCloud, and the like. Although regarding Figure 3 The database of the regulatory agency in the United States is shown, but the databases of other regulatory agencies outside the United States can also be used. Figure 3 The databases shown are not limited to the databases shown, and other databases that may have data about medications and / or medication identities may be used.

[0209] Database 302 may include or may include 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, and the like. A drug dictionary may include information about one or more drugs (e.g., medications). For example, a drug dictionary may include information about the NDC associated with a drug, the RxCUI associated with a drug, the active ingredient associated with a drug, the brand name, the OTC name, the generic name, the prescribing synonyms, combinations thereof, and the like. A drug dictionary may be public or private. For example, a drug dictionary may be a commercial drug dictionary such as REDBOOK and / or the Gold Standard Drug Database.

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

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

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

[0213] Database 302 may include data from MedlinePlus or may include MedlinePlus. MedlinePlus is 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 and a directory of medical services. MedlinePlus may provide information about medications.

[0214] Database 302 may include data from or may include 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 on therapeutic equivalence assessments 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, and the like. The drug database includes complementary medicines such as vitamins, herbs, and / or alternative therapies. The drug database may include patient information, product labels, approval letters for drugs, drug reviews, and / or other drug-related information.

[0215] Database 302 may include data from or may include an NDC database. The NDC database may track products (e.g., at the particle size level), including active ingredients, strengths, packaging, manufacturers, and / or adverse events. An adverse event may be associated with an active ingredient of a particular strength (e.g., Vioxx 50 mg) that has been isolated to various manufacturers due to excipients, quality control, or contamination.

[0216] The NDC database provides drugs listed according to the National Drug Code (NDC). The National Drug Code (NDC) is a product identifier for drugs used for human use in the United States. For example, the Drug Listing Act of 1972 ensures that registered drug facilities provide the Food and Drug Administration (FDA) with a list of drugs that they manufacture, prepare, disseminate, compound, or process for commercial distribution. The NDC can be used to identify and report drug products. Although the embodiments shown herein may use the NDC, other drug identifiers such as the Generic Product Identifier (GPI) can be used.

[0217] Figure 4 An exemplary format of a National Drug Code (NDC) is depicted. An NDC can be in one format. For example, an NDC can be in a 9-digit format, a 10-digit format, an 11-digit format, or a 12-digit format. Although the embodiments described herein may be described with respect to 9-digit, 10-digit, 11-digit, and / or 12-digit formats, other formats may be used, such as formats including various numbers, characters, and / or lengths.

[0218] The format of the NDC may include one or more parts. The format may include at least one of a labeler code, a product code, or a packaging code. For example, the format of the NDC may include a first part that may be a labeler code and a second part that may be a product code. As another example, the format of the NDC may include a first part that may be a labeler code, a second part that may be a product code, and a third part that may be a packaging code.

[0219] like Figure 4 As shown, NDC 402 may be a 3-segment numeric identifier and may be assigned to a drug listed under the U.S. Federal Food, Drug, and Cosmetic Act. The segments may identify the labeler or supplier, the product, and / or the commercial packaging (e.g., of the product).

[0220] The labeler code 404 may be assigned by the Food and Drug Administration (FDA) when a labeler code request is submitted. A labeler may be any company that manufactures, repackages, or distributes a drug product. The labeler code 404 may be 4, 5, or 6 digits long.

[0221] The product code 406 may be 3 or 4 digits long and may identify a company's specific strength, dosage form, and formulation.

[0222] The packaging code 408 may be 1 or 2 digits long and may identify the packaging form and size. In some examples, the product and packaging segments may contain characters other than numbers.

[0223] While the FDA assigns labeler codes, both product and package segments can be assigned by the labeler. In the past, labelers may have had the opportunity to reassign older product codes that are no longer in use to new products. Currently, under the FDA validation program, when an NDC code is assigned to a product (e.g., defined by key characteristics, including active ingredient, strength, and dosage form), it may not be reassigned to a different product at a later time.

[0224] The NDC code may be presented in one or more groupings, such as 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, the NDC code may be in a 9-digit format that may include a labeler and product code grouping. For example, NDC 402 may include a labeler code 404 and a product code 405 (5-4), which may be used to identify a product regardless of its packaging.

[0225] In an example, the NDC structure rules may depend on the length of certain segments. The following rules may apply to 10 or 11 bit formats:

[0226] If the labeler code can be 5 or 6 digits in length, it can be combined with:

[0227] ○ A 4-digit product code and a 1-digit package code, for a total NDC length of 10 or 11 digits (5-4-1 or 6-4-1), or

[0228] ○ A 3-digit product code and a 2-digit package code result in a total NDC length of 10 or 11 digits (5-3-2 or 6-3-2).

[0229] • If the labeler code is 4 digits in length, it can be combined with a product code consisting of 4 digits and a packaging code consisting of 2 digits, for a total NDC length of 10 digits (4-4-2).

[0230] • A registrant or private label distributor with a given labeler code may use a product-package code configuration (eg, a 3-digit product code combined with a 2-digit package code, or a 4-digit product code combined with a 1-digit package code).

[0231] The NDC may be printed on the box and / or bottle of a medication, which may be prescription, over-the-counter, or otherwise. For prescriptions that may be repackaged without the original packaging, the NDC may be provided on the medication insert, which may be inconvenient for the patient. In some 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.

[0232] The NDC may be a source NDC, a package NDC, and / or a product NDC. The source NDC may be an NDC determined based on the product label and / or medication information. The package NDC may be a 10-digit or 11-digit NDC. The package NDC may include a labeler code, a product code, and a package code. The product NDC may be a 9-digit NDC. The product NDC may include a labeler code and a product code. Although numbers are mentioned with respect to the NDC, the NDC may also be in a character format, such as a 9-, 10-, 11-, or 12-character format.

[0233] Figure 5 Described is an exemplary method for capturing medications and / or medication usage. The medications can be over-the-counter (OTC) medications, prescription medications, brand name medications, generic medications, combinations thereof, etc. Figure 5 As shown, method 500 may execute one or more of 502, 504, 505, 506, 508, 510, 512, 514, 516, 518, 520, and 522 to capture drugs and / or drug use. Method 500 may be executed by a smart device, which may include Figure 1 One or more of the components shown.

[0234] Reference again Figure 5 At 502, a first medication identifier associated with a medication may be determined. When identifying the medication, it may be determined whether the medication is a prescription medication or an over-the-counter medication. In one example, different methods may be performed to determine the first medication identifier based on whether the medication is a prescription medication or an over-the-counter medication.

[0235] The first drug 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 a generic name and vice versa. The first drug identifier may be a source NDC.

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

[0237] If the smart device determines that the NDC is available, it may attempt to verify the NDC at 508. The NDC may be determined as 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 not available, it may attempt to determine a second medication identifier at 504.

[0238] 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 description of the medication from a user and performing a search for the medication using a database such as RxNorm. In one example, the user may enter a description of the medication, such as the brand name, generic name, and / or active ingredient of the medication. The smart device may transmit a query to the database using an API (such as RxNorm) and may receive a database identifier for the medication, such as a conceptually unique identifier (RxCUI), a structured product label identifier (SPL ID), a combination thereof, or the like. The database identifier may be assigned as the second medication identifier.

[0239] At 505, a confirmation may be performed. For example, the device may request the user to confirm the second medication identifier. The embodiments described herein may utilize the RxNorm API to capture medication data in a medication list.

[0240] The user may provide a medication identifier for the medication. In one example, the user types 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 supplemented with auto-complete and / or confirmation functionality. For example, in the case of an entry in auto-complete, the list may be populated with RxNorm branded drugs and clinical drug TTYs retrieved via the RxNorm API. The RxNorm API may be used to resolve medications typed by the user using RxCUI.

[0241] 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 found, and an additional database identifier (e.g., SPLID) may be determined.

[0242] 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 at 510 to retrieve additional information and / or an identifier (eg, a SPLID).

[0243] At 508, the NDC may be verified. For example, if the first drug identifier indicates that it is an NDC, the NDC may be verified against a regulatory database, such as an NDC database provided by the FDA. For example, this may be done to verify an NDC determined from a drug label to ensure accurate detection of the drug. In examples, the NDC to be verified may be converted into one or more formats to allow for verification against one or more databases.

[0244] At 510, medication information associated with the medication can be determined, for example, using the first medication identifier and / or the second medication identifier. For example, the first medication identifier and / or the second medication identifier can be used to retrieve data from one or more databases. The data from the one or more databases can be combined. In an example, the first medication identifier and / or the second medication identifier can be used to determine a database identifier (such as RxCUI) and a product identifier (such as SPLID).

[0245] At 512, one or more active ingredients associated with the drug can be determined. In one example, the first drug identifier and / or the second drug identifier can be used to query one or more databases to determine the active ingredient and / or prescribing synonyms of the drug. In one example, the prescribing synonym of the drug can be a generic name of the drug.

[0246] In one example, the active ingredient may be associated with a prescription medication, an OTC medication, a complementary medication, a combination thereof, etc. Complementary medications may include vitamins, herbs, and / or alternative therapies.

[0247] A medication may consist of one or more active ingredients. For example, a cold medicine may include 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, and the like may be retrieved.

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

[0249] The drug display name can be selected to prevent user confusion. The drug display name can be selected to indicate a common name that the user may know. For example, the display name can indicate that the drug is similar or equivalent to a brand name (such as Tylenol).

[0250] At 516, drug information about the active ingredient and / or a prescribing synonym name can be determined. For example, the drug can be an over-the-counter drug consisting of one or more active ingredients. Prescribing synonyms for over-the-counter drugs can be determined. For example, an acetaminophen drug can be determined for an over-the-counter drug Tylenol. In one example, it can be determined that the drug is an over-the-counter drug consisting of one or more active ingredients, such as a cold medicine. Information about the active ingredient and / or a prescribing synonym name can be retrieved. In an example, the prescribing synonym name can be the active ingredient name. As described herein, drug information about the active ingredient and / or a prescribing synonym may include side effects, patient information, morning after, recall, dosage information, drug strength, strength of the active ingredient, interactions with other drugs, and the like.

[0251] 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 identifier. 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.

[0252] A user may be presented with an overview of the active ingredients the user has consumed. For example, it may be determined that the user has consumed two medications, and five active ingredients may be associated with the two medications. It may be determined how much of the five active ingredients the user has consumed from the two medications, and the total amount consumed for each of the five active ingredients may be presented to the user.

[0253] At 520, it may be determined that the user has confirmed that the identification of the medication is accurate. 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 confirms the identification of the medication, then at 522 the user may be asked to capture an image of the medication.

[0254] At 522, the user may capture an image of the medication so that the image can assist in reminding the user of the medication. As described herein, a photo of the medication the user is taking may allow the user to better remember which medication they recorded in their medication diary.

[0255] Figure 6 Another exemplary method for capturing drugs and / or drug use is described. Figure 6 As shown, method 600 may include one or more of 610, 612, 614, 616, 618, 620, 622, 624, and 626 to capture drugs and / or drug use. Figure 6 As shown, the method 600 may be performed by an apparatus 601, which may be any apparatus disclosed herein, such as Figure 6 The device 204 shown. The device 601 may include Figure 1 Component 120 is shown.

[0256] Reference again Figure 6 At 610, device 601 may determine identification information of the medication. The identification information may include at least one of an NDC, a regulatory identifier, an active ingredient, a brand name, a generic name, a combination thereof, and the like. The medication may be an over-the-counter medication or a prescription medication. Device 601 may determine the identification information of the medication by performing dynamic capture of the medication, such that information (e.g., text) may be retrieved from an image or video. Device 601 may determine the identification information by identifying the medication using artificial intelligence. Device 601 may determine an NDC associated with the medication.

[0257] At 612, if the NDC is available, the device 601 may verify the NDC number. For example, if the NDC number has been identified, the device 601 may query the 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 the source NDC.

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

[0259] At 614, the first NDC is used to determine a second NDC. Apparatus 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 utilize different NDC formats. For example, the NDC may be a source NDC in a 10- or 11-bit format. The source NDC may be converted to a 9-bit format, and the 9-bit format may be used to retrieve information from one or more databases.

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

[0261] 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 the 9-bit format NDC to determine the SPL ID (e.g., SPL_SetID). As another example, the device 601 may use the SPL ID (which may be associated with the NDC) to retrieve medication information using RxNorm.

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

[0263] At 618, active ingredients and / or prescription synonym names, clinical drugs (SCDs) and / or brand name drugs (SBDs) can be determined. Device 601 can use a drug identifier and / or a database identifier (such as RxCUI) associated with the drug to determine one or more active ingredients used in the drug. For example, device 601 can use RxNorm 602 to query and / or retrieve active ingredients, prescription synonym names, clinical drugs and / or brand name drugs. One or more active ingredients may have prescription synonym names. Device 601 can determine prescription synonym names and can retrieve information related to prescription synonym names. Information about active ingredients and / or prescription synonym names may include warnings, recalls, benefits provided by the drug, side effects that may be caused by the drug, diseases that may be treated by the drug, patient information, prescription information, treatment information, combinations thereof, etc.

[0264] At 620, the drug display name may be determined using the brand name and / or prescribeable synonym name. The drug display name may indicate to the user which active ingredients may be included in the drug. 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 prescribeable synonym name, the active ingredient, the amount of the active ingredient, the amount of the brand name drug, combinations thereof, and the like. In one example, 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.

[0265] At 622, drug information may be determined using identification information from the drug. Device 601 may have determined one or more drug identifiers, such as NDC, RxCUI, SPLID, etc. Device 601 may transmit a query to OpenFDA 604 to retrieve information about the identified drug, such as an SPL ID. Device 601 may transmit a query to DailyMed 606 to retrieve information about the identified drug. For example, device 601 may retrieve prescription information, boxed warning information, indications and usage of the drug, dosage and administration of the drug, contraindications for the drug, warnings and precautions for the drug, adverse reactions to the drug, drug interactions with the drug, overdose information, a description of the drug, clinical pharmacology information, nonclinical toxicology information, clinical studies, storage and handling information, SPL information, display panel information, ingredients and appearance information, manufacturing information, marketing status, Drug Enforcement Administration (DEA) schedule, packager information, combinations thereof, and the like.

[0266] At 624, the active ingredient and / or prescribing synonym information may be determined using identification information of the drug (such as RxCUI). The active ingredient and / or prescribing synonym information may be received from a database associated with a national library of medicine (e.g., DailyMed 606 and Medline Plus 608). For example, the device 601 may transmit a query to retrieve information from OpenFDA 604, DailyMed 606, and / or Medline Plus 608. The information may include articles about active ingredient and / or prescribing synonym names. Examples of information may be found at Figure 7 Seen in.

[0267] Reference again Figure 6At 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 may request the user to confirm that the identification of the medication is correct. The device 601 may present information retrieved from one or more databases to the user. The device 601 may provide the user with an overview of the medication and the amount of active ingredient included in the medication. Examples of information may be found at Figure 7 Seen in.

[0268] Figure 7 An example of information about a medication that can be displayed to a user is depicted. This information may be medication information 700. Medication information 702 may include medication details 702 and / or drug interactions 704. Medication details 702 may include medication details, such as the medication name and strength at 710. For example, at 710, the user may be informed that the medication is identified as Tylenol Extra Strength 500 mg Oral Tablets. At 710, this information may include an NDC code. For example, the user may be informed that the NDC code may be in an 11-digit format within the NDC, and the NDC may be provided to the user. Information may include images of the medication from the manufacturer, the FDA, regulatory agencies, or combinations thereof. This image may help the user confirm that the medication has been identified. Information may include dosing instructions and reminders at 710. For example, the user may be informed how to use the medication. Information may include links and / or information from DailyMed at 706 and / or information from MedlinePlus at 708.

[0269] 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. Warnings regarding potential drug interactions may be received and determined by the National Library of Medicine, FDA, regulatory agencies, and the like.

[0270] Figure 8 Depicted are exemplary methods for determining the amount of active ingredient included in a pharmaceutical. Figure 8 As shown, method 800 may include one or more of 808, 810, 814, and / or 816 to determine the amount of active ingredient that may be included in the medication. Figure 8 As shown, the method 800 may be performed by an apparatus 801, which may be any apparatus disclosed herein, such as Figure 6 In addition, the device 601 may include Figure 1 Component 120 is shown.

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

[0272] Reference again Figure 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 the NDC. The first medication identifier may be validated against a database and may be assigned as a source NDC and / or source medication identifier. For example, the first medication identifier may be identified and / or validated by transmitting a request at 809 using RxNorm 802. At 811, RxNorm 802 may respond by transmitting a response to device 801. In one example, the response may indicate that the identification is validated. In one example, the response may indicate that the identification cannot be validated.

[0273] At 808, a request may be transmitted to one or more databases using an API such as RxNorm 802. The request may indicate a request for information associated with a first drug identifier (e.g., 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, device 801 may receive the requested information, which may include a second drug identifier such as NDC, RxCUI, etc. The requested information may include a mapping of the first drug identifier to the second drug identifier.

[0274] 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 .

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

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

[0277] At 814, the active ingredients associated with the medication may be determined. The medication may be composed 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 has an overview of how much active ingredient (e.g., each active ingredient) is included in the medication.

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

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

[0280] Figure 9A An exemplary user interface listing one or more identified medications is depicted. Figure 9AThe data shown can be determined, calculated, and / or displayed by the device. The data can include a subject identifier at 902, a date at 904, an NDC at 906, an amount at 908, a unit at 910, a display name at 912, one or more ingredients at 914, a dose at 916, a dosage unit at 918, combinations thereof, and the like. For example, the device can determine one or more active ingredients of a medication, concentrations associated with the one or more active ingredients, amounts of the one or more active ingredients, combinations thereof, and the like.

[0281] In one example, the user interface can display an overview. The overview can be called a dose overview, a medication overview, an ingredient overview, and / or a dose summary by active ingredient.

[0282] like Figure 9A As shown, a display name of the medication may be determined at 912. 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, and the like.

[0283] like Figure 9A As shown, at 914, one or more active ingredients of the medication may be determined. At 916, the dosage and / or strength of the one or more active ingredients may be determined. At 918, the units of the one or more active ingredients may be determined. For example, it may be determined that an extra-strength headache relief medication contains 130 mg of caffeine, 500 mg of aspirin, and 500 mg of acetaminophen.

[0284] At 904, the date on which the medication may have been consumed may be recorded. At 906, the NDC of the identified medication may be recorded. At 908, a quantity of medication and a unit of medication may be provided. For example, it may be determined that a super strength headache relief medication may be a tablet and that two tablets may have been consumed.

[0285] Figure 9B An exemplary user interface for aggregating one or more active ingredients associated with one or more medications is depicted. Figure 9B The data shown can be determined, calculated, and / or displayed by the device. The data can include a subject identifier at 920, a date at 922, one or more ingredients at 924, a count at 926, an average at 928, a sum at 930, a minimum at 932, a maximum at 934, combinations thereof, and the like. The summary can be referred to as a dose summary, a medication summary, an ingredient summary, and / or a dose summary by active ingredient.

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

[0287] like Figure 9B As shown, at 922, active ingredients may be listed according to a time frame (such as a date). Information about the active ingredients may be displayed. At 926, a count of how many times the active ingredient may have been consumed in a day may be provided. At 928, an average value of the amount of the active ingredient may be provided. This may indicate to the user the average amount of the active ingredient they consumed per count. At 930, a total of the amounts of the active ingredients may be provided to the user. At 932, the user may be provided with the minimum amount of active ingredient from the medication consumed by the user. At 934, the user may be provided with the maximum amount of active ingredient from the medication consumed by the user.

[0288] Embodiments herein may provide for aggregation and analysis of pharmaceutical data. Figure 9C An exemplary user interface for aggregating one or more active ingredients associated with one or more medications is depicted. For example, Figure 9C The data shown may include a sample of medication diary data and may include a subject identifier at 936, a date at 938, an NDC at 940, an RxCUI at 942, an amount at 944, a unit at 946, a 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, and the like.

[0289] In one example, NDC can be mapped to RxCUI, which provides detailed information about ingredients, dosage (such as known strength), and dosage units. Data can be mapped to various drug categories, such as the Anatomical Therapeutic Chemical (ATC) classification, to address analysis requests. Aggregation and analysis at the patient level or study level can be performed by drug, ingredient, or category using RxNorm and links to other drug dictionaries. Drugs entered as free text can be mapped using an algorithm that can be incorporated as an endpoint of the RxNorm API.

[0290] Figure 9D An exemplary user interface providing a summary of daily dosages of one or more active ingredients associated with one or more medications is depicted. Figure 9DThe data shown may include a subject identifier at 956, a date at 958, an NDC at 960, an RxCUI at 962, an amount at 964, a unit at 966, a drug name at 968, one or more ingredients at 970, one or more doses at 972, one or more dose units at 974, combinations thereof, and the like.

[0291] like Figure 9D As shown, embodiments herein can determine how much medication and / or active ingredient a user may have consumed over a period of time. For example, an overview can be determined for hourly dosages (e.g., 8 hours, 12 hours, 23 hours, 48 ​​hours, etc.), daily dosages, weekly dosages, monthly dosages, combinations thereof, and the like. Dosages can be specific to active ingredients. For example, a daily dosage of acetaminophen can be determined.

[0292] It is possible to determine how many active ingredients a user may have consumed. It is possible to determine how much of those active ingredients a user may have consumed. For example, if a user consumes cold medicine with three active ingredients and headache medicine with two active ingredients, an overview of the five active ingredients may be provided.

[0293] Figure 10 An exemplary user interface for listing one or more medications associated with a patient is depicted. Figure 10 As shown, interface 1000 may be an interface that lists medications that a patient may be taking or may have taken. For example, interface 1000 may display medications that a user may have taken in the past. As another example, at 1002, interface 1000 may display medications that a user is currently taking or may have been prescribed. At 1006, the user may add medications to the medication list.

[0294] In one example, at 1004, the list of one or more medications may include photos of the one or more medications, such as at 1008 and 1010. For example, a user may take a photo of the 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 medication label, 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 a photo 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 that the user has associated with the medication. As another example, the photo may be a photo of the location where the user stores the medication.

[0295] Figure 11An exemplary user interface for capturing medications and / or medication usage is depicted. At 1100, a user may initiate the start of a process for capturing medications and / or medication usage. As shown in 1100, the user may have the ability to record their medications (e.g., a medication diary), identify medications, provide and / or view patient information, provide and / or view information about medical conditions, provide and / or view information about allergies, combinations thereof, and the like.

[0296] At 1102, one or more medications that have been identified may be presented to the user. The identified medications (such as the list shown at 1108) may include photos that the user may have captured (such as at 1110). Photos may help the user remember the medications. For example, a photo of the medication packaging or medication label may be easier for the user to remember than the medication name. As shown at 1112, the user may add a new medication.

[0297] 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 the 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 may use information from the photo and / or video to identify the medication, as described herein.

[0298] At 1106, an interface may be presented to the user to indicate what medications the user may have consumed. The user interface may enable the user to know when they took the medication. 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 indicate 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, and the like.

[0299] Figure 12 An exemplary user interface for capturing medications and / or medication usage for a medication list is depicted. 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 watch list module at 1210, and a frequently asked questions module at 1212.

[0300] The interface 1200 may include a medication list module 1202. The medication list module 1202 may be related to Figure 3 Describes the interface of the medication list 317. Again refer to Figure 12The medication list module 1202 can provide a repository for one or more medications that a user is currently taking or has taken in the past. It can provide a view of the user's medication history, which can help healthcare providers understand the user's health status and plan future treatments.

[0301] 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 the user with a visually intuitive method to add medications to their list and may be helpful when dealing with multiple medications with complex names.

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

[0303] The interface 1200 may include a medication diary module 1204. The medication diary module 1204 may be an interface to the medication diary 320, such as Figure 3 As described. Again refer to Figure 12 The medication diary module 1204 can allow users to record their medication use over a period of time. For example, users can record when they took the medication, the dosage, and any side effects they experienced. This can provide information about the effectiveness of the medication and its impact on the user's health.

[0304] The interface 1200 may include a dose / exposure module 1206. The dose / exposure module 1206 may be an interface to the dose summary 322, such as Figure 3 As described. Again refer to Figure 12 The dosage / exposure module 1206 may allow the user to monitor the amount of medication to which the user is exposed. It may calculate the dosage based on information provided by the user or 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.

[0305] The interface 1200 may include an interaction module 1208. The interaction module 1208 may be an interface for interaction 322, such as Figure 3 As described. Again refer to Figure 12 The interaction module 1208 can allow the user to analyze potential interactions between medications the user is taking. It can flag any possible negative interactions or synergistic effects. This can help prevent harmful drug interactions and optimize the benefits of the drug treatment regimen.

[0306] The interface 1200 may include a watch list module 1210. The watch list module 1210 may be an interface for the watch list 323, such as Figure 3 As described. Again refer to Figure 12 The watch list module 1210 can provide the user with and / or monitor a list of medications that the user should avoid. These may be medications that a healthcare provider has identified as potentially harmful to the user due to interactions with other medications the user may be taking. This module can help protect the user from adverse drug interactions.

[0307] The interface 1200 may include a frequently asked questions (FAQ) module 1212. The FAQ module 1212 may include questions about Figure 3 The information is retrieved from the medication information 318 shown. Figure 12 The FAQ module 1212 can provide users with answers to questions about their medications. This can include information about side effects, dosage, timing, and potential interactions. The FAQ module 121 can provide users with a reference to help them understand and manage their medications more effectively.

[0308] Figure 13 An exemplary user interface for capturing medications and / or medication usage for drug interactions is depicted. As described herein, interface 1200 may include a watch list module 1210. In one example, data may be provided at 1302 that may include various important information about one or more medications. This may include the name of the medication at 1304, which may allow the user to identify the medication. One or more ingredients may be listed at 1306, which may inform the user of 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. A link to drug information may be provided at 1310. 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.

[0309] Figure 14 Depicts exemplary drug information. At 1402, product label information may be provided to the user. The product label information may be drug information as 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, such as Figure 13 shown.

[0310] Reference again Figure 14At 1404, drug information may be provided. The product label information may be the drug information described herein. The drug information may be from a database such as MedlinePlus. The drug information may be the drug information provided by the link at 1310, such as the information about Figure 13 shown.

[0311] Figure 15 An exemplary user interface for capturing medications and / or medication use for a medication diary is depicted. For example, Figure 15 Illustrated is an exemplary user interface for recording medications and their use in the medication diary module 1204. User-provided data may be incorporated at 1504, which may include details such as the date and time of medication, the name of the medication, the amount taken, the unit of measurement, the active ingredient(s), the dosage, and the dosage unit.

[0312] For example, the user may enter the name of the medication at 1506, enter the amount at 1508, select the relevant unit 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.

[0313] A dosage warning may be provided at 1502, which 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 this situation may help prevent overdose or adverse reactions due to excessive medication intake.

[0314] Figure 16 An exemplary user interface for capturing medications and / or medication usage for a medication diary is depicted. At 1602, interface 1200 may alert a user that they have exceeded a threshold for a particular medication. For example, a user may have exceeded the maximum recommended amount of acetaminophen within a given time period.

[0315] In one example, the interface can generate warnings and instructions to the user. The warning can include instructions such as "Warning: You have exceeded the recommended daily limit of acetaminophen. Excessive intake can cause liver damage." The system can provide instructions such as "Please discontinue use and consult your healthcare provider."

[0316] In addition to these user-facing alerts, the system can also notify healthcare professionals associated with the user. This can be done automatically or upon user confirmation. The healthcare provider can take appropriate action, such as contacting the patient for a consultation, adjusting medication regimen, and / or arranging immediate medical intervention.

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

[0318] Interface 1200 may provide recommendations for future actions, such as suggestions on how to avoid similar incidents in the future. For example, the user may be advised to: double-check the dosage before taking medication; avoid taking multiple products containing the same active ingredient; consult a healthcare provider before starting a new medication; or a combination thereof.

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

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

[0321] At 1708, data detailing exposure to the drug over a period of time may be provided to the user. The data may include details such as date, time, ingredients, quantity, units, dosage, total exposure over a period of time, combinations thereof, and the like.

[0322] At 1710, the interface 1200 may present a summary of the daily dosage of the pharmaceutical ingredients. The data may include date, one or more ingredients, number of intakes, units, average, minimum, maximum, total, combinations thereof, and the like.

[0323] Figure 18 An exemplary user interface for capturing medications and / or medication usage for a medication watch list is depicted. In one example, interface 1200 displays data associated with a watch list module 1210, which may include displaying data at 1800. The data at 1800 may include the name of the medication, one or more active ingredients, and medication information. The medication information may also include a product label, a link to a product label, medication information, a link to medication information, combinations thereof, and the like. The data at 1800 may provide a user with a view of their medication watch list, thereby providing information about one or more medications that a healthcare provider wants the user to monitor.

[0324] Figure 19 An exemplary user interface for capturing medications and / or drug usage for drug interactions is depicted. As part of interface 1200, interaction module 1208 can analyze a list of medications a user is taking and identify potential interactions between them. This can include both positive and negative interactions and can involve evaluating the effects of different combinations of medications on the user's health.

[0325] The interface 1200 may display data at 1900 , which may include the source of the information, the names of the first and second medications, one or more interacting ingredients, a description of the interaction, combinations thereof, and the like.

[0326] The data can be organized based on priority. For example, at 1902, interactions that are considered high priority can be listed before those interactions that are classified as lower priority. This prioritization can help users and healthcare providers quickly identify and resolve interactions.

[0327] The data presented at 1900 may indicate an interaction between a first drug and a second drug. Interacting components may be responsible for such interactions and may be identified at 1904. Information regarding these interactions may be provided at 1904, which may include the nature of the interaction, potential impact on the patient, recommended actions for the user or their healthcare provider, combinations thereof, and the like.

[0328] Figure 20 An exemplary user interface for capturing medications and / or medication usage for a medication watch list is depicted. Interface 1200 can provide data generated by a watch list module 1210. At 2002, the data can include ingredients and / or drug categories on the watch list.

[0329] Drug class refers to a group of drugs that work in a similar manner or have similar chemical structures. Grouping drugs into categories allows for better monitoring of drugs that may have interactions. Classification systems (such as anatomical therapeutic chemical (ATC) classification systems) can be used to provide drug classes. The ATC classification system can be used to classify the active ingredients of drugs based on the organs or systems on which the drugs act, their therapeutic and pharmacological properties and / or their chemical characteristics. The ATC classification system can be used as a tool for drug utilization research, and can help monitor and analyze drug use and trends. In one example, a classification system (such as the ATC classification system) can organize drugs (e.g., drugs) into different hierarchical levels or categories, starting from anatomical groups, and then broken down into therapeutic, pharmacological and chemical subdivisions. This hierarchical structure can allow effective classification, and can promote comparison of drug use, research and / or monitoring.

[0330] At 2004, drug categories or types may be listed, which may provide the user with an understanding of the category their drug falls into. At 2006, information such as drug information and / or links to drug information may be provided for one or more drug categories. This may assist the user in understanding the nature of the drug they are being advised to avoid.

[0331] At 2008, the healthcare provider may provide a list of medications that the user has been instructed to remove due to potential adverse reactions or interactions with other medications the user is taking.

[0332] At 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 adverse reactions to a certain class of medications, medications from that class may be included in the list.

[0333] The above detailed description has been described using block diagrams, flow charts, examples and / or implementation schemes to illustrate various forms of devices and / or processes. As long as such block diagrams, flow charts, examples and / or implementation schemes include 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 charts and / or examples can be implemented individually and / or collectively by a variety of hardware, software, firmware or any combination thereof. Those skilled in the art will recognize that some aspects of the forms disclosed herein can be implemented equivalently in whole or in part in an integrated circuit 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 as any combination thereof. Those skilled in the art will recognize 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 the illustrative forms of the subject matter described herein are applicable regardless of the specific type of signal-bearing medium used for distribution.

[0334] Instructions for programming logic to perform various disclosed aspects may be stored in a memory in the system, such as dynamic random access memory (DRAM), cache, flash memory, or other memory. Instructions may be distributed via a network or by other computer-readable media. For example, instructions may be transmitted via messages and / or signals. Machine-readable media may include any mechanism for storing or sending information in a machine (e.g., computer) readable form, but is not limited to floppy disks, optical disks, optical disks, read-only memories (CD-ROMs) and magneto-optical disks, read-only memories (ROMs), random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memories, or tangible, computer-readable storage devices used when sending information over a network (e.g., the Internet) via electrical signals, optical signals, acoustic signals, or other forms of propagation signals (e.g., carrier waves, infrared signals, digital signals, etc.). Non-transitory computer-readable media may include any type of tangible computer-readable medium suitable for storing or sending electronic instructions or information in a form readable by a device (e.g., a computer).

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

[0336] Additionally, this application may refer to "receiving" various pieces of information. Like "accessing," receiving is intended to be a broad term. Receiving the information may include, for example, one or more of: accessing the information or retrieving the information (e.g., from a memory device). Furthermore, "receiving" generally involves, in one way or another, an operation such as storing the information, processing the information, transmitting the information, moving the information, copying the information, erasing the information, calculating the information, determining the information, predicting the information, or estimating the information.

[0337] It should be understood that, for example, in the case of "A / B," "A and / or B," and "at least one of A and B," the use of any of " / ," "and / or," and "at least one of..." is intended to encompass the selection of only the first-listed option (A), or only the second-listed option (B), or both options (A and B). As another example, in the case of "A, B, and / or C" and "at least one of A, B, and C," such phraseology is intended to encompass the selection of only the first-listed option (A), or only the second-listed option (B), or only the third-listed option (C), or only the first-listed option and the second-listed option (A and B), or only the first-listed option and the third-listed option (A and C), or only the second-listed option and the third-listed option (B and C), or all three options (A, B, and C). It will be clear to one of ordinary skill in this and related arts that this can be extended to as many items as there are listed.

[0338] We have described a number of examples. Features of these examples may be provided individually or in any combination across various claim categories and types. Furthermore, embodiments may include one or more of the following features, devices, or aspects, individually or in any combination across various claim categories and types.

Claims

1. A device for determining medication used by a patient, the device comprising: A processor configured to: Determine label information for medications; using the label information to determine a source National Drug Code (NDC) associated with the drug; transmitting a first message to a first server, wherein the first message indicates a request for verification of the source NDC; receiving a second message from the first server, wherein the second message indicates that the source NDC is valid, indicates a product NDC, and indicates a normalized identifier; Using the product NDC to determine the brand name associated with the drug; using the normalized identifier to identify one or more active ingredients associated with the brand name; determining a drug display name using the brand name and the one or more active ingredients; determining active ingredient information for the one or more active ingredients; as well as The drug display name and the active ingredient information are displayed to the user. 2 . The apparatus of claim 1 , wherein the normalized identifier is an RxNorm Conceptually Unique Identifier (RxCUI).

3. The apparatus of claim 1, wherein the product NDC comprises a labeler code and a product code.

4. The apparatus of claim 1, wherein the source NDC is a packaging NDC, and wherein the packaging NDC comprises a labeler code, a product code, and a packaging code.

5. The apparatus of claim 1, wherein the source NDC comprises a labeler code, a product code, and a packaging code, and wherein the product NDC comprises the labeler code and the product code.

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

7. The apparatus of claim 1 , wherein the processor is configured to determine the brand name using the product NDC by: transmitting a brand name request message to a second server, wherein the brand name request message indicates a request for a brand name associated with the product NDC; and A brand name response message is received from the second server, wherein the brand name response message indicates the brand name.

8. The apparatus of claim 1 , wherein the processor is configured to determine the one or more active ingredients associated with the brand name by: transmitting an ingredient request message to the first server, wherein the ingredient request message indicates a request for one or more active ingredients associated with the normalized identifier; receiving an ingredient response message from the first server, wherein the ingredient response message indicates the normalized identifier and indicates one or more active ingredients; and The one or more active ingredients are stored in a database such that the one or more active ingredients are associated with the brand name.

9. A method for determining medication used by a patient, performed by a device, the method comprising: Determine label information for medications; using the label information to determine a source National Drug Code (NDC) associated with the drug; transmitting a first message to a first server, wherein the first message indicates a request for verification of the source NDC; receiving a second message from the first server, wherein the second message indicates that the source NDC is valid, indicates a product NDC, and indicates a normalized identifier; Using the product NDC to determine the brand name associated with the drug; using the normalized identifier to identify one or more active ingredients associated with the brand name; determining a drug display name using the brand name and the one or more active ingredients; determining active ingredient information for the one or more active ingredients; as well as The drug display name and the active ingredient information are displayed to the user.

10. The method of claim 9, wherein the normalized identifier is an RxNorm Conceptually Unique Identifier (RxCUI). The method of claim 9 , wherein the product NDC comprises a labeler code and a product code.

12. The method of claim 9, wherein the source NDC is a packaging NDC, and wherein the packaging NDC includes a labeler code, a product code, and a packaging code.

13. The method of claim 9, wherein the source NDC comprises a labeler code, a product code, and a packaging code, and wherein the product NDC comprises the labeler code and the product code.

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

15. A non-transitory computer-readable medium storing processor-executable instructions, the processor-executable instructions comprising: Identify images or videos of drug labels; as well as determining a source National Drug Code (NDC) from the image, wherein the source NDC is associated with the medication label; transmitting a first message to a first server, wherein the first message indicates a request for verification of the source NDC; receiving a second message from the first server, wherein the second message indicates that the source NDC is valid, indicates a product NDC, and indicates a normalized identifier; Using the product NDC to determine the brand name associated with the drug; using the normalized identifier to identify one or more active ingredients associated with the brand name; determining a drug display name using the brand name and the one or more active ingredients; determining active ingredient information for the one or more active ingredients; as well as The drug display name and the active ingredient information are displayed to the user.

16. The non-transitory computer-readable medium of claim 15, wherein the processor-executable instructions for determining the drug display name using the brand name and the one or more active ingredients comprise: determining a prescribable synonym name for at least one of the one or more active ingredients; as well as The drug display name is generated by combining the brand name with the prescribeable synonym name.

17. The non-transitory computer-readable medium of claim 15, wherein the processor-executable instructions for determining the active ingredient information for the one or more active ingredients comprise: transmitting an active ingredient information request to a third server, wherein the active ingredient information request indicates at least one of a structured product label identification (SPL ID) or the normalized identifier; as well as An active ingredient information response is received, wherein the active ingredient information response indicates an active ingredient and indicates at least one of a warning, instructions for use regarding the active ingredient, or a drug interaction warning.

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

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

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

Images