What is built, and what is standing in.
The clinical software is finished and running. Some of the outside services it talks to — a card processor, a pharmacy, a video vendor — are commercial relationships that get signed before launch, not code that gets written. Until each one is connected, this page says so.
8 services are simulating right now
This deployment has sandbox mode on so the whole journey can be walked end to end. Simulated records carry a Simulated badge wherever they appear and a reference beginning sbx_. No money moves, nothing reaches a pharmacy, and no message leaves the server. Connecting a real vendor is one set of credentials — the code path does not change.
24
treatments, none controlled
5
versioned intake questionnaires
5
legal documents, captured by version
Before you are a patient
Everything up to the point of payment runs here, with no third party involved.
Screening that can say no
Live5 versioned questionnaires across the service lines, scored as you answer. A disqualifying answer stops the enrolment before any payment details are asked for.
Validated clinical instruments
LivePHQ-9 and GAD-7 are scored in full, including the self-harm item, which routes to a hard stop rather than a queue.
State licensure and age gates
LiveChecked at intake and again at prescribing, so an address change between the two cannot slip a prescription past the rule.
Versioned consent capture
Live5 legal documents, each recorded against the exact version the patient agreed to.
The clinical record
The parts a regulator would ask about are implemented, not stubbed.
Append-only audit log
LiveEvery read and write against patient data is recorded with actor, role and entity, per HIPAA §164.312(b). Searchable in the admin console.
Compounding justification gate
LiveA compounded preparation cannot be prescribed on cost, convenience or patient preference. The server refuses the reason, not just the form.
Office-stock refusal
LiveAn in-clinic administration must be linked to an order dispensed in that patient’s own name, with lot number and site. There is no bulk path to record against.
No controlled substances
LiveAll 24 catalog items are non-scheduled. The prescribing gate rejects anything else, which is what keeps the practice clear of DEA telemedicine registration.
Session security
Livescrypt password hashing, opaque server-side sessions with rotation, and TOTP required on every clinical account before it can open a chart.
Connected services
Each of these needs an outside vendor. Until one is connected the work falls to a person, and the interface says so rather than pretending otherwise.
Card payments
SimulatedCharges settle against a simulated processor so the flow can be walked end to end. Every such payment is labelled, and no money moves.
Electronic prescribing
SimulatedTransmission is simulated and the prescription is marked as such. No pharmacy receives anything.
Pharmacy fulfilment
SimulatedFills return a simulated order id and delivery estimate, both labelled.
Video visits
SimulatedA placeholder room stands in for the vendor. The link points here, never at a domain that would imply a real meeting.
Mail is marked delivered without leaving this server.
Identity verification
SimulatedVerification passes automatically and is labelled simulated.
Lab ordering
SimulatedOrders return a simulated requisition id.
External EHR
SimulatedSync is simulated.
The rule this page enforces
The application never asserts something it cannot back up. Nothing shows as paid unless a processor confirmed it. Nothing shows as transmitted unless a pharmacy accepted it. Where a service is simulated, it says simulated — on this page, in the record, and on the screen the patient sees.