The systems ArkCloud connects to.
Every integration below is implemented in ArkCloud Health and names the code that implements it. None runs on a shared ArkCloud account: each uses credentials your organisation supplies and controls.
Electronic health records
Read and write against the EHR of record. Each connector speaks that vendor's own API; the FHIR connector covers systems exposing a conformant FHIR endpoint rather than a proprietary one.
- EpicImplemented
Patient, encounter and coverage retrieval against the Epic API.
lib/ehr/connectors/epic-connector.ts - Oracle Health (Cerner)Implemented
Equivalent retrieval against the Cerner API.
lib/ehr/connectors/cerner-connector.ts - athenahealthImplemented
Equivalent retrieval against the athenahealth API.
lib/ehr/connectors/athena-connector.ts - Generic FHIRImplemented
For any system exposing a conformant FHIR R4 endpoint, including EHRs without a dedicated connector above.
lib/ehr/connectors/fhir-connector.ts
Clearinghouses and EDI
Claims leave as X12 837 and remittances return as X12 835. The clearinghouse is the route; the X12 generation and parsing are ours.
- AvailityImplemented
Claim submission and status retrieval.
lib/edi/clearinghouse/availity.ts - WaystarImplemented
Claim submission and status retrieval.
lib/edi/clearinghouse/waystar.ts - Change HealthcareImplemented
Claim submission and status retrieval.
lib/edi/clearinghouse/change-healthcare.ts - X12 837 and 835Implemented
Claim generation and remittance posting, including SFTP transport where a payer or clearinghouse requires it.
lib/edi/claim-submission.ts
Payments
Patient payments and payment plans. In production a processor must be configured; the system refuses to run rather than silently reporting a payment that never happened.
- StripeImplemented
Card payments, including Stripe Elements in the patient portal.
lib/payment-processor.ts - SquareImplemented
Card payments through Square.
lib/payment-processor.ts - Authorize.NetImplemented
Card payments through Authorize.Net.
lib/payment-processor.ts
Communications
Statements, reminders and notifications to patients and staff.
- SendGridImplemented
Transactional email, including statement delivery.
lib/email.ts - TwilioImplemented
SMS notifications.
lib/email.ts
Identity
One ArkCloud account per person, federated to the identity provider the organisation already runs.
- Microsoft Entra IDImplemented
OIDC single sign-on with PKCE. Supports single-tenant and multi-tenant directories.
lib/auth/config.ts - Google WorkspaceImplemented
OIDC single sign-on with PKCE.
lib/auth/config.ts - SAMLImplemented
Per-tenant SAML configuration exists in the application. Treat it as available only once your directory has been tested against it.
app/(dashboard)/dashboard/settings/security/sso
Infrastructure
Not third-party product integrations so much as the services ArkCloud runs on. Listed because procurement asks where data goes.
- S3-compatible object storageImplemented
Documents and exports. One storage API across environments, so local and cloud are not two divergent code paths.
lib/storage/s3-client-factory.ts - Cold storage archivalImplemented
Long-term retention of aged records to Glacier-class storage.
lib/cold-storage/glacier-archival.ts
What “implemented” means here
That the connector is written and exercised by this codebase, not that ArkCloud holds a partnership, certification or marketplace listing with the vendor. Every integration needs credentials your organisation supplies, and where they are absent the system returns an explicit error rather than a silent success.