OnePlan

Every programme a patient is on, on one page — inside Care Plans. A view inside Care Plans — installing it installs Care Plans, which 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. 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 — the same rows the programme owner works from, not a copy of them, which is the only way one plan stays one plan.

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 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.

Yes — OnePlan is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.