# US 8,788,296 B1 · Systems and methods for providing notifications of availability of generic drugs or products > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,788,296 B1 - Document ID: US8788296B1 - Status: Granted - Kind: B1 - Application number: 12/696,717 - Filed: 2010-01-29 - Granted: 2014-07-22 - Earliest claimed: 2010-01-29 - Assignees: McKesson Financial Holdings - Applicants: James Morgan Ringold - Inventors: James Morgan Ringold - Web page: https://patentgrep.com/patent/US8788296B1 ## CPC - G06Q 40/08: Insurance - G06Q 10/10: Office automation; Time management - G16H 20/10: relating to drugs or medications, e.g. for ensuring correct administration to patients - G16H 80/00: ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA ## Abstract Systems and methods may provide notifications of availability of generic drugs or products. The systems and methods may include receiving, from a healthcare provider computer, a healthcare claim transaction request that identifies a product for a patient; determining that the product identified by the healthcare claim transaction request is a non-generic product or a branded product; determining that a generic equivalent for the product identified by the healthcare claim transaction request will become available on a future date; generating a generic notification message indicating the availability of generic equivalent for the product on the future date; and delivering or directing a delivery of the generic notification message. ## Claims ### Claim 1 A computer-implemented method, comprising: receiving, from a healthcare provider computer, a healthcare claim transaction request that identifies a product for a patient; determining that the product identified by the healthcare claim transaction request is a non-generic product or a branded product; determining that a generic equivalent for the product identified by the healthcare claim transaction request will become available on a future date by accessing a database comprising one or more future dates of an availability of one or more generic equivalents to the non-generic drug or the branded product; generating a generic notification message indicating the availability of the generic equivalent for the product on the future date; delivering or directing a delivery of the generic notification message, wherein the above operations are performed by one or more computers associated with a service provider. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, further comprising: prior to generating the generic notification message, further determining that the future date is within a predetermined time period from a current date associated with the healthcare claim transaction request, wherein the above operation is performed by one or more computers associated with a service provider. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, wherein the generic notification message further specifies an expected price or savings associated with the generic equivalent. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, wherein the healthcare provider computer is associated with one or more particular pharmacy locations, wherein the future date is based upon an expected delivery date of the generic equivalent to the one or more particular pharmacy locations. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, wherein the generic notification message is delivered to the healthcare provider computer. ### Claim 6 (depends on 5) The computer-implemented method of claim 5, further comprising: transmitting a reject response to the healthcare provider computer in response to the received healthcare claim transaction request, the reject response including the generic notification message, wherein the above operation is performed by one or more computers associated with a service provider. ### Claim 7 (depends on 6) The computer-implemented method of claim 6, wherein the healthcare claim transaction request is a first healthcare claim transaction request, and further comprising: storing information indicating a prior rejection of the healthcare claim transaction request identifying the product for the patient; receiving, from the healthcare provider computer, a second healthcare claim transaction request that identifies the product for the patient, the product being a same product as for the first healthcare claim transaction request; identifying a presence of the stored information indicating the prior rejection associated with the product for the patient; and delivering the second healthcare claim transaction request to a claims processor computer for adjudication, wherein the above operations are performed by one or more computers associated with a service provider. ### Claim 8 (depends on 1) The computer-implemented method of claim 1, wherein the generic notification message is delivered by at least one of: (i) via email, (ii) to a facsimile, (iii) to a printer, (iv) via text message to a cellular phone or personal communications device, (v) via Internet message or presentation, or (v) via paper mailing. ### Claim 9 (depends on 1) The computer-implemented method of claim 1, wherein the generic notification message is delivered to at least one of (i) a pharmacy; (ii) a healthcare provider; or (iii) the patient. ### Claim 10 (depends on 1) The computer-implemented method of claim 1, wherein the product is identified in the healthcare claim transaction request by a National Drug Code (NDC), a Universal Product Code, or a SKU number, wherein the product identified by the healthcare claim transaction request is determined to be a non-generic product or a branded product based upon the NDC, UPC, or SKU number. ### Claim 11 A system, comprising: at least one memory operable to store computer-executable instructions; and at least one processor configured to access the at least one memory and execute the computer-executable instructions to: receive, from a healthcare provider computer, a healthcare claim transaction request that identifies a product for a patient, determine that the product identified by the healthcare claim transaction request is a non-generic product or a branded product, determine that a generic equivalent for the product identified by the healthcare claim transaction request will become available on a future date by accessing a database comprising one or more future dates of an availability of one or more generic equivalents to the non-generic drug or the branded product, generate a generic notification message indicating the availability of the generic equivalent for the product on the future date, and deliver or direct a delivery of the generic notification message. ### Claim 12 (depends on 11) The system of claim 11, wherein the at least one processor is further configured to execute the computer-executable instructions to: prior to generating the generic notification message, further determine that the future date is within a predetermined time period from a current date associated with the healthcare claim transaction request. ### Claim 13 (depends on 11) The system of claim 11, wherein the generic notification message further specifies an expected price or savings associated with the generic equivalent. ### Claim 14 (depends on 11) The system of claim 11, wherein the healthcare provider computer is associated with one or more particular pharmacy locations, wherein the future date is based upon an expected delivery date of the generic equivalent to the one or more particular pharmacy locations. ### Claim 15 (depends on 11) The system of claim 11, wherein the generic notification message is delivered to the healthcare provider computer. ### Claim 16 (depends on 15) The system of claim 15, wherein the at least one processor is further configured to execute the computer-executable instructions to: transmit a reject response to the healthcare provider computer in response to the received healthcare claim transaction request, the reject response including the generic notification message. ### Claim 17 (depends on 16) The system of claim 16, wherein the healthcare claim transaction request is a first healthcare claim transaction request, and wherein the at least one processor is further configured to execute the computer-executable instructions to: store information indicating a prior rejection of the healthcare claim transaction request identifying the product for the patient; receive, from the healthcare provider computer, a second healthcare claim transaction request that identifies the product for the patient, the product being a same product as for the first healthcare claim transaction request; identify a presence of the stored information indicating the prior rejection associated with the product for the patient; and deliver the second healthcare claim transaction request to a claims processor computer for adjudication. ### Claim 18 (depends on 11) The system of claim 11, wherein the generic notification message is delivered by at least one of: (i) via email, (ii) to a facsimile, (iii) to a printer, (iv) via text message to a cellular phone or personal communications device, (v) via Internet message or presentation, or (v) via paper mailing. ### Claim 19 (depends on 11) The system of claim 11, wherein the generic notification message is delivered to at least one of (i) a pharmacy; (ii) a healthcare provider; or (iii) the patient. ### Claim 20 (depends on 11) The system of claim 11, wherein the product is identified in the healthcare claim transaction request by a National Drug Code (NDC), a Universal Product Code, or a SKU number, wherein the product identified by the healthcare claim transaction request is determined to be a non-generic product or a branded product based upon the NDC, UPC, or SKU number.