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.
|
0. 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.
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.
0. 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.
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.
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.
0. 2. The pharmaceutical information control system of
3. The pharmaceutical information control system of
0. 5. The pharmaceutical information control system of
6. The pharmaceutical information control system of
0. 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.
0. 10. The pharmaceutical information control system of claim 8, further comprising a computer network in communication with the at least one entity database.
0. 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.
0. 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.
0. 13. The pharmaceutical information control system of claim 8, wherein the at least one program is software, hardware, and combinations thereof.
0. 14. The pharmaceutical information control system of claim 8, wherein the data transfer device comprises an information access filter.
0. 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.
0. 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.
0. 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.
0. 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.
0. 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.
0. 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.
0. 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.
0. 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.
0. 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.
0. 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.
0. 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.
|
|||||||||||||||||
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.
Anon, Jeffery, Bornfreund, Jesse J., Lilly, Ralph B.
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 5737539, | Oct 28 1994 | CYBEAR, INC | Prescription creation system |
| 5790409, | Jan 25 1993 | AutoMed Technologies, Inc | Inventory monitoring and dispensing system for medical items |
| 6421650, | Mar 04 1998 | Goetech LLC | Medication monitoring system and apparatus |
| 6687676, | Sep 21 1999 | Nevoca, Com, Inc. | Prescription verification system |
| 6859780, | Nov 13 1995 | Trialcard Incorporated | Method and system for dispensing, tracking and managing pharmaceutical products |
| 7426475, | Mar 21 2000 | Secure electronic healthcare information management process and system | |
| 20020042723, | |||
| 20020042725, | |||
| 20020052760, | |||
| 20030050802, | |||
| 20030074225, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Date | Maintenance Fee Events |
| Jan 07 2020 | M2552: Payment of Maintenance Fee, 8th Yr, Small Entity. |
| Feb 26 2024 | REM: Maintenance Fee Reminder Mailed. |
| Aug 12 2024 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
| Date | Maintenance Schedule |
| Sep 04 2021 | 4 years fee payment window open |
| Mar 04 2022 | 6 months grace period start (w surcharge) |
| Sep 04 2022 | patent expiry (for year 4) |
| Sep 04 2024 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Sep 04 2025 | 8 years fee payment window open |
| Mar 04 2026 | 6 months grace period start (w surcharge) |
| Sep 04 2026 | patent expiry (for year 8) |
| Sep 04 2028 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Sep 04 2029 | 12 years fee payment window open |
| Mar 04 2030 | 6 months grace period start (w surcharge) |
| Sep 04 2030 | patent expiry (for year 12) |
| Sep 04 2032 | 2 years to revive unintentionally abandoned end. (for year 12) |