What a peptide clinic actually needs from its software

What's happening

A peptide is a small molecule built from a short chain of amino acids, the same building blocks that make up proteins. Your body produces thousands of them to carry instructions between cells: insulin is one, and so are many hormones. Some synthetic peptides are approved drugs you've heard of, like Ozempic. Many others have never been through FDA approval but are widely used for recovery, metabolism, and healthy aging.

This spring, FDA cleared the way for licensed pharmacies to make more of those unapproved peptides again, and in July an FDA advisory panel recommended six of them for the official list. A final rule is expected early next year. In the same months, FDA sent more than 55 warning letters to companies selling these drugs with misleading claims. So the market is opening up and being audited on day one.

What a peptide business is

A website where a customer fills out a health form, a licensed clinician reviews it, and a compounding pharmacy (a pharmacy that mixes a drug to order for one named patient) makes it and ships it home. The customer pays cash; insurance isn't involved. Most visits are asynchronous: no video call, just a clinician reviewing the form.

This is personalized medicine in practice. The premise is that a mass-produced drug at a fixed dose doesn't fit everyone, and a clinician should be able to tailor the compound and the dose to one person's physiology and symptoms.

Why it's four companies, not one

The brand can't simply employ the doctors. Most states forbid anyone who isn't a physician from owning or controlling a medical practice, so the clinicians work in a separate physician-owned group. The pharmacy is a third company, often in another state. The lab that runs the blood work is a fourth.

One patient's record is split across four legal entities. Each is bound by HIPAA, the federal health-privacy law, and each needs a signed agreement with the others before any data moves. This is the part that catches first-time health builders.

What the software has to do

1. Track what's legal. Store which peptides can be compounded, in which states, as of which date. The answer changes every few months, and some states ban what others allow.
2. Route by state. Match the patient's location to a clinician licensed there and a pharmacy licensed to ship there.
3. Capture real consent. The form must name the drug, the pharmacy and its license, the batch number, and say plainly the drug is not FDA-approved. Keep every version a patient signed.
4. Order labs and explain doses. Blood work before starting and at intervals, plus a written reason for every dose change. Medical boards discipline clinicians who skip this.
5. Prove a person reviewed it. Show a named clinician looked at each order and could have declined.
6. Log side effects. Make reporting a bad reaction to FDA a button in the workflow, not something someone remembers to do.

What you can buy off the shelf

Scheduling, payments, the storefront, and marketing tools. They all live inside one company and are ordinary software. Don't spend your compliance effort there.

Where 1health fits

Everything on the list above is patient data crossing between four companies. That is what 1health is built for: a shared patient record, consent that travels with it, lab ordering and results, and the SOC 2 Type II & HIPAA agreements already handled. Start at the developer portal.

---

Sources

• FDA, Federal Register notice removing twelve peptide substances from Category 2 (April 16, 2026; effective April 23, 2026)
• FDA Pharmacy Compounding Advisory Committee meeting outcome (July 23–24, 2026)
• FDA press releases on warning letters to telehealth companies (March 3 and week of June 15, 2026)
• Alabama Board of Medical Examiners notice on non-FDA-approved peptides (May 26, 2026)