Skip to content

Log point-of-care QC checks on every day they are due

Each QC check comes due in Tasks when it is required, a missed one shows up the same day, and out-of-range results are acted on at once.

  • Tabflows
  • Saves about 1 hr per month (est.)

Last checked Oct 27, 2026 against Tabflows v3.10.63

The situation

Point-of-care quality control logging is the routine documentation that shows in-house testing equipment, such as glucose meters, rapid strep tests and urine analyzers, is working correctly, usually daily or per-run control checks logged against expected ranges. A QC check takes well under a minute: run a control sample, confirm it falls in the expected range, write it down. The hard part is doing it every day it is due, for every test, for months, against a clinic day full of things that feel more pressing.

A skipped entry causes no visible problem that day, so nothing tells you it mattered. Months later the gap turns up in an inspection, and a log with scattered gaps looks the same to an inspector whether they came from oversight or from equipment that was actually malfunctioning.

Steps

  1. Write down how often each test needs QC List every point-of-care test with its required frequency, such as daily, per lot or per shift, and have an Admin add the list to Practice Brain with Add Text & Documents. Anyone can then ask Sidekick how often a test needs QC instead of relying on memory.
  2. Make each daily check a repeating Task Create one Task per test, assigned to the group that runs testing, with Due on today, a clinic Tag such as QC and a Repeat schedule that matches the test. Repeat runs at most once a day, so a per-shift check needs one Task per shift.
  3. Start per-lot checks from a template An Admin makes a task template for the new-lot check with Set due date to after set to 0 days. Whoever opens a new lot creates a Task from it, due that same day.
  4. Log it as you run it, then close the Task Record the result in your QC log at the moment you run the control, not from memory at the end of the day. Then mark the Task Done, so an open Task always means a check that has not happened.
  5. Act on an out-of-range result at once Keep that equipment out of patient testing until it has been troubleshot. Create a Task for the troubleshooting, assigned to whoever owns the equipment, set Due on to today and select Mark as urgent, so it shows in their My Tasks now with a red Urgent marker.
  6. Have one person review for gaps Save a filter for the QC tag with Status To do and Due on today, and have one person, such as your CMA lead, check it at a set time each day so a missed check shows up the same day. In their regular review of the full log, look for patterns such as missed Fridays that point to a scheduling or staffing gap.

The outcome

QC documentation stays current instead of being reconstructed right before an inspection. Each check is logged when it is run, a missed day is seen while you can still act on it, and equipment with an out-of-range result is fixed before it is used for patient testing.

Ask Sidekick

Sidekick is the AI assistant inside Tabflows.