Healthcare: HIPAA Access Review with Claude Code: Sandbox Policy
A production playbook for HIPAA access review in healthcare operations using Claude Code: sandbox policy, run-scoped inputs, logs, typed results, and artifacts.
Audience: Healthcare security and compliance teams
The problem
Healthcare security and compliance teams need HIPAA access review to run repeatedly against access logs, user roles, patient data events, and policy exceptions. In healthcare operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Run HIPAA access review in an ephemeral sandbox, keep provider credentials in the broker, expose narrow tools, and store logs outside the workspace for review.
Tradeoffs and failure modes
A narrower runtime blocks ambient machine behavior, but it gives security reviewers a concrete boundary. For HIPAA access review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Runtime boundary
filesystem: /skill and /skill/.argo/inputs only
network: deny by default
artifacts: /skill/output/artifacts
logs: retained outside sandbox
provider: Claude Code
Run this on Argo