SeeMyVitals19 / 47
Pillar · the framework
The patient portal
What the patient sees: plan, prescription, next visit, care status.
- Plan, active prescription, next appointment, lab flags, care status and cases for a sample patient.
- The sample case is waiting for clinician review: no decision, no prescription, and nothing sent to Hallandale Pharmacy (demo connection).
- Patient sign-up and login are built in the engine; the demo uses session data.
- Video visits: the connector is built in the engine and waits on a key and a BAA.
One sample patientAwaiting clinician reviewSession data in the demo
Prescription telemedicine · LastStop OS · sample data19 / 47
SeeMyVitals20 / 47
20LastStop
Refills
Opens in the last weekThe clinician re-approvesThen the pharmacy
- Refills open in the last week of a 30-day supply.
- The request goes to the clinician, then to Hallandale Pharmacy only after approval, then ships with tracking.
- The engine's refill request and recheck gate are built.
Refills go to the prescriber first, then the pharmacy. Never the other way round.
Prescription telemedicine · LastStop OS · sample data20 / 47
SeeMyVitals21 / 47
21LastStop
Secure messages
The care team answersClinical questions go to a clinicianServer messaging built
- The sample patient has not written yet, so the thread is empty. A new message goes to the care team.
- Staff or clinicians answer. Clinical questions go to a clinician.
- In the demo, threads live in the browser; server-side messaging is built in the engine.
Patients write to their care team, not to a shared inbox.
Prescription telemedicine · LastStop OS · sample data21 / 47
SeeMyVitals22 / 47
22LastStop
Billing, stated plainly
Cancel in the portalNo fabricated card dataProcessor not contracted
- No plan price, card on file or invoices, because the payment processor is not connected.
- Card details are never fabricated.
- Cancel is offered in the portal.
No processor connected, so no price, card or invoice is invented.
Prescription telemedicine · LastStop OS · sample data22 / 47
SeeMyVitals23 / 47
23LastStop
On a phone
390-pixel phone widthSAMPLE label stays visibleApprove taps still required
- The dashboard, AtlasTx, record codes and the care flow fit a 390-pixel phone screen without sideways scrolling.
- The patient portal is laid out for the same width.
- SAMPLE DATA stays visible on the phone.
- Anything that sends or changes a record still needs an approve tap.
- Perfectly wrapped to fit your phone. iOS and Android apps are planned, for you and your patients.
The whole console fits a phone.
Prescription telemedicine · LastStop OS · sample data23 / 47
SeeMyVitals47 / 47
47Where it stands
What's real today
Built: all four pillarsWaiting: signaturesNot claimed: patients or revenue
- Built: the platform and its four pillars, shown here on labelled SAMPLE data from a local demo build.
- Waiting on signatures: the pharmacy, a clinician network or EHR, the payment processor, BAAs, a messaging provider and 10DLC registration, the LegitScript filing and counsel review.
- Not claimed: patients, orders, revenue or certifications.
- Next in the build: host the engine and wire the app to it, so every screen runs on real records.
Built and demonstrable today. Live with patients after the agreements are signed.
Prescription telemedicine · LastStop OS · sample data47 / 47
