Sequence plan analysis
Your protocol, checked against the card before you scan.
Protocol Check reads the sequence you are about to run and compares every parameter against the department protocol card — TR, TE, flip angle, averages, turbo factor, slice thickness, distance factor, slices and FoV. Matches are confirmed in green, deviations are called out in red with what they cost, and the count is typed by category so a geometry problem never hides inside a long list.
How it works
Three steps, on a real console workflow.
Build the plan
Queue the sequences and position the slice groups on the three-plane localizer the way you normally would.
Open Protocol Check
Every parameter is listed against the card. Green means it matches; red names the deviation and what it changes — coverage, resolution, contrast or scan time.
Fix, or justify
The Hints tab explains the correction. Learners either bring the plan back to the card or defend the deviation — which is exactly the conversation on a real console.
What Protocol Check compares
| Parameter | Example verdict | What a deviation costs |
|---|---|---|
| TR / TE | 500 ms / 11 ms — as per protocol card | Weighting drifts away from the clinical question |
| Flip angle | 90° — as per protocol card | Signal and SAR move together |
| Averages / turbo factor | 1 / 1 — as per protocol card | SNR traded against scan time |
| Slice thickness / distance | 5 mm / 1.8 mm — as per protocol card | Partial volume and gaps in coverage |
| FoV | 230 × 201 mm — card 230 × 201.25 mm | Changes coverage or resolution — flagged as geometry |
In the classroom
How programs use it
- Have learners submit the Protocol Check report as the graded artefact, before any images.
- Plant one deviation per exam and let the class find it — first by eye, then with the check.
- Use a deliberate deviation as an OSCE prompt: keep it or correct it, and say why.
Learn the concepts
Short guides that pair with this feature:
Put your learners at the console today.
Free student tier. No installs. Runs in any browser.