Skip to main content

Governance and readiness work

Who this is for​

This guide is for authorised staff reviewing organisational governance, AI readiness or accreditation preparation. Existing Solve and document-review screens are useful, but their presence does not establish complete output quality or an accepted external action flow. Patient-specific clinical decision support is inactive.

Start here​

  1. Open Abe console. The master question is What problem are we solving? Use Build it, Research it or Look it up for a non-clinical organisational task.
  2. Review the returned work in Your work. An Uncertain or Needs review state requires review; do not treat it as completed work.
  3. For an existing governance document, open its detail and check the document, version, organisation and linked tasks. Regenerate requests a new version and supersedes the old one; read the confirmation before proceeding.
  4. Current sign-off accepts optional notes and applies to the current, unsuperseded document in the organisation. Do not approve a document whose purpose, evidence or content you cannot verify.

The current governance detail does not display confidence, risk or citations. The sign-off service now requires the originating output, its corpus version, citations, assessed confidence and a matching document-content hash. Missing assurance refuses sign-off. Template review alone supplies none of these: current template-generated drafts remain unassessed and need further evidence work. The sign-off request still does not enforce atomic confirmation of the same reviewed revision; complete assurance and the external generation/task interface remain unfinished. Reading a governance document does not supply those permissions.

The required acceptance rule is: HIGH confidence, non-clinical work only through a proven supported action flow; MEDIUM needs explicit confirmation of the same output and revision; LOW or missing citations needs human review rather than completion. Those are requirements for the fuller action journey, not controls this guide claims are currently present. A recorded sign-off is not proof that the full safety rule was followed.

Reviewing an answer and finishing its work​

The next prepared Solve change adds Review exact answer to an answer linked in Your work. It is not available until its database migration and application release are both accepted. Once released, open that control, read the retained answer and sources, select I have reviewed this exact answer, then Acknowledge this answer. Acknowledgement records your review; it does not approve treatment advice or complete unfinished tasks. If the answer or its assessed source changes, review the new version. A closed thread reopens when required work or its supporting evidence changes.

All required work must still be complete and assessed before the thread can close. An unsigned document, missing source or LOW confidence keeps it open. Dismiss records why work was abandoned; it does not mark that work completed. Account changes invalidate an in-progress answer review. After an uncertain response, inspect the current thread before another attempt.

The prepared assurance path covers a new, source-verified answer issued by Abe's own producer and its supported tasks. It does not certify old answers, user-supplied confidence, or governance and accreditation outputs without their own assessment owner. The verified-corpus view was absent in the 5 October database check. Until that separately governed source access is available, Abe must retain the answer as unassessed and keep the work open. A historical sign-off or closed status is not retrospective verification under the new controls.

What success looks like​

You can inspect a document's current version and recorded sign-off state, or see a clear review/error state. A sign-off date records the existing approval action; it does not guarantee clinical, legal or regulatory compliance. Readiness work is preparation, not an accreditation award. No diagnosis or prescribing authority follows from it.

If it does not work​

If the version was superseded, open and review the current version rather than retrying approval of the old one. For a changed revision or missing evidence, stop and obtain current material before confirming. Sign-off failed or Regeneration failed is not success. Check the existing document state before another attempt and use Troubleshooting.

Stop or change your choices​

Cancel a confirmation you cannot support. If the existing screen offers clearing your document sign-off, review that explicit confirmation and check the resulting state. Manage app permission and paid funding separately through Manage and cancel. Do not use an organisational service credential as another person's approval.