Smile Digital Health
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 product, Smile CDR — marketed under the broader Smile Omni portfolio as the OmniVera Health Data Platform — is a FHIR-native clinical data repository and integration platform that ingests HL7 v2.x, CDA, CSV, JSON, XML, and FHIR payloads, normalizes them into FHIR (R4, R5, STU3, DSTU2), and exposes them through a hardened FHIR REST API, SMART on FHIR / OAuth2 / OIDC security, Bulk Data export, Subscriptions, MDM, Terminology Services, CQL-based Quality Measures, and a JSON Admin API. The platform is deployed on-prem and across AWS, Azure, and GCP, with HITRUST v9.4, SOC 2 Type II, ISO 27001, and ONC 2015 Edition certifications, and is used by 190+ global customers, including 30+ US payers running CMS Interoperability and Prior Authorization (CMS-0057-F) workloads on its CMS Suite. Adjacent Smile Omni product families include OmniCompli (regulatory compliance, including CMS Suite and CMS Concierge), OmniQ (digital quality measures / HEDIS, Intelligence Hub), and OmniConcierge (managed and professional services). The primary developer surface is the FHIR REST API, with per-endpoint auto-generated OpenAPI / Swagger UI at `{baseUrl}/swagger-ui/`, plus a separate JSON Admin API for cluster, module, user, audit, batch job, MDM, and OpenID Connect administration.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Smile Digital Health the way a machine reads it — 12 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Smile Digital Health scores 21.5/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Smile Digital Health
Each block below is one kind of artifact we hold for Smile Digital Health. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Smile CDR FHIR Endpoint
The core FHIR REST API exposed by every Smile CDR FHIR Endpoint module. Supports the full FHIR REST interaction set (read, vread, update, patch, delete, history, search, transac...
Smile CDR SMART on FHIR
SMART on FHIR / OAuth2 / OIDC authorization surface for FHIR endpoints, supporting standalone launch, EHR launch, public and confidential clients, scopes, PKCE, refresh tokens, ...
Smile CDR Bulk Data
Implementation of the FHIR Bulk Data Access (Flat FHIR) specification for asynchronous, system-, group-, and patient-level export of FHIR resources as NDJSON, with status pollin...
Smile CDR Subscriptions
FHIR Subscription (R4) and Subscription / SubscriptionTopic (R4B/R5 backport) support for push notifications on resource change, with REST hook, websocket, email, and message-qu...
Smile CDR Master Data Management
FHIR-native Master Data Management for Patient and Practitioner records, with probabilistic matching, golden records, candidate matching rules, survivorship, and administrative ...
Smile CDR Terminology Services
Terminology Service implementing FHIR `$expand`, `$validate-code`, `$lookup`, `$translate`, and `$subsumes` operations over CodeSystems, ValueSets, and ConceptMaps. Bundled supp...
Smile CDR CQL & Quality Measures
Clinical Quality Language (CQL) engine and FHIR Clinical Reasoning module (Measure, Library, PlanDefinition) backing OmniQ digital Quality Measures (dQM) including HEDIS measure...
Smile CDR CDA Exchange
Bidirectional HL7 CDA / C-CDA exchange — ingest CDA documents and convert to FHIR Bundle, and render FHIR data as CDA for partners that consume the older standard. Exposed via t...
Smile CDR HL7 v2.x Interface
MLLP-based HL7 v2.x inbound and outbound interfaces for ADT, ORM, ORU, MDM, SIU, VXU, and DFT messages, with bidirectional v2-to-FHIR mapping and ACK/NAK handling.
Smile CDR JSON Admin API
REST/JSON administrative API for cluster operations — Module Config, System Config, User Management, Audit Log, Transaction Log, Troubleshooting Log, Metrics, Runtime Status, Ba...
Smile CDR CMS Interoperability Suite
Pre-packaged CMS-compliant FHIR APIs for US payers — Patient Access, Provider Directory, Drug Formulary, Payer-to-Payer (CMS-9115-F) and Prior Authorization (CMS-0057-F / HL7 Da...
Scroll within the panel for all 11 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Smile Digital Health — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 6
Portal, sign-up, and the first successful call
Documentation 5
Reference material describing how the API behaves
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 9
Properties that don't map to a standard resource type
Scroll within the panel for all 9 ·
← All providers · Data indexed from github.com/api-evangelist/smile-cdr · machine-readable index on apis.io