What is an operating system for longitudinal care?
An operating system for longitudinal care is software that runs the operational side of care delivered over many visits, weeks or months. It holds the episode, treatment plan, sessions, insurance approvals and billing in one place. AI workers complete routine work inside it within permitted actions. It is judged on operational measures agreed with the clinic before go-live.
Longitudinal care is care that runs over time: physiotherapy and rehab, developmental paediatrics therapy, dialysis, orthodontics and dentistry, orthopaedic follow-up. The patient comes back many times, several professionals are involved, and an insurer usually approves the care in blocks. This page sets out what the term means, the three layers such a system has, what it is not, and a checklist you can apply to any system that uses the name, including ours.
Is longitudinal care the same as G2211 or chronic care management?
No. G2211 is a US Medicare add-on billing code, in use since January 2024, for office visits that are part of a continuing relationship with a patient. Chronic care management is a US Medicare service for patients with two or more chronic conditions. Both are US billing concepts. Here, longitudinal care means the operational side of treatment delivered over many visits, such as physiotherapy, developmental paediatrics therapy, dialysis and orthodontics, in clinics anywhere, including the UAE, where neither code applies.
Longitudinal care is not a series of single visits
Most clinic software is built around the appointment. A patient books, is seen, is billed, and the visit closes. That fits a general practice consultation or a one-off scan. It does not fit a course of physiotherapy after a knee replacement, a year of therapy for a child with a developmental delay, or dialysis several times a week.
In longitudinal care the unit of work is the episode: a plan, a number of sessions, a baseline, reassessments, and a point where the plan ends or is extended. Most of what goes wrong happens between visits, in places an appointment calendar does not show.
| Aspect | Single-visit care | Longitudinal care |
|---|---|---|
| The unit of care | The appointment | The episode: a treatment plan, its sessions and its reassessments |
| Who is involved | Usually one clinician | A team across professions, plus the front desk, finance and often the family |
| What progress means | The visit was completed | Change against a baseline, measured again at set points |
| Insurance | One claim for one visit | An approval for a number of sessions, with limits, expiry dates and extension requests |
| A missed appointment | A gap in the day | Lost capacity, a plan that slips, and often an approval that runs out before the plan does |
| Between visits | Little | Home programmes, adherence, reminders and recalls |
In Abu Dhabi this is now written into quality reporting: the Department of Health’s twelve outpatient rehabilitation Jawda indicators, in force from Q4 2026, ask a clinic to record the baseline before therapy, reassessments on time and the discharge assessment. They are explained in Position Paper No. 10.
A system of record for the episode, workers inside it, and measures on top
A system qualifies when it has all three. Any one of them alone is a familiar product: practice software, an AI assistant, or a dashboard.
The operations of the episode, shaped for one specialty.
Patients, episodes, treatment plans, sessions, records, insurance approvals and extensions, billing and outcome measures, held together. Each specialty adds its own records, rules and workflows: a physiotherapy plan is not a child’s therapy plan.
Ask: Can it show, for one patient, sessions approved, used and left, against the plan?
Workers that complete routine work and write it back.
AI workers take a role, such as the front desk or clinic finance. Each works only through the functions it is permitted to use, writes completed work back into the system, and hands to a person with the reason when it reaches its limit. It never answers clinically.
Ask: Which actions may it take on its own, and where is that written down?
Operational measures, agreed before go-live.
Cost per completed session, treatment-plan completion, missed sessions recovered, sessions per therapist, approval turnaround, cost per patient interaction, and tasks done autonomously against assisted. Each is set from a baseline of the clinic’s own data.
Ask: Which numbers will we agree before go-live, and from what baseline?
Clinical outcomes are measured separately
A longitudinal care operating system is accountable for administrative and operational measures: whether sessions happened, whether approvals were renewed in time, whether missed sessions were recovered, what each completed session cost to run. Those are things the system and its workers actually do.
Whether a patient walks better, or a child reaches a milestone, is a clinical outcome. It belongs to the clinicians and is measured with clinical instruments. The system records those measures and keeps the reassessment clock, but the AI takes no credit for a clinical outcome without clinical evidence that it caused it. A vendor that blends the two, and reports better recovery as a software result, is claiming something it has not shown.
Not an EMR replacement, and not a booking chatbot
It is not an EMR replacement. It sits beside the EMR. The EMR stays the master patient record and the system that connects to the emirate’s health information exchange. The operating system runs what happens around the record: approvals and their session caps, outcome measures against baseline, the reassessment clock, the home programme and the claims follow-up.
It is not a booking chatbot. A chatbot that books appointments works on one visit at a time and knows nothing about the plan, the approval or the reason a session was missed. In a longitudinal care system the worker that answers the phone can see that the approval ends next week, and the rebooking it makes is written back to the episode.
It is not clinical decision support. The AI workers do not diagnose, rate progress or change a plan. Anything clinical stays with a clinician.
Where care runs over weeks and months
The model applies wherever a patient returns many times under one plan. The last column says plainly what Xamun has built.
| Specialty | What makes it longitudinal | Xamun today |
|---|---|---|
| Physiotherapy and rehab | A course of sessions after injury or surgery, a baseline and reassessments, insurer session caps and extensions, a home exercise programme. | Built specialty version of ClinicOS |
| Developmental paediatrics therapy | Therapy over months or years, several therapists and a doctor on one child’s plan, the family and the school involved, a home programme. | Built specialty version of ClinicOS |
| Dialysis | Sessions several times a week, often for years, with fixed chair capacity and recurring approvals. | Built on the ClinicOS core for a dialysis provider. No public demo or specialty page yet. |
| Orthodontics and dentistry | Treatment plans that run for months, with adjustment visits and staged payment. | Built on the ClinicOS core for an orthodontic practice. No public demo or specialty page yet. |
| Orthopaedic follow-up | Review visits after surgery or injury, often with physiotherapy running alongside. | The same model applies. Not a Xamun specialty version. |
Seven numbers to agree before go-live
These are measures, not results. Each is set from a baseline of the clinic’s own data and agreed with the clinic before the system goes live. This page reports no figures against them.
| Measure | What it counts | Why it matters over time |
|---|---|---|
| Cost per completed session | The cost of running the clinic’s operations, divided by sessions actually delivered | Booked sessions that never happen still cost staff time |
| Treatment-plan completion | Episodes that reach the planned end or a discharge assessment, against episodes started | Plans that stop early are lost care and lost revenue |
| Missed sessions recovered | Missed or cancelled sessions that are rebooked and delivered | Each missed session is capacity that cannot be sold again |
| Sessions per therapist | Sessions delivered per therapist per period | Time spent on notes and phone calls is time not spent in sessions |
| Approval turnaround | Time from the need for an approval or extension to the insurer’s answer | A late extension stops a plan that is working |
| Cost per patient interaction | The cost of handling calls, messages, reminders and recalls, per interaction | A long episode means many interactions per patient |
| Tasks done autonomously against assisted | Actions the AI worker completed on its own, against actions a person approved first | Shows how much work has been handed over, and whether it was earned |
None of these is a clinical outcome. Clinical measures, such as function scores or developmental milestones, are recorded in the system and reported by the clinicians who own them.
Eight checks you can put in a meeting
A system that fails one of these may still be good software. It is not an operating system for longitudinal care.
- The episode is the unit. The plan, the sessions planned and delivered, and the reassessment dates are records, not notes in a calendar.
- Approvals are tracked against the plan. Sessions used against sessions approved are shown before the session is given, and extension requests are drafted from the record.
- Missed sessions are a queue someone owns. Each one is followed up, rebooked and counted.
- The whole team works on one plan. Therapists, the doctor, the front desk, finance and, where the clinic allows, the family each see the part they need.
- AI workers act only within written permissions. Each worker’s role, the actions it may take and the point where it hands to a person are written down and can be audited.
- Completed work is written back. What a worker does lands in the record, with who, what and why, and the count of autonomous against assisted actions is kept.
- The measures are agreed before go-live, from a baseline of the clinic’s own data, and clinical outcomes are kept separate from them.
- It sits beside the EMR. The EMR stays the master record and the link to the health information exchange.
How Xamun builds to it: ClinicOS and Sam
Each row says what we have built and where on this site you can check it.
| Layer | What Xamun does | Where to check |
|---|---|---|
| 1 · The specialty system | ClinicOS: intake, booking, records, billing and claims for multi-branch clinics, with each specialty’s own records, rules and workflows on top. Two specialty versions are public, with films and demos: physiotherapy and rehab, which carries Abu Dhabi’s outpatient rehab Jawda indicators and insurer session caps, and developmental paediatrics, which carries the child’s plan, the therapy and the family’s home programme. Dialysis and orthodontics are also built on the same core for providers, without a public demo yet. | ClinicOS, physiotherapy, developmental paediatrics |
| 2 · AI workers | Sam, the AI worker, hired per role and in early access. In ClinicOS today: the front desk, recalls, intake, clinic finance, and claims and approvals; in RosterOS, rostering. Sam says it is AI every time. Each role is written down before Sam starts: its queue, the actions it may take, the mode for each action and who it hands to. Sam starts in Assist, where a person approves its work, and an action goes autonomous only when its record is strong and the role owner signs off. Anything clinical stays in Assist. Other roles follow the same pattern. | Xami Workers, the clinic front desk |
| 3 · Outcome measures | A baseline from an extract of the clinic’s data, at no cost; one or two sites live beside the EMR; then one reporting quarter compared with the baseline, on the numbers the clinic named at the start. | Healthcare at Xamun |
You buy it as a licence, or under Outcome-as-a-Service. For three years after done, if the agreed number slips, Xamun re-engineers it without asking why; the terms are on Outcome-as-a-Service. What this page does not claim: that the measures above have been achieved at a clinic in the UAE, or that ClinicOS has a built version for orthopaedic follow-up. Client rollouts in the UAE run on UAE-compliant hosting and AI providers, in the UAE.
Questions about longitudinal care systems
What is an operating system for longitudinal care?
An operating system for longitudinal care is software that runs the operational side of care delivered over many visits, weeks or months. It holds the episode, treatment plan, sessions, insurance approvals and billing in one place. AI workers complete routine work inside it within permitted actions. It is judged on operational measures agreed with the clinic before go-live. Clinical outcomes are measured separately, by the clinicians who own them.
What does longitudinal care mean?
Care delivered over many visits, weeks or months under one plan, rather than in a single visit. Physiotherapy and rehab, developmental paediatrics therapy, dialysis, orthodontics and dentistry, and orthopaedic follow-up are examples. The patient returns many times, several professionals are involved, progress is measured against a baseline, and an insurer usually approves the care in blocks of sessions.
Is longitudinal care the same as G2211 or chronic care management?
No. G2211 is a US Medicare add-on billing code, in use since January 2024, for office visits that are part of a continuing relationship with a patient. Chronic care management is a US Medicare service for patients with two or more chronic conditions. Both are US billing concepts. Here, longitudinal care means the operational side of treatment delivered over many visits, such as physiotherapy, developmental paediatrics therapy, dialysis and orthodontics, in clinics anywhere, including the UAE, where neither code applies.
What are the three layers of a longitudinal care operating system?
First, a specialty-specific system that holds patients, episodes, treatment plans, sessions, records, insurance approvals and extensions, billing and outcome measures. Second, AI workers inside it that work only through permitted functions and write their completed work back. Third, operational outcome measures agreed with the clinic before go-live, such as cost per completed session, treatment-plan completion, missed sessions recovered, sessions per therapist, approval turnaround, cost per patient interaction, and tasks done autonomously against assisted.
Does a longitudinal care operating system replace the EMR?
No. It sits beside the EMR. The EMR stays the master patient record and the system that connects to the health information exchange. The operating system runs what happens around the record: approvals and their session caps, outcome measures against baseline, the reassessment clock, the home programme and the claims follow-up.
Is it the same as an AI booking chatbot?
No. A booking chatbot handles one visit at a time and knows nothing about the plan, the approval or why a session was missed. In a longitudinal care system the AI worker on the front desk can see that an approval ends next week, and the rebooking it makes is written back to the episode. It never answers clinically.
Does the AI take credit for clinical outcomes?
No. The system is accountable for administrative and operational measures, such as sessions delivered, approvals renewed in time and missed sessions recovered. Clinical outcomes, such as function scores or developmental milestones, belong to the clinicians and are measured with clinical instruments. The AI takes no credit for a clinical outcome without clinical evidence that it caused it.
Which specialties does Xamun’s ClinicOS cover as longitudinal care?
ClinicOS has public specialty versions, with films and demos, for physiotherapy and rehab and for developmental paediatrics therapy. Dialysis and orthodontics have also been built on the same ClinicOS core for providers, without a public demo yet. Orthopaedic follow-up is another longitudinal specialty where the same model applies.
How is a longitudinal care operating system from Xamun bought?
As a licence, or under Outcome-as-a-Service. Usually it starts with a baseline from an extract of the clinic’s data at no cost, one or two sites live beside the EMR, and one reporting quarter compared with the baseline on the numbers the clinic named. For three years after done, if the agreed number slips, Xamun re-engineers it without asking why.
- Xamun, Position Paper No. 10, “Jawda counts what you wrote down, not what you did”, for the Abu Dhabi outpatient rehabilitation indicators in force from Q4 2026.
- Xamun, Position Paper No. 11, for what an AI front desk in a UAE clinic must say, and what it must hand to a person.
- Xamun, How physiotherapy approvals and extensions work in Abu Dhabi.
- Xamun, Xami Workers, for the Sam roles and how autonomy is earned one action at a time.
This page defines a category and describes how Xamun builds to it. What a clinic must record or report depends on its licence and service type; confirm with DHA, DoH or MOHAP, a lawyer or your insurer.
Name the numbers first. Then look at the system.
Tell us which of the seven measures matter to your clinic, in your own words. We build the baseline from an extract of your data and show the episode running in ClinicOS.