IP Library Granted Patent US 11,328,825
Granted Patent B1
US 11,328,825 · App. 16/847,562 · Granted May 10, 2022

Machine learning techniques for identifying opportunity patients

Inventors: Kezi Yu (King of Prussia, PA); Fan Zhang (Plymouth Meeting, PA); Yunlong Wang (Malvern, PA); Yilian Yuan (North Wales, PA); Emily Zhao (Wayne, PA); William McClellan (Collegeville, PA); Yong Cai (Bala Cynwyd, PA)
Assignee: IQVIA Inc.
G16H50/70A61B5/4848A61B5/7267G16H10/60G16H20/10G16H40/20G16H50/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,328,825
App. No.
16/847,562
Granted
May 10, 2022
Kind
B1
Abstract

Systems and techniques are disclosed for using machine-learning to identify potential opportunity patients that are more likely to adjust his/her preference for a healthcare provider or service. In some implementations, integrated patient data is obtained. A patient sequence feature vector, a provider sequence feature vector, and a set of entity-specific feature vectors are generated. A set of opportunity patients is identified. A notification is transmitted to the set of opportunity patients about a second treatment plan.

Claims (55)

1. A computer-implemented method, the method comprising:

obtaining patient sequence information identifying treatment events associated with a first treatment plan and provider sequence information identifying providers that have participated in a treatment event associated with the first treatment plan;

generating a plurality of feature vectors, including:

generating a patient sequence feature vector corresponding to the patient sequence information based on applying a first model to the patient sequence information, wherein the first model is trained to output patient sequence feature vectors for respective patients with different patient sequences;

generating a provider sequence feature vector corresponding to the provider sequence information based on applying a second model to the provider sequence information, wherein the second model is trained to output provider sequence feature vectors for respective providers with different provider sequences;

training a combining model to classify a patient as being likely to adjust the first treatment plan;

providing at least some of the plurality of feature vectors as an input to the combining model;

classifying, based on the combining model, a set of patients as being likely to adjust the first treatment plan; and

transmitting a notification to the set of patients about a second treatment plan.

2. The method of claim 1 , wherein:

the first treatment plan represents treatment of a disease condition using a pharmaceutical product;

the patient sequence information identifies, for each patient, a first treatment event indicating diagnosis of the disease condition, a second treatment event indicating a prescription of the pharmaceutical product, and a third treatment event indicating a treatment follow-up; and

the set of patients represents patients that are classified by the combining model as being likely to withdraw from the first treatment plan based on data associated with the first treatment event, the second treatment event, or the third treatment event.

3. The method of claim 1 , wherein generating the plurality of feature vectors comprises generating a set of entity-specific feature vectors corresponding to a set of entity-specific attributes based on applying a third model to the set of entity-specific attributes, wherein the third model is trained to output sets of entity-specific feature vectors for respective sets of entity-specific attributes.

4. The method of claim 3 , wherein:

the first model and the second model each comprise recurrent neural networks; and

the third model and the combining model each comprise deep neural networks.

5. The method of claim 3 , wherein:

the set of entity-specific attributes comprises provider-level attributes, patient-level attributes, and plan-level attributes; and

the set of entity-specific feature vectors comprises a provider-level feature vector, a patient-level feature vector, and a plan-level feature vector.

6. The method of claim 1 , comprising:

training the combining model to classify a provider as being likely to adjust the first treatment plan.

7. The method of claim 1 , wherein the set of patients comprises one or more patients classified by the combining model as being likely to adjust a pharmaceutical product associated with the first treatment plan.

8. The method of claim 1 , wherein the set of patients comprises one or more patients classified by the combining model as being likely to adjust a provider associated with the first treatment plan.

9. A system comprising:

one or more computing devices; and

a non-transitory computer-readable storage device storing instructions that are executable by the one or more computing devices to perform operations comprising:

obtaining patient sequence information identifying treatment events associated with a first treatment plan and provider sequence information identifying providers that have participated in a treatment event associated with the first treatment plan;

generating a plurality of feature vectors, including:

generating a patient sequence feature vector corresponding to the patient sequence information based on applying a first model to the patient sequence information, wherein the first model is trained to output patient sequence feature vectors for respective patients with different patient sequences;

generating a provider sequence feature vector corresponding to the provider sequence information based on applying a second model to the provider sequence information, wherein the second model is trained to output provider sequence feature vectors for respective providers with different provider sequences;

training a combining model to classify a patient as being likely to adjust the first treatment plan;

training a combining model to classify a patient as being likely to adjust the first treatment plan;

