Controlled substance tracking system and method
A method for tracking prescriptive medications is provided whereby a complete prescriptive medication history including active and inactive prescriptive medications is stored for a plurality of patients utilizing a plurality of pharmacies wherein the pharmacies may be affiliated or unaffiliated. The information may be selectively retrieved through a secure computer connection by entities such as hospitals, doctors, pharmacies, insurance companies, government agencies and the like. The information may be utilized to benefit the patient whereby a doctor is able to obtain an accurate view of the complete prescriptive medication history of the patient including prescriptive medications by other doctors. Hospitals will be able to obtain, in accord with the invention, a prescriptive medication history prior to treatment such as emergency treatment where such information is not normally available. The stored data for each prescriptive medication transaction includes searchable data such as the patient's name, address, doctor, pharmacy, aberrant use flag, and the like.
This is a reissue application claims the benefit of U.S. Pat. No. 8,219,418, filed on Jun. 27, 2011 and issued on Jul. 10, 2012, which is a continuation of U.S. Provisional Application No. 60/332,807 filed on Nov. 14, 2001, and claims the benefit of U.S. application Ser. No. 10/062,251 filed Jan. 31, 2002, and claims the benefit of and is a continuation of U.S. application Ser. No. 10/803,259, filed Mar. 18, 2004, now U.S. Pat. No. 7,970,622 issued Jun. 28, 2011, the entirety Pat. No. 7,970,622, filed on Mar. 18, 2004 and issued Jun. 28, 2011, which is a continuation of U.S. patent application Ser. No. 10/062,251 filed on Jan. 31, 2002, which is now abandoned, wherein this reissue application claims the benefit of, and this abandoned patent application was a non-provisional of, U.S. Provisional Patent Application No. 60/332,807, filed on Nov. 14, 2001 and now abandoned, the entireties of which is are incorporated herein by this reference.
FIELDThe present invention relates generally to methods and systems for tracking controlled substances and, more specifically, to methods and systems especially suitable for tracking and managing prescription information in aggregate.
BACKGROUNDAlthough the exact frequency of prescription drug abuse is unknown in the United States, it has been reported that more than fifty percent of all emergency room visits for drug-related problems are connected to prescription drug misuse or accidental overdose. It has also been estimated that in some communities, more than sixty percent of medical examiner cases are related to prescription drugs.
It is estimated that more than four million people a year in the U.S. misuse or abuse prescription drugs. For instance, according to an August 1999 article in the Journal of the American Geriatrics Society, older Americans (age 65 and older) currently account for 12.5% of the total US population, but consume 25% of all prescription medications. It is documented that 17% of the senior population misuses medications, accounting for approximately $2 billion loss annually.
The AMA estimates that 5% of physicians are grossly negligent and 1-1.5% are dishonest in their prescribing of pharmaceuticals. This would amount to a cost of $2.5 billion annually.
Three hundred fifty thousand adverse medication errors (probably far greater not reported) occur each year among one-half million nursing home residents in the United States. One employee in ten has a problem with alcohol/drugs. Absenteeism is 66% higher among drug users.
Among drug users, health benefit utilization is 300% higher, disciplinary actions are 90% higher, and employee turnover is significantly higher. Forty-seven percent of workplace accidents are drug related.
In fact, it is clear that the Healthcare industry is facing a number of challenges today unlike ever faced before. An educated, consuming public has ever increasing expectations for exponential improvement in healthcare delivery, while at the same time, economic pressures are forcing tighter controls over cost, efficiency and quality.
The industry has widely recognized a need for better efficiencies, but without notable success in many areas, including prescription abuse. For instance, the Healthcare Information Portability and Accountability Act (HIPAA) mandates making the exchange of information more ubiquitous, secure, and efficient but does not provide a solution with respect to prescription tracking and abuse. While it is well known that it would be desirable to reduce spiraling cost structures, mitigate health risks, provide more efficient billing and business modeling, eliminate redundancy, and improve informational flow, the solutions to such overwhelming problems are generally unavailable.
In 1993, prescription drug sales were $25 billion. Since that time prescriptions have risen more than 50%, totaling close to three billion prescriptions annually. With soaring costs, the sum of prescription drugs is currently greater that $50 billion annually, with limited ability to control or manage those costs.
These estimates are only for the cost of drugs themselves, and don't include many of the highly significant tangential costs associated with abuse, additional healthcare requirements and costs associated with drug interactions, insurance fraud resulting from purchase of class drugs for resale on the street, dispensing of wrong prescriptions due to misread prescriptions, and the like, which are proportionally of greater cost.
It would be desirable to provide a healthcare utility that can assist substantially in reducing these misused and abused prescriptions. It would be desirable to provide major changes in the delivery of prescription drugs that produce measurable social and economic impacts on spending within the healthcare value chain including less abuse-related healthcare costs, fewer erroneous prescriptions, more accountability, and better tracking and management of prescriptions.
Patents that involve attempts to solve the above or related problems include the following:
U.S. Pat. No. 6,067,524, issued May 23, 2000, to Byerly et al., discloses a method and system for generating advisory messages to pharmacy patients that includes appending patient-specific information to a data record containing normally transmitted information. The data record is transmitted between a third party computer and a pharmacy computer during a pharmacy transaction. The data record transmitted to the pharmacy computer is captured by an advisory computer as the data record is received by the pharmacy computer or after the data record is transmitted to the pharmacy computer, and the patient-specific information is extracted from the captured data record. The advisory computer generates an advisory message based on the extracted patient-specific information, and it transmits the generated advisory message to a pharmacy printer. The advisory computer includes a memory containing a data structure for storing the patient-specific information, the normally transmitted information, and the generated advisory message. A computer program product includes a computer storage medium and a computer program code mechanism embedded in the computer storage medium for causing a computer to generate an advisory message. The computer program code mechanism includes a first computer code device configured to append the patient-specific information, a second computer code device configured to capture the data record transmitted to the pharmacy computer, a third computer code device configured to extract the patient-specific information from the captured data record, a fourth computer code device configured to generate the advisory message based on the extracted patient specific information, and a fifth computer code device configured to transmit the generated advisory message to the pharmacy printer.
U.S. Pat. No. 6,055,507, issued Apr. 25, 2000, to D. W. Cunningham, discloses a new and improved method of dispensing, tracking and managing pharmaceutical product samples by communicatively linking prescribers and pharmacies to a central computing station. The method entails utilizing product trial media that is exchanged for actual pharmaceutical product. The media is encoded with information that identifies a particular pharmaceutical trial product, such as by magnetic encoding similar to that used with credit cards. The media is distributed to participating medical doctors or prescribers who then activate the media via the central computing station. The prescriber then transfers the activated media to patients who then present the media to participating pharmacies. Before filling the pharmaceutical trial product identified by the media, the pharmacy validates the media via a link with the central computing station. Then, the pharmacy dispenses the prescribed pharmaceutical trial product. The central computing station also includes a database that records data related to the use of the media so that all pharmaceutical trial products can be accounted for.
U.S. Pat. No. 5,542,420, issued Aug. 6, 1996, to Goldman et al., discloses a health care system for specifying edibles to individual subjects. The personalized method and system for storage, communication, analysis and processing of health-related data comprises a storage containing data relating to health and edibles and is adapted to receive data on the conditions and characteristics of the individual subjects. The health care system further comprises input terminals adapted to be coupled to the storage means for providing data on the conditions and characteristics of the individual subjects, and a health computer for correlating the data relating to health and edibles with the data on the condition and characteristics of an individual subject to provide a personalized prescription of edibles.
U.S. Pat. No. 5,628,530, issued May 13, 1997, to G. B. Thornton, discloses a method and system for collectively tracking demographics of physician prescribed starter drug samples dispensed to a plurality of patients from a plurality of different dispensing locations employs a multipart product specific sample drug voucher, such as a smart card or a pre-printed two part voucher, which has a marketing information portion and a separable prescription portion to be completed by the prescribing physician with starter drug sample quantity and dosage information along with patient demographic information. The prescription portion is segregated from the marketing information portion at the pharmacy either electronically by a card reader, if it had been encoded on a smart card by the physician, or physically by separation along a perforation, if recorded on a two part voucher, and is electronically retrievably stored in the pharmacy computer from where this tracking information is electronically transmitted to a central remote computer, such as at the drug manufacturer, for subsequent rapid market analysis.
U.S. Pat. No. 5,737,539, issued Apr. 7, 1998, to Edelson et al., discloses an electronic prescription creation system for use by professional prescribers at the point of care which has a prescription division subsystem permitting creation of a single prescription to be automatically divided into two components for fulfillment of one portion quickly and locally at higher cost and of another portion by remote mail order taking more time but providing a cost saving for a major part of the prescription. The prescription creation system has an ability to access remote source databases for system presentation to the prescriber of relevant, authorized and current drug, drug formulary and patient history information, with dynamic creation of a transient virtual patient record, the information being presented to the prescriber before completion of the prescription, permitting enhancement of the quality of prescribing decisions.
U.S. Pat. No. 5,758,095, issued May 26, 1998, to Albaum et al., discloses a system and method for ordering and prescribing drugs for a patient. This system includes an improved process for facilitating and automating the process of drug order entry. The user may interact with the system in a variety of ways such as keyboard, mouse, pen-base entry or voice entry. The system includes a database containing medical prescribing and drug information which is both general and patient-specific. The system also permits the user to view current and previously prescribed medications for any patient. The system can alert the user to potentially adverse situations as a result of the prescribed medication based on information in the database. The system also can automatically determine product selection based on descriptions and can automatically communicate the order to a pharmacy. Further, the system includes a means for automatically displaying messages to the user relating to predetermined situations. For example, such situations may include a medication which is not available in the formulary or the prescription of a non-recommended medication. The system streamlines the order entry process and makes information important to the drug ordering process easily available.
U.S. Pat. No. 5,845,255, issued Dec. 1, 1998, to C. Mayaud, discloses a wirelessly deployable, electronic prescription creation system for physician use that captures into a prescription a patient condition-objective of the prescribed treatment and provides for patient record assembly from source elements, with privacy controls for patient and doctor, adverse indication review and online access to comprehensive drug information including scientific literature. Extensions to novel multi-drug packages and dispensing devices, and an “intelligent network” remote data retrieval architecture as well as onscreen physician-to-pharmacy and physician-to-physician e-mail are also provided.
U.S. Pat. No. 5,991,731, issued Nov. 23, 1999, to Colon et al., discloses a computer system and method for managing data used in conducting clinical studies concerning subjects at a plurality of participating, geographically distributed clinical sites, wherein each participating clinical site having a computer or inputting, transmitting and receiving data over the Internet. An Internet network server computer is interfaced to a database host computer through a private network. The system communicates data over the Internet to determine patient eligibility, randomization and initial prescriptions, which can then be adjusted by the physician online. The final prescription is printed out for signature and sent electronically to a distribution center. Study data is maintained in a database in the host computer behind a firewall provided in the Internet server computer.
U.S. Pat. No. 5,832,449, issued Nov. 3, 1998, to D. W. Cunningham, discloses a new and improved method of dispensing, tracking and managing pharmaceutical product samples by communicatively linking prescribers and pharmacies to a central computing station. The method entails utilizing product trial media that is exchanged for actual pharmaceutical product. The media is encoded with information that identifies a particular pharmaceutical trial product, such as by magnetic encoding similar to that used with credit cards. The media is distributed to participating medical doctors or prescribers who then activate the media via the central computing station. The prescriber then transfers the activated media to patients who then present the media to participating pharmacies. Before filling the pharmaceutical trial product identified by the media, the pharmacy validates the media via a link with the central computing station. Then, the pharmacy dispenses the prescribed pharmaceutical trial product. The central computing station also includes a database that records data related to the use of the media so that all pharmaceutical trial products can be accounted for.
U.S. Pat. No. 6,068,156, issued May 30, 2000, to Liff et al., discloses an automated drug dispensing system that includes a cabinet adapted to store a variety of prepackaged pharmaceuticals in a plurality of bins for filling patient prescriptions. Each bin stores a particular variety of packaged multiple-dose pharmaceutical. Each variety of pharmaceutical is associated with a particular code. A controller receives request signals and in response generates dispense signals. Each bin includes a dispenser coupled to the controller for dispensing the packaged pharmaceuticals therefrom in response to a dispense signal sent from the controller. After a package is dispensed, a code reader determines the code of the dispensed package and verifies whether the code on the dispensed package matches the code of the requested package.
U.S. Pat. No. 6,073,106, issued Jun. 6, 2000, to Rozen et al., discloses a method whereby via Internet communications or via phone/fax/mail, a participant is prompted to provide a constant identifier and a selected password. Emergency and confidential categories of medical information are identified, and the participant is prompted to provide personal information in each of the categories and a different personal identification number (E-PIN, C-PIN) for each category. The participant is also prompted to provide an instruction to disclose or to not disclose the personal information in the emergency category in the event a requester of the information is an emergency medical facility and is unable to provide the participant's E-PIN. Alteration of any of the participant's medical information is enabled upon presentation of the participant's identifier and password by the requester. The emergency information or the confidential information is disclosed upon presentation of the participant's identifier and E-PIN or C-PIN. In addition, the emergency information is disclosed to an emergency medical facility verified as such by a service provider in the event the participant has provided an instruction to disclose the emergency information. Storage and access to health related documents such as healthcare power of attorney, consent for treatment, and eyeglass prescription is also provided.
U.S. Pat. No. 6,128,620, issued Oct. 3, 2000, to Pissanos et al., discloses a medical database and associated methods especially suited for compiling information in a medical malpractice situation. A general medical database is provided and specific medical information corresponding to a given situation is entered. Entry of the information automatically cross-references some terms of the entered data to definitions in the general medical database. Terms are readily looked up when reviewing specific medical information and definitions are easily inserted where desired. A drug reference display provides two-way lookup from drugs to their side effects (or contraindications or interactions) and back. Significant information from an entered medical chronology is easily copied to a significant information section when a reviewer finds the information important.
U.S. Pat. No. 6,195,612, issued Feb. 27, 2001, to T. L. Pack-Harris, discloses a pharmacy benefit management system that includes a pharmacy computer for generating pharmacy claim information based on pharmacy activity of a medical group. A health plan computer is responsive to the pharmacy claim information for generating pharmacy activity information for the medical group. A medical group computer receives the pharmacy activity information from the health plan computer and stores the pharmacy activity information. The pharmacy activity information is processed to generate utilization information to enable the medical group to monitor the pharmacy activity.
U.S. Pat. No. 6,216,104 B1, issued Apr. 10, 2001, to Mosfeghi et al., discloses a Computer-based Patient Record (CPR) system including user equipment devices which are configured for speech synthesis in response to speech markup language text and which are connected via a network to a middle tier of a server system. The CPR system further includes a message delivery facility for delivery of textual messages to any of pager, electronic mail, or voice mail (after text-to-speech synthesis) message delivery vehicles. The server system accesses a user specific data store containing speech synthesis profiles which include prosodic information of the voices and speech of users, and message delivery profiles which specify which of the aforementioned message delivery vehicles are to be used and in what order. The stored speech synthesis information associated with an originator of a message and the stored message delivery information associated with the recipient of message are provided by the server to user equipment or a reminder generator to produce speech markup files containing information needed to synthesize the vocal and speech characteristics of the originator accompanied by delivery instructions reflecting the message delivery preferences of the recipient.
U.S. Pat. No. 6,219,674 B1, issued Apr. 17, 2001, to J. B. Classen, discloses systems and methods for creating and using product data to enhance the safety of a medical or non-medical products. The systems receive vast amounts of data regarding adverse events associated with a particular product and analyze the data in light of already known adverse events associated with the product. The system develops at least one proprietary database of newly discovered adverse event information and new uses for the product and may catalog adverse event information for a large number of population sub-groups. The system may also be programmed to incorporate the information into intellectual property and contract documents. Manufacturers can include the information in consumer product information, which they provide to consumers or, in the case of certain medical products, prescribers of the medical products.
U.S. Pat. No. 6,230,142 B1, issued May 8, 2001, to Benigno et al., discloses systems useful for analyzing data related to clinical pathways and performing actions based upon the analyses. A self-analyzing system for suggesting default clinical pathways for various procedures. A self-analyzing system for suggesting deviation from a current clinical pathway and entry into an alternative clinical pathway based upon historical information about the results of actions, statistical analysis systems based on the clinical pathways, a rating system for care providers or proposed pathways based on historical information, systems for gathering clinical pathway information, systems for tracking clinical pathway outcomes based on data collected post-treatment, a system for prequalification for appropriate discharge and post-discharge handling of and communication with a new class of patient, those requiring stable acute care, and a questionnaire computer language and subsystem are used in various stages of the systems disclosed. Corresponding methods are also disclosed.
U.S. Pat. No. 6,283,322 B1, issued Sep. 4, 2001, to Liff et al., discloses an automated drug dispensing system that includes a cabinet adapted to store a variety of prepackaged pharmaceuticals in a plurality of bins for filling patient prescriptions. Each bin stores a particular variety of packaged multiple-dose pharmaceutical. Each variety of pharmaceutical is associated with a particular code. A controller receives request signals and in response generates dispense signals. Each bin includes a dispenser coupled to the controller for dispensing the packaged pharmaceuticals therefrom in response to a dispense signal sent from the controller. After a package is dispensed, a code reader determines the code of the dispensed package and verifies whether the code on the dispensed package matches the code of the requested package.
U.S. Pat. No. 6,240,394 B1, issued May 29, 2001, to Uecker et al., discloses a system for generating targeted advisory messages for pharmacy patients based on selected monitored data components of each transaction. When a pharmacy computer prints transaction data, the system monitors the data using printer data capture hardware interposed between the pharmacy computer and its printer. An additional processor compares selected components of the monitored transaction data with preselected combinations of the components in a database. The database associates the preselected combinations of transaction data components with advisory message components retrieved from the database and used to build an advisory message for output to a printer, which may be the pharmacy computer or an additional printer. Targeting of the advisory messages is based on selected combinations of the identity of the drug being dispensed to the patient, the patient's age and gender, the new or renewal status of the prescription, and the identity of the party primarily responsible for payment to the pharmacy for the transaction.
The above-cited patents do not solve the problem of misused and abused prescriptions discussed above. Consequently, there remains a need for an improved system for tracking prescription drugs and/or controlled substances. Those of skill in the art will appreciate the present invention, which addresses the above, and other problems.
SUMMARYAn objective of the present invention is to provide an improved method for controlling information related to controlled substances and/or prescriptive medications.
Another objective of the present invention is to provide a complete prescriptive medication history of patients for use by doctors, hospitals, pharmacists, and other health care workers.
Another objective of the present invention is to provide a means for searching massive amounts of data for selected criteria to reduce costs involved with prescriptive medications.
These and other objectives, features, and advantages of the present invention will become apparent from the drawings, the descriptions given herein, and the appended claims. However, it will be understood that the above-listed objectives of the invention are intended only as an aid in quickly understanding aspects of the invention, and are not intended to limit the invention in any way, and therefore do not form a comprehensive or restrictive list of objectives, and/or features, and/or advantages.
Accordingly, the invention comprises, in one embodiment thereof, a method for tracking prescriptive medications. The method may comprise one or more steps such as, for instance, providing respective computer connections to a plurality of entities wherein the plurality of entities may comprise a plurality of unaffiliated and/or affiliated pharmacies, storing pharmaceutical computer data relating to prescriptive medication purchases obtained by a plurality of prescriptive medication purchasers from the plurality of unaffiliated pharmacies, and selectively transferring the pharmaceutical computer data through the computer connections to at least one of the plurality of entities for obtaining a medication history of a selected prescriptive medication purchaser for all prescriptive medications purchased by the selected prescriptive medication purchaser from all of the plurality of unaffiliated pharmacies based on the transferred pharmaceutical computer data.
The method may further comprise providing that the at least one of the plurality of entities comprises a physician's office and the selected prescriptive medication purchaser is a patient of the physician such that the physician's office utilizes the pharmaceutical computer data to verify the medication history of the selected prescriptive medication purchaser.
Other steps may further comprise providing that the at least one of the plurality of entities comprises a pharmacy with a pharmacist, such that when the selected prescriptive medication purchaser requests that the pharmacist fill a new prescriptive medication then the pharmacist utilizes the pharmaceutical computer data to compare the new prescriptive medication with respect to the medication history of the selected prescriptive medication purchaser. The method may further comprise the pharmacist accepting or declining to fill the new prescriptive medication based on the medication history.
Other steps may further comprise providing that at least one of the plurality of entities comprises a hospital and the selected prescriptive medication purchaser is a patient of the hospital such that the hospital utilizes the pharmaceutical computer data to determine the medication history of the selected prescriptive medication purchaser.
The method may further comprise providing that the pharmaceutical computer data for each of the prescriptive medication purchases comprises a name of a respective prescriptive medication purchaser, an address of the respective prescriptive medication purchaser, a drug prescribed, the respective prescriptive medication purchaser, a quantity of the drug, a dosage of the drug, a pharmacist name, and a doctor name.
The method may further comprise searching the stored pharmaceutical computer data based on one or more of the name of a respective prescriptive medication purchaser, the address of the respective prescriptive medication purchaser, the drug prescribed, the respective prescriptive medication purchaser, the quantity of the drug, the dosage of the drug, the pharmacist name, and the doctor name.
Other steps may further comprise storing pharmaceutical data related to whether a request for filling a prescriptive medication is filled or declined and/or providing that at least one of the plurality of entities comprises a government agency and/or storing pharmaceutical computer data relating to aberrant use of prescriptive medications.
The method of claim may further comprise providing that the plurality of entities may comprise a plurality of hospitals, a plurality of doctors, and at least one government agency, and selectively transferring the pharmaceutical computer data through the computer connections to at least one of the plurality of hospitals, the plurality of doctors, or the at least one government agency.
This summary is not intended to be a limitation with respect to the features of the invention as claimed, and this and other objects can be more readily observed and understood in the detailed description of the preferred embodiment and in the claims.
For a further understanding of the nature and objects of the present invention, reference should be had to the following detailed description, taken in conjunction with the accompanying drawings, in which like elements are given the same or analogous reference numbers and wherein:
While the present invention will be described in connection with presently preferred embodiments, it will be understood that it is not intended to limit the invention to those embodiments. On the contrary, it is intended to cover all alternatives, modifications, and equivalents included within the spirit of the invention.
DESCRIPTION OF THE EMBODIMENTSIn accord with the method of the present invention, a secure, private, independent, network-based, centralized method operable for tracking and managing prescriptive medication information in aggregate is provided which allows electronic querying and real-time notification of patients' prescriptive medication history at the time of prescriptive medication creation. According to the method of the invention, this information is accessible within a controlled and appropriate context for use by healthcare professionals involved in the delivery of care to that patient.
Referring now to the drawings and, more particularly to
Many different types of entities/organizations may be electronically interconnected in accord with the present invention with respect to pharmaceutical information control organization 12. The types of data available to each organization may be filtered depending on the type of organization/entity and the need thereof for the various types of pharmaceutical information available from pharmaceutical information control organization 12.
Consumers and patients 16 get the most benefit from the present invention. They will have a comfort knowing that their physician and other healthcare professionals involved in their care will have secure and private access to historical information about their active and inactive prescriptive medications that can create problems or interactions. Pharmaceutical information control organization 12 will permit consumers and their physicians to better manage the patient's prescriptive plan, lessening risk of misuse and counter indications. If desired, consumers may have access only to their own pharmaceutical records. Schedules of use may be provided and means for tracking, such as reminders, clocks, and so forth may be provided. If desired, consumers may provide feedback through pharmaceutical information control organization 12 as to the patient's perceived condition that may be accessed by physicians 18, pharmaceutical drug companies and/or research organizations 22 interested in drug efficacy, managed care organizations 20, and the like.
Government oversight entities 14, such as the DEA, FBI, CDC, and so forth, may be able to utilize data as required to reach the organization goals and within the limitations required therefore. For instance, the DEA may review data to determine areas where violations may be occurring. Presently, legal regulations may require that each time a prescriptive medication is filled that a paper copy of the transaction is forwarded to the DEA. However, compiling and using such data, which may involve billions of transactions, is overwhelming governmental manpower availability and results in high manpower costs with reduced investigative overview capability. Moreover, pharmacies waste manpower and time filling out and filing such papers. Government agencies such as the DEA, FBI, Veterans Administration Medical System, National Institute of Health, and the like, will find new efficiencies by utilizing the present invention. Even the pending new Medicare Programs, which include Pharmaceutical programs, can be brought to public availability with the comprehensive management support that is lacking today. The present invention removes many of the management limitations that affect such efficiencies and will help control costs of program delivery. All of these entities can have immediate access to potential medication abuse by identification of needless prescription duplications, potential drug interactions, and multi-source interstate prescriptive medication abuse. The system of the present invention may be utilized to recognize fraudulent prescriptive medications, geographically track selected drug purchases as may be desired in tracking disease spread, track purchases related to security investigations such as use of antidotes for certain bioweapons, track pharmaceutical purchase for other investigative reasons, obtain feedback from prescriptive medication users as discussed subsequently, and/or provide many types of information and statistics not presently available today.
Pharmaceutical companies and researchers 22 are in a constant race to provide the public with pharmacological formulations that are compatible with constantly evolving therapeutic formulations, and whose availability is being accelerated by the rapid expansion of effective clinical trials and research protocols. The pharmaceutical industry's ability to respond effectively to the competitive as well as regulatory demands is challenging because of the difficulty in realizing real or near term information access and tracking information. This responsibility requires an ongoing current database of pharmaceutical demands, immediate identification of adverse reactions, and recognition of the costly development of redundant pharmaceutical products. Pharmaceutical information control organization 12 provides the pharmaceutical industry with a vehicle to help them track and access appropriate information about prescriptive drugs. Pharmaceutical information control organization 12 provides the pharmaceutical industry with services which will assist in better planning, real time assessment and forecasting of regional pharmaceutical demands, helping to prevent essential medication shortages or unavailability. As well, the need for recalls can be more quickly determined based on focused adverse drug reactions, which are noted to occur.
Insurance companies 24, health organizations 28 such as employers' health organizations, workers' compensation providers, private third party payers, PPO's, HMO's, MCO's 20, Medicare programs, life insurance companies, and the like, can monitor information to immediately determine needless prescription duplications, potential drug interactions, and multi-source interstate prescriptive medication abuse to thereby significantly reduce insurance costs.
Pharmacies 26 may check to personally verify the drug usage of each purchaser to immediately detect problems related to abuse, fraud, and misuse of medications. Pharmacies require a more precise method of monitoring the efficiency of the distribution of the more than three billion prescriptive medications they fill each year. The number of chain pharmacies has now risen to approximately 35,000 stores. The ability of pharmacies 26 to provide the highest quality service is placing a strain on staffing and the delivery of rapid, timely and accurate products. Pharmacists are constantly challenged to circumvent duplication, abuse, fraud, and misuse of these medications while providing a cost effective medication delivery system. In the present health system the wide availability of pharmaceuticals from different pharmacies raises the risks of negative drug interactions and its associated destructive medical outcome. Pharmaceutical information control organization 12 can flag these issues in real time, thereby completely preventing or at least minimizing their occurrences. Pharmaceutical information control organization 12 reduces or eliminates reliance on poorly trained pharmacy technicians or assistants in ensuring compliance with the regulatory agency demands in the accurate delivery of pharmaceuticals.
Physicians 18 and other healthcare providers are at risk every time they prescribe a drug. These physicians, seeking to provide their patients with the best possible healthcare possible, do not currently have a vehicle for ensuring they have an accurate view of their patients' use of prescription drugs. Information about prescriptive medications from specialists or other referral services may not be communicated appropriately. Patients may not remember prescriptive medications they are taking, forgetting about them completely or not being able to pronounce them. Patients with regular prescriptive medication patterns can empower physicians to proactively deal with potential abuse problems. Pharmaceutical information control organization 12 can also provide audit information that helps protect the professional from lawsuits and other potential liabilities. Physicians or their staff can also interact with patients 16 through information control organization 12, if desired. As well, physicians and/or their staff can keep records of patients in the system as well as provide researchers valuable information about the effects of prescriptive medications on literally hundreds of millions of patients.
Hospitals' 30 therapeutics, e.g., emergency room, often requires administration of medications on an acute and subacute basis with little or no knowledge of each patient's outpatient medication profile. Pharmaceutical information control organization 12 provides this vital data in a manner that will change the hospital medication delivery system in a dramatic fashion. The added information immediately reduces costs, adverse drug reactions, and eliminates the risks of facilitating drug abuse and misuse.
Application products and industry service providers 32, such as healthcare informatics providers, may use industry standard XML interfaces W3C that may define a dialect of SGML suitable for use on the World-Wide Web. SGML provides a generic markup language for representing documents and/or other data. SGML is an International Standard that describes the relationship between a document's content and its structure. SGML allows document-based information to be shared and reused across applications and computer platforms in an open, vendor-neutral format. SGML is sometimes compared to SQL, in that it enables companies to structure information in documents in an open fashion, so that it can be accessed or reused by any SGML-aware application across multiple platforms. SGML is defined in “ISO 8879:1986 Information processing—Text and office systems—Standard Generalized Markup Language (SGML),” an ISO standard produced by JTC 1/SC 18 and amended by “Amendment 1:1988.” Unlike other common document file formats that represent both content and presentation, SGML represents a document's content data and structure (interrelationships among the data). Removing the presentation from content establishes a neutral format. SGML documents and the information within can easily be reused by publishing and non-publishing applications. SGML identifies document elements such as titles, paragraphs, tables, and chapters as distinct objects, allowing users to define the relationships between the objects for structuring data in documents. The relationships between document elements are defined in a Document Type Definition (DTD). This is roughly analogous to a collection of field definitions in a database. Once a document is converted into SGML and the information has been ‘tagged,’ it becomes a database-like document. It can be searched, printed or even programmatically manipulated by SGML-aware applications. If desired, secure access applets will allow informatics providers to integrate their products and services to include data access from pharmaceutical information control organization 12 in a seamless fashion. Thus, pharmaceutical information control organization 12 creates an independent utility service that adds value to application products and other service providers 32 while maintaining the overall goal of benefiting the public.
Thus, healthcare informatics and applications (such as physician practice management systems or Pharmacy systems) will be provided vehicles to securely access and interact with pharmaceutical information control organization 12 using industry standards such as XML and security tools. As appropriate, pharmaceutical information control organization 12 may provide secure applets that will make it easier to integrate computer interactions with pharmaceutical information control organization 12, as well as minimize the development costs associated with interfacing these applications.
In a preferred embodiment, when pharmaceutical data is needed by entities 102-120, or other suitable entities, then a login request is made as indicated at 124. The login request may be made through one or more different types of computer network interconnections, three possibilities of which are in
Alternatively, or in conjunction therewith, an application program interfaces (API) may be utilized to effect the login as indicated at 128. The API is the interface (calling conventions) by which an application program accesses the pharmaceutical data. An API may typically be defined as source code level and provides a level of abstraction between the application and the kernel (or other privileged utilities) to ensure the portability of the code. The API can provide an interface between a high level language and lower level utilities and services which were written without consideration for the calling conventions supported by compiled languages. In this case, the API's main task may be the translation of parameter lists from one format to another and the interpretation of call-by-value and call-by-reference arguments in one or both directions.
As another option, a consumer accessing pharmaceutical information control organization 12 may utilize a secure web browser as indicated at 130 to initiate the login. By web browser it is meant a program which allows a person to read hypertext. The browser gives some means of viewing the contents of nodes (or “pages”) and of navigating from one node to another.
Login authentication system 132 is provided to authenticate the validity of the login to provide verification of the identity of a person/entity or process that is attempting to access pharmaceutical information control organization 12. Authentication verifies that messages really come from their stated source. Various means of authentication may be utilized including login/password, biometrics, digital signatures, public and private digital encryption keys, digital certificates, and the like. The login process will identify the user and restrict the type of data transmitted according to the predetermined data sets that the particular user may access. If the login step is not successful, then the attempted login is automatically reported to security as indicated at 134.
Various types of security information may be stored by pharmaceutical information control organization 12 within data storage 122 or elsewhere. Such information may typically include the login name, login password, an optional biometric identifier, authentication of the user, authorized data set access for each user, authorized types of information transactions, an information log of access attempts (both successful and unsuccessful, an information log of transaction attempts (both successful and unsuccessful), encryption keys, digital signatures, and application programming interfaces where possible.
Assuming login process is successful, then the user may request a pharmaceutical information transaction as indicated at 134. Such transactions may be of various types and include searches, updates, selecting specific information, displaying information, and the like. The so-determined pharmaceutical information is available in the appropriate context via the secure applet, API, and/or browser as discussed hereinbefore in connection with the login as indicated at 126, 128, and 130. In this manner, current prescriptive medication information may be requested. The various programs discussed above and/or others may be used to select specific types of data for transfer as indicated at information access filter 136, and to send data either to or from the computer system of pharmaceutical information control organization 12, and change the format of the data as needed between that used by the computer software of pharmaceutical information control organization 12 and the user software.
Various types of data may be stored and/or obtained such as the doctor name, the doctor DEA number, patient name, patient ID (e.g., SS#, passport #, driver's license #, etc.), patient address, city, state, zip, patient phone number, drugs prescribed, dosage, frequency, start/end date, duration, quantity, number refills, whether substitution is allowed, generic allowed, notes, aberrant use flag, date prescription filed, place prescription filled, pharmacist name, pharmacist phone number, pharmacist DEA number, and application programming interfaces utilized.
The request of data from the pharmaceutical transaction 134 is sent to data storage 122. Various types of transactions may be utilized such as updates, key word or other types of searches, name searches, drug type searches, and/or other types of searches based on the above-listed types of data stored and/or other types of data which may be stored. Transactions include authentication transactions, display of active medication history, display of inactive medication history, and display of complete medication history. The display may be made by a patient identifier, patient name, date, drug name, doctor prescribing the medication, pharmacy, geography (city, state, zip code), by phone number, and/or by aberrant use flag. Other transactions may include adding a new record, update/change a record, add log entry, update log entry, display log entries, approve prescriptive medication, decline prescriptive medication, aberrant use flag true or false, accept results, decline results, logon, logoff, time out for inactivity, time out for disconnection, encryption, and creating reports.
The data is filtered as to availability for the particular user, as indicated at 136. The data may be sent for display 137 and/or printing. Data may be retrieved for updating data storage 122 as indicated at 148. The user may then check the data or the user's application in a preset time frame as indicated at 138. Depending on the type of user, red flag issues may be indicated. For instance, if a pharmacist is checking on a prescriptive medication prior to dispensing the prescriptive medication, a red flag as indicated at 140 may be issued if the prescription presents a problem, e.g., is a conflicting type of drug (contraindicated prescriptive medication) or perhaps a similar type of drug which in combination with a previous prescriptive medication might be harmful to the consumer. Red flags may be issued as a result of automatic or manual operation. The system 100 and/or the pharmacist and/or the doctor may require or suggest declining or approving the prescriptive medication, and otherwise add notes, comments, and flags, as desired. Assuming the user reviews and checks the information supplied within the time frame, the control may be returned to the user's application as indicated at 142 which may require action as indicated at 144 such as updating 146 either a local system and/or data storage 122. Updating of data storage 122 may be programmed to occur at any time, depending on system operation, and may occur outside of or during the transaction process as indicated at 148 whereby a connection is provided directly to the databases of the subscribers 102-120. Data storage 122 may also receive other provider information for use with applications and services as indicated at 150.
In a presently preferred embodiment, if the user does not respond to the check request within a desired time frame, if necessary, such as by stating whether the prescriptive medication is approved/declined or so forth, such as after the pharmacist has checked a new request to fill a prescription with respect to the requesters medical history, then the system resends the request to check the data as indicated at 152. Thus, the system seeks to know whether any new prescription is filled and the various data associated with the new prescriptive medication. Depending on the type of entity, different types of data may be requested. For instance, for the hospital, information as to treatment and prescriptive medications may be requested by the system. If no response is received as indicated at 154, then the data such as displayed data is cleared from the screen, the user is automatically logged off at 156, and a report is sent as may be required by an oversight agency as indicated at 158. For instance, there may be a requirement to enter new data related to prescriptive medications, whether prescriptions are filled or declined, and so forth. In either case, a log is made of the request, status, time, data, requester, as indicated at 160, and the access log is updated.
Pharmaceutical information control organization 12 will provide appropriate levels of reporting, as desired, to any selected oversight body or committee, as well as other healthcare members as appropriate and necessary. Such reporting/informational access can include up-to-date patient prescriptive medication information to their primary care physician or pharmacy, comparisons for potential drug interactions, and/or emergency information access.
For hosting and management, deployment of computer connections with pharmaceutical information control organization 12 is preferably made via a secure, redundant, hosted environment. Operational and administrative personnel will need to pass rigorous screening processes, and will only have access to information as is contextually necessary.
The foregoing disclosure and description of the invention is therefore illustrative and explanatory of one or more presently preferred embodiments of the invention and variations thereof, and it will be appreciated by those skilled in the art that various changes in the design, organization, order of operation, means of operation, equipment structures and location, methodology, and use of mechanical equivalents, as well as in the details of the illustrated construction or combinations of features of the various elements, may be made without departing from the spirit of the invention. As well, the drawings are intended to describe the concepts of the invention so that the presently preferred embodiments of the invention will be plainly disclosed to one of skill in the art but are not intended to be manufacturing level drawings or renditions of final products and may include simplified conceptual views as desired for easier and quicker understanding or explanation of the invention. As well, the relative arrangement of the components may be greatly different from that shown and still operate well within the spirit of the invention as described hereinbefore and in the appended claims. It will be seen that various changes and alternatives may be used that are contained within the spirit of the invention. Because many varying and different embodiments may be made within the scope of the inventive concept(s) herein taught, and because many modifications may be made in the embodiment herein detailed in accordance with the descriptive requirements of the law, it is to be understood that the details herein are to be interpreted as illustrative and not in a limiting sense.
In various example embodiments, disclosed are:
1. A pharmaceutical information control system comprising:
a data input/output station configured for use by doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof for entering and receiving prescription drug information of an individual;
the data input/output station in association with an entity database associated with a plurality of entities, networks, organizations, legislative bodies, or a combination thereof at various positions within the prescriptive medication system configured for maintaining databases of pharmaceutical data including prescription drug use data, each database having a format configured for providing for access control and management capabilities for a user as dictated by each of the plurality of entities, networks and organizations, legislative bodies or a combination thereof;
wherein the plurality of entities, networks organizations, legislative bodies, or a combination thereof comprise doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof;
a data storage device configured for accessing the entity databases of the plurality of entities, networks organizations, legislative bodies, or a combination thereof, and for storing entity information; and
an information access filter configured for selecting specific types of data for an individual available for transfer to the user; and
secure applets, application programming interfaces, service components, browsers, other programs, or combinations thereof configured for integration of an entity system,
wherein the secure applets, application programming interfaces, service components, browsers, other programs, or combinations thereof are configured to manage access and share contextually relevant information from the plurality of entities, networks and organizations, to provide business logic and workflow for the contextual management, collection, assembly, reporting, alerting, sharing or a combination thereof of information, and for mapping a format of the data used by the entity database and a format used by a data storage device configured for selecting pharmaceutical data, for creating a medication history of the individual, and for maintaining privacy of information related to the individual,
wherein the data storage is adapted for communicating with the information access filter and the secure applets, application programming interfaces, and service components, browsers, other programs, or combinations thereof, for analyzing the information in the data storage device, and for providing analysis thereof to the secure applets, application programming interfaces, and service components, browsers, other programs, or combinations,
wherein the secure applets, application programming interfaces, and service components, browsers, other programs, or combinations are in operative communication with the data storage device, the entity database and a login authentication system configured for validating the access of the user and for the user to requesting, by the user, a pharmaceutical transaction for the individual, wherein the pharmaceutical transaction is communicated to the data storage device for storage,
wherein the data storage device is adapted to acquire the entity information and prior pharmaceutical transactions related to the pharmaceutical transaction from the data input/output station in order for the data storage device to provide, within a timeframe, a response comprising at least one of: the medication history, the information related to the individual, a recommendation to approve the pharmaceutical transaction, a recommendation to decline the pharmaceutical transaction, notes, comments, or flags to the data input/output station,
wherein the data storage device is adapted to request and receive, within the timeframe, a reply for user action taken on the response to the pharmaceutical transaction for the individual, and either to update the medication history for the individual based on the response, or, if the data storage device does not receive the reply from the user, then to log off the user, send a report of no reply to an overseer in communication with the system, or both.
2. The pharmaceutical information control system of claim 1, wherein the user implements the the system to determine the medication history of the individual.
3. The pharmaceutical information control system of claim 1, wherein the pharmaceutical data for each prescriptive medication purchase comprises a name of purchaser, an address of the purchaser, a drug prescribed, a quantity of said drug, a dosage of said drug, a pharmacist name, a doctor name or a combination thereof.
4. A pharmaceutical information control system comprising:
a data input/output station configured for use by doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof for entering and receiving prescription drug information of an individual;
the data input/output station in association with an entity database associated with a plurality of entities, networks, organizations, legislative bodies, or a combination thereof at various positions within the prescriptive medication system configured for maintaining databases of pharmaceutical data including prescription drug use data, each database having a format configured for providing access control and management capabilities for a user as dictated by each of the plurality of entities, networks and organizations, legislative bodies or a combination thereof;
wherein the plurality of entities, networks organizations, legislative bodies, or a combination thereof comprise doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers, and combinations thereof;
a data query device configured for accessing the entity databases of the plurality of entities, networks and organizations and for providing the entity information to data input/output station;
an information access filter configured for selecting specific types of data for an individual available for transfer to the user; and
secure applets, application programming interfaces, service components, browsers, other programs, or combinations thereof configured for integration of an entity system,
wherein the secure applets, application programming interfaces, service components, browsers, other programs, or combinations thereof are configured to manage access and share contextually relevant information from the plurality of entities, networks and organizations, to provide business logic and workflow for the contextual management, collection, assembly, reporting, alerting, sharing or a combination thereof of information, and for mapping a format of the data used by the entity database and a format used by a data query device configured for selecting pharmaceutical data, for creating a medication history of the individual, and for maintaining privacy of information related to the individual,
wherein the data query device is adapted for communication with the information access filter and the secure applets, application programming interfaces, service components, browsers, other programs, or combinations thereof, for analyzing the information queried by the data query device, and for providing analysis thereof to the secure applets, application programming interfaces, service components, browsers, other programs, or combinations thereof,
wherein the secure applets, application programming interfaces, service components, browsers, other programs, or combinations thereof are in operative communication with the data query device, the entity database, and a login authentication system configured for validating access of the user and for requesting, by the user, a pharmaceutical transaction via the data input/output station, wherein the pharmaceutical transaction is communicated via the data query device to the data input/output station, and
wherein the data query device is adapted to acquire the entity information and prior pharmaceutical transactions related to the pharmaceutical transaction from the data input/output station in order for the data storage device to provide, within a timeframe, a response comprising at least one of: the medication history, the information related to the individual, a recommendation to approve the pharmaceutical transaction, a recommendation to decline the pharmaceutical transaction, notes, comments, or flags to the data input/output station, and
wherein the data query device is adapted to request and receive, within the timeframe, a reply for user action taken on the response to the pharmaceutical transaction for the individual, and either to update the medication history for the individual based on the response, or, if the data storage device does not receive the reply from the user, then to log off the user, send a report of no reply to an overseer in communication with the system, or both.
5. The pharmaceutical information control system of claim 4, wherein the user implements the system to determine the medication history of the individual.
6. The pharmaceutical information control system of claim 4, wherein the pharmaceutical data for each prescriptive medication purchase comprises a name of purchaser, an address of the purchaser, a drug prescribed, a quantity of said drug, a dosage of said drug, a pharmacist name, a doctor name or a combination thereof.
7. A pharmaceutical information control system comprising:
at least one entity database, at least one defined entity, network, legislative body, or a combination thereof, a data storage device, a software interface for the at least one entity database, and a filter for conversion of data between the at least one entity database and the data storage device;
wherein the at least one entity database is associated with the at least one defined entity, network, organization, legislative body, or a combination thereof at various points within a prescriptive medication system configured for maintaining databases of pharmaceutical data including prescription drug use data, each of the at least one entity databases having a format that provides for access control and management capabilities for a user as dictated by each of the at least one defined entity, network, organization, legislative body, or a combination thereof;
wherein the at least one defined entity, network, organization, legislative body, or a combination thereof comprise doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof;
the data storage device configured for accessing the at least one entity database of the at least one entity, network, organization, legislative body, or a combination thereof, and for storing entity information;
an information access filter configured for selecting specific types of data for an individual available for transfer to the user; and
the software interface configured to integrate an entity system,
wherein the software interface is configured to manage access and share contextually relevant information from the at least one defined entity, network, organization, legislative body, or a combination thereof, to provide business logic and workflow for the contextual management, collection, assembly, reporting, alerting, sharing or a combination thereof of information consistent with availability and satisfying legislative and corporate requirements and standards for data management, entity security, integration needs or combinations thereof, and to change a format of the data used by the at least one entity database and a format used by the data storage device configured for selecting pharmaceutical data, for creating a medication history of an individual, and for maintaining privacy of information related to the individual,
wherein the data storage device is adapted for communicating with the filter and the software interface, for analyzing the information in the data storage device, and for providing analysis thereof to the software interface,
wherein the software interface is in operative communication with the data storage device, the at least one entity database, and a login authentication system configured for validating the access of the user and for requesting, by the user, a pharmaceutical transaction, wherein the pharmaceutical transaction is communicated to the data storage device for storage,
wherein the data storage device is adapted to acquire the entity information and prior pharmaceutical transactions related to the pharmaceutical transaction, and for providing, within a timeframe, a response comprising at least one of: the medication history, the information related to the individual, a recommendation to approve the pharmaceutical transaction, a recommendation to decline the pharmaceutical transaction, notes, comments, or flags to the data input/output station,
wherein the data storage device is adapted to request and receive, within the timeframe, a reply for user action taken on the response to the pharmaceutical transaction for the individual, and either to update the medication history for the individual based on the response, or, if the data storage device does not receive the reply from the user, then to log off the user, send a report of no reply to an overseer in communication with the system, or both.
8. A pharmaceutical information control system comprising:
an entity database associated with a plurality of entities, networks, organizations, legislative bodies, or a combination thereof at various positions within a prescriptive medication system configured for maintaining databases of pharmaceutical data comprising prescription drug use data, wherein each database has a format configured to provide access control and management for a user as dictated by each of the plurality;
a data storage device configured for accessing entity databases of the plurality and for storing the pharmaceutical data, entity information, or combinations thereof of one or more of the entity databases;
logic for integrating the pharmaceutical information control system;
wherein the logic is configured for accessing, managing, collecting, assembling, reporting, alerting, sharing of the pharmaceutical data, the entity information, or combinations thereof from, between or among the plurality;
a data transfer device configured for providing the pharmaceutical data, the entity information, or combinations thereof from the entity database in a format used by the data storage device, for selecting the pharmaceutical data, and for creating a medication history of an individual;
wherein the data storage is adapted for communication with the data transfer device and the logic is adapted for analyzing the information in the data storage device and for providing analysis thereof to the logic;
wherein the logic is in operative communication with the data storage device, the entity database and a login authentication system configured to permit validation of user access, a request, by a user, for a pharmaceutical transaction, or combinations thereof, wherein the logic communicates the pharmaceutical transaction to the data storage device
wherein the data storage device is adapted to acquire the pharmaceutical data, the entity information, prior pharmaceutical transactions related to the pharmaceutical transaction, or combinations thereof, and to provide, within a timeframe, a response comprising at least one of: the medication history of the individual, the information related to the individual, a recommendation to approve or disapprove the pharmaceutical transaction, application of notes, comments or flags to the pharmaceutical transaction, or combinations thereof.
wherein the data storage device is adapted to request and receive, within the timeframe, a reply for user action taken on the response to the pharmaceutical transaction for the individual, and either to update the medication history for the individual based on the response, or, if the data storage device does not receive the reply from the user, then to log off the user, send a report of no reply to an overseer in communication with the system, or both.
9. The pharmaceutical information control system of claim 8, wherein the plurality comprises doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof.
10. The pharmaceutical information control system of claim 8, further comprising a data input/output station in communication with the entity database, the data storage device, the logic, and the data transfer device.
11. The pharmaceutical information control system of claim 8, further comprising a data input/output station for use by doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof for entering and receiving prescription drug information.
12. The pharmaceutical information control system of claim 8, wherein the logic comprises one or more secure applets, application programming interfaces, browsers, service components, other programs, or combinations thereof.
13. The pharmaceutical information control system of claim 8, wherein the logic is reduced to software, hardware or combinations thereof.
14. The pharmaceutical information control system of claim 8, wherein the data transfer device comprises an information access filter.
15. The pharmaceutical information control system of claim 8, wherein the data transfer device is configured to map a different format used by the entity database, one or more of the databases associated with the entity database, or combinations thereof to the format used by the data storage device.
16. The pharmaceutical information control system of claim 8, wherein the data transfer device is configured to translate a different format used by the entity database, one or more of the databases associated with the entity database, or combinations thereof to the format used by the data storage device.
17. The pharmaceutical information control system of claim 8, wherein a format used by the entity database, one or more of the databases associated with the entity database, or combinations thereof is identical or different to the format used by the data storage device.
18. The pharmaceutical information control system of claim 8, further comprising the data transfer device is configured to maintain privacy of the pharmaceutical data, the entity information, personal information or combinations thereof.
19. The pharmaceutical information control system of claim 8, wherein the medication history comprises prescriptions that are active, inactive, and combinations thereof between a time of the request and an earlier time for the individual.
20. The pharmaceutical information control system of claim 1, wherein the medication history comprises an active prescriptive history, an inactive prescriptive history, a complete prescriptive history, or any portion of the medication history.
Claims
1. A pharmaceutical information control system comprising:
- a data input/output station for use by doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof computer network comprising a plurality of entities for entering and, receiving, and communicating prescription drug information,;
- the data input/output station in association computer network in communication with an at least one entity database associated with a one or more of the plurality of entities, networks and organizations or a combination thereof at located at various positions within the prescriptive medication process that maintain databases of pharmaceutical data including prescription drug use data, each database having a format that provides for access control and management capabilities for individual users as dictated by each of the plurality of entities, networks and organizations, legislation or a combination thereof, pharmaceutical information control system, wherein the at least one entity database receives, stores, and communicates pharmaceutical computer data comprising medication history of a prescription medication purchaser and prescription drug quantities, dosages, and prescription drug use of the prescription medication purchaser;
- wherein the plurality of entities, networks and organizations comprise doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof,
- a central data storage device for accessing the entity databases of the plurality of entities, networks and organizations and storing entity information, in communication with each of the at least one entity databases for receiving and storing the pharmaceutical computer data of each entity database, managing and allowing access to the pharmaceutical computer data by the plurality of entities at various points within the pharmaceutical information control system, and creating an audit capability for tracking the pharmaceutical computer data for each prescription medication purchaser;
- application programming interfaces and in communication with the central data storage device and comprising secure applets, service components to enable the integration of an entity system,, browsers, other programs, and combinations thereof, wherein the application programming interfaces are configured to change a format of the pharmaceutical computer data received from the at least one entity database to a vendor-neutral format by defining a relationship between content and structure of the pharmaceutical computer data and removing presentation information from the pharmaceutical computer data, to allow the plurality of entities to integrate their products and services to include access to the pharmaceutical computer data from the central data storage device and to integrate computer interactions between the plurality of entities within the computer network of the pharmaceutical information control system;
- wherein the application programming interfaces and service components provide managed manage, access, and sharing of share contextually relevant information received from the plurality of entities, networks and organizations, and provide business logic and workflow for the contextual management implement at least one program that manages, collection collects, assembly assembles, reporting reports, alerting alerts, sharing or a combination shares, and combinations thereof of information, the pharmaceutical computer data available within the pharmaceutical information control system;
- an information access filter for mapping the format of the data between the data format used by the entity database and the format used by the data storage device for selecting that selectively filters from the central data storage device the pharmaceutical computer data for creating that creates a complete prescriptive history of an individual, and for maintaining the privacy of information related to the individual, the prescription medication purchaser;
- wherein the central data storage is adapted for communication device communicates with the information access filter and the application program interfaces and service components, for analyzing the information stored in the central data storage device comprising the medication history and the pharmaceutical computer data, and for providing analysis thereof to the application program programming interfaces and service components,
- wherein the application programming interfaces and service components are in operative association with the data storage device, the entity database and a login authentication system for validating the access of the user and for the user to request a pharmaceutical transaction, wherein the pharmaceutical transaction is communicated to the data storage device for storage,
- and wherein a user in association with one or more of the plurality of entities is authenticated for accessing the central data storage device of the pharmaceutical information control system to request a pharmaceutical transaction for a prescription medication purchaser, wherein the pharmaceutical transaction requested by the authenticated user is communicated to the central data storage device via the application programing interfaces;
- wherein the central data storage device is adapted to acquire the entity acquires information and prior pharmaceutical transactions related to the pharmaceutical transaction from the data input/output station, thereby acquiring an updated complete prescriptive history related to the current pharmaceutical transaction and analyzing the updated complete prescriptive history by generating one or more patterns that detect prescription duplication or multi-source prescription abuse for providing at least one of: the analysis of the information, or a recommendation to the user, thereby recommending the approval of the pharmaceutical transaction, the declination of the pharmaceutical transaction, application of notes, comments or flags to the pharmaceutical transaction or a combination thereof to the data input/output station from each of the plurality of entities and prior pharmaceutical transactions of the prescription medication purchaser from the computer network, wherein the central data storage device is programmed with one or more predetermined parameters relating to the prior pharmaceutical transactions, wherein the central data storage device denies the pharmaceutical transaction if the pharmaceutical transaction goes beyond any one of the predetermined parameters relating to the prior pharmaceutical transactions, and wherein the central data storage device provides, within a timeframe, a response of whether the pharmaceutical transaction is denied to the computer network associated with the pharmaceutical transaction request, and
- wherein the central data storage device requests and receives, within the timeframe, a reply taken on the response to the pharmaceutical transaction and either updates the pharmaceutical computer data of the prescription medication purchaser based on the response, or, if the central data storage device does not receive the reply within the timeframe, then logs off, sends a report of no reply, or both.
2. The pharmaceutical information control system of claim 1 wherein the user implements the pharmaceutical data to verify the complete prescriptive history of a patient.
3. The pharmaceutical information control system of claim 1, wherein the pharmaceutical computer data for each of the prescriptive medication purchases comprises a name of purchaser, an address of the purchaser, a drug prescribed, a quantity of said drug, a dosage of said drug, a pharmacist name, a doctor name, or a combination thereof.
4. A pharmaceutical information control system comprising:
- a data input/output station for use by doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof computer network comprising a plurality of entities for entering and, receiving, and communicating prescription drug information,;
- the data input/output station in association computer network in communication with an at least one entity database associated with a one or more of the plurality of entities, networks and organizations or a combination thereof at located at various positions within the prescriptive medication process that maintain databases of pharmaceutical data including prescription drug use data, each database having a format that provides for access control and management capabilities for individual users as dictated by each of the plurality of entities, networks and organizations, and or legislation or a combination thereof, pharmaceutical information control system, wherein the at least one entity database receives, stores, and communicates pharmaceutical computer data comprising medication history of a prescription medication purchaser and prescription drug quantities, dosages, and prescription drug use of the prescription medication purchaser;
- wherein the plurality of entities, networks and organizations comprise doctors, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers, managed care organizations, healthcare providers and combinations thereof,
- a central data query device for accessing the entity databases of the plurality of entities, networks and organizations and providing the entity information to data input/output station, in communication with each of the at least one entity databases for receiving and storing the pharmaceutical computer data of each at least one entity database, managing and allowing access to the pharmaceutical computer data information by the plurality of entities at various points within the pharmaceutical information control system, and creating an audit capability for tracking the pharmaceutical computer data for each prescription medication purchaser;
- application programming interfaces and in communication with the central data query device and comprising secure applets, service components to enable the integration of an entity system,, browsers, other programs, and combinations thereof, wherein the application programming interfaces are configured to change a format of the pharmaceutical computer data received from the at least one entity database to a vendor-neutral format by defining a relationship between content and structure of the pharmaceutical computer data and removing presentation information from the pharmaceutical computer data, to allow the plurality of entities to integrate their products and services to include access to the pharmaceutical computer data from the central data query device and to integrate computer interactions between the plurality of entities within the computer network of the pharmaceutical information control system;
- wherein the application programming interfaces and service components provide managed manage, access, and sharing of share contextually relevant information received from the plurality of entities, networks and organizations, and provide business logic and workflow for the contextual management implement at least one program that manages, collection collects, assembly assembles, reporting reports, alerting alerts, sharing or a combination shares, and combinations thereof of information, the pharmaceutical computer data available within the pharmaceutical information control system, wherein an alert by the at least one program comprises notification of one of: an adverse medical reaction to a prescribed medication, incompatibility with a pre-existing prescribed medication(s), a prescribed medication already filled, an inability to fill a prescribed medication, and fulfillment of a similar prescribed medication; and
- an information access filter for mapping the format of the data between the data format used by the entity database and the format used by the data query device for selecting that selectively filters from the central data query device the pharmaceutical computer data for creating that creates a complete prescriptive history of an individual, and for maintaining the privacy of information related to the individual, the prescription medication purchaser;
- wherein the central data query device is adapted for communication communicates with the information access filter and the application program interfaces and service components, for analyzing the information queried by the stored in the central data query device comprising the pharmaceutical computer data, and for providing analysis thereof to the application program programming interfaces and service components,
- wherein the application programming interfaces and service components are in operative association with the data query device, the entity database and a login authentication system for validating the access of the user and for the user to request a pharmaceutical transaction via the data input/output station, wherein the pharmaceutical transaction is communicated via the data query device to the data input/output station,
- and wherein a user in association with one or more of the plurality of entities is authenticated for accessing the central data query device of the pharmaceutical information control system to request a pharmaceutical transaction, wherein the pharmaceutical transaction requested by the authenticated user is communicated to the central data query device for storage via the application programing interfaces;
- wherein the central data query device is adapted to acquire the entity acquires information and prior pharmaceutical transactions related to the pharmaceutical transaction, thereby acquiring an updated complete prescriptive history related to the current pharmaceutical transaction and analyzing the updated complete prescriptive history by generating one or more patterns that detect prescription duplication or multi-source prescription abuse for providing at least one of: the analysis of the information, or a recommendation to the data input/output station, thereby recommending the approval of the pharmaceutical transaction, the declination of the pharmaceutical transaction, application of notes, comments or flags to the pharmaceutical transaction or a combination thereof to the data input/output station from each of the plurality of entities and prior pharmaceutical transactions from the computer network, wherein the central data query device is programmed with one or more predetermined parameters relating to the prior pharmaceutical transactions, wherein the central data query device denies the pharmaceutical transaction if the pharmaceutical transaction goes beyond any one of the predetermined parameters relating to the prior pharmaceutical transactions, and wherein the central data query device provides, within a timeframe, a response of whether the pharmaceutical transaction is denied to the computer network associated with the pharmaceutical transaction request, and
- wherein the central data query device requests and receives, within the timeframe, a reply taken on the response to the pharmaceutical transaction, and either updates the pharmaceutical computer data of the prescription medication purchaser based on the response, or, if the data query device does not receive the reply within the timeframe, then logs off, sends a report of no reply, or both.
5. The pharmaceutical information control system of claim 4 wherein the user implements the pharmaceutical data to verify the complete prescriptive history of a patient.
6. The pharmaceutical information control system of claim 4, wherein the pharmaceutical computer data for each of the prescriptive medication purchases comprises a name of purchaser, an address of the purchaser, a drug prescribed, a quantity of said drug, a dosage of said drug, a pharmacist name, a doctor name or a combination, and combinations thereof.
7. A pharmaceutical information control system comprising:
- at least one entity database, and at least one of: a defined entity, a network, an organization, a legislation, and combinations thereof, a data storage device, a software interface for each the at least one entity database, and a filter for conversion of data between the at least one entity database and the data storage device,;
- such that the wherein the at least one entity database is associated with the at least one of: the defined entities, networks and organizations entity the network, the organization, the legislation, and combinations thereof at various points within a prescriptive medication process that maintain system that maintains databases of pharmaceutical computer data comprising medication histories for each prescription medication purchaser, including prescription drug use data, each database having a format that provides for access control and management capabilities for individual users as dictated by each of the at least one defined entities, networks and organizations, legislation or a combination thereof,
- wherein the at least one of: the defined entities entity, networks and organizations the network, the organization, the legislation, and combinations thereof comprise doctors' offices, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health researchers research organizations and companies, managed care organizations, healthcare providers provider organizations and companies, and combinations thereof,;
- the data storage device for accessing accesses the at least one entity databases of database, the at least one of: the defined entities entity, networks and organizations the network, the organization, the legislation, and combinations thereof and storing stores entity information,; and
- at least one filter that selects specific types of data for an individual available for transfer to the user; and
- the software wherein an application programming interface to enable enables the integration of an entity the system, by changing a format of the pharmaceutical computer data to a vendor-neutral format by defining a relationship between content and structure of the pharmaceutical computer data and removing presentation information from the pharmaceutical computer data, to allow the at least one of: the defined entity, the network, the organization, the legislation, and combinations thereof to integrate their products and services to include access to the pharmaceutical computer data;
- wherein the software application programming interface provides managed access manages, accesses, and sharing of contextually shares relevant information from the at least one of: the defined entities entity, network and organizations the network, the organization, and provide business logic and workflow for the contextual management the legislation, and combinations thereof, and implements at least one program that manages, collection collects, assembly assembles, reporting reports, alerting alerts, sharing shares, or a combination any combinations thereof of, the entity information consistent with availability and satisfying legislative and corporate requirements and standards for data management, entity security, integration needs or combinations thereof,
- wherein the at least one filter for changing the format of the data between the data format used by the entity database and the format used by the data storage device for selecting selectively filters the pharmaceutical computer data for creating that creates a complete prescriptive history of an individual, and for maintaining the privacy of information related to the individual,
- wherein the data storage device is adapted for communication communicates with the at least one filter and the software application programming interface for analyzing, and analyzes the information in the data storage device, and providing provides analysis thereof to the software interface,
- wherein the software application programming interface is in operative association communicates with the data storage device, the at least one entity database, and a login authentication system for validating the access of the user and for the user to request a requesting a pharmaceutical transaction, wherein the pharmaceutical transaction is communicated to the data storage device for storage via the application programming interface, and
- wherein the data storage device is adapted to acquire acquires the entity information and prior pharmaceutical transactions related to the pharmaceutical transaction, thereby acquiring an updated complete prescriptive history related to the current pharmaceutical transaction and analyzing the updated complete prescriptive history by generating one or more patterns that detect prescription duplication or multi-source prescription abuse for providing at least one of: the analysis of the information, or a recommendation to the user, thereby recommending the approval of the pharmaceutical transaction, the declination of the pharmaceutical transaction, application of notes, comments or flags to the pharmaceutical transaction or a combination thereof, wherein the central data storage device is preprogrammed with one or more predetermined parameters, wherein the central data storage device denies the pharmaceutical transaction if the pharmaceutical transaction goes beyond the predetermined parameters, and wherein the data storage device provides, within a timeframe, a response of whether the pharmaceutical transaction was denied to the at least one entity database associated with the pharmaceutical transaction request,
- wherein the data storage device requests and receives, within the timeframe, a reply taken on the response to the pharmaceutical transaction, and either updates the pharmaceutical computer data of the prescription medication purchaser based on the response, or, if the data storage device does not receive the reply within the timeframe, then logs off, sends a report of no reply, or both.
8. A pharmaceutical information control system comprising:
- at least one entity database associated with a plurality of entities located at various positions within the pharmaceutical information control system, wherein the at least one entity database receives, stores, and communicates pharmaceutical computer data comprising medication history of a prescription medication purchaser and prescription drug quantities, dosages, and prescription drug use of the prescription medication purchaser;
- a central data storage device in communication with each of the at least one entity databases for receiving and storing the pharmaceutical computer data of each prescription medication purchaser received from the at least one entity database, wherein the central data storage device manages and allows access to the pharmaceutical computer data information by the plurality of entities at various points within the pharmaceutical information control system, and creates an audit capability for tracking the pharmaceutical computer data for each prescription medication purchaser;
- at least one program for integrating the pharmaceutical information control system by changing a format of the pharmaceutical computer data to a vendor-neutral format by defining a relationship between content and structure of the pharmaceutical computer data and removing presentation information from the pharmaceutical computer data, to allow the plurality of entities to integrate their products and services to include access to the pharmaceutical computer data from the central data storage device,
- wherein the at least one program accesses, manages, collects, assembles, reports, alerts, shares, and combinations thereof, the pharmaceutical computer data available within the pharmaceutical information control system; and
- a data transfer device, wherein the central data storage device communicates with the data transfer device and the at least one program for analyzing information stored in the central data storage device and for providing analysis thereof to the at least one program;
- wherein a user in association with one or more of the plurality of entities is authenticated for accessing the central data storage device of the pharmaceutical information control system to request a pharmaceutical transaction, wherein the pharmaceutical transaction requested by the authenticated user is communicated to the central data storage device via the at least one program;
- wherein the central data storage device acquires information from each of the plurality of entities and prior pharmaceutical transactions, wherein the central data storage device is programmed with one or more predetermined parameters relating to the prior pharmaceutical transactions, wherein the central data storage device denies the pharmaceutical transaction if the pharmaceutical transaction goes beyond any one of the predetermined number of parameters relating to the prior pharmaceutical transactions, and
- wherein the central data storage device provides, within a timeframe, a response of whether the pharmaceutical transaction is denied to the plurality of entities associated with the pharmaceutical transaction request, and wherein the central data storage device requests and receives, within the timeframe, a reply taken on the response to the pharmaceutical transaction, and either updates the pharmaceutical computer data of the prescription medication purchaser based on the response, or, if the central data storage device does not receive the reply, then logs off, sends a report of no reply, or both.
9. The pharmaceutical information control system of claim 8, wherein the plurality of entities comprises doctors' offices, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health research organizations and companies, managed care organizations, healthcare provider organizations and companies and combinations thereof.
10. The pharmaceutical information control system of claim 8, further comprising a computer network in communication with the at least one entity database.
11. The pharmaceutical information control system of claim 8, further comprising a computer network in communication with the at least one entity database for use by doctors' offices, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health research organizations and companies, managed care organizations, healthcare provider organizations and companies and combinations thereof for entering and receiving prescription drug information.
12. The pharmaceutical information control system of claim 8, wherein the at least one program comprises one or more secure applets, application programming interfaces, browsers, service components, other programs, and combinations thereof.
13. The pharmaceutical information control system of claim 8, wherein the at least one program is software, hardware, and combinations thereof.
14. The pharmaceutical information control system of claim 8, wherein the data transfer device comprises an information access filter.
15. The pharmaceutical information control system of claim 8, wherein the data transfer device selects the pharmaceutical computer data that creates a complete prescription history of the prescription medication purchaser.
16. The pharmaceutical information control system of claim 8, wherein the data transfer device translates data format used by each of the at least one entity databases to the data format used by the central data storage device.
17. The pharmaceutical information control system of claim 8, wherein a data format used by the at least one entity database is different than a data format used by the central data storage device.
18. The pharmaceutical information control system of claim 8, further comprising the central data storage device maintains privacy of the pharmaceutical computer data within the pharmaceutical information control system.
19. A pharmaceutical information control system, wherein the system comprises:
- a computer network comprising a plurality of entities for entering, receiving, and communicating prescription drug information;
- the computer network in communication with at least one entity database associated with one or more of the plurality of entities, located at various positions within the pharmaceutical information control system, wherein the at least one entity database receives, stores, and communicates pharmaceutical computer data comprising medication history of a prescription medication purchaser and prescription drug quantities, dosages, and use data of the prescription medication purchaser;
- a central data storage device in communication with each of the at least one entity databases for receiving and storing the pharmaceutical computer data of each entity database, managing and allowing access to the pharmaceutical computer data information by the plurality of entities at various points within the prescription medication process, and creating an audit capability for tracking the pharmaceutical computer data for each prescription medication purchaser;
- application programming interfaces communicate with the central data storage device and comprise secure applets, service components, browsers, other programs, and combinations thereof, wherein the application programming interfaces are configured to change a format of the pharmaceutical computer data received from the at least one entity database to a vendor-neutral format by defining a relationship between content and structure of the pharmaceutical computer data and removing presentation information from the pharmaceutical computer data, to allow the plurality of entities to integrate their products and services to include access to the pharmaceutical computer data from the central data storage device and to integrate computer interactions between the plurality of entities within the computer network of the pharmaceutical information control system;
- wherein the application programming interfaces manage, access, and share contextually relevant information received from the plurality of entities, and implement at least one program that manages, collects, assembles, reports, alerts, shares, and combinations thereof, the pharmaceutical computer data available within the pharmaceutical information control system; and
- an information access filter that selectively filters from the central storage device the pharmaceutical computer data that creates a complete prescription history of the prescription medication purchaser,
- wherein the central data storage device communicates with the information access filter and the application programing interfaces for analyzing information stored in the central data storage device comprising the pharmaceutical computer data, and for providing analysis thereof to the application programing interfaces,
- wherein a user in association with one or more of the plurality of entities is authenticated for accessing the central data storage device of the pharmaceutical information control system to request a pharmaceutical transaction, wherein the authentication process comprises computer transactions for comparing a user login name and/or password and a user biometric identifier for authentication of the user, and wherein the pharmaceutical transaction requested by the authenticated user is communicated to the central data storage device for analysis and storage via the application programing interfaces;
- wherein the central data storage device acquires information from each of the plurality of entities and prior pharmaceutical transactions from the computer network, wherein the central data storage device is programmed with one or more predetermined parameters relating to the prior pharmaceutical transactions, wherein the central data storage device denies the pharmaceutical transaction if the pharmaceutical transaction goes beyond any one of the predetermined number of parameters relating to the prior pharmaceutical transactions, and wherein the central data storage device provides, within a timeframe, a response of whether the pharmaceutical transaction is denied to the computer network associated with the pharmaceutical transaction request, and
- wherein the central date storage device requests and receives, within the timeframe, a reply taken on the response to the pharmaceutical transaction and either updates the pharmaceutical computer data of the prescription medication purchaser based on the response, or if the central data storage device does not receive the reply within the timeframe, then logs off, sends a report of no reply, or both.
20. The pharmaceutical information control system of claim 1, wherein the plurality of entities comprises doctors' offices, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health research organizations and companies, managed care organizations, healthcare provider organizations and companies, and combinations thereof.
21. The pharmaceutical information control system of claim 19, wherein the plurality of entities comprises doctors' offices, affiliated pharmacies, unaffiliated pharmacies, hospitals, pharmaceutical companies, insurance companies, government agencies, health care informatics companies, health research organizations and companies, managed care organizations, healthcare provider organizations and companies, and combinations thereof.
22. The pharmaceutical information control system of claim 1, wherein an alert by the at least one program comprises notification of one of: an adverse medical reaction to a prescribed medication, incompatibility with a pre-existing prescribed medication(s), a prescribed medication already filled, an inability to fill a prescribed medication, and fulfillment of a similar prescribed medication.
23. The pharmaceutical information control system of claim 22, wherein any one of the plurality of entities generate one or more reports after the alert is issued, and wherein the one or more reports are transmitted via the computer network to at least one of the plurality of entities.
24. The pharmaceutical information control system of claim 1, wherein the medication history comprises the prescription medication purchaser's name, address, phone number, age, adverse reactions, dosages, prescription history, and combinations thereof.
25. The pharmaceutical information control system of claim 1, wherein the pharmaceutical transactions comprise requesting one or more prescription medications, requesting a specific medication history, requesting prescription history of specific doctors or doctors' offices, requesting verification of prescription history of a specific prescription medication purchaser, requesting prescription history of a specific prescription medication, requesting prescription history of a particular geographical area, and combinations thereof.
26. The pharmaceutical information control system of claim 4, wherein any one of the plurality of entities generate one or more reports in response to receiving the alert, and wherein the one or more reports are transmitted via the computer network to at least one of the plurality of entities.
| 5737539 | April 7, 1998 | Edelson et al. |
| 5790409 | August 4, 1998 | Fedor et al. |
| 6421650 | July 16, 2002 | Goetz |
| 6687676 | February 3, 2004 | Denny |
| 6859780 | February 22, 2005 | Cunningham |
| 7426475 | September 16, 2008 | Tangellapally |
| 20020042723 | April 11, 2002 | Rice et al. |
| 20020042725 | April 11, 2002 | Mayaud |
| 20020052760 | May 2, 2002 | Munoz et al. |
| 20030050802 | March 13, 2003 | Jay et al. |
| 20030074225 | April 17, 2003 | Borsand et al. |
- Stallings et al, Business Data Communications, 1994, Prentice-Hall, Inc.second edition, pp. 457-469.
- Notice of Allowance for U.S. Appl. No. 10/803,259, dated Feb. 18, 2011, USPTO, Alexandria, VA, USA.
- Jacob S. Mattis, Supplemental Response to Advisory Action and Final Office Action for U.S. Appl. No. 10/803,259, dated Dec. 10, 2010, Houston, TX, USA.
- Jacob S. Mattis, Response to Advisory Action and Final Office Action for U.S. Appl. No. 10/803,259, dated Jun. 21, 2010, Houston, TX, USA.
- Advisory Action for U.S. Appl. No. 10/803,259, dated Apr. 9, 2010, USPTO, Alexandria, VA, USA.
- Jacob S. Mattis, Response to Final Office Action for U.S. Appl. No. 10/803,259, dated Mar. 22, 2010, Houston, TX, USA.
- Final Office Action for U.S. Appl. No. 10/803,259, dated Apr. 9, 2010, USPTO, Alexandria, VA, USA.
- Jacob S. Mattis, Response to Non-Final Office Action for U.S. Appl. No. 10/803,259, dated Oct. 30, 2009, Houston, TX, USA.
- Non-Final Office Action for U.S. Appl. No. 10/803,259, dated Jul. 30, 2009, USPTO, Alexandria, VA, USA.
- Interview Summary for U.S. Appl. No. 10/803,259, dated Jun. 4, 2009, USPTO, Alexandria, VA, USA.
- Jacob S. Mattis, Response to Final Office Action for U.S. Appl. No. 10/803,259, dated Jun. 3, 2009, Houston, TX, USA.
- Advisory Action for U.S. Appl. No. 10/803,259, dated May 14, 2009, USPTO, Alexandria, VA, USA.
- Jacob S. Mattis, Response to Final Office Action for U.S. Appl. No. 10/803,259, dated May 4, 2009, Houston, TX, USA.
- Final Office Action for U.S. Appl. N o. 10/803,259, dated Mar. 3, 2009, USPTO, Alexandria, VA, USA.
- William E. Johnson, Jr., Response to Non-Final Office Action for U.S. Appl. No. 10/803,259, dated Nov. 17, 2008, Houston, TX, USA.
- Non-Final Office Action for U.S. Appl. No. 10/803,259, dated Jul. 30, 2009 USPTO, Alexandria, VA, USA.
- William E. Johnson, Jr., Response to Advisory Action and Final Office Action for U.S. Appl. No. 10/803,259, dated Jun. 20, 2008, Houston, TX, USA.
- Advisory Action for U.S. Appl. No. 10/803,259, dated Jun. 9, 2008, USPTO, Alexandria, VA, USA.
- Final Office Action for U.S. Appl. No. 10/803,259, dated Feb. 22, 2008, USPTO, Alexandria, VA, USA.
- William E. Johnson, Jr., Response to Non-Final Office Action for U.S. Appl. No. 10/803,259, dated Dec. 26, 2007, Houston, TX, USA.
- Non-Final Office Action for U.S. Appl. No. 10/803,259, dated Sep. 26, 2007, USPTO, Alexandria, VA, USA.
- Notice of Allowance for U.S. Appl. No. 13/135,151, dated May 15, 2012, USPTO, Alexandria, VA, USA.
- Granted Terminal Disclaimer for U.S. Appl. No. 13/135,151 filed by Guy E. Matthews, Feb. 3, 2012, USPTO, Alexandria, VA, USA.
- Non-Final Office Action for U.S. Appl. No. 13/135,151, dated Oct. 3, 2011, USPTO, Alexandria, VA, USA.
Type: Grant
Filed: Jul 10, 2014
Date of Patent: Sep 4, 2018
Inventors: Jeffery Anon (Houston, TX), Jesse J. Bornfreund (Houston, TX), Ralph B. Lilly (Washington, TX)
Primary Examiner: Jeffrey Carlson
Application Number: 14/328,363
International Classification: G06Q 10/00 (20120101); G06Q 50/24 (20120101); G16H 10/00 (20180101); G16H 10/60 (20180101); G16H 80/00 (20180101);
