Healthcare Software SDLC Evidence: Change Control, Code Review, and Release Approval Proof for HIPAA Security Rule, SOC 2, and HITRUST Reviews

Healthcare and life-sciences software teams

Your BAA says you have change control.
Your next security review asks you to prove it.

Hospital systems, payers, and life-sciences customers do not take a vendor’s word for secure development. They send a questionnaire, a HITRUST or SOC 2 request, and a sample of production changes. SDLC Playbook produces the engineering evidence those reviews ask for, continuously, from GitHub, Azure DevOps, Jira, Slack, and Teams, so the answer is a package rather than a scramble.

The operational problem

Every health-system customer runs its own audit. Your engineers rebuild the same proof each time.

A software vendor handling protected health information lives under the HIPAA Security Rule as a business associate, under SOC 2 because procurement demands it, and under HITRUST because the largest health systems and payers ask for it. None of those regimes tells you how to build software. All of them ask whether changes to systems that touch PHI were authorized, reviewed, tested, approved by someone independent of the author, and deployed with a way back, and whether you can show it for the period in question.

That evidence exists in pull requests, pipeline logs, Jira, and chat. It is not in one place, and every customer review (and there are many, because each covered entity runs its own vendor program) sends a senior engineer back to reconstruct it. The gaps that surface are familiar: a hotfix to a PHI-handling service with no ticket, a reviewer who was also the author, a deploy with no rollback plan, an AI-assisted change nobody can say who reviewed.

The reviewers are not going away. The reconstruction can.

What healthcare reviews expect from engineering

The obligations that reach into the development process.

A starting-point map, not a compliance or legal opinion. Your assessor’s, examiner’s, or customer’s interpretation governs, and scope varies by organization.

HIPAA Security Rule · 45 CFR 164.308 and 164.312
Risk management, information system activity review, and audit controls. A business associate is expected to manage changes to systems that create, receive, maintain, or transmit ePHI and to be able to review what changed. Formal change-management procedures are what assessors look for.
Business associate agreements
Most BAAs and the security exhibits attached to them commit the vendor to documented secure development and change control. The customer’s vendor-risk team tests that commitment with questionnaires and sampled evidence.
HITRUST CSF · change management and secure development domains
Large health systems and payers increasingly require HITRUST. Its change-management and development controls ask for authorization, testing, segregation of duties, and records retained for the assessment period.
SOC 2 · CC8.1 change management
Procurement’s default ask. The auditor samples production changes and wants the ticket, review, tests, approval, deployment record, and exception handling for each. See the SOC 2 SDLC controls page.
FDA guidance for device-adjacent software
If your product is or feeds a regulated medical device, design controls under 21 CFR 820 and FDA’s premarket cybersecurity guidance add traceability from requirement to test to release. The same evidence trail serves both, but the regulatory determination is yours and your counsel’s.
Evidence checklist

What a health-system reviewer asks for on a sampled change.

Use this as the list to test your own process against before a customer does. For each production change to a system in PHI scope during the review period, can you produce the following without reconstructing it?

  1. A linked work item that authorized the change, with acceptance criteria written before the work started.
  2. PHI scope noted so the reviewer can see which changes touched systems that handle ePHI and which did not.
  3. A code review by someone other than the author, with the reviewer identified and the approval timestamped.
  4. Test results for the change, including coverage on the changed code and any required test plan.
  5. Security scan results from your CI pipeline, with high-severity findings resolved or formally accepted.
  6. A release approval by an authorized approver who is not the author or the deployer.
  7. A rollback plan attached before deployment, not written after.
  8. The deployment record: who deployed, when, from which build.
  9. Exception handling for any skipped gate: justification, approver, follow-up task, and its resolution.
  10. AI involvement: which changes were AI-assisted, and who reviewed them.
  11. Integrity and period coverage: a way to show the evidence has not been edited since capture, and the same evidence for every change in the window, not only the ones sampled.
How SDLC Playbook supports the workflow

Every item on that list, captured when the control runs.

Gates that produce evidence

Six PR gates run by Code Sentinel (ticket linkage, non-author review, coverage, and more) and six release gates run by Release Gatekeeper (approval, rollback plan, test signoff). Each gate result is stored as evidence mapped to the control it satisfies.

Separation of duties, enforced

