These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Healthcare Analytics
- Features
- Review and evidence
Review and evidence
Record independent reviewer decisions against an exact cohort revision and verify its evidence.
OverviewReview decisions awaiting reviewer×
Healthcare Analytics · Review and evidence
New
Review decisions awaiting reviewer
Action waits for the clinical reviewer
| Source | Source revision | Decision | Reviewer | Evidence reference | |
|---|---|---|---|---|---|
| OC-26964 | 520 | Pending | ER-445 | ||
| OC-95547 | 140 | Pending | ER-535 | ||
| OC-93015 | 300 | Pending | ER-236 | ||
| OC-50216 | 560 | Pending | ER-838 | ||
| OC-39867 | 590 | Pending | ER-716 |
6 of 6 records
ER-445Review decisions · RD-46476
PendingSourceOC-26964
Source revision520
What you can do
Review the revision you will publish
A review decision only means something if it is tied to the exact data that was reviewed. Each review decision records the cohort, the source revision, the reviewer, the decision, the date it was made, the reason and an evidence reference. If the cohort changes after the decision, the change is recorded as a new revision, and the earlier approval covers only the revision it names.
How the work is organized
The construction workflow opens a review decision with Decision = 'Pending' when the cohort needs approval. The Clinical Reviewer, who is not the cohort’s owner, reads the accepted facts, the calculated results and the attached evidence, then records Approved, Returned or Rejected with a reason. A returned revision goes back to the Outcomes Analyst with the reason attached. Only an approved revision can be published.
- Independent reviewer. The reviewer must be a different person from the cohort Owner, and the app records who decided.
- Evidence verified by the reviewer. Evidence documents move from
Verified = 'No'toYesand record who verified them. - History that cannot be edited. State history keeps every status change with the actor, the revision, the operation key and the reason.
What to agree during setup
Agree which outcome definitions require independent review before publication and which do not. Agree who can act as a Clinical Reviewer for each organization, and whether a second reviewer is needed for particular measures. Decide what evidence a reviewer expects to see, such as a source extract log, a data-quality check or a clinical sign-off memo, and how each is referenced. Agree the reasons a reviewer may give for returning or rejecting a revision.
Check the handoff on an actual case
Take an analyzed cohort with a pending review decision. Sign in as the cohort Owner and try to approve it; the decision should be refused. Sign in as a Clinical Reviewer, open the evidence and mark the extract log verified. Approve the decision with a reason and an evidence reference, and confirm that the decided at date and reviewer are recorded.
Now ask the Outcomes Analyst to reject one more fact and record a new revision. A new review decision should be needed, and the earlier approval should still be visible against the old revision in the “Cohort state history” view. Publication should be blocked until the new revision is approved.
What your team sees
- Review decisions awaiting reviewer — pending decisions with the cohort, source revision, assigned reviewer and evidence reference.
- My review decisions — decisions the signed-in reviewer has made, with date, reason and evidence reference.
- Cohort state history — every status change with its actor, revision, operation key and reason.
Follow the work through
- Independent review to publication: Approve the exact revision and publish its outcome rates.
- Run reconciliation and correction: Resolve failed runs and correct a published revision without losing the original.
Review the implementation plan and the data model before preparing your import files.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- Evidence documents
- Supporting source evidence documents and verification state.
- State history
- Immutable lifecycle transition history for each source.
- Outcome cohorts
- Measured web properties with lifecycle status and observed outcome fields.
Who uses it
Permissions- Clinical Reviewer
- , Outcomes Analyst, Analytics Manager.
- The Clinical Reviewer decides and verifies evidence.
- The Outcomes Analyst prepares the revision and attaches evidence.
- The Analytics Manager follows pending decisions and starts publication once a revision is approved.
Set up Healthcare Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.