ZapEHR is a cloud-service for building health software, also known as a headless EHR. Its secure and compliant backend services are designed to make it easier to build features such as:
- Telemedicine EHRs (like our sample EHR, Ottehr (opens in a new tab)).
- Scheduling, intake apps, and patient portals.
- AI-enabled clinical decision support tools.
- Analytics dashboards and reporting tools.
- Insurance eligibility checking and claims management.
Integrate with your existing system, or build something totally new!
We believe that the future of healthcare is a vibrant ecosystem of apps and services that work together to reduce time to market and cut costs. We're building the infrastructure to make that future a reality.
Overview of the ZapEHR platform (click to zoom),
In the diagram, the blue boxes represent services that are provided by ZapEHR. This includes:
Authentication — Secure your apps with OAuth 2.0 standard authentication. When Users log into your applications, you get the access token used to hit ZapEHR's FHIR and Project APIs.
FHIR API — At the core of the ZapEHR platform is the FHIR (opens in a new tab) compliant FHIR API. FHIR is the industry standard for exchanging electronic healthcare information. If you're new to FHIR, you will want to start with our FHIR overview guide.
Project API — The Project API includes endpoints for every other service in the ZapEHR platform:
- App — Login and user management for your applications.
- IAM — Covers Developer access, M2M Client access (for API access from scripts and Zambda Functions), and Role configuration.
- Messaging — HIPAA-compliant rails for building healthcare messaging workflows.
- Project — Configure project-wide settings.
- RCM — Perform real-time health insurance eligibility checks.
- Telemed — Build cross-platform video calls into your applications.
- Z3 — HIPAA-compliant file storage and retrieval.
Zambda — Run custom code with ZapEHR's FHIR-integrated Function as a Service solution. Run custom code when certain conditions are met in the FHIR store, at a regular time or interval with a cron job, or using authenticated and anonymous REST API invocations.