CURRENT STAGE
Provider outcome recorded
The licensed provider completes the review, signs the documentation, and independently decides whether to prescribe.
Included pharmacy automations
Connect Meds is the name we use for the configured pharmacy automations shared across Connect Telehealth and Connect Scripts. It is not another platform, subscription, or login.
Connect Telehealth runs the branded patient and CRM workflow. Providers review and prescribe in Connect Scripts. Surescripts carries the configured e-prescription. Independent pharmacies review and, if accepted, dispense and fulfill. The included automations keep those operational handoffs connected.
CURRENT STAGE
The licensed provider completes the review, signs the documentation, and independently decides whether to prescribe.
BUILT FOR CONNECTED PHARMACY OPERATIONS
Included automation patterns
The applicable patterns are configured across Connect Telehealth and Connect Scripts around the pharmacy, program, permissions, and source data that actually exist.
Start the configured pharmacy path only after Connect Scripts records a provider-authorized prescription.
PRESCRIBED · THEN ROUTEMove the operational workflow toward the configured independent-pharmacy relationship for the approved program.
THE RIGHT HANDOFF · CONFIGUREDBring supported pharmacy events back into authorized operational views so teams can see what moved and what needs attention.
SENT · REVIEWING · NEXT STEPTurn supported events into the right authorized team or patient-facing update without exposing clinical details in public analytics.
RIGHT MESSAGE · RIGHT CHANNELCreate a clear next action when a supported workflow needs attention, clarification, reconciliation, or human follow-up.
AUTOMATE · THEN ESCALATEBring available pharmacy and fulfillment context into approved views so teams can understand movement and bottlenecks.
SUPPORTED CONTEXT · VISIBLEPrescription pathways
Connect Scripts handles provider review and the configured Surescripts transmission. The included Connect Meds automations coordinate what happens around the pharmacy connection and return supported operational context to the connected workflow.
NON-CONTROLLED PRESCRIPTIONS
SUPPORTED COMPOUNDED PRESCRIPTIONS
CONTROLLED-SUBSTANCE PRESCRIPTIONS
Compounded and controlled are not opposite categories. If a compounded prescription contains a controlled substance, it uses the controlled-substance path and requires an enabled EPCS workflow.
Connected status
Where configured, supported pharmacy events can return to connected systems so founders, operators, and developers can see whether the workflow is moving or needs attention.
Exact statuses, timing, and connection methods depend on the pharmacy, systems, agreements, and implementation scope.
Clear ownership
The handoff works because the responsibilities stay clear.
Clinical review, documentation, treatment decision, and prescription authorization based on independent professional judgment.
Provider review tools and configured transmission of the authorized prescription through the Surescripts network.
Configured CRM tasks, authorized updates, patient-facing workflow steps, and operational visibility around the pharmacy handoff.
Prescription acceptance, pharmacy review, pricing, dispensing or compounding, fulfillment, shipping, and medication-related patient communication.
Approved programs, payment context, branded operations, and authorized non-clinical updates through its connected patient experience.
Simple above. Solid underneath.
These automations run inside Connect Telehealth and Connect Scripts, with role-aware access, organization-scoped data, authenticated connections, and activity history. The CRM is designed to support HIPAA-compliant workflows; eligible customers can put a BAA in place before using PHI.
See how security works ↗Straight answers
Have a specific pharmacy setup in mind?
Talk it through with us ↗Connect Meds is the name for the configured pharmacy automations included across Connect Telehealth and Connect Scripts. It describes how the connected system coordinates a prescription handoff, compatible pharmacy relationships, supported operational status context, and authorized updates after an independent provider prescribes.
No. Connect Meds is not a standalone platform, separate subscription, or additional login. The applicable automations are configured within the connected Connect Telehealth and Connect Scripts implementation.
No. The pharmacy automations are used only when an independent provider issues a prescription and the configured program requires a pharmacy handoff. A prescription is never guaranteed.
The prescribing workflow begins in Connect Scripts. In approved configurations, an authorized prescriber can transmit a prescription through the Surescripts network. The included automations coordinate the connected pharmacy workflow around that handoff.
Approved configurations may support non-controlled prescriptions, structured compound information, and controlled-substance prescriptions through an EPCS-enabled Surescripts workflow. Support is configuration-specific, and prescriber, application, pharmacy, jurisdictional, and other legal requirements apply.
Potentially. An existing independent pharmacy or an available pharmacy option can be evaluated during implementation. Compatibility depends on the program, jurisdiction, medication type, pharmacy capabilities, contracts, technical connection, and required authorizations.
Where supported, the configured automations can coordinate authorized prescription and fulfillment context from connected systems. The available statuses, timing, and source depend on the implementation and do not guarantee pharmacy acceptance, dispensing, shipping, or delivery.
Independent licensed pharmacies are responsible for prescription acceptance, pharmacy review, dispensing, fulfillment, shipping, delivery, and pharmacy-patient communications. The Connect system and its included automations do not prescribe, dispense, or ship medication.
Authorized operational updates can be sent through configured channels when the necessary source data, permissions, and communication consents are in place. The exact messages and sender responsibilities are defined for each implementation.
Bring us the pharmacy workflow
Show us your programs, prescription paths, pharmacy relationships, systems, and status needs. We’ll map the cleanest practical connection.
Ready to start building? Register your health brand