Healthcare service management using a centralized service management module

• US 8,660,856 B2
• Filed: 01/29/2009
• Issued: 02/25/2014
• Est. Priority Date: 01/31/2008
• Status: Active Grant

• Current Assignee: Health Catalyst, Inc.
• Original Assignee: Medicity Incorporated (Health Catalyst, Inc.)
• Inventors: Lassetter, J. Kipp, Crapo, Jared, Meyerowitz, Jordan, Myers, Lilian T., Shah, Ashish V.
• Primary Examiner(s): Gort, Elaine
• Assistant Examiner(s): Ng, Jonathan K
• Application Number:
  US12/362,336
• Publication Number:
  US 20090222283A1
• Time in Patent Office: 1,853 Days
• Field of Search: 340/573, 705/2
• US Class Current: 705/2
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms

Abstract

A system and method for scheduling or managing receipt of healthcare services are disclosed. A centralized service management module is coupled to one or more client devices and to one or more service providers, such as healthcare providers or insurance providers. The centralized service management module receives an interaction, such as an appointment request, from a client device or a service provider associated with healthcare services. The centralized service management module associates a service provider with the interaction based on a stored user profile. The interaction is then transmitted by the centralized service management module to the associated service provider, which provides data associated with a healthcare product or service associated with the interaction to the centralized service management module. The data is stored in the user profile and transmitted, buy the centralized service management module, to a client device using a communication protocol specified by the user profile.

Claims

1. A system for managing a healthcare service or product comprising:

one or more processors; and

a centralized service management module stored on a memory and executable by the one or more processors, the centralized service management module communicatively coupled to a client device and a plurality of independent service providers that provide the healthcare product or service, the centralized service management module for;

receiving an interaction record from the client device that includes an appointment request identifying a first time for receipt of the healthcare product or service, and a distance for receiving the healthcare product or service,

storing a user profile including data describing healthcare information associated with a user of the client device, results of a treatment from a first service provider and suggested follow-up treatments,

identifying the first service provider associated with the interaction record from the plurality of independent service providers based on at least one of the first time and determining that the first service provider is located within the distance from the client device,

transmitting the interaction record to the first service provider,

transmitting to the client device an appointment reminder including data describing a scheduled appointment associated with the appointment request and the first service provider'"'"'s preference specifying a time window prior to a start of the scheduled appointment for sending a check-in request,

transmitting a delay notification to the client device for rescheduling the scheduled appointment to a second time,

responsive to receiving the check-in request from the client device after the appointment reminder,

retrieving data from the user profile describing healthcare information associated with the appointment request, and

transmitting the retrieved data from the user profile to the first service provider prior to the user'"'"'s arrival at the first service provider, and

responsive to failing to receive the check-in request,

transmitting a miss notification to the client device for notifying the user that the scheduled appointment was missed and prompting the user to reschedule the scheduled appointment to a third time.

2. The system of claim 1, wherein the interaction record includes an identifier associated with the user, an identifier describing the first service provider, a date associated with the healthcare product or service, the first time associated with the healthcare product or service and a text description of the healthcare product or service.

3. The system of claim 1, wherein the interaction record comprises the appointment request identifying the first time for receipt of the healthcare service or product, the first service provider and the user.

4. The system of claim 1, wherein the centralized service management module includes a user data store for storing data received from the first service provider describing the healthcare product or service associated with the interaction record in the user profile associated with the user of the client device.

5. The system of claim 4, wherein the centralized service management module includes an individualized healthcare module coupled to the user data store, the individualized healthcare management module for receiving data from the first service provider, identifying the user associated with the data from the first service provider and transmitting the data from the first service provider to the client device using a plurality of settings included in the user profile associated with the user of the client device.

6. The system of claim 5, wherein the plurality of settings included in the user profile associated with the user of the client device identify a subset of the data from the first service provider for transmission to the client device.

7. The system of claim 5, wherein the plurality of settings included in the user profile associated with the user of the client device identify a subset of the data from the first service provider for transmission to a second service provider.

8. The system of claim 5 wherein the plurality of settings included in the user profile identify a communication protocol for transmitting the data from the first service provider to the client device.

9. The system of claim 4, wherein the user data store stores data associated with the user of the client device received from a second service provider which is independent from the first service provider.

10. The system of claim 9, wherein the data received from the second service provider is authenticated by the second service provider.

11. The system of claim 1, wherein the plurality of independent service providers comprise at least one of a hospital, a pharmacy, a physician office, a clinic, a medical laboratory, a physician rating service, a hospital rating service, a personal health record store, a health coach, a health bank, a health information provider, a health savings account, a flexible savings account, a health reimbursement arrangement, a medical savings account, a diagnostic imaging facility, an outpatient surgery facility, a long-term care facility, an urgent care facility and an insurance provider.

12. A method for managing a healthcare product or service comprising:

receiving, with one or more processors, an interaction record associated with the healthcare product or service from a client device, the interaction record including an appointment request identifying a first time for receipt of the healthcare product or service and a distance for receiving the healthcare product or service;

identifying, with the one or more processors, a first service provider associated with the interaction record, the first service provider identified from a plurality of independent service providers based on at least one of the first time and determining that the first service provider is located within the distance from the client device;

identifying, with the one or more processors, a user profile associated with the interaction record, the user profile including data describing healthcare information associated with a user of the client device;

transmitting, with the one or more processors, the interaction record to the first service provider associated with the interaction record;

receiving, with the one or more processors, data from the first service provider associated with the interaction record, the data describing the healthcare product or service associated with the interaction record and user profile data including results of a treatment from the first service provider and suggested follow-up treatments;

storing, with the one or more processors, the received data from the first service provider describing the healthcare product or service associated with the interaction record in the identified user profile;

transmitting, with the one or more processors, an appointment reminder including data describing a scheduled appointment associated with the appointment request and the first service provider'"'"'s preference specifying a time window prior to a start of the scheduled appointment for sending a check-in request to the client device;

transmitting, with the one or more processors, a delay notification to the client device for rescheduling the scheduled appointment to a second time;

responsive to receiving, with the one or more processors, a check-in request from the client device after the appointment reminder,

retrieving, with the one or more processors, data from the user profile describing healthcare information associated with the appointment request, and

transmitting, with the one or more processors, the retrieved data from the user profile to the first service provider prior to the user'"'"'s arrival at the first service provider; and

responsive to failing to receive the check-in request,

transmitting a miss notification to the client device for notifying the user that the scheduled appointment was missed and prompting the user to reschedule the scheduled appointment to a third time.

13. The method of claim 12, wherein the interaction record includes an identifier associated with the user, an identifier describing the first service provider, a date associated with the healthcare product or service, the first time associated with the healthcare product or service and a text description of the healthcare product or service.

14. The method of claim 12, wherein the interaction record comprises the appointment request identifying the first time for receipt of the healthcare product or service, the healthcare product or service, the first service provider and the user.

15. The method of claim 14, further comprising:

transmitting the appointment reminder to the client device at multiple intervals until the check-in request is received.

16. The method of claim 12, wherein retrieving the data from the user profile describing healthcare information associated with the appointment request comprises:

identifying a subset of the data from the user profile according to a plurality of settings included in the user profile; and

retrieving the subset of the data from the user profile.

17. The method of claim 12, wherein transmitting the appointment reminder including data describing the scheduled appointment to the client device comprises:

transmitting a short message service (SMS) message to the client device.

18. The method of claim 12, wherein transmitting the appointment reminder including data describing the scheduled appointment to the client device comprises:

transmitting an email message to the client device.

19. The method of claim 12, wherein transmitting the appointment reminder including data describing the scheduled appointment to the client device comprises:

initiating a telephone call to the client device.

20. The method of claim 12, wherein the user profile identifies a communication protocol for transmitting data associated with the interaction record received from the first service provider to the client device.

21. The method of claim 12, further comprising:

receiving data from a second service provider associated with the healthcare product or service, the second service provider being independent from the first service provider;

associating the data from the second service provider with the user profile; and

storing the data from the second service provider in the user profile.

22. The method of claim 21, wherein the data from the second service provider comprises data authenticated by the second service provider.

23. The method of claim 21, further comprising:

associating a setting in the user profile with the data from the second service provider, the setting determining whether the data from the second service provider is accessible by one or more additional service providers, the one or more additional service providers being independent from the first service provider and the second service provider.

24. The method of claim 12, wherein the plurality of independent service providers comprise at least one of a hospital, a pharmacy, a physician office, a clinic, a medical laboratory, a physician rating service, a hospital rating service, a personal health record store, a health coach, a health bank, a health information provider, a health savings account, a flexible savings account, a health reimbursement arrangement, a medical savings account, a diagnostic imaging facility, an outpatient surgery facility, a long-term care facility, an urgent care facility and an insurance provider.

25. A computer program product comprising a computer readable storage medium storing computer executable code for managing a healthcare product or service, the computer executable code performing the steps of:

receiving an interaction record associated with the healthcare product or service from a client device, the interaction record including an appointment request identifying a first time for receipt of the healthcare product or service and a distance for receiving the healthcare product or service;

identifying a first service provider associated with the interaction record, the first service provider identified from a plurality of independent service providers based on at least one of the first time and determining that the first service provider is located within the distance from the client device;

identifying a user profile associated with the interaction record, the user profile including data describing healthcare information associated with a user of the client device;

transmitting the interaction record to the first service provider associated with the interaction record;

receiving data from the first service provider associated with the interaction record, the data describing the healthcare product or service associated with the interaction record and user profile information including results of a treatment from the first service provider and suggested follow-up treatments;

