The signal from the top has been consistent: current HHS leadership wants peptide access to move through lawful medical channels, and it has been openly skeptical of the research-use-only market that grew while those channels were closed.
The Pharmacy Compounding Advisory Committee meeting on July 23rd and 24th was the first formal step in that direction, and the committee has now made its recommendations to FDA on the seven peptides under review. Six peptides received a passing vote by the committee and are thus recommended for inclusion on the 503A Bulk List: BPC-157, KPV, TB-500, MOTS-c, Epitalon, and Semax. One peptide, emideltide (DSIP), was rejected and thus will not be recommended for inclusion on the 503A Bulk List.
Predicting enforcement is not the same thing as reading policy intent. The government moves slowly, rulemaking after a PCAC recommendation can take a year or more, and no one can say with certainty whether enforcement in the RUO space will accelerate after this meeting. But the direction is clear enough that many RUO peptide companies are starting to plan for a future where the RUO channel narrows.
The most common strategy we are seeing is a telehealth hedge: launching a peptide or GLP-1 telehealth platform that can deliver products through the compounding pathway if and when the RUO channel becomes less viable.
That instinct makes sense. It can also create serious legal exposure if it is done casually.
A telehealth business is not just an adjacent product line to an RUO business. It is governed by a different body of law, supplied through a different chain, and structured in a fundamentally different way. If the two sides are blurred, the telehealth channel may not protect the RUO business at all. It may instead give FDA evidence that existing RUO products are really being marketed as unapproved, misbranded drugs.
For RUO operators thinking about moving into telehealth peptides, the question is not only whether the hedge is smart. The question is whether the hedge is built cleanly enough to work.
The Foundational Five
Most RUO operators raise the same five issues first. These are the starting points, and they should be addressed before the structure is built.
1. Keep the Two Businesses Genuinely Separate
The RUO business and the telehealth business should be separate in every meaningful way: different entities, different operations, different books, and different compliance systems.
Most founders will want common ownership at a holding-company level, which can be workable. The safer structure is generally to place the RUO entity and the telehealth entity as sibling silos under the HoldCo, not as a parent-subsidiary structure with the RUO entity sitting above the telehealth entity.
That separation matters because the FDA looks at intended use holistically. Separate entities alone do not solve the problem if the businesses still look connected in practice. Affiliation itself can carry evidentiary weight, and FDA has cited one affiliated company’s website and marketing as evidence against another. Separation is necessary. It is not enough by itself.
2. Do Not Cross-Solicit Customers
This is the highest-risk issue on the list. RUO customers should not become the lead list for the telehealth platform, and telehealth patients should not become the lead list for the RUO business. Marketing a research chemical to a patient population is direct intended-use evidence, and it is one of the fastest ways to make an RUO product look like an unapproved drug.
That means no shared email lists, no shared CRM, no retargeting pixels across both sites, no “ask us about the clinical option” links, and no shared affiliate or influencer rosters.
This is a bright-line rule. The growth instincts that work in ecommerce can create the exact evidence regulators would want to see.
3. Build a Telehealth Structure, Not an RUO Structure
The structure that works for an ecommerce research-chemical company is not the structure that works for telehealth. Telehealth in most states runs directly into the corporate practice of medicine doctrine. A compliant build typically requires a professional entity that owns the clinical relationship and a management services organization that handles non-clinical services. Those entities are usually tied together through a management services agreement with a fair-market-value fee.
The point is simple: the RUO company cannot just bolt on a medical channel and assume the old structure works. Telehealth needs its own legal architecture. For a deeper look at the structuring decision, read our guide on White-Label vs. PC/MSO, where we break down the choice between using a turnkey medical network and building your own MSO/PC structure. We also compare the build-your-own MSO model against an aggregator model in Telehealth MSO vs. OpenLoop.
4. Learn the New Body of Law
RUO compliance and telehealth compliance are not the same discipline.
RUO compliance focuses on FDCA intended-use rules, FTC substantiation, HazCom and SDS obligations, and Prop 65. Telehealth compliance involves corporate practice of medicine statutes, state telehealth practice standards, prescribing and supervision rules, fee-splitting and anti-kickback law, and the FDCA framework for compounded drugs.
There is some overlap, but not enough to treat the two models as interchangeable. A team that understands RUO compliance does not automatically understand telehealth compliance, and assuming otherwise is one of the first ways a medical channel can go wrong.
5. Rebuild the Supply Chain From Scratch
The RUO supply chain and the telehealth supply chain are fundamentally different. RUO products often come from an unregulated chain, frequently sourced overseas, with no prescription involved. Telehealth products must come from a licensed 503A compounding pharmacy and be dispensed pursuant to a valid patient-specific prescription.
There is another important consequence: the telehealth menu will usually be much narrower than the RUO catalog. A 503A pharmacy can only compound from the 503A bulks list, a USP monograph, or the components of an approved drug. That means many peptides currently sold as RUO products may not be lawfully prescribed and compounded at all. This is why the PCAC outcome matters so directly. Before building the telehealth platform, ooperators should map the intended formulary against the current bulks list and confirm which products are actually viable in a medical channel.
The Longer List: Where the Real Work Begins
The five points above create the framework. The details below are where avoidable mistakes tend to appear once the structure is already moving.
6. Use Separate Brands and Separate Websites
The RUO company and the telehealth platform should not share the same brand, domain, social accounts, or “our story.” They should not cross-link to each other or create a consumer-facing impression that one is simply the medical version of the other. A confusingly similar brand can undercut the separation strategy and become affiliation evidence.
7. Separate Personnel and Customer Service
The two businesses should not share staff who touch product or patient decisions. RUO customer service should not answer dosing questions, injection questions, or clinical-use questions. Those answers become intended-use evidence. On the telehealth side, clinical questions should be routed to licensed clinicians. If back-office functions are genuinely shared, the arrangement should be documented through an arm’s-length shared-services agreement instead of being left informal.
8. Separate Payment Processing and Banking
RUO is a high-risk merchant category with its own processor relationships. Telehealth should have separate merchant accounts, separate bank accounts, and separate books.
Commingled processing can invite account shutdowns, misrepresentation claims on processor applications, and veil-piercing arguments from FDA or future plaintiffs. The separation needs to be financial, not just cosmetic.
9. Treat Health Data as a Separate Universe
The telehealth business handles protected health information. That means it needs business associate agreements, a compliant technology stack, and attention to the FTC Health Breach Notification Rule and state laws such as Washington’s My Health My Data Act.
The RUO business should not touch health data at all. A shared email platform or shared database across the RUO and telehealth businesses can quickly become a privacy problem.
10. Get the CPOM and MSO/PC Build Right
The MSO/PC structure deserves special attention. A compliant model may involve a friendly professional corporation, or a master-PC structure where a state makes foreign registration unavailable. The MSO should charge a fair-market-value management fee, and the structure should be reviewed state by state. Physicians must retain independence over clinical protocols and formulary decisions. If the MSO appears to control the clinical side, the structure may not hold.
11. Map Prescriber Licensure and Visit Rules
A telehealth platform can only serve patients in states where its clinicians are properly licensed and where the visit model is permitted. Operators need to review multi-state clinician licensure, collaborating-physician requirements for nurse practitioners and physician assistants, and state rules around asynchronous versus synchronous encounters.
An async-only intake flow is not lawful everywhere. The footprint is defined by where the clinicians are licensed and what each state permits, not by where the website can load.
12. Flip the Marketing Claims Regime
RUO marketing must avoid therapeutic claims. Telehealth marketing can discuss therapeutic use, but it creates a different set of risks. For GLP-1 and peptide telehealth, marketing needs to avoid the warning-letter patterns FDA has already identified: no “generic” or “same as the brand” claims, no implication of FDA approval, and no private-label misbranding.
The team that learned how to market RUO products should not simply be turned loose on the telehealth site. The rules are different, and the team needs to be retrained.
13. Rebuild Referral and Marketing Economics
RUO affiliate and commission models should not be copied into telehealth. Percentage-based marketing arrangements on the medical side can implicate state mini-anti-kickback statutes, the Florida Patient Brokering Act, and potentially EKRA depending on how payments are structured. Referral-partner arrangements need to be rebuilt for the telehealth model rather than ported over from ecommerce.
14. Plan for LegitScript and Ad-Platform Gatekeeping
Google and Meta effectively require LegitScript certification to advertise telehealth. That review looks at corporate structure, supply chain, and marketing claims. A visible RUO affiliation can harm the application. This is another reason the separation between the RUO business and telehealth platform needs to be real, not just a branding exercise.
15. Separate Fulfillment and Inventory
Prescriptions should ship from the pharmacy directly to the patient. RUO products should ship from the company’s warehouse or third-party logistics provider. Inventory should never be commingled. Operators also need to confirm that the dispensing pharmacy’s multi-state shipping licensure covers the intended patient footprint.
16. Insure Each Business for What It Actually Is
RUO product-liability coverage does not cover the practice of medicine. The professional corporation needs medical malpractice coverage. The MSO needs its own errors-and-omissions and cyber coverage. Insurance carriers will ask about the corporate family, and the separation story needs to hold up in underwriting as well as on the org chart.
17. Comply With Subscription and Consumer-Protection Law
Telehealth weight-loss and longevity programs are often subscription-based. That triggers state automatic-renewal statutes, FTC negative-option rules, and refund and cancellation obligations.
Those obligations do not exist in the same way for ordinary RUO ecommerce. Telehealth operators need to build them into the model from the beginning.
18. Hold IP in the Right Silo
Each side’s trademarks should sit in its own IP entity. Cross-licensing the same mark between the RUO and telehealth businesses can recreate the affiliation the structure is trying to avoid.
IP ownership should support separation, not blur it.
19. Watch How You Describe the Hedge Internally
Internal language matters. Emails, pitch decks, and board materials that describe the telehealth platform as a “hedge for the RUO business” or a “migration path for our RUO customers” are discoverable. They are also the kind of intended-use and affiliation evidence a regulator would want. The team should be trained to describe the two businesses as what they legally need to be: independent operations.
20. Preserve Exit and Financing Optionality
Acquirers and lenders in the telehealth space will diligence for RUO taint. Clean separation preserves the ability to sell or finance the medical business without the research-chemical business affecting the process, and vice versa. If the businesses are blurred, the hedge may create a financing or exit problem instead of solving one.
21. Run Two Separate Compliance Calendars
The RUO business and the telehealth business need different compliance calendars. The RUO side must monitor HazCom and SDS obligations, Prop 65, and FTC substantiation. The telehealth side must track pharmacy-board rules, telehealth practice standards, the evolving 503A bulks list, and potential action by the HHS Secretary under 503A(c). Each silo needs its own compliance owner and monitoring cadence because the regulatory ground is moving under both businesses, and not always in the same direction.
Where This Leaves RUO Operators
Building a telehealth hedge is rational. Federal policy appears to be moving toward lawful medical channels, and for some RUO operators, a compliant medical platform may eventually become the primary business.
But the value of the hedge depends entirely on building it as a separate, independent business. If the telehealth platform starts to look like a rebranded distribution arm of the RUO company, it stops protecting the business and starts creating a larger problem.
The three biggest tripwires are cross-solicitation, the marketing-claims flip, and internal characterization of the hedge. Each one runs against the natural growth instincts of an ecommerce team, which is why these are the mistakes first-time medical channels are most likely to make in the first 90 days.
LumaLex Law advises RUO peptide companies, 503A and 503B compounding relationships, and telehealth platforms at the intersection of FDA enforcement, corporate structure, and payment processing. If you are considering a telehealth hedge, we can help build the structure correctly from the start. Contact us today to schedule a consultation!
FAQ
Can an RUO peptide company start a telehealth business?
Yes, but the two businesses should be structured and operated separately. Telehealth is governed by a different body of law and requires a different supply chain, corporate structure, compliance framework, and marketing approach.
Why should RUO and telehealth operations be separated?
Separation helps reduce intended-use, affiliation, privacy, payment-processing, and corporate-structure risk. Separate entities alone are not enough if the businesses share branding, customers, marketing systems, data, payment processing, or internal messaging.
Can RUO customers be marketed to for telehealth services?
This is one of the highest-risk areas. RUO customers should not be treated as a lead list for the telehealth business, and telehealth patients should not be marketed RUO products.
Can the same peptide catalog be used in telehealth?
No. The telehealth menu will usually be narrower because a 503A pharmacy can only compound from the 503A bulks list, a USP monograph, or the components of an approved drug.
What is the biggest mistake RUO companies make when launching telehealth?
The biggest mistake is treating telehealth as an extension of the RUO business instead of a separate medical channel with its own structure, supply chain, marketing rules, data obligations, and compliance calendar.
Disclaimer: This article is provided for general informational purposes only and does not constitute legal advice or create an attorney-client relationship. Telehealth and healthcare rules vary by state and change frequently. Consult qualified counsel about your specific facts.
