# US 2020/0402060 A1 · Medical benefit fraud protection system and method

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

- Number: US 2020/0402060 A1
- Document ID: US20200402060A1
- Status: Published application
- Kind: A1
- Application number: 16/448,559
- Filed: 2019-06-21
- Published: 2020-12-24
- Earliest claimed: 2019-06-21
- Assignees: Zero Copay Program, Inc.
- Applicants: Zero Copay Program, Inc.
- Inventors: Yuriy Davydov
- Web page: https://patentgrep.com/patent/US20200402060A1

## CPC

- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06F 21/31: User authentication
- G06Q 20/023: {the neutral party being a clearing house}
- G06Q 20/102: {Bill distribution or payments}
- G06Q 20/387: {Payment using discounts or coupons (relating to marketing G06Q30/02)}
- G06Q 40/08: Insurance
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- G06F 2221/2137: Time limited access, e.g. to a computer or data
- G06Q 10/10: Office automation; Time management
- G06Q 20/34: using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G16H 20/10: relating to drugs or medications, e.g. for ensuring correct administration to patients
- G16H 20/30: relating to physical therapies or activities, e.g. physiotherapy, acupressure or exercising
- G16H 40/00: ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- H04L 63/102: {Entity profiles}
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Medical benefit fraud protection system and method are disclosed herein. The method, in an embodiment, performs the following steps: receiving a provisioning request from a first processor controlled by a product related entity, wherein the provisioning request comprises a benefit specification from the product related entity, including limitations of use; configuring a benefit processing business logic of the benefit processing system with the provisioning request; receiving a benefit submission from a second processor controlled by a dispensary entity; determining an approval decision or a denial decision of the benefit submission based on the limitations of use in the benefit specification; and processing or denying the benefit submission based on such determination.

## Claims

### Claim 1

A medical benefit fraud protection system comprising:
one or more data storage devices storing a plurality of instructions configured to be executed to:
receive a provisioning request from a first processor controlled by a product related entity, the provisioning request comprising a medical benefit specification from the product related entity, the medical benefit specification comprising a plurality of limitations of use;
configure a benefit processing business logic with the provisioning request, the provisioning occurring during continued execution of the instructions;
receive a benefit submission from a second processor controlled by a dispensary entity, the benefit submission relating to the medical benefit specification;
determine an approval decision or a denial decision of the benefit submission based on the limitations of use of the medical benefit specification;
in response to determining an approval decision of the benefit submission, process the benefit submission using the benefit processing business logic based on the benefit specification;
in response to determining a denial decision of the benefit submission, deny the benefit submission;
generate a benefit transaction record or a denial record related to the benefit submission; and
display a first access interface to the product related entity and a second access interface to the dispensing entity, the displaying occurring during the execution of the instructions, wherein the first and second access interfaces are accessible during the execution and comprise different views to different portions of the benefit transaction record related to the benefit submission.

### Claim 2 (depends on 1)

The medical benefit fraud protection system of claim 1, wherein the limitations of use in the benefit specification limit the benefit specification to one or more patients.

### Claim 3 (depends on 1)

The medical benefit fraud protection system of claim 1, wherein the limitations of use in the benefit specification limit the benefit specification to a period of time.

### Claim 4 (depends on 1)

The medical benefit fraud protection system of claim 1, wherein the limitations of use in the benefit specification limit the benefit specification to a number of uses.

### Claim 5 (depends on 1)

The medical benefit fraud protection system of claim 1, wherein the limitations of use in the benefit specification limit the benefit specification to one or more patients for a period of time and a number of uses.

### Claim 6 (depends on 1)

The medical benefit fraud protection system of claim 1, wherein provisioning the benefit processing business logic comprises generating one or more business rules based on the provisioning request.

### Claim 7 (depends on 1)

The medical benefit fraud protection system of claim 1, wherein the product related entity comprises a manufacturer of the medical benefit specification.

### Claim 8 (depends on 1)

The medical benefit fraud protection system of claim 1, wherein the benefit submission is received via a clearinghouse.

### Claim 9 (depends on 1)

The medical benefit fraud protection system of claim 1, wherein the benefit submission is not received via a clearinghouse.

### Claim 10 (depends on 1)

The medical benefit fraud protection system of claim 1, wherein the plurality of instructions are further configured to be executed to receive a plurality of provisioning requests from a plurality of product related entities, the plurality of provisioning requests comprising specifications of a plurality of benefit specifications from the plurality of product related entities.

### Claim 11 (depends on 10)

The medical benefit fraud protection system of claim 10, wherein the plurality of instructions are further configured to be executed to provision the benefit processing business logic of the medical benefit fraud protection system with the plurality of provisioning requests, the provisioning occurring during continued operation of the medical benefit fraud protection system.

### Claim 12

A medical benefit fraud protection method, the method comprising:
receiving a provisioning request from a first processor controlled by a product related entity, the provisioning request comprising a benefit specification from the product related entity, the benefit specification comprising a plurality of limitations of use;
configuring a benefit processing business logic with the provisioning request;
receiving a benefit submission from a second processor controlled by a dispensary entity, the benefit submission relating to the benefit specification from the product related entity;
determining an approval decision or a denial decision of the benefit submission based on the limitations of use of the benefit specification;
in response to determining an approval decision of the benefit submission, processing the benefit submission using the benefit processing business logic based on the benefit specification;
in response to determining a denial decision of the benefit submission, denying the benefit submission;
generating a benefit transaction record related to the benefit submission; and
displaying a first access interface to the product related entity and a second access interface to the dispensing entity, the displaying occurring during execution, wherein the first and second access interfaces are accessible and comprise different views to different portions of the benefit transaction record related to the benefit submission.

### Claim 13 (depends on 12)

The medical benefit fraud protection method of claim 12, wherein the limitations of use in the benefit specification limit the benefit specification to one or more patients.

### Claim 14 (depends on 12)

The medical benefit fraud protection method of claim 12, wherein the limitations of use in the benefit specification limit the benefit specification to a period of time.

### Claim 15 (depends on 12)

The medical benefit fraud protection method of claim 12, wherein the limitations of use in the benefit specification limit the benefit specification to a number of uses.

### Claim 16 (depends on 12)

The medical benefit fraud protection method of claim 12, wherein the limitations of use in the benefit specification limit the benefit specification to one or more patients for a period of time and a number of uses.

### Claim 17 (depends on 12)

The medical benefit fraud protection method of claim 12, wherein provisioning the benefit processing business logic comprises generating one or more business rules based on the provisioning request.

### Claim 18

A medical benefit fraud protection system comprising:
one or more data storage devices storing a plurality of computer-readable instructions configured to be executed to:
receive a provisioning request from a product related entity, the provisioning request comprising a medical benefit specification from the product related entity, the medical benefit specification comprising a plurality of limitations of use associated with a product marketed by the product related entity;
receive a benefit submission from a medical merchant, the benefit submission relating to the medical benefit specification;
determine whether the benefit submission is approved or denied based on the limitations of use;
in response to the determination of approval, process the benefit submission, generate a benefit transaction record, and cause the benefit transaction record to be graphically indicated; and
in response to the determination of denial, deny the benefit submission and generate a benefit denial record, and cause the benefit denial record to be graphically indicated.

### Claim 19 (depends on 18)

The medical benefit fraud protection system of claim 18, wherein the limitations of use of the benefit specification limit the benefit specification to a unique identity of a customer.

### Claim 20 (depends on 18)

The medical benefit fraud protection system of claim 18, wherein the limitations of use of the benefit specification limit the benefit specification to a designated period of time.
