Healthcare
interoperability.

CMS/ONC compliance, USCDI data classes, SMART on FHIR launches, and bulk-data export — the platform layer that makes your roadmap a regulatory non-event.

Brief us See work
What we build

We build healthcare interoperability platforms aligned with CMS Interoperability and Patient Access, ONC Cures Act, and the data-classes in USCDI. SMART on FHIR app launch, bulk-data export, and proper conformance testing — the regulatory side and the engineering side, run as one program.

Problem · approach · outcome.

How we run this kind of work
01 · Problem

Regulators wrote the rules; somebody still has to build to them.

CMS, ONC, and the rest published rules; the engineering work is yours. Most teams understand the standards but underestimate the operational discipline they require — conformance testing, audit trail, public-facing API documentation, and ongoing US Core IG alignment as it updates.

02 · Approach

Conformance as a system, not a checkbox.

We build to the published Implementation Guides (US Core, CARIN BB, Da Vinci PDex/PCDH/HRex, IPS) with conformance tests in CI. Bulk Data Export is implemented to the actual NDJSON spec, not a flat-file approximation. SMART app launch passes the open-source test harness.

03 · Outcome

A platform you can show to a regulator without rehearsing.

Public-facing developer portal, conformance dashboard, and audit trail. Patient Access API, Provider Directory API, and Payer-to-Payer exchange — all running and documented.

What we ship.

6 modules · extensible
F-01

US Core profiles

Implementation against the published US Core IG with conformance tests in CI — versioned across IG updates.

F-02

Bulk Data Export

FHIR Bulk Data Export (NDJSON over HTTP) for cohort-scale extraction by payers, researchers, and accountable-care organisations.

F-03

SMART app launch

SMART on FHIR app launch framework — passes the open-source SMART test harness for EHR and standalone launch.

F-04

Patient Access API

CMS-mandated Patient Access API for payer organisations — exposes claims, encounters, formulary, and provider directory data.

F-05

Provider Directory API

Da Vinci PDex Provider Directory IG implementation — searchable provider network with quality data.

F-06

Developer portal

Public-facing API documentation, sandbox, and registration flow — auditor-defensible and developer-friendly.

Tech stack.

Production-tested
FHIR servers
HAPI FHIRMicrosoft FHIR ServiceAidboxAWS HealthLake
IGs
US CoreCARIN BBDa Vinci PDexDa Vinci HRexIPS
Stack
Java / KotlinNode.jsPostgreSQLElasticsearch
Standards
FHIR R4 / R5SMART on FHIROAuth 2.0

Have a CMS
or ONC deadline?

Healthcare interop · 8-week starts
Get a quote

Healthcare interoperability FAQs.

Q-01Do you support CMS Patient Access API requirements?
Yes — full implementation of the Patient Access API for payers including claims, encounters, formulary, and provider directory data.
Q-02What is SMART on FHIR and do you implement it?
SMART on FHIR is a standard for app launch and authorisation inside an EHR. We implement it for both EHR-launched and standalone apps; our implementations pass the open-source SMART test harness.
Q-03Can you do FHIR Bulk Data Export?
Yes — to the published spec (NDJSON over HTTP) for cohort-scale extraction. Used by ACOs, researchers, and payer-to-payer exchange.
Q-04Which FHIR Implementation Guides do you support?
US Core, CARIN BB, Da Vinci PDex / HRex / PCDH, IPS, and others. We track IG updates and run conformance tests in CI.
Q-05Do you build this with HAPI FHIR or Microsoft FHIR?
Both, plus Aidbox and AWS HealthLake. Choice depends on volume, deployment, and the partner ecosystem you have to interoperate with.

Related across the cluster.