ArkCloud Health

One platform. Multiple workflows.

Healthcare technology platform spanning revenue cycle management and clinical intelligence.

Available

ArkCloud RCM

Revenue Cycle Management

Claims, denials, payments, collections, and revenue analytics for healthcare organizations.

Learn more
Available

ArkCloud Rehab

Governed Rehabilitation Outcomes

A governed platform for rehabilitation outcome measurement: versioned clinical content with source provenance, licensing governance, and reviewed publication. Clinical scoring and interpretation activate as approved definitions are published.

Learn more
Private Preview

ArkCloud Clinical

Clinical Decision Support

A clinician-driven workspace for governed clinical guidance.

Learn more
Up & Coming

The platform is expanding

One connected healthcare platform spanning patient access, clinical care, rehabilitation, revenue cycle, care management, analytics, and workforce operations. These applications are in private preview and not yet generally available.

Private Preview

ArkCloud Access

Patient Access & Intake

The digital front door for scheduling, referrals, intake, eligibility, authorization, registration, and patient engagement.

Learn more
Private Preview

ArkCloud Care

Care Management

Coordinate patients beyond the encounter with longitudinal care plans, outreach, transitions, and population-level workflows.

Learn more
Private Preview

ArkCloud Insights

Analytics & Intelligence

Turn clinical, operational, rehabilitation, and revenue-cycle data into actionable intelligence across the ArkCloud platform.

Learn more
Private Preview

ArkCloud Workforce

Workforce Operations

Coordinate healthcare teams, staffing, credentials, schedules, productivity, and workforce operations from one platform.

Learn more
One platform

What they share

These are products, not separate applications. Each one is built on the same foundation, so an organisation using more than one does not run two of anything.

  • One account

    A single ArkCloud identity per person, with single sign-on and multi-factor authentication. Which products it opens is decided afterwards, server-side.

  • One tenant model

    Organisations, roles and data isolation are defined once and enforced at the database level, not re-implemented per product.

  • One entitlement layer

    Access to a product is granted centrally, so adding one is a permission change rather than a new deployment.

  • One audit trail

    Security events are recorded to the same immutable log whichever product produced them, which is what makes a single review possible.

How the platform works

Status

What the labels above mean

A product is marked from a single registry, so a page cannot present one as available before it is. The distinction is worth stating plainly rather than leaving a reader to guess how much of this exists.

Generally available
Shipping today. It can be bought, deployed and used, and it is what the pricing page prices.
In development
Being built and not available. The capabilities described on its page are planned, not delivered, and nothing about it can be purchased.
Reserved
A registered name with no product behind it. It exists so entitlements, API namespaces and the tenant resolver account for it from the start - not because anything is being built.