Elation EMR API: Development and Usage Guide Adhering to ONC Standards
Getting started with the Elation FHIR API
Summary
Elation explains that its EMR system's API adheres to the HL7 FHIR R4 specification, meeting the requirements for the ONC Certified 'Standardized API for Patient and Population Services'. The guide provides information for partners and customers (trusted developers) integrating the API into their workflows, detailing steps from sandbox testing to production use.
Details
The Elation EMR API is designed to meet HL7 FHIR R4 specifications and comply with the requirements of the ONC Certified (g)(10) Standardized API. This API targets partners and customers—referred to as 'trusted developers'—who intend to integrate it into their healthcare workflows. Developers can begin by testing in a sandbox environment, which is PHI-free for privacy. For production use, users must follow the Authentication and Authorization guide for client registration and token generation. The process also involves data sharing consent and potential fees. Accessing production requires meeting specific conditions outlined by Elation. The platform emphasizes adherence to U.S. standards for healthcare information exchange. Developers are required to review and sign API terms of service, while the sandbox environment allows self-service credential management without needing support tickets. The guide outlines a structured path from initial testing to full production integration, including details on pricing and necessary authorizations.
Original content copyright by respective publishers