GLP-1 Clinic Software: Prescribing Integration Guide (2026)
CTO & Co-Founder
CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

GLP-1 clinic software is the EHR and the tools around it that a med spa, telehealth or wellness clinic uses to see patients and prescribe drugs such as semaglutide and tirzepatide. In three of the four clinic EHRs we checked, the prescriber writes the order in an e-prescribing partner that the EHR opens (the fourth, Lobbie, does not publish its engine). That partner sends the prescription to the pharmacy over the Surescripts network.
This guide is for a product lead or buyer who has to connect a GLP-1 program to these clinics' systems: a telehealth platform, a pharmacy, a lab or a patient app. It sums up our four EHR guides. It shows which e-prescribing engine each EHR uses and whether an outside app can read prescriptions. It also lists the FDA dates that changed how these drugs are compounded. It gives no medical advice. If you need a team to scope the build, see our EHR integration services. Last checked: Nov 18, 2026.
GLP-1 prescribing integration at a glance
| Question | Short answer |
|---|---|
| Where is the prescription written? | In an e-prescribing partner the EHR opens: MDToolbox for OptiMantra, and ScriptSure for Aesthetic Record and Prospyr. Lobbie does not publish its engine. |
| How does it reach the pharmacy? | Over the Surescripts network, as an NCPDP SCRIPT message. OptiMantra states its route through MDToolbox and Surescripts. |
| Can an outside app read prescriptions from the EHR? | Not through any published API in the four EHRs we checked. |
| Can an outside app write a prescription into the EHR? | No published route in any of the four. |
| What did FDA change for compounding? | It declared the tirzepatide shortage resolved on Dec 19, 2024 and the semaglutide shortage on Feb 21, 2025. In 2025 it ended its enforcement discretion for 503A and 503B compounders in 2025. |
| What does e-prescribing cost the clinic? | OptiMantra and Aesthetic Record publish eRx prices. Prospyr and Lobbie do not. |
| What is the biggest limit? | Prescription data sits with the e-prescribing partner, and the EHR APIs expose none of it. |
Which e-prescribing engine does each GLP-1 clinic EHR use?
Each of the four EHRs hands prescribing to a partner. The table sums up what each vendor publishes, from our guides, read on Nov 18, 2026.
| EHR | E-prescribing engine | Can an outside app read prescriptions? | Published eRx price |
|---|---|---|---|
| OptiMantra | MDToolbox, connected to Surescripts, including EPCS | No. OptiMantra has no general API, and its webhooks carry no medication fields. | $38 per practitioner per month, EPCS included |
| Aesthetic Record | ScriptSure, opened from the patient chart | No published route. A PDF record of each prescription is kept in the chart's Document Repository. | EPCS $505 a year or $295 for 6 months. Non-EPCS $397 a year or $235 for 6 months. |
| Prospyr | ScriptSure in the help center. The eRx page names DoseSpot with ScriptSure "rolling out" | No. Neither the REST nor the GraphQL API has a prescription field or call. History reaches Prospyr itself by webhook from ScriptSure. | Not published |
| Lobbie | Not published. Lobbie EMR lists prescribing as a feature. | No. Neither the public API nor the Partner API release notes show a prescription endpoint. | Not published |
EPCS means electronic prescribing for controlled substances. It needs extra identity checks for the prescriber.
OptiMantra
OptiMantra runs eRx through MDToolbox, which opens in a separate window. A user can pull the patient's medication history in MDToolbox and import it into OptiMantra, but no documented route lets an outside app read it. OptiMantra cannot connect to an MDToolbox account the clinic already has elsewhere. The full detail is in our OptiMantra integration guide.
Aesthetic Record
Aesthetic Record sends patient details from the chart to the ScriptSure prescription pad. Each eRx account belongs to one prescriber, who proves identity through ID.me, and a second party must approve the enrollment. ScriptSure's own site is a login page with no public partner documents. See our Aesthetic Record integration guide.
Prospyr
Prospyr has public REST and GraphQL APIs, but prescribing is in the app only. In ScriptSure, a provider picks a medication or a compound, the quantity and the pharmacy. The history then comes back into the patient profile by webhook. See our Prospyr integration guide.
Lobbie
Lobbie sells intake software and its own EMR, which it says covers prescribing. Its public Developer API covers patients, forms, PDFs and webhooks, with no prescription endpoints. See our Lobbie integration guide.
How does a GLP-1 prescription travel from the clinic EHR to the pharmacy?
The prescriber writes it in the e-prescribing partner, which sends it over Surescripts to the pharmacy as an NCPDP SCRIPT message. NCPDP SCRIPT is the message standard for US e-prescriptions.
The EHR passes the patient's details to the partner and, in some products, gets a record back. Our Surescripts integration guide covers how software joins that network, directly or through a certified partner. Our NCPDP SCRIPT guide shows the messages themselves, with XML examples.
What did FDA decide about GLP-1 shortages and compounding?
FDA declared the tirzepatide shortage resolved on Dec 19, 2024 and the semaglutide shortage resolved on Feb 21, 2025. It then gave 503A and 503B compounders a fixed period before enforcing the normal rules. All dates below come from the FDA page "FDA clarifies policies for compounders as national GLP-1 supply begins to stabilize" (content current as of Apr 1, 2026).
Under section 503A, a state-licensed pharmacy or physician compounds a drug "for an individual patient based on receipt of a prescription", in FDA's words. Section 503B covers outsourcing facilities, which have their own, separate rules and periods.
| Drug | Shortage resolved | 503A period ended | 503B period ended |
|---|---|---|---|
| Tirzepatide injection | Dec 19, 2024 (FDA first listed it as resolved on Oct 2, 2024, then re-evaluated) | Feb 18, 2025 | Mar 19, 2025 |
| Semaglutide injection | Feb 21, 2025 | Apr 22, 2025 | May 22, 2025 |
FDA states on the same page that "Compounded drugs are not approved by FDA." It also notes that section 503A of the FD&C Act "includes restrictions on compounding drugs that are essentially copies of a commercially available drug."
For a platform, these dates matter because a compounded order and an approved-drug order can go to different pharmacies. The software has to send each one where the prescriber and the clinic's pharmacy contracts say it goes. The clinic, its pharmacist and its lawyers make that decision. The software carries it out.
What is not possible in GLP-1 clinic EHR integrations today?
None of the four EHRs publishes an API route to read prescriptions, write them, or get dispense status back from the pharmacy. The table lists what each vendor leaves out.
| Need | What the four EHRs publish | The usual way round it |
|---|---|---|
| Read prescriptions in an outside app | No API route in any of the four | Work with the e-prescribing partner, or take the record from the pharmacy side |
| Send a prescription from your platform into the EHR | No route | Prescribers write it in the clinic's own eRx tool, or your platform runs its own certified eRx |
| Know when the pharmacy filled it | Not published | Ask the pharmacy for its own status feed |
| Medication history in an outside app | OptiMantra: a user imports it into the chart by hand. Others: not published | Read it in the EHR screen, or use the eRx partner's own route |
How do you plan a GLP-1 clinic software integration?
Start with where the prescription lives. Four steps cover most programs.
- List the EHRs and the eRx engine behind each. Use the table above. Check it with each clinic, since a clinic may use a different eRx setup.
- Decide what your platform needs. Patient and visit data often comes from the EHR's API or webhooks. Prescription data comes from the eRx partner or the pharmacy.
- Ask the eRx partner and the pharmacy what they share. MDToolbox, ScriptSure and DoseSpot each have their own partner terms. Ask about access, fees and the time to go live in writing.
- Keep the patient's consent and the BAA in place for each data flow. A BAA (business associate agreement) is the HIPAA contract a vendor signs before it handles patient data.
What should you ask each vendor before you sign?
Ask questions that put a date and a price on each route. These come from the gaps in the four guides.
- Which e-prescribing engine does this clinic use, and is it the same in every location?
- Can our app read prescription records, and through which route: API, webhook, file or report?
- What does the eRx partner charge a third-party app for access, and how long does approval take?
- Will the vendor sign a BAA with us?
- How does the pharmacy report fills and cancellations?
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
What is GLP-1 clinic software?
Which e-prescribing engine does OptiMantra use?
Which e-prescribing engine do Aesthetic Record and Prospyr use?
Can a telehealth platform read GLP-1 prescriptions from these EHRs?
When did FDA say the semaglutide shortage was over?
When did FDA say the tirzepatide shortage was over?
Are compounded GLP-1 drugs FDA approved?
What is the difference between 503A and 503B compounding?
How does a GLP-1 e-prescription reach the pharmacy?
Can our platform write a prescription into a clinic's EHR?


