BPC-157, Sermorelin, NAD+: Managing Multi-Protocol Patients in One System

The Multi-Protocol Challenge: Patients on 2–4 Compounds Simultaneously

The peptide therapy patient of 2026 is not a single-compound patient. A growing segment of the population presenting to longevity and performance clinics arrives already managing multiple goals at once: tissue repair from a recent surgery, declining growth hormone levels, metabolic dysfunction, and accelerating cellular aging. Their optimal clinical protocol is not one compound — it is a stack.

A representative patient profile looks like this: BPC-157 for post-surgery gut healing and tissue regeneration, Sermorelin to stimulate endogenous GH release and improve body composition, Semaglutide for metabolic optimization and weight management, and NAD+ infusions for mitochondrial support and cognitive clarity. Each compound is clinically justified. Together, they create a coordination problem that most clinic software was never designed to handle.

The operational burden becomes clear immediately. Each compound has its own:

• Dosing schedule (daily, three-times-weekly, weekly titration, induction series)
• Cycling pattern (continuous, 4-weeks-on/2-weeks-off, 12-week cycle with rest period)
• Required laboratory monitoring (IGF-1, GLP-1 panel, metabolic markers, inflammatory panel)
• Compounding pharmacy — not every pharmacy compounds every compound, and state licensing adds further constraints
• Prescription expiry timeline and refill count
• Contraindications and interaction flags relative to the other compounds in the stack

When clinics try to manage this complexity across separate EMR entries, spreadsheets, and disconnected pharmacy portals, things go wrong in predictable ways: a patient continues BPC-157 past their 4-week on-cycle window because no one flagged it; Sermorelin labs get pulled at the wrong time in the cycle; Semaglutide dose titration gets stalled because the system doesn't prompt the next step; NAD+ infusion scheduling falls to a manual calendar. The result is suboptimal clinical outcomes, staff overload, and — most critically — liability exposure from undocumented protocol states.

The rest of this guide breaks down how that software must be structured — covering conflict detection, cycling management, lab coordination, prescription routing, and the patient-facing experience — along with the revenue opportunities that emerge when the data is organized correctly. For an overview of the full technology platform required to run these operations, see our complete peptide clinic technology stack guide.

Protocol Conflict Detection: Drug Interactions, Timing Conflicts, Dosage Adjustments

The first function a multi-protocol system must perform is conflict detection — not as an afterthought but as a gatekeeping step that runs every time a new protocol is added to an existing patient record.

Three Categories of Conflicts

Category 1: Pharmacodynamic interactions. These are cases where two compounds affect the same biological pathway in ways that may amplify or counteract each other. The most clinically significant example in peptide stacking is the combination of a GHRH analog (Sermorelin, CJC-1295) with a GHRP (Ipamorelin, Hexarelin). Both act on the GH axis but through distinct receptor mechanisms — combined, they have a synergistic effect on GH pulse amplitude that is intentional and desirable when dosed correctly, but dangerous if the dosing logic for each is set up independently without acknowledging the combination. A system that treats these as independent protocols will miss this calculation entirely.

Category 2: Timing conflicts. Many peptides have time-of-day sensitivity that, when two protocols share a time window, requires scheduling arbitration. Sermorelin must be administered at bedtime to leverage the nocturnal GH pulse — this window cannot be moved. BPC-157, often dosed twice daily, nominally has a "before bed" dose that should not be co-injected with Sermorelin in the same syringe (different stability profiles and reconstitution requirements), though the timing can be adjacent. The system needs to know these rules and flag when a patient's combined schedule creates an unresolvable collision.

Category 3: Dosage adjustment requirements. Some combinations require dosage reduction in one or both compounds when stacked. Clinicians adding Ipamorelin to an existing Sermorelin protocol, for example, often reduce the Sermorelin dose to account for the combined GH stimulus. A system that tracks these protocols independently cannot prompt this reduction — only a unified multi-protocol record can surface the flag at the moment the second prescription is written.

