ELECTRONIC HEALTH RECORDS DATA MANAGEMENT SYSTEMS AND METHODS

• US 20160042124A1
• Filed: 08/08/2014
• Published: 02/11/2016
• Est. Priority Date: 08/08/2014
• Status: Active Grant

• Current Assignee: Allscripts Software LLC (Veradigm, Inc.)
• Original Assignee: Practice Fusion Incorporated (Veradigm, Inc.)
• Inventors: DOUGLASS, Matthew Christopher, Malek, Jonathan Mark
• Granted Patent: US 9,824,185 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass

Abstract

Systems and methods are disclosed for managing and storing electronic health records data. In an embodiment, a database module containing a plurality of databases stores a plurality of different types of patient medical data records. Each patient medical data record is composed of one or more categories of data which may be stored in different databases. A server module configured to respond to requests received from a client is connected to the database module. The server module includes a layer of application logic, a layer of composite services, a layer of domain services, and a layer of foundation services. A request received by the server module is first processed by the application logic, then by the appropriate composite services, domain services and foundation services. Domain services may communicate with the database module, generating a response that may be processed by the composite and application logic layers before sending back to the client.

Claims

1. An electronic health records system, comprising:

a database module, comprising a plurality of databases storing a plurality of different types of patient medical data records, each patient medical data record comprising one or more categories of data, and each of the plurality of databases storing one or more categories of data such that no category of data resides in more than one database; and

a server module connected to the database module, comprising;

a domain layer comprising a plurality of domain services, the domain services configured to interact with the plurality of databases, wherein each of the plurality of domain services corresponds to a single category of data;

a composite layer comprising a plurality of composite services, the composite services configured to integrate data from a plurality of different domain services and initiate communication with the domain layer; and

an application logic layer configured to respond to requests received via a network and initiate communication with the composite layer and the domain layer.

2. The system of claim 1, wherein the server module further comprises:

a foundation layer comprising a plurality of foundation services, the foundation services configured to interact with the plurality of databases, and wherein communication with the foundation layer can be initiated by the domain layer, the composite layer, and the application logic layer.

3. The system of claim 1, wherein the server module is connected to the database module via a network.

4. The system of claim 1, wherein the plurality of databases of the database module are located in the same physical location.

5. The system of claim 1, wherein the categories of data stored in the plurality of databases comprise:

practice data, patient data, message data, schedule data, document data, patient chart data, lab vendor data, lab results data, report data and e-prescription data.

6. The system of claim 1, wherein the plurality of composite services includes an authorization service configured to determine whether a request received by the server module has sufficient permissions to complete.

7. An electronic health records system, comprising:

a database module, comprising a plurality of databases storing a plurality of different types of patient medical data records, each patient medical data record comprising one or more categories of data, and each of the plurality of databases storing at most one category of data; and

a server module connected to the database module, comprising;

a domain layer comprising a plurality of domain services, the domain services configured to interact with the plurality of databases, wherein each of the plurality of domain services corresponds to a single category of data;

a composite layer comprising a plurality of composite services, the composite services configured to integrate data from a plurality of different domain services and initiate communication with the domain layer; and

an application logic layer configured to respond to requests received via a network and initiate communication with the composite layer and the domain layer.

8. The system of claim 7, wherein the server module farther comprises:

A foundation layer comprising a plurality of foundation services, the foundation services configured to interact with the plurality of databases, and wherein communication with the foundation layer can be initiated by the domain layer, the composite layer, and the application logic layer.

9. The system of claim 7, wherein the server module is connected to the database module via a network.

10. The system of claim 7, wherein the plurality of databases of the database module are located in the same physical location.

11. The system of claim 7, wherein the categories of data stored in the plurality of databases comprise:

practice data, patient data, message data, schedule data, document data, patient chart data, lab vendor data, lab results data, report data and e-prescription data.

12. The system of claim 7, Wherein the plurality of composite services includes an authorization service configured to determine whether a request received by the server module has sufficient permissions to complete.

13. A computer-implemented method for managing and storing electronic health records data, comprising:

receiving a request into a central EHR system via a network from a requester;

processing the request to identify a list of composite services to call;

issuing calls to each composite service in the list of composite services;

processing the request to identify a list of domain services to call;

issuing calls to each domain service in the list of domain services;

communicating with a plurality of databases storing a plurality of different types of patient medical data records, each patient medical data record comprising one or more categories of data, wherein a response is generated from said communication; and

processing the response and sending the processed response via the network to the requester.

14. The method of claim 13, wherein the communicating with a plurality of databases is accomplished via a network.

15. The method of claim 13, wherein the plurality of databases are located in the same physical location.

16. The method of claim 13, wherein the categories of data comprise:

practice data, patient data, message data, schedule data, document data, patient chart data, lab vendor data, lab results data, report data and e-prescription data.