How a care-coordination startup rolled out AI workflows inside HIPAA constraints

Security had frozen every AI tool request for a year at this Columbus health-tech company, and shadow usage was spreading anyway. Reviewing one platform once, instead of eight tools separately, got the team from freeze to approved rollout in six weeks, with shadow-AI accounts down from eleven to zero.

6 wks
from security freeze to approved rollout
0
shadow-AI accounts after rollout, down from 11
3 days
to approve a new workflow, down from 6-8 wks
12
workflows vetted and live in the first quarter

The situation

The security lead was not being difficult; he was being asked to do the impossible. Eight separate AI tool requests sat in the review queue, each needing its own BAA, its own data-flow review, and its own prompt-injection assessment. So everything stayed frozen, and the freeze created exactly the risk it was meant to prevent: an internal check found eleven personal AI accounts being used for work, some with pasted chart-note fragments.

The VP of Product needed the productivity and the security lead needed the perimeter. Neither was getting either.

The turn

The pitch to security was structural: review one platform once, then let every workflow inherit that review. Second Axis ran its session isolation, encryption, access boundaries, and no-training posture through the full assessment in six weeks, BAA included. Sentinel's screening then became the per-workflow gate: a new workflow now clears in about three days instead of joining an eight-week queue.

Shadow usage ended without a crackdown. Once the sanctioned workspace was faster than a personal account, the eleven shadow accounts went quiet on their own; the follow-up check two months later found zero.

Security said yes in six weeks because they reviewed one platform once, instead of reviewing every tool my PMs were smuggling in. That is the whole story.
VP of Product, care-coordination platform

How Second Axis fits

01

One security review, inherited by every workflow

Session isolation, encryption, and access boundaries assessed once. Every subsequent workflow inherits the approved posture.

02

Sentinel screening as the per-workflow gate

Prompt injection and data-access checks run before a workflow reaches the team, turning an eight-week queue into a three-day check.

03

Guardrails matched to PHI boundaries

Access rules define what agents can touch, so PHI-adjacent workflows run inside limits security set once.

04

A sanctioned path faster than shadow AI

The approved workspace outperformed personal accounts, so shadow usage ended by preference rather than policy.

Results

AreaBeforeAfter
AI tools awaiting security review8 in queue1 platform, approved
Shadow-AI accounts in use11 found0 at follow-up
Time to approve a new workflow6-8 weeks3 days
PM hours per week on manual note synthesis~61.5
PHI incidents attributable to AI tooling00, maintained

What came next

Week 0Security agrees to assess one platform in place of eight queued tool reviews.
Week 6Full security assessment and BAA complete. Rollout approved.
Week 8First five Sentinel-vetted workflows live for product and clinical ops.
Month 3Follow-up check: zero shadow accounts. Twelve workflows in production.
Month 4Customer success onboards on the same approved posture, no new review cycle.

The review queue is gone, and so is the standoff between product velocity and the security perimeter. The security lead now cites the single-review model as the template for evaluating any new category of tooling.

Company details anonymized at the customer's request.