# US 2014/0156298 A1 · Modularization for prescription fulfillment and adherence

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

- Number: US 2014/0156298 A1
- Document ID: US20140156298A1
- Status: Published application
- Kind: A1
- Application number: 14/101,997
- Filed: 2013-12-10
- Published: 2014-06-05
- Earliest claimed: 2012-12-05
- Applicants: MeadWestvaco Corporation
- Inventors: Patricia CRAWFORD; Mark MAGLIONE; Justin TOWLE; Thomas R. GRINNAN; Sandra J. EYERLY; Frederick THOMPSON; Kenneth G. SADLER
- Web page: https://patentgrep.com/patent/US20140156298A1

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G16H 20/10: relating to drugs or medications, e.g. for ensuring correct administration to patients
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA

## Abstract

A modular system for facilitating fulfillment and patient adherence for multiple prescriptions. Each module is an independently executing software widget configured to perform complementary tasks in a coordinated manner to achieve specific functions as described below. Including a system module to determine a patient customize drug regimen schedule, a module to identify potential side effects and drug interactions, and other modules useful to fulfill a patient order for multiple-medications.

## Claims

### Claim 1

A system implemented in a distributed computing environment, the system comprising:
a core module configured to:
receive a prescription order that covers one or more medications to be taken over a period of days and during one or more administration times, the prescription order comprising one or more prescriptions for a single patient, each prescription representative of a medication and including prescription data comprised of one or more prescriber instructions and one or more product identification codes;
determine a patient customized drug regimen (PCDR) schedule that assigns an administration time to each of the prescriptions in the prescription order over the period of days;
depending on a hold status, execute filling at least one of the prescriptions for the single patient; and
a synchronization module configured to:
receive one or more of patient profile information, information indicating at least one change to the prescription order, and medication anomaly information;
determine the hold status.

### Claim 2 (depends on 1)

The system of claim 1, wherein the distributed computing environment is a cloud computing environment.

### Claim 3 (depends on 1)

The system of claim 1, wherein determining the hold status is based at least in part on the received patient profile information.

### Claim 4 (depends on 1)

The system of claim 1, wherein determining the hold status is based at least in part on the received information indicating changes to the prescription order.

### Claim 5 (depends on 4)

The system of claim 4, wherein the received information indicating at least one change to the prescription order comprises a new prescription for the single patient.

### Claim 6 (depends on 1)

The system of claim 1, wherein determining the hold status is based at least in part on the medication anomaly information.

### Claim 7 (depends on 1)

The system of claim 1, wherein determining the hold status is based at least in part on compatibility between two or more medications.

### Claim 8 (depends on 1)

The system of claim 1, wherein the hold status comprises a status level for the single patient.

### Claim 9 (depends on 1)

The system of claim 1, wherein the hold status comprises a status level for a single medication.

### Claim 10 (depends on 1)

The system of claim 1, wherein executing filling at least one of the prescriptions for the single patient comprises outputting data for manually filling the at least one of the prescriptions.

### Claim 11 (depends on 1)

The system of claim 1, wherein executing filling at least one of the prescriptions for the single patient comprises communicating with at least one prescription filling apparatus.

### Claim 12 (depends on 1)

The system of claim 1, wherein the synchronization module is further configured to automatically determine a production date to start the period of days.

### Claim 13 (depends on 1)

The system of claim 1, further comprising a parser module configured to:
receive responses to patient profile questions;
extract PCDR-related information from the responses; and
send the PCDR-related information to the core module.

### Claim 14 (depends on 1)

The system of claim 1, further comprising a patient adherence module configured to:
provide a plurality of patient profile questions;
receive responses to the plurality of patient profile questions;
identify medication issues from the responses; and
output updated patient profile information.

### Claim 15 (depends on 14)

The system of claim 14, wherein identifying medication issues from the responses comprises recognizing a side effect.

### Claim 16 (depends on 14)

The system of claim 14, wherein identifying medication issues from the responses comprises accessing a patient DNA profile.

### Claim 17 (depends on 14)

The system of claim 14, wherein the patient adherence module is further configured to maintain at least one of a communication log, medication history table, indications table, a biometrics table, or a side effects table.

