Universal application integrator
A universal application integrator system enables the automated integration of data from patient care devices into electronic health records (EHRs). In addition, the system acts as a context manager between these patient care devices, EHR applications, and ancillary specific patient care applications. The system is the central controller for direct integration with patient care devices. This allows for click-once implementation and automated driver uploads for patient care devices. Third party application integration allows for device and patient context information to be shared among applications in a standardized patient care fashion.
1. A networked electronic health record (ERR) computer system enabling electronic access to patient data of electronic health records (ERRs), comprising:
an ERR database, which stores ERRs for a plurality of patients;
an ERR module, which reads and writes patient data to ERRs in the ERR database;
a device interface module comprising an application driver layer or framework configured to receive, from a plurality of patient care devices (PCDs), patient diagnostic data in different formats, and standardize the received patient diagnostic data to an integrated format of the ERRs stored in the ERR database;
a context manager, which provides context information to and receives context information from each of the plurality of PCDs, applications, and services, wherein the context information for a particular communication is based at least in part on the respective PCD, respective application, or respective service of the communication;
a service module, which provides information to each of a plurality of services for supporting performance of the respective service, the information provided to a particular service being in a format usable by the service; and
an application module, which, electronically provides patient data from the ERRs to each of a plurality of applications, the patient data electronically provided to a particular application being in a format that usable by the application, and receives patient data from each of the plurality of applications for saving in the ERRs of the ERR computer system;
wherein the context manager is configured to provide a first instance of context information to a first PCD, the first instance of context information comprising at least one of patient bibliographic data, procedure codes, and billing information for a particular patient,
wherein the device interface module is configured to receive patient diagnostic data from the first PCD in response to the provided first instance of context information, and save the patient diagnostic data in a respective ERR for the particular patient that is stored in the ERR database, by writing of the patient diagnostic data by the ERR module to the respective ERR for the particular patient, and set a flag indicating that the ERR of the particular patient has been updated by patient data.
2. The ERR computer system of claim 1 , wherein the patient bibliographic data comprises at least one of (i) a unique patient identifier that identifies the patient in the networked ERR computer system, (i) a patient's name, (i) a patient's address, and (ii) a patient's date of birth.
3. The ERR computer system of claim 1 , wherein the application module communicates with an application over the Internet.
4. The ERR computer system of claim 1 , wherein the context manager receives patient identifier information and causes the ERR module to retrieve the respective ERR of the patient from the ERR database based on the patient identifier information.
5. The ERR computer system of claim 1 , wherein the service module automatically provides information to a billing service upon receipt of particular patient diagnostic data by the device interface module.
6. The ERR computer system of claim 1 , wherein the service module provides information to a service by causing a paper-based output of the information at an applicable physical location associated with the service.
7. The ERR computer system of claim 1 , wherein the service module provides information to a service by causing electronic document capture of the information by an application associated with the service.
8. The ERR computer system of claim 1 , wherein the system further comprises a configurable rules processor that enables the automated generation of tasks based on patient diagnostic data that is received by the device interface module.
9. The ERR computer system of claim 1 , wherein the system further comprises a configurable rules processor that automatically generates an alert based on patient diagnostic data that is received by the device interface module.
10. The ERR computer system of claim 1 , wherein the plurality of PCDs comprise a PCD configured to measure a patient's heart rate.
11. The ERR computer system of claim 1 , wherein the plurality of PCDs comprise a PCD configured to measure a patient's blood pressure.
12. The ERR computer system of claim 1 , wherein the plurality of PCDs comprise a PCD configured to measure a patient's temperature.
13. A method of operating a networked electronic health record (ERR) computer system enabling electronic access to patient data of electronic health records (ERRs), comprising:
storing ERRs for a plurality of patients in an ERR database;
reading and writing patient data to ERRs in the ERR database via an ERR module;
receiving, via a device interface module comprising an application driver layer or framework, patient diagnostic data in different formats from a plurality of patient care devices (PCDs);
standardizing, via the device interface module, the received patient diagnostic data to an integrated format of the ERRs stored in the ERR database;
electronically providing, via a context manager, context information to and receiving context information from each of the plurality of PCDs, applications, and services, wherein the context information for a particular communication is based at least in part on the respective PCD, respective application, or respective service of the communication;
electronically providing, via a service module, information to each of a plurality of services for supporting performance of the respective service, the information provided to a particular service being in a format usable by the service;
electronically providing, via an application module, patient data from the ERRs to each of a plurality of applications, the patient data electronically provided to a particular application being in a format that usable by the application, and receives patient data from each of the plurality of applications for saving in the ERRs of the ERR computer system; and
electronically providing, via the context manager, a first instance of context information to a first PCD, the first instance of context information comprising at least one of patient bibliographic data, procedure codes, and billing information for a particular patient,
receiving, via the device interface module, patient diagnostic data from the first PCD in response to the provided first instance of context information, and saving the patient diagnostic data in a respective ERR for the particular patient that is stored in the ERR database, by writing the patient diagnostic data by the ERR module to the respective ERR for the particular patient, and setting a flag indicating that the ERR of the particular patient has been updated by patient data.
14. The method of claim 13 , wherein the patient bibliographic data comprises at least one of (i) a unique patient identifier that identifies the patient in the networked ERR computer system, (i) a patient's name, (i) a patient's address, and (ii) a patient's date of birth.
15. The method of claim 13 , wherein electronically providing, via the application module, patient data comprises communicating with an application over the Internet.
16. The method of claim 13 , further comprising receiving, via the context manager, patient identifier information and causing the ERR module to retrieve the respective ERR of the patient from the ERR database based on the patient identifier information.
17. The method of claim 13 , further comprising automatically providing, via the service module, information to a billing service upon receipt of particular patient diagnostic data by the device interface module.
18. The method of claim 13 , further comprising providing, via the service module, information to a service by causing a paper-based output of the information at an applicable physical location associated with the service.
19. The method of claim 13 , further comprising providing, via the service module, information to a service by causing electronic document capture of the information by an application associated with the service.
20. The method of claim 13 , further comprising enabling, via a configurable rules processor, an automated generation of tasks based on patient diagnostic data that is received by the device interface module.
21. The method of claim 13 , further comprising automatically generating, via a configurable rules processor, an alert based on patient diagnostic data that is received by the device interface module.