Payment Request-Triggered, Pull-Based Collection of Electronic Health Records

• US 20140278532A1
• Filed: 03/15/2013
• Published: 09/18/2014
• Est. Priority Date: 03/15/2013
• Status: Abandoned Application

• Current Assignee: Ravi K. Kalathil
• Original Assignee: Ravi K. Kalathil
• Inventors: Kalathil, Ravi K.
• Application Number:
  US13/839,539
• Publication Number:
  US 20140278532A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass

Abstract

EHR data of a Patient is collected from a Provider for each instance of the Provider delivering Healthcare to the Patient, and that collected EHR data is aggregated with any pre-existing EHR data of the Patient to create augmented EHR data for the Patient. The EHR data is collected from the Provider in response to a payment request submitted by the Provider to a Payer, and other techniques.

Claims

1. A method of collecting and aggregating EHR data of a Patient to whom Healthcare is delivered by a Provider who creates the EHR data and submits a payment request to a Payer for compensation for delivery of Healthcare to the Patient, comprising:

collecting the EHR data from the Provider for each instance of the Provider delivering Healthcare to the Patient in response to the Provider submitting the payment request to the Payer; and

aggregating the collected EHR data with any pre-existing EHR data to create augmented EHR data for the Patient.

2. A method as defined in claim 1, further comprising:

including in the payment request an identification of the Patient, an identification of the Provider, and a basic description of the Healthcare delivered to the Patient; and

requesting the Provider identified in the payment request to supply the EHR data created by the Provider for the Patient identified in the payment request.

3. A method as defined in claim 2, further comprising:

additionally requesting the Provider identified in the payment request to supply the EHR data created by the Provider for the Patient identified in the payment request by reference to at least one aspect of the basic description of the Healthcare delivered contained in the payment request.

4. A method as defined in claim 2, wherein the EHR data of the Patient is collected, aggregated and augmented by a Provider.

5. A method as defined in claim 4, wherein the Provider that collects, aggregates and augments the EHR data of the Patient is different from each other Provider that delivers Healthcare to the Patient.

6. A method as defined in claim 1, wherein the EHR data of the Patient is collected, aggregated and augmented by an Aggregator that has authority to access the EHR data of the Patient created by the Provider, and the Aggregator is not a Provider who submits the payment request to the Payer.

7. A method as defined in claim 6, wherein the Aggregator derives the authority to communicate with each Provider who delivers Healthcare to the Patient by obtaining the consent for such communication from the Patient.

8. A method as defined in claim 6, wherein the Aggregator derives the authority to communicate with each Provider who creates EHR data of the Patient by obtaining lawful regulatory status as a Provider.

9. A method as defined in claim 6, wherein:

the Aggregator is an entity separate from the Provider;

the Payer transmits a payment request trigger to the Aggregator after the Provider submits the payment request to the Payer,

the payment request trigger includes an identification of the Patient, an identification of the Provider, and a basic description of the Healthcare delivered by the identified Provider to the Patient; and

the Aggregator responds to the payment request trigger by requesting the identified Provider to supply the EHR data created by the Provider for the Healthcare delivered to the identified Patient.

10. A method as defined in claim 9, wherein:

the Aggregator responds to the payment request trigger by requesting the identified provider to supply the EHR data created by the Provider for Healthcare delivered to the identified Patient by reference at least one aspect to the basic description of the Healthcare delivered contained in the payment request trigger.

11. A method as defined in claim 1, further comprising:

collecting and aggregating pre-existing EHR data of the Patient from the Payer who previously compensated a Provider for delivering Healthcare to the Patient.

12. A method as defined in claim 11, further comprising:

collecting and aggregating pre-existing EHR data of the Patient from multiple different Payers.

13. A method as defined in claim 1, further comprising:

collecting and aggregating pre-existing EHR data of the Patient from Providers who previously delivered Healthcare to the Patient.

14. A method as defined in claim 1, further comprising:

collecting and aggregating pre-existing EHR data of the Patient from statements describing Healthcare delivered by the Provider that were obtained by the Patient from the Provider and submitted to the Aggregator.

15. A method as defined in claim 1, further comprising:

collecting and aggregating pre-existing medical information of the Patient by accessing a PHR vault of the Patient and obtaining medical information of the Patient recorded in that PHR vault.

16. A method as defined in claim 1, further comprising:

collecting and aggregating EHR data of the Patient by periodically requesting the EHR data from each Provider who has previously delivered Healthcare to the Patient within a predetermined amount of elapsed time after the Provider has previously delivered the Healthcare.

17. A method as defined in claim 1, further comprising:

including in the payment request an identification of the Patient, an identification of the Provider, and a basic description of the Healthcare delivered to the Patient;

collecting and aggregating EHR data of the Patient by using the identification of the Patient and the identification of the Provider and at least one aspect of the basic description of the Healthcare delivered to the Patient; and

requesting EHR data for the identified Patient from a class of other Providers for which there is a reasonable probability of delivering Healthcare to the Patient based on at least one aspect of the basic description of the Healthcare delivered to the Patient contained in the payment request.

18. A method as defined in claim 17, further comprising:

limiting the request for EHR data to those other Providers of the class that have geographic addresses within a predetermined geographic proximity of the address of the one of the Provider submitting the payment request or the Patient.

19. A method as defined in claim 1, further comprising:

collecting and aggregating EHR data of the Patient by periodically requesting the EHR data from each Provider who has an address within a predetermined geographic proximity of the address of one of the Provider submitting the payment request or the Patient.

20. A method as defined in claim 1, wherein:

a Provider requests and obtains the aggregated EHR data of a Patient in connection with delivering Healthcare to the Patient.

21. A method as defined in claim 20, wherein:

the Provider updates any EHR data of the Provider for the Patient with the augmented EHR data received.

22. A method as defined in claim 20, further comprising:

augmenting EHR data of the Patient by periodically collecting, aggregating and augmenting the EHR data from each Provider who has previously requested augmented EHR data for the Patient within a predetermined amount of elapsed time after the Provider requested the augmented EHR data.