What the review workspace shows

The workspace

Three panels: the verified source observations, the editable structured draft, and the change, evidence, and audit trail. The reviewer confirms the fictional member’s identity, compares draft against source, edits, requests a correction, saves, approves, and releases. A preview shows exactly what the member and the PDF will receive.

What approval means

Approval attests an exact content hash of one version. Every save carries the version it was made against (If-Match); a stale write is refused rather than merged. Any edit after approval invalidates it. Release is a separate action that requires a verified PDF of the same hash. A released version is never edited in place; a correction starts a new version with a visible reason and lineage.

Three content types, always visibly distinct

• measuredMeasured / source. Exact numbers, collection dates, source intervals or decision limits, source flags, and provenance. Shown as the laboratory reported them.
• software-preparedSoftware-prepared. Factual changes and general explanations with their sources and review status. Never a diagnosis, never a plan.
• clinicianClinician. Assessment and next steps with the identifiable fictional author, date, and approval metadata.

These badges appear in the HTML report and the PDF alike. A generic footer is not a substitute for labelling each section.

The clinician workspace lives under a role-gated route and is reached through the demo sign-in as a fictional clinician persona.