1. Pharmacy Management System
  2. Features
  3. Review evidence
Feature · Review evidence

Review evidence

Evidence lines and attachments belong to a care request.

OverviewReview decisions
Pharmacy Management System · Review evidence

Review decisions

Review decisions

New
ParentReviewerSource revisionDecisionDecided atReason
CR-69589820Approve10 OctApprove rd-150
CR-78969120Return14 OctReject rd-710
CR-10291700Approve09 OctReturn rd-561
CR-42381120Return08 OctApprove rd-981
CR-49645240Approve05 OctReject rd-645
6 of 6 records
Approve rd-150Review decisions · RD-10395
Approve
ParentCR-69589
Source revision820
Decided at10 Oct
Example screen with sample data

What you can do

Work from the linked record

Evidence lines and attachments belong to a care request. An evidence line records its type, occurrence time, provider, external record identifier and verification state. An attachment has its own visibility and uploader. Review decisions preserve the source revision, reviewer, decision, time, reason and operation key. Operation receipts retain the expected revision, result state and failure reason for guarded actions.

An evidence line points to its care request and can retain the provider, clinical system and external record identifier. An attachment adds an uploader and visibility choice. A review decision records the reviewer, reason and request revision; an operation receipt records the result of a guarded action.

How the work is organized

  • Collect source evidence. Link evidence lines and attachments to the care request.
  • Record the review. Retain the decision, reviewer, reason and source revision.
  • Inspect exceptions. Follow failed receipts back to the request and any recorded effect.

Review decisions lets the reviewer and auditor inspect who decided a case and why. Operation exceptions lists failed and review-needed receipts. The coordinator opens the parent request before retrying any action and checks whether a prior effect was already recorded.

What to agree during setup

Agree which clinical source supplies each external record identifier and who may verify it. Set attachment visibility deliberately before sharing. Decide how a return for rework is communicated to the coordinator and how a failed operation receipt is investigated before another action.

Rehearse a returned request with an evidence line and attachment. The reviewer records a reason against the current revision; the coordinator corrects the evidence for another review. Include a failed receipt and inspect its action, expected revision and failure reason.

Check the handoff on an actual case

Take a request with one evidence line and one attachment. The reviewer checks the source, records a decision and cites a reason. The coordinator sees a returned request, updates the supporting evidence and sends it through review again. Compare both decisions with their source revisions; inspect any operation receipt that needs review before trying the action again.

A reviewer opens the request evidence and attachment visibility before deciding. The recorded decision keeps the reviewer, source revision and reason together. For a failed action, the coordinator reads the receipt and parent request before deciding whether to retry.

What your team sees

  • Review decisions — The starting screen for the module’s current work and linked records.
  • Operation exceptions — A related screen for checking the neighboring handoff or exception.

Follow the work through

Follow prescription to dispensing and care authorization. Review the data model when mapping source identifiers.

What it keeps track of

Data model
Clinical evidence
Clinical evidence lines attached to a care request
Record attachments
Files attached to a care request
Review decisions
Independent reviewer decisions
Operation receipts
Idempotent operation receipts for guarded actions
Care requests
Patient care and dispensing request records

Who uses it

Permissions
Authorized Clinical Reviewer
, Care Coordinator, Auditor work from their assigned records and review the related evidence before completing the handoff.
App Administrator
Maintains the configuration used by the operating team.

Set up Pharmacy Management System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started