Home › Integrations
Integrations
Connected where it counts, honest about the rest
Carezeve is built to work with the data clinics already have: diagnosis code sets built in, patient lists importable, device readings flowing in, and reports flowing out. Anything not yet connected is labeled as such — here and in the product.
Connection Status
What connects today, and what does not
Every connection below is labeled with its real status in the current pre-launch build.
| Connection | What it does | Status |
|---|---|---|
| ICD-10-CM code sets | FY2026 and FY2027 diagnosis libraries built into the product for condition and care-plan selection — no external lookup needed. | Built in |
| Patient list import (CSV) | Clinics can import existing patient lists; the import reports exactly what was created and what was skipped, and why. | Built in |
| RPM devices | Devices are enrolled to patients by serial number; readings appear in the chart and in the live monitoring view, and out-of-range readings raise alerts and tasks. | Built in |
| Reports & exports | Billing reports in PDF, CSV, and spreadsheet formats; per-patient and claim-detail downloads; a clinic data export of the clinic’s own records. | Built in |
| Phone & SMS | Per-clinic numbers, calling, and two-way texting with consent records and opt-out handling, built behind a provider connection that can be swapped. Today it runs against a clearly labeled test-mode provider — no real calls or messages are sent. | Test mode |
| External AI provider | The connection point for an approved external AI provider exists in the architecture, server-side. No provider is connected; all drafting today is local. See AI Workflows. | Not connected |
| Payer claim submission | Carezeve prepares draft claims and reports; it does not transmit claims to payers or clearinghouses. Submission stays with your billing process. | Not offered |
| External EHR connections | No live connection to an external electronic health record is offered today. Carezeve is the record for the care-management work it manages. | Not offered |
Why the labels? A connection that is not live should never look live. When a connection’s status changes, this page — and the product — will say so.
Principles
How Carezeve connects
- No vendor lock-in for communications. Calling and texting sit behind a provider layer, so the clinic’s numbers and history stay in Carezeve whichever provider is connected.
- Credentials stay server-side. Connection keys never live in the browser or in the page code.
- Agreements before data. A communications or AI provider is connected for real patient use only after the required data-protection agreements are in place.
- Your data stays yours. A clinic can export its own records; one clinic’s data is never visible to another clinic, through any connection.
Need a specific connection?
Tell us what your clinic uses today through the contact page. Connection requests from early-access clinics will shape the order in which integrations are built — but nothing will be listed here until it is real and tested.