Skip to content

Condor · the clinical assistant

Condor, the Dudoxx clinical engine

Condor plans the work, you approve it.

Condor gathers what you need to know about the patient and shows its plan. A change you typed runs as asked; a delete, cancel or void always waits for your approval.

What Condor does

  • Plans you can see

    Condor plans its steps and shows them as it works: what it reads and what it brings back.

  • Approval first

    Before a delete, cancel or void, Condor always waits for your approval.

  • The patient's memory

    Visits, letters, lab results and scanned reports come together in one consolidated picture of the patient.

  • Diagnosis support

    Advisory differential suggestions are shown for the doctor's review before anything is recorded.

Watch how it works

A narrated tour of the real screens, chapter by chapter.

Working with Condor

The Dudoxx AI assistant: where it lives, how to prompt it for medicine, and how it plans, runs and reports its work.

Narrated in: English, German, French35 chapters

All manuals

AI suggests; clinicians decide.

Assistants make the data work faster; they do not take over the judgement about what belongs in a patient's record.

Condor at work

  1. Your choices at the approval

    • Approve
    • Edit first
    • Reject: the change is not made

    Keep the decision

    Before a delete, cancel or void, Condor stops and waits for your decision.

  1. Ask your question

    Ask Condor a clinical question and the first thing you see is a plan.

  2. Check the run

    The run recap lists the steps completed, the tools used and the time taken.

How a Condor run moves

A request becomes one plan, and the plan runs step by step while you watch. A change you typed runs as asked. A delete, cancel or void always waits for the doctor's approval.

Condor: plan, ask, act — the doctor approves before a destructive change The doctor asks in chat or on a patient; Condor drafts one plan for the request; the steps run on clinic data with the doctor's own permissions, and the model sees aliases, never record ids. When two patients match, a card lets the doctor pick. Reads and changes the doctor typed run as asked; a delete, cancel or void always waits for the doctor's approval (approve, edit first, reject; a rejection changes nothing). Results arrive as cards: tables, documents, sources. reads + changes the doctor typed delete or cancel approved two patients match doctor picks rejected Doctor asks in chat or on a patient 1 Condor Plan drafted steps in order, some side by side · for this request 2 Steps run on clinic data · your rights · model sees aliases only 3 Doctor approves approve · edit first · reject 4 Result cards tables · documents · sources 5 Which patient? the doctor picks from a list Nothing changes the change is not made A change the doctor typed runs as asked: the request is the approval. A delete, cancel or void always waits for the doctor, whatever the settings. the answer doctor checkpoint starts here nothing written automatic step doctor decides
Condor: plan, ask, act — the doctor approves before a destructive change The doctor asks in chat or on a patient; Condor drafts one plan for the request; the steps run on clinic data with the doctor's own permissions, and the model sees aliases, never record ids. When two patients match, a card lets the doctor pick. Reads and changes the doctor typed run as asked; a delete, cancel or void always waits for the doctor's approval (approve, edit first, reject; a rejection changes nothing). Results arrive as cards: tables, documents, sources. reads + changes the doctor typed delete or cancel approved two patients match doctor picks rejected Doctor asks in chat or on a patient 1 Condor Plan drafted steps in order, some side by side · for this request 2 Steps run on clinic data · your rights · model sees aliases only 3 Doctor approves approve · edit first · reject 4 Result cards tables · documents · sources 5 Which patient? the doctor picks from a list Nothing changes the change is not made A change the doctor typed runs as asked: the request is the approval. A delete, cancel or void always waits for the doctor, whatever the settings. the answer doctor checkpoint starts here nothing written automatic step doctor decides
Condor: plan, ask, act — the doctor approves before a destructive change The doctor asks in chat or on a patient; Condor drafts one plan for the request; the steps run on clinic data with the doctor's own permissions, and the model sees aliases, never record ids. When two patients match, a card lets the doctor pick. Reads and changes the doctor typed run as asked; a delete, cancel or void always waits for the doctor's approval (approve, edit first, reject; a rejection changes nothing). Results arrive as cards: tables, documents, sources. request one plan per request two patients match doctor picks delete or cancel reads + changes the doctor typed rejected approved Doctor asks in chat or on a patient 1 Condor Plan drafted steps in order, some side by side · for this request 2 Steps run on clinic data · your rights · model sees aliases only 3 Doctor approves approve · edit first · reject 4 Result cards tables · documents · sources 5 Which patient? the doctor picks from a list Nothing changes the change is not made A change the doctor typed runs as asked: the request is the approval. A delete, cancel or void always waits for the doctor, whatever the settings. the answer doctor checkpoint starts here nothing written automatic step doctor decides
Condor: plan, ask, act — the doctor approves before a destructive change The doctor asks in chat or on a patient; Condor drafts one plan for the request; the steps run on clinic data with the doctor's own permissions, and the model sees aliases, never record ids. When two patients match, a card lets the doctor pick. Reads and changes the doctor typed run as asked; a delete, cancel or void always waits for the doctor's approval (approve, edit first, reject; a rejection changes nothing). Results arrive as cards: tables, documents, sources. request one plan per request two patients match doctor picks delete or cancel reads + changes the doctor typed rejected approved Doctor asks in chat or on a patient 1 Condor Plan drafted steps in order, some side by side · for this request 2 Steps run on clinic data · your rights · model sees aliases only 3 Doctor approves approve · edit first · reject 4 Result cards tables · documents · sources 5 Which patient? the doctor picks from a list Nothing changes the change is not made A change the doctor typed runs as asked: the request is the approval. A delete, cancel or void always waits for the doctor, whatever the settings. the answer doctor checkpoint starts here nothing written automatic step doctor decides

How a Condor run moves: the request, one plan, the steps, the doctor's approval and the result cards.

Open the full diagram (opens in a new tab)

What doctors ask about Condor

Bring a real case to the demo

We will run it with Condor while you watch the plan.