ArkCloud Clinical capabilities
Clinical is the earliest of the ArkCloud applications, and its capability set is correspondingly small. Two things exist: the governance process that decides what clinical guidance may be published, and the decision support that reasons over it.
Decision support is built and cannot currently answer a question. It only reasons over guidance that has been published and reviewed by a person, and no guidance has been published. That is deliberate sequencing rather than an unfinished feature: a decision-support tool that answers from an unreviewed source is a clinical risk, so the product reports the blocker instead of producing an answer. Nothing degrades to a plausible-sounding guess.
The governance capability is the one that has to come first. It is what makes publishing guidance an auditable act with a named reviewer, which is the precondition for the other one being safe to switch on.
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.
1 built, 1 built but not yet usable — 2 in total.
Built (1)
Real implementations with data behind them. Availability to a given organisation still depends on its subscription and product entitlement.
Clinical guidance governance
Four-eyes review, licensing and legal sign-off, and validated publication for clinical guidance.
Built, not yet usable (1)
The implementation exists and is waiting on something outside the code.
AI decision support over published guidance
Restates and points to PUBLISHED, source-cited, human-reviewed guidance so a clinician can review its basis and decide. Never generates a patient-specific recommendation.
No clinical guidance has been published and reviewed yet, so this cannot answer a question.
Built is not the same as available to you. Whether your organisation can open ArkCloud Clinical 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.