Enter test results

What result entry is for

The result entry screen is where technicians enter measured or observed values for the tests attached to an order. The page organizes rows by sample and test, then stores each result with its unit, reference range, flag, metadata, and review status.

Use this page after the required samples exist and have moved far enough in the sample workflow. If no sample exists, Kashef blocks result saving and asks staff to create a sample first.

Interactive result workspaces follow the selected Kashef interface language. Page titles, buttons, status messages, notifications, validation, help text, and dates are localized; Arabic uses a right-to-left layout. Laboratory test names remain their canonical English names in small left-to-right areas so staff can identify the same test consistently. Numeric values and reference intervals keep their scientific left-to-right order where needed. The standalone released-result sheet and PDF are English left-to-right documents; leaving the document returns the surrounding interface to its selected language.

Result rows

Each row represents either a test result or a parameter result inside a test. A CBC, chemistry panel, or culture-related test can produce multiple rows if the catalog defines parameters. A simple test can produce one row.

Rows can include:

• Sample barcode and sample status.
• Test name and parameter name.
• Result value.
• Unit.
• Reference interval.
• Flag.
• Interpretation or insight.
• Review status.
• Review trail.

The row exists because the catalog defines the test and its parameters. If a needed parameter is missing, correct the catalog setup rather than typing extra information into notes.

Numeric, text, and calculated values

Numeric results are evaluated against reference ranges when a matching range exists for the patient age, gender, test, and parameter. Text results store a raw value and do not receive the same numeric flagging. Calculated rows can be recalculated from other values when the test setup supports it.

When a value changes, Kashef recalculates flags and calculated rows for the same sample. This helps reduce manual interpretation mistakes, but it does not replace professional review.

Reference ranges and flags

Reference ranges come from the catalog. Kashef resolves the best matching range for the patient and test parameter. It can then show normal, high, low, critical high, or critical low style flags depending on the configured limits.

If the wrong reference interval appears, do not force the result to look correct by changing the value. Check the patient age, gender, test parameter, and reference range setup. Incorrect setup should be corrected at the catalog or patient level so future orders work properly too.

Reference values always keep their scientific left-to-right order in result workspaces and printed reports. Read a numeric interval as the lower limit on the left and the upper limit on the right.

Saving results

Use Save All Results to persist entered rows. Empty rows are skipped. Invalid values are skipped and reported in the notification. Existing result rows are updated when the payload changes, and revision metadata can be stored when an approved or released result is amended.

Save before asking a manager to review. An entered value that is still only visible in the form is not ready for approval.

Approval and rejection during entry

Users with review permission can approve individual rows, approve all entered rows, approve selected rows, or reject selected rows with a note. Rejection should explain what needs correction, such as instrument rerun required, value inconsistent with sample, missing dilution note, or wrong unit.

Released results cannot be rejected from this screen. If a released result needs correction, follow the released-result amendment process and involve a manager.

Releasing from the entry page

Some users can release results directly when all required rows are entered and approved. Kashef checks that release is allowed in the current context, that results belong to releasable samples, and that QC gates allow release. If QC has warnings, stale runs, or missing runs, a manager may need to provide an override reason.

For routed orders, result release is available only from the source branch context. This prevents a receiving or processing branch from releasing a report outside the proper ownership path.

Good entry habits

Enter values from the instrument, worksheet, or validated source exactly as approved by lab policy. Confirm units before saving. Watch critical flags before moving to the next sample. Use rejection notes for work that must be corrected, not for ordinary comments.

Do not release all results just because most rows look complete. Every required row must be entered and approved unless the workflow intentionally allows a partial release group.