QC results

Entering a QC run

Use Enter QC Results to record a QC run. The run information section asks for run date, active control, and optional instrument. After selecting a control, Fohosat loads the tests configured in that control's targets and creates required numeric fields for each test. Each field shows the English clinical test name, unit suffix, and helper text with Mean and SD.

QC result entry and QC result history follow the staff member's selected interface language, including headings, controls, statuses, notifications, validation, help text, and release-gate messages. Arabic uses a right-to-left layout. Laboratory test names remain canonical English in small left-to-right islands; numeric values, units, targets, ranges, and QC rule codes keep their scientific or recorded notation. Leaving the result workspace does not change the selected language.

If no fields appear after selecting a control, the control probably has no targets. Go back to QC Controls and add Mean/SD targets for the tests that control covers.

Saving and analysis

When saved, Fohosat creates one QC result for each configured test value. It stores the active branch, control, test, user, value, run date, and instrument, then analyzes each result against the configured target. The recorded branch is used when routing manager alerts back to the QC event. The selected control, instrument, and tests are checked again against the current lab company before anything is written. All results in the run are saved in one database transaction, so a failure does not leave a partially saved run.

The save notification tells staff how many results were saved and whether there were warnings or rejections. If all values are within range, the notification is successful. If warnings exist, it shows a warning. If rejections exist, it shows a danger notification.

Status meanings

Normal means no configured QC rule was violated. Warning usually means a single result exceeded plus or minus 2 SD but did not exceed 3 SD, producing 1-2s. Rejected means a stronger rule was violated, such as 1-3s or repeated same-side 2-2s. Unknown target is retained in the history filter for older, imported, or integration-created results. The current entry page only submits configured targets and blocks invalid target references.

Do not treat statuses as automatic release decisions without your lab's SOP. They are decision support. The quality officer should decide when to repeat QC, hold patient samples, recalibrate, change reagent, or document an exception.

History table

QC Results History keeps the measured run immutable. It shows run date, control, recorded branch, test, result value, target, the acceptable ±2 SD range, status badge, violated rules, quality-review state, disposition, instrument, and operator. It is sorted by newest run first. A legacy result may show that its branch is unavailable when the original operator's branch could not be verified safely.

Use this page to review recent values, investigate a QC failure, or confirm that a control was run before patient testing. Because editing is disabled, corrections should follow the lab's policy and normally require a new documented QC run. The page does not currently provide a plotted trend chart.

Disposition and corrective action

A warning or rejected row is marked Pending review. A user with QC release-override authority can select Record quality review, choose the accountable disposition, and describe the corrective action completed. Examples include repeating QC, recalibrating, instrument maintenance, replacing reagent, accepting after investigation, or suspending testing.

The review stores its author and time and writes a quality audit event. It does not change the measured value or QC status, and it does not by itself override the patient-result release gate. Complete the corrective action, enter a new QC run when required by SOP, and confirm that the release gate is clear before patient testing continues.

Filters

The date range filter narrows by run date. Control, test, status, and instrument filters help isolate a specific method or analyzer. Use status to find warnings and rejections. Use instrument to see whether a problem is limited to one analyzer.

When investigating a rejected run, start with the control and test, then compare recent results for the same instrument. Check whether previous values were trending toward a rule violation.

Checklist

• Correct control lot is selected.
• Correct instrument is selected when the analyzer is known.
• All required test values are entered for the QC run.
• Warning and rejected statuses are reviewed immediately.
• Every warning or rejection has a documented disposition and corrective action.
• Any historical unknown-target result is investigated and its source configuration is corrected.
• History is filtered by date, control, test, status, and instrument during investigations.