A Release Approver role with deny-by-default deploy gating. Nobody approves their own release. Approvals given in Slack or Microsoft Teams are captured as control-mapped evidence at the moment they happen.

Overrides with a paper trail

When a gate has to be bypassed, the override records justification, approver, follow-up task, and audit tag. The exception becomes evidence instead of a gap.

Tamper-evident vault and export

Every evidence item carries a canonical-JSON SHA-256 and a verify endpoint confirms it has not changed. One click produces a PDF audit package and an evidence ZIP with a chain-of-custody manifest, scoped to the period you were asked about.

Drift detection across the period

Governance Drift Detection reconciles the process you documented against what actually ran. Each control reports CONFIRMED, OBSERVED_ONLY, or NOT_OBSERVED_IN_WINDOW, so you find the gap before a reviewer samples it.

AI-assisted code, accounted for

Commits and pull requests carrying AI co-author or bot signals are recorded, so when a reviewer asks which changes were AI-assisted and who reviewed them, the answer comes from evidence rather than recollection. Where no signal exists the product reports unknown, never human-only. Whether your team calls it the SDLC or the agentic delivery lifecycle (ADLC), the record it has to produce is the same.

Integrations shipped today: GitHub, Azure DevOps, Jira, Slack, and Microsoft Teams (commercial cloud). Evidence is mapped to SOC 2, NIST SSDF (SP 800-218), and NIST 800-171 today; one finding lights up every framework the control belongs to. Mapping to HIPAA Security Rule citations and to HITRUST CSF control IDs is on the roadmap; today the evidence is exported with its SOC 2 and SSDF mapping and handed to your assessor as-is.

Clear limits

What SDLC Playbook does not do.

It does not make you HIPAA compliant, HITRUST certified, or SOC 2 compliant, and it does not replace your assessor or your counsel. It produces and maintains evidence about your development process; the opinion is theirs.

It does not scan code for PHI leakage, encrypt your databases, or manage access to your production systems. Those are infrastructure and application controls your security team owns. SDLC Playbook covers the process evidence around changes to those systems.

It does not yet map evidence to HIPAA or HITRUST control identifiers. Evidence is mapped to SOC 2, NIST SSDF, and NIST 800-171 today and exported for your assessor to map; HIPAA and HITRUST mapping are on the roadmap and we will say so until they ship. SDLC Playbook itself has not completed a SOC 2 or HITRUST assessment; see our security page for exactly where we stand.

Healthcare engineering FAQ

What healthcare engineering leaders ask, answered.

Does the HIPAA Security Rule require change management for software?

The Security Rule does not prescribe a software development process, but its risk-management, information-system-activity-review, and audit-control requirements are read by assessors to require that changes to systems handling ePHI are controlled, reviewed, and reviewable. Business associate agreements usually make that commitment explicit. Your counsel and assessor determine the exact obligation for your organization.

What do HITRUST assessors ask for from the engineering team?

Typically evidence that changes were authorized and tested, that development, test, and production are separated, that the person approving a change is not the person who made it, and that records exist for the assessment period. The specific requirement statements depend on your HITRUST scope and assessment level.

Does SDLC Playbook map evidence to HIPAA or HITRUST controls?

Not yet. Evidence is mapped to SOC 2, NIST SSDF, and NIST 800-171 today and exported with that mapping; HIPAA Security Rule and HITRUST CSF mapping are on the roadmap. Assessors can work from the exported package in the meantime.

Does SDLC Playbook see or store PHI?

No. It reads work-item and pull-request metadata, pipeline outcomes, and approval events through scoped connectors, and stores the governance record and evidence hashes. It does not connect to your production databases or hold patient data. Our security page describes exactly what is held.

How does this help with the volume of customer security reviews?

Each review asks for roughly the same engineering evidence for a different period. With the evidence captured continuously and tamper-evident, producing the package for a new reviewer is an export scoped to their period rather than a fresh reconstruction. The SOC 2 report gets you onto the shortlist; what keeps you on it is whether the answer to who approved a specific change and what testing ran comes from a system of record or from chat threads and memory.

Design partner program

Health-system security review on the calendar?
Answer it with evidence that was already collected.

The product is built and in private design-partner stage. Design partners get 90 days free and early-partner pricing in exchange for reference rights and honest feedback. If your engineering team is the part of HIPAA, HITRUST, and SOC 2 that still runs on screenshots, let’s talk.