Keep your existing software — add the AI layer. Three working patterns: a live API sync (AxisCare publishes a real OpenAPI spec), a batch export (Therap's External Data Feed CSV, its only third-party path), and national-standard files (the X12 835 remittance every clearinghouse returns). Imported data is analyzed and shown; nothing is copied into CareNotes.
Pulls yesterday's visits — care notes, ADL completion, EVV clock data — over AxisCare's Bearer-token REST API, then runs the same morning-briefing AI our native digest uses. In production the base URL is the agency's own {siteNumber}.axiscare.com+ admin-issued token; this demo targets a built-in endpoint shaped to AxisCare's published spec (v2025-06-25), using their documented field shapes and example conventions.
Note on what the source data actually looks like: care notes are typed at the end of a shift and are short — AxisCare's own spec example is a single sentence. So the demo models terse notes and bullet lists, and most of the usable signal comes from the structured ADL rows (which task was not completed, and its note). That is the realistic input an integration has to work with.
I/DD providers use Therap deeply — GERs, case notes, ISP data — and in several states it is the mandated statewide incident system, so the realistic integration is alongside, not instead. Therap has no public API; its documented third-party path is the External Data Feed (ExDF): scheduled CSV exports over SFTP, refreshed multiple times daily, provisioned by Therap for the agency. Column mapping is tolerant of agency-specific export configurations.
Reachable via ExDF (documented)
No third-party path (stays in Therap)
Flow 1 — incident export → incident-trend analysis (AI)
Column mapping is tolerant, so this accepts an incident export from anysystem that can produce one — demonstrated here with Therap's documented GER format.
Flow 2 — Case Note export → documentation-compliance audit (deterministic)
Audits existing Therap documentation against the state-published standardsa licensing reviewer applies (Virginia DMAS's “Language to Avoid” and “What's NOT Required” lists). Deterministic rule scan — no AI call — and every finding cites its source rule. Works with a notes export from anysystem (tolerant column mapping) — demonstrated here with Therap's Case Note export.
The X12 835 is the HIPAA-mandated remittance format every clearinghouse and payer returns — whatever software generated the claims. Drop the 835 and see where the money is leaking: denial rates, the reason codes behind them, and which denials were preventable before submission. Deterministic parse — no AI call. This closes the billing loop: CareNotes generates the outbound 837; the 835 is what comes back.