Systems and methods for establishing an individual's longitudinal medication history

• US 10,297,344 B1
• Filed: 03/31/2014
• Issued: 05/21/2019
• Est. Priority Date: 03/31/2014
• Status: Active Grant

• Current Assignee: McKesson Corp.
• Original Assignee: McKesson Corp.
• Inventors: Beers, Mark, Timmerman, Elke Helga Katharina, Adair, James
• Primary Examiner(s): Nguyen, Hiep V
• Assistant Examiner(s): Nguyen, Trang T
• Application Number:
  US14/230,721
• Time in Patent Office: 1,877 Days
• Field of Search: 705 2, 705 3
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients

Abstract

Systems and methods are provided for generating an individual'"'"'s longitudinal medication history. Consent to generate an individual'"'"'s longitudinal medication history across a pharmacy(s) and a claims processor(s) is received. A first collection of medication history data corresponding to the individual is selectively identified from medication history data files associated with the claims processor(s) and a first plurality of individuals. The selective identification is based on a claims processor patient identifier(s) associated with the individual and the claims processor(s). A second collection of medication history data corresponding to the individual is selectively identified from medication history data files associated with the pharmacy(s) and a second plurality of individuals. The selective identification is based on a linking index(s) associated with the claims processor patient identifier(s). An individual'"'"'s longitudinal medication history is generated, based on the first collection of medication history data and the second collection of medication history data.

Claims

1. A computer-implemented method comprising:

receiving, by one or more service provider computers associated with a service provider and on behalf of a patient, consent to generate a longitudinal medication history for the patient across one or more selected pharmacies from among a plurality of pharmacies and one or more selected claims processors from among a plurality of claims processors;

receiving, by the one or more service provider computers, a plurality of patient identification data for the patient;

generating, by the one or more service provider computers, a patient identification key comprising at least a portion of the received plurality of patient identification data, wherein the plurality of patient identification data comprises patient date of birth, patient cardholder ID, and patient person code;

identifying, by the one or more service provider computers, a first claims processor identifier for one of the one or more claims processors;

parsing, by the one or more service provider computers, a plurality of linking indexes in a database, wherein each linking index comprises a claims processor patient identifying key and at least one second claims processor identifier;

determining, by the one or more service provider computers, at least one linking index comprising a second claims processor identifier matching the first claims processor identifier and a claims processor patient identifying key matching at least a portion of the patient identification key;

computing a probabilistic similarity between the claims processor patient identifying key and the patient identifying key;

identifying, by the one or more service provider computers, a claims processor patient identifier for the patient in the at least one matching linking index;

accessing, by the one or more service provider computers using a routing table maintained by memory accessible to the service provider computer that identifies where to route different requests and based at least on the claims processor patient identifier, a first patient medication history for the patient; and

generating, by the one or more service provider computers and based at least in part on the first patient medication history for the patient in response to the probabilistic similarity between the claims processor patient identifying key and the patient identifying key satisfying a predetermined threshold, the longitudinal medication history for the patient.

2. The computer-implemented method of claim 1, further comprising:

identifying, by the one or more service provider computers, a pharmacy identifier for one of the one or more pharmacies;

comparing, by the one or more service provider computers, the patient identification key and the pharmacy identifier to a second plurality of linking indexes comprising pharmacy patient identifying keys and pharmacy identifiers to determine if the patient identification key and the pharmacy identifier match the pharmacy identifier and at least a portion of the pharmacy patient identifying key in one of the second plurality of linking indexes;

selecting, by the one or more service provider computers and based on a positive determination that the patient identification key and the pharmacy identifier match at least a portion of the data in one of the second plurality of linking indexes, a longitudinal identifier for the patient in the matching linking index;

retrieving, by the one or more service provider computers and based on the pharmacy identifier, a second set of patient medication history data for the patient from the matching linking index;

wherein the longitudinal medication history for the patient is generated based at least on the first patient medication history and the second set of patient medication history data.

3. The computer-implemented method of claim 2, wherein the one or more claims processor patient identifying keys and one or more pharmacy patient identifying keys comprise key fields associated with patient identification data and wherein the claims processor patient identifying key values and pharmacy patient identifying key values comprise patient identification data for the patient.

4. The computer-implemented method of claim 3, wherein the one or more claims processor patient identifying keys and one or more matching pharmacy patient identifying keys comprise one or more common key fields and one or more matching key values corresponding to the one or more key fields.

5. The computer-implement method of claim 1, further comprising:

determining, by the one or more service provider computers, if the at least one matching linking index includes at least one other claims processor identifier different from the first claims processor identifier;

identifying, by the one or more service provider computers and based on a positive determination that the at least one matching linking index includes at least one other claims processor identifier different from the first claims processor identifier, a second claims processor patient identifier for the patient and associated with the at least one other claims processor identifier in the at least one matching linking index; and

accessing, by the one or more service provider computers and based at least on the claims processor patient identifier, a second patient medication history data for the patient; and

wherein the longitudinal medication history for the patient is generated based at least on the first patient medication history and the second patient medication history data.

