Skip to content
ArkCloud Health

Explore the ArkCloud Platform

Seven connected healthcare applications. Each designed for a specific part of your organization's operations.

Every application runs on shared identity, tenancy, billing, security and integration infrastructure. Add an application without adding another login, another audit trail, or another security review - and buy only the ones you use.

The applications

Which part of your organisation each one serves

Compare

How the applications differ

Each application is the source of truth for its own records. Where two of them touch the same thing - Access and Rehab both show the appointment book - one owns it and the other works on it, so nothing is kept twice.

  • ArkCloud Access

    Patient Access & Intake

    Purpose:
    Take referrals, register patients, book appointments, check insurance and check patients in.
    Main users:
    Front-desk staff, Scheduling coordinators, Registration and intake teams
    Source of truth for:
    Referral intake log; Registrations; Configurable intake forms and responses
  • ArkCloud Clinical

    Clinical Decision Support

    Purpose:
    Write, review and publish clinical guidance that clinicians can consult, with its source cited.
    Main users:
    Clinical leaders and medical directors, Clinical content reviewers, Supervising clinicians
    Source of truth for:
    Clinical guidance and its review history
  • ArkCloud Rehab

    Rehabilitation & Therapy

    Purpose:
    Evaluate, treat, document and bill therapy patients from referral to discharge.
    Main users:
    Physical, occupational and speech therapists, Therapy assistants, Rehab clinic directors
    Source of truth for:
    Patients and episodes of care; Appointment book, availability, reminders and check-in; Encounters, SOAP notes, evaluations and assessments
  • ArkCloud Care

    Care Management & Coordination

    Purpose:
    Plan and track what a patient needs between and after visits.
    Main users:
    Care coordinators, Case managers, Care management nurses
    Source of truth for:
    Care pathways and patient care plans; Coordination tasks and queues; Follow-ups and outreach log
  • ArkCloud RCM

    Revenue Cycle Management

    Purpose:
    Submit claims, post payments, work denials and collect patient balances.
    Main users:
    Billing specialists, Revenue cycle managers, Collections staff
    Source of truth for:
    Patient accounts, charges and the ledger; Claims, remittances and payment posting; Denials and appeals
  • ArkCloud Insights

    Analytics & Reporting

    Purpose:
    See financial, operational and clinical performance across the organisation.
    Main users:
    Executives and practice owners, Operations leaders, Practice administrators
    Source of truth for:
    Measure definitions and their method notes (no patient or financial records of its own)
  • ArkCloud Workforce

    Workforce Operations

    Purpose:
    Schedule staff, track credentials and licences, and see who is available.
    Main users:
    Department managers, Staffing coordinators, Practice administrators
    Source of truth for:
    Staff records; Shifts and staff availability; Credentials and licences
Find the right one

Which application do I use to...

  • Log a referral and register a new patientAccess
  • Check a patient's insurance before their first visitAccess
  • Check a patient in when they arriveAccess
  • Write and sign a therapy evaluation or SOAP noteRehab
  • Update a plan of care and its goalsRehab
  • Review and publish clinical guidance for cliniciansClinical
  • Schedule a follow-up call after a hospital dischargeCare
  • Find patients with an open care gapCare
  • Submit a claim or work a denialRCM
  • Send a patient statement or set up a payment planRCM
  • See denial rates by payer for last quarterInsights
  • Build next week's staff rosterWorkforce
  • See whose licence expires this monthWorkforce
How they work together

One patient, several applications

An example path for a therapy patient. Each hand-off says whether the platform moves the information automatically, a member of staff sends it, or the link is not built yet.

  1. Stage 1 · ArkCloud Access

    Getting in

    The referral is logged, the patient registered, insurance checked and the first visit booked.

    Built - staff send itA referral, registration or waitlist entry is sent to Rehab, which creates or links the patient.
  2. Stage 2 · ArkCloud Rehab

    Treatment

    The therapist evaluates, documents each visit, keeps the plan of care and discharges the patient.

    Built - staff send itA completed visit's service is checked automatically; an administrator posts the charge to the RCM account.
  3. Stage 3 · ArkCloud RCM

    Getting paid

    Charges become claims, remittances are posted, denials are worked and the patient's balance is collected.

    AutomaticCollections, denial, payer and aging figures feed Insights' financial analytics.
  4. Stage 4 · ArkCloud Insights

    Seeing the results

    Leaders review financial, operational and clinical performance from the same records.

Working alongside the journey

  • ArkCloud Care

    Coordinates follow-ups, transitions and care gaps for patients who need help between and after visits.

    AutomaticDischarges needing follow-up, and requests clinicians send from a Rehab episode, arrive as Care transitions, follow-ups or tasks on the same patient.
  • ArkCloud Clinical

    Holds reviewed clinical guidance that clinicians can consult (private preview).

    AutomaticPublished guidance, with its sources, is listed read-only beside the documentation on a Rehab episode for users who can also open Clinical.
  • ArkCloud Workforce

    Keeps the staff, shifts and licences that Rehab checks before booking and billing.

    AutomaticLicences and staff records gate note signing for billing and appointment booking in Rehab.

Not every patient passes through every application, and an organisation can run any of them on its own. They share one patient record, one login and one audit trail, so a team using several does not re-enter the same patient.

Underneath every application

What they share

lib/auth

Identity and access

Single sign-on with Google, multi-factor authentication required for administrators, role-based access control, and account lockout.

Row-level security

Organizations and tenancy

Every record is tenant-scoped. Organizations, users, and roles are shared across products rather than duplicated per product.

lib/product-access

Billing and entitlements

Subscriptions are held per product, so an organization can buy one product without the other. Product access is enforced server-side on every request.

Tamper-evident audit

Security and audit

Hash-chained, append-only audit logging, dedicated PHI access logs, field-level encryption of designated PHI fields, and scheduled data-retention jobs.

Structured logging

Observability

Structured logging with sensitive-field redaction across every product. OpenTelemetry tracing is built in and exports once a collector is configured.

lib/outside-records, lib/interop/vendor-compatibility.ts

Integrations

Standards-based interoperability using FHIR R4. A Rehab administrator can configure a per-hospital connection for read-only hospital record import, built to Epic's and Oracle Health's SMART Backend Services requirements, and staff can upload FHIR R4 bundles and C-CDA documents; imported records are proposals a clinician reviews before anything reaches the chart. No EHR vendor connection has been verified yet, nothing is written back to an EHR, and none is a vendor partnership or certification. The HL7 v2 parser has no inbound listener.

See every application in detail