The setting
is a marketplace and software platform that connects patients, health insurers and independent providers of mental health care across the United States. is the software therapists and psychiatric prescribers use to accept insurance and run their practice.
Clinical transparency pulls against keeping sensitive access records difficult to alter.
Clinicians need a usable history of note access, while privacy and integrity require that history to remain trustworthy.
Who you’d be doing this for
“I got feedback on a note, and now I’m digging through messages to find out who saw it first.”
Gustaf Laine · Independent Clinical Social Worker · a character in this brief
Runs a solo outpatient practice and uses the clinical workspace for progress notes and documentation review responses.
What is at stake
Clinicians cannot independently see who accessed a note when review feedback arrives. You must weigh a useful clinical audit trail against the risk of exposing or weakening sensitive access records.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- clinician transparency vs. sensitive metadata exposure
- audit completeness vs. documentation performance
- shared trust primitives vs. a focused pilot
- fast learning vs. privacy review
Why Headway
The clinical documentation workspace holds the records independent providers rely on to run care and respond to annual note review.
Written with these in mind
Not your kind of problem? 104 more at Headway, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Headway. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Security Engineer (Infrastructure) (opens in a new tab)
- Staff Infrastructure Engineer · no longer posted
- Staff-level influence: you drive decisions across team boundaries and raise the infrastructure bar org-wide without requiring management authority to do it
- Build the Terraform self-serve platform with guardrails so engineering teams own their standard infrastructure changes and Reliability Engineering reviews only the non-standard ones.
- Senior Security Engineer (Product) · no longer posted
- Headway’s mission is a big one – to build a new mental health care system everyone can access.
- Senior Software Engineer (Trust Foundations) · no longer posted
- Building for trust is non‑negotiable in our mission of making mental healthcare more accessible and affordable across the US: patients share sensitive information, payers demand demonstrably strong controls, and providers depend on reliable, secure infrastructure.
- Design, build, and operate core trust primitives - authentication providers, authorization engines, data governance, stratified encrypted data stores, and tamper‑evident audits.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about people starting something and never quite finishing it.
Reviewers flagged 3.2% of signed notes as needing a delay or extra handling, and they disagree on how wide the exceptions should be.
You have to set the release policy before go-live, and wrong exposure is expensive to undo.
Eighteen recent investigations would have exposed encounter context unrelated to the incident.
You have to tighten access before launch without slowing recovery beyond what clinicians can tolerate.
Security reviewers chase service owners for context before they can decide on each access-review item.
You decide whether an identity that looks routine in one system and privileged in another is ranked by the routing or goes straight to a reviewer to judge.
The same setting, from another role
Each is set around Headway’s Headway for Providers, written for a different role. They’re separate briefs, not the same scenario.
New clinicians are missing first appointments after completing early onboarding steps.
You must decide whether AI drafts explanations from evidence or only assembles the evidence for PM review.
Virginia clinicians are unsure whether their enrollment records are complete before January 29.
You must decide which readiness signals prompt action without implying payer approval.
Clinicians are receiving lower payments while claim records still look processed.
You must choose which suspected downcodes can move automatically and which need human review.
Other problems with a similar purpose
In each of these, as in this one, the aim is to remove a real security exposure while keeping the everyday workflow people depend on running smoothly.
Staged testing shows a 0.6% session failure rate on older mobile versions before an irreversible authentication cutover.
You need to close the token exposure without locking members out of liquidity and repayment flows.
One authentication mode has a confirmed flaw and has to be off in every managed workspace within 21 days.
You have to sequence migration and enforcement so exposure closes without breaking data delivery.
Valid workspace members are looping through sign-in despite appearing in the right SSO groups.
You have to restore access while preserving the permission boundary administrators rely on.
