For Clinicians & Facilities · The Practice
Built under a clinical governance model: every client-facing word passes clinical sign-off; every data flow passes counsel. That’s not a footnote — it’s the product.
Showing the clinician view — triage and between-session work first.
Triage
Not a feed. A roster sorted by concern, each line telling you why it’s there.
Between-Session Work
Assign from a quiet drawer — five clinical modules, three grounding tools, state-gated so heavy work waits for GREEN. Then the language does the ethics:
PENDING
You assigned it. It waits for the right state — RED can never be overridden.
DELIVERED
It reached them. That’s all you see — never “completed.” Completion is private by default.
SHARED
They chose to share back: a structured summary — pre→post state, time, interventions. Never their raw writing.
The client who knows their counselor can’t read their journal writes an honest journal. Alliance, preserved by architecture.
The Facility Lane
Remote Therapeutic Monitoring is a real reimbursement lane. FORGED does the timekeeping.
RTM telemetry
Passive monitoring minutes auto-accrued and server-re-derived — over-claim-proof. Synchronous minutes entered. A monthly attestation workflow produces an auditable billing record. [Exact CPT positioning pending counsel.]
UR cadence
Per-client payer, plan, and level-of-care review profiles with research-seeded defaults — RES 7d, PHP 7d, IOP 10d, OP 30d — countdowns, overdue flags, self-pay master-off. The client never sees insurance language.
Scoping & peer lane
Multi-facility scoping for groups. Peer-support Crew coordination runs content-free — outreach signals only, no clinical detail in the peer lane.
Compliance & Integration
Enforced before any PHI renders. Revoked consent is a first-class, designed-for state — not an error.
Displays minimize identifiers; writes are idempotent and audited. [Exact claim language per counsel.]
Kipu adapter pattern for the chart your team already lives in; Cloudflare infrastructure under BAA.
The client is the only valve. For you, that means the signal you see is one your client can trust — and so can your documentation.
Read the principle →Pilots are conversations, not contracts.
Request a pilot conversation