Review and release results

What review protects

Review and release is the final clinical gate before a patient, doctor, portal user, or WhatsApp recipient can see results. The page is not just a printable worksheet. It brings together patient identity, sample status, result values, previous result context, reference intervals, abnormal flags, approval state, release groups, QC checks, print actions, and WhatsApp delivery.

Only staff with result permissions should work here. If a receptionist needs to know whether a report is ready, they can check order status, but they should not approve or release clinical rows.

The interactive clinical results workflow follows the user's selected Kashef language. Entry, review, approval, release, report preview, and their status messages, notifications, validation, help text, and dates are localized; Arabic pages use right-to-left layout. Laboratory test names remain canonical English in small left-to-right islands, and scientific values or reference intervals keep their left-to-right order where needed. The standalone released-result sheet and PDF are rendered as English left-to-right documents.

Header summary

The top summary shows the order code, generation time, sample count, order status, critical count, abnormal count, patient name, saved result count, manager approval count, and released result count. The order's Reason for Tests appears directly below it so reviewers can keep the clinical question in view.

Use these numbers before reading individual rows. If saved results are not complete, the order is not ready. If approval is incomplete, a reviewer still has work. If released count is lower than total, the patient may not see every test yet.

Working by sample

Rows are grouped by sample. Each sample section shows sample barcode, sample type, sample status, received time, approved count, and released count. This matters because one order can have multiple sample types and they may not all be ready at the same time.

If a sample still shows pending or not received, do not release its results. Go back to the Sample Log and resolve the sample workflow first.

Row details

Each result row can show:

• Test and parameter.
• Previous result value and date when available.
• Current result value.
• Unit.
• Reference interval.
• Flag.
• Interpretation or clinical advice.
• Review status.
• Review trail with reviewer and time.
• Manager action.

Columns follow the configured reference type. Numeric ranges and lists of numeric ranges show unit, reference, flag, and interpretation. A list of expected values shows its expected values, flag, and interpretation but omits Unit. A free-text reference is treated as narrative output and omits Unit, Reference Range, Flag, and Interpretation entirely. When a sample contains mixed types, an em dash marks only an inapplicable cell; when every row omits a field, the whole column is removed. The printable report follows the same rules.

The released report shows the marker that matches the stored flag: no arrow for Normal, ↑ for High, ↑↑ for Critical High, ↓ for Low, and ↓↓ for Critical Low. The Reference Range cell lists every configured demographic range for that test or parameter, with sex and age criteria on one line and the scientific value beneath it. The range applied to the released result is marked Applicable; review the full list for configuration completeness without mistaking another demographic range for the patient's applied range.

Previous result context helps reviewers spot large changes. It should not be used to hide a true new result, but it can help decide whether rerun, dilution, phone confirmation, or doctor communication is needed.

Approving and rejecting

Reviewers can approve all rows, approve selected rows, or reject selected rows. A rejected row needs a note that tells the technician what to correct. Good notes mention the exact issue: wrong unit, suspicious delta, instrument rerun required, sample quality concern, missing comment, or range mismatch.

If the patient has estimated or unknown age, or sex at birth is unknown/diverse, the review sheet displays Patient demographic verification required. Kashef will not guess an age- or sex-specific range. A numeric row can be approved only when the patient has exact required demographics or the catalog contains a deliberate all-age, all-sex range for that test. Correct the patient profile when verified; otherwise ask the catalog owner to configure a clinically valid universal range.

Do not use rejection for administrative delay. If a row is clinically fine but payment or delivery is blocked, solve that blocker in the relevant workflow.

Release groups

Kashef can group rows for release. A group is releasable when every row in that group is entered and approved, and at least one row is not already released. This supports controlled release for tests that can be reported together.

Release only the group that is ready. If another group still needs review, leave it unreleased until the rows are complete.

QC gate and override reason

Before release, Kashef evaluates every release group and shows the current gate state on the review sheet. The message identifies the affected test and, when available, the QC control, lot, instrument, and run time. A rejected QC run is a hard block and disables Release. Missing, stale, or warning QC follows the configured policy and the user's authority.

When the policy permits a manager override, an accessible QC override reason (required) field appears beside that release group. The system will not release the group with an empty reason. A successful override records the manager, reason, QC warning context, affected tests, branch, order, and released-result count in the quality audit log.

Write an override reason like a clinical note. Include what was checked and why release is safe. Example: "Urgent potassium confirmed by repeat run; control trend reviewed by manager." Avoid vague notes such as "urgent" or "manager said ok." A recorded QC disposition does not automatically clear this gate; enter a new acceptable QC run when required by the lab SOP.

Print and WhatsApp

After results are released, the header can show Print Released Tests. This opens the released-test print route in a new tab. Review the printed report for patient identity, test names, units, ranges, signatures, QR code, footer, and branch information.

Every released report identifies whether it is the original or an amended report, prints a REV- version marker, and shows the latest approval time. A configured signature block prints the actual releasing staff member, their role, the block's configured credential/approval label, and that signer's approval time. If the report says Approval identity not recorded, do not treat it as complete evidence; investigate the legacy result record before delivery.

Kashef reserves a small A4 print boundary so a compact report footer stays on its clinical page instead of creating a footer-only sheet. In Chrome's print preview, confirm that a compact report shows one page before saving or printing. A genuinely long report may have multiple content-bearing pages; no page should contain only the footer.

If an order has no released results, the direct report route shows a protected empty state instead of a printable report. There is no Print action. Use Return to order, confirm whether the order is cancelled or still awaiting review, and complete the correct workflow; never treat the empty screen as a clinical report.

WhatsApp delivery is handled from the order header after clinical review. Return to the order, choose Send WhatsApp, and select an active results template. Kashef enables a results-link template only when a released result and secure portal link are available. Confirm the saved recipient and prepared Arabic message in WhatsApp before pressing Send; the final send is always the employee's action.

Routed orders

For routed orders, result release is available only from the source branch context. This protects ownership and prevents a receiving branch from publishing a report before the source branch has completed its review responsibilities.

What to do after release

After release, confirm the order status and released count. If all required results are released and samples have reached their final state, the order can close. If the patient cannot see results in the portal or did not receive WhatsApp delivery, check portal visibility, phone number, release status, and report settings before re-entering clinical data.