An OOS result is the moment a QC lab is most closely watched. Swat iQua Suite makes the investigation path explicit: which levels are needed is decided when the record is created, each level has its own reviewer and approver, and the record cannot be edited once it is finalised.
Mapping to your OOS procedure
The three levels give you a structure to follow your own SOP — for example, a laboratory investigation at Level 1 and a full-scale investigation at Level 2 where the lab cannot find an assignable cause. Because the server works out the current level from the flags, the order is always followed and every level’s approval is recorded separately.
Lab quality events and incidents
Not every lab problem is an OOS. Lab quality events record OOS, deviation, complaint or out-of-trend (OOT) events and other incidents, with categories, a Level 1 review and approval, and Level 2 when required. After approval the event produces a controlled PDF report, with a watermarked preview before then. Like OOS, an event can raise one CAPA that is approved when the event is fully approved.
Linked to samples, instruments and release
- An OOS record can link to the testing sample in Sample & Testing Management or to an instrument maintenance record.
- In-house QC testing classifies each result as within limits or OOS, so the analyst sees the failure immediately and opens the investigation.
- Open OOS investigations prevent the related batch release checklist items from being attested.
- OOS and lab event records are available through the REST API.
OOS records are opened by the lab team. Automatic creation of an OOS record from a flagged in-house QC result is not yet part of the product.