ArkCloud Care capabilities

Care is about what happens between visits: the plan a patient is on, the team responsible for it, the outreach that follows up, and the handover when they move between settings.

The analytical half — care gaps, risk stratification and the population cohorts built on them — is inference about patients, and an inference presented as a finding is a clinical claim. So Care ships no rule and no model of its own. Your organisation authors each one, cites its source, and publishes it only after a clinical review by someone other than its author and a legal sign-off — the same gate as a care pathway. Until something is published, nothing is evaluated.

Every rule reads only what Care itself recorded: active plans and their review dates, programme enrollment, outreach outcomes, follow-ups, transitions, remote check-ins, coordination tasks and open gaps - statuses and dates only, never a name or a note. A risk model is a points table over those events, every tier shows the points behind it, and anyone working the list can override it with a reason. None of it is a diagnosis or a prognosis.

Chronic care management and remote care are recorded, not billed. Care records consent, an eligibility attestation and care-management time against a target you set, and keeps a check-in schedule with what the patient reported. No billing code is applied, no charge is created, and no device feed is read.

This list is generated from the same capability registry the application itself obeys — not maintained by hand. A capability appears here as built on the deploy it ships, and one that has not been built cannot be described as working.

12 built — 12 in total.

Built (12)

Real implementations with data behind them. Availability to a given organisation still depends on its subscription and product entitlement.

  • Care coordination

  • Care gaps

  • Care plans

  • Chronic care management

  • Multidisciplinary care teams

  • Patient follow-up

  • Patient outreach

  • Population health workflows

  • Remote care workflows

  • Risk stratification

  • Task queues

  • Transitions of care

Built is not the same as available to you. Whether your organisation can open ArkCloud Care depends on its subscription and on the product being enabled for your tenant. A capability listed as built can still be unavailable to a given signed-in user — entitlement is enforced where the data lives, not in this page.

Back to the ArkCloud Care overview