How to Screen GLP-1, TRT & Peptide Patients Online Sept 2026

What Conditional Logic Does in a Patient Intake Questionnaire

Conditional logic in a patient intake questionnaire means the form responds to what a patient selects. Answer "yes" to a thyroid history question, and a follow-up appears. Answer "no," and the form skips it entirely.

This mechanic goes by several names: branching logic, skip logic, though the behavior is the same. Prior answers control which fields show next. A GLP-1 weight loss inquiry patient and a peptide inquiry patient might start on the same form, but their paths diverge almost immediately based on service interest, medical history, and current medications.

For elective-care practices screening online patients, that specificity matters. A form asking everyone every question creates friction, raises abandonment, and collects noise alongside signal. Conditional logic keeps the form short for patients who qualify quickly, and thorough for those who need closer review.

Why Elective Care Practices Cannot Use Generic Intake Forms

Generic intake forms were not built for GLP-1 programs, TRT, or peptide therapy. They ask the basics and stop there, leaving providers without the clinical picture they need to make a responsible prescribing decision.

The consequences show up in practice. A large share of GLP-1 prescriptions now originate from online intake, and a widely reported secret-shopper investigation found many of those prescriptions followed questionnaires reviewed in five minutes or less that never asked about disordered eating, active medications, or baseline labs. A form that misses those questions creates real liability exposure and puts patients at risk.

Elective-care practices offering these services have specific screening requirements, real contraindications, and patients who cannot be treated identically at the intake step.

The Anatomy of a Conditional Intake Form for High-Risk Services

A well-structured conditional intake form for high-risk services has two distinct layers.

The first is a universal intake layer that every patient completes: demographics, reason for visit, and general health history. This section is short and non-branching, collecting enough baseline information to identify who the patient is and what they're seeking.

Once a patient selects a service type, the second layer activates. A GLP-1 weight loss selection triggers a path entirely different from peptide therapy, pulling in only the fields relevant to that service's contraindication profile and screening criteria.

Four logic types carry the actual work within those branches:

• Show/hide fields surface or suppress questions based on prior answers, keeping the form focused on what's actually relevant to each patient.
• Required-field nesting makes follow-up questions mandatory only when a parent question is answered a specific way.
• Skip logic moves a patient over entire sections when those sections don't apply to their history.
• Disqualification routing ends the form early when answers indicate a patient cannot proceed, then triggers a specific staff action instead of dropping the submission into a general queue.

That last mechanic is the most underbuilt in generic forms. Ending the form early is only useful if something happens next. A disqualification without a defined follow-up action, such as a staff review flag or a redirect to a different service, creates the same liability gap as never screening at all.

Screening Questions Specific to GLP-1 Candidates

GLP-1 screening carries a defined list of required disclosures. Patients must disclose diabetes status, heart conditions, thyroid history, pancreatitis, kidney function, eating disorders, and pregnancy status before semaglutide therapy can be safely considered.

Conditional logic maps directly onto that list:

• A "yes" to personal or family history of medullary thyroid carcinoma ends the intake immediately and triggers a disqualification flag for staff review.
• A "yes" to current diabetes medications opens a drug-interaction sub-section asking which agents, at what dose, and when the last labs were drawn.
• A "yes" to a history of pancreatitis routes the patient to a provider-review queue, bypassing self-scheduling.

Patients who clear every flag move toward booking. Patients who don't get held for clinical review are stopped from falling through into a consultation they shouldn't have.

Screening Questions Specific to TRT Candidates

TRT intake has to document more than a patient's chief complaint. All TRT candidates should be screened for contraindications before initiating therapy, and the form needs to capture symptom history, cardiovascular status, and prostate risk before a provider ever picks up the chart.

A conditional form asks about persistent fatigue, decline in muscle mass, reduced libido, erectile dysfunction, depression, sleep disturbance, and osteopenia or osteoporosis. Patients who report none of these get routed to a provider-review queue. Those who flag several move forward into deeper branches.

From there, age and cardiovascular history control which follow-up questions appear:

• Patients above a defined age threshold, typically 40, see PSA history and prostate-related questions that younger patients skip entirely.
• A "yes" to personal cardiovascular history opens a sub-section on current medications, prior cardiac events, and most recent lipid panel results.
• A "yes" to current anticoagulant use triggers a flag for provider review before scheduling proceeds.

By the time a consultation is booked, the provider already has documented symptom burden, relevant contraindication flags, and any TRT lab gaps that need filling before treatment can begin.

Screening Questions Specific to Peptide Programs

Peptide therapy intake sits in a different position than GLP-1 or TRT screening. With compounds like BPC-157, TB-500, CJC-1295, and ipamorelin, there is no single standardized contraindication list the way there is for semaglutide. Form design here relies more on clinical judgment than on a fixed protocol, which makes conditional logic harder to build but no less necessary.

Responsible practices collect:

• Current medication list, with branching for known hormone-modulating agents
• Personal or family history of hormone-sensitive cancers, which surfaces a provider-review flag in place of a hard stop
• Kidney and liver function history, given peptides' metabolic clearance pathways
• Stated goals, which shape which compounds and dosing conversations are relevant at consultation

The key structural difference from GLP-1 or TRT forms is that disqualification branches are rare. Conditional logic surfaces advisory flags instead. A "yes" to cancer history routes the submission to a provider queue with a notation, leaving the clinical decision where it belongs.

