Integrations — Prescription telemedicine

|on LastStop OS

Contents PDF All PDFs

SeeMyVitals12 / 47

LastStop · the framework

Pillar · the framework

Integrations 1 · Bring your own EHR

For example, Charm Health.

Your clinicians keep charting where they already chart.

For a practice with its own clinicians: the chart is created in Charm Health from the intake, your clinician reviews, and the encounter syncs back.
Only an approved prescription moves on to the pharmacy.
Charm Health publishes REST and FHIR R4 APIs; the LastStop connector is planned.
Simulated in this demo. Nothing is sent to Charm Health.

Setup A: your own cliniciansChart made from the intakeDemo connection — agreement pending

Sample dataDemo connection — agreement pending · connector plannedCare flow

13Integrations 2 · Contracted clinician network: Beluga Health 14Seen, prescribed, sent 15Integrations 3 · Hallandale Pharmacy 16Fulfilment and tracking 17Integrations 4 · Payment processing 18Integrations 5 · The full catalog

Prescription telemedicine · LastStop OS · sample data12 / 47

SeeMyVitals13 / 47

13LastStop

Integrations 2 · Contracted clinician network: Beluga Health

Setup B: a clinician networkLicensed in the patient's stateOpenLoop and Wheel as alternatives

Sample dataDemo connection — agreement pending · adapters built in the engineCare flow

The case goes to the network with the intake and consent; a clinician licensed in the patient's state is assigned and a video visit is booked.
E-prescribing, PDMP checks and EPCS are the network's responsibility, not LastStop's.
Built in the engine: a Beluga Health simulator, and a live connector that refuses to run until an agreement is signed.
OpenLoop and Wheel are built the same way, as alternatives.

No clinicians on staff? A licensed network sees the patient in their state.

Prescription telemedicine · LastStop OS · sample data13 / 47

SeeMyVitals14 / 47

14LastStop

Seen, prescribed, sent

Visit before the decisionThe clinician prescribesLastStop never prescribes

Sample dataDemo connection — agreement pendingCare flow

Intake, identity and consent, routed to Beluga Health, clinician assigned, visit completed, prescribed, received by Hallandale Pharmacy.
The screen states it: "A clinician decides every prescription. LastStop never prescribes or dispenses."
The pharmacist verifies and compounds.
Simulated in this demo; nothing is sent until an agreement is signed.

One approved case, from intake to the pharmacy, on one screen.

Prescription telemedicine · LastStop OS · sample data14 / 47

SeeMyVitals15 / 47

15LastStop

Integrations 3 · Hallandale Pharmacy

Connector code-completeHeld order until connectedAgreement pending

Sample dataNeeds vendor agreement · connector built in the engineDemo connection — agreement pendingFill routing · vendor not connected

Hallandale is a Florida 503A/503B compounding pharmacy. A clinic onboards through its partner portal and sends each prescription by LifeFile eRx, Surescripts or an EMR API.
Four sample orders: two waiting for a prescription, one shipped, one cancelled.
Until a pharmacy is connected, every approved case creates a held order instead of being routed.
The LastStop connector is code-complete in the engine; credentials and the agreement are pending.
Five more compounding pharmacies are planned on the same pharmacy interface.

Approved prescriptions go to the pharmacy. Nothing unapproved can.

Prescription telemedicine · LastStop OS · sample data15 / 47

SeeMyVitals16 / 47

16LastStop

Fulfilment and tracking

Received, compounding, shippedCold-chain handlingLabelled demo tracking number

Sample dataDemo connection — agreement pendingStatus timeline

Order O-PUWD: prescription confirmed, compounded, shipped with cold-chain handling, tracking on the order.
DEMO-PUWD is a labelled demo tracking number.
The step states: "Compounded medications are not FDA-approved."
Real tracking arrives with the pharmacy agreement and a shipping integration (planned).

Pharmacy status flows back to the order and to the patient's portal.

Prescription telemedicine · LastStop OS · sample data16 / 47

SeeMyVitals17 / 47

17LastStop

Integrations 4 · Payment processing

Card and ACHProcessor not yet contractedNo card data invented

Needs vendor agreement · payment engine built, not hosted

Card and bank (ACH) payments go through one processor, not yet named or contracted. The platform does not use Stripe.
Built in the engine, not yet hosted: card authorize and capture, refunds, subscriptions and dunning.
Until the processor is connected, the patient portal shows no plan price, no card on file and no invoices. Nothing is invented.
Refunds, payment holds and chargebacks stay with a person.

Charging, refunds and renewals are built. The processor isn't signed yet.

Prescription telemedicine · LastStop OS · sample data17 / 47

SeeMyVitals18 / 47

18LastStop

Integrations 5 · The full catalog

6 adapters built15 plannedNothing connected yet

Built in engine / Planned, as labelled on each card

Categories: clinician networks, EHR, pharmacies, payments, shipping, messaging, video visits, identity verification and labs.
Adapters built in the engine: Beluga Health, OpenLoop, Wheel, Healthie, Hallandale Pharmacy and the video-visit connector. None has a contract or credentials yet.
"Demo connection" means shown connected in this demo only, with the agreement pending.
Messaging (SMS and email) is planned. Until a provider and carrier registration exist, every message is a draft.
The page is read from the same catalog the platform uses.

21 partners, 9 categories, and an honest status on every card.

Prescription telemedicine · LastStop OS · sample data18 / 47