Your questions, answered.

Adherence intelligence for medically supervised metabolic weight-loss programs: connect patient signals, understand likely barriers and coordinate timely support through clinic-approved outreach and care-team review.

Yes, the proposed scope can include participating locations within your organization. Eligibility, system access, ownership and rollout requirements are agreed together.

The initial scope can include up to three agreed medications. Medication, formulation, prescribing context and content sources must be defined and reviewed. This is not a claim that every medication is already supported.

Agreed care milestones, consent and communication preferences, patient replies and relevant follow-through events. Measurements are included only when needed for the approved journey. Missing data and inferred barriers are kept distinct from confirmed facts.

Compatibility must be verified. We need to establish available events, permission to send through the intended channels, access to replies and a workable clinical handoff. Live external integrations are still in development.

AI can assist with drafting journey branches and interpreting replies. Approved sources, clinical review and deterministic delivery rules constrain what can happen. AI does not make treatment or dose decisions.

The clinic approves content and workflow rules, and names staff for clinical concerns, ambiguous responses and follow-up. Routine automation does not remove the need for clinical ownership.

No. It supports communication and follow-through around the clinic’s plan. It is not an emergency service or a substitute for medical assessment.

Through day-90 continuation, required care completed, interruption resolution, staff effort and collected contribution. Replies and engagement rates are supporting indicators. Appropriate pauses or discontinuations are not retention failures. Calculator outputs are scenarios, not observed outcomes.

Program drafts and synthetic previews are available. Live enrollment, messaging and integrations require implementation, security validation, appropriate agreements and authorization before use.