Platform capabilities
Structured the way you actually evaluate an EHR/clinical-platform vendor — not generic feature marketing.
Intake
Structured intake payload per request, mapped directly into the clinical note a provider works from — no re-keying patient answers into a separate documentation step.
Async triage & queue matching
The default pathway: a request lands in a live-matched queue (state license × credentialed condition × tenant/network agreement, evaluated at claim time, never a stale precomputed list) and any eligible provider claims it. Renewals and follow-ups route directly back to the assigned provider, bypassing the queue.
Scheduling
For the subset of care that genuinely needs a live visit, booking with timezone handling is a secondary surface — not the platform's home screen.
Clinical documentation
Problem, medication, and allergy lists; condition-specific structured note templates; photo, document, and PDF attachments; provider text-expansion macros for high-volume charting.
E-prescribing
Standard, non-controlled e-prescribing via WENO. Routed to curated compounding and standard pharmacy partners by condition and state licensing, with fallback/priority logic — not a single hardcoded pharmacy.
Compliance
Row-level security enforces tenant isolation at the database layer, not just in application code. A full, append-only audit log covers every PHI access. A distinct, separately-audited break-glass path exists for genuine emergency access — never a normal workflow shortcut.
Interoperability
A documented REST/webhook contract for tenant integration: submit a request, receive lifecycle webhooks. Bring your own patient-facing portal against this contract, or use our reference provider and admin apps directly.
Provider & pharmacy network administration
Provider onboarding, state license and condition credential verification, and provider-network agreements per tenant — plus pharmacy partner onboarding and routing rules — all manageable without engineering involvement.
What this platform explicitly doesn't do yet
A mismatched expectation discovered after you sign is worse than knowing the real scope up front. Every deferred capability below has a stated reason, not a silent gap.
Insurance billing
No claims submission, ICD-10/CPT coding, or clearinghouse integration. This platform is cash-pay only, by design — not a gap we're racing to close.
Controlled substances (EPCS)
Standard, non-controlled e-prescribing only at this stage. Controlled-substance prescribing is a deliberate scope decision, not an oversight.
Lab integration
No lab ordering/results integration yet. Deferred, not silently ignored — revisit criteria are documented internally.
Bidirectional FHIR API
Our tenant integration contract is a custom REST/webhook API, not FHIR. Simpler to integrate against for the multi-tenant, cash-pay model this platform serves; a FHIR-shaped adapter is a scoped addition we'd build only if a real integration requires it.