Prescription Telemedicine

AtlasTx, your Triage COO

Every open item in the practice, in one list, in the right order.

• The dashboard opens on AtlasTx. It watches intake, the clinician queue, the pharmacy, refills, compliance flags and support.
• Every record is named by a random code with a lock chip (for example S-C859), never by a patient's name.
• Atlas ranks every open item inside the app.
• Open safety reports sit above everything else; a clinician reviews every one.
• Nothing runs until someone presses Run AtlasTx.

LastStop, the framework

One platform, many practices, each with its own brand.

• The framework: intake, cases, both clinical setups, the pharmacy, the patient portal, billing, audit and integrations.
• Staff sign in first, then choose the practice, so one platform can run several practices.
• Each practice gets its own brand kit and separated data. The separation is built in the engine, which is not hosted yet.
• The demo signs in with shared preview logins. Per-staff accounts, roles and MFA are built in the engine and get wired in before launch.

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.

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.

Growth Engine

Brand, ads and outreach from one kit, checked before anything runs.

• Brand Absorber reads a site into a brand kit; Style Absorber borrows a look without the identity.
• Ad Studio builds finished ads in 7 formats from pre-approved messages, in the practice's locked Seasons.
• Outreach bots draft messages for four patient segments. Nothing sends without a person.
• Every ad and message runs through the claim rules before a person sees it.

Compliance: the section you don't skip

Two sample ads. Both stopped before they ran.

• Behind the stamps: ClaimRight catching an outcome guarantee and a false FDA-approval claim in two sample ads.
• This section covers the claim rules, the FDA disclosure, LegitScript readiness, text consent and STOP, state prescribing rules, visit before prescribe, the licence check, the approval gate, the audit log and Blind Atlas.
• No certification is claimed: LegitScript is not filed, SOC 2 is not started, and no BAA is signed yet.
• These are the controls the practice runs on from day one.