Built into Care Plans: every programme a patient is on, on one page.
Clinical · Full PHI · Every specialtyRead against what already exists, “one plan every clinician can see” turned out to be a join rather than a product. Care Plans already holds the programmes, the dated milestones, the overdue clock and the skip reasons; what it had no read for was the PATIENT — somebody on three programmes appeared three times on the chronic panel and nowhere as one person. So that read shipped inside Care Plans instead of beside it: open anyone on the panel and you get every programme they are on, every open milestone across all of them in date order, how many are late, and when they were last seen. It is the same rows the programme owner works from, not a copy of them, which is the only way one plan stays one plan.
It is not a separate app and adds no second plan, no parallel goal engine and no coordinator role. It does not reconcile medicines — the prescription list is the medication module’s, and duplicating it here would be a second answer to what a patient is taking. It shares nothing outside the practice: a patient moving between facilities of the same group is CrossCare, and a different organisation is a referral, not a plan.
Every app page carries this section. A listing with only benefits is an advertisement.OnePlan reads the care plans the practice already runs, the visit record and writes nothing — it is a read across the plans that exist. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
It is not a separate app and adds no second plan, no parallel goal engine and no coordinator role. It does not reconcile medicines — the prescription list is the medication module’s, and duplicating it here would be a second answer to what a patient is taking. It shares nothing outside the practice: a patient moving between facilities of the same group is CrossCare, and a different organisation is a referral, not a plan.
Every record stays; only the workflow leaves.
OnePlan is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.