providing at least some of the plurality of feature vectors as an input to the combining model;

classifying, based on the combining model, a set of patients as being likely to adjust the first treatment plan; and

transmitting a notification to the set of patients about a second treatment plan.

10. The system of claim 9 , wherein:

the first treatment plan represents treatment of a disease condition using a pharmaceutical product;

the patient sequence information identifies, for each patient, a first treatment event indicating diagnosis of the disease condition, a second treatment event indicating a prescription of the pharmaceutical product, and a third treatment event indicating a treatment follow-up; and

the set of patients represents patients that are classified by the combining model as being likely to withdraw from the first treatment plan based on data associated with the first treatment event, the second treatment event, or the third treatment event.

11. The system of claim 9 , wherein generating the plurality of feature vectors comprises generating a set of entity-specific feature vectors corresponding to a set of entity-specific attributes based on applying a third model to the set of entity-specific attributes, wherein the third model is trained to output sets of entity-specific feature vectors for respective sets of entity-specific attributes.

12. At least one non-transitory computer-readable storage device storing instructions that are executable by one or more computing devices to perform operations comprising:

obtaining patient sequence information identifying treatment events associated with a first treatment plan and provider sequence information identifying providers that have participated in a treatment event associated with the first treatment plan;

generating a plurality of feature vectors, including:

generating a patient sequence feature vector corresponding to the patient sequence information based on applying a first model to the patient sequence information, wherein the first model is trained to output patient sequence feature vectors for respective patients with different patient sequences;

generating a provider sequence feature vector corresponding to the provider sequence information based on applying a second model to the provider sequence information, wherein the second model is trained to output provider sequence feature vectors for respective providers with different provider sequences;

training a combining model to classify a patient as being likely to adjust the first treatment plan;

providing at least some of the plurality of feature vectors as an input to the combining model;

classifying, based on the combining model, a set of patients as being likely to adjust the first treatment plan; and

transmitting a notification to the set of patients about a second treatment plan.

13. The one non-transitory computer-readable storage device of claim 12 , wherein:

the first treatment plan represents treatment of a disease condition using a pharmaceutical product;

the patient sequence information identifies, for each patient, a first treatment event indicating diagnosis of the disease condition, a second treatment event indicating a prescription of the pharmaceutical product, and a third treatment event indicating a treatment follow-up; and

the set of patients represents patients that are classified by the combining model as being likely to withdraw from the first treatment plan based on data associated with the first treatment event, the second treatment event, or the third treatment event.

14. The one non-transitory computer-readable storage device of claim 12 , wherein generating the plurality of feature vectors comprises generating a set of entity-specific feature vectors corresponding to a set of entity-specific attributes based on applying a third model to the set of entity-specific attributes, wherein the third model is trained to output sets of entity-specific feature vectors for respective sets of entity-specific attributes.

Assignments (7)
SECURITY INTEREST Recorded Mar 12, 2026
From: IMS SOFTWARE SERVICES LTD.; IQVIA INC.; IQVIA RDS INC.; RULES-BASED MEDICINE, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 075047/0061 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTIES INADVERTENTLY NOT INCLUDED IN FILING PREVIOUSLY RECORDED AT REEL: 065709 FRAME: 618. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY AGREEMENT. Recorded Dec 6, 2023
From: IQVIA INC.; IQVIA RDS INC.; IMS SOFTWARE SERVICES LTD.; Q SQUARED SOLUTIONS HOLDINGS LLC
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 065790/0781 →
SECURITY INTEREST Recorded Nov 29, 2023
From: IQVIA INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 065709/0618 →
SECURITY INTEREST Recorded Nov 29, 2023
From: IQVIA INC.; IQVIA RDS INC.; IMS SOFTWARE SERVICES LTD.; Q SQUARED SOLUTIONS HOLDINGS LLC
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 065710/0253 →
SECURITY INTEREST Recorded Jul 12, 2023
From: IQVIA INC.; IMS SOFTWARE SERVICES, LTD.
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 064258/0577 →
SECURITY INTEREST Recorded May 24, 2023
From: IQVIA INC.; IQVIA RDS INC.; IMS SOFTWARE SERVICES LTD.; Q SQUARED SOLUTIONS HOLDINGS LLC
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 063745/0279 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 17, 2020
From: YU, KEZI; ZHANG, FAN; WANG, YUNLONG; YUAN, YILIAN; ZHAO, EMILY; MCCLELLAN, WILLIAM; CAI, YONG
To: IQVIA INC.
Reel/Frame 052964/0517 →
Cited By (1)
US 12,633,400