With SMART on FHIR, developers can connect the FHIR framework with an API to improve communication between their applications. This will have a profound impact on interoperability and enable data exchange not currently feasible with HL7 is a Standards Developing Organization accredited by the American National Standards Institute (ANSI) to author consensus-based standards representing a board view from healthcare system stakeholders. HL7 has compiled a collection of message form... More V2. In the case of EHRs, capturing and transmitting relevant data could be as simple as pressing a button once SMART on An HL7 standard that is short for Fast Healthcare Interoperability Resources and pronounced “Fire”. The standard defines a set of “Resources” that represent granular clinical concepts. The resources provide flexibility for a range of healthca... More is implemented.
Information from an Electronic Health Record (EHR), as defined in Defining Key Health Information Technology Terms (The National Alliance for Health Information Technology, April 28, 2008): An electronic record of health-related information on an individual that conform... More is vital when making clinical decisions, but the lack of a direct connection restricts the flow of data. As EHRs begin to adopt FHIR, mobile application interfaces to mobile applications could be created simply in Cerner, Epic, Allscripts, eClinicalworks, etc., using the SMART framework for data exchange. For example, after the mobile app engages the EHR, a browser window could open, giving the user direct access to pull information out and integrate it for caregivers to use in real time. In comparison to HL7 V2, this integration would reduce development time and enable greater use of the EHR data in relevant workflows.
Watch Corepoint Health CTO Dave Shaver discuss in more detail: