Key Benefits
Everything you need in integrations
FHIR R4 DocumentReference export, with the review record attached
HMAC-SHA256 signed webhooks you can verify
Automatic retries with exponential backoff
Versioned REST API with scoped API keys
Delivery history and per-attempt logs
Email delivery to named recipients
Real-World Use Cases
See how professionals use integrations
Into a Clinical System of Record
Export an approved document as a FHIR R4 DocumentReference. The attestation travels with it - who reviewed the content, over what hash, and how long after the transcript - so the review record lands in your system rather than staying in ours.
Push to Your Own System
Receive a signed callback the moment a document is approved, and write it wherever you keep records.
Client Delivery
Email the finished document to the people who need it as soon as it is signed off.
Scheduled Retrieval
Pull completed work on your own schedule through the versioned API using a scoped key.
Audit and Reconciliation
Every delivery attempt is logged with its response, so a missed handoff is visible rather than silent.
Technical Details
Under the hood of integrations
API
Versioned REST endpoints with cursor pagination and per-key scopes. Read access today; write access is on the roadmap.
FHIR R4
Approved documents export as a base R4 DocumentReference with the content embedded and the attestation carried in authenticator, date, and namespaced extensions. Pull it from the API, or configure a delivery rule to push it to your FHIR server the moment a document is approved. A document nobody verified is exported as preliminary and carries no authenticator, because claiming otherwise would put an unreviewed note into a patient record. No implementation-guide profile is asserted and no EHR vendor is claimed - we will name one when we have tested against its sandbox, not before.
Webhooks
Real-time notifications for document creation, updates, and exports.
Rate Limits
Generous rate limits with burst capacity for high-volume integrations.