Todas las guías

User Manual

El Manual del usuario en su idioma está en preparación. Mientras tanto, aquí lo tiene en English.

Chapter 12Daily QC

Menu: Daily QC. Address: /lab/qc.

12.1 What this screen is for

This is where the laboratory proves, every day, that its analyzers measure correctly. A technologist records a run of a control material (a control lot of known target value), the program judges each value against the Westgard rules, and the Levey-Jennings chart shows how the lot has behaved over time.

The screen is also a gate. A quality-control run that fails, or the absence of a passing run, holds the approval of results on the Results screen: the held result cannot be approved until a passing run is recorded and any open violation is resolved here. The same screen holds the setup of the automatic release of results (rules per test, a replay of the rules, and the analyzer controls).

12.2 Who sees it

Whoever holds Enter results. The menu hides the screen from everyone else. The dossier of the screen names no other permission; the buttons below are not separately restricted on the screen.

You can……if your role holds
Open the screen, record a run, resolve a violation, manage lots, read the rules, and set the automatic releaseEnter results

12.3 The screen in a glance

Figure 12-1: The Daily QC screen: 1 the head with its buttons, 2 the figures, 3 the list of lots, 4 the chosen lot's details and chart.
Figure 12-1: The Daily QC screen: 1 the head with its buttons, 2 the figures, 3 the list of lots, 4 the chosen lot's details and chart.
  1. The head: the title with today's date and the number of runs, and the buttons Lots, Automatic release and Record a run (Ctrl+Enter).
  2. The figures: Quality score, Today's runs, Warnings, Rejected, Open violations and Lots expiring soon.
  3. The list of lots: each active lot with its last run today.
  4. The lot details: the chosen lot, its Levey-Jennings chart, its latest runs and its actions.

12.4 The head and the figures