The regulatory angle matters too. Peptide compounds face ongoing FDA scrutiny, and that environment makes documented pre-screening a compliance asset. A timestamped conditional intake record is evidence the screening happened, what the patient disclosed, and how staff responded.

How Disqualification Routing and Soft-Redirect Logic Work

When a patient's answers trigger a contraindication, the form has to stop, and something useful has to come next.

Hard disqualification ends the intake and delivers a message explaining that the patient cannot be served through this program, with direction toward an appropriate care setting. Soft redirect keeps the patient inside your practice but points them toward a different service. A GLP-1 candidate with a thyroid history might get routed to nutritional counseling or a metabolic wellness consult instead.

The messaging at the endpoint carries most of the weight. A disqualification message that reads as a rejection loses the patient. One that acknowledges their goals and offers a clear next step preserves the relationship even when the original service is off the table.

• Disqualification endpoints should always specify what happens next, whether that's a staff callback, a different service link, or a referral recommendation.
• Soft redirects work best when the alternative service is genuinely relevant to the patient's stated goal, and not a mere fallback booking option.
• The form should never close without output. A patient who discloses fully and gets silence is less likely to return.

Practices that build this layer thoughtfully turn screening from a gatekeeping function into a triage function, which matters when patient acquisition costs are high.

HIPAA Compliance Requirements for Conditional Intake Forms

Before any conditional intake form goes live, the compliance layer has to be in place.

Conditional logic fields that show only relevant questions reduce unnecessary PHI exposure, and consent capture must include standalone acknowledgments for HIPAA privacy practices, financial policies, telehealth consent, and communications authorization. Bundling all of that into one checkbox does not satisfy the requirement.

The minimum checklist for any practice deploying digital intake:

• Signed Business Associate Agreement with the form vendor before a single patient record touches the system
• Encryption in transit and at rest for all submitted data
• Role-based access controls limiting who can view completed forms
• Audit logging that records who accessed a submission and when
• E-signature compliance that captures a legally valid patient authorization

Vendor selection is where practices most often cut corners. HIPAA compliance requires purpose-built tools, and consumer-grade form builders will not sign a BAA. A Google Form collecting symptom history is not a compliant intake tool regardless of how the questions are structured.

How to Test and Maintain Your Conditional Logic Forms

Form logic fails quietly. A patient answers an unusual combination of questions, a branch misfires, a required field inside a conditional section turns out to be skippable, and the submission lands in the queue missing information no one knew to check for.

A structured test plan catches this before a real patient does. Run hypothetical profiles through every branch: a GLP-1 candidate who answers "yes" to pancreatitis, a TRT candidate with cardiovascular history and anticoagulant use, a peptide inquiry with a cancer history flag. Confirm that disqualification routing fires on the right triggers, that flagged submissions reach the correct queue, and that form output maps to the right fields in the EMR without manual re-entry.

Maintenance is where most practices fall short. GLP-1 indications have shifted, TRT screening criteria have been updated, and peptide regulatory status continues to move. A form accurate at launch can drift out of alignment within a year. Set a review cadence, document the version currently live, and log what changed and when.

Front desk staff also need a pre-launch briefing. A flagged submission looks different from a clean one, and staff who have never seen a disqualification routing output will not know how to respond to it. That briefing prevents patient-facing errors on day one.

From Form Submission to Consultation: Connecting Intake to Your Scheduling Workflow

Qualified intake submissions only matter if they reach the right person before the appointment, not sitting in a generic inbox waiting to be re-typed into the EMR.

The practical difference is real. Paper-based intake burdens front-desk teams with hours of manual transcription each week, and intake errors are a recognized contributor to downstream claims problems across the industry. A digital form that feeds directly into the scheduling workflow removes that labor and the transcription errors that come with it.

When intake connects to scheduling, staff see at a glance which patients have completed intake, flagged responses reach the provider before the appointment, and submitted data populates the chart without manual re-entry. A GLP-1 candidate who disclosed pancreatitis during intake should have that flag visible on the schedule view before minute one, not surfacing mid-consultation. Conditional logic produced a cleaner submission; bidirectional EMR integration routes it to the right place automatically.

How Decoda Health Handles Intake for GLP-1, TRT, and Peptide Practices

Decoda Health generates patient intake forms on demand using AI, building each one from the treatment context instead of pulling from a static template library. Type the treatment context, and the system builds clinically relevant fields for it, whether that's a GLP-1 weight loss inquiry, a peptide consultation, or a hormone therapy intake. Fields specific to that service appear automatically, and providers can refine the output through a drag-and-drop editor without starting from scratch.

The more consequential piece is what happens after submission. Because Decoda Health is purpose-built for elective care, the intake form connects directly to scheduling, clinical charting, and payments inside the same environment. A flagged GLP-1 submission routes to a good-faith exam queue. A qualified candidate moves toward booking. Completed form data populates the chart without re-entry. Clinic partners see an average 80% reduction in check-in time when intake flows through this connected workflow, compared to paper or a disconnected tool.

Conditional logic produces better intake data, but only a connected system can act on it. A form tool stops at submission. A full operating layer routes, flags, schedules, and charts, turning a qualified response into a booked consultation with minimal staff intervention.

Final Thoughts on Screening Elective Care Patients With Conditional Intake Logic

The intake form is often the first clinical decision point your practice controls, and most generic tools weren't built to handle it well. Getting conditional logic right means your providers have the information they need before the consultation starts, and patients who don't qualify get a clear next step instead of silence. That's better for patients and better for your practice. Schedule a short intro with Decoda Health to see how it works in practice.