A computing device, method and computer program product are provided in order to automatically reverse an action indicated by an electronic message and, more particularly, to automatically reverse an action indicated by an electronic message in order to permit consideration of an alternative action.
Messages are exchanged between different parties in various different contexts. For example, a first party may issue a request and a second party may analyze the request and, in turn, issue a response. Based upon the response, the first party may then cause a subsequent action to be taken. While widely utilized, the exchange of messages including requests and subsequent responses consumes substantial network resources including network bandwidth in order to transmit the various messages. Additionally, processing resources of the first and second sources are consumed in order to construct or analyze the various messages. In at least some situations, the messages between first and second parties are not exchanged directly between the first and second parties, but propagate through one or more intermediary parties. Thus, the exchange of messages by the first and second parties not only consume processing resources of the first and second parties, but, in some instances, processing resources of the one or more intermediary parties.
Based upon the response to a request, an action may sometimes be taken by or caused to be taken by the first party. However, in other instances, the first party may elect to take no action based upon the response to the request. In these instances in which no action is taken or caused to be taken by the first party, the exchange of messages generally makes the entire roundtrip between the first and second parties, thereby consuming substantial network and processing resources, even though no action is eventually taken based thereupon.
In some instances, an alternative action may be preferable to the action that is triggered by the response to a request. However, the specific sequence of operations that are performed to exchange a request and a corresponding response may not be configured to permit alternative actions to be identified and considered. Instead, only the action that is associated with the particular request is performed even though some other action may be more desirable. Thus, the first party may cause a less desirable action to be performed based upon the response to the request since the first party may be unaware of the availability of an alternative action. In these instances, substantial network and processing resources may be consumed by the exchange of messages with the action that is subsequently performed being less desirable than other alternatives.
A computing device, method and computer program product are provided in accordance with an example embodiment in order to increase the efficiency with which messages are exchanged, thereby conserving network and processing resources associated with the exchange of messages. In this regard, a computing device, method and computer program product are provided in accordance with an example embodiment in order to automatically reverse an action indicated by an electronic message. By automatically reversing an action, the number of messages that are constructed, transmitted and received may be reduced. Moreover, the action indicated by an electronic message may be reversed because an alternative action that is more preferable may have been identified such that the computing device, method and computer program product of an example embodiment may facilitate the performance of actions that are more preferable, even in instances in which the initial action that is identified is one that is less preferable.
In accordance with an example embodiment, a computing device is provided that is configured to automatically reverse an action indicated by an electronic message. The computing device includes a communication interface configured to receive and transmit electronic messages. The computing device also includes processing circuitry configured, for a respective electronic message, to parse the electronic message to separately identify a plurality of fields of the electronic message providing different types of information. The processing circuitry is also configured to construct a response to the electronic message that reverses the action indicated by the electronic message. The processor is further configured to construct an alternative message that provides an alternative action to the action indicated by the electronic message. In an instance in which a subsequent request indicating that the alternative action be taken is received, the processing circuitry is configured to process the subsequent request in a different manner than a request that generated the electronic message. In this example embodiment, the communication interface is configured to receive the electronic message, to transmit the response to the electronic message to a request processor that provided the electronic message, to transmit the alternative message to a source of the request and to receive the subsequent request from the source. In an example embodiment, the processing circuitry is configured to automatically construct the response to the electronic message that reverses the action indicated by the electronic message and to automatically cause the communication interface to transmit the response to the electronic message to the request processor without input from the source.
The communication interface of an example embodiment is further configured to receive the request that generated the electronic message. The computing device of this example embodiment also includes at least one database configured to store the request. The processing circuitry of this example embodiment is further configured to compare the subsequent request to the request stored by the at least one database that generated the electronic message in order to determine whether the request and the subsequent request correspond. In an instance in which the request and the subsequent request are determined to correspond, the processing circuitry is configured to cause the subsequent request to be directed to the request processor and to cause a second electronic message received from the request processor in response to the subsequent request to be provided to the source without reversal of the action indicated by the second electronic message.
The processing circuitry of an example embodiment is further configured to determine the alternative action based upon the action indicated by the electronic message. In this example embodiment, the processing circuitry is configured to parse the electronic message to identify the field that indicates a cost of a product or service. The processing circuitry of this example embodiment is further configured to determine the alternative action by determining an alternative cost of the product or service based upon the cost of the product or service identified by the electronic message.
In another example embodiment, a method is provided for automatically reversing an action indicated by an electronic message. The method includes receiving a plurality of electronic messages. For a respective electronic message, the method includes parsing the electronic message to separately identify a plurality of fields of the electronic message providing different types of information. The method also includes constructing a response to the electronic message that reverses the action indicated by the electronic message and transmitting the response to the electronic message to a request processor that provided the electronic message. The method further includes constructing an alternative message that provides an alternative action to the action indicated by the electronic message and transmitting the alternative message to a source. In response to transmission of the alternative message, the method includes receiving a subsequent request from the source. In an instance in which the subsequent request indicates that the alternative action be taken, the method includes processing the subsequent request in a different manner than the request that generated the electronic message. In an example embodiment, the response to the electronic message that reverses the action indicated by the electronic message is automatically constructed and the response to the electronic message is automatically transmitted to the request processor without input from the source.
The method of an example embodiment further includes receiving the request that generated the electronic message and storing the request in at least one database. In this example embodiment, the method also includes comparing the subsequent request to the request stored by the at least one database that generated the electronic message in order to determine whether the request and the subsequent request correspond. In an instance in which the request and the subsequent request are determined to correspond, the method of this example embodiment also includes transmitting the subsequent request to the request processor and transmitting a second electronic message received from the request processor in response to the subsequent request to the source without reversal of the action indicated by the second electronic message.
The method of an example embodiment also includes determining the alternative action based upon the action indicated by the electronic message. In this example embodiment, the method parses the electronic message by parsing the electronic message to identify the field that indicates the cost of a product or service. The method of this example embodiment also includes determining the alternative action by determining an alternative cost for the product or service based upon the cost of the product or service identified by the electronic message.
In a further example embodiment, a computer program product is provided for automatically reversing an action indicated by an electronic message. The computer program product includes a non-transitory computer readable medium having program code stored thereon with the program code including program code instructions configured, upon execution, to receive a plurality of electronic messages. For a respective electronic message, the program code also includes program code instructions configured, upon execution, to parse the electronic message to separately identify a plurality of fields of the electronic message providing different types of information. The program code further includes program code instructions configured, upon execution, to construct a response to the electronic message that reverses the action indicated by the electronic message and to cause the response to the electronic message to be transmitted to a request processor that provided the electronic message. The program code also includes program code instructions configured, upon execution, to construct an alternative message that provides an alternative action to the action indicated by the electronic message and to cause the alternative message to be transmitted to a source. In response to transmission of the alternative message, the program code includes program code instructions configured, upon execution, to receive a subsequent request from the source. In an instance in which the subsequent request indicates that the alternative action be taken, the program code further includes program code instructions configured, upon execution, to process the subsequent request in a different manner than the request that generated the electronic message.
The program code of an example embodiment also includes program code instructions configured to receive the request that generated the electronic message and to cause the request to be stored in at least one database. The program code of this example embodiment also includes program code instructions configured to compare the subsequent request to the request stored by the at least one database that generated the electronic message in order to determine whether the request and the subsequent request correspond. In an instance in which the request and the subsequent request are determined to correspond, the program code further includes program code instructions configured to cause the subsequent request to be transmitted to the request processor and to cause a second electronic message received from the request processor in response to the subsequent request to be provided to the source without reversal of the action indicated by the second electronic message.
The program code of an example embodiment also includes program code instructions configured to determine the alternative action based upon the action indicated by the electronic message. In this example embodiment, the program code instructions configured to parse the electronic message include program code instructions configured to parse the electronic message to identify the field that indicates the cost of a product or service. The program code of this example embodiment also includes program code instructions configured to determine the alternative action by determining an alternative cost to the product or service based upon the cost of the product or service identified by the electronic message.
Having thus described certain 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:
The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the inventions are shown. Indeed, these inventions 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 numbers refer to like elements throughout.
A computing device, method and computer program product are provided in order to process electronic messages exchanged between a source and a request processor and to automatically reverse an action indicated by an electronic message from the request processor in some situations. By automatically reversing an action indicated by an electronic message from the request processor without relaying that electronic message to the source and without seeking instructions or input from the source, the computing device, method and computer program product of an example embodiment conserve network resources by eliminating the network resources otherwise consumed by the transmission of the electronic message to the source. Further, the computing device, method and computer program product of an example embodiment conserve processing resources, such as processing resources of the source, which otherwise would be consumed with the receipt, storage and processing of an electronic message that was to be reversed. By automatically reversing an action indicated by an electronic message from a request processor, the computing device, method and computer program product of an example embodiment also permit an alternative action to be identified and taken in a more timely manner.
A computing device, method and computer program product of an example embodiment may be implemented in a variety of systems, one of which is depicted in
Although the computing device, method and computer program product may be employed in various applications, the computing device, method and computer program product of example embodiments are employed in conjunction with electronic messages seeking to invoke an action that may be reversed in certain circumstances. For example, the electronic messages may be communicated and processed in conjunction with telecommunication applications, content delivery and provisioning and healthcare applications, such as in conjunction with the submission and evaluation of prescription and/or medical claims, such as a prescription claim and/or a medical claim submitted by a pharmacy management system, and the provision of feedback regarding reimbursement of the pharmacy by a claims payor, e.g., an insurance company or the like, to name but a few.
The service provider 14 may be configured in various manners, but, in one embodiment, the service provider is embodied by a switch, such as a router, that includes a computing device 20 configured to parse an electronic message and to determine whether to the action proposed by the request processor 16 is to be reversed and an alternative action should, instead, be proposed. The computing device may be embodied as shown in
In an example embodiment, the memory 26 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. The memory may be configured to store information, data, applications, instructions or the like for enabling the computing device 20 to carry out various functions in accordance with example embodiments of the present invention. For example, the memory could be configured to buffer input data for processing by the processor 24. Additionally, or alternatively, the memory could be configured to store instructions for execution by the processor.
The processor 24 may be embodied in a number of different ways. For example, the processor 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. In an example embodiment, the processor may be configured to execute instructions stored in the memory 26 or otherwise accessible to the processor. As such, whether configured by hardware or by a combination of hardware and software, the processor may represent an entity (e.g., physically embodied in circuitry—in the form of processing circuitry) specifically configured to perform operations according to embodiments of the present invention while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the operations described herein.
The communication interface 28 may include one or more interface mechanisms for enabling communication with the source 12 and the request processor 16, such as one or more input/output (I/O) interfaces. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling the communications therewith.
The database 30 may be embodied by any of a variety of data storage devices such as a Network Attached Storage (NAS) device or devices, or as a separate database server or servers. The database 30 includes information accessed and stored by the processing circuitry 22 to facilitate the operations of the service provider 14. For example, the database 30 may comprise a series of tables configured to store data received from one or more other entities and/or information regarding different types of messages and/or portions of different types of messages as described below.
The operations performed by the computing device 20 embodied by the service provider 14 are depicted in accordance with an example embodiment in
As an example of a source 12, a pharmacy management system may be operated by a pharmacy in order to track the fulfillment of the various prescriptions and to submit prescription claims for reimbursement, requests for the predetermination of prescription benefits or the like via the service provider 14 to various request processors 16, such as claims processors, in order to obtain an analysis of the prescription claim or other request submitted by the pharmacy management system and to identify, for example, the patient's out of pocket costs, typically in real time or near real time. In the context of a predetermination of prescription benefits request, the claims processor responds with an indication as to whether or not the prescription claim will be reimbursed and, if so, to what extent and the service provider, in turn, provides this information to the pharmacy management system. In light of the performance of an increasing number of medical services by a pharmacy or a medical clinic housed by a pharmacy, a pharmacy management system of an example embodiment may also be configured to submit medical claims for reimbursement, requests for the predetermination of medical benefits or the like. In an instance in which the service provider returns a response regarding the reimbursement expected for a particular prescription or medical service, a pharmacy management system may direct fulfillment of the prescription or delivery of the medical service and/or direct communication between a pharmacist or other provider and a patient regarding the cost of the prescription or medical service that is not reimbursable and that must be borne by the patient. Although described herein in conjunction with a pharmacy management system, certain prescribers or other sources may also similarly communicate with the service provider, such as in conjunction with the submission and adjudication of a prescription claim request, medical claims request, predetermination of benefits request or the like. As such, the subsequent discussion applies equally to electronic messages submitted by various types of sources including pharmacy management systems and other prescribers.
The request includes a plurality of fields, each of which provides a different type of information. Although different types of requests may include different fields, the request of one example embodiment includes the following fields:
Purchase Plan Identifier—Payor ID/Routing Information
Upon receipt of the request, the request processor 16 processes the request and returns the response to the request in the form of an electronic message. The type of processing performed by the request processor is dependent upon the application in which the computing device 20, method and computer program product are employed. In an example embodiment in which the request is an electronic health care message, such as a prescription claim request, a medical claim request, a predetermination of benefits request or the like, the request processor may be owned, operated or otherwise associated with an insurance company or other payor or provider of health care benefits and, as such, may be configured to process the electronic health care message to determine, for example, the cost of a product or service, such as a prescribed medication, to a patient once the patient's health care benefits have been taken into account.
In an example embodiment, the request may be in the form of a predetermination of benefits request for a prescription that a patient is attempting to fill at a pharmacy and for which the patient has presented a prescription discount card to the pharmacist. The pharmacist may then interact with a pharmacy management system in order to transmit a predetermination of benefits request to a request processor configured to support the prescription discount program associated with or represented by the prescription discount card and to provide information to the pharmacy management system regarding the cost of the prescription to the patient once any discount provided by the prescription discount program has been taken into account.
Prescription discount cards are increasingly available to patients. Prescription discount cards may be obtained in various manners including by being downloaded by a patient, available to the patient in the office of a physician or other health care professional or mailed to the patient. The vendors of prescription discount cards generate revenue by charging an administration fee which is added to the patient's prescription price and subsequently paid to the vendor of the prescription discount card by the pharmacy. The sum of the patient's prescription price and the administration fee may be less than the cost of the prescription in the absence of the benefits provided by the prescription discount program such that the patient saves money even after taking into account the administration fee. For example, the usual and customary charge for a prescription by a pharmacy may be $72.66. Pursuant to the agreement between the pharmacy and the vendor of a prescription discount card, the discount provided by the patient's use of the prescription discount card is 70%, such that the usual and customary charge is reduced by 70% resulting in a cost to the patient utilizing the prescription discount card of $21.80 for the prescription. In this example, the administration fee charged by the vendor of the prescription discount card is $6.00. This administration fee is paid from the prescription cost borne by the patient. Thus, of the $21.80 paid by the patient, the vendor of the prescription discount card receives the $6.00 administration fee from the pharmacy and the pharmacy retains the remainder, that is, $15.80. As exemplified by the foregoing example in which the request from the source is a predetermination of benefits request related to a prescription discount card presented by a patient, the request processor 16 may be configured to determine the benefits conferred by the use of a prescription discount card, and, as such, may provide a response in the form of an electronic message to such a request indicating the cost of a product, such as a medication, or service to the patient pursuant to their use of the prescription discount card.
As such, the computing device 20 includes means, such as the processing circuitry 22, the processor 24, the communication interface 28 or the like, for receiving an electronic message generated by the request processor 16 responsive to the request. See block 44 of
In accordance with an example embodiment, the computing device 20 includes mean, such as the processing circuitry 22, the processor 24 or the like, for constructing a response to the electronic message that reverses the action indicated by the electronic message. See block 48 of
As shown in block 52 of
Once the alternative action has been determined, such as by determining an alternative cost for the product, such as a medication, or service pursuant to the alternative prescription discount program, the computing device 20 includes means, such as the processing circuitry 22, the processor 24 or the like, for constructing an alternative message that provides the alternative action. See block 54 of
Referring now to
As shown in block 72 of
Alternatively, in an instance in which the first alternative cost is not less than the cost identified by the electronic message pursuant to the prescription discount program associated with the prescription discount card, the computing device 20 of this example embodiment includes means, such as the processing circuitry 22, the processor 24 or the like, for determining a second alternative cost for the product or service. See block 78 of
In this instance, the computing device 20 also includes means, such as the processing circuitry 22, the processor 24 or the like, for constructing the alternative message so as to reference the second alternative cost for the product or service and to indicate the availability of the second alternative cost pursuant to the alternative prescription discount program along with an indication that the second alternative cost is less than the cost for the same product or service available pursuant to the prescription discount program associated with the prescription discount card. See block 80 of
In response to the transmission of the alternative message to the source 12, the computing device 20, includes means, such as the processing circuitry 22, the processor 24, the communication interface 28 or the like, for receiving a subsequent request from the source. See block 58 of
In the example embodiment depicted in
The request processor 16 then processes the subsequent request and transmits a second electronic message in response thereto. Since the original request and the subsequent request correspond, the second electronic message may also correspond, such as by being identical, to the prior electronic request provided by the request processor in response to the original request. Among other information, the second electronic request may include the cost to the patient for fulfillment of the product or service pursuant to the prescription discount program associated with the prescription discount card. As such, the computing device 20 of this example embodiment includes means, such as the processing circuitry 22, the processor 24, the communication interface 28 or the like, for receiving the second electronic message from the request processor and for causing the second electronic message to be transmitted to the source 12 without reversal of the action indicated by the second electronic message, that is, authorization of the fulfillment of the prescription at the cost indicated in the second electronic message. See block 64 of
Alternatively, in an instance in which the request and the subsequent request are determined as described above in conjunction with block 60 of
In either instance and as shown by the signal designated 6b(2) in the signal flow diagram of
Upon receipt of the response to the subsequent request and in an instance in which the patient elected to utilize the alternative prescription discount program, the patient may purchase the product, such as medication, or service at the alternative cost, thereby saving the patient money in comparison to the cost otherwise paid by the patient as a result to their use of the prescription discount card. The pharmacy then remits to the alternative prescription discount program a fee, such as a predefined fee associated with the use of the alternative prescription discount program in conjunction with the fulfillment of a prescription. The pharmacy retains the remainder of the price paid by the patient. By defining the fee so as to be less than the administration fee charged by the vendors of prescription drug cards, the pharmacy may also retain more money in an instance in which the alternative prescription discount program is utilized then in an instance in which a prescription discount card is utilized.
As described above, the computing device 20, method and computer program product increase the efficiency with which messages are exchanged, thereby conserving network and processing resources associated with the exchange of messages. In this regard, the computing device, method and computer program product are configured to automatically reverse an action indicated by an electronic message. By automatically reversing an action, the number of messages that are constructed, transmitted and received may be reduced relative to an instance in which a message must first returned to the source 12 which then issues a reversal message.
As noted above,
Accordingly, blocks of the flowcharts 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 flowcharts, 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. In some embodiments, certain ones of the operations above may be modified or further amplified and additional optional operations may be included. It should be appreciated that each of the modifications, optional additions or amplifications below may be included with the operations above either alone or in combination with any others among the features described herein.
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. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
This application is a continuation of and claims priority to U.S. application Ser. No. 16/043,401, filed Jul. 24, 2018, and entitled, “Computing System And Method For Automatically Reversing An Action Indicated By An Electronic Message,” the entire contents of which are hereby incorporated by reference.
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 |
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 |
8326773 | Bellamy | Dec 2012 | B1 |
8412537 | Fenton et al. | Apr 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 |
8738399 | Abou Nader et al. | May 2014 | B1 |
8786650 | Eller et al. | Jul 2014 | B1 |
8984059 | Johnson | Mar 2015 | B2 |
9026507 | Shraim et al. | May 2015 | B2 |
9100793 | Johnson | Aug 2015 | B2 |
9171322 | Spievak | Oct 2015 | B2 |
9356947 | Shraim et al. | May 2016 | B2 |
10157262 | Pinsonneault | Dec 2018 | 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 | 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 |
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 |
20020147614 | Doerr et al. | Oct 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 |
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 |
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 |
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 |
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 |
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 | 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 | May 2008 | A1 |
20080152107 | Mendiola | Jun 2008 | A1 |
20080215361 | Nunnari et al. | Sep 2008 | A1 |
20080262948 | Grady et al. | Oct 2008 | A1 |
20090030719 | Nadas et al. | Jan 2009 | A1 |
20090064330 | Shraim et al. | Mar 2009 | A1 |
20090094051 | Ard et al. | Apr 2009 | A1 |
20090100099 | Buckwaiter | Apr 2009 | A1 |
20090112707 | Weiss et al. | Apr 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 |
20100293236 | Wisner et al. | Nov 2010 | 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 |
20130041968 | Cohen et al. | Feb 2013 | A1 |
20130103602 | Melnick et al. | Apr 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 |
20140278456 | Milosevich et al. | Sep 2014 | 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 | Jun 2015 | A1 |
20150195224 | Karnin | 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 |
20160213512 | Palanker | Jul 2016 | A1 |
20160267544 | Flood | Sep 2016 | A1 |
20160267545 | Glass | Sep 2016 | A1 |
20160307195 | Cantwell et al. | Oct 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 |
20180012244 | Leonardi | Jan 2018 | A1 |
20180366810 | Nero et al. | Dec 2018 | A1 |
20190213212 | Adato et al. | Jul 2019 | A1 |
20190385733 | Kaye et al. | Dec 2019 | A1 |
20190385734 | Pinsonneault | Dec 2019 | A1 |
20210319887 | Derrick, Jr. et al. | Oct 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 |
100793852 | Jan 2008 | 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 | Jul 2007 | WO |
WO 2008092109 | Jul 2008 | WO |
Entry |
---|
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 dated 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 dated Feb. 25, 2019, 5 pages. |
Advisory Action for U.S. Appl. No. 15/427,746 dated 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. |
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 dated 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 dated Jan. 31, 2011, 10 pages. |
Final Office Action for U.S. Appl. No. 12/415,062 dated Oct. 6, 2011, 18 pages. |
Final Office Action for U.S. Appl. No. 12/555,589 dated Apr. 11, 2012, 17 pages. |
Final Office Action for U.S. Appl. No. 12/560,071 dated Aug. 28, 2015, 8 pages. |
Final Office Action for U.S. Appl. No. 12/560,071 dated Nov. 8, 2012, 11 pages. |
Final Office Action for U.S. Appl. No. 12/570,982 dated Apr. 11, 2014, 22 pages. |
Final Office Action for U.S. Appl. No. 12/570,982 dated Aug. 28, 2015, 10 pages. |
Final Office Action for U.S. Appl. No. 12/570,982 dated Jan. 17, 2013, 19 pages. |
Final Office Action for U.S. Appl. No. 12/730,015 dated Aug. 14, 2012, 10 pages. |
Final Office Action for U.S. Appl. No. 12/978,898 dated May 16, 2013, 16 pages. |
Final Office Action for U.S. Appl. No. 13/721,890 dated Jun. 24, 2015, 14 pages. |
Final Office Action for U.S. Appl. No. 13/721,890 dated Nov. 25, 2016, 12 pages. |
Final Office Action for U.S. Appl. No. 13/782,909 dated May 31, 2016, 18 pages. |
Final Office Action for U.S. Appl. No. 13/782,909 dated Oct. 6, 2015, 24 pages. |
Final Office Action for U.S. Appl. No. 13/804,175 dated Oct. 6, 2015, 6 pages. |
Final Office Action for U.S. Appl. No. 13/827,676 dated Jul. 13, 2015, 17 pages. |
Final Office Action for U.S. Appl. No. 14/090,113 dated Jan. 6, 2016, 18 pages. |
Final Office Action for U.S. Appl. No. 14/090,122 dated Apr. 22, 2016, 13 pages. |
Final Office Action for U.S. Appl. No. 14/145,027 dated Nov. 19, 2015, 12 pages. |
Final Office Action for U.S. Appl. No. 14/193,294 dated May 2, 2016, 29 pages. |
Final Office Action for U.S. Appl. No. 14/218,326 dated 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 dated Nov. 28, 2018, 24 pages. |
Final Office Action for U.S. Appl. No. 15/427,746 dated Apr. 15, 2019, 9 pages. |
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-PRESCRIPIIONS, 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 dated 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 dated Jun. 21, 2012, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 12/570,982 dated Jun. 20, 2012, 10 pages. |
Non-Final Office Action for U.S. Appl. No. 14/193,294 dated 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-fmal Office Action for U.S. Appl. No. 12/140,015 dated Oct. 8, 2010, 9 pages. |
Non-fmal Office Action for U.S. Appl. No. 12/189,650 dated Jan. 22, 2010, 11 pages. |
Non-fmal Office Action for U.S. Appl. No. 12/189,654 dated Jan. 22, 2010, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 12/388,956 dated Feb. 3, 2011, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 12/415,062 dated Mar. 30, 2011, 23 pages. |
Non-Final Office Action for U.S. Appl. No. 12/555,589 dated Dec. 9, 2011, 12 pages. |
Non-Final Office Action for U.S. Appl. No. 12/560,071 dated Sep. 23, 2014, 17 pages. |
Non-Final Office Action for U.S. Appl. No. 12/570,982 dated Sep. 12, 2013, 22 pages. |
Non-Final Office Action for U.S. Appl. No. 12/730,015 dated Mar. 6, 2012, 9 pages. |
Non-Final Office Action for U.S. Appl. No. 12/956,411 dated Jan. 24, 2011, 9 pages. |
Non-Final Office Action for U.S. Appl. No. 12/978,898 dated Feb. 6, 2013, 12 pages. |
Non-Final Office Action for U.S. Appl. No. 12/982,395 dated Dec. 11, 2012, 13 pages. |
Non-Final Office Action for U.S. Appl. No. 13/721,890 dated Jan. 9, 2015, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 13/721,890 dated Jun. 14, 2016, 9 pages. |
Non-fmal Office Action for U.S. Appl. No. 13/782,909 dated Feb. 11, 2016, 17 pages. |
Non-Final Office Action for U.S. Appl. No. 13/827,676 dated Dec. 26, 2014, 13 pages. |
Non-fmal Office Action for U.S. Appl. No. 13/827,676 dated Dec. 30, 2015, 23 pages. |
Non-Final Office Action for U.S. Appl. No. 14/145,027 dated Mar. 23, 2015, 13 pages. |
Non-Final Office Action for U.S. Appl. No. 15/137,371 dated May 29, 2018, 19 pages. |
Non-Final Office Action for U.S. Appl. No. 15/427,746 dated 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 dated Mar. 26, 2021, 45 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/832,318 dated 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 dated Jul. 19, 2010, 13 pages. |
Notice of Allowance for U.S. Appl. No. 12/140,015 dated Jun. 10, 2011, 10 pages. |
Notice of Allowance for U.S. Appl. No. 12/165,221 dated Nov. 16, 2010, 6 pages. |
Notice of Allowance for U.S. Appl. No. 12/189,650 dated Aug. 13, 2010, 11 pages. |
Notice of Allowance for U.S. Appl. No. 12/388,956 dated Jun. 14, 2011, 9 pages. |
Notice of Allowance for U.S. Appl. No. 12/956,411 dated Aug. 5, 2011, 8 pages. |
Notice of Allowance for U.S. Appl. No. 12/982,395 dated 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 dated May 2, 2019, 11 pages. |
Notice of Allowance for U.S. Appl. No. 15/427,746 dated Dec. 4, 2019, 5 pages. |
Notice of Allowance for U.S. Appl. No. 15/427,746 dated Jul. 31, 2019, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 14,643,468, dated Oct. 24, 2018, 22 pages. |
Notice of Allowance received for U.S. Appl. No. 14/181,011, dated 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 dated Apr. 8, 2015, 9 pages. |
Office Action for U.S. Appl. No. 13/782,909 dated Jun. 25, 2015, 16 pages. |
Office Action for U.S. Appl. No. 13/804,175 dated Mar. 13, 2015, 9 pages. |
Office Action for U.S. Appl. No. 14/090,113 dated Jun. 18, 2015, 14 pages. |
Office Action for U.S. Appl. No. 14/090,122 dated Oct. 21, 2016, 12 pages. |
Office Action for U.S. Appl. No. 14/090,122 dated Sep. 11, 2015, 10 pages. |
Office Action for U.S. Appl. No. 14/181,011 dated Feb. 29, 2016, 23 pages. |
Office Action for U.S. Appl. No. 14/181,011 dated Mar. 20, 2017, 28 pages. |
Office Action for U.S. Appl. No. 14/181,011 dated Oct. 20, 2016, 28 pages. |
Office Action for U.S. Appl. No. 14/181,011 dated Sep. 12, 2017, 17 pages. |
Office Action for U.S. Appl. No. 14/193,294 dated Dec. 17, 2015, 21 pages. |
Office Action for U.S. Appl. No. 14/218,326 dated 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. |
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. |
United States Patent and Trademark Office, Advisory Action for U.S. Appl. No. 15/422,184, dated Jun. 25, 2019, 4 pages, U.S.A. |
United States Patent and Trademark Office, Advisory Action for U.S. Appl. No. 15/422,184, dated Mar. 26, 2020, 5 pages, U.S.A. |
United States Patent and Trademark Office, Advisory Action for U.S. Appl. No. 15/925,011, dated Jan. 31, 2020, 3 pages, U.S.A. |
United States Patent and Trademark Office, Advisory Action for U.S. Appl. No. 15/925,948, dated Jan. 31, 2020, 4 pages, U.S.A. |
United States Patent and Trademark Office, Notice of Allowability received for U.S. Appl. No. 15/422,184, dated Nov. 16, 2020, 2 pages, U.S.A. |
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 15/422,184, dated 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, dated Nov. 5, 2020, 22 pages, U.S.A. |
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 15/925,011, dated Apr. 8, 2020, 17 pages, U.S.A. |
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 15/925,948, dated 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, dated 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, dated 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. |
CMS Updates Drug Dashboards with Prescription Drug Pricing and Spending Data, Data, Medicare Part D, Prescription drugs (Mar. 14, 2019). |
How to Estimate the Cost of a Prescription. Pam Olson, Sr. Client Services Executive, Navitus Health Solutions (Year: 2015). |
United States Patent and Trademark Office, Final Office Action received for Application No. 16/453,509, dated Aug. 18, 2021, 16 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, Notice of Allowance received for U.S. Appl. No. 16/043,401, dated Aug. 10, 2020, 9 pages, U.S.A. |
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). |
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). |
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). |
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, Corrected Notice of Allowability received for U.S. Appl. No. 15/085,166, dated Sep. 20, 2021, 6 pages, U.S. |
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. |
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, 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. |
U.S. Appl. No. 16/043,401, filed Jul. 24, 2018, U.S. Pat. No. 10,862,832, Patented. |
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, 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, 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, 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, Non-Final Office Action received for U.S. Appl. No. 16/867,286, dated Feb. 22, 2022, 38 pages, U.S. |
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. |
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 payement 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%F2010%2 . . . > on Feb. 20, 2022 at 3:00 pm, 2 pages. |
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, 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. 16/551,962, dated Mar. 1, 2022, 14 pages, US. |
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, US. |
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. |
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. 218, 8 pages, BioMed Central LTD, UK. |
Google Patents Search (including Web Search History, Prior Art Search Printable History Generator) on “pharmaby payment 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=refills&q=error+code&country=US&before=filing:20131231> 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. |
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 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. |
Number | Date | Country | |
---|---|---|---|
Parent | 16043401 | Jul 2018 | US |
Child | 17092705 | US |