ElementWhat it does
LotsOpens the control lots window (12.7.4 Task 4 — Manage the control lots).
Automatic releaseA menu with Rules per test, Replay the rules and Analyzer controls (12.7.5 Task 5 — Set the automatic release rules per test, 12.7.6 Task 6 — Replay the rules before relying on them, 12.7.7 Task 7 — Map an analyzer's control to a lot).
Record a run (Ctrl+Enter)Opens the window to record a run (12.7.1 Task 1 — Record a run).
Quality scoreThe quality score for the last 30 days.
Today's runsThe runs recorded today and how many passed.
Warnings and RejectedThe warnings and rejections counted by the server. A non-zero rejected count is marked as due.
Open violationsViolations still open. Each one holds results until it is resolved.
Lots expiring soonLots that expire within 45 days.

The screen refreshes itself every minute.

12.5 The list of lots

Figure 12-2: The list of lots: 1 one lot, 2 its state.
Figure 12-2: The list of lots: 1 one lot, 2 its state.

The list is headed «Each lot's last run today». Its columns are Lot, Test, Level, Device, Last value, Z and State. Z is how many standard deviations the value lies from the target. The state is the verdict the server gave: Pass, Warning or Reject, with the rule that failed beside it; or Not run today if the lot has no run today. A lot with an open violation is marked as urgent. If there is no active lot the list says to add one from Lots.

Choose a lot to see its details.

12.6 The lot details and the chart

Figure 12-3: The chosen lot: 1 the Levey-Jennings chart, 2 the open violation, 3 Resolve the violation, 4 the latest runs.
Figure 12-3: The chosen lot: 1 the Levey-Jennings chart, 2 the open violation, 3 Resolve the violation, 4 the latest runs.

The heading gives the lot code and its state; under it are the test, the level, the target with its standard deviation (or «No target set»), the device and the expiry date.

ElementWhat it does
The Levey-Jennings chartPlots the lot's runs against its target. A warning or rejected run is a larger point with a ring, and its verdict shows in the tooltip. Empty, it says the lot has no runs yet.
The note about the chartIf it appears, the chart shows only the lot's runs among the newest results until the server returns all of them.
The red note about an open violationNames the rule, the time of the run, the test and the device, and says that the device's results are held in Results until it is resolved with a written action.
The expiry noteAppears when the lot expires within 45 days: prepare the next lot and add it from Lots.
Resolve the violation with a corrective actionShown only while the lot has an open violation. Opens 12.7.3 Task 3 — Resolve a violation.
Record a run for this lotOpens the run window for this lot.
Westgard rulesOpens the Westgard rules and device performance window (12.7.8 Task 8 — Read the Westgard rules and device performance).
Latest runsThe lot's six latest runs: time, value, Z and the rules that failed or the verdict.

12.7 Tasks, step by step

12.7.1 Task 1 — Record a run

Figure 12-4: Recording a run: 1 the device, 2 the test, 3 one value per level, 4 Record the run.
Figure 12-4: Recording a run: 1 the device, 2 the test, 3 one value per level, 4 Record the run.
  1. Press Record a run (Ctrl+Enter, which works even while the cursor is in a field, but not while another window is open), or Record a run for this lot on a chosen lot.
  2. Choose the Device, or leave it as Manual entry. If only one device exists it is chosen for you.
  3. Choose the Test (it is already chosen when you started from a lot). The table lists one line per level of that test's active lots, with the lot and its target.
  4. Type the measured value of each level. A level left empty is not recorded.
  5. Press Record the run. The levels are recorded in order as one run, so the rules that compare levels within a run (such as R-4s) apply. Each line then shows its verdict, the failed rules and Z.
  6. Press Done.

If the server refuses, the reason shows in red in the window; correct and try again.

12.7.2 Task 2 — Read the Levey-Jennings chart

  1. Choose the lot in the list.
  2. Read the chart: the target line and the lot's runs. A point far from the target, or a ringed point, is a run that warned or was rejected.
  3. Read Latest runs for the exact value, Z and the rule behind each.
  4. If you need the rules' meaning, press Westgard rules (12.7.8 Task 8 — Read the Westgard rules and device performance).

12.7.3 Task 3 — Resolve a violation

Figure 12-5: Resolving a violation: 1 the value and the device, 2 the corrective action, 3 Resolve the violation.
Figure 12-5: Resolving a violation: 1 the value and the device, 2 the corrective action, 3 Resolve the violation.

A failed run opens a violation. While it is open, the results of that device are held in Results.

  1. Rerun the control first and record the run (12.7.1 Task 1 — Record a run). The window says: rerun, then resolve.
  2. Choose the lot with the violation and press Resolve the violation with a corrective action.
  3. The window shows the value and the device. Write the corrective action that was taken.
  4. Press Resolve the violation.

A reject cannot be closed without its written corrective action: the button stays dim until you write it. A warning closes without one; write what was done if you wish. When it is resolved, the hold on the device's results is lifted.

12.7.4 Task 4 — Manage the control lots

Figure 12-6: Control lots: 1 the lots with their switch, 2 New lot.
Figure 12-6: Control lots: 1 the lots with their switch, 2 New lot.
  1. Press Lots. The window Control lots lists the lots; if empty it says so.
  2. To retire a spent bottle, turn off its Active switch. A lot is switched off, never deleted; the window keeps listing switched-off lots, while the main list shows active ones only.
  3. To add a lot press New lot and fill Lot code (written in capitals), Test code (a test code; it also accepts one not yet used by any lot), Level (1, 2 or 3), Expires (optional), Target and Standard deviation. The standard deviation must be greater than zero, and the code, the test, the target and the deviation must all be filled before the button is enabled.
  4. Press Save and activate.

12.7.5 Task 5 — Set the automatic release rules per test

Figure 12-7: Automatic release rules: 1 a test's switch, 2 its measuring range.
Figure 12-7: Automatic release rules: 1 a test's switch, 2 its measuring range.
  1. Press Automatic release, then Rules per test. The window Automatic release rules per test lists the tests with a rule; if none, it says so.
  2. To allow or forbid the automatic release of a test, use the switch Automatic release on its line. A test switched off is never released automatically, whatever the analyzer's card says.
  3. To write a rule press Add a rule, choose the Test (search by code or name), and give the Lower limit and Upper limit limits of the Measuring range. Leave both empty to remove the range. A value beyond the range, or one the analyzer marks with "<" or ">", is kept for a person.
  4. Press Save.

A test not listed works as before.

12.7.6 Task 6 — Replay the rules before relying on them

Figure 12-8: The replay: 1 the period, 2 Run the replay, 3 the decisions.
Figure 12-8: The replay: 1 the period, 2 Run the replay, 3 the decisions.
  1. Press Automatic release, then Replay the rules.
  2. Choose From day and To day.
  3. Press Run the replay.
  4. Read the counts: how many results, how many would have been released automatically and how many held. The table gives, per result, the Test, Value, Approved at, the decision (Would be released automatically or Would be held) and the reasons.
  5. To keep the table, press Export CSV.

The replay changes nothing: no result, no record and no alert. Quality-control, calibration and connection state are judged as they are now, not as they were when the result was approved. If the replay reaches its limit of results, narrow the period.

12.7.7 Task 7 — Map an analyzer's control to a lot

Figure 12-9: Analyzer controls: 1 the mapped controls, 2 Map a control.
Figure 12-9: Analyzer controls: 1 the mapped controls, 2 Map a control.
  1. Press Automatic release, then Analyzer controls.
  2. Press Map a control.
  3. Choose the Analyzer, type the Control id exactly as the analyzer sends it, choose the Lot, and add a Note if you wish.
  4. Press Save.

The values the analyzer sends under that control id then reach the Levey-Jennings chart without a switch on the analyzer's card. One control id may name a lot for each test, never two lots of one test. Remove deletes a mapping.

12.7.8 Task 8 — Read the Westgard rules and device performance

Press Westgard rules. The window Westgard rules and performance lists each rule with its Meaning, its Effect (Reject or Warning) and how many are Open; and under Device performance, per device, the Runs and the Mean |Z|. If there is no run yet, it says so.

12.8 How quality control holds approval

Two checks on the Results screen depend on this one:

Check on ResultsWhat holdsHow to release it
Quality control passed in the last 24 hoursNo passing quality-control run in the last 24 hoursRecord a passing run (12.7.1 Task 1 — Record a run)
No quality-control holdAn open violation on the deviceRerun the control, then resolve the violation (12.7.3 Task 3 — Resolve a violation)

The Results screen shows the hold as a red mark in its foot, and its own messages call this page «Daily quality». The hold is on the device's results, not on the lot alone. Some holds cannot be overridden from Results; they are lifted only here.

12.9 Messages and what to do

The screen saysMeaningWhat to do
Quality control could not be loaded.A fault reading the screen's dataRetry; check the connection
No active control lots. Add one from Lots.No active lotAdd a lot (12.7.4 Task 4 — Manage the control lots)
The action failed. Try again.The server refused a stepRead the reason in red and try again
Open violation: … results … are held in Results until it is resolved with a written action.A failed run holds that deviceResolve it (12.7.3 Task 3 — Resolve a violation)
This lot expires … Prepare the next one.Expiry within 45 daysAdd the next lot (12.7.4 Task 4 — Manage the control lots)
Unreadable range: …A stored measuring range cannot be readOpen the rule and write the range again (12.7.5 Task 5 — Set the automatic release rules per test)
The replay failed.The replay could not runNarrow the period and try again
The replay reached its limit of resultsToo many results in the periodNarrow the period
The rules could not be read.A fault reading the rulesClose and reopen the window
The controls could not be read.A fault reading the mappingsClose and reopen the window
It could not be saved.The server refused the saveCheck the fields and try again

12.10 See also

Results (where the hold shows and approval happens), Devices and printers (analyzer cards and their faults), Quality (corrective actions).

Informar de un error de traducción
WhatsApp Enviar el enlace de descarga a su computadora