QA Basics for Imaging Teams
Quality assurance is easier to manage when teams separate routine checks, acceptance work, and issue-driven investigations.
Common QA layers
- Acceptance testing after installation or major upgrade
- Baseline measurements for future comparison
- Routine constancy checks and trending
- Change-control review after service, software, or protocol updates
- Investigation and documentation when image quality concerns are raised
What engineering contributes
- Coordinating documentation across service, physics, operations, and IT
- Tracking whether a change affects performance, workflow, or both
- Making sure baseline data is easy to find after maintenance events
- Turning one-off fixes into repeatable checklists
Questions to ask during any QA task
- What changed?
- What is the expected baseline?
- Who needs the results, and in what format?
- Is the issue technical, workflow-related, or a mix of both?
- What follow-up should happen if the result is out of tolerance?
A lightweight monthly review checklist
- Review unresolved image-quality and downtime issues.
- Note recent software updates, calibrations, or hardware replacements.
- Verify that acceptance and baseline records are stored consistently.
- Check whether recurring issues point to training, workflow, or infrastructure gaps.
- Capture one or two improvement actions rather than rebuilding the whole process at once.