Interaction Rule Maintenance

The interaction rule library must be maintained at the clinic level and updated as clinical evidence evolves. Unlike pharmaceutical drug databases (which are updated centrally and licensed), peptide interaction data is largely derived from clinical observation, compounding pharmacy experience, and emerging research. Clinics should treat their interaction rule set as a living clinical document, assigning a designated reviewer to update it quarterly.

Cycling Schedules: How Different Peptides Have Different Cycling Requirements

One of the most commonly mismanaged aspects of multi-protocol peptide therapy is cycling — specifically, the failure to track each compound's cycle independently and the failure to coordinate cycle timing across compounds when coordination matters clinically.

BPC-157: Cyclical or Continuous Depending on Indication

BPC-157 protocols vary more than any other common peptide. For acute tissue repair (post-surgical, injury recovery), a short intensive cycle of 4–6 weeks is standard, after which patients typically pause and reassess. For gut healing and systemic anti-inflammatory purposes, some clinicians run BPC-157 continuously at lower doses (200–250 mcg daily) for 12+ weeks without a structured break. The system needs to capture which indication is driving the prescription and apply the correct cycling logic accordingly — these are not interchangeable.

Sermorelin and GHRH Analogs: 12-Week Cycles with Rest Periods

Sermorelin, CJC-1295, and similar GHRH analogs are typically prescribed in 12-week continuous cycles followed by a 4-to-6 week rest period. The clinical rationale is receptor sensitivity maintenance — continuous GHRH stimulation without a break can lead to diminished pituitary responsiveness over time. The system must track not just when the cycle started but when the rest period begins and ends, sending reminders to both the clinical team (to schedule the post-rest IGF-1 check) and the patient (so the pause does not feel like a treatment failure).

Semaglutide and GLP-1 Analogs: Continuous with Dose Titration Milestones

Semaglutide and other GLP-1 receptor agonists do not follow traditional peptide cycling patterns. They are administered continuously, with clinical checkpoints at weeks 4, 8, 12, and 24 to assess tolerability and titrate dose upward. The system must track the current dose tier (not just "active" or "paused") and automatically schedule the next titration assessment based on the titration protocol the prescriber selected at initiation. Missing a titration window — even by one or two weeks — can result in patients under-dosed for extended periods, slowing clinical response and driving dropout.

NAD+: Induction Series Followed by Maintenance

NAD+ IV infusion therapy has a distinct two-phase structure: an induction series (typically 4–10 consecutive daily or every-other-day infusions) followed by monthly or bi-monthly maintenance infusions. The system must represent both phases and transition automatically from induction to maintenance upon series completion. The induction phase also requires the most intensive clinical monitoring — some patients experience significant nausea, chest tightness, or blood pressure fluctuation during rapid NAD+ infusion — and the system should prompt post-infusion check-in protocols during this window.

Protocol Matrix

The following matrix covers the four most commonly combined compounds in longevity and performance peptide clinics. It is intended as a clinical reference for building protocol templates within your management software — not as prescribing guidance.

Patient Timeline Visualization

Understanding how overlapping protocols interact across a 12-week window requires a visual representation. The following timeline shows a representative multi-protocol patient across 12 weeks, with each compound's active periods, rest windows, and key clinical milestones marked.

The timeline above illustrates several important operational realities. First, Sermorelin runs continuously across all 12 weeks — it never pauses in this cycle. BPC-157 runs a 4-on/2-off pattern, with the rest windows aligning to weeks 5–6 and weeks 11–12. Semaglutide dose-escalates at weeks 5 and 9 — the system must auto-schedule the titration assessment consult the week before each escalation point. NAD+ runs as an induction series in weeks 1–4 (4 consecutive infusions), then returns to a monthly maintenance infusion at week 9.