6. A computer-implemented method comprising:

generating, by one or more service provider computers associated with a service provider and based upon claims processor identifiers for one or more claims processors and patient identification data for a first plurality of patients, one or more claims processor linking indexes associated with a first patient of the first plurality of patients and comprising separate fields for a claims processor identifier identifying one of a plurality of claims processors, a claims processor patient identifier identifying the first patient, and one or more claims processor patient identifying keys,

wherein the one or more claims processor patient identifying keys comprise one or more claims processor patient identifying key fields and corresponding claims processor patient identifying key values,

wherein the claims processor patient identifying key fields correspond to patient identification data for the first patient, and

wherein the corresponding claims processor patient identifying key values are generated from the patient identification data for the first patient;

generating, by the one or more service provider computers and based upon pharmacy identifiers for one or more pharmacies and patient identification data for a second plurality of patients, one or more pharmacy linking indexes associated with the first patient and comprising separate fields for a pharmacy identifier identifying one of the one or more pharmacies and one or more pharmacy patient identifying keys,

wherein the one or more pharmacy patient identifying keys comprise one or more pharmacy patient identifying key fields and corresponding pharmacy patient identifying key values,

wherein the pharmacy patient identifying key fields correspond to patient identification data, and

wherein the corresponding pharmacy patient identifying key values are generated from the patient identification data for the first patient,

computing a probabilistic similarity between the claims processor patient identifying key for the first patient and the pharmacy patient identifying key for the first patient; and

generating, by the one or more service provider computers and in response to receiving consent on behalf of the individual and in response to the probabilistic similarity between the claims processor patient identifying key for the first patient and the pharmacy patient identifying key for the first patient satisfying a predetermined threshold, a longitudinal medication history for the first patient, wherein the generating is based at least in part on at least one of the one or more of the claims processor linking indexes and at least one of the one or more pharmacy linking indexes.

7. The computer implemented method of claim 6, wherein for at least one of the one or more claims processor linking indexes, the generating comprises:

identifying, by the one or more service provider computers, patient identification data for the first patient and patient identification data for a second patient from patient identification data associated with the one or more claims processors;

applying, by the one or more service provider computers, probabilistic matching techniques to the patient identification data for the first patient and the patient identification data for the second patient to calculate an overall matching score;

comparing, by the one or more service provider computers, the overall matching score to a matching threshold score;

determining, by the one or more service provider computers that the overall matching score satisfies the matching threshold score;

determining, by the one or more service provider computers and based at least in part on the overall matching score satisfying the matching threshold score, that the patient identification data for the first patient and the patient identification data for the second patient each are for the first patient,

generating, by the one or more service provider computers, a second claims processor patient identifying key for the second patient, based at least in part on the patient identification data for the second patient and

adding the second claims processor patient identifying key for the second patient to the at least one of the claims processor linking indexes for the first patient.

8. The method of claim 6, wherein the claims processor patient identifying key fields correspond to demographic data and/or billing data and wherein the corresponding claims processor patient identifying key values are generated from the patient identification data for the first patient and from the one or more claims processors.

9. The method of claim 8, wherein the pharmacy patient identifying key fields correspond to demographic data and/or billing data and wherein the corresponding pharmacy patient identifying key values are generated from the patient identification data for the first patient and from the one or more pharmacies.

10. The computer implemented method of claim 9, wherein at least one of generating one or more claims processor linking indexes and generating one or more pharmacy linking indexes is performed prior to the receiving the consent on behalf of the user.

11. A system comprising:

at least one memory operable to store computer-executable instructions and

at least one processor configured to access the at least on memory and execute the computer-executable instructions to;

receive, on behalf of a patient, consent to generate a longitudinal medication history for the patient across one or more pharmacies and one or more claims processors;

receive a plurality of patient identification data for the patient;

generate a patient identification key comprising at least a portion of the received plurality of patient identification data wherein the plurality of patient identification data comprises patient date of birth, patient cardholder ID, and patient person code;

identify a first claims processor identifier for one of the one or more claims processors;

parse a plurality of linking indexes in a database, wherein each linking index comprises a claims processor patient identifying key and at least one second claims processor identifier;

determine at least one linking index comprising a second claims processor identifier matching the first claims processor identifier and a claims processor patient identifying key matching at least a portion of the patient identification key;

compute a probabilistic similarity between the claims processor patient identifying key and the patient identifying key;

identify a claims processor patient identifier for the patient in the at least one matching linking index;

access, based at least on the claims processor patient identifier, a first patient medication history for the patient; and

generate, based at least in part on the first patient medication history for the patient and in response to the probabilistic similarity between the claims processor patient identifying key and the patient identifying key satisfying a predetermined threshold, the longitudinal medication history for the patient.

12. The system of claim 11, wherein the at least one processor is further configured to access the at least one memory and execute the computer-executable instructions to:

identify a pharmacy identifier for one of the one or more pharmacies;

