HIPAA Security Rule Implementation for Federal Healthcare Contractors

Mar
9
2027
Virtual 4-Hour Workshop 1:00 PM ET

Workshop on HIPAA Security Rule implementation for organizations supporting federal healthcare programs (VA, IHS, CMS, DHA). Covers administrative, physical, and technical safeguards, business associate agreements, the relationship to NIST 800-66, and the intersection with FedRAMP for cloud-hosted ePHI.

HIPAA Security Rule ePHI NIST 800-66 BAA
Instructor: Carl B. Johnson  |  Location: Virtual (Zoom)
Tuition
$595
Register

What This Session Covers

Federal healthcare contractors supporting agencies such as the VA, IHS, CMS, and DHA operate under HIPAA Security Rule obligations that are more complex than those facing typical covered entities. This four-hour workshop cuts directly to implementation — translating regulatory requirements into the specific safeguards, agreements, and documentation your organization must have in place to protect electronic protected health information (ePHI).

Administrative Safeguards

We examine the full set of required and addressable administrative safeguard standards, including security management process, assigned security responsibility, workforce training, contingency planning, and periodic evaluation. Participants will learn how to structure and document a risk analysis that satisfies both HIPAA Security Rule expectations and the guidance articulated in NIST SP 800-66, the recognized federal implementation resource for the Security Rule. We discuss how to map your existing policies to these standards and identify gaps that regulators and auditors commonly flag.

Physical and Technical Safeguards

The workshop moves through physical safeguard requirements — facility access controls, workstation use policies, and device and media controls — and then into technical safeguards covering access control, audit controls, integrity, and transmission security. For each category, instruction focuses on what implementation evidence looks like and how to demonstrate compliance through documentation rather than assumption.

Business Associate Agreements

Contractors working with federal healthcare programs frequently occupy the role of business associate, and many also engage their own subcontractors and cloud providers in that capacity. This session covers what a compliant Business Associate Agreement (BAA) must contain, common deficiencies found in vendor-supplied BAA templates, and how to manage BAA inventory as part of a sustainable compliance program. We address the downstream obligation to flow HIPAA requirements to subcontractors who handle ePHI on your behalf.

NIST 800-66 Alignment and FedRAMP Intersection

NIST SP 800-66 provides crosswalks and implementation guidance that federal contractors are expected to apply. We work through how 800-66 supports — but does not replace — the Security Rule's own standards, and where the two frameworks reinforce each other. For organizations hosting or processing ePHI in cloud environments, the session addresses the intersection with FedRAMP: what a FedRAMP authorization does and does not cover relative to HIPAA obligations, and what additional controls and documentation a contractor must layer on top of a cloud provider's existing authorization.

What You Will Leave With

This workshop is built around practical outputs. By the end of the session, attendees will have:

  • A gap assessment checklist mapped to HIPAA Security Rule administrative, physical, and technical safeguard standards, cross-referenced to NIST 800-66 guidance
  • A BAA review checklist identifying required provisions and common deficiencies to look for in incoming and outgoing agreements
  • A risk analysis documentation outline suitable for use in an HHS audit or agency contract review
  • Clarity on how to position your HIPAA compliance program relative to FedRAMP authorizations when using cloud-hosted ePHI systems
  • A prioritized list of implementation steps tailored to the federal contractor context

Participants who want to build on this foundation with ongoing support can explore Cleared Systems' Regulatory vCISO Services or review our broader Compliance Program Development engagements.

Who Should Attend

This session is designed for the people responsible for making HIPAA compliance work day to day inside a defense or federal contracting organization. If your organization holds contracts or subcontracts with the VA, IHS, CMS, DHA, or any other federal agency that involves access to ePHI, the following roles will get direct, actionable value from this workshop:

  • Compliance officers and managers who own HIPAA program documentation and audit readiness
  • Information security analysts and IT compliance staff responsible for implementing and evidencing technical safeguards
  • Contract and procurement personnel who negotiate or review Business Associate Agreements with agencies and subcontractors
  • Privacy officers whose scope includes the Security Rule as well as the Privacy Rule
  • Program managers on federal healthcare program accounts who need to understand their team's compliance obligations

Managers approving training budgets: this is a half-day investment that replaces weeks of independent research and produces usable compliance artifacts your team can apply immediately after the session. For organizations where HIPAA obligations have grown alongside a federal healthcare portfolio, this workshop closes knowledge gaps before they become findings.

Continuing Your Compliance Work

HIPAA Security Rule implementation rarely exists in isolation for federal contractors — it intersects with broader risk management obligations, cloud security requirements, and increasingly with other federal frameworks. Carl B. Johnson brings direct experience helping federal contractors navigate exactly these intersections. To learn how Cleared Systems can support your compliance program beyond this workshop, visit our full services overview.

Questions About This Session?

Ask about group rates, private delivery of this curriculum for your team, or whether this session fits your compliance roadmap.

Contact Us