Condor — the next-generation clinical engine
Condor keeps important patient facts and current procedures available through governed longitudinal memory that curates change and self-heals inconsistencies — always under clinical oversight.
- Runs alongside TUCAN
- Diagnosis decision support
- Curated patient memory
- Reviewed documents
- Switch flow-by-flow
- Open FHIR standard
How Condor works
Condor is the next-generation engine running alongside TUCAN. It plans the work, streams a live activity feed, and reviews its own documents before finalising.
Route
Each capability is routed to either TUCAN or Condor. Clinics move one capability at a time, and any of them can be switched back instantly.
Plan
Condor plans the request and binds only the tools that request needs, working on the clinic's real data.
Show
Every tool start and result streams to an on-screen activity feed, so the work is visible as it happens.
Review
For documents, an independent reviewer scores and improves the draft in a bounded loop before it is finalised.
Approve
Before anything is written, prescribed or billed, an approval card appears in the conversation with three choices — approve, edit first, or reject. The gate is built in and cannot be switched off.
A closer look
Move to the new engine, one capability at a time
Condor is the successor engine, running side by side with TUCAN. A single control routes each capability to one engine or the other — nothing is big-bang, and any capability can be rolled back instantly.
- The Diagnosis Engine runs on Condor with clinical guardrails switched on.
- Each capability moves independently — no downtime, no all-or-nothing cutover.
- TUCAN keeps running for everything not yet moved; it is not retired.
The Diagnosis Engine — decision support, with guardrails
The Diagnosis Engine helps a clinician reason through a case: it surfaces candidate conditions from a curated disease-knowledge base, aware of comorbidities. It is decision support — the clinician always decides. Condor also produces documents that an independent reviewer scores and improves before finalising.
- Surfaces candidate conditions to consider — it never diagnoses the patient for you.
- Clinical guardrails stay on for diagnostic work; the clinician is always in control.
- Documents are produced, independently reviewed, improved and only then finalised.
What Condor adds
Runs alongside TUCAN
Condor and TUCAN work side by side. Clinics adopt the new engine capability by capability, with instant rollback — never a disruptive switchover.
Diagnosis decision support
The Diagnosis Engine surfaces candidate conditions from a curated disease-knowledge base, aware of comorbidities — assistive support, never an autonomous diagnosis.
Clinical guardrails
Diagnostic work runs with clinical guardrails on. The engine supports the clinician's reasoning; the clinician always makes the call.
Reviewed documents
Condor produces a document, then an independent reviewer scores and improves it in a bounded loop — so what you finalise is already checked.
Live activity feed
Every tool start and result streams to an on-screen feed, so the work is transparent as it happens.
Attachment intelligence
Condor reads uploaded scans and PDFs and summarises them into the record, and can bring in up-to-date external references as sourced cards.
Three modes, one safety rule
Ask answers, Task runs one scoped job, Auto chains a multi-step workflow. The mode changes how much the engine does on its own — it never changes the rule that a write waits for your approval.
Context and citations built in
Open it from a patient and that chart is already in context, within your own role and clinic scope — and every fact carries a citation chip back to the record it came from.
See it on screen
Live views of the product, built from the real interface.
1 of 3
Frequently asked questions
Ready to Transform Your Practice?
Explore how Dudoxx coordinates clinical and administrative workflows on one FHIR R4 platform.
