A system and method for regulating alcohol consumption includes an id tag having a unique id for a person. When a person desires to purchase an alcoholic beverage, the id tag is scanned or read by a reader. Information relating to prior purchases of alcoholic beverages are retrieved. An anticipated blood alcohol level is calculated based upon the current order and previous orders of alcoholic beverages. If the blood alcohol level of the user is anticipated to exceed a threshold, then sales of alcohol beverage are declined.
|
8. A method for regulating alcohol consumption by a user comprising:
providing the user with a unique id;
storing a quantity of an alcoholic beverage ordered by the user;
calculating an anticipated blood alcohol level for the user based upon the quantity of the alcoholic beverage ordered by the user and upon personal information regarding the user; and
refusing a sale of the alcoholic beverage if the anticipated blood alcohol level exceeds a threshold.
1. A system for regulating alcohol consumption of a user comprising:
a personal id tag having a unique id associated with the user;
a reader for reading the unique id;
a first computer for recording an alcoholic beverage order of the user identified by the unique id;
blood alcohol calculation means for approximating a blood alcohol level of the user based upon the alcoholic beverage order;
an alert for indicating that the user may exceed a threshold if the user consumes an alcoholic beverage;
a first database for storing the alcohol order by the user, the first database including personal information regarding the user; and
a second computer for receiving from the first computer information regarding the alcoholic beverage order.
17. A method of regulating the alcohol consumption by a user comprising:
associating a plurality of unique IDs with a plurality of users;
providing the user with an id tag having a first unique id;
before fulfilling an order for an alcoholic beverage, reading the first unique id;
attempting to match the first unique id with one of the plurality of unique IDs;
if the first unique id matches one of the plurality of unique IDs, then retrieving information about the user associated with that unique id;
displaying the information;
verifying that the information for the user associated with the unique id is that of the person presenting the id tag;
if the person presenting the id tag is the user associated with the unique id, retrieving information regarding prior alcoholic beverage orders associated with the unique id; and
calculating an anticipated blood alcohol level for the user before the order for the alcoholic beverage is fulfilled.
5. The system of
6. The system of
7. The system of
9. The method of
initiating an alert if the anticipated blood alcohol level exceed the threshold.
10. The method of
storing a time indicative of when the quantity of alcoholic beverage was ordered.
11. The method of
calculating the anticipated blood alcohol level based upon previous orders for alcoholic beverages by the user.
12. The method of
calculating the anticipated blood alcohol level based upon the time.
13. The method of
if the anticipated blood alcohol level does not exceed the threshold, completing the sale of the alcoholic beverage.
14. The method of
storing a quantity and a time of the sale for the alcoholic beverage.
15. The method of
storing a personal information regarding the user in a database.
16. The method of
18. The method of
if the person is identical to the user associated with the unique id, then fulfilling the order for the alcoholic beverage.
19. The method of
if the anticipated blood alcohol level exceeds a threshold, then refusing to fulfill the order for the alcoholic beverage.
20. The method of
if the anticipated blood alcohol level does not exceed the threshold, then fulfilling the order for the alcoholic beverage.
21. The method of
storing in a database information regarding the order for the alcoholic beverage.
22. The method of
|
Many people consume alcoholic beverages. However, the excessive consumption of alcoholic beverages can be a significant problem. An inebriated person may sometimes act inappropriately and become a nuisance. In some situations, such as the operation of a motor vehicle, the inebriated person may create a serious danger to himself and other persons.
Current attempts to limit the consumption of alcohol generally relate to penalties after the person has become inebriated. For example, a person can be incarcerated or fined for public drunkenness or operating a motor vehicle under the influence of alcohol. However, these punishments are imposed after the person has consumed too much alcohol.
Attempts to stop a person from becoming inebriated are generally ineffective. Usually, a server or bartender is expected to refuse providing an individual with an alcoholic beverage if that individual is inebriated. However, the ability of the server to ascertain the inebriation of the individual is limited by several factors. The server may not be have experience in detecting whether a person is inebriated. The server also may have only a limited amount of time to interact with the person. Finally, an inebriated person may be able to appear normal even if he has consumed an excessive amount of alcoholic beverages.
The failure to limit the consumption of alcoholic beverages has a detrimental affect not only upon the person consuming the beverage, but also on the establishment serving the liquor. Inebriated persons tend to create adverse situations at the establishment, thereby resulting in other customers leaving the establishment, and thereby reducing the sales of alcoholic beverages by the establishment. In severe cases, the establishment that provided alcoholic beverages to a person may itself be held liable for injuries resulting from that person's inebriation.
Thus, an improved method to limit the alcohol consumption by an individual is highly desirable.
A system for regulating the alcohol consumption of a user includes a personal ID tag. The personal ID tag includes a personal ID. The personal ID tag could be a swipe card, a smart card, a drivers license, a wristband, or any item that could contain an ID.
In order to obtain a tag, a person could be required to provide personal information such as height, weight and gender. The person could also be required to submit to a controlled blood alcohol test. In this situation, the person consumes a specific alcoholic beverage at specified time intervals. The person's blood alcohol is periodically checked and recorded. Thus, the reaction of the person to the consumption of alcohol is recorded. The results of the test could then be used to make more accurate determinations of blood alcohol levels for the person.
When a person orders an alcoholic beverage, the ID on the personal ID tag is read by a reader. Information regarding the owner of the ID is retrieved and displayed in order to verify that the person presenting the ID tag is in fact the person associated with the ID. If so, then information regarding prior alcoholic beverage orders by the owner is retrieved.
Based upon the information regarding the prior alcoholic beverage orders as well as the current order, a computer calculates the anticipated blood alcohol level. If the anticipated blood alcohol level exceeds a threshold, then the order is not fulfilled. If the anticipated blood alcohol level does not exceed the threshold, then the order is fulfilled, and information regarding the newly fulfilled order is stored in a database for later reference if the ID owner again places an order for alcoholic beverages.
The information regarding alcoholic beverage sales could be stored by the reader, or it could be stored in a computer located near the reader. Additionally, a central computer could be provided in order to upload information regarding alcoholic beverage sales so that all orders by the owner can be tracked. For example, if the owner were at an amusement park where a single proprietor was responsible for all the places where alcoholic beverages are sold, the proprietor could track all alcohol orders by a person, and thus limit the supply of alcohol to that person if the person is in danger of consuming too much alcohol.
By limiting the ability of a person to consume excessive amounts of alcohol, the person's sobriety can be assured. The problems associated with excessive alcohol consumption are thereby ameliorated.
These and other objects, advantages and features of the invention will be more readily understood and appreciated by reference to the detailed description of the drawings.
A person presents the personal ID tag 10 whenever he desires to purchase an alcoholic beverage. When the order for an alcoholic beverage is presented, the tag is read by way of reader 12. Reader 12 is shown as a PDA (personal digital assistant) with swipe card reader 13. However, reader 12 could be any one of numerous devices for reading tags, such as a laser scanner. Alternatively, the information from personal ID tag 10 could be manually entered into reader 12. Reader 12 is provided with alert 15. When activated, alert 15 signals that the order should not be completed.
Reader 12 is connected to establishment computer 14. Establishment computer 14 is connected by way of network 16 to central computer 18. Establishment computer 14 has establishment database 20. Establishment database 20 contains a plurality of unique IDs associated with specific customers. Establishment database 20 could also contain a picture of the individual associated with the unique identification number or other information allowing the person serving the alcoholic beverage to verify the identity of the person ordering the beverage. Similarly, central computer 18 could have central computer database 22.
Central computer 18 could be for a particular locale or group of establishments. For example, if the establishments were part of an amusement park or a sports complex, all places which serve alcoholic beverages within the amusement park or sports complex would be connected to central computer 18. Alternatively, the central computer 18 could also be located with a local or state government.
Central computer database 22 could have information similar to that of establishment database 20, or it could have more detailed information about the user. For example, central computer database 22 could contain information about previous events involving the user which might indicate that the user should not be provided with alcoholic beverages.
In order to obtain personal ID tag 10, an individual may be required to engage in a test. The individual would be provided a specific alcoholic beverage at regular intervals over a period of time. A blood alcohol test, such as a breathalyzer test, would be administered to the person. The blood alcohol level shown for each test would be recorded and stored either on personal ID tag 10, establishment computer 14, or central computer 18. The height, weight and gender of the person taking the test would also be stored.
For example, a person could be asked to consume two beers each hour. At the end of each hour, a breathalyzer test would be performed. At the end of four hours, the results of each test would be recorded. The person would thus be provided with specific information regarding the effect of alcohol consumption on him. Additionally, that information would be available for use at a later time to assist in determining whether additional sales of an alcoholic beverage is prudent.
Memory device 50 could have three fields. Consumption rate field 52 contains the rate of alcoholic consumption for a user. For example, if a user can consume two ounces of an alcoholic beverage per hour, then the rate recorded would be “two.” Obviously, other schemes could be used to identify the acceptable rate of consumption. Consumption rate field 52 is written only once. Alcohol beverages consumed field 54 is a field containing the amount of alcoholic beverages consumed. With each use of the card, the alcohol beverages consumed field 54 is changed to indicate the amount consumed. Depending upon the memory available on memory device 50, the alcoholic beverages consumed field could include a running total of beverages consumed, or it could contain a list of each beverage consumed. Finally, consumption time field 56 contains the time of the consumption of the alcoholic beverages. Consumption time field 56 could include a time entry for every alcoholic beverage consumed or it could include only the time of the last alcoholic beverage consumed. ID field 58 includes a unique ID for a user.
The reading of ID tag 10 supplies a unique ID to establishment computer 14. Step 100. Establishment computer 14 determines if the unique identification number currently exists. Step 102. If so, establishment computer 14 retrieves from establishment database 20 information associated with the unique ID. Step 104.
At the same time, personal information regarding the user is displayed. Step 104. The information regarding the owner of the card is displayed. If the database contains a picture of the person using the card, then the picture could be retrieved and displayed. Step 106. If the information displayed does not match the person presenting the ID tag, the ID tag is confiscated, (step 108) and the request to purchase more alcoholic beverages is denied. Step 110
If, on the other hand, the information regarding the owner of the ID tag and the user of the ID tag does match, then various actions occur to determine whether alcoholic beverages should be provided to the user. In one embodiment, the time and quantity of previous alcoholic beverages orders are retrieved. Step 112. Using this information as well as personal information about the user, such as the user's weight and gender and the results of any tests regarding alcohol consumption on the specific user, the establishment computer can calculate the anticipated blood alcohol level of the user if he is provided the ordered alcoholic beverage. Step 114. For example, if the calculated blood alcohol content of the user, based upon the time and quantity of previous orders of alcohol, is 0.075%, then an order for an alcoholic beverage such as a 12 ounce serving of beer would raise the blood alcohol level of the user by an additional 0.02% to 0.095%.
Based upon this calculation of blood alcohol level, establishment computer 14 would then determine whether the blood alcohol level is above a threshold. Step 116. The predetermined threshold could be any amount. For example, if the user is expected to operate a motor vehicle, then the threshold could be at 0.08%, the level set by many governmental units as being an unacceptable blood alcohol level for operating a motor vehicle. On the other hand, if the user was not expected to operate a motor vehicle, then the blood alcohol level could be higher. Conversely, if the user was a ‘designated driver’, the blood alcohol level could be much less than 0.08%.
If the blood alcohol level would exceed the threshold, then an alert would be initiated. Step 109. The user's request for the alcoholic beverage would be denied. Step 110. If the anticipated blood alcohol level would not exceed the threshold, then the user's request would be fulfilled. Step 118. The amount and type of alcoholic beverage as well as the time the order was fulfilled would be stored in establishment computer 14. Step 120. The information regarding the purchase of the alcoholic beverage would be uploaded to central computer 18. Step 121. The process would then terminate. Step 122.
Alternatively, in place of steps 112, 114, and 116, establishment computer 14 could simply calculate the number of drinks previously served to the user. Once the number of drinks served to a user reaches a threshold, no further drinks would be provided to the user.
Returning to Step 102, if no record exists for the unique ID, then establishment computer 14 determines if the unique ID exists at central computer 18. Step 124. If so, then the information is downloaded from central computer 18 to establishment computer 14. Step 126. If not, a new record is created. Step 128. Information about a user is then collected. Step 130. Such information could include the height and weight of the user and a picture of the user. Additionally, a breathalyzer test could be administered to the user. Step 132. The results of the breathalyzer test would then be stored in establishment computer 14. Once the information is recorded, all of the information in establishment computer 14 with respect to the user would then be uploaded to central computer 18. Step 134.
In this manner, the alcohol consumption by an individual could be limited to insure that he did not become impaired so as to present a threat to himself or others.
The above description is of the preferred embodiment. Various alterations and changes can be made without departing from the spirit and broader aspects of the invention as defined in the appended claims, which are to be interpreted in accordance with the principles of patent law including the doctrine of equivalents. Any references to claim elements in the singular, for example, using the articles “a,” “an,” “the,” or “said,” is not to be construed as limiting the element to the singular.
Vercnocke, Geoffrey A., Vergote, Daniel S.
Patent | Priority | Assignee | Title |
8195406, | Dec 03 2008 | International Business Machines Corporation | Estimating consumer status using non-invasive technology |
8814804, | Dec 13 2010 | IPH, LLC | Interactive blood-alcohol content tester |
Patent | Priority | Assignee | Title |
4463098, | Oct 14 1980 | Albert Einstein College of Medicine of Yeshiva University a Division of | Hemoglobin marker of alcoholism |
4632428, | Feb 06 1984 | Combination medical data, identification and health insurance card | |
4770996, | Jun 12 1986 | Identification of individuals predisposed toward alcohol abuse | |
4822988, | Nov 08 1985 | Eurotechnique | Card containing a component and a micromodule having side contacts |
5049728, | Apr 04 1990 | COMPUTERIZED DATA SYSTEMS FOR MANUFACTURERS C D S M | IC card system with removable IC modules |
5066583, | Dec 21 1988 | Wisconsin Alumni Research Foundation | Method for distinguishing alcoholics from non-alcoholics |
5880445, | Oct 19 1993 | Ricoh Company, Ltd. | Method of recording information and images in card having information recording portion and image recording portion |
5974124, | Jan 21 1997 | MED GRAPH, INC | Method and system aiding medical diagnosis and treatment |
6017308, | May 19 1998 | Blood alcohol content monitoring device | |
6113538, | Sep 15 1997 | PREDICTIVE SAFETY SRP, INC | Alertness tester |
6421650, | Mar 04 1998 | Goetech LLC | Medication monitoring system and apparatus |
6454708, | Apr 15 1999 | CLEARPATH PARTNERS, LLC | Portable remote patient telemonitoring system using a memory card or smart card |
6557752, | Jun 12 1996 | Q-International, Inc.; Q-INTERNATIONAL, INC | Smart card for recording identification, and operational, service and maintenance transactions |
6679425, | Jun 18 1997 | EXPRESS TECHNOLOGY, INC | Systems, apparatus and processes to verify a person's age to determine if the person is authorized |
6708893, | Apr 12 2002 | Lucent Technologies Inc. | Multiple-use smart card with security features and method |
7163146, | Jan 21 2003 | Pump-On LLC | Methods and systems for retail club membership authorization |
WO186463, | |||
WO193756, | |||
WO2081015, | |||
WO3056491, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Mar 22 2005 | I.C.A.R.D., L.L.C. | (assignment on the face of the patent) | / | |||
May 09 2005 | VERCNOCKE, GEOFFREY A | I C A R D , L L C | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 016074 | /0308 | |
May 09 2005 | VERGOTE, DANIEL S | I C A R D , L L C | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 016074 | /0308 |
Date | Maintenance Fee Events |
Feb 28 2011 | M2551: Payment of Maintenance Fee, 4th Yr, Small Entity. |
Feb 01 2012 | ASPN: Payor Number Assigned. |
Jun 12 2015 | REM: Maintenance Fee Reminder Mailed. |
Oct 30 2015 | EXPX: Patent Reinstated After Maintenance Fee Payment Confirmed. |
Sep 26 2016 | M2552: Payment of Maintenance Fee, 8th Yr, Small Entity. |
Sep 26 2016 | M2558: Surcharge, Petition to Accept Pymt After Exp, Unintentional. |
Sep 26 2016 | PMFG: Petition Related to Maintenance Fees Granted. |
Sep 26 2016 | PMFP: Petition Related to Maintenance Fees Filed. |
Apr 30 2019 | M2553: Payment of Maintenance Fee, 12th Yr, Small Entity. |
Date | Maintenance Schedule |
Oct 30 2010 | 4 years fee payment window open |
Apr 30 2011 | 6 months grace period start (w surcharge) |
Oct 30 2011 | patent expiry (for year 4) |
Oct 30 2013 | 2 years to revive unintentionally abandoned end. (for year 4) |
Oct 30 2014 | 8 years fee payment window open |
Apr 30 2015 | 6 months grace period start (w surcharge) |
Oct 30 2015 | patent expiry (for year 8) |
Oct 30 2017 | 2 years to revive unintentionally abandoned end. (for year 8) |
Oct 30 2018 | 12 years fee payment window open |
Apr 30 2019 | 6 months grace period start (w surcharge) |
Oct 30 2019 | patent expiry (for year 12) |
Oct 30 2021 | 2 years to revive unintentionally abandoned end. (for year 12) |