This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with security in the subject line and you will get a person, not a form. We will tell you exactly which public URLs this profile was built from so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
Smile Digital Health (formerly Smile CDR) is a Toronto-based health interoperability software company and the commercial steward of the open source HAPI FHIR project — the world's most widely deployed Java implementation of the HL7 FHIR standard. Its flagship platform, Smile CDR (marketed under the Smile Omni portfolio as the OmniVera Health Data Platform), is a FHIR-native clinical data repository and integration engine that ingests HL7 v2.x, CDA, CSV, JSON, XML, and FHIR payloads, normalizes them to FHIR (R4, R5, STU3, DSTU2), and exposes them through a hardened FHIR REST API, SMART on FHIR / OAuth2 / OIDC, Bulk Data, Subscriptions, MDM, Terminology Services, CQL-based Quality Measures, and a JSON Admin API.
URL: Visit APIs.json
- Healthcare, FHIR, HL7, Clinical Data Repository, Interoperability, HAPI FHIR, SMART on FHIR, Terminology Services, MDM, Bulk Data, Subscriptions, CMS Interoperability, Prior Authorization, Digital Quality Measures, CQL, Payer, Provider
- Created: 2026-05-24
- Modified: 2026-05-24
| Family | Purpose | Key Modules |
|---|---|---|
| OmniVera | FHIR-native data platform (Smile CDR) | Health Data Platform, Data Quality+, Data Access+ |
| OmniCompli | Regulatory compliance for US payers | CMS Suite, CMS Suite+, CMS Concierge |
| OmniQ | Digital quality measurement | dQM (HEDIS + custom), Intelligence Hub |
| OmniConcierge | Implementation and operations | Managed Services, Professional Services, Knowledge |
Core FHIR REST API — full FHIR REST interaction set (read, vread, update, patch, delete, history, search, transaction, batch, conditional CRUD) across FHIR R4, R5, STU3, DSTU2. OpenAPI / Swagger UI auto-generated at {baseUrl}/swagger-ui/.
- Documentation — FHIR Standard
- Documentation — CRUD Operations
- Documentation — Searching
- OpenAPI / Swagger Support
- Public Swagger UI — HAPI FHIR test server
SMART on FHIR / OAuth2 / OIDC authorization for FHIR endpoints — standalone launch, EHR launch, PKCE, refresh tokens, consent, .well-known/smart-configuration.
FHIR Bulk Data Access (Flat FHIR) — asynchronous system-, group-, and patient-level NDJSON export with backend-services authorization.
FHIR R4 Subscription and R4B/R5 Subscription / SubscriptionTopic backport — REST hook, websocket, email, and message-queue channels.
FHIR-native MDM for Patient and Practitioner — probabilistic matching, golden records, candidate rules, survivorship, $mdm-* operations, MDM Admin endpoint.
$expand, $validate-code, $lookup, $translate, $subsumes over CodeSystem, ValueSet, ConceptMap. Bundled SNOMED CT, LOINC, ICD-10/11, RxNorm, CPT.
Clinical Quality Language engine and FHIR Clinical Reasoning module backing OmniQ dQM including HEDIS — $evaluate-measure, $apply.
Bidirectional HL7 CDA / C-CDA exchange — CDA-to-FHIR ingest and FHIR-to-CDA rendering.
MLLP HL7 v2.x inbound and outbound — ADT, ORM, ORU, MDM, SIU, VXU, DFT — with v2-to-FHIR mapping.
REST/JSON admin surface — Module Config, System Config, User Management, Audit Log, Transaction Log, Metrics, Runtime Status, Batch Job, Bulk Import, MDM Admin, OpenID Connect Clients / Keystores / Servers / Sessions.
- Documentation — JSON Admin API
- Documentation — Module Config Endpoint
- Documentation — User Management Endpoint
Pre-packaged CMS-compliant FHIR APIs for US payers — Patient Access, Provider Directory, Drug Formulary, Payer-to-Payer (CMS-9115-F), Prior Authorization (CMS-0057-F / Da Vinci PAS, CRD, DTR). Built on US Core, CARIN BB, Da Vinci, PDex profiles.
Smile Digital Health maintains HAPI FHIR, the Apache 2.0-licensed Java implementation of HL7 FHIR (>2,300 GitHub stars, 1,400+ forks). The codebase originated at University Health Network, has been developed for two decades, and is hosted at github.com/hapifhir. Smile CDR is the commercial, hardened, enterprise-supported distribution built around HAPI FHIR.
| Repository | Purpose |
|---|---|
| hapifhir/hapi-fhir | Core Java FHIR library, client, and JPA server |
| hapifhir/hapi-fhir-jpaserver-starter | Reference JPA server starter |
| hapifhir/org.hl7.fhir.core | Core FHIR standards library |
| hapifhir/org.hl7.fhir.validator-wrapper | FHIR Validator CLI, GUI, and server |
| hapifhir/hapi-hl7v2 | HL7 v2 messaging library |
| smilecdr/FHIR.ts | TypeScript / JavaScript FHIR library (Apache 2.0) |
- Website — smiledigitalhealth.com
- Smile Omni
- OmniVera Health Data Platform
- OmniCompli CMS Suite
- OmniQ Digital Quality Measures
- OmniConcierge Professional Services
- Documentation — Table of Contents
- Documentation — Installation
- Documentation — Security
- Documentation — OpenAPI / Swagger
- Documentation — JSON Admin API
- HAPI FHIR — hapifhir.io
- GitHub — Smile Digital Health
- GitHub — HAPI FHIR
- Public HAPI FHIR test server
- YouTube — @SmileCDR
- Twitter — @SmileDigiHealth
- Deployment: On-premises, AWS, Azure, GCP, Kubernetes; supported databases include PostgreSQL, MySQL, MariaDB, Oracle, SQL Server, and MongoDB
- Architecture: MegaScale horizontal partitioning, 60–80 percent storage reduction via binary offloading
- Certifications: HITRUST v9.4, SOC 2 Type II, ISO 27001 / 27017 / 27018, ISO 13485, ONC 2015 Edition
- Footprint: 190+ global implementations; 30+ US payer deployments; 2B+ records transformed to FHIR; 255K+ transactions/second on reference benchmarks; 99.99 percent annual availability target
- Pricing: Commercial; not publicly listed — quoted per deployment and module footprint
FN: Kin Lane
Email: kin@apievangelist.com