Your team manages the patient.
Connect remembers the dose schedule.
Not every GLP-1 patient moves up on the same timeline. Connect lets your practice define how long a treatment plan stays at each dose, tracks each patient's cycles, and advances the dose on the schedule you configured, with the provider able to override it at any time.
Available on every Connect plan.
The dose schedule should follow the treatment plan, not your staff's memory.
Some patients may stay at an early dose for several cycles. Others may move through the treatment plan sooner. Connect keeps the configured timing attached to the patient, so your team can see where they are now and what is planned next.
Three months at one dose. Two months at the next. Connect keeps track.
Example: a provider-configured GLP-1 plan keeps a patient at the starting dose for three monthly cycles, then moves to the next dose for two cycles. Connect counts the cycles, keeps upcoming orders visible and advances the dose when the configured point is reached. The provider can override the progression at any time.
Set the dosing schedule once. Let Connect track the timing.
Define the starting dose, the planned progression, the number of cycles at each dose and the maximum dose in the treatment plan. Patients enrolled on that plan inherit the schedule, and an individual patient can still be handled differently when needed.
If the patient is doing well at the current dose, keep the plan there.
A dose does not need to change just because another month arrived. When the provider's treatment plan calls for more time at the current dose, Connect can keep that dose active for additional cycles without rebuilding the program. When the configured change is due, it surfaces for review.
Connect advances the dose on schedule. The provider can override it at any time.
Dosage progression can be configured on medications where the dose needs to increase after each dose or after a set number of cycles. Connect shows the current dose, the next dose and where the patient sits in the treatment plan, and the provider can override the progression at any point in the patient's journey.
Give patients a clear view of where they are in the plan.
Patients can see their current dose, their next shipment and the next planned dose change in the portal. Clinical questions still route to the provider, but routine schedule questions do not have to start with the front desk.
Stop maintaining a separate GLP-1 dosing calendar.
Connect tracks cycles at the current dose and surfaces the next planned change with the order.
The medication order reflects the treatment-plan schedule, and the provider can override the dose before it goes out.
Dose changes are recorded on the patient record with the date and the user.
GLP-1 dosage tracking, answered
Dosage progression can be configured on medications where dosages need to increase after each dose or after a certain number of cycles. Providers can override the dosage progression at any time during the patient's journey in the plan.
Yes. Each treatment plan can carry its own order cycle, dose schedule and hold rules, so a GLP-1 on a 28-day cycle and another medication on an 84-day cycle move independently inside a single subscription.
Yes. The provider can override the progression on an order, and the treatment plan can be configured to hold doses for multiple cycles. A paused subscription does not consume a cycle.
Connect can be configured to keep a dose active for multiple treatment cycles. How long a patient should remain at a dose is a clinical decision for the licensed provider.
Every Connect plan. Dosage tracking and dosage progression are not gated by tier, and neither is the medication catalog. Plans change your enrollee capacity, transaction rate and support level.
Bring your GLP-1 dosing workflow. We'll build the schedule in Connect.
Show us how your practice handles dose progression today. We will configure the starting dose, the cycle timing, the holds and the planned progression, then show what the provider and the patient see when the next order comes due.
%20(1)%20(1)%20(1).png)