Skip to content
API & integrations

FHIR R4. SMART on FHIR. CDS Hooks. No proprietary middleware.

Materna Health Solutions speaks the standards your team already uses. Every integration is designed to be documented, versioned, and BAA-covered. We are deliberate about what we wrap, and transparent about what we do not.

A patient at home, connected to her care team

FHIR R4

Standards we will speak

HL7 v2.x, CDS Hooks, CCDA, SMART, X12, NCPDP

Epic, Cerner, athena

EHRs targeted

Designed against the SMART on FHIR R4 spec

8

Integration categories

EHR, claims, lab, pharmacy, imaging, telehealth, identity, comms

Honest framing

Materna Health Solutions is in early development. The catalog below is what we are building, designed against published interoperability standards, not integrations running in production. We will not publish live partners, traffic metrics, or implementation timelines until a real practice is using the platform. Each item is a design goal buyers can hold us to.

The catalog

What we have designed to the standard, and what is planned.

EHR

Epic (HL7 FHIR R4)

designed

Read + write via SMART on FHIR. Designed against the SMART on FHIR R4 spec.

Oracle Cerner Millennium

designed

FHIR R4 read, CDS Hooks for risk surfacing.

athenahealth

designed

FHIR R4 read + write. Patient and encounter scoped.

eClinicalWorks

planned

FHIR R4 read. Write API in roadmap.

NextGen

planned

CCD bridge designed, FHIR R4 planned.

Claims

Medicaid 837/835 (X12)

designed

Built to the X12 spec for AHCCCS, PA Medicaid, Medi-Cal, and TX Medicaid.

Commercial X12 837P/I, 835

designed

BCBS, United, Aetna, Cigna, Anthem.

CMS 1500 / UB-04 PDF render

designed

For paper-claim contingencies.

Lab

LabCorp HL7 v2.5.1

designed

Inbound results, outbound orders.

Quest Diagnostics

designed

Inbound results, outbound orders.

In-house lab via FHIR

designed

For FQHCs running their own lab.

Pharmacy

Surescripts ePrescribing

designed

NCPDP SCRIPT 2017071. EPCS supported.

Walgreens Rx Direct

planned

Direct-to-pharmacy benefit checks.

Imaging

DICOM web (WADO-RS)

designed

Pull ultrasound studies into the chart.

Ambra Health

designed

Cross-facility imaging exchange.

Telehealth

Doxy.me embed

designed

Native iframe with chart context.

Zoom for Healthcare

designed

BAA-covered, HIPAA-aligned.

Materna native (WebRTC)

designed

Built-in, no extra logins.

Identity

OAuth 2.0 / OIDC

designed

For SSO into provider workspaces.

SAML 2.0

designed

IdP-initiated SSO supported.

SCIM 2.0

planned

Just-in-time provisioning for partners.

Comms

Twilio SMS + WhatsApp

designed

Bilingual outbound + 2-way messaging.

SendGrid email

designed

Templated, branded.

Push notifications (PWA)

designed

iOS 16.4+ and Android.

REST API

A small surface, well documented, versioned.

The Materna API is small on purpose. We expose what teams actually need to compose, and we resist the urge to publish everything.

GET

/v1/patients/{id}/risk

Returns the latest risk band and contributing factors.

GET

/v1/patients/{id}/screenings

List of validated screening results, scoped by date range.

POST

/v1/patients/{id}/messages

Send a message into the patient inbox, with optional safety tags.

POST

/v1/referrals

Create an in-network specialist referral with chart context.

GET

/v1/care-gaps

Open care gaps across your panel, filterable by severity.

POST

/v1/sdoh-requests

Create or update an SDOH closed-loop request.

GET

/v1/audit-log

HIPAA audit log query, scoped by user, patient, or date range.

POST

/v1/fhir-export

Generate a consent-gated FHIR R4 patient bundle for cross-border export.

Auth & rate limits

OAuth 2.0 client-credentials flow for system-to-system. Authorization-code flow for SMART on FHIR launches. Mutual TLS available for high-trust deployments.

Default rate limit: 600 requests / minute / client, scaled higher on demand. Bulk export jobs run on a separate quota.

SDKs

Official SDKs in TypeScript and Python. Strong typing across the surface. Generated from a published OpenAPI 3.1 spec, so unofficial SDKs in any language stay aligned.

Postman collection and a CLI scaffolder for sandbox setup. We keep examples in EN + ES, because we design for a patient base that lives in Spanish.

Webhooks

Listen for events. We send them at-least-once with a signed body.

EventDescription
patient.risk.changedA patient's risk band moved up or down.
screening.self_harm_detectedA screening or voice flagged a self-harm phrase. Always also routes to safety pathway.
care_gap.openedA new care gap was opened for a patient on your panel.
care_gap.closedA care gap was closed with a documented action.
sdoh.matchedA coordinator matched a patient to a verified resource.
sdoh.deliveredAn SDOH resource was confirmed delivered (closed loop).
visit.signedA SOAP note was finalized by the provider.
voice.safety_keywordA voice agent detected a safety keyword. Routes to safety pathway in parallel.

Bodies are signed with HMAC-SHA256. Replay protection via timestamps. Retries on a 1m, 5m, 30m, 2h, 12h schedule. Dead-letter visibility in the partner console.

Cross-border export

The thing other vendors do not have.

A consent-gated FHIR R4 bundle that carries a patient's record across health systems and across the international border, audited in both directions.

Bilingual bundle

All text values bundled in EN and ES. Receiving system selects display language with no loss of fidelity.

Consent first

Patient signs off in plain language. Consent is revocable. Each access on the receiving side is logged and visible to the patient.

Audited both ways

Every read on the receiving side, regardless of country, lands in the patient's unified audit log. Regulators and auditors can request a complete trace.

Bring your stack. We will meet it where it is.

We design each integration to connect quickly once we go live. Our integrations engineering team has real names and real Slack channels.