Abstract: 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.

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.

Abstract: 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.

Abstract: The HIPAA Security Rule introduces problems that are solved by technical solutions including minimizing transactions among devices, reducing the number of times and places a captured image is stored, and transforming image data. Embodiments allow a user (e.g., a healthcare provider such as a physician or nurse) to use a computing device (e.g., a smart phone, a tablet, a personal digital assistant (PDA), or a personal computer) to capture an image and/or add an image (e.g., a photo of a rash), encrypt the image, transmit the encrypted image, decrypt the encrypted image, and insert the image directly into a patient medical data record while maintaining HIPAA Security Rule compliance. In embodiments, the selection of the patient medical data record may be based on a search of a user's patient list or the user's electronic appointment schedule that may be integrated into a workflow of the user's practice.

Abstract: 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.

Abstract: In an embodiment, a computer-implemented method helps a physician prescribe a medical application to a patient. In the method, a plurality of medical applications are activated in an EHR system. Then, a request to retrieve medical applications for an encounter between the physician and the patient is received. Based on the medical information describing the encounter and feature information associated with the respective medical application, the EHR system filters the plurality of medical applications to generate a suggested list of medical applications. Finally, the suggested list of medical applications is output to a device for display.

Abstract: In an embodiment, a computer-implemented method presents a patient-related medical application marketplace. In the method, a plurality of medical applications are activated in an EHR system. Then, a request for browsing the medical application marketplace is received. Based on medical information describing health of the patient and feature information associated with the plurality of medical applications, the EHR system filters the plurality of medical applications to generate a recommended list of medical applications. Finally, the recommended list of medical applications is output to a device for display to the patient.

Abstract: In an embodiment, a computer-implemented method presents a physician-related medical application marketplace. In the method, a plurality of medical applications are activated in the EHR system. Then, a request for browsing the medical application marketplace is received. Based on medical information describing practice of the physician and feature information associated with the plurality of medical applications, the EHR system filters the plurality of medical applications to generate a recommended list of medical applications. Finally, the recommended list of medical applications is output to a device for display to the physician.

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.

Abstract: 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.

Abstract: 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 physician's account. To integrate a physician'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 physician's account. Embodiments securely provide these APIs to third party providers.

Abstract: 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.

Abstract: 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.