555 realistic outpatient scenarios. You classify, count and price each one; Genesis marks it and tells you which rule you broke.
Coders do not fail the Abu Dhabi Outpatient Classification (ADOC) on theory. They fail on the encounter that could be C or P, on the follow-up that should have been zero, on the diagnostic they left off the claim, and on the second same-series event that quietly gets denied.
The practicum puts those decisions in front of you several hundred times. Every scenario is built to mirror real outpatient patterns — realistic departments, diagnosis and procedure combinations, and messiness.
It runs in a browser, on a phone or a laptop, at whatever pace you want. Your progress is kept and you can export your whole record to CSV for your trainer.
A score on its own teaches nothing. Where you go wrong, the practicum explains what the rule actually says, why your answer does not satisfy it, and cites the section — so you can go and read it.
Feedback cites the governing section by name — General rules #1 to #5 of the Counting Rules, or §4.6 of the Claims & Adjudication Rules for the follow-up windows.
Miss a D-Series line and you are told that diagnostics never stand alone but are still reported, at zero, linked to the event that ordered them — not simply “the answer was D8”.
The amount is worked through line by line: which classes carry value, at what base price, and which ride at zero.
| Set | Scenarios | What it drills |
|---|---|---|
| Day 1 · Introduction | 130 | Scope, the four elements of a service event, series identification, out-of-scope settings |
| Day 2 · C-Series | 175 | Classification and counting across the eight clinical clusters, follow-up windows, inclusions |
| Day 3 · P-Series | 100 | The gatekeeper check, boundary calls between P2, P3, P10 and P11, same-day P and C |
| Day 4 · S & D Series + Claims | 150 | S routing by qualification, diagnostic linking and quantities, end-to-end claim building |
Each set is graded easy, medium and hard, and you choose how many to take and in what order.
The full ADOC service code list sits behind a button on every scenario — searchable by code or description, filterable by series. You are meant to use it. The exam is open-manual for the same reason.
Every student gets a personal GEN-XXXX-XXXX code. It carries your name into the watermark on every screen and into every result you export, which is what makes your work yours.
The answer key never reaches the browser. Scenarios are marked by Genesis on submission and released one at a time — a saved copy of the page is an empty shell.
Codes are personal and are issued for the length of your cohort. Sharing one is visible in the logs and the code can be revoked.
The scenarios simulate actual outpatient encounters so that the case mix, the diagnosis and procedure combinations and the departmental patterns are the ones coders actually meet.
Questions about cohort dates, in-house training for your department, or anything on this site — we answer within one working day.
Our student counsellor will talk you through the programme, the dates and the fee, and answer anything the website has not. One conversation, no obligation.