# US 2026/0088147 A1 · System and method for seamless prescription medication discounting

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0088147 A1
- Document ID: US20260088147A1
- Status: Published application
- Kind: A1
- Application number: 18/891,765
- Filed: 2024-09-20
- Published: 2026-03-26
- Earliest claimed: 2024-09-20
- Inventors: Shawn Ohri; Nathan Daugherty; Rajasekar Ramaswamy; Byung Joon Min
- Web page: https://patentgrep.com/patent/US20260088147A1

## CPC

- G16H 20/10: relating to drugs or medications, e.g. for ensuring correct administration to patients
- G06Q 30/0207: Discounts or incentives, e.g. coupons or rebates
- G06Q 30/0224: {based on user history}
- G06Q 40/08: Insurance
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- 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

## Abstract

A system and method for a seamless provision of discounting for prescription services that are not eligible for financial coverage by a plan, such as a Medicare Part D plan. The system and method take denials from Pharmacy Benefit Managers (PBMs) and seamlessly provides to end users (patients) a discounted cost for the denied coverage of the prescription. Denials of coverage are transmitted to a switch server where rejection codes are detected at the switch server and relayed to the seamless server. The seamless server then provides an approval instead of the original PBM.

## Claims

### Claim 1

A method for seamless provision of discount prescription information comprising:
transmitting prescription data from a pharmacy server to a switch server;
transmitting the prescription data from the switch server to a pharmacy benefit manager (PBM) server;
determining at the PBM server if financial coverage will be provided based on the prescription data;
transmitting a rejection code to the switch server if it is determined that coverage will not be provided;
processing the rejection code at the switch server to determine if the rejection code corresponds to an actionable rejection code;
transmitting the rejection code from the switch server to the seamless server based on the processing of the rejection code;
transmitting from the seamless server to the switch server destination information for sending the patient information and the medication information, wherein the destination information is at least one discount server;
routing the patient information and the medication information to the discount server from the switch server;
determining confirmation of coverage at the discount server using the patient information and the medication information;
transmitting from the discount server to the switch server confirmation of coverage; and
transmitting from the switch server to the pharmacy server the confirmation of coverage.

### Claim 2 (depends on 1)

The method of claim 1, wherein there is more than one discount server.

### Claim 3 (depends on 2)

The method of claim 2, further comprising processing at the seamless server the rejection code to determine which discount server to provide destination information.

### Claim 4 (depends on 3)

The method of claim 3, wherein the rejection code is determined based on the medication information.

### Claim 5 (depends on 1)

The method of claim 1, wherein the rejection code is one of a plurality of rejection codes, wherein not all rejection codes are transmitted to the seamless server.

### Claim 6 (depends on 1)

The method of claim 1, wherein the prescription data comprises financial coverage information, patient information, and medication information.

### Claim 7 (depends on 1)

The method of claim 1, wherein the destination information comprises new BIN information.

### Claim 8 (depends on 1)

The method of claim 1, further comprising transmitting confirmation of coverage to the seamless server in addition to transmitting confirmation of coverage to the switch server.

### Claim 9 (depends on 1)

The method of claim 1, wherein more than one rejection code is generated for the prescription data.

### Claim 10 (depends on 9)

The method of claim 9, wherein each of the more than one rejection code is determined to be actionable by the discount server.

### Claim 11

A system for seamless provision of discount prescription information comprising:
a pharmacy server adapted to receive and transmit prescription data;
a switch server operably connected to the pharmacy server, wherein the switch server is adapted to receive and transmit prescription data;
a pharmacy benefit manager (PBM) server adapted to receive prescription;
wherein the PBM server is adapted to process prescription data to determine if financial coverage will be provided and if financial coverage will not be provided to generate a rejection code based in part on the prescription data;
a seamless server adapted to receive processed rejection codes that are rejection codes received by the switch server and processed by the switch server to determine if the received rejections are actionable rejection codes, wherein the seamless server is adapted to transmit destination data related to a discount server to the switch server based on received processed rejection codes; and
a discount server adapted to provide confirmation of coverage to the switch server based on patient information and medication information provided by the seamless server.

### Claim 12 (depends on 11)

The system of claim 11, wherein there is at least one other discount server.

### Claim 13 (depends on 12)

The system of claim 12, wherein the seamless server is adapted to process the rejection code to determine which discount server to provide destination information to.

### Claim 14 (depends on 13)

The system of claim 13, wherein the rejection code is determined based on the medication information.

### Claim 15 (depends on 11)

The system of claim 11, wherein the rejection code is one of a plurality of rejection codes, wherein not all rejection codes are transmitted to the seamless server.

### Claim 16 (depends on 11)

The system of claim 11, wherein the prescription data comprises financial coverage information, patient information, and medication information.

### Claim 17 (depends on 11)

The system of claim 11, wherein the destination information comprises new BIN information.

### Claim 18 (depends on 11)

The system of claim 11, wherein the discount server is adapted to provide confirmation of coverage to the seamless server in addition to the switch server.

### Claim 19 (depends on 18)

The system of claim 18, wherein more than one rejection code is generated for the prescription data.

### Claim 20 (depends on 19)

The system of claim 19, wherein each of the more than one rejection code is determined to be actionable by the discount server.
