COLLABORATIVE HEALTHCARE

• US 20110099027A1
• Filed: 10/22/2010
• Published: 04/28/2011
• Est. Priority Date: 10/22/2009
• Status: Abandoned Application

• Current Assignee: Vitalz Technologies LLC
• Original Assignee: Vitalz Technologies LLC
• Inventors: Weathers, R. David
• Application Number:
  US12/910,766
• Publication Number:
  US 20110099027A1
• Time in Patent Office: Days
• US Class Current: 705/2
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 21/6263 during internet communication, e.g. revealing personal data from cookies
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 70/20 relating to practices or guidelines

Abstract

A specialty programmed computing system provides a platform for collaboratively providing and consuming healthcare products and services. Modules of the platform and third-party modules (accessing through an API) process and display patient EHR, practice management information, relationship (social network) information, and organizational structure information that is stored within the system and/or in data repositories of member entities in state/regional/national health information exchanges. The patent and/or provider portal is branded for the sponsoring organization, and communication tools and resources are made available to a given user based on their role, affiliation(s), and relationships.

Claims

1. A system for managing health information, comprising a processor and a memory in communication with the processor, the memory storing programming instructions executable by the processor to:

maintain an index of patients;

manage a first database of health information about the patients in a first data format;

enable read-write access to a separate database of health information about at least one of the patients, where the separate database is in a second data format, by implementing a bidirectional mapping between the first data format and the second data format; and

as a function of business rules, health information from the first database, and health information in the separate database, automatically creating a secure electronic message accessible only to a specific authenticated user of the system.

2. The system of claim 0, wherein the automatically created message is triggered by a real-life event related to the authenticated user.

3. The system of claim 2, wherein the event is reflected in a change in the data in the first database.

4. The system of claim 0, wherein the automatically created message is triggered by command of a different authenticated user of the system.

5. The system of claim 0, wherein:

the authenticated user is a patient; and

the content of the automatically created message is post-consultation follow-up instructions for the user.

6. A system for managing health information, comprising a processor and a memory, the memory being encoded with programming instructions executable by the processor to display a user interface that:

authenticates a user;

once a user is authenticated, accepts input from the user; and

interprets the input to control access across computing systems of multiple providers, which includes controlling the flow of data to or from the providers'"'"' systems;

wherein the providers'"'"' systems do not natively exchange data with each other.

7. The system of claim 6, wherein at least one of the providers is a physician.

8. The system of claim 6, wherein at least one of the providers is a hospital.

9. The system of claim 6, wherein at least one of the providers is a dentist.

10. A system for managing health information, comprising a processor and a memory in communication with the processor, the memory storing programming instructions executable by the processor to:

maintain a database of patient health data and patient-provider relationships;

provide a computing facility for a third party to implement an extension to the systems, wherein the extension accesses the patient health data and patient-provider relationship data;

wherein the access provided to the extension is limited as a function of patient permission data in the database.

11. The system of claim 10, wherein the access provided to the extension is further limited as a function of patient-provider relationship data in the database.

12. The system of claim 10, wherein the access provided to the extension is further limited as a function of provider affiliation data in the database.