One login carries your whole professional life.
Your solo caseload, the group you contract with — each practice cleanly separated, with its own records, roles, and billing. Built by a practicing clinician who was tired of paying full price at every place he worked.
In private beta — onboarding practices directly, not self-serve yet
Five working foundations, still being hardened.
Available in the current private beta. Security and workflow hardening continues before broader release.
- Client recordsOne record, however the work changes shape.
Identified client profiles, insurance, and outcome measures live on the person — not the case — so a couples case splitting into individual work never re-collects demographics or loses PHQ-9 history. The beta includes versioned note edits, audit logging for record access and changes, and workflows for export, amendment, and hard-delete. Security hardening continues before broader release.
- SchedulingA real week grid, and every EHR you already use in one agenda.
Recurring appointments materialize as real, individually-manageable instances — canceling a series leaves history untouched. Separately, your existing EHR calendars (SimplePractice, TherapyNotes, anything with an iCal feed) aggregate into one read-only agenda, plus a shareable link that strips every name and shows only busy/free blocks.
- SuperbillsA real receipt, not a screenshot of your ledger.
Every logged payment can produce a print-ready superbill — practice info, the one identified patient (never "the couple," even for a joint case), the service line, and the required not-a-guarantee-of-payment disclosure. Payments are logged today (amount, method, code); card processing is a deliberate later step, not yet built.
- Practice & teamRoles that actually restrict what a role can see.
The beta enforces owner, admin, associate, biller, front-desk, and viewer roles server-side. Biller and front-desk responses are designed to exclude clinical narrative. Invites, role changes, suspensions, and removals are audited, while authorization hardening continues before broader release.
- Bring your own AI keyConnect Claude, OpenAI, or Gemini — pay provider cost, not a markup.
Each clinician connects their own key, per practice, behind an explicit consent step. Keys are envelope-encrypted at rest and decrypted only by the dedicated provider proxy when it makes a model call. They are never displayed back in plaintext, and the beta does not fall back to a colleague's key.
Straight about what this is, and isn't.
Security and compliance detail — encryption, BAAs, subprocessors — is on one page for the whole product, not repeated here: see Security.
This is not a full EHR — no scheduling-to-claims-submission pipeline or client-facing portal yet. It's the documentation and billing layer with memory of each client.
Pricing isn't public yet — the model depends on a couple of decisions still being finalized. Ask, and we'll tell you honestly where that stands.
Built for HIPAA-sensitive workflows. NoteScreen is a documentation-support tool and does not guarantee payment or any particular claim outcome. See Security & Compliance for the full picture.
We onboard practices one at a time, by hand.
Tell us how your practice is set up and which EHRs you already use, and we'll walk you through what the private beta covers today.