compare the patient identification key and the pharmacy identifier to a second plurality of linking indexes comprising pharmacy patient identifying keys and pharmacy identifiers to determine if the patient identification key and the pharmacy identifier match the pharmacy identifier and at least a portion of the pharmacy patient identifying key in one of the second plurality of linking indexes;

select, based on a positive determination that the patient identification key and the pharmacy identifier match at least a portion of the data in one of the second plurality of linking indexes, a longitudinal identifier for the patient in the matching linking index;

retrieve, based on the pharmacy identifier, a second set of patient medication history data for the patient from the matching linking index;

wherein the longitudinal medication history for the patient is generated based at least on the first patient medication history and the second set of patient medication history data.

13. The system of claim 12, wherein the one or more claims processor patient identifying keys and one or more pharmacy patient identifying keys comprise key fields associated with patient identification data and wherein the claims processor patient identifying key values and pharmacy patient identifying key values comprise patient identification data for the patient.

14. The system of claim 13, wherein the one or more claims processor patient identifying keys and one or more matching pharmacy patient identifying keys comprise one or more common key fields and one or more matching key values corresponding to the one or more key fields.

15. The system of claim 12, wherein the at least one processor is further configured to access the at least one memory and execute the computer-executable instructions to:

determine if the at least one matching linking index includes at least one other claims processor identifier different from the first claims processor identifier;

identify, based on a positive determination that the at least one matching linking index includes at least one other claims processor identifier different from the first claims processor identifier, a second claims processor patient identifier for the patient and associated with the at least one other claims processor identifier in the at least one matching linking index; and

access, based at least on the claims processor patient identifier, a second patient medication history data for the patient; and

wherein the longitudinal medication history for the patient is generated based at least on the first patient medication history and the second patient medication history data.

16. A system comprising:

at least one memory operable to store computer-executable instructions and

at least one processor configured to access the at least one memory and execute the computer-executable instructions to;

generate, based upon identification data associated with one or more claims processors and a first plurality of patients, one or more claims processor linking indexes associated with a first patient of the first plurality of patients and comprising separate fields for a claims processor identifier identifying one of a plurality of claims processors, a claims processor patient identifier identifying the first patient, and one or more claims processor patient identifying keys,

wherein the one or more claims processor patient identifying keys comprise one or more claims processor patient identifying key fields and corresponding claims processor patient identifying key values,

wherein the claims processor patient identifying key fields correspond to patient identification data for a patient, and

wherein the corresponding claims processor patient identifying key values are generated from the patient identification data for the first patient;

generate, based upon pharmacy identifiers for one or more pharmacies and patient identification data for a second plurality of patients, one or more pharmacy linking indexes associated with the first patient and comprising separate fields for a pharmacy identifier identifying a selected one of the one or more pharmacies and selected one or more pharmacy patient identifying keys,

wherein the selected one or more pharmacy patient identifying keys comprise one or more pharmacy patient identifying key fields and corresponding pharmacy patient identifying key values,

wherein the pharmacy patient identifying key fields correspond to patient identification data, and

wherein the corresponding pharmacy patient identifying key values are generated from the patient identification data for the first patient and from the at least one of the one or more pharmacies;

compute a probabilistic similarity between the claims processor patient identifying key for the first patient and the pharmacy patient identifying key for the first patient; and

generate, in response to receiving consent on behalf of the individual and in response to the probabilistic similarity between the claims processor patient identifying key for the first patient and the pharmacy patient identifying key for the first patient satisfying a predetermined threshold, a longitudinal medication history for the first patient, wherein the generating is based at least in part on at least one of the one or more of the claims processor linking indexes and at least one of the one or more pharmacy linking indexes.

17. The system of claim 16, wherein for at least one of the one or more claims processor linking indexes, the at least one processor is further configured to access the at least one memory and execute the computer-executable instructions to:

identify patient identification data for first patient and patient identification data for a second patient from patient identification data received from the one or more claims processors;

apply probabilistic matching techniques to the patient identification data for the first patient and the patient identification data for the second patient to calculate an overall matching score;

compare the overall matching score to a matching threshold score;

determine that the overall matching score satisfies the matching threshold score;

determine, based at least in part on the overall matching score satisfying the matching threshold score, that the patient identification data for the first patient and the patient identification data for the second patient each identify the first patient,

generate a second claims processor patient identifying key for the second patient, based at least in part on the patient identification data for the second patient and

add the second claims processor patient identifying key for the second patient to the at least one of the claims processor linking indexes for the first patient.

18. The system of claim 16, wherein the claims processor patient identifying keys comprise claims processor patient identifying key fields corresponding to demographic data and/or billing data and wherein the corresponding claims processor patient identifying key values are generated from the patient identification data for the first patient and from the one or more claims processors.

19. The system of claim 18, wherein the pharmacy patient identifying keys comprise pharmacy patient identifying key fields corresponding to demographic data and/or billing data and wherein the corresponding pharmacy patient identifying key values are generated from the patient identification data for the first patient and from the one or more pharmacies.

20. The system of claim 19, wherein at least one of generating one or more claims processor linking indexes and generating one or more pharmacy linking indexes is performed prior to the receiving the consent on behalf of the user.