Documentation
ArkCloud Clinical
A clinical workspace with governed guidance and a decision-support engine built to explain what published guidance says - never to become the source of a clinical value.
Decision support declines today. No clinical guidance is published, and the engine may only explain guidance that is. Asked a question with nothing published behind it, it refuses rather than answering from the model's own knowledge. That refusal is the designed behaviour, not an outage.
Private preview. ArkCloud Clinical is open to invited organisations that hold the Clinical entitlement, and to supervisors and administrators only. The decision-support screen offers a question box only once guidance is published; until then it shows its status and there is nothing for a clinician to ask it.
The ArkCloud Clinical dashboard reports that decision support has no published guidance to reason over - the state the notice above describes, shown where a clinician would meet it.
Not yet usable. This capability is implemented and cannot be used until something outside the software exists - published clinical content, or a live payer or payment connection. The screen states the reason rather than offering a control that would fail.
/clinical/dashboard
The rule the product is built on
AI may explain a published, governed value. It may never be the source of one.
That single sentence decides most of the design. It is why guidance has to be published before it can be cited, why an answer without a source is withheld rather than hedged, and why the clinician asks the questions instead of receiving unprompted conclusions. A tool that explains a cited source is decision support. A tool that originates a clinical conclusion is a different regulated thing entirely, and this is deliberately not that.
What is not available
- No published guidance library. Nothing has completed review, so there is nothing to cite or explain.
- No diagnosis, triage or treatment recommendation. The engine does not produce clinical conclusions, and no configuration enables it to.
Guidance governance
A guidance document carries its source, its citation and its reviewer. Draft guidance cannot be cited; only a published version is visible to the workspace.
Decision support, clinician-driven
The clinician asks the question and judges the answer. The engine retrieves published guidance and explains what it says - it does not decide, diagnose, or rank treatments.
Citations, not assertions
Every statement the engine returns resolves to a published source. An answer with no citable source is not returned with a caveat; it is not returned.
Tenant isolation
Row-level security under a runtime role that cannot bypass it, with product entitlement, lifecycle and role all enforced server-side.
Related: Security covers tenant isolation and access control across every product, and the API reference covers authentication and error handling.