How it reaches the app
Your patient creates a single-use link in their app and gives it to you with a passcode. You open it in a browser and fill in a form. No account, no sign-up, nothing installed. The link works once and expires on its own.
Your program, in your patient’s pocket: your stage windows, your supplement lines, your lab schedule, replacing ours. Loopa handles the part that happens between visits: protein, fluid, supplements, symptoms and movement, logged daily and summarized for the appointment.
Loopa ships a standards-based reference protocol of stage windows, protein and fluid targets, a supplement schedule and a lab calendar, assembled from the guidelines listed in Sources and quoted rather than paraphrased. It is a default for a patient whose team has not sent anything in, and it is labeled as one: until you send yours, the app calls it a reference timeline and tells the patient their dates are yours to set.
Your patient creates a single-use link in their app and gives it to you with a passcode. You open it in a browser and fill in a form. No account, no sign-up, nothing installed. The link works once and expires on its own.
Stages with your own day windows, textures, protein and fluid targets, sip amounts, rules and exit criteria. Supplement lines by nutrient, dose, unit, frequency, route and separation rule. Lab milestones with your own panels. Twelve stages, twenty supplement lines, twenty-four lab milestones.
A section you fill in replaces the published one entirely. A section you leave empty keeps the reference, which is why the reference is there. Resolution is per stage rather than per field, so a patient never sees a stage that is half your protocol and half ours.
What you send is inert until they open it, and they see exactly what it would change first. They cannot edit it, because its value is that it is your words. They can decline it, and they can withdraw it later, at which point the published reference resumes and the app says so.
The patient does. Loopa does not run a clinician registry and does not claim to have checked your credentials, because the person who knows who they handed the link to is the person who handed it over. Saying otherwise would be dressing up a lookup as an assurance.
Any published supplement line can be replaced with your own figures, and any line can be stopped, with your reason shown to the patient on the schedule itself. A stopped line raises no reminders.
There is no clinician dashboard and no standing feed. That is a decision, not a gap: a channel that keeps delivering after the relationship has ended is one nobody remembered to close. When your patient wants you to have their data they generate a report link from inside the app.
Time-limited, revocable at any moment, and it can carry a passcode. The file itself is stored encrypted under the patient’s own key and is never emailed by the platform. The patient shares it or nobody does.
Their track and its dates, the stage they are in and when they entered it, their full stage history, the supplement schedule with each line’s source, the symptom journal for the period, and their food-tolerance list.
The same export carries the parts of their log they chose to include across the period: weight and measurements, activity, vitals, medications and the protocol journals. It is built for the fifteen minutes before an appointment.
The patient can see that the link was opened, and how often. IP addresses are kept only as keyed hashes, enough to tell them the same reader opened it twice, not enough for anyone to hold your address.
None of these decide anything. They are standing cards and watch-list entries that put the published caution in front of the patient at the moment it is relevant, and name you as the person who settles it.
The published guideline is that nonsteroidal anti-inflammatory drugs should be completely avoided after bariatric surgery. (source) Setting up a bariatric track adds the NSAID class to the patient’s interaction watch list, with the severity set by the procedure. The anastomosis procedures carry the stronger warning.
The multisociety guidance frames perioperative GLP-1 use as shared decision-making between the patient and their procedural, anesthesia and prescribing teams. (source) The card says that and sends them to that conversation. It does not tell them to hold a dose and it does not supply a date.
Before a scheduled procedure the app tells the patient to get your written list of what to pause and the exact dates, and to bring it away with them. Loopa records what they report. It never supplies a stop date for anything.
Shown to everyone on the track, never triggered by reading somebody’s log. Nothing in the feature triages, and there is no action anywhere in it that places a call.
The alcohol card quotes the long-term cohort evidence on alcohol use disorder after these procedures. (source) The pregnancy card carries the published guidance to avoid pregnancy for 12 to 18 months after surgery. (source) Both point at your team for the specifics.
Early and late dumping are described as the international consensus describes them, with its dietary first line of smaller portions, fluids delayed about 30 minutes after a meal, simple sugars eliminated, protein-rich food eaten slowly. (source) The stage rules carry the same guidance, so the app is not saying two things.
If your patient works with a Loopa coach (your own in-house staff, or a trainer they found themselves) the coach sees the training and habit half and nothing clinical. The split is enforced in the service, not in the interface.
Which stage the patient is in and for how long. How many days they logged in the last two weeks, and their average protein and fluid against that stage’s target. How many supplement reminders are switched on, as a count and never which ones. Which symptoms were flagged and how often over 30 days. That a care team protocol exists, never what it says.
Any supplement name or amount. Any lab result and any lab date. Weight and anything measured from it. The notes written on a symptom and the food beside it. The food-tolerance list. Questions written for the care team. Anything you sent in.
A coach supports the training and the habits. They cannot change a stage, a supplement or a lab schedule, and there is no route in the app by which they could.
Consent is per coach and per category, default off, and revocable. Changing coach ends the old coach’s access in the same request.
Programs that want this experience branded as theirs run mobieusHealth, the white-label version of the same platform: your name, your colors, your domain, the same engine underneath. If that is the conversation, it starts the same way as any other.
No, and there is nothing for you to sign up for. Your patient creates a single-use link in their app and gives it to you with a passcode. You open it in a browser, fill in the form and submit. The link is spent at that point and it expires on its own. Nothing is installed and no credential of yours is stored.
Three sections: their eating stages, their supplement schedule and their lab schedule. Stages take your own day windows, textures, protein and fluid targets, sip amounts, rules and exit criteria, up to twelve of them. Supplements take nutrient, dose, unit, frequency, route and any separation rule, up to twenty lines. Labs take your own milestones and panels, up to twenty-four. Free-text fields are length-capped and the numeric fields are range-checked.
Yes, and completely, section by section. Where you set stages, your stages are what the patient sees and the screen is headed Your care team’s protocol. A section you leave empty keeps the published reference, which is the point of having one. Resolution is per stage and all-or-nothing rather than field by field, so the patient never sees a stage that is half yours and half ours.
No. Its whole value is that it is your words and not theirs. They can decline it before it takes effect, and they can withdraw it afterwards, at which point the published reference comes back and the app tells them so. What they cannot do is quietly reword it and leave it looking like yours.
Only what they send you. There is no clinician dashboard and no ongoing feed, by design. When they want you to have their data they generate a read-only report link (time-limited, revocable, optionally passcode-protected) and the bariatric section of it carries their track, current stage and stage history, the supplement schedule with each line’s source, their symptom journal for the period and their food-tolerance list.
It is neither. Loopa is a tracking, education and adherence tool. It does not diagnose, does not recommend or rank a procedure, does not assess candidacy, does not set or adjust a dose, and never supplies a date to stop a medication before surgery. Where a member asks it something in that territory, it points at their care team. It is built so that it cannot do otherwise, and that is checked rather than assumed.
The protocol you sent is theirs to withdraw, and withdrawing it restores the published reference. Report links expire and can be revoked at any time by the patient. Nothing you sent continues to update, and nothing about them continues to reach you.
Yes. That is mobieusHealth, the white-label version of the same platform for programs that want the experience branded as theirs. Read about mobieusHealth or talk to us about your program.
Loopa shows you what the published guidelines say. It does not decide what procedure is right for you, and it never sets a dose. Your care team does both. Questions about your medication belong with your prescriber. Loopa records what you report and reflects it back. Where your care team says something different from anything here or anything in the app, follow them.