Home physio logged, reviewed, progressed on review.
Clinical · Full PHI · Physiotherapy & RehabThe home programme’s second side ships inside PhysioFlow (Physio) rather than as an app of its own: a day of an exercise is logged, the physio reviews it once, and a progression cannot be written — a constraint trigger refuses it — until a logged attempt has been reviewed and passed; the Progress button stays disabled until then, and the exercise tile counts the days logged and the days passed. The log is staff-entered: the physiotherapist records what the patient reports, because no patient-side surface writes here. What is left of this idea is the video: nothing attaches a recording to a log, so "form" is what the physio saw in the room or was told, not what a camera saw.
It does not verify adherence by video — no recording is attached to a log, and adherence is what the physiotherapist entered from the patient’s account. It does not auto-progress on counts: the database refuses a progression until a physio has passed a logged day.
Every app page carries this section. A listing with only benefits is an advertisement.RehabCam reads home programmes and writes nothing — the log and the review are PhysioFlow’s. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
It does not verify adherence by video — no recording is attached to a log, and adherence is what the physiotherapist entered from the patient’s account. It does not auto-progress on counts: the database refuses a progression until a physio has passed a logged day.
All clinical data stays in the record; operational history stays queryable.
RehabCam 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.