Practice Fusion, Inc.

Allscripts Software, LLC

Matthew Christopher Douglass

Jonathan Mark Malek

Thomas William Evans

Ryan Paul Howard

Embodiments allow for the retrieval of information identifying the current context (patient being seen, medical record associated with the patient, or medical field selected) of a practice member. That information may be used as a key for subsequent API calls to match data submitted with records in an EHR system. In addition, a confidence level may be associated with that context. The confidence level may describe the level of confidence that context is correctly associated with that key.

Electronic health record system context API

In an embodiment, a computer-implemented method aggregates medical data from a plurality of source providers. In the method, medical data is received from a source provider. This medical data may be associated with patient-identification information. In order to aggregate this data with other data about the same patient, this data is then reconciled with existing patient medical data records in a medical records database to identify a master patient to whom the received medical data relates. The medical records database includes a plurality of different types of patient medical data records, and each data record is associated with a corresponding time and a corresponding source. Verification is performed to confirm that the source provider associated with the received medical data is authorized to add medical data related to the identified master patient, and finally a new medical data record containing the received medical data is written to the database.

Aggregating a patient's disparate medical data from multiple sources

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.

Electronic health records data management systems and methods

Embodiments include an offline application, encrypted patient medical data records, and an encryption key that are stored in a cache of a browser application on the local computing device when a network connection is available. The offline application is accessed when the network connection is subsequently lost. Embodiments allow the user to access decrypted patient medical data records stored in the browser application cache, as well as create and access new patient medical data records when a network connection is offline. Any access to a patient medical data record when the network connection is offline may be documented in an offline-access record, an audit record that satisfies HIPAA Security Rule restrictions, that is created and encrypted. When a network connection becomes available, corresponding patient medical data records in the EHR system are updated or created according to the offline-access record and/or an offline-updated patient medical data record.

Offline electronic health record management

Embodiments relate to integrating data collection and productivity applications with an EHR system. To integrate a patient's data collection application with the EHR system, an EHR server provides API calls to (i) retrieve patient information, (ii) post data to the patient's account, and (iii) post data to the medical professional's account. To integrate a medical professional's productivity application with the EHR system, an EHR server provides API calls to (i) retrieve practice information, (ii) retrieve patient information, and (iii) post data to the medical professional's account. Embodiments securely provide these APIs to third party providers.

Growing community of inventors

San Francisco, CA, United States of America

Matthew Christopher Douglass