# US 2003/0078809 A1 · Prescription approval 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 2003/0078809 A1
- Document ID: US20030078809A1
- Status: Published application
- Kind: A1
- Application number: 10/032,909
- Filed: 2001-10-18
- Published: 2003-04-24
- Earliest claimed: 2001-10-18
- Inventors: Jude LaCour
- Web page: https://patentgrep.com/patent/US20030078809A1

## CPC

- G06Q 10/10: Office automation; Time management
- G16H 20/10: relating to drugs or medications, e.g. for ensuring correct administration to patients
- G16H 40/67: for remote operation
- 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

A network-based system and method for reviewing and approving or declining orders, particularly for prescription drugs includes a server and an associated memory accessible over the network. Doctors access the server to review customer order requests and medical histories. If the prescription is warranted based on the customer medical condition, the doctor approves the order for further processing and delivery.

## Claims

### Claim 1

A system for processing a customer prescription by a user via a remote client, the system comprising:
a server coupled to a network; and
a memory coupled to the server, the memory containing stored programming instructions that, when executed by the server, cause the server to:
(i) present, on a display associated with the client, information related to a prescription request;
(ii) receive user approval or disapproval of the prescription request; and
(iii) process the prescription request based upon the user approval or disapproval.

### Claim 2 (depends on 1)

The system of claim 1, wherein the information presented related to the prescription request comprises medical information related to the customer.

### Claim 3 (depends on 2)

The system of claim 2, wherein the information presented related to the prescription request further comprises a customer medical history.

### Claim 4 (depends on 3)

The system of claim 3, wherein the stored programming instructions further cause the server to send an approval or disapproval email to the customer.

### Claim 5 (depends on 4)

The system of claim 4, wherein the stored programming instructions further cause the server request from the client a user name and password, and to determine whether the user is an authorized user as a function of the user name and password.

### Claim 6 (depends on 5)

The system of claim 5, wherein the user is a doctor.

### Claim 7

A method for processing a customer prescription request by a user, the method comprising:
providing the customer prescription request to the user accessing a server via a remote client over a network;
providing customer medical information to the user over the network;
receiving a user approval or disapproval based upon the customer prescription request and customer medical information; and
processing the customer prescription request based upon the user approval or disapproval.

### Claim 8 (depends on 7)

The method of claim 7, wherein the user is a doctor.

### Claim 9 (depends on 8)

The method of claim 8, wherein the medical information presented comprises a customer medical history.

### Claim 10 (depends on 9)

The method of claim 9 further comprising requesting a password from the doctor before providing the customer medical information or the customer prescription request to the doctor.

### Claim 11 (depends on 10)

The method of claim 10, wherein the customer prescription request is submitted to the server by the customer accessing the server via a client over the network.

### Claim 12 (depends on 10)

The method of claim 10, wherein the customer medical information is submitted to the server by the customer accessing the server via a client over the network.

### Claim 13 (depends on 10)

The method of claim 10, wherein the customer prescription request is submitted by the customer via email.

### Claim 14 (depends on 10)

The method of claim 10, wherein the customer medical information is submitted by the customer via email.

### Claim 15 (depends on 10)

The method of claim 10, wherein the customer medical information is submitted to the server by the doctor over the network.

### Claim 16 (depends on 10)

The method of claim 10, wherein processing the prescription request further comprises sending an email to the customer indicating whether the prescription request has been approved or declined.

### Claim 17 (depends on 16)

The method of claim 16, wherein processing the prescription request further comprises shipping a requested prescription drug to the customer.

### Claim 18

A system for processing a customer prescription request by a user via a remote client, the system comprising:
a database containing the customer prescription;
a database containing medical information associated with a customer requesting the customer prescription;
a means for presenting the customer prescription to the user over a network; and
a means for processing a user indication to approve or decline the customer prescription request.

### Claim 19 (depends on 18)

The system of claim 18, further comprising a means for informing the customer whether the prescription request has been approved or declined.

### Claim 20 (depends on 19)

The system of claim 19, further comprising a means to ensure that the user is a doctor authorized to approve or decline the customer prescription request.
