Custom Integrations

What is available

• API and webhooks (experimental): read claims and appointments with a scoped API key, and receive signed events when visits, notes, charges, claims, remittances and payments change. Managed by an administrator in Settings → API & Integrations, and available only once the deployment and your organisation have switched it on. API reference
• Clearinghouse SFTP mailbox: claims go out as X12 837P files, and 999, 277CA and 835 files are read back, through any clearinghouse that offers an SFTP mailbox. Off until the mailbox credentials are entered. Clearinghouse
• File import: an administrator can set up S3, SFTP or manual-upload connections in Settings → Integrations → Connections and test them.File pipelines are not available yet: inbound files are not imported into ArkCloud and exports are not generated or delivered. 835 remittance files can be uploaded by hand.
• Other packaged integrations (payments, email, SMS, Amazon Connect, Google sign-in). Each one's page says what it does and what it needs before it works. EHR, HL7 and FHIR exchange with external systems is not available, apart from two Rehab connections an administrator sets up per partner, neither yet proven with a real partner system: the FHIR referral exchange, which receives referrals from a referring EHR (see FHIR), and the read-only import of outside records from a hospital's FHIR service (see outside records).
• Integration set up by ArkCloud during implementation for a system that has no packaged connector.

Requesting an integration

Tell us which system you need to connect and what has to flow in each direction: [email protected]. See the API reference for exactly what the API covers today.