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
- Deidentified outcome facts
Deidentified outcome facts
Load observation-level facts under a recorded consent basis and accept or reject each one.
OverviewDeidentified facts awaiting acceptance×
Healthcare Analytics · Deidentified outcome facts
New
Deidentified facts awaiting acceptance
Approval conditions
| Parent | Sequence | Description | Observed on | Patient count | Session count | |
|---|---|---|---|---|---|---|
| OC-22234 | 70 | Pending dof-157 | 17 Oct | 15 | 34 | |
| OC-53985 | 50 | Pending dof-153 | 03 Oct | 32 | 15 | |
| OC-75131 | 10 | Pending dof-855 | 20 Oct | 29 | 8 | |
| OC-80631 | 60 | Pending dof-268 | 25 Oct | 35 | 5 | |
| OC-51290 | 10 | Pending dof-425 | 10 Oct | 27 | 37 |
6 of 6 records
Pending dof-157Deidentified outcome facts · DOF-68783
PendingParentOC-22234
Sequence70
Observed on17 Oct
Patient count15
Session count34
What you can do
Keep the facts behind every rate
A published rate is only as good as the observations under it. Deidentified outcome facts are those observations: one row per fact, tied to its parent cohort, with a sequence, a description, the date it was observed, the cohort date and the counts it contributes. Each fact keeps its source reference and the consent basis under which it was used. Identifiable patient data stays in the source system; the app holds the deidentified fact and the reference back to it.
How the work is organized
Facts arrive with Outcome = 'Pending'. The Outcomes Analyst checks each one against the source snapshot and the outcome definition, then accepts or rejects it. Rejected facts stay on the cohort with their outcome recorded, so the reviewer can see what was excluded. Supporting documents, such as an extract log or a data-quality note, are attached to the cohort as evidence and wait for verification.
- Accept or reject explicitly. A fact moves
Pending → AcceptedorPending → Rejected; nothing leaves the pending queue silently. - Consent travels with the fact. consent basis is recorded per fact as well as per cohort, so a mixed cohort can be explained.
- Evidence waits for a reviewer. Evidence documents start with
Verified = 'No'and only a Clinical Reviewer marks them verified.
What to agree during setup
Agree the consent bases your organization uses and the exact wording to record for each. Decide which source reference identifies a fact uniquely, so a reloaded extract does not duplicate rows. Agree the rejection rules for facts outside the cohort window, facts without a consent basis and facts whose counts do not reconcile with the snapshot. Confirm where deidentification happens before load, and who in your organization signs off that process.
Check the handoff on an actual case
Load facts for a cohort from a snapshot whose record count you know. Include one fact with no consent basis and one observed outside the cohort window. The Outcomes Analyst should reject both with the outcome recorded, and accept the rest. The accepted patient count on the facts should reconcile with the patient count held on the cohort.
Reload the same extract. The source references should match the existing facts and no duplicate rows should appear. Then ask the Clinical Reviewer to open the cohort’s evidence and mark the extract log verified. The Outcomes Analyst should not be able to verify evidence for their own cohort.
What your team sees
- Deidentified facts awaiting acceptance — pending facts with their parent cohort, observation date, counts, consent basis and source reference.
- Evidence awaiting verification — evidence documents not yet verified, with document date, external reference and attachment.
Follow the work through
- Cohort construction to validation: Build a cohort revision, load its facts and accept or reject each one.
- Independent review to publication: Approve the exact revision and publish its outcome rates.
Review the implementation plan and the data model before preparing your import files.
What it keeps track of
Data model- Deidentified outcome facts
- Consented observation-level session and conversion event facts.
- Evidence documents
- Supporting source evidence documents and verification state.
- Metric observations
- Observation-level metric readings tied to a snapshot and source.
- Source snapshots
- Sourced snapshot captures with coverage window and freshness status.
Who uses it
Permissions- Outcomes Analyst
- , Clinical Reviewer.
- The Outcomes Analyst loads and decides each fact.
- The Clinical Reviewer reads the facts and verifies the evidence before reviewing the cohort revision.
Set up Healthcare Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.