A key insight from this timeline: the weeks 5–6 window is a natural clinical checkpoint. BPC-157 is on its rest period, the first Semaglutide titration has just occurred, and the clinical team should be scheduling the 45-day assessment visit. A well-configured multi-protocol system automatically generates this appointment suggestion based on the intersection of protocol states — not from a generic recall schedule.

Lab Panel Coordination: Which Labs for Which Protocols, Shared vs. Protocol-Specific

Lab management is where multi-protocol complexity most visibly breaks down in practice. The failure mode is not ordering too many labs — it is ordering the wrong labs at the wrong time for each protocol, or ordering labs that are required by multiple protocols and billing for them twice.

The Shared Baseline Panel

Every multi-protocol patient should have a shared baseline panel that serves as the clinical foundation regardless of which compounds they are taking. This panel includes CBC with differential, comprehensive metabolic panel (CMP), fasting lipid panel, fasting glucose, HbA1c, and a standard hormonal baseline (total testosterone, free testosterone, estradiol, DHEA-S, cortisol AM). This panel is ordered once per 90-day assessment cycle and maps to all protocols simultaneously.

Protocol-Specific Add-Ons

Each protocol then adds its own required markers on top of the shared baseline. The system should present these as a single consolidated order — not four separate lab orders that may result in duplicate draws — with the compound-to-lab mapping visible in the ordering interface so clinicians can see why each marker is being ordered. For a complete guide to how automated lab workflows integrate with clinic software, see our article on lab integration for peptide clinics:

• BPC-157 addition: C-reactive protein (CRP), ESR (if inflammatory indication), H. pylori antibody (if gut healing indication), calprotectin (if IBD-adjacent)
• Sermorelin addition: IGF-1 (critical — must be drawn 12 hours after last dose, not on injection day), IGFBP-3, fasting insulin
• Semaglutide addition: Amylase, lipase, TSH, Free T4, urinary microalbumin (quarterly after 6 months), complete urinalysis
• NAD+ addition: Metabolic organic acids (first-morning urine), B12, folate, plasma methylmalonic acid at induction; repeat organic acids at 90 days

Cycle-Aware Lab Timing

The most operationally critical aspect of lab coordination is timing. IGF-1 must be drawn at a specific point in the Sermorelin cycle — ideally 4–6 weeks into the on-cycle and timed relative to the last injection. Semaglutide labs should be ordered at week 12 to coincide with the first major titration decision. NAD+ organic acids panels are most informative at the end of the induction series.

A properly configured multi-protocol system tracks each protocol's current week and automatically generates lab orders with the correct timing window, sending both a clinician prompt and a patient notification (with prep instructions specific to each test — fasting requirements, injection timing guidance) when the draw window opens.

Prescription Management: Multiple Active Rx Per Patient, Different Pharmacies Per Compound

A patient on all four protocols in our example may have prescriptions at three different compounding pharmacies. BPC-157 and Sermorelin may come from a licensed peptide compounding pharmacy with 503A status. Semaglutide, now requiring a 503B outsourcing facility following recent FDA guidance on GLP-1 compounding, must come from an FDA-registered 503B pharmacy. NAD+ IV bags require a pharmacy with a USP 797-compliant IV clean room — a separate certification that many peptide pharmacies do not hold.

Pharmacy Routing Rules

The system must encode pharmacy routing logic at the compound level, not the patient level. When a new prescription is generated for a patient, the system should automatically select the correct pharmacy from the clinic's approved vendor list based on which compound is being prescribed — not require the prescriber or staff to remember which pharmacy handles which compound. This routing rule should also enforce state licensing: if a patient is in a state where a given pharmacy is not licensed to ship, the system should surface the next-best option and flag the conflict before the Rx is transmitted.

Unified Prescription Status View

Despite prescriptions routing to multiple pharmacies, the clinical team needs a single view of all active prescriptions for each patient. This unified Rx dashboard should show, for each compound:

• Current prescription status (pending, transmitted, filled, shipped, delivered, expired)
• Refills remaining and the number of days until the next refill window opens
• Pharmacy name and order confirmation number
• Expiry date — with a 14-day advance warning alert
• Last fill date and projected next fill need based on dose and quantity

When a prescription is approaching expiry and requires clinical re-evaluation before renewal, the system should generate a chart review task assigned to the supervising prescriber — not silently let the prescription lapse and leave the patient without medication.

Multi-Prescriber Coordination

In many clinics, different compounds in a patient's stack may be managed by different members of the clinical team — a supervising physician for Semaglutide and an NP for the peptide protocols. The system must support multi-prescriber attribution per patient, track which provider owns each protocol, and route renewal alerts and lab flags to the correct prescriber rather than a generic inbox.

Patient-Facing Dashboard: All Active Protocols, Next Injection Dates, Lab Due Dates

The patient experience in a multi-protocol program determines adherence. A patient receiving four different compounds, each with different injection schedules, cycling windows, and lab requirements, cannot reliably self-manage from a treatment summary PDF. They need a live dashboard that tells them, at any given moment, exactly what to inject today, when their next lab is due, and what is happening with each active protocol.

The following represents what an effective multi-protocol patient dashboard surfaces:

This dashboard communicates three things that patients consistently say they need: what to do right now, what is coming next, and confirmation that everything is on track. The emotional component is important — patients on multi-protocol programs often feel anxious about managing the complexity correctly. A clear, real-time status view reduces anxiety-driven support calls and improves adherence because patients feel informed rather than confused.

The dashboard should be accessible via a mobile-responsive web portal and, ideally, via SMS summary for patients who don't regularly check app interfaces. A weekly Sunday evening summary message — "This week: BPC-157 AM and PM daily, Sermorelin nightly, Semaglutide on Tuesday. Your IGF-1 lab window opens Thursday." — reduces no-shows and missed doses significantly.

Revenue Optimization: Protocol Bundling, Upgrade Paths, Cross-Sell Opportunities

A well-structured multi-protocol system is not just a clinical operations tool — it is the foundation for a significantly higher revenue-per-patient model. The data visibility that comes from tracking patients across multiple protocols creates natural, clinically appropriate opportunities to expand care — but only if the system is designed to surface them.

Protocol Bundling

Bundling two or more protocols into a named program (rather than selling individual compounds) changes the patient's mental model of the engagement. A "Metabolic Optimization Program" that includes Semaglutide, a structured nutrition consultation, quarterly labs, and a monthly provider check-in commands a significantly higher monthly subscription price than Semaglutide prescribed à la carte. When NAD+ is added as the "Cellular Performance Add-On," the bundle economics become compelling for patients who are already invested in the base program.

The system should support bundle-level billing — a single subscription line item that covers all included protocols — rather than requiring patients to reconcile multiple separate charges each month. For a detailed look at how to configure recurring billing models and Rx-gated renewals for multi-protocol programs, see our guide to subscription billing for peptide therapy programs.

Upgrade Paths Triggered by Clinical Data

The most effective upgrade prompts are clinically grounded, not sales-driven. When a patient at week 8 of Sermorelin shows IGF-1 that has moved from baseline but remains below optimal range, the system should surface a provider note suggesting evaluation for a GHRP stack addition (Ipamorelin) — and prompt scheduling a brief consult to discuss. This is not upselling; it is responsive clinical care that also drives revenue.

Other common data-triggered upgrade opportunities:

• Patient on Semaglutide for 12 weeks with good metabolic response — prompt BPC-157 evaluation for gut microbiome support during GLP-1 treatment
• Patient on Sermorelin approaching 12-week cycle rest — prompt NAD+ induction series during the off-period to leverage the rest window productively
• Patient on BPC-157 acute protocol completing recovery — prompt transition to a longevity maintenance stack (low-dose BPC-157 + NAD+ quarterly maintenance)

Cross-Sell Opportunities from Lab Results

