Enter and release results
Enter patient results, review flags, approve or reject rows, and release reports through the QC gate.
Before result entry starts
Result entry should begin only after the order has a sample. The result page builds its rows from the order samples, selected tests, test parameters, and any existing saved results. If there are no samples, Kashef warns that a sample must be created first.
Before entering values, confirm patient identity, order code, sample status, selected tests, and whether the sample belongs to the current branch or a routed order context. A result entered against the wrong order is harder to fix than a missing result.
Open the result page
Open the order and choose the result entry or review action. The page title includes the order code. Kashef loads samples, tests, parameters, existing results, reference ranges, units, status flags, verifier information, rejection notes, and release status.
For tests with parameters, each parameter appears as a separate row. For tests without parameters, the test itself appears as one row. If a sample has no linked tests, Kashef can fall back to the order tests so the team can still complete the work.
Enter values carefully
Type the result value in each row. Numeric rows expect numeric values. Text rows can hold text results. When the value changes, Kashef recalculates interpretation, status flag, insight, clinical advice, and calculated rows for the same sample where configured.
Do not force a value to fit the system. If a result type, unit, reference range, or parameter is wrong, stop and ask a catalog administrator or senior technologist to fix the test definition. Wrong catalogue setup can create wrong report flags.
Read reference ranges and flags
Kashef resolves reference ranges using the test, parameter, patient age, and patient gender. Ranges may be simple numeric bounds, lists of values, lists of ranges, or free-text interpretation. The page uses the resolved range to format the reference interval and determine flags where possible.
Flags help reviewers, but they do not replace clinical judgment. Always compare flagged values with sample quality, instrument output, patient context, and any manual notes. If the range is missing or inappropriate, record the issue and correct the catalogue before relying on the report.
Save all results
Use Save All Results after entering values. Kashef persists valid rows, skips invalid entered values, and notifies managers when results were added. Saved rows can move into entered status and become available for review.
Saving is not the same as releasing. A saved result may still require approval, rejection handling, QC checks, payment settlement, and final report release.
Approve or reject rows
Users with approval permission can approve individual rows, approve selected rows, or approve all entered rows. Approval is blocked when a row has no valid saved value, is already released, or is in a status that cannot be approved.
Reviewers can reject an entered unreleased row with a required note. Bulk rejection is also supported when selected rows share a clear reason. Rejection notes should tell the technician exactly what to correct: rerun, recollect, verify dilution, check unit, confirm instrument output, or review patient details.
Release results
The Release Results action is visible only to users who can approve results and when release is allowed from the current context. For routed orders, release may be restricted to the source branch. The release action requires confirmation and runs a QC check before publishing approved results.
Kashef blocks release when required rows are not entered or approved, when no sample exists, when the user is not authorized, or when the result release gate fails. The release gate can also block release when full order payment is required and not settled.
QC gate and override reason
If the QC release gate feature is enabled, Kashef checks QC configuration for the tests being released. Missing QC, stale QC, or warning QC may require manager override, depending on permissions and the exact condition. Rejected QC blocks release.
When override is allowed, enter a clear override reason before publishing. A good reason explains why release is still safe, who reviewed it, and what follow-up is planned. Do not use generic notes such as "approved" or "urgent" without clinical context.
After release
Released results become available to printing and portal/report workflows according to status configuration. The order can be completed when all relevant results and closure rules are satisfied. Use the report preview or released report output to confirm patient name, test names, values, units, reference intervals, flags, signatures, QR code, and footer.
If a released report needs correction, follow the lab's correction policy. Do not quietly overwrite values without an audit trail and reviewer approval.