Feature catalog
Everything in the clinical engine
Structured the way a founder evaluates vendors — tenant, patient journey, clinical work, pharmacy, workforce, ops, and integration. Plus the capabilities we will not pretend to ship.
Tenant and brand
Multi-tenant isolation
Every tenant-scoped table carries a tenant id and is isolated by Postgres row-level security. Isolation is structural, not a convention that one missed query can break.
Tenant administration
Tenant admins configure their own practice — offerings, staff, and operations — without seeing another tenant. Platform ops stay on a separate role axis.
CMS-driven public pages
Site chrome, marketing pages, and disclosures are governed content, not a one-off theme fork per brand.
White-label patient app
Use the reference patient experience under your brand, or bring your own portal against the same API and webhook contract.
Patient journey
OTP login
Patients authenticate with a one-time code. No password reset theatre and no third-party identity product in the critical path.
Structured intake
Condition-specific questionnaires land as a structured payload on the request the provider works from. Answers are not re-typed into a note.
Offerings and pricing
Tenants publish the products and cash-pay prices they actually sell. No insurance fee schedule lives here.
Cash-pay checkout
Patients pay the practice, not a payer. There is no claims submission, ICD-10/CPT coding, or clearinghouse integration.
Fulfillment timeline
Patients and staff see where an order stands after it leaves the chart — without inventing status from a pharmacy inbox.
Clinical engine
Async queue matching
A request lands in a live-matched queue: state license × credentialed condition × tenant/network agreement, evaluated at claim time. Renewals route back to the assigned provider.
Clinical chart
Problem, medication, and allergy lists; condition-specific notes; photo, document, and PDF attachments.
Provider macros
Text-expansion macros for high-volume charting so the note stays structured without slowing the clinician down.
NP/PA supervision
Nurse practitioner and physician-assistant supervision is enforced in the product, matching how the practice is actually licensed to operate.
MD-governed protocols
Clinical content is versioned and reviewed. What a provider can offer is the protocol a medical director approved, not a silent local edit.
Prescribing and pharmacy
Non-controlled e-prescribing
Standard e-prescribing via WENO. Controlled-substance prescribing (EPCS) is a deliberate non-goal at this stage, not an oversight.
Multi-pharmacy routing
Route to compounding and standard pharmacy partners by condition and state licensing, with fallback and priority rules — not a single hardcoded pharmacy.
Workforce
Provider app
The clinicians who run the queue get a dedicated web and mobile app — registration, queue, chart, and messaging — not a resized admin console.
Credentialing
Provider onboarding with state license and condition-credential verification before a request can be claimed.
Network agreements
A provider network can serve more than one tenant under explicit agreements. Cross-network visibility is never implied by role name alone.
Operations
Shared admin console
Platform ops and tenant admin share one codebase, split by role and organization scope.
Append-only audit log
Every PHI access is recorded. The audit trail is not a best-effort application log you hope someone grepped.
Break-glass
Emergency cross-scope access is a distinct, separately audited path — never a hidden admin toggle in the normal workflow.
Lead inbox
Visitor interest on a tenant site can land in an ops inbox. That is lead capture, not automatic tenant or patient provisioning.
Integration
REST and webhooks
A documented request/webhook contract: submit a case, receive lifecycle events. Authentication is server-side. Tenant identity is never taken from a client-supplied id.
Bring your own portal
If you already have a patient-facing brand site, integrate against the contract. If you don't, use the reference provider, admin, and patient apps.
What this platform explicitly doesn't do yet
A mismatched expectation after you sign is worse than knowing the real scope up front. Every deferred capability has a reason.
Insurance billing
No claims submission, ICD-10/CPT coding, or clearinghouse integration. ShriMD is cash-pay only, by design — not a gap we are racing to close.
Controlled substances (EPCS)
Standard, non-controlled e-prescribing only. Schedule II–V prescribing is a deliberate scope decision. Do not evaluate ShriMD for TRT or other controlled-substance programs.
Lab integration
No lab ordering or results integration yet. Deferred and documented, not silently ignored.
FHIR-native EHR
The tenant contract is REST and webhooks. A FHIR-shaped adapter is a scoped addition if a real integration requires it — not a claim that ShriMD is a FHIR-native EHR.
Ready to map this against your brand? Contact the ShriMD team.
Talk to the ShriMD team
Tell us what you want to build. A person follows up. This is not a self-serve signup and it never creates platform access.
No patient information. No PHI. A human on the ShriMD team reads every note.