GLP-1 patient follow-up app: a clinical workflow checklist

Start with a clinical workflow question

For a team following patients prescribed GLP-1 medicines, evaluating a patient app is different from comparing complete practice-management systems. Start with one question: at the next visit, can we find the injections and observations a patient recorded, with dates and gaps visible? WHO describes obesity care as long-term and person-centred, supported by health professionals. A tool needs to fit that care process.

Decide who will use the information and at what point. An endocrinologist, another weight-management clinician and a receptionist may need different workflows and access. Begin with the team’s actual work, without treating app adoption as evidence of better clinical outcomes or adherence.

Source: WHO: GLP-1 guidance within comprehensive, person-centred care

Demonstrate the route from the phone to the review

Use a demonstration account with fictional data. Create an entry in the app, check its date and find the same information in the team’s environment. In myMON, availability in the clinic panel depends on an internet connection and an active clinic link. A synced entry does not confirm that a professional has read it.

Ask the person responsible for reviewing records to follow that route. Observe whether they can distinguish a recorded injection, a reminder and missing information. This tests a workflow; it does not validate treatment or establish patient outcomes.

Keep patient-reported information separate from assessment

A symptom entry is a patient’s observation. Recorded weight and measurements also need context. Before using an entry, check its date, source and uncertainties instead of treating a gap as proof of a missed injection or discontinued care.

Agree who reviews the history, how questions are escalated and where professional assessment will be documented in the clinic’s workflow. The app brings records together. Diagnosis, prescribing and treatment adjustments remain the responsibility of qualified professionals.

Give the patient an agreement they can explain back

During onboarding, show a short example and ask the patient to explain what they will do next. The aim is to check understanding, not require perfect logging. Select what to record according to the care plan the team has established.

• What to record, and how to make a question or a gap clear.
• Who will review the history and what review routine was agreed.
• Which channel to use for clinical questions and what response time to expect.
• Where to get technical help and how to seek care when waiting is not appropriate.

Evaluate privacy alongside access

Before using real information, review the product’s policies and your clinic’s access arrangements. Ask which records are shared, who can view them and how correction, account-link removal and deletion requests work. Check the requirements that apply to your practice; a generic security statement does not answer these questions.

Avoid using real health records in presentations or posting health information in public support channels. Establish an explicit clinical contact channel as well: saving an entry or receiving a reminder is not a request for urgent medical care.

Finish the demo with an operational decision

At the end, record whether the patient and team completed the agreed route, what difficulties occurred and who needs to resolve them. Discuss support, access and implementation before expanding use. Compare the workflow your practice needs with what was actually demonstrated. Do not assume additional capabilities or attribute unmeasured outcomes to the software.