storing the received data from the first service provider describing the healthcare product or service associated with the interaction record in the identified user profile;

transmitting an appointment reminder including data describing a scheduled appointment associated with the appointment request and the first service provider'"'"'s preference specifying a time window prior to a start of the scheduled appointment for sending a check-in request to the client device;

transmitting a delay notification to the client device for rescheduling the scheduled appointment to a second time;

responsive to receiving a check-in request from the client device after the appointment reminder,

retrieving data from the user profile describing healthcare information associated with the appointment request; and

transmitting the retrieved data from the user profile to the first service provider prior to the user'"'"'s arrival at the first service provider; and

responsive to failing to receive the check-in request,

transmitting a miss notification to the client device for notifying the user that the scheduled appointment was missed and prompting the user to reschedule the scheduled appointment to a third time.

26. The computer program product of claim 25, wherein the interaction record includes an identifier associated with the user, an identifier describing the first service provider, a date associated with the healthcare product or service, the first time associated with the healthcare product or service, and a text description of the healthcare product or service.

27. The computer program product of claim 25, wherein the interaction record comprises the appointment request identifying the first time for receipt of the healthcare product or service, the healthcare product or service, the first service provider and the user.

28. The computer program product of claim 27, wherein the computer executable code further performs the steps of:

transmitting the appointment reminder to the client device at multiple intervals until the check-in request is received.

29. The computer program product of claim 25, wherein retrieving the data from the user profile describing healthcare information associated with the appointment request comprises:

identifying a subset of the data from the user profile according to a plurality of settings included in the user profile; and

retrieving the subset of the data from the user profile.

30. The computer program product of claim 25, wherein transmitting the appointment reminder including data describing the scheduled appointment to the client device comprises:

transmitting a short message service (SMS) message to the client device.

31. The computer program product of claim 25, wherein transmitting the appointment reminder including data describing the scheduled appointment to the client device comprises:

transmitting an email message to the client device.

32. The computer program product of claim 25, wherein transmitting the appointment reminder including data describing the scheduled appointment to the client device comprises:

initiating a telephone call to the client device.

33. The computer program product of claim 25, wherein the user profile identifies a communication protocol for transmitting data associated with the interaction record received from the first service provider to the client device.

34. The computer program product of claim 25, wherein the computer executable code further performs the steps of:

receiving data from a second service provider associated with the healthcare product or service, the second service provider being independent from the first service provider;

associating the data from the second service provider with the user profile; and

storing the data from the second service provider.

35. The computer program product of claim 34, wherein the data from the second service provider comprises data authenticated by the second service provider.

36. The computer program product of claim 34, wherein the computer executable code further performs the steps of:

associating a setting in the user profile with the data from the second service provider, the setting determining whether the data from the second service provider is accessible by one or more additional service providers, the one or more additional service providers being independent from the first service provider and the second service provider.

37. The computer program product of claim 25, wherein the plurality of independent service providers comprise at least one of a hospital, a pharmacy, a physician office, a clinic, a medical laboratory, a physician rating service, a hospital rating service, a personal health record store, a health coach, a health bank, a health information provider, a health savings account, a flexible savings account, a health reimbursement arrangement, a medical savings account, a diagnostic imaging facility, an outpatient surgery facility, a long-term care facility, an urgent care facility and an insurance provider.

38. A method for managing a healthcare product or service comprising:

receiving, with one or more processors, an interaction record associated with the healthcare product or service from a service provider that includes an appointment request identifying a first time for receipt of the healthcare product or service and a distance for receiving the healthcare product or service;

identifying, with the one or more processors, a user profile associated with the interaction record, the user profile including data describing healthcare information associated with a user of a client device;

storing, with the one or more processors, the interaction record in the user profile;

transmitting, with the one or more processors, the interaction record to the client device associated with the user profile based on a setting included in the user profile, the setting included in the user profile identifying a plurality of communication protocols;

transmitting, with the one or more processors, an appointment reminder including data describing a scheduled appointment associated with the appointment request and the first service provider'"'"'s preference specifying a time window prior to a start of the scheduled appointment for sending a check-in request to the client device;

transmitting, with the one or more processors, a delay notification to the client device for rescheduling the scheduled appointment to a second time;

receiving, with the one or more processors, a check-in request from the client device responsive to the appointment reminder and the user being able to take the scheduled appointment, the received check-in request being associated with the interaction record;

responsive to receiving the check-in request,

retrieving, with the one or more processors, healthcare information associated with the appointment request;

transmitting, with the one or more processors, the retrieved healthcare information from the user profile to the service provider prior to the user'"'"'s arrival at the service provider; and

receiving, with the one or more processors, user profile information from the service provider that includes results of a treatment and suggested follow-up treatments; and

responsive to failing to receive the check-in request,

transmitting a miss notification to the client device for notifying the user that the scheduled appointment was missed and prompting the user to reschedule the scheduled appointment to a third time.