Infrastructure layer
Clinical work queue
Structured, evidence-linked tasks derived deterministically from the uploaded records.
What is the Clinical Work Queue?
The Clinical Work Queue shows what needs human attention next. MedLineage agents turn fragmented records into source-grounded tasks: missing documents to request, claims to review, MDT checks, surveillance signals, and approval-gated exports.
Tasks are not clinical recommendations. They are record-preparation actions for human review.
Show task category explanations
Task categories
- Missing record request: A document that may be needed before review is not present.
- Claim needs review: A clinical fact was extracted but should be checked by a human reviewer.
- MDT briefing ready: A tumor board briefing is available for clinician review.
- Surveillance signal: A factual gap, outdated record, or contradiction needs attention.
- Write-back approval: A dry-run EHR handoff is ready but requires human approval before any external action.
- Terminology mapping needed: An observation was extracted but could not be mapped to a standard code.
- Consent missing: A consent or purpose record is missing before this action can proceed.
Scan record for tasks
Scans the current Patient Graph and creates source-grounded tasks for human review. It does not diagnose, recommend treatment, or modify clinical facts.
What this does
- Reads the patient graph, ledger and finalized packet
- Creates source-grounded work-queue tasks (missing records, claims to verify, MDT checks, surveillance, write-back approvals)
- Cites graph IDs for every claim; every tool call is logged
What this does not do
- Does not diagnose, recommend treatment or replace a clinician
- Does not modify clinical facts, observations or the ledger
- Does not resolve approval-gated tasks — only a role-matched human can
- Does not write to external EHRs (write-back previews are dry-run)
Filter:
Loading tasks…