A diagnostic algorithm is most educational when you can explain why the next branch matters. ddxof offers a useful starting point for that exercise: case-inspired algorithms organised around complaints and diagnoses. The productive habit is to predict, justify and check the next step, rather than memorise the route through a finished diagram.
This review examines the public website as checked on 23 September 2026. It does not claim that the algorithms have been prospectively validated, that every recommendation is current or that a complete clinical pathway can be safely inferred from a teaching graphic.
What ddxof is
ddxof describes itself as a collection of cases based on real patients, with each case inspiring an approach to evaluation or management. Its public index, checked on 23 September 2026, provides search, clinical categories and tags.
The name signals the emphasis on differential diagnosis, but the site's stated scope is broader than producing lists of possible conditions. Some entries concern investigation, management or image interpretation. Those different purposes should remain visible when you select an article.
For revision, a diagram can make the organisation of a topic easier to inspect. That is an educational design advantage, not proof that following the diagram will produce the correct decision in every setting.
Read the question at the entrance
Before studying the branches, identify who the algorithm is about and what problem it is intended to address. A pathway for an undifferentiated complaint may not answer the same question as one for a confirmed diagnosis. A diagram also may begin after an assessment step that a novice has not yet recognised.
Write the entry condition in your own words. Then ask what information must already be known before the first branch makes sense. If that prerequisite is missing from your fictional case, the correct educational response is to identify the missing information, not force the case into the diagram.
This habit keeps the flowchart connected to clinical reasoning. It also gives a supervisor something specific to discuss when the learner finds the apparent logic too simple or too complex.
Predict one branch, then explain it
Choose a small section and cover the next part of the diagram during your own study. Predict what distinction should come next and explain why it would change the investigation or interpretation. Then reveal the published branch and compare the reasoning.
Do not score yourself only on whether the wording matches. You may choose a different but relevant distinction, or use the expected term without understanding its purpose. The explanation is the useful evidence of what you have understood.
After checking, record the discriminator in one sentence. A note such as "This question separates two different mechanisms" is a starting point, but it should name those mechanisms and the information that distinguishes them when your source supports doing so.
Inspect the source trail
The ddxof erythrocytosis article, published on 12 November 2024 and checked on 23 September 2026, illustrates the format: a case introduction, an algorithm and references including a guideline, a review and a textbook. That establishes a traceable educational source trail for the example, not universal currency across the site.
Notice the difference between the article's date and the dates of its references. Neither is a guarantee that all subsequent evidence has been incorporated. For a clinical question, inspect the relevant source and current local guidance rather than assuming that the date of your visit is the date of a content review.
A case-inspired algorithm also should not be treated as a frequency table. The fact that a condition appears in a memorable teaching case does not establish how likely it is in the patient population you see.
A fictional error that a flowchart can expose
Imagine a trainee studying a fictional abnormal-result vignette. They select a rare diagnosis because it is memorable, then read the algorithm and realise they never clarified the clinical context or whether the result was persistent.
The useful learning note is not simply the name of the missed diagnosis. It is the earlier question that should have been asked. The trainee can then construct a new fictional vignette in which that contextual detail changes, and explain how their initial reasoning would differ.
This is an original study exercise, not a reproduction of a ddxof case or a claim that the app automatically generates counterfactual scenarios. It uses the algorithm to expose an omission in reasoning rather than to award points for remembering a diagram.
Know when the pathway does not fit
An algorithm becomes less useful when its starting conditions, available investigations or intended setting do not match the problem. Recognising that mismatch is a legitimate learning outcome.
For UK readers, check terminology, units, referral arrangements and treatment context rather than assuming that an emergency-medicine teaching resource is a local protocol. That does not make the resource unsuitable; it defines which elements can be used for learning and which need contextual verification.
Do not reproduce clinical treatment details from a diagram into a personal shortcut without checking the source and the relevant local process. This article deliberately teaches a study method, not an investigation or prescribing pathway.
A teaching session built around disagreement
For a small group, ask each learner to explain the same branch before showing the published diagram. Compare the reasons, not just the chosen labels. One learner may be prioritising likelihood, another urgency and another test availability without realising they are answering different questions.
The educator can then ask which question the algorithm actually addresses. This creates a focused discussion about purpose and scope, rather than a debate over whose memory of the flowchart is best.
End by asking what would make the diagram inapplicable. An answer that identifies a missing prerequisite or a different clinical setting is more useful than an unqualified statement that the pathway should always be followed.
Where iatroX adds a different function
This review is published by iatroX and includes its source-linked reference as a complement to ddxof. Per iatroX product information, September 2026, Ask-iatroX is free without trial expiry or a verification gate and is grounded in NICE, CKS, SIGN and SmPC information from emc.
A relevant next step is to investigate the clinical question behind an uncertain branch and inspect the linked sources. The published methodology describes retrieval and checking, but it does not remove the need to verify applicability or guarantee correctness.
Use ddxof when a visual structure helps organise the topic. Use a current reference when you need to check a specific recommendation. Use tutoring or supervised discussion when you cannot explain the distinction. Those are different jobs, not a contest for one universal tool.
Frequently asked questions
Is ddxof a list of diagnoses or a clinical guideline?
It describes case-inspired algorithms for complaints and diagnoses, including evaluation and management. A teaching algorithm should not automatically be treated as a current local guideline.
How can I study an algorithm actively?
Predict a branch, explain the discriminator and then compare your reasoning with the published diagram and references. Record the question you missed rather than copying the entire flowchart.
Can UK trainees use ddxof?
Yes, as an educational resource with appropriate source and context checking. Local pathways, terminology and current clinical recommendations need separate verification.
Investigate the source behind a clinical reasoning question →