### Claim 18 (depends on 17)

The system of claim 17, wherein identifying medication issues from the responses comprises recognizing a side effect based on the side effects table.

### Claim 19 (depends on 14)

The system of claim 14, wherein the patient adherence module is further configured to determine the hold status based on at least one of an identified medical issue, potential medication incompatibility, or user input.

### Claim 20 (depends on 14)

The system of claim 14, wherein the patient adherence module is further configured to initiate communications to obtain updated patient profile information.

### Claim 21 (depends on 20)

The system of claim 20, wherein the communications are initiated periodically.

### Claim 22 (depends on 21)

The system of claim 21, wherein the communications are initiated monthly.

### Claim 23 (depends on 14)

The system of claim 14, wherein outputting updated patient profile information comprises outputting data to the synchronization module.

### Claim 24 (depends on 1)

The system of claim 1, wherein the core module further comprises a tracking interface configured to bilaterally communicate scan data indicative of prescription fulfillment functions.

### Claim 25 (depends on 1)

The system of claim 1, wherein the core module is further configured to bilaterally communicate with one or more databases.

### Claim 26 (depends on 1)

The system of claim 1, wherein the core module is further configured to output medical records.

### Claim 27 (depends on 1)

The system of claim 1, wherein the synchronization module is further configured to generate reports for at least one of adherence outcomes, monthly fill data, and exception data for multiple patients.

### Claim 28 (depends on 1)

The system of claim 1, further comprising an inventory module configured to monitor medication availability.

### Claim 29

A patient adherence module implemented in a distributed computing environment, the patient adherence module configured to:
provide a plurality of patient profile questions;
receive responses to the plurality of patient profile questions;
identify medication issues from the responses; and
output updated patient profile information.

### Claim 30 (depends on 29)

The patient adherence module of claim 29, wherein identifying medication issues from the responses comprises recognizing a side effect.

### Claim 31 (depends on 29)

The patient adherence module of claim 29, wherein identifying medication issues from the responses comprises accessing a patient DNA profile.

### Claim 32 (depends on 29)

The patient adherence module of claim 29 wherein the patient adherence module is further configured to maintain at least one of a communication log, a biometrics table, or a side effects table.

### Claim 33 (depends on 32)

The patient adherence module of claim 32, wherein identifying medication issues from the responses comprises recognizing a side effect based on the side effects table.

### Claim 34 (depends on 29)

The patient adherence module of claim 29 wherein the patient adherence module is further configured to determine a hold status based on at least one of an identified medical issue or user input.

### Claim 35 (depends on 29)

The patient adherence module of claim 29, wherein the patient adherence module is further configured to initiate communications to obtain updated patient profile information.

### Claim 36 (depends on 35)

The patient adherence module of claim 35, wherein the communications are initiated periodically.

### Claim 37 (depends on 36)

The patient adherence module of claim 36, wherein the communications are initiated monthly.

### Claim 38 (depends on 29)

The patient adherence module of claim 29 wherein outputting updated patient profile information comprises outputting data to at least one database.

### Claim 39

A method implemented on a computing system, the method comprising:
receiving a prescription order that covers one or more medications to be taken over a period of days and during one or more administration times, the prescription order comprising one or more prescriptions for a single patient, each prescription representative of a medication and including prescription data comprised of one or more prescriber instructions and one or more product identification codes;
receiving one or more of patient profile information, information indicating at least one change to the prescription order, and medication anomaly information;
determining a patient customized drug regimen (PCDR) schedule that assigns an administration time to each of the prescriptions in the prescription order over the period of days;
determining a hold status; and
depending on the hold status, executing filling at least one of the prescriptions for the single patient.

### Claim 40 (depends on 39)

The method of claim 39, wherein the distributed computing environment is a cloud computing environment.

### Claim 41 (depends on 39)

The method of claim 39, wherein determining the hold status is based at least in part on the received patient profile information.

### Claim 42 (depends on 39)

The method of claim 39, wherein determining the hold status is based at least in part on the received information indicating changes to the prescription order.

### Claim 43 (depends on 42)

