Skip to content

Self-Serve Plans (Mobile)

People who use the app on their own, without a clinic, get their home exercise plan from the app itself. Two flows do that, both in the mobile app and both written by AI from the person's own words:

  • The plan builder runs before there is an account. "I'm New Here" on the welcome screen of the consumer app (Otera, OKTA) opens it: the person describes what is going on, answers a few questions a physical therapist would ask, sees their first week, and creates an account to keep it.
  • The plan updater runs from the home screen of a signed-in patient. The Adjust your plan card takes a request in plain words ("my knee is sore after Tuesday", "make it easier", "less time this week") and rewrites the coming week, which the person accepts or rejects.

Both pick exercises only from the public exercise library: public, active exercises with a demo video, never a therapist's private exercise, a personalized video or an AI-written stand-in. That is the main site's library, or a clinic's own public library when a clinic has turned the updater on. Every exercise the AI names is checked against that library before it is shown or saved, and names, descriptions and videos come from the library, never from the AI.

What the person sees

The plan builder

  1. Tell us what's going on. One free-text field. A message that is not about a physical problem or goal gets a gentle "tell us about a physical problem or goal" right away.
  2. A few questions. The app reflects back what it understood ("What we heard"), then asks three to eight questions, each answered from options ("Other" opens a text field), with an optional "Anything else we should know?" at the end. The questions cover what a safe first week needs, recent surgery or fractures included, so a second round is rarely needed; when something essential is still missing there is one more, and after two rounds the plan is written with what is known.
  3. Your plan is ready. The summary and what is likely going on, the goals, pointers before starting, precautions, what to notice over the week, and the first week's sessions, labelled by day so the rest days show (Day 1, Day 3, Day 5). Each exercise opens a sheet with its video (or photo), dosage and how-to.
  4. Create your account (or I already have an account). The plan becomes the account's first week. Someone signing in to an existing account with unfinished sessions is asked whether to keep them or start the new plan. If the plan cannot be added right away (no connection, a server hiccup), the account is still created and the screen says so, with Add my plan to try again and Continue without it.

If the person describes a warning sign (severe or night pain that does not ease, new numbness or weakness, loss of bladder or bowel control, chest pain, fever with back pain, a suspected fracture, a fall with marked swelling), the app shows the advice to see a doctor today instead of questions or a plan.

The plan updater

  1. Adjust your plan on the home screen (see the flag below; on the web, Manage your plan on the patient dashboard follows the same flag).
  2. The screen shows this week's sessions, a free-text field, and quick chips ("Make it easier", "Something hurts", "Less time", …).
  3. While the AI works, the screen says what it understood within a second or so ("Making it gentler…", "We'll ask you a few more questions first") and shows each new session as soon as it is complete. The close button (or Android's back) stops the request.
  4. Your new week: what changes and why, every session, and Accept this week or Keep my current plan. Accepting replaces the person's unfinished sessions, whoever wrote them, with the new ones; a session they already started (sets logged, a video recorded) is kept. The dashboard, reminders and plan continuation then treat the new week like any other plan and continue from it.

The AI reads the person's recent sessions (pain, effort, what was skipped) and the facts remembered from earlier plans, so "make it easier" eases the exercises they rated painful rather than everything. A warning sign gets the advice to see a doctor, not a new week.

Languages

The plan is written in the language the app runs in (English or Russian). Someone who writes in another language gets the plan in theirs. An older app build, which does not say its language, gets the language of the text the person typed.

Flags

Flag Where Effect
selfServePlanUpdates Admin → Feature Flags → Plans & HEP builder Whether patients may rewrite their own week. Missing means on for the main site (tenant 1) and off for a clinic; a stored value wins. Off hides the card in the app and on the web and the API refuses the rewrite, so a therapist's plan stays theirs. On the main site it is on for every patient, including those connected to a therapist there. Signing up from the builder is never blocked: a new account always gets the plan it was built with.

The quick judgements that let the app react within a second (is this about the body, is there a warning sign, is enough known, which exercises fit) come from OpenAI's Decisions API wherever the server has OpenAI set up, independently of the openaiDecisions flag; without it, the plan writer makes them itself, more slowly. See Feature Flags for how flags are stored, and Self-Serve Plans (internals) for how it all works.