Embodiments of the present invention relate generally to electronic messages, and more particularly, to methods, apparatuses, and computer program products for generating alternative evaluation messages, facilitating selection thereof, and facilitating approval by a verification system.
Electronic messages are frequently transmitted and routed according to an identifier in the message. A processing system may therefore route the message as directed, await a response, and forward or route the response message to the message originator or requestor. However, in certain examples, different information to be included in the message response may be obtained from different evaluation systems, but the message router may not have the necessary routing information available to obtain the different information. In such examples, the requesting system may not be able to obtain the different information or may not be configured to poll the different evaluation systems.
Methods, apparatuses, and computer program products are therefore provided generating alternative evaluation messages, facilitating selection thereof, and facilitating approval by a verification system. An apparatus is provided, including at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the processor, cause the apparatus to at least parse an electronic message received from a requesting computer to determine a first evaluation system, and a verification indication, and generate and cause transmission of a first evaluation message to at least the first evaluation system. The at least one memory and the computer program code are further configured to, with the processor, generate and cause transmission of at least one alternative evaluation message, wherein at least one of (a) the at least one alternative evaluation message comprises at least a second product identifier, or (b) the at least one alternative evaluation message is transmitted to a second evaluation system.
In response to receiving a first evaluation message response and at least one alternative evaluation message response, cause transmission of the first evaluation message response and the at least one alternative evaluation message response to the requesting computer. The at least one memory and the computer program code are further configured to, with the processor, receive an indication of a selection of an alternative evaluation message response, modify the electronic message to reflect the selected alternative evaluation message response, and cause transmission of the modified electronic message to a verification system identified by the routing indication.
The first evaluation message response and the at least one alternative evaluation message response is caused to be transmitted to the requesting computer in real-time or near real-time relative to receiving the electronic message from the requesting computer.
In certain embodiments, generating the at least one alternative evaluation message comprises determining the second product identifier by identifying a formulary alternative to a product identified by the first product identifier. The first evaluation system may be associated with a prescription benefit plan and the second evaluation system is associated with a cash price.
The at least one memory and the computer program code configured to, with the processor, cause the apparatus to at least cause display of the at least first evaluation message response and the alternative evaluation message response via the requesting computer. The at least one of the first evaluation message response or the at least one alternative evaluation message response comprises deductible stage information. The at least one memory and the computer program code are configured to, with the processor, cause the apparatus to at least receive a response from the verification system indicating approval, and cause transmission of the response to the requesting computer.
A method is provided, including parsing an electronic message received from a requesting computer to determine a first evaluation system, and a verification indication, generating and cause transmission of a first evaluation message to at least the first evaluation system, and generating and cause transmission of at least one alternative evaluation message, wherein at least one of (a) the at least one alternative evaluation message comprises at least a second product identifier, or (b) the at least one alternative evaluation message is transmitted to a second evaluation system. The method further includes, in response to receiving a first evaluation message response and at least one alternative evaluation message response, causing transmission of the first evaluation message response and the at least one alternative evaluation message response to the requesting computer. The method further includes receiving an indication of a selection of an alternative evaluation message response, modifying the electronic message to reflect the selected alternative evaluation message response, and causing transmission of the modified electronic message to a verification system identified by the routing indication. The method may further include causing display of the at least first evaluation message response and the alternative evaluation message response via the requesting computer, receiving a response from the verification system indicating approval, and causing transmission of the response to the requesting computer.
A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising program code instructions to parse an electronic message received from a requesting computer to determine a first evaluation system, and a verification indication, and to generate and cause transmission of a first evaluation message to at least the first evaluation system. The computer-executable program code instructions further comprise program code instructions to generate and cause transmission of at least one alternative evaluation message, wherein at least one of (a) the at least one alternative evaluation message comprises at least a second product identifier, or (b) the at least one alternative evaluation message is transmitted to a second evaluation system. In response to receiving a first evaluation message response and at least one alternative evaluation message response, the computer-executable program code instructions further comprise program code instructions to cause transmission of the first evaluation message response and the at least one alternative evaluation message response to the requesting computer. The computer-executable program code instructions further comprise program code instructions to receive an indication of a selection of an alternative evaluation message response, modify the electronic message to reflect the selected alternative evaluation message response, and cause transmission of the modified electronic message to a verification system identified by the routing indication. The computer-executable program code instructions further comprise program code instructions to cause display of the at least first evaluation message response and the alternative evaluation message response via the requesting computer.
An apparatus is provided, including means for parsing an electronic message received from a requesting computer to determine a first evaluation system, and a verification indication, means for generating and cause transmission of a first evaluation message to at least the first evaluation system, and means generating and cause transmission of at least one alternative evaluation message, wherein at least one of (a) the at least one alternative evaluation message comprises at least a second product identifier, or (b) the at least one alternative evaluation message is transmitted to a second evaluation system. The apparatus further includes means for, in response to receiving a first evaluation message response and at least one alternative evaluation message response, causing transmission of the first evaluation message response and the at least one alternative evaluation message response to the requesting computer. The apparatus further includes means for receiving an indication of a selection of an alternative evaluation message response, means for modifying the electronic message to reflect the selected alternative evaluation message response, and means for causing transmission of the modified electronic message to a verification system identified by the routing indication. The apparatus further includes means for causing display of the at least first evaluation message response and the alternative evaluation message response via the requesting computer, means for receiving a response from the verification system indicating approval, and means for causing transmission of the response to the requesting computer.
The above summary is provided merely for purposes of summarizing some example embodiments of the invention so as to provide a basic understanding of some aspects of the invention. Accordingly, it will be appreciated that the above described example embodiments are merely examples and should not be construed to narrow the scope or spirit of the disclosure in any way. It will be appreciated that the scope of the disclosure encompasses many potential embodiments, some of which will be further described below, in addition to those here summarized.
Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
Some embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, various embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout.
As used herein, where a computing device is described to receive data from another computing device, it will be appreciated that the data may be received directly from the other computing device and/or may be received indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, and/or the like. Similarly, where a computing device is described herein to transmit data to another computing device, it will be appreciated that the data may be sent directly to the other computing device or may be sent to the other computing device via one or more interlinking computing devices, such as, for example, one or more servers, relays, routers, network access points, and/or the like.
Pharmacists have limited ability to determine the cost of the medication and costs associated with the patient's formulary alternatives without having to generate multiple billing transactions to the patient's insurance carrier or a service provider that indicates cash pricing. This process creates workflow inefficiencies for pharmacies which could lead to delays in dispensing medications, and additionally leads to unnecessary consumption of processing, memory, and network resources to process and route such requests throughout a network, reconcile responses, and route the responses accordingly. Such multiple requests can therefore bog down a system and cause performance issues.
When processing a refill for a patient that requires provider approval, the benefits for the patient may have changed which could further lead to higher cost of a medication intended to be dispensed. Even if the benefit plan is unchanged, a patient could be at a different stage in their deductible, which could further impact prescription drug pricing. For example, early in the plan year, a patient may not have met their deductible, but later in the plan year the patient may meet the deductible. Various medications can be moved on or off formulary for a particular plan, and/or change year to year even within the same plan.
In current systems, pharmacists or other users of a requesting computer often initiate a refill request when a patient has utilized all available refills but is requesting additional refills. The refill request is routed to a prescriber computer so that the prescriber can approve the refill request and the patient can obtain additional refills. In current systems, the pharmacist does not have insight to medication pricing until a later time when the refill is approved, then further processed by the pharmacy computer to initiate a prescription claim and to fill the order. When a response is received from the prescription benefit plan, the pharmacist is informed of pricing information, but at this time the prescribing computer and prescriber (physician and/or the like) has already processed and approved the refill request. To research pricing of medication and/or pricing alternatives, the pharmacist may have to submit the multiple inquiries as described above, wasting the processing, memory and network resources.
Example embodiments improve upon such systems by checking for alterative medications, and/or different pricing schemas for the same or alternative medications before the refill request is transmitted to the prescriber. In some embodiments, the pharmacy may opt in for such alternative inquires for all refill requests by default, or a pharmacist or other user of the requesting computer may indicate a request for alternative inquiries on a case-by-case basis. In any event, a service provider computer, upon receiving the refill request, performs a check for alternative medication such as one in the same therapeutic class, a generic or brand alternative, and/or the like. U.S. patent application Ser. No. 15/085,166, filed Mar. 30, 2016, and titled “Alternative Therapy Identification System,” describes identifying alternative therapies, such as by using alternative therapy tables, and is hereby incorporated by reference in its entirety.
Additionally or alternatively, the service provider computer may determine a cash price for the medication or alternative medication and/or via a prescription benefit plan (e.g., commercial insurance plan and/or government sponsored plan) in which the patient is enrolled and is eligible for coverage. The service provider computer may perform such pricing inquiries with a cash discount card, and/or different plan or payer than with which the patient previously purchased the prescription and/or different plan or payer than which the patient typically utilizes or that the pharmacy has on record. U.S. patent applicant Ser. No. 16/867,286, filed May 5, 2020 and titled, “Method, Apparatus, And Computer Program Product For Constructing Electronic Message Responses Dependent Upon Historical Information,” and U.S. Patent Publication No. 2022/0076797, filed Sep. 4, 2020, and titled, “Method, Apparatus, And Computer Program Product For Performing An Alternative Evaluation Procedure In Response To An Electronic Message.” describe various methods for obtaining different out-of-pockets costs of prescription drugs for patients and are hereby incorporated by reference in their entireties.
The service provider computer returns a response, optionally including various alternatives for the medication and pricing, and the pharmacist may optionally select an alternative medication, cash pricing system, and/or payer such that the refill request is modified and then forwarded to the prescriber for approval. If an alternative medication is selected, the prescriber may recognize the alternative medication as an equivalent therapy and approve the refill request similarly as though the refill request was for the same prescription. The approved refill request can then be returned to the pharmacy computer and may be further routed as a prescription claim and processed for filling the prescription at the pharmacy.
In certain embodiments, a requesting computer 104 may be associated with a pharmacy or pharmacy network to facilitate the filling of prescriptions, transmitting prescription claims, prescription inquiries, and/or prescription refill requests to a service provider computer 106, and/or the like. Further, it will be appreciated that the requesting computer 104 may be implemented as a pharmacy computer, and that references herein to a “requesting computer” may be interchanged with references to a “pharmacy computer.”
The requesting computer 104 may therefore facilitate the submission of messages, such as prescription refill requests, made by pharmacists on behalf of patients or consumers, and the communication of information associated with such messages (e.g., prescription transactions) to the service provider computer 106. In certain example embodiments, the requesting computer 104 may be a point of sale device associated with a pharmacy. The execution of the computer-implemented instructions by the requesting computer 104 may form a special purpose computer or other particular machine that is operable to facilitate the submission of pharmacy transaction requests made by patients, pharmacists, and/or the like, and the communication of information associated therewith to a service provider computer 106.
The service provider computer 106 may include, but is not limited to, a processor-driven device that is configured for receiving, processing, and responding to messages (e.g., prescription transactions) from the requesting computer 104. The service provider computer 106 may process such messages by identifying alternative medications or therapy, if any, and/or by identifying alternative evaluation systems (e.g., cash systems and/or other payers). The service provider computer 106 may therefore perform any operations to determine pricing, or best pricing, of certain medication including alternative medication, for a patient.
The service provider computer 106 may route prescription inquiries to various evaluation systems 108, described in further detail below to obtain responses regarding pricing. In certain embodiments, the service provider computer 106 may receive responses from evaluation systems 108, and return responses, such as those indicating a patient out-of-pocket cost of a prescription drug or alternative to a requesting computer 104 from which an associated refill request originated. Accordingly, the service provider computer 106 may be operable to facilitate the receipt, routing, and/or processing of healthcare transactions such as prescription refill requests, prescription transactions, prescription claims, and/or associated responses amongst various components and/or subsystems such as, but not limited to, those depicted in
In certain exemplary embodiments, the service provider computer 106 may be configured as or may comprise a switch or router that evaluates, modifies, reformats, generates, and/or routes transactions such as healthcare transactions and prescription transactions. For example, the service provider computer 106 may route transactions communicated from the requesting computer 104 to an evaluation system 108 configured to return information regarding the transactions, and/or the service provider computer 106 may poll an evaluation system accordingly. In certain embodiments, the service provider computer 106 may reformat transactions, such as refill request, into another form of transaction and modify the recipient information of the reformatted transaction before routing the reformatted transaction to another party, such as evaluation system 108 and/or verification system 109 (e.g., a prescriber computer, described in further detail below, and configured to verify, approve or reject refill requests). The service provider computer 106 may also optionally apply edits to at least some of the messages and/or transactions, and/or construct a separate message response for messages received via the switch.
In certain embodiments, an evaluation system 108 may be associated with a cash pricing system. The evaluation system 108 may comprise a computer system that receives, adjudicates, or otherwise processes a prescription claim on behalf of the payer associated with an evaluation system 108, such as a cash pricing system.
Cash pricing systems provide discounted prescription drugs to patients when the patient purchases a prescription at a particular pharmacy with which the cash pricing system has an agreement. In some instances, a pharmacy works in agreement with a cash pricing system to offer the cash price and/or discount on behalf of the cash pricing system. A pharmacy may agree to cooperate with the cash pricing system to keep up with competition in a price-competitive market. The pharmacy may receive a dispense fee for dispensing the drug under the cash pricing system, such that the pharmacy's revenue for a particular transaction may be the dispense fee, less the cost of ingredients (e.g., the drug), less any applicable administration fees.
In some instances, cash pricing systems enable a patient to present a cash discount card and to obtain a medication at a lower cost than what would otherwise be obtainable by submitting a prescription claim to a pharmacy benefits manager (PBM), or other insurance provider, for the same medication.
Additionally or alternatively, an evaluation system 108 may be associated with a payer of prescription benefits and/or prescription benefit manager, and may be associated with a commercial prescription insurance plan and/or government sponsored plan.
Accordingly, references herein to an “evaluation system” may be interchanged with the term “cash pricing system,” and/or “prescription benefit manager computer,” according to certain embodiments.
The service provider computer 106 may transmit responses from an evaluation system 108 regarding a prescription inquiry, to the requesting computer 104. For example, the service provider computer 106 may notify the requesting computer 104 of out of pocket costs to be paid by the patient for various prescription drugs, such as an initially prescribed drug and/or alternative prescription, and certain embodiments may provide costs under different evaluation systems, such as a cash pricing system and/or prescription benefit plan. In this regard, a message or other notification may be appended to or included in the response transmitted to the requesting computer 104 indicating the evaluation system 108 associated with a respective medication and/or price. Any number of responses may be provided to the requesting computer 104 in association with a received refill request, and/or aggregated or compiled into a response to provide to the requesting computer 104. Accordingly, the service provider computer 106 may reformat the refill request to include the details of such responses, and transmit the reformatted refill request to the requesting computer 104. A user of the requesting computer 104, such as a pharmacist, may make a selection of a particular prescription drug and/or evaluation system (e.g., cash pricing system and/or other payer), and the service provider computer 106 may further modify the refill request before forwarding the refill request to a verification system 109.
The verification system 109 may be a prescriber computer, such as one in association with a physician, hospital, and/or other medical provider. The verification system 109 receives refill requests from the service provider computer 106, and enables a user to indicate to approve or reject the refill request.
The historical data source 110 may comprise any computing device configured to provide historical information and/or data, such as but not limited to the data received in various transactions and from various evaluation systems 108. The historical information may therefore comprise historical cash pricing information as provided under various cash pricing systems and/or historical out-of-pocket costs for prescription drugs under various prescription benefit plans. For example, the historical data source 110 may be a system or database configured to track pricing offered by various evaluation systems.
According to certain embodiments, the historical data source 110 may be maintained or operated by various requesting computers 104, such as in instances in which a pharmacy tracks historical data or historical pricing of cash transactions occurring at the pharmacy. Additionally or alternatively, the historical data source 110 may be maintained or operated by the service provider computer 106, as it functions as a switch for routing and processing certain transactions submitted by various requesting computers 104.
Referring now to
Apparatus 200 may at least partially or wholly embody or be embodied by any of the requesting computer 104, service provider computer 106, and/or evaluation system 108. Apparatus 200 may therefore implement any of the requesting computer 104, service provider computer 106, and/or evaluation system 108, in accordance with some example embodiments, or may be implemented as a distributed system that includes any of the requesting computer 104, service provider computer 106, evaluation system 108, and/or associated network(s).
It should be noted that the components, devices, and elements illustrated in and described with respect to
Continuing with
In some example embodiments, the processing circuitry 210 may include a processor 212, and in some embodiments, such as that illustrated in
The processor 212 may be embodied in a number of different ways. For example, the processor 212 may be embodied as various processing means such as one or more of a microprocessor or other processing element, a coprocessor, a controller, or various other computing or processing devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), or the like. Although illustrated as a single processor, it will be appreciated that the processor 212 may comprise a plurality of processors. The plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of apparatus 200 as described herein. The plurality of processors may be embodied on a single computing device or distributed across a plurality of computing devices collectively configured to function as requesting computer 104, service provider computer 106, evaluation system 108, and/or apparatus 200. In some example embodiments, the processor 212 may be configured to execute instructions stored in the memory 214 or otherwise accessible to the processor 212. As such, whether configured by hardware or by a combination of hardware and software, the processor 212 may represent an entity (e.g., physically embodied in circuitry-in the form of processing circuitry 210) capable of performing operations according to embodiments of the present invention while configured accordingly. Thus, for example, when the processor 212 is embodied as an ASIC, FPGA, or the like, the processor 212 may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor 212 is embodied as an executor of software instructions, the instructions may specifically configure the processor 212 to perform one or more operations described herein.
In some example embodiments, the memory 214 may include one or more non-transitory memory devices such as, for example, volatile and/or non-volatile memory that may be either fixed or removable. In this regard, the memory 214 may comprise a non-transitory computer-readable storage medium. It will be appreciated that while the memory 214 is illustrated as a single memory, the memory 214 may comprise a plurality of memories. The plurality of memories may be embodied on a single computing device or may be distributed across a plurality of computing devices. The memory 214 may be configured to store information, data, applications, computer program code, instructions and/or the like for enabling apparatus 200 to carry out various functions in accordance with one or more example embodiments. For example, when apparatus 200 is implemented as service provider computer 106, memory 214 may be configured to store computer program code for performing corresponding functions thereof, as described herein according to example embodiments.
Still further, memory 214 may be configured to store routing tables, that facilitate determining the destination of communications received from a requesting computer 104, and/or evaluation system 108. Memory 214 may further include reconciliation tables for tracking the healthcare transactions, such as refill requests, received from the requesting computer 104, and reconciling them with responses received from evaluation system 108. The memory 214 may further comprise a database, such as historical data source 110, comprising cash prices of particular medications, and/or alternative therapy tables 112, comprising alternative medications by prescription identifier (e.g., national drug code (NDC)). Still further, according to certain embodiments, the memory 214 may be modified as described herein, to reformat refill requests, prescription claims and/or prescription transactions with additional information received, determined and/or generated according to example embodiments.
The memory 214 may be further configured to buffer input data for processing by the processor 212. Additionally or alternatively, the memory 214 may be configured to store instructions for execution by the processor 212. In some embodiments, the memory 214 may include one or more databases that may store a variety of files, content, or data sets. Among the contents of the memory 214, applications may be stored for execution by the processor 212 to carry out the functionality associated with each respective application. In some cases, the memory 214 may be in communication with one or more of the processor 212, user interface 216, and/or communication interface 218, for passing information among components of apparatus 200.
The optional user interface 216 may be in communication with the processing circuitry 210 to receive an indication of a user input at the user interface 216 and/or to provide an audible, visual, mechanical, or other output to the user. As such, the user interface 216 may include, for example, a keyboard, a mouse, a display, a touch screen display, a microphone, a speaker, and/or other input/output mechanisms. As such, in embodiments in which apparatus 200 is implemented as the requesting computer 104, the user interface 216 may, in some example embodiments, provide means for user entry of payer information, details relating to the dispensing of a prescription, request for a refill, and/or the like. The user interface 216 may be further configured to display or provide evaluation responses and patient pay amounts of prescription medications, such as when apparatus 200 is implemented as a requesting computer 104. The user interface 216 of verification system 109 may be configured for display of a refill request (including a modified refill request) so that a prescriber or other user may approve or reject a refill request. In some example embodiments, aspects of user interface 216 may be limited or the user interface 216 may not be present.
The communication interface 218 may include one or more interface mechanisms for enabling communication with other devices and/or networks. In some cases, the communication interface 218 may be any means such as a device or circuitry embodied in either hardware, or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the processing circuitry 210. By way of example, the communication interface 218 may be configured to enable communication amongst any of requesting computer 104, service provider computer 106, evaluation system 108, verification system 109, historical data source 110, alternative therapy tables 112, and/or apparatus 200 over a network. Accordingly, the communication interface 218 may, for example, include supporting hardware and/or software for enabling wireless and/or wireline communications via cable, digital subscriber line (DSL), universal serial bus (USB), Ethernet, or other methods.
A network, such as the network in which any of the systems of
According to certain embodiments, the service provider computer 106 receives a patient's benefit coverage inquiry that is generated by a prescriber computer, such as via an electronic health record (EHR) system, then obtains a response from the patient's PBM or other payer that facilities their prescription benefit coverage, and/or the service provider computer's estimation engine will return an estimated range that a patient can expect to pay for their prescription. The service provider computer 106 may also return a flag to the prescriber indicating that the prescription can be submitted to the pharmacy (such as when the EHR/Health System and the pharmacy is contracted to be supported by the service provider computer. The service provider computer 106 will receive a prescription order that is generated by the prescriber or the prescriber's staff via an EHR system or Health system using HL7 (FHIR) standards or a proprietary transaction. The service provider computer 106 will perform a validation check to ensure that all required fills are populated.
If a field validation is triggered and indicates errors, the service provider computer 106 will return a response to the EHR or Health System indicating what required data elements are missing and request that they are populated prior to the prescription order being sent to the pharmacy. The service provider computer 106 may therefore require that the data is added before the prescription order is reprocessed, and re-validated the prescription order
Once validated, the service provider computer 106 may then convert the prescription order into National Council for Prescription Drug Programs (NCPDP) SCRIPT standard for processing.
The service provider computer 106 will also combine the benefit response with the prescription order so that the transmission not only includes the clinical details for the prescription, but it also includes the patient's pharmacy benefit information that is displayed to the prescriber or the prescriber's staff. The service provider computer 106 will then review the order to determine the ultimate recipient of the prescription order. The service provider computer 106 will facilitate all routing and determine the ultimate delivery of the prescription order based upon the identifier (NPI or NCPDP ID) of the pharmacy that will dispense. The service provider computer will check configuration tables and databases that map the pharmacy identifier that will route the prescription order to the to a specific URL that is configured at the pharmacy chain, pharmacy software vendor, outpatient pharmacy, buying group, pharmacy service administrative organization PSAO or independent pharmacy level, then transmit the order to the identified destination. The pharmacy will then process the prescription order and it is adjudicated to determine the patient's financial responsibility.
In some instances a patient may obtain refills. In some instances, a patient may seek refills, but no refills are available or all initially available have already been filled. As reflected in
Accordingly, as shown by operation 300 of
The electronic message (e.g., refill request) may be received from the requesting computer 104, such as following entry by a pharmacist, or other user, of data relating to a prescription drug attempting to be refilled, insurance information relating to the first evaluation system, indication of a cash pricing system relating to the first evaluation system, and/or a prescriber that prescribed the prior prescription. The requesting computer 104 may store any information from a prior prescription transaction, such as information described herein, to populate the refill request. In this regard, the message (e.g., refill request) may include a prescription claim entered by a healthcare provider, such as a pharmacist, when a patient seeks additional refills to be approved by their physician (when no available refills remain). The message (e.g., refill request) may be received at the service provider computer 106 for further processing as described below.
As shown by operation 304, apparatus 200 may include means, such as processor 212, memory 214, communication interface 218, and/or the like, for generating and causing transmission of a first evaluation message to at least the first evaluation system. In this regard, the service provider computer 106 may initiate a first evaluation message (e.g., prescription benefit inquiry) toward the first evaluation system, such as an evaluation system 108 identified by the patient's insurance, preferred cash pricing system, and/or the like, which may be identified by a PCN and/or BIN, for example. Said differently, the service provider computer 106 may poll a certain evaluation system 108 identified based on a PCN, BIN, and/or the like.
In this regard, in certain embodiments, polling the first evaluation system or transmitting a first evaluation message may include, or may result in, receiving, from the evaluation system, a first evaluation message regarding the transaction. In certain embodiments, the first evaluation message may include at least a patient pay amount for the prescription drug. The switch of the service provider computer 106 may receive a data feed of responses from various evaluation systems 108 (e.g., PBM's associated with commercial insurance payers, cash pricing systems and/or other payers). An identifier included in a message response may be associated with a transmitted message to the evaluation system such that the service provider computer 106 reconciles a response with the associated request (e.g. evaluation message).
As shown by operation 308, apparatus 200 may include means, such as processor 212, memory 214, communication interface 218, and/or the like, for generating and causing transmission of at least one alternative evaluation message, wherein at least one of (a) the at least one alternative evaluation message comprises at least a second product identifier, or (b) the at least one alternative evaluation message is transmitted to a second evaluation system.
Generating the alternative evaluation message may include determining an alternative, or second product identifier, associated with the prescription drug indicated by the electronic message. Accordingly, the second product identifier may identify an alternative drug or formulary alternative to a product identified by the first product identifier, such as an alternative drug identified in an alternative therapy table 112, and/or by any process described in U.S. patent application Ser. No. 15/085,166.
Additionally or alternatively, an alternative evaluation message may indicate a different evaluation system than the first evaluation system. For example, if the first evaluation system is a PBM associated with a benefit plan, the second evaluation system may be a cash pricing system. If the first evaluation system is a cash pricing system, the second evaluation system may be a PBM associated with a benefit plan. U.S. patent application Ser. No. 16/867,286 and U.S. Patent Publication No. 2022/0076797 provide examples of methods for determining cash prices and/or patient pay amounts under prescription benefit plans, but it will be appreciated that any such method for determining pricing may be utilized. In certain embodiments, historical data source 110 may be utilized to determine or estimate pricing.
One or more prescription benefit inquiries may then be transmitted in the form of an alternative evaluation message. In certain examples, if an alternative product, such as an alternative medication, is identified by a second product identifier, in some examples multiple alternative evaluation messages may be generated for different evaluation systems (such as a first and/or second evaluation system). Any number of alternative evaluation messages may be generated and transmitted, such as in attempt to identify the best value prescription drug for the patient.
As shown by operation 310, apparatus 200 may include means, such as processor 212, memory 214, communication interface 218, and/or the like, for receiving a first evaluation message response and at least one alternative evaluation message response. Responses associated with any or all of the messages caused to be transmitted in operation 308 may be received via the communication interface 218 and reconciled with their respective electronic messages. For example, an identifier included in a request transmitted with respect to operation 308 may be included in a response such that the service provider computer 106 reconciles the requests and responses, such as with routing table, and determines a requesting computer 104 to which to route responses.
In certain embodiments, a first evaluation message response may reflect a patient pay amount for a refill of the previously prescribed medication, and in certain embodiments may include any combination of a price based on insurance coverage, rebates, cash pricing, and/or the like. The alternative evaluation message response may reflect a patient pay amount according to the second product identifier or the at least one alternative evaluation system, and may include any combination of a price based on insurance coverage, rebates, cash pricing, and/or the like.
As shown by operation 312, apparatus 200 may include means, such as processor 212, memory 214, user interface 216, communication interface 218, and/or the like, for in response to receiving a first evaluation message response and at least one alternative evaluation message response, causing transmission of the first evaluation message response and the at least one alternative evaluation message response to the requesting computer. In this regard, any number of responses, including alternative evaluation message responses may be provided to the requesting computer 104.
Example embodiments may cause the communication and display of information from the various responses, such as with computer program code to direct the user interface 216 of the requesting computer 104. A user such as the pharmacist may therefore review different options for alternative therapies and/or evaluation systems (e.g., cash or PBM) and corresponding patient pay amounts. In some examples a user such as a pharmacist may discuss options with a patient. In certain embodiments, the information transmitted and received may include further details such that a user can determine rationale for different pricing. For example, at least one of the first evaluation message response or the at least one alternative evaluation message response may include deductible stage information. This may indicate to the pharmacist and/or patient that a cost of medication under a plan has gone up due to the resetting of payments toward a deductible (such as in a calendar year since the patient last obtained the prescription), or down due a deductible being met. Various information may be provided that may assist the pharmacist and/or patient in understanding different options and corresponding prices.
In any event, the user, such as a pharmacist, may select an option for the patient that the user determines as the best price, or best option for the patient, which may not always necessarily be the best price, dependent on other factors such as the patient's progress toward a deductible in an insurance plan. It will be appreciated that the operations 304, 308, 310, 312 and 316 occur in real-time or near real-time relative to the receipt of the electronic message referenced in operation 300. Description of near real-time processing allows for short delays due to computer processing time. In any event, when a pharmacist is interacting with a user interface and considering a refill request for a patient, the pharmacist can view the alternative options and pricing information in real-time or near real-time relative to having initiated the refill request transmitted to the service provider computer 106, which is unconventional in prior systems. The facilitation of submission for approval is also unconventional in prior systems, and is described in further detail below.
As shown by operation 316, apparatus 200 may include means, such as processor 212, memory 214, user interface 216, communication interface 218, and/or the like, for receiving an indication of a selection of an alternative evaluation message response. In this regard, a user such as a pharmacist may select a desired option for the patient, via a user interface 216, and the selected option is returned to the service provider computer 106. It will be appreciated that in some scenarios, the user may select the first evaluation message, and a corresponding refill request may then be transmitted to the verification system 109.
In an event, in response to an indication of a selection of an alternative evaluation message, as shown by operation 320, apparatus 200 may include means, such as processor 212, memory 214, communication interface 218, and/or the like, for modifying the electronic message to reflect the selected alternative evaluation message. In this regard, the service provider computer 106 changes at least one of the product identifier identifying the prescription drug, or the evaluation system (e.g., cash payment and/or PBM) in the electronic message according to the selection made via the requesting computer 104, such as a pharmacy computer.
As shown by operation 324, apparatus 200 may include means, such as processor 212, memory 214, user interface 216, communication interface 218, and/or the like, for causing transmission of the modified electronic message to a verification system identified by the routing indication. In this regard, the modified electronic message is routed to the verification system 109 with which the electronic message was associated. The verification system 109 may be a prescriber computer associated with the prior prescription transaction. A message may therefore be transmitted and displayed to a physician or prescriber, prompting the prescriber to approve a refill request that may include an alternative medication. In a circumstance in which the medication is not changed, but the evaluation system (e.g., cash or PBM) is changed, the prescriber may be presented with an option to approve the refill request. In any event, the prescriber using the verification system 109 can verify or approve the refill request as modified by the service provider computer 106, and a response, such as a refill response, is returned to the service provider computer 106 and routed to the requesting computer 104. The prescriber may alternatively reject the refill response and optionally provide a rationale or explanation. As another option, if the prescriber denies the refill request, the prescriber may select or indicate a different prescription (e.g., newRX), such as a follow-up response and to close the loop if the prescriber doesn't agree with the alternative medication and/or want to prescribe a different prescription for the patient.
As shown by operation 328, apparatus 200 may include means, such as processor 212, memory 214, communication interface 218, and/or the like, for receiving a response, such as a refill response, from the verification system 109, and routing the response to the requesting computer 104. The refill response may indicate the refill is approved or verified. If approved or verified, the pharmacy may fill the prescription for the patient and further initiate transmission, via the service provider computer 106, to an evaluation system 108 or related adjudication computer upon the patient obtaining the prescription. In some scenarios, the prescriber using verification system 109 may reject the refill request (optionally with a rationale, explanation, and/or different prescription drug indicated), which may be routed via the service provider computer 106 to the requesting computer 104 for display to the pharmacist or other user. A new prescription by the prescriber may be coded as a newRX.
Example embodiments provided herein therefore provide a technical solution to a technical problem presented by requesting computers, such as pharmacy computer, not having direct access to prescription pricing information, nor being configured to obtain prescriber approval of a prescription refill. Enabling the pharmacy or pharmacist to initiate a request via the electronic message reduces the number of transactions a pharmacist would otherwise need to attempt, and possibly cancel, while attempting to find a best price for a prescription drug. Additionally or alternatively, current systems may not enable a pharmacist to request a refill approval from a prescriber for a prescription other than the medication prescribed. Example embodiments therefore improve upon such systems by facilitating a change to an electronic message, as directed by a pharmacist or other user of a requesting computer, and by facilitating the approval process with the verification system, such as a prescriber computer.
Example embodiments are further integrated into a practical application of systematically generating alternative evaluation message, to provide improved information to the patient and/or pharmacy. This application in the area of prescription claims and prescription drug pricing provides an improvement to the technology of automated prescription pricing inquiries, service provider computers, requesting computers such as pharmacy computers, and/or the like.
Without the advantages of the present disclosure, pharmacists may have to research other prescriptions and submit multiple prescription inquiries and/or transactions via the service provider computer. Accordingly, example embodiments improve the technology of automated prescription pricing inquiries and service provider computers by providing the improvement to the requesting computer and associated pharmacy. Additionally, based on the reduced or limited need to submit multiple prescription inquiries for the same prescription transaction, example embodiments reduce or limit the processing resources, network resources, and memory resources otherwise required to facilitate the processing, routing, and completion of the otherwise submitted multiple prescription inquiries for the same transaction that without the advantages of disclosed example embodiments, would need to be used to “test” the pricing schemas and identify a good price or best price.
Moreover, in addition to reducing the number of additional claims that may otherwise be submitted to test pricing under different cash pricing systems, example embodiments may further need to process transaction reversals, to indicate to certain evaluation systems that the transaction will not be processed under their system. Reversals require additional processing, network, and memory resources to be routed and processed, such that example embodiments further reduce the required processing and memory resources that would otherwise be expended on the facilitation, processing and routing of reversal transactions. The reduction in the utilization of such resources may be realized by the requesting computer 104, service provider computer 106, and/or evaluation system 108.
It will be appreciated that the figures are each provided as examples and should not be construed to narrow the scope or spirit of the disclosure in any way. In this regard, the scope of the disclosure encompasses many potential embodiments in addition to those illustrated and described herein. Numerous other configurations may also be used to implement embodiments of the present invention.
Accordingly, blocks of the flowchart support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowchart, and combinations of blocks in the flowchart, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.
Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Number | Name | Date | Kind |
---|---|---|---|
5012035 | Sartori et al. | Apr 1991 | A |
5173851 | Off et al. | Dec 1992 | A |
5595342 | McNair et al. | Jan 1997 | A |
5628530 | Thornton | May 1997 | A |
5726092 | Mathews et al. | Mar 1998 | A |
5757898 | Nishikawa | May 1998 | A |
5769228 | Wroblewski | Jun 1998 | A |
6012035 | Freeman et al. | Jan 2000 | A |
6111218 | Akers et al. | Aug 2000 | A |
6463462 | Smith et al. | Oct 2002 | B1 |
6595342 | Maritzen et al. | Jul 2003 | B1 |
6726092 | Goldberg et al. | Apr 2004 | B2 |
6757898 | Ilsen et al. | Jun 2004 | B1 |
6769228 | Mahar | Aug 2004 | B1 |
7155397 | Alexander et al. | Dec 2006 | B2 |
7192741 | Otte et al. | Mar 2007 | B2 |
7337129 | Lowry et al. | Feb 2008 | B1 |
7346768 | DiRienzo | Mar 2008 | B2 |
7409632 | DiRienzo | Aug 2008 | B1 |
7426476 | Munoz et al. | Sep 2008 | B2 |
7734483 | Smith et al. | Jun 2010 | B1 |
7783383 | Eliuk et al. | Aug 2010 | B2 |
7840424 | Wiley et al. | Nov 2010 | B2 |
7856364 | Wiley et al. | Dec 2010 | B1 |
7912741 | Pinsonneault | Mar 2011 | B1 |
7921021 | Newman | Apr 2011 | B1 |
8036913 | Pinsonneault et al. | Oct 2011 | B1 |
8036914 | Pinsonneault | Oct 2011 | B1 |
8036918 | Pinsonneault | Oct 2011 | B1 |
8050943 | Wiley et al. | Nov 2011 | B1 |
8060379 | Pinsonneault et al. | Nov 2011 | B1 |
8126743 | Wilk | Feb 2012 | B1 |
8326773 | Bellamy | Dec 2012 | B1 |
8412537 | Fenton et al. | Apr 2013 | B1 |
8442847 | Shrivastava | May 2013 | B1 |
8489415 | Ringold | Jul 2013 | B1 |
8521557 | Ringold et al. | Aug 2013 | B1 |
8560340 | Ringold | Oct 2013 | B1 |
8645162 | Boerger et al. | Feb 2014 | B2 |
8671018 | Thomas et al. | Mar 2014 | B2 |
8712797 | Bezdek | Apr 2014 | B1 |
8738399 | Abou Nader et al. | May 2014 | B1 |
8786650 | Eller et al. | Jul 2014 | B1 |
8799018 | Rea et al. | Aug 2014 | B1 |
8984059 | Johnson | Mar 2015 | B2 |
9026507 | Shraim et al. | May 2015 | B2 |
9100793 | Johnson | Aug 2015 | B2 |
9171322 | Spievak et al. | Oct 2015 | B2 |
9356947 | Shraim et al. | May 2016 | B2 |
9760871 | Pourfallah et al. | Sep 2017 | B1 |
9786023 | Cohan et al. | Oct 2017 | B2 |
10109027 | Stack | Oct 2018 | B1 |
10157262 | Pinsonneault | Dec 2018 | B1 |
10331855 | Bratton et al. | Jun 2019 | B1 |
10417380 | Kaye et al. | Sep 2019 | B1 |
10489552 | Pinsonneault | Nov 2019 | B2 |
10496793 | Lawrence et al. | Dec 2019 | B1 |
10565656 | Pinsonneault et al. | Feb 2020 | B1 |
10606984 | Kaye et al. | Mar 2020 | B1 |
10616146 | Hopkins et al. | Apr 2020 | B1 |
10628797 | Shraim et al. | Apr 2020 | B2 |
10642812 | Hopkins et al. | May 2020 | B1 |
10713694 | Harris et al. | Jul 2020 | B1 |
10747848 | Guinan | Aug 2020 | B2 |
10778618 | Karnin et al. | Sep 2020 | B2 |
10862832 | Harris | Dec 2020 | B1 |
10924545 | Momchilov et al. | Feb 2021 | B2 |
10924585 | Harris et al. | Feb 2021 | B1 |
10929932 | Golden et al. | Feb 2021 | B1 |
10978198 | Pinsonneault | Apr 2021 | B1 |
10999224 | Frechen et al. | May 2021 | B1 |
11043293 | Salzbrenner | Jun 2021 | B1 |
11443835 | Gangaikondan-Iyer et al. | Sep 2022 | B1 |
11508471 | Anselmi | Nov 2022 | B1 |
20010029483 | Schultz et al. | Oct 2001 | A1 |
20010037216 | Oscar et al. | Nov 2001 | A1 |
20010039589 | Aho et al. | Nov 2001 | A1 |
20010056359 | Abreu | Dec 2001 | A1 |
20020002495 | Ullman | Jan 2002 | A1 |
20020004812 | Motoyama | Jan 2002 | A1 |
20020032582 | Feeney et al. | Mar 2002 | A1 |
20020032583 | Joao | Mar 2002 | A1 |
20020035484 | McCormick | Mar 2002 | A1 |
20020087583 | Morgan et al. | Jul 2002 | A1 |
20020111832 | Judge | Aug 2002 | A1 |
20020133379 | Lewis et al. | Sep 2002 | A1 |
20020143579 | Docherty et al. | Oct 2002 | A1 |
20020147614 | Doerr et al. | Oct 2002 | A1 |
20020188552 | Kavounas et al. | Dec 2002 | A1 |
20020198831 | Patricelli et al. | Dec 2002 | A1 |
20030009367 | Morrison | Jan 2003 | A1 |
20030050796 | Baldwin | Mar 2003 | A1 |
20030050799 | Jay et al. | Mar 2003 | A1 |
20030069760 | Gelber | Apr 2003 | A1 |
20030074234 | Stasny | Apr 2003 | A1 |
20030097310 | Ono et al. | May 2003 | A1 |
20030130875 | Hawash | Jul 2003 | A1 |
20030149625 | Leonardi et al. | Aug 2003 | A1 |
20030154163 | Phillips et al. | Aug 2003 | A1 |
20030172008 | Hage et al. | Sep 2003 | A1 |
20030187690 | Miller | Oct 2003 | A1 |
20030229540 | Algiene | Dec 2003 | A1 |
20030236747 | Sager | Dec 2003 | A1 |
20040006490 | Gingrich et al. | Jan 2004 | A1 |
20040039599 | Fralic | Feb 2004 | A1 |
20040054685 | Rahn et al. | Mar 2004 | A1 |
20040059607 | Ball et al. | Mar 2004 | A1 |
20040073456 | Gottlieb et al. | Apr 2004 | A1 |
20040073457 | Kalies | Apr 2004 | A1 |
20040078222 | Khan et al. | Apr 2004 | A1 |
20040078234 | Tallal, Jr. | Apr 2004 | A1 |
20040088187 | Chudy et al. | May 2004 | A1 |
20040103062 | Wood et al. | May 2004 | A1 |
20040117323 | Mindala | Jun 2004 | A1 |
20040148198 | Kalies | Jul 2004 | A1 |
20040153336 | Virdee et al. | Aug 2004 | A1 |
20040199545 | Wagner et al. | Oct 2004 | A1 |
20040236630 | Kost et al. | Nov 2004 | A1 |
20040249745 | Baaren | Dec 2004 | A1 |
20050015280 | Gabel et al. | Jan 2005 | A1 |
20050060201 | Connely, III et al. | Mar 2005 | A1 |
20050065821 | Kalies, Jr. | Mar 2005 | A1 |
20050075932 | Mankoff | Apr 2005 | A1 |
20050080692 | Padam et al. | Apr 2005 | A1 |
20050102169 | Wilson | May 2005 | A1 |
20050154627 | Zuzek et al. | Jul 2005 | A1 |
20050187793 | Myles | Aug 2005 | A1 |
20050197862 | Paterson et al. | Sep 2005 | A1 |
20050240442 | Lapsker et al. | Oct 2005 | A1 |
20050240473 | Ayers, Jr. et al. | Oct 2005 | A1 |
20050261939 | Augspurger et al. | Nov 2005 | A1 |
20050288972 | Marvin et al. | Dec 2005 | A1 |
20060020514 | Yered | Jan 2006 | A1 |
20060026041 | Ullman | Feb 2006 | A1 |
20060036470 | Oaks | Feb 2006 | A1 |
20060085231 | Brofman | Apr 2006 | A1 |
20060085385 | Foster et al. | Apr 2006 | A1 |
20060113376 | Reed et al. | Jun 2006 | A1 |
20060149595 | Williams et al. | Jul 2006 | A1 |
20060149784 | Tholl et al. | Jul 2006 | A1 |
20060184391 | Barre et al. | Aug 2006 | A1 |
20060212318 | Dooley | Sep 2006 | A1 |
20060212345 | Soza et al. | Sep 2006 | A1 |
20060224414 | Astrup et al. | Oct 2006 | A1 |
20060224417 | Werner | Oct 2006 | A1 |
20060224443 | Soza et al. | Oct 2006 | A1 |
20060235747 | Hammond et al. | Oct 2006 | A1 |
20060259363 | Jhetam et al. | Nov 2006 | A1 |
20070005402 | Kennedy et al. | Jan 2007 | A1 |
20070033137 | Provost et al. | Feb 2007 | A1 |
20070043589 | Warren et al. | Feb 2007 | A1 |
20070043595 | Pederson | Feb 2007 | A1 |
20070050209 | Yered | Mar 2007 | A1 |
20070050210 | Wiley, II | Mar 2007 | A1 |
20070067186 | Brenner et al. | Mar 2007 | A1 |
20070094133 | Anandarao et al. | Apr 2007 | A1 |
20070108053 | Cramer et al. | May 2007 | A1 |
20070136100 | Daugherty et al. | Jun 2007 | A1 |
20070162303 | Wiley et al. | Jul 2007 | A1 |
20070168228 | Lawless | Jul 2007 | A1 |
20070185799 | Harrison et al. | Aug 2007 | A1 |
20070191985 | Bain | Aug 2007 | A1 |
20070194352 | Han | Aug 2007 | A1 |
20070202886 | Dhebri et al. | Aug 2007 | A1 |
20070204043 | Espinosa et al. | Aug 2007 | A1 |
20070219813 | Moore | Sep 2007 | A1 |
20070233525 | Boyle | Oct 2007 | A1 |
20070233526 | Hoffman et al. | Oct 2007 | A1 |
20070239493 | Sweetland et al. | Oct 2007 | A1 |
20070250341 | Howe et al. | Oct 2007 | A1 |
20070260750 | Feied et al. | Nov 2007 | A1 |
20070276697 | Wiley et al. | Nov 2007 | A1 |
20070294765 | Rihn et al. | Dec 2007 | A1 |
20070299915 | Shraim et al. | Dec 2007 | A1 |
20080033750 | Swiss et al. | Feb 2008 | A1 |
20080103836 | Park et al. | May 2008 | A1 |
20080112411 | Stafford et al. | May 2008 | A1 |
20080152107 | Mendiola | Jun 2008 | A1 |
20080183492 | Warren et al. | Jul 2008 | A1 |
20080215361 | Nunnari et al. | Sep 2008 | A1 |
20080262948 | Grady et al. | Oct 2008 | A1 |
20090006141 | Karr | Jan 2009 | A1 |
20090030719 | Nadas et al. | Jan 2009 | A1 |
20090064330 | Shraim et al. | Mar 2009 | A1 |
20090083064 | Mahinda | Mar 2009 | A1 |
20090094051 | Ard et al. | Apr 2009 | A1 |
20090100099 | Buckwalter | Apr 2009 | A1 |
20090106313 | Boldyga | Apr 2009 | A1 |
20090112707 | Weiss et al. | Apr 2009 | A1 |
20090198510 | Ditto | Aug 2009 | A1 |
20090204477 | Urso | Aug 2009 | A1 |
20090287558 | Seth et al. | Nov 2009 | A1 |
20090313112 | Champ et al. | Dec 2009 | A1 |
20090327363 | Cullen et al. | Dec 2009 | A1 |
20100030667 | Chudy et al. | Feb 2010 | A1 |
20100070298 | Kalies | Mar 2010 | A1 |
20100144259 | Allexon et al. | Jun 2010 | A1 |
20100145730 | Abreu | Jun 2010 | A1 |
20100161353 | Mayaud | Jun 2010 | A1 |
20100217622 | Brown et al. | Aug 2010 | A1 |
20100285821 | Smeeding et al. | Nov 2010 | A1 |
20100287001 | Pearce et al. | Nov 2010 | A1 |
20100293236 | Wisner et al. | Nov 2010 | A1 |
20110015978 | Welch, Jr. | Jan 2011 | A1 |
20110112871 | Simonowski et al. | May 2011 | A1 |
20110161109 | Pinsonneault et al. | Jun 2011 | A1 |
20110196697 | Akers | Aug 2011 | A1 |
20110288925 | Thomas et al. | Nov 2011 | A1 |
20120053958 | Marshall et al. | Mar 2012 | A1 |
20120136809 | Cannata et al. | May 2012 | A1 |
20120143627 | Ruben et al. | Jun 2012 | A1 |
20120166268 | Griffiths | Jun 2012 | A1 |
20120179481 | Patel et al. | Jul 2012 | A1 |
20120185263 | Emert | Jul 2012 | A1 |
20120185264 | Demogenes et al. | Jul 2012 | A1 |
20120253829 | John et al. | Oct 2012 | A1 |
20120253830 | John et al. | Oct 2012 | A1 |
20120253831 | John et al. | Oct 2012 | A1 |
20120253832 | John et al. | Oct 2012 | A1 |
20120253833 | John et al. | Oct 2012 | A1 |
20120253846 | John et al. | Oct 2012 | A1 |
20120265591 | Hwang | Oct 2012 | A1 |
20120323608 | Herzlinger | Dec 2012 | A1 |
20130041968 | Cohen et al. | Feb 2013 | A1 |
20130046610 | Abraham | Feb 2013 | A1 |
20130103602 | Melnick et al. | Apr 2013 | A1 |
20130144715 | Kranzley et al. | Jun 2013 | A1 |
20130179180 | Patra | Jul 2013 | A1 |
20130197980 | Lerner et al. | Aug 2013 | A1 |
20130246082 | Brylawski et al. | Sep 2013 | A1 |
20130311389 | Kaehler et al. | Nov 2013 | A1 |
20140039911 | Iyer | Feb 2014 | A1 |
20140088985 | Grant et al. | Mar 2014 | A1 |
20140214435 | Previdi | Jul 2014 | A1 |
20140249861 | Gamble et al. | Sep 2014 | A1 |
20140249864 | Sultan et al. | Sep 2014 | A1 |
20140278448 | Sadeghi et al. | Sep 2014 | A1 |
20140278456 | Milosevich et al. | Sep 2014 | A1 |
20140278531 | Gupta | Sep 2014 | A1 |
20150032465 | Sundar et al. | Jan 2015 | A1 |
20150088557 | Huynh et al. | Mar 2015 | A1 |
20150142479 | Porter et al. | May 2015 | A1 |
20150149197 | Guinan | May 2015 | A1 |
20150154565 | Kaehler et al. | Jun 2015 | A1 |
20150154588 | Purves et al. | Jun 2015 | A1 |
20150195224 | Karnin et al. | Jul 2015 | A1 |
20150213195 | Blechman | Jul 2015 | A1 |
20150234991 | Pinsonneault | Aug 2015 | A1 |
20150235177 | Shraim et al. | Aug 2015 | A1 |
20150269695 | Pinsonneault et al. | Sep 2015 | A1 |
20150332422 | Gilmartin | Nov 2015 | A1 |
20150371000 | Pinsonneault | Dec 2015 | A1 |
20160012465 | Sharp | Jan 2016 | A1 |
20160103978 | Stong | Apr 2016 | A1 |
20160140593 | Smeeding et al. | May 2016 | A1 |
20160213512 | Palanker et al. | Jul 2016 | A1 |
20160267544 | Flood et al. | Sep 2016 | A1 |
20160267545 | Glass et al. | Sep 2016 | A1 |
20160307195 | Cantwell et al. | Oct 2016 | A1 |
20160321406 | Timmerman et al. | Nov 2016 | A1 |
20160321410 | Timmerman et al. | Nov 2016 | A1 |
20160358142 | Hillen | Dec 2016 | A1 |
20160359795 | Fehling | Dec 2016 | A1 |
20170034087 | Borenstein et al. | Feb 2017 | A1 |
20170220768 | Tanner, Jr. et al. | Aug 2017 | A1 |
20170323295 | Kranzley et al. | Nov 2017 | A1 |
20170324695 | Fischer et al. | Nov 2017 | A1 |
20170329922 | Eberting et al. | Nov 2017 | A1 |
20180012244 | Leonardi | Jan 2018 | A1 |
20180366810 | Nero et al. | Dec 2018 | A1 |
20190095582 | Waits | Mar 2019 | A1 |
20190213212 | Adato et al. | Jul 2019 | A1 |
20190252049 | Fotsch | Aug 2019 | A1 |
20190385733 | Kaye et al. | Dec 2019 | A1 |
20190385734 | Pinsonneault | Dec 2019 | A1 |
20200105392 | Karkazis et al. | Apr 2020 | A1 |
20200372988 | Bezdek et al. | Nov 2020 | A1 |
20210319887 | Derrick, Jr. et al. | Oct 2021 | A1 |
20210374876 | Cedergreen | Dec 2021 | A1 |
Number | Date | Country |
---|---|---|
2003243327 | Dec 2003 | AU |
2 482 370 | Mar 2006 | CA |
2792252 | Apr 2013 | CA |
2810686 | Oct 2013 | CA |
102362778 | Feb 2012 | CN |
100755440 | Sep 2007 | KR |
101038074 | Jun 2011 | KR |
101101692 | Dec 2011 | KR |
20110138108 | Dec 2011 | KR |
20110138572 | Dec 2011 | KR |
101154858 | Jun 2012 | KR |
WO 1991006917 | May 1991 | WO |
WO 1995003569 | Feb 1995 | WO |
WO 1997025682 | Jul 1997 | WO |
WO 1998050871 | Nov 1998 | WO |
WO 2000039737 | Jul 2000 | WO |
WO 2003098401 | Nov 2003 | WO |
WO 2007025295 | Mar 2007 | WO |
WO 2007094772 | Aug 2007 | WO |
WO 2008092109 | Jul 2008 | WO |
Entry |
---|
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 16/816,460, dated Aug. 10, 2023, 14 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/144,426, dated Jul. 13, 2023, 17 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/158,118, dated Jul. 13, 2023, 18 pages, U.S. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 16/552,021, dated Oct. 20, 2022, 14 pages, U.S. |
U.S. Appl. No. 16/816,460, “Adaptive System and Method for Adjudicating Claims to Reduce Member Responsibility”, Unpublished (Filing Date Mar. 12, 2020), (Michael Rea, Inventor), (RC Savings, LLC, Assignee). |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/816,460, dated Mar. 3, 2023, 14 pages, U.S. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/162,461, dated May 19, 2023, 23 pages, U.S. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 17/158,118, dated May 26, 2023, 5 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/674,366, dated Jun. 6, 2023, 75 pages, U.S. |
United States Patent and Trademark Office, Miscellaneous Office Action, Restarting Period, received for U.S. Appl. No. 17/175,939, dated Jun. 14, 2023, 23 pages, U.S. |
Viswanthan, Meera, et al., “Interventions to Improve Adherence to Self-administered Medications for Chronic Diseases in the United States,” Annals of Internal Medicine, Dec. 4, 2012, retrieved from the Internet at <https://www.acpjournals.org/doi/full/10.7326/0003-4819-157-11-201212040-00538?rfr_dat=cr_pub++0pubmed&url_ver=Z39.88-2003&rfr_id=ori%3Arid%3Acrossref.org> on Jun. 14, 2023, 25 pages. |
American Hospital Association, “Drug Price Proposals”, dated Apr. 2019, retrieved from the Internet at <URL: https://www.aha.org/system/files/media/file/2019/04/aha-drug-policy-recommendations_2.pdf>, 8 pages. |
California Health Care Foundation, “When the Price Is Not Right: State Options on Prescription Drug Pricing”, dated Jun. 2016, retrieved from the Internet at: <URL: https://www.chcf.org/wp-content/uploads/2017/12/PDF-WhenStateRxPricing.pdf>, 16 pages. |
Hsee, Christopher K., et al., “General Evaluability Theory”, Perspectives on Psychological Science, Jul. 2010, pp. 343-355, vol. 5, No. 4, Sage Publications, Inc. on behalf of the Association for Psychological Science retrieved from the Internet at <URL: https://www.jstor.org/stable/41613442>. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 16/867,286, dated Dec. 6, 2022, 8 pages, US. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 17/175,939, dated Dec. 22, 2022, 5 pages, US. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/144,426, dated Dec. 8, 2022, 21 pages, US. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 16/832,318, dated Dec. 8, 2022, 26 pages, US. |
Van Nuys, Ph.D., Karen, et al., “Prescription Drug Copayment Coupon Landscape”, Drug Pricing White Paper, USC Leonard D. Schaeffer Center for Health Policy and Economics, Feb. 7, 2018, retrieved from the Internet at <URL: https://healthpolicy.usc.edu/research/prescription-drug-copayment-coupon-landscape/>, 21 pages. |
Dubois, Robert W., “Rx Drug Costs: List Prices Versus Net Prices And The Importance Of Staying Within The Data”, Health Affairs Blog, Mar. 2019, 7 pages. |
Kamal, Rabah, et al., “What are the recent and forecasted trends in prescription drug spending?” Peterson-KFF Health System Tracker, Feb. 20, 2019, 19 pages, Peterson Center on Healthcare. |
Cepeda, Maria Soledad, et al., “Quantification of missing prescriptions in commercial claims databases : results of a cohort study.”, Pharmacoepidemiology and Drug Safety, Apr. 2017, pp. 386-392, vol. 26, Epub Jan. 25, 2017 on Wiley Online Library. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 16/867,286, dated Sep. 8, 2022, 19 pages, U.S. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 16/792,413, dated Sep. 8, 2022, 18 pages, U.S. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 17/012,565, dated Sep. 21, 2022, 11 pages, U.S. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 16/453,509, dated Oct. 3, 2022, 23 pages, U.S. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/175,939, dated Oct. 5, 2022, 30 pages, U.S. |
United States Patent and Trademark Office, Nonfinal Office Action received for U.S. Appl. No. 17/162,461, dated Oct. 5, 2022, 47 pages, U.S. |
United States Patent and Trademark Office, Nonfinal Office Action received for U.S. Appl. No. 17/158,118, dated Oct. 7, 2022, 46 pages, U.S. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 16/867,286, dated Feb. 6, 2023, 3 pages, US. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 17/144,426, dated Mar. 3, 2023, 6 pages, US. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/158,118, dated Mar. 3, 2023, 19 pages, US. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/012,565, dated Jul. 25, 2022, 43 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/867,286, dated Mar. 31, 2023, 16 pages, US. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/175,939, dated Apr. 26, 2023, 24 pages, US. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 16/867,286, dated Sep. 19, 2023, 16 pages, US. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 16/816,460, dated Oct. 19, 2023, 3 pages, US. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/162,461, dated Oct. 19, 2023, 25 pages, US. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/674,366, dated Dec. 15, 2023, 53 pages, US. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/144,426, dated Dec. 19, 2023, 22 pages, US. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/158,118, dated Dec. 19, 2023, 22 pages, US. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/816,460, dated Dec. 22, 2023, 46 pages, US. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 17/162,461, dated Aug. 24, 2023, 2 pages, US. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 17/144,426, dated Mar. 21, 2024, 5 pages. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 17/674,366, dated Mar. 22, 2024, 6 pages. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/175,939, dated Mar. 1, 2024, 24 pages. |
'Pharmacy Reject Codes NCPDP, 5 pages. |
'St. Vincent's first to use Birmingham startup's information system. The Birmingham News [Online] Apr. 11, 2005. URL: http://www.awarix.com. |
'St. Vincent's is Digital Flagship D. Lockridge; Birmingham Medical News [Online] Sep. 2005. |
'Two automatic identification technology, neither new in the sense if being recent developments . . . Patient Safety & Quality Healthcare [Online] Aug. 2005_ URL: http://www_awarix.com. |
Advisory Action for U.S. Appl. No. 14/193,294 mailed Nov. 9, 2017, 3 pages. |
Advisory Action for U.S. Appl. No. 15/085,166 dated Apr. 11, 2019, 4 pages. |
Advisory Action for U.S. Appl. No. 15/085,166 dated Apr. 29, 2020, 3 pages. |
Advisory Action for U.S. Appl. No. 15/137,371 mailed Feb. 25, 2019, 5 pages. |
Advisory Action for U.S. Appl. No. 15/427,746 mailed Jul. 2, 2019, 2 pages. |
Advisory Action received for U.S. Appl. No. 15/085,166, dated Jan. 29, 2021, 3 pages, US. |
Almaro, Moshe; “Recovery and Reuse of Unused Prescription Drugs” MIT What Matters: Aug. 2005. |
American Society of Health-System Pharmacists (ASHP), “Is Prescribing the Next Step in the Evolution of Pharmacy?” May 15, 2012. |
Anonymous, ACS to Demonstrate Electronic Health Record Solution Suite at MMIS 2007 Conference; EHR Tools Consolidate Data, Provide Useful Information at the Point of Care for Medicaid Providers, Payers, and Patients, PR Newswire, Aug. 13, 2007, New York, NY, USA. |
Anonymous, Medic; On-line Goes In-House, Chain Store Age Executive, Jan. 1987, vol. 63, Issue 1, USA; Abstract only. |
Anonymous, Pharmacy Industry Leaders Launch Firm to Supply Real-Time Data, PR Newswire, Jul. 30, 2001, p. 1, New York, NY, USA. |
Anonymous, TechRx Announces Successful Beta Deployment of T-Rex. PR Newswire. May 13, 2002. |
Chu, Kuan-Yu, et al., “Incremental analysis of the reengineering of an outpatient billing process: an empirical study in a public hospital”, BMC Health Services Research, Jun. 13, 2013, vol. 13, No. 215, 8 pages, BioMed Central LTD, UK. |
CMS Updates Drug Dashboards with Prescription Drug Pricing and Spending Data, Data, Medicare Part D, Prescription drugs (Mar. 14, 2019). |
Consalvo, Bob; “City of Boston in the City Council” hearing notice, Dec. 6, 2006. |
Coping with Information Overload. The News Source for Healthcare Information Technology [Online] Nov. 2004. URL: http://www.awarix.com. |
Decision to Grant European Patent Application No. 13809457.8 dated May 18, 2017. |
Examiner's Answer for U.S. Appl. No. 14/145,027 mailed Sep. 7, 2016, 27 pages. |
Extended European Search Report for European Application No. 13809457.8 dated Apr. 15, 2016, 6 pages. |
Final Office Action for U.S. Appl. No. 12/140,015 mailed Jan. 31, 2011, 10 pages. |
Final Office Action for U.S. Appl. No. 12/415,062 mailed Oct. 6, 2011, 18 pages. |
Final Office Action for U.S. Appl. No. 12/555,589 mailed Apr. 11, 2012, 17 pages. |
Final Office Action for U.S. Appl. No. 12/560,071 mailed Aug. 28, 2015, 8 pages. |
Final Office Action for U.S. Appl. No. 12/560,071 mailed Nov. 8, 2012, 11 pages. |
Final Office Action for U.S. Appl. No. 12/570,982 mailed Apr. 11, 2014, 22 pages. |
Final Office Action for U.S. Appl. No. 12/570,982 mailed Aug. 28, 2015, 10 pages. |
Final Office Action for U.S. Appl. No. 12/570,982 mailed Jan. 17, 2013, 19 pages. |
Final Office Action for U.S. Appl. No. 12/730,015 mailed Aug. 14, 2012, 10 pages. |
Final Office Action for U.S. Appl. No. 12/978,898 mailed May 16, 2013, 16 pages. |
Final Office Action for U.S. Appl. No. 13/721,890 mailed Jun. 24, 2015, 14 pages. |
Final Office Action for U.S. Appl. No. 13/721,890 mailed Nov. 25, 2016, 12 pages. |
Final Office Action for U.S. Appl. No. 13/782,909 mailed May 31, 2016, 18 pages. |
Final Office Action for U.S. Appl. No. 13/782,909 mailed Oct. 6, 2015, 24 pages. |
Final Office Action for U.S. Appl. No. 13/804,175 mailed Oct. 6, 2015, 6 pages. |
Final Office Action for U.S. Appl. No. 13/827,676 mailed Jul. 13, 2015, 17 pages. |
Final Office Action for U.S. Appl. No. 14/090,113 mailed Jan. 6, 2016, 18 pages. |
Final Office Action for U.S. Appl. No. 14/090,122 mailed Apr. 22, 2016, 13 pages. |
Final Office Action for U.S. Appl. No. 14/145,027 mailed Nov. 19, 2015, 12 pages. |
Final Office Action for U.S. Appl. No. 14/193,294 mailed May 2, 2016, 29 pages. |
Final Office Action for U.S. Appl. No. 14/218,326 mailed Jun. 30, 2016, 17 pages. |
Final Office Action for U.S. Appl. No. 15/085,166, dated Dec. 4, 2020, 11 pages. |
Final Office Action for U.S. Appl. No. 15/137,371 mailed Nov. 28, 2018, 24 pages. |
Final Office Action for U.S. Appl. No. 15/427,746 mailed Apr. 15, 2019, 9 pages. |
Google NPL (non-patent literature) Search on “pharmacy payment benefit copay NDC database”, retrieved from the Internet at <https://scholar.google.com/scholar?hl=en&as_sdt=3,47&g-pharmacy+payment+benefit+copay+NDC+database> on Feb. 20, 2022 at 3:02 pm, 1 page. |
Google NPL (non-patent literature) Search on “pharmacy payment benefit copay NDC database”, retrieved from the Internet at <https://www.google.com/search?g=pharmacy+payment+benefit+copay+ndc+database&source=int&tbs=cdr%3A1%2Ccd_min%3A1%2F1%2F2010%2 . . . > on Feb. 20, 2022 at 3:00 pm, 2 pages. |
Google Patents Search (including Web Search History, Prior Art Search Printable History Generator) on “pharmacy payment benefit copay NDC database) (prescription) (code) (refills) (error code) country: US before:filing:Dec. 31, 2013”, retrieved from the Internet at <https://patents.google.com/?q=pharmacy+payment+benefit+copay+NDC+database&q=prescription&q=code&q=refills&q=error+code&country=US&before-filing:Dec. 31, 2013> retrieved on Jun. 1, 2022, 4 pages. |
Google Scholar Search (including Web Search History, Prior Art Search Printable History Generator) on “pharmacy payment benefit copay NDC database prescription . . . ”, retrieved from the Internet at <https://scholar.google.com/scholar?hl=en&as_sdt=0%2C47&as_ylo=2010&as_yhi=2013&q=pharmacy+payment+benefit+copay+NDC+database+pres . . . > retrieved on Jun. 1, 2022, 3 pages. |
How to Estimate the Cost of a Prescription. Pam Olson, Sr. Client Services Executive, Navitus Health Solutions (Year: 2015). |
Kaplan et al., “Let the Needles Do the Talking! Evaluating the New Haven Needle Exchange.” Interfaces 23:1, Jan.-Feb. 1993 (pp. 7-26). |
Lamb, J., New Era of Electronic Medicine Management: E-PRESCRIPTIONS, Britain's Traditionally Cautious National Health Service is Starting Trials for Online Prescription, with the Aim of Cutting Costs, Finance Times, London, Feb. 21, 2001, p. 6, London, United Kingdom. |
Letter Restarting Period for Response for U.S. Appl. No. 13/721,890 mailed Jan. 14, 2015, 11 pages. |
Marie Chisholm et al. “Pharmaceutical Manufacturer Assistance Program.” Arch Intern Med. vol. 162, Apr. 8, 2002. |
Non-Final Office Action for U.S. Appl. No. 12/560,071 mailed Jun. 21, 2012, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 12/570,982 mailed Jun. 20, 2012, 10 pages. |
Non-Final Office Action for U.S. Appl. No. 14/193,294 mailed Feb. 21, 2017, 32 pages. |
Non-Final Office Action for U.S. Appl. No. 15/085,166 dated Jun. 12, 2020, 26 pages. |
Non-Final Office Action for U.S. Appl. No. 16/180,915 dated Jun. 1, 2020, 40 pages. |
Non-final Office Action for U.S. Appl. No. 12/140,015 mailed Oct. 8, 2010, 9 pages. |
Non-final Office Action for U.S. Appl. No. 12/189,650 mailed Jan. 22, 2010, 11 pages. |
Non-final Office Action for U.S. Appl. No. 12/189,654 mailed Jan. 22, 2010, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 12/388,956 mailed Feb. 3, 2011, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 12/415,062 mailed Mar. 30, 2011, 23 pages. |
Non-Final Office Action for U.S. Appl. No. 12/555,589 mailed Dec. 9, 2011, 12 pages. |
Non-Final Office Action for U.S. Appl. No. 12/560,071 mailed Sep. 23, 2014, 17 pages. |
Non-Final Office Action for U.S. Appl. No. 12/570,982 mailed Sep. 12, 2013, 22 pages. |
Non-Final Office Action for U.S. Appl. No. 12/730,015 mailed Mar. 6, 2012, 9 pages. |
Non-Final Office Action for U.S. Appl. No. 12/956,411 mailed Jan. 24, 2011, 9 pages. |
Non-Final Office Action for U.S. Appl. No. 12/978,898 mailed Feb. 6, 2013, 12 pages. |
Non-Final Office Action for U.S. Appl. No. 12/982,395 mailed Dec. 11, 2012, 13 pages. |
Non-Final Office Action for U.S. Appl. No. 13/721,890 mailed Jan. 9, 2015, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 13/721,890 mailed Jun. 14, 2016, 9 pages. |
Non-final Office Action for U.S. Appl. No. 13/782,909 mailed Feb. 11, 2016, 17 pages. |
Non-Final Office Action for U.S. Appl. No. 13/827,676 mailed Dec. 26, 2014, 13 pages. |
Non-final Office Action for U.S. Appl. No. 13/827,676 mailed Dec. 30, 2015, 23 pages. |
Non-Final Office Action for U.S. Appl. No. 14/145,027 mailed Mar. 23, 2015, 13 pages. |
Non-Final Office Action for U.S. Appl. No. 15/137,371 mailed May 29, 2018, 19 pages. |
Non-Final Office Action for U.S. Appl. No. 15/427,746 mailed Oct. 18, 2018, 9 pages. |
Non-Final Office Action for U.S. Appl. No. 16/819,258 dated Sep. 4, 2020, 6 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/085,166, dated Mar. 17, 2021, 11 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/551,962, dated Mar. 2, 2021, 16 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/453,509 mailed Mar. 26, 2021, 45 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/832,318 mailed Apr. 23, 2021, 52 pages. |
Notice of Allowance and Fees(s) Due for U.S. Appl. No. 15/925,011 dated Jan. 22, 2021, 15 pages. |
Notice of Allowance for U.S. Appl. No. 16/180,915 dated Dec. 11, 2020, 23 pages. |
Notice of Allowance for U.S. Appl. No. 11/674,069 mailed Jul. 19, 2010, 13 pages. |
Notice of Allowance for U.S. Appl. No. 12/140,015 mailed Jun. 10, 2011, 10 pages. |
Notice of Allowance for U.S. Appl. No. 12/165,221 mailed Nov. 16, 2010, 6 pages. |
Notice of Allowance for U.S. Appl. No. 12/189,650 mailed Aug. 13, 2010, 11 pages. |
Notice of Allowance for U.S. Appl. No. 12/388,956 mailed Jun. 14, 2011, 9 pages. |
Notice of Allowance for U.S. Appl. No. 12/956,411 mailed Aug. 5, 2011, 8 pages. |
Notice of Allowance for U.S. Appl. No. 12/982,395 mailed Apr. 24, 2013, 9 pages. |
Notice of Allowance for U.S. Appl. No. 14/181,011 dated May 15, 2019, 9 pages. |
Notice of Allowance for U.S. Appl. No. 15/137,371 mailed May 2, 2019, 11 pages. |
Notice of Allowance for U.S. Appl. No. 15/427,746 mailed Dec. 4, 2019, 5 pages. |
Notice of Allowance for U.S. Appl. No. 15/427,746 mailed Jul. 31, 2019, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 14/643,468, Oct. 24, 2018, 22 pages. |
Notice of Allowance received for U.S. Appl. No. 14/181,011, filed Feb. 13, 2019, 9 pages. |
Office Action for U.S. Appl. No. 14/193,294 dated Aug. 4, 2017, 31 pages. |
Office Action for U.S. Appl. No. 14/193,294 dated Mar. 22, 2018, 28 pages. |
Office Action for U.S. Appl. No. 14/193,294 dated Sep. 19, 2018, 27 pages. |
Office Action for U.S. Appl. No. 14/229,043 dated Feb. 27, 2019, 18 pages. |
Office Action for U.S. Appl. No. 14/229,043 dated Jul. 24, 2017, 19 pages. |
Office Action for U.S. Appl. No. 14/229,043 dated Sep. 5, 2019, 22 pages. |
Office Action for U.S. Appl. No. 14/229,043 dated Sep. 14, 2018, 17 pages. |
Office Action for U.S. Appl. No. 14/643,468 dated Mar. 8, 2018, 11 pages. |
Office Action for U.S. Appl. No. 15/085,166 dated Dec. 27, 2018, 24 pages. |
Office Action for U.S. Appl. No. 15/085,166 dated Jun. 29, 2018, 19 pages. |
Office Action for U.S. Appl. No. 15/085,166 dated Mar. 3, 2020, 25 pages. |
Office Action for U.S. Appl. No. 15/085,166 dated Sep. 4, 2019, 23 pages. |
Office Action for U.S. Appl. No. 15/422,184 dated Aug. 27, 2019, 16 pages. |
Office Action for U.S. Appl. No. 15/422,184 dated Feb. 15, 2019, 15 pages. |
Office Action for U.S. Appl. No. 15/422,184 dated Jan. 14, 2020, 19 pages. |
Office Action for U.S. Appl. No. 15/422,184 dated Sep. 10, 2018, 13 pages. |
Office Action for U.S. Appl. No. 15/925,011 dated Jun. 27, 2019, 15 pages. |
Office Action for U.S. Appl. No. 15/925,011 dated Oct. 24, 2019, 19 pages. |
Office Action for U.S. Appl. No. 15/925,948 dated Jun. 25, 2019, 13 pages. |
Office Action for U.S. Appl. No. 15/925,948 dated Oct. 23, 2019, 18 pages. |
Office Action for U.S. Appl. No. 12/570,982 mailed Apr. 8, 2015, 9 pages. |
Office Action for U.S. Appl. No. 13/782,909 mailed Jun. 25, 2015, 16 pages. |
Office Action for U.S. Appl. No. 13/804,175 mailed Mar. 13, 2015, 9 pages. |
Office Action for U.S. Appl. No. 14/090,113 mailed Jun. 18, 2015, 14 pages. |
Office Action for U.S. Appl. No. 14/090,122 mailed Oct. 21, 2016, 12 pages. |
Office Action for U.S. Appl. No. 14/090,122 mailed Sep. 11, 2015, 10 pages. |
Office Action for U.S. Appl. No. 14/181,011 mailed Feb. 29, 2016, 23 pages. |
Office Action for U.S. Appl. No. 14/181,011 mailed Mar. 20, 2017, 28 pages. |
Office Action for U.S. Appl. No. 14/181,011 mailed Oct. 20, 2016, 28 pages. |
Office Action for U.S. Appl. No. 14/181,011 mailed Sep. 12, 2017, 17 pages. |
Office Action for U.S. Appl. No. 14/193,294 mailed Dec. 17, 2015, 21 pages. |
Office Action for U.S. Appl. No. 14/218,326 mailed Dec. 1, 2015, 13 pages. |
Opar, Alisa; “Rising drug costs prompt new uses for old pills.” Nature Medicine, 1211333 (2006). |
PTAB Decision on Appeal for U.S. Appl. No. 14/145,027 mailed May 31, 2018, 11 pages. |
PTAB Decision on Request for Rehearing for U.S. Appl. No. 14/145,027 mailed Aug. 30, 2018, 9 pages. |
Sampson, R.J., Taking Control of Health Care Costs, Best's Review—Life Health Insurance Edition, Nov. 1983, vol. 84, Issue 7, USA; Abstract only. |
Scientific and Technical Information Center, Report of Information from Dialog (NPL (non-patent literature) Search Results, Abstracts only), dated Nov. 1, 2021, (Year: 2021), 9 pages. |
Siler, Sharon et al., “Safe Disposal of Unused Controlled Substances” Avalere Health 2008. |
Strom, Stephanie; “Old Pills Finding New Medicine Cabinets” NY Times, May 18, 2005. |
Subnotebooks, Phones, and More. St. Vincent's Gets on Track. Mobile Health Data [Online], Nov. 19, 2004. URL:http://www.awarix.com. |
Supplemental Notice of Allowability received for U.S. Appl. No. 16/180,915, dated Jan. 28, 2021, 2 pages. |
Supplemental Notice of Allowability received for U.S. Appl. No. 16/180,915, dated Mar. 12, 2021, 10 pages. |
U.S. Notice of Allowance received for U.S. Appl. No. 16/819,258, dated Nov. 16, 2020, 8 pages, U.S. |
U.S. Appl. No. 14/229,043, “Systems And Methods For Monitoring And Reporting Redemption Information At A Pharmacy For Patient Incentive Information Identified At The Time Of Prescribing,” Unpublished (Filed Mar. 28, 2014), (Roger Pinsonneault, Inventor), (McKesson Corporation, Assignee), abandoned. |
U.S. Appl. No. 15/084,034, “Prescription Provider System,” Unpublished (Filed Mar. 29, 2016), (Scott Genone, Inventor), (McKesson Corporation, Assignee), abandoned. |
U.S. Appl. No. 15/085,166, “Alternative Therapy Identification System”, Unpublished (Filed Mar. 30, 2016), (Elizabeth Kaye, Inventor), (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 16/832,318, “Method, Apparatus, And Computer Program Product for Estimated Prescription Costs”, Unpublished (Filed Mar. 27, 2020), (Stacy Hopkins, Inventor), (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/012,565, “Method, Apparatus, and Computer Program Product for Performing an Alternative Evaluation Procedure in Response to an Electronic Message,” Unpublished (filing date Sep. 4, 2020), (Stacy Hopkins, et al., Inventors) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/092,705, “Computing System and Method for Automatically Reversing an Action Indicated by an Electronic Message,” Unpublished (filing date Nov. 9, 2020), (Patrick Harris, Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 16/792,413, “Method, Apparatus and Computer Program Product for Partitioning Prescription Transaction Costs in an Electronic Prescription Transaction,” Unpublished (filed Feb. 17, 2020), (Jared Burdine, Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 16/867,286, “Method, Apparatus, and Computer Program Product for Constructing Electronic Message Responses Dependent Upon Historical Information,” Unpublished (filed May 5, 2020), (Jared Burdine, et al., Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/175,939, “Method, Apparatus, And Computer Program Product For Generating Inquiries In Different Formats, And Compiling Different Information Types In A Response,” Unpublished (filed Feb. 15, 2021), (Stacy Hopkins, et al., Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 16/453,509, “Method, Apparatus, And Computer Program Product For Providing Estimated Prescription Costs,” Unpublished (filed Jun. 26, 2019), (Stacy Hopkins, et al., Inventor) (Mckesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/499,976, “Method, Apparatus, And Computer Program Product For Providing Real-Time Pricing Information,” Unpublished (filed Oct. 13, 2021), (Stacy Hopkins, et al., Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/501,532, “Method, Apparatus, And Computer Program Product For Providing Real-Time Pricing Information,” Unpublished (filed Oct. 14, 2021), (Keith Crozier, et al., Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/219,526, “Method And Apparatus For Parsing And Differently Processing Different Portions Of A Request,” Unpublished (filed Mar. 31, 2021), (Melissa Frechen, et al., Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/162,461, “Method, Apparatus, And Computer Program Product For Constructing Electronic Message Responses Dependent Upon Historical Information,” Unpublished (filed Jan. 19, 2021), (Stewart Aragon, et al., Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/144,426, “Method, Apparatus, And Computer Program Product For Estimating A Target Quantitative Measure Based Upon Historical Electronic Messages,” Unpublished (filed Jan. 8, 2021), (Stewart Aragon, et al., Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/158,118, “Method, Apparatus, And Computer Program Product For Estimating A Target Quantitative Measure Based Upon Historical Electronic Messages,” Unpublished (filed Jan. 26, 2021), (Stewart Aragon, et al., Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/675,616, “Method, Apparatus, And Computer Program Product For Reformatting An Electronic Prescription Transaction,” Unpublished (filed Feb. 18, 2022), (Phillip Draa, et al., Inventor) (McKesson Corporation, Assignee), pending. |
U.S. Appl. No. 17/676,437, “Method, Apparatus, And Computer Program Product For Partitioning Prescription Transaction Costs In An Electronic Prescription Transaction,” Unpublished (filed Feb. 21, 2022), (Phillip Draa, et al., Inventor) (McKesson Corporation, Assignee), pending. |
United States Patent and Trademark Office, Advisory Action for U.S. Appl. No. 15/422,184, Jun. 25, 2019, 4 pages, U.S.A. |
United States Patent and Trademark Office, Advisory Action for U.S. Appl. No. 15/422,184, filed Mar. 26, 2020, 5 pages, U.S.A. |
United States Patent and Trademark Office, Advisory Action for U.S. Appl. No. 15/925,011, filed Jan. 31, 2020, 3 pages, U.S.A. |
United States Patent and Trademark Office, Advisory Action for U.S. Appl. No. 15/925,948, filed Jan. 31, 2020, 4 pages, U.S.A. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 16/453,509, dated Oct. 12, 2021, 5 pages, U.S. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 16/832,318, dated Jan. 28, 2022, 4 pages, U.S. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 16/792,413, dated Mar. 10, 2022, 4 pages, US. |
United States Patent and Trademark Office, Corrected Notice of Allowability received for U.S. Appl. No. 15/085,166, dated Sep. 20, 2021, 6 pages, U.S. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 16/453,509, dated Aug. 18, 2021, 16 pages, U.S. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 16/551,962, dated Nov. 4, 2021, 32 pages, U.S. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 16/832,318, dated Nov. 3, 2021, 22 pages, U.S. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 16/792,413, dated Jan. 10, 2022, 80 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/792,413, dated Aug. 5, 2021, 32 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 15/085,166, dated Jan. 10, 2022, 12 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/867,286, dated Feb. 22, 2022, 38 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/012,565, dated Apr. 12, 2022, 19 pages, U.S.A. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/453,509, dated Apr. 28, 2022, 16 pages, U.S.A. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/552,021, dated May 3, 2022, 60 pages, U.S.A. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/175,939, dated May 12, 2022, 48 pages, U.S.A. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/792,413, dated May 24, 2022, 48 pages, US. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/144,426, dated May 31, 2022, 42 pages, US. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/832,318, dated Jun. 8, 2022, 17 pages, US. |
United States Patent and Trademark Office, Notice of Allowability received for U.S. Appl. No. 15/422,184, filed Nov. 16, 2020, 2 pages, U.S.A. |
United States Patent and Trademark Office, Notice of Allowance and Fee(s) Due received for U.S. Appl. No. 17/219,526, dated Mar. 22, 2022, 11 pages, US. |
United States Patent and Trademark Office, Notice of Allowance and Fee(s) Due received for U.S. Appl. No. 16/551,962, dated Mar. 16, 2022, 10 pages, US. |
United States Patent and Trademark Office, Notice of Allowance and Fee(s) Due received for U.S. Appl. No. 17/092,705, dated Mar. 24, 2022, 9 pages, US. |
United States Patent and Trademark Office, Notice of Allowance and Fee(s) Due received for U.S. Appl. No. 16/551,962, dated Mar. 1, 2022, 14 pages, US. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 15/422,184, filed Oct. 13, 2020, 12 pages, U.S.A. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 15/925,948, filed Nov. 5, 2020, 22 pages, U.S.A. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 15/085,166, dated Sep. 10, 2021, 21 pages, U.S. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 15/085,166, dated Jun. 15, 2022, 18 pages, U.S. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 17/092,705, dated Dec. 23, 2021, 42 pages, U.S. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 16/043,401, dated Aug. 10, 2020, 9 pages, U.S.A. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 17/219,526, dated Feb. 3, 2022, 48 pages, U.S. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 17/092,705, dated May 31, 2022, 9 pages, US. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 17/219,526, dated Jun. 2, 2022, 8 pages, US. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 16/551,962, dated Jun. 8, 2022, 11 pages, US. |
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 15/925,011, filed Apr. 8, 2020, 17 pages, U.S.A. |
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 15/925,948, filed Mar. 23, 2020, 29 pages, U.S.A. |
United States Patent and Trademark Office, Office Action received for U.S. Appl. No. 15/422,184, filed May 18, 2020, 31 pages, U.S.A. |
United States Patent and Trademark Office, Office Action received for U.S. Appl. No. 15/925,011, filed Oct. 8, 2020, 8 pages, U.S.A. |
Wisconsin Physicians Service (WPS) Insurance Corporation, “How to Read Your Explanation of Benefits Chart,” Jun. 16, 2012. |
www.ncoil.org/news/DrugCards2.doc dated Apr. 2002, 5 pages. |
Zhu, V. et al., “Data for drugs available through low-cost prescription drug programs are available through pharmacy benefit manager and claims data,” BMC Clinical Pharmacology, Jun. 22, 2012, vol. 12, No. 12., BioMed Central Ltd., UK. |
Bowman, Michelle, et al., “Risk Assessment of Pharmacies & Electronic Prescriptions,” 2019 IEEE/ACM International Conference on Advances in Social Networks Analysis and Mining (ASONAM), Aug. 27-30, 2019, pp. 641-644, Vancouver, BC, Canada. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 16/816,460, dated May 3, 2024, 22 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/675,616, dated May 8, 2024, 74 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/676,437, dated May 9, 2024, 73 pages, U.S. |
Coase, R. H., “The Nature of the Firm”, Economica, Nov. 1937, pp. 386-405, vol. 4, No. 16, Blackwell Publishing for London School of Economics and Political Science, retrieved from the Internet at http://www.jstor.org/stable/2626876 on Nov. 7, 2011. |
Gemmill, Marin, “The price elasticity of demand for prescription drugs: An exploration of demand in different settings”, Doctor of Philosophy Thesis submitted to the London School of Economics and Political Science, Jan. 2008, 380 pages, UMI No. U615895, UMI Dissertation Publishing, ProQuest LLC, US. |
United States Patent and Trademark Office, Examiner's Answer received for U.S. Appl. No. 16/867,286, dated Jun. 28, 2024, 9 pages, US. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/144,426, dated Jul. 18, 2024, 19 pages, US. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/158,118, dated Jul. 18, 2024, 22 pages, US. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 17/846,373, dated Jul. 25, 2024, 16 pages, US. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/846,373, dated Apr. 5, 2024, 76 pages. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/674,366, dated Jun. 5, 2024, 54 pages, US. |
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/162,461, dated Jun. 4, 2024, 38 pages, US. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 16/816,460, dated Aug. 1, 2024, 3 pages, U.S. |
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 17/162,461, dated Aug. 19, 2024, 2 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 18/098,150, dated Aug. 27, 2024, 61 pages, U.S. |
United States Patent and Trademark Office, Interview Summary received for U.S. Appl. No. 17/675,616, dated Aug. 15, 2024,8 pages, U.S. |
Liu, Shiyong, et al., “Evaluating Cost-Effectiveness Of Treatment Options For Diabetes Patients Using System Dynamics Modeling”, Proceeding of the 2018 Winter Simulation Conference (WSC), Dec. 9-12, 2018, pp. 2577-2588, IEEE, Gothenburg, Sweden. |
Tiriveedhi, V., “Impact of Precision Medicine on Drug Repositioning and Pricing: A Too Small to Thrive Crisis”, Journal of Personalized Medicine, Nov. 5, 2018, 11 pages, vol. 8, No. 36, MDPI, Switzerland. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 17/675,616, dated Sep. 25, 2024, 21 pages, USA. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 17/676,437, dated Sep. 25, 2024, 20 pages, USA. |
United States Patent and Trademark Office, Examiner Interview Summary received for U.S. Appl. No. 17/144,426, dated Oct. 22, 2024,8 pages, U.S. |
United States Patent and Trademark Office, Examiner Interview Summary received for U.S. Appl. No. 17/158,118, dated Oct. 22, 2024,8 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/501,532, dated Oct. 17, 2024, 37 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/499,976, dated Oct. 1, 2024, 79 pages, U.S. |
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/175,939, dated Oct. 24, 2024, 17 pages, U.S. |
United States Patent & Trademark Office, Examiner Interview Summary received for U.S. Appl. No. 18/098,150, dated Nov. 18, 2024, 3 pages, U.S. |
United States Patent & Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/816,460, dated Nov. 21, 2024, 28 pages, US. |