Integrations

One API, and an honest list of what connects today

Arcapse is built on a REST /v1 API with a committed OpenAPI spec and FHIR-aligned resources. Below is what is live and what is roadmap, named as such — scheduling, messaging, audit and users already run on that API from the portal, and the remaining screens are migrating onto it. We would rather you read the gaps here than find them in a scoping call.

REST /v1 API — live

One versioned API under one committed OpenAPI spec, the same one the portal is being migrated onto. Authenticates the same sessions the portal does; scoped API keys are roadmap.

Learn More

FHIR R4 read facade — live

Patient, Practitioner and Encounter plus a capability statement, tenancy-preserving and end-to-end tested. Resources were named FHIR-aligned from day one, so this is a mapper rather than a translation project.

Learn More

State EVV aggregators — live

Sandata, HHAeXchange and AuthentiCare export builders over one shared input and one date-window query. Provider enrollment per state programme is paperwork on your side, not code on ours.

Learn More

Payroll export — live

A deliberately generic CSV: employee id, period, minutes by band, cents by band. No names, no clients, no addresses — a payroll file leaves the building by definition. Your provider maps it once.

Learn More

X12 837P + 835 claims — live

Professional claim generation and remittance parsing, behind a scrub that will not release a line without a verified visit, a signed note and a live authorization. 837I (institutional) is not built.

Learn More

Ontario Health atHome — adapter only

Referral, EVV and claims interfaces are written and tested against a fixture, enforcing the rules that cost money when an integration gets them wrong. The live connection needs the partner spec pack, a PIA and a TRA.

Learn More

Scoped API keys & webhooks — roadmap

Not built. The API authenticates portal sessions today, and the only webhook in the product is inbound from the payment processor. Server-to-server keys with scopes, and outbound signed webhooks, are the next integration milestone.

Learn More

Accounting & payroll connectors — roadmap

Not built. There is no QuickBooks, Xero, ADP, Ceridian, Gusto or Paychex code in the product; the CSV export above is how hours and invoices leave today. Connectors are gated on sandbox accounts with each vendor.

Learn More

Telephony / IVR clock-in — pipeline built

Line registry, caller-ID matching, call log and the unregistered-caller path into the exceptions queue are built and work end to end, on the same demo data tier as most portal screens; a simulator drives the identical pipeline. What is missing is a live carrier number.

Learn More

Give every client better care, starting this week

Start free and run your first verified visit in days — or book a demo and we’ll walk your team through scheduling, billing, and the family portal.

Get Started For Free