Practice management runs the visit. iksa runs the protocol.
Current software is built to book a patient and fill some labs and prescriptions. iksa is the harness for n‑of‑1 medicine, built to run clinical operations around a patient’s protocols instead of bookings. Your calendar and your chart stay where they are.
Leaves outThe record a study needs, every result sourced and dated.
The three sides
The patient, by reminderDoctors, nurses and patients, and a clinician decides each change.
The system of action
Reminders and follow-up messages, no markersReads each result, flags what’s due, drafts the follow-up and routes what’s clinical to a clinician.
The protocol
A plan as a series of booked servicesEvery protocol a patient is on, read from the doctor’s own notes and carried for years.
The clinical context platform
Who the patient is, when they came and what they paidLabs, notes, genetics, messages and wearables, each with its source.Reads the booking system beside it, where it connects
Covers part
Leaves out
iksa covers all of it
The harness, from the clinical context platform up to the evidence, beside booking and practice software. Booking and practice software covers part of the clinical context platform, the protocol, the system of action and the three sides, and leaves out the rest. iksa covers all of it, and reads the booking system beside it, where it connects.
The EHR holds the visit and the bill, the CRM holds the lead, the dashboard holds the biomarkers, and nobody runs the protocol
Most software is still adapting practice management for med spas instead of building adverse event reporting, patient-reported outcome monitoring, or the many other feedback loops necessary to effectively generate real-world evidence that regulators require.
The EHR holds the visit and the bill, the CRM holds the lead, the dashboard holds the biomarkers, and nobody runs the protocol
A calendar can’t watch a biomarker, so the protocol runs on iksa
A protocol for one patient needs what a trial protocol has: the markers it should move, the target for each and the warning signs to watch for. A harness runs that for every patient you keep, and reads every result against that patient’s first draw.
A marker moves
Practice software files a new ApoB with the visit, while iksa reads it against that patient’s target with their genetics beside it, so their doctor opens that patient on what moved.
A side effect comes up
A patient mentions in a message that their skin has tingled since the incretin dose went up. Practice software has nowhere to put it, and on iksa it goes by urgency to a nurse or doctor with what they reported.
A re-test falls due
A calendar knows only what someone booked, and on iksa the re-test the doctor dated six weeks into a woman’s testosterone protocol stays open with your team until it’s closed.
A dashboard or a CRM on its own splits one patient in two
With no payer in between, a patient’s protocol is also the clinic’s book of business, so holding both on one record beside your EHR is the painkiller.
An outcomes dashboard on its own
Doctors love it in the demo, and then it is one more thing for them to keep up, with no nurse able to pick up what it shows, so the tracking stops.
A CRM on its own
The nurse answers with no clinical context in front of them, the follow-up gets botched, and the patient just doesn’t come back.
One record beside your EHR
A doctor’s change to the protocol is there when the nurse opens the patient, and you read what each therapy brought in on that same patient.
Anyone can buy a model, but no model runs a protocol
These protocols are moving faster than any general model retrains, and no general model was specialized for them. A doctor asking about a therapy their clinic runs every day gets told it shouldn’t be used and gets a diluted answer on the rest. Clinical Intelligence beats the general models on this medicine because it follows each protocol’s markers, re-tests and targets for the one patient in front of that doctor, with the source behind every answer.
It waits to be asked
A general model answers the question someone types, and a protocol runs on what nobody thought to ask, so noticing what came due and what moved stays somebody’s job.
It meets the patient from scratch
It knows nothing of a patient until someone on your team feeds it their files, and on a hard case it still answers from what was said at the first visit.
Its answer stops at the screen
Nothing it says reaches a nurse, becomes a follow-up or gets kept with who decided what, so the work around the answer is all still yours.
iksa is for the patient whose protocol keeps changing, year after year
iksa fits when
Your patients follow a protocol written for them, over months and years.
They pay you directly, and they stay because the protocol is working.
Practice software is enough when
Insurance pays per visit, and the visit is the whole relationship.
Most patients come once, for one treatment.
See one patient’s protocol run, from the doctor’s change to the nurse’s follow-up
Bring a protocol you run. We’ll walk one patient through it.