founder-led, clinician-led, evidence-first
editorial policy built for
accuracy, traceability, and trust
iatroX is a clinical knowledge and education platform built for clinicians across the UK, Australia, Canada, and the United States. This page explains how content is sourced, validated, reviewed, updated, and governed across the platform.
clinician-led oversight guideline-first hierarchy rolling and six-month review
policy foundation
an editorial system designed for clinical reality
The iatroX editorial process is built around one central assumption: clinicians do not need more unstructured text. They need high-utility output that is accurate, grounded, current, and shaped for practical use. That is why content governance on iatroX combines evidence hierarchy, proprietary validation logic, human review, and a continuous correction pathway.
clinical usefulness over verbosity
iatroX content is built to help clinicians move from question to usable answer quickly. The objective is not to produce generic prose, but to surface clear, practical, high-value output that fits real decision-making and learning workflows.
accuracy is engineered, not assumed
The editorial process combines source hierarchy, technical validation, inconsistency checks, and human review. Accuracy is approached as a system property that is actively protected at each stage of content production and revision.
traceability and provenance first
iatroX is designed so that content is not detached from the evidence base that supports it. Source discipline, grounded synthesis, and clear evidentiary logic are central to the way the platform is built.
founder-led and clinician-led oversight
Editorial direction is founder-led by Dr Kola Tytler, a trained clinician, with content governance shaped around practical clinical relevance, medical learning utility, and disciplined product behaviour under real-world conditions.
source hierarchy
what iatroX prioritises when content is built
Not all source classes carry the same editorial weight. iatroX uses a defined hierarchy so that content production is led by accepted guidance and strengthened by triangulation rather than by indiscriminate aggregation.
01
accepted clinical guidance first
For UK clinical content, iatroX prioritises accepted guidance sources such as NICE and NICE CKS where applicable, alongside other established nationally relevant guidance layers.
02
triangulation against peer-reviewed research
Where appropriate, guidance-led content is checked against peer-reviewed literature to validate alignment, clarify nuance, and identify areas where additional interpretation or caution may be required.
03
specialty society guidance and expert-domain material
Specialty-relevant material may be incorporated where it improves completeness, precision, or jurisdiction-specific relevance, particularly in areas where specialty guidance materially shapes practice.
04
exam blueprints and public curricula for education
Educational and revision surfaces are structured against official exam blueprints, published curricula, and core competency domains for the relevant market and exam pathway.
05
internal synthesis for clinician-ready delivery
iatroX converts source material into structured, clinician-ready synthesis. The objective is not to replace primary sources but to surface them in a faster, more usable, and more intelligible form.
review workflow
how content moves from evidence to publication
The platform combines algorithmic validation with human oversight. The objective is not simply to publish quickly, but to publish responsibly while preserving the speed clinicians expect from a modern platform.
01
source discovery and targeted retrieval
A proprietary algorithmic system searches the source classes relevant to the task and jurisdiction, identifying the most appropriate material for the specific question or content update pathway.
02
triangulation and semantic comparison
Retrieved guidance is computed and triangulated against peer-reviewed research and other relevant supporting material. Content is then assessed against semantic similarity thresholds and tested again for inconsistencies.
03
automatic escalation when signals conflict
If material appears contrasting, incomplete, or insufficiently aligned, the system does not simply force a polished answer. It flags the scenario for human review rather than lowering the evidentiary standard.
04
human review before and after publication
Static content is reviewed by a human before publication. Reviewed content then remains within an ongoing revision loop rather than being treated as permanently finished once surfaced.
05
scheduled refresh and ad hoc revision
iatroX combines a rolling ad hoc update process with a formal refresh target of every six months. When material changes, pages may be corrected, expanded, or refined accordingly.
scope and applicability
different jurisdictions, different content pathways
iatroX serves both practising clinicians and learners. That means editorial policy must be explicit not only about evidence quality, but also about geographic relevance and content type.
UK clinical content
Clinical knowledge surfaces are structured first around UK-accepted guidance logic, with NICE and NICE CKS forming core reference classes where relevant.
education across four core markets
Educational content is designed for clinicians and learners across the UK, Australia, Canada, and the United States, with exam-facing material mapped to the public blueprint and curriculum landscape of each pathway.
different surfaces, different standards of use
iatroX distinguishes between static editorial content, dynamic AI-supported answers, and educational material. Each is governed with a source-appropriate and workflow-appropriate standard rather than a one-size-fits-all rule set.
safeguards and corrections
how iatroX handles quality control in practice
Editorial quality is not treated as a one-off publishing event. It is maintained through a live system of prioritisation, review, escalation, feedback, and revision.
source prioritisation
Content is not assembled from arbitrary web material. iatroX uses a defined source hierarchy intended to keep outputs grounded in recognised clinical and educational frameworks.
clarity and traceability
Outputs are designed to remain attributable and intelligible, so that users can understand the logic beneath what is being surfaced rather than receiving opaque, free-floating text.
user feedback pathway
Users can report potential issues, missing nuance, or suspected errors. Reported concerns may trigger review, correction, or refinement of the relevant content layer.
escalation where uncertainty is material
Where evidence alignment is weak or important contradictions are detected, content can be withheld from automatic surfacing and escalated into review rather than overstated.
common questions
editorial policy FAQ
What sources does iatroX prioritise?
iatroX prioritises accepted clinical guidance first, particularly UK-relevant guidance for UK clinical use, then triangulates against peer-reviewed research and specialty society guidance where appropriate. Educational content is additionally structured against public exam blueprints and curricula.
Who is responsible for editorial oversight?
Editorial oversight is founder-led and clinician-led under Dr Kola Tytler, supported by a proprietary automated validation workflow that flags scenarios where material appears to conflict or requires closer human review.
How often is content updated?
iatroX uses both ad hoc updates and scheduled refresh cycles. Important changes can trigger earlier revision, while content is also reviewed on a rolling basis with a formal refresh target of every six months.
Can users report errors or concerns?
Yes. Users can report issues, and content may then be corrected, updated, or expanded. Feedback is treated as part of the editorial improvement loop rather than as an afterthought.
Does this policy apply equally to every iatroX surface?
The principles are platform-wide, but their application varies by content type. Static editorial pages, dynamic AI-supported answers, and educational surfaces each operate within their own source, validation, and update logic.