The method of claim 42, wherein the received information indicating at least one change to the prescription order comprises a new prescription for the single patient.

### Claim 44 (depends on 39)

The method of claim 39, wherein determining the hold status is based at least in part on the medication anomaly information.

### Claim 45 (depends on 39)

The method of claim 39, wherein determining the hold status is based at least in part on compatibility between two or more medications.

### Claim 46 (depends on 39)

The method of claim 39, wherein the hold status comprises a status level for the single patient.

### Claim 47 (depends on 39)

The method of claim 39, wherein the hold status comprises a status level for a single medication.

### Claim 48 (depends on 39)

The method of claim 39, wherein executing filling at least one of the prescriptions for the single patient comprises outputting data for manually filling the at least one of the prescriptions.

### Claim 49 (depends on 39)

The method of claim 39, wherein executing filling at least one of the prescriptions for the single patient comprises communicating with a prescription filling apparatus.

### Claim 50 (depends on 39)

The method of claim 39, further comprising automatically determining a production date to start the period of days.

### Claim 51 (depends on 39)

The method of claim 39, further comprising bilaterally communicating to obtain scan data indicative of prescription fulfillment functions.

### Claim 52 (depends on 39)

The method of claim 39, further comprising updating one or more databases.

### Claim 53 (depends on 39)

The method of claim 39, further comprising outputting medical records.

### Claim 54 (depends on 39)

The method of claim 39, further comprising generating reports for at least one of adherence outcomes, monthly fill data, and exception data for multiple patients.

### Claim 55 (depends on 39)

The method of claim 39, further comprising monitoring medication availability.

### Claim 56

A method implemented on a computing system, the method comprising:
providing a plurality of patient profile questions;
receiving responses to the plurality of patient profile questions;
identifying medication issues from the responses; and
outputting updated patient profile information.

### Claim 57 (depends on 56)

The method of claim 56, wherein identifying medication issues from the responses comprises recognizing one of a medication side effect or a drug interaction.

### Claim 58 (depends on 56)

The method of claim 56, wherein identifying medication issues from the responses comprises accessing a patient DNA profile.

### Claim 59 (depends on 56)

The method of claim 56, further comprising maintaining at least one of a communication log, a biometrics table, or a side effects table.

### Claim 60 (depends on 59)

The method of claim 59, wherein identifying medication issues from the responses comprises recognizing a side effect based on the side effects table.

### Claim 61 (depends on 56)

The method of claim 56, further comprising determining a hold status based on at least one of an identified medical issue or user input.

### Claim 62 (depends on 56)

The method of claim 56, further comprising initiating communications to obtain updated patient profile information.

### Claim 63 (depends on 62)

The method of claim 62, wherein the communications are initiated periodically.

### Claim 64 (depends on 63)

The method of claim 63, wherein the communications are initiated monthly.

### Claim 65 (depends on 56)

The method of claim 56, wherein outputting updated patient profile information comprises outputting data to one or more databases.

### Claim 66

A method implemented on a computing system, the method comprising:
providing a plurality of patient profile questions;
receiving responses to the plurality of patient profile questions;
identifying medication issues from the responses; and
collecting the medication issues in one or more log(s).

### Claim 67 (depends on 66)

The method of claim 66 further comprising, analyzing the medication issues in the one or more log(s), determining when 10 or more patients taking the same medication are reporting one or more of the same medication issues, and identifying the medication issue as a new medication issue associated with the medication the 10 or more patients were taking

### Claim 68 (depends on 67)

The method of claim 67 further comprising reporting the new medication issue as being associated with the medication the 10 or more patients were taking to one of an external database or an internal database.

### Claim 69 (depends on 66, 69)

The method of claim 66 further comprising, analyzing the medication issues in the one or more log(s), determining when 10 or more patients taking the two or more of the same medication(s) are reporting one or more of the same medication issues, and identifying the medication issue as a new medication issue associated with the two or more medication(s) the 10 or more patients were taking
70. The method of claim 69 further comprising reporting the new medication issue as being associate with the two or more medications the 10 or more patients were taking to one of an external database or an internal database.