Lab results create the highest-converting cross-sell moments because they are grounded in objective clinical data. A patient whose 90-day labs show elevated inflammatory markers despite BPC-157 therapy is a clear candidate for a provider conversation about NAD+ addition. A patient whose IGF-1 remains low after 12 weeks of Sermorelin is a candidate for a GHRH/GHRP combination discussion. These conversations should be system-prompted at the time of lab review — not left to the provider to remember from memory.

Common Mistakes Clinics Make Managing Multi-Protocol Patients

• Treating each protocol as a separate patient record

  The most fundamental error. When BPC-157 and Sermorelin live in separate chart entries — or worse, separate patient profiles across systems — the clinical team loses visibility into the combined protocol state. Interactions go undetected, lab timing becomes protocol-specific rather than patient-coordinated, and the patient experience fragments into disconnected communications from different staff members about different compounds.

• Failing to track cycle end dates in real time

  A protocol with a 4-week on-cycle must have its end date tracked to the day. Without automated cycle tracking, patients continue protocols past their recommended rest window because no one flagged the end date. Staff often discover this only when a patient mentions they've been on their "break" compound for two months straight — at which point receptor desensitization may already be reducing efficacy.

• Ordering labs without accounting for cycle timing

  An IGF-1 drawn on the day of a Sermorelin injection will reflect the acute GH pulse, not the patient's baseline functional GH production. A metabolic panel drawn two weeks into a Semaglutide titration will show transient changes that don't reflect steady-state response. Multi-protocol labs must be cycle-aware — drawn at the correct point in each protocol's timeline — and the system must enforce this rather than relying on clinician memory.

• Routing all prescriptions to a single pharmacy

  Many clinics have a single preferred compounding pharmacy and route every prescription there by default. This creates compliance risk — especially for Semaglutide (requires 503B facility) and NAD+ IV (requires USP 797-compliant IV room) — and may mean patients in certain states cannot receive their medication from that pharmacy at all. Compound-specific pharmacy routing is a compliance requirement, not a preference.

• Missing protocol expansion opportunities at lab review

  The 90-day lab review is the highest-value clinical touchpoint in a patient's treatment cycle. Most clinics use it to confirm that existing protocols are working and schedule the next refill. Few use it systematically to evaluate whether the patient's current clinical picture warrants adding or adjusting a protocol. Without system prompts tied to lab values, these opportunities are missed in the moment and the patient doesn't hear about them until a future appointment they may not schedule.

• Sending generic communications instead of protocol-specific guidance

  A patient on four compounds should never receive a generic "time for your refill" text. Every patient communication — refill reminder, lab request, cycle transition notification, titration prompt — should name the specific compound, state the clinical reason, and tell the patient exactly what action to take. Generic communications increase confusion, drive inbound support calls, and signal to patients that the clinic doesn't actually know what's going on with their care.

What Good Multi-Protocol Management Looks Like

The operational picture of a well-run multi-protocol program has specific, measurable characteristics. Protocol end dates are tracked to the day and surfaced in the clinical team's daily task queue, not buried in chart notes. Lab orders are generated automatically with correct timing windows and consolidated into a single draw request. Prescriptions route to the correct pharmacy for each compound without staff intervention. The patient dashboard updates in real time as protocols transition between phases. And the 90-day review generates a structured assessment that includes protocol expansion flags alongside refill decisions.

The clinical team's role in this model is decision-making, not coordination. Software handles the coordination — the tracking, the routing, the reminders, the consolidation. Clinicians spend their time on the judgment calls: is this patient ready to add Ipamorelin? Is the BPC-157 rest period correctly timed given the injury healing progress? Should we extend the Semaglutide titration window given the GI side effect profile?

That is the shift that multi-protocol peptide management software enables — from coordination-heavy clinical operations to judgment-focused clinical care. The clinics that build this infrastructure first will deliver better outcomes, retain patients longer, and generate significantly higher revenue per patient than those still managing multi-protocol complexity on spreadsheets and sticky notes.