Healthcare

Patient Care Journey

Every appointment waits for insurance approval, and the next specialist is chosen from what the last visit found.

by StudioX5.0 (1) 1 downloadsFreeImport and run

What it does

A patient presents with symptoms. The Reasoning Core recommends who to see; each appointment is gated by an insurance approval; after each visit the core evaluates the patient and either stops (resolved) or reasons about the best next expert and requests the next approval. The path is decided by the LLM, not hardcoded.

How it works

A patient presents with symptoms; the Reasoning Core decides who they should see, one visit at a time, with each appointment gated by an insurance approval. After every visit the core evaluates whether the patient is better and — if not — reasons about the best next specialist and requests insurance for that appointment. It stops when it judges the case resolved. The escalation path is decided by the LLM, not hardcoded.

How it's wired

One poll watcher intakes waiting patients and raises the first insurance gate. Each approval's intent invokes the recommended expert, updates the patient's journey, and — if still symptomatic — recommends and requests the next appointment (self-chaining through the decision queue).

The team

DDoctor

General practitioner — first-line assessment of common complaints; decides whether a specialist or imaging is warranted.

SSpecialist

Specialist physician — deeper, targeted diagnosis when a GP can't resolve the complaint (neurology, cardiology, etc. as fits the symptoms).

RRadiology

Radiology / imaging — MRI, CT, X-ray to find structural causes a physical exam misses.

Connects to

Patient Intakeno setup

What it watches

Patient Intake + Insurance Gatepollevery 60s

Polls the intake queue for waiting patients; each approval self-chains to the next recommended appointment.

Human approval

One consequential step waits for a person's approval before it acts.

What it already knows (2)

Mission overview — the roster and the goalChat protocol — admitting a patient in conversation

Data it carries

1 table

What it shows a human

Patients by statusPatient charts

Ask it

“New patient: James Chen, 51 — sharp chest pain on exertion with shortness of breath.”

“New patient: Maria Gonzalez, 34 — persistent headache, vomiting, and dizziness for three days.”

“New patient: Aisha Patel, 29 — recurring upper-abdominal pain and nausea after meals.”

“New patient: Liam O'Brien, 46 — lower-back pain radiating down the left leg, with numbness in the foot.”

“New patient: Sofia Rossi, 38 — blurred vision, frequent migraines, and sensitivity to light.”

“New patient: David Kim, 57 — joint pain and swelling in both knees with morning stiffness.”

“New patient: Grace Okafor, 62 — shortness of breath climbing stairs and swelling in both ankles.”

“New patient: Tom Whitfield, 44 — sudden severe headache, worst of his life, with neck stiffness.”

Before it runs, you'll

1Confirm the Patient Intake server at import — it is credential-free, and the answer repoints it if you have your own.
2Provision the three experts — Doctor, Specialist, Radiology (pure reasoning).
3Enable the observation, then approve (or deny) each insurance gate as it appears and watch the patient's chart fill visit by visit.

Import into StudioX

Download the .sxm file.
In StudioX → Missions → Import, drop the file.
Review, finalize, and it's live — chat to it or enable the observation.

Reviews

5.0 (1)

Ajay Malik

Really interesting approach to agentic healthcare workflows. I like that the care path isn’t hardcoded—the Reasoning Core reassesses after each visit, while insurance approval remains a human-controlled gate.

8/16/2026