US2022189606A1PendingUtilityA1

Ingestible event marker data framework

Assignee: OTSUKA PHARMA CO LTDPriority: Jul 8, 2008Filed: Nov 29, 2021Published: Jun 16, 2022
Est. expiryJul 8, 2028(~1.9 yrs left)· nominal 20-yr term from priority
G06Q 10/40G16H 40/67G16H 20/60A61B 5/0022A61B 5/021G16H 20/30A61B 5/07G16H 20/10G16H 50/20G16Y 40/10G16Y 20/40G16H 70/40G16H 20/00G16H 10/65A61B 5/4833A61B 5/117G16H 80/00
74
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

The ingestible event marker data framework provides a uniform, comprehensive framework to enable various functions and utilities related to ingestible event marker data (IEM data). The functions and utilities include data and/or information having an aspect of data derived from, collected by, aggregated by, or otherwise associated with, an ingestion event.

Claims

exact text as granted — not AI-modified
1 .- 26 . (canceled) 
     
     
         27 . A system for generating a notification regarding medication usage, the system comprising:
 a processor programmed to:
 receive data associated with a physiological pattern of an individual, wherein the data associated with the physiological pattern is encoded in an ingestible event marker (IEM) device and is derived from a signal generated by the IEM device after the IEM device has been ingested by the individual; 
 receive one or more measured data samples of a physiologic parameter of the individual; 
 compare the one or more measured data samples of the physiologic parameter to the data associated with the physiologic pattern derived from the IEM device; and 
 generate a first electronic notification indicating whether the individual ingested the IEM device based on the comparison between the one or more measured data samples of the physiologic parameter and the data associated with the physiologic pattern. 
   
     
     
         28 . The system of  claim 27 , wherein the physiologic pattern of the individual includes
 a heart rate variability, a breathing rate, or a heart rate.   
     
     
         29 . The system of  claim 27 , wherein the IEM device is configured to be ingested with the medication. 
     
     
         30 . The system of  claim 27 , wherein the processor is further programmed to:
 receive timing data from the signal generated by the IEM device, the timing data indicative of when the IEM device was ingested;   compare the timing data to a dosing schedule associated with the individual; and   generate a second electronic notification indicating whether the individual ingested the IEM device in a timely manner.   
     
     
         31 . The system of  claim 27 , wherein the processor is further programmed to:
 compute a total number of IEM devices ingested by the individual over a time period; and   compare the total number of ingested IEM devices with prescription information associated with the individual.   
     
     
         32 . The system of  claim 31 , wherein the processor is further configured to generate a second electronic notification indicating whether a prescription refill is necessary based on the comparison between the total number of ingested IEM devices with prescription information. 
     
     
         33 . The system of  claim 31 , wherein the processor is further configured to generate a second electronic notification indicating whether the individual is overdosing based on the comparison between the total number of ingested IEM devices with prescription information. 
     
     
         34 . The system of  claim 27 , wherein the processor is further programmed to receive data generated by the IEM device identifying an ingested substance associated with the IEM device. 
     
     
         35 . The system of  claim 31 , wherein the processor is further configured to generate a second electronic notification to automatically refill a prescription based on the comparison between the total number of ingested IEM devices with prescription information. 
     
     
         36 . The system of  claim 27 , wherein the processor is further configured to cause display of medical information including whether the individual ingested the IEM device. 
     
     
         37 . The system of  claim 36 , wherein the medical further comprises a recommendation for how to improve the individual's health. 
     
     
         38 . The system of  claim 27 , wherein the processor is further configured to generate a second notification providing a reminder for the individual to ingest a subsequent IEM device at a prescribed time. 
     
     
         39 . The system of  claim 27 , wherein the processor is further configured to:
 analyze the one or more measured data samples of a physiologic parameter of the individual; and   generate a second notification indicating an efficacy of the ingested IEM device, based on the analysis of the one or more measured data samples and the indication of whether the individual ingested the IEM device.   
     
     
         40 . The system of  claim 39 , wherein the processor is further configured to initiate a scheduled appointment to a physician, based on the analysis of the one or more measured data samples and the indication of whether the individual ingested the IEM device. 
     
     
         41 . The system of  claim 27 , wherein the processor is further configured to generate a second notification providing an inventive for the individual to ingest a subsequent IEM device at a prescribed time. 
     
     
         42 . The system of  claim 27 , wherein the processor is further configured to generate a second notification to a regulatory agency providing information about a controlled substance associated with the IEM device. 
     
     
         43 . The system of  claim 27 , wherein the processor is further configured to generate a second notification to a social networking system providing notification of the individual's activity related to ingesting the IEM device.

Join the waitlist — get patent alerts

Track US2022189606A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.