October 29, 2026

HIPAA Compliance for Nonprofits Running Health or Social Service Programs

HIPAA compliance for nonprofits running health or social service programs depends on what an organization does. The less obvious route into the law is a contract to handle patient information for a healthcare partner. Understanding that role comes before choosing software or writing policies, because compliance has to match both the nonprofit’s legal obligations and the way its programs work.

What HIPAA actually protects and why the law's scope surprises nonprofits

“We're a 501(c)(3), so this doesn't apply to us” is an understandable assumption, but HIPAA contains no nonprofit exemption. The law defines covered entities by what they do, including health plans, healthcare clearinghouses, and healthcare providers that send health information electronically as part of covered transactions. Tax status does not enter that test. A nonprofit community clinic that bills Medicaid electronically is a covered entity on the same terms as a for-profit hospital.

The information protected is also broader than a clinical chart. Protected health information, or PHI, is health information that can identify a person and that a covered entity or business associate holds or sends. It can include appointment dates, billing records, insurance information, and names and addresses associated with health information. The context determines whether the information is PHI. So intake forms, donor records that include health history, and sign-in sheets from community health events can fall under the law’s protection when a covered entity holds them.

The two paths into HIPAA obligations — and which one catches nonprofits off guard

The covered entity route is comparatively easy to recognize. A nonprofit that runs a clinic, home health service, mental health practice, or substance use treatment program may qualify because of the healthcare it provides and the electronic transactions it makes. A charity-only clinic that never bills insurance electronically may fall outside the covered entity definition, but billing electronically can bring it under that definition.

The business associate route is easier to miss because it does not require the nonprofit to provide clinical care. A business associate handles PHI on behalf of a covered entity. That can describe a care coordination organization, a social services agency receiving hospital referrals, or a housing program connected to a healthcare system. The contract can be the turning point. An agreement with a county health department, managed care organization, or hospital system that calls for handling patient records may bring duties the nonprofit never expected.

What if only one program handles this information? Larger nonprofits with clinical and non-clinical programs may be able to designate healthcare components, limiting HIPAA’s scope to those components. That is a legal and governance question for counsel. The same need for legal review applies when business associate status is uncertain. Uncertainty does not make non-compliant handling of PHI safe.

Where nonprofit health organizations face exposure they don't expect

Volunteer programs create a particular access challenge. HIPAA’s workforce includes paid employees, volunteers, trainees, and students working under the organization’s direction. So volunteer physicians, intake volunteers, and nursing students need training and access only to what their roles call for. Their access also needs to end when they leave. Frequent turnover makes a repeatable training and offboarding process more reliable than informal arrangements.

Fundraising creates a different boundary to maintain. Donor information on its own is not PHI, but nonprofit health organizations often keep records on both donors and patients. The risk appears when those uses mix. A free care provider needs compliant written authorization before including patient stories in fundraising materials. A donor’s support does not entitle that donor to patient information, and a referring faith-based partner is not automatically entitled to hear about a patient’s condition.

Outside services have their own rules through Business Associate Agreements, or BAAs. These contracts establish protections when a vendor handles PHI on an organization’s behalf, whether the service is cloud storage, billing, IT support, or fundraising software. Workforce volunteers and outside business associates are distinct categories. Meanwhile, a stolen laptop, phishing email, or misdirected fax can create breach notification duties regardless of the nonprofit’s size. The Office for Civil Rights enforces HIPAA without a nonprofit exemption.

What compliance actually requires at a nonprofit's scale

For an organization in scope, the first operational check is whether the required BAAs exist. A vendor’s security features do not replace that contract. Agreements need to cover permitted uses and disclosures, safeguards, incident reporting, support for individual rights, audit rights, and return or destruction of PHI when services end. Subcontractors must be bound to the same protections. Tracking the agreements in one place and reviewing them each year, or when services change, helps keep them in line with how data is handled.

Those contracts need an internal owner. A nonprofit should appoint a privacy officer and a security officer, though a small organization can assign both roles to one person with other responsibilities. Governance also includes mapping where PHI is collected, stored, shared, and disposed of, and writing policies that distinguish covered components from non-covered functions. A Notice of Privacy Practices should be maintained online and on-site where required.

The technical work starts with individual logins, role-based access, and audit controls. Logs need to show who accessed records, when access occurred, and what changed. Audit controls are required no matter how small the organization is. Encryption at rest and in transit, TLS/HTTPS connections, and multi-factor authentication are also key safeguards to evaluate, with AES the current federal encryption benchmark. The current rule treats some implementation specifications differently from the proposed requirements below that would apply to all of them.

Workforce practice completes this foundation. Staff and volunteers should see only the PHI needed for their jobs, with documented training at hire and periodically afterward, backed by a sanctions policy. Reviewing intake forms, spreadsheets, messaging apps, and other collection points also creates an opportunity to remove unnecessary identifiers. The written procedures for incident response and disaster recovery should be tested. But if the software platform will not sign a required BAA, even excellent internal policies cannot close that gap.

The 2026 Security Rule update and what it changes in practice

HHS published a proposal to overhaul the Security Rule in the Federal Register on 6 January 2025, and the deadline for comments was March 7, 2025. As of October 2026, it is not final, and the current rule remains fully enforced. A final rule is targeted for July 2027, with a compliance deadline expected around early-to-mid 2028. Those dates may shift again. Preparation can focus on the proposed requirements without treating them as current law.

The proposal would remove the distinction between “addressable” and “required” implementation specifications. Addressable does not simply mean optional under the current framework, but the proposal would make every implementation specification mandatory. It would require encryption at rest and in transit, MFA across all systems, biannual vulnerability scanning, annual penetration testing, formal patch management timelines, network segmentation, and annual testing of technical controls. An annual, documented, repeatable assessment would cover the entire ePHI environment, including subcontractors, cloud environments, and shared systems, grounded in a comprehensive asset inventory.

Vendor accountability would change as well. Covered entities would need annual written verification that each business associate has the required technical safeguards in place, signed off by qualified cybersecurity personnel. A contract signature would not substitute for that evidence. The proposal would also require business associates to notify covered entities within 24 hours of a security incident. To prepare, nonprofits should identify their business associates, confirm current BAAs, and begin asking about documented risk analysis, encryption, MFA readiness, and incident response plans.

How the platform choice determines whether compliance is actually achievable

Software determines which policies a nonprofit can enforce in practice. A policy limiting record access has little force if the database cannot separate permissions by role. The same problem comes up when a system cannot give the nonprofit the audit trail it needs. So general-purpose databases, spreadsheet tools, and messaging apps need to be checked before they hold PHI. Familiarity is not evidence of suitable controls or BAA coverage.

Airtable limits BAA availability for Airtable AI to Enterprise Scale and gates AI features behind additional terms. Its documentation warns against storing ePHI in workspaces where Airtable AI is enabled unless supplemental AI Terms for Health Information have been accepted. The configuration and terms are decisive. A nonprofit cannot infer that every plan or feature is suitable because a vendor offers a healthcare-related agreement somewhere in its product range.

For a team evaluating alternatives, the claims “secure” and “HIPAA compliant” raise questions about access controls, audit controls, encryption, transmission security, and an applicable signed BAA. The organization can sustain the choice if it fits its workflow and budget. Tools built for case management and tools that work like spreadsheets meet different needs.

HIPAA-capable software platforms built for nonprofit human services programs

LiveImpact is built specifically for human services nonprofits, with HIPAA compliance embedded in its core architecture. Bonterra Apricot offers an established alternative, with HIPAA compliance and SOC 2 Type II certification. Its library of templates and tools for reporting are a good fit for larger human services agencies. For those agencies, the fit depends partly on how well existing templates match their programs.

PlanStreet fits organizations with complex multi-program workflows and detailed funder reporting requirements. Its Power BI integration helps with that reporting. It offers HIPAA capabilities and FedRAMP Ready status, which is not full FedRAMP authorization. Casebook takes a human services and social work focus, with intake and case note functionality. Its mid-tier, per-user pricing makes the number of people needing access relevant to affordability.

For teams seeking spreadsheet-like familiarity, Baserow offers an open-source database with GDPR, HIPAA, and SOC 2 compliance. It supports self-hosting for data control, API-first workflows, and transparent pricing. Knack Health offers HIPAA-compliant hosting, a signed BAA, encryption, and role-based access. Its flat rate starts at $499 per month, and it has no per-user fees. Nonprofits can get nonprofit pricing on annual plans, which gives them another way to pay that they can compare with platforms that charge per user.

No stated feature set establishes a deployment timetable. Implementation speed depends on workflow fit, and the available details do not support promising a launch date for any option. Where no off-the-shelf platform fits cleanly, or existing custom tools have become compliance liabilities, a product engineering partner is another route to evaluate. That route is for genuinely custom or complex needs. The partner must work with tight budgets, staff who have several jobs, and decisions that put the mission first, without assuming the nonprofit runs on the scale of a hospital.

How to determine your organization's actual obligations and where to start

Start by determining the nonprofit’s role. Does the nonprofit provide care and conduct covered electronic transactions, or handle PHI on behalf of a covered entity? Counsel familiar with healthcare privacy law is the right resource when the answer is unclear. Vendor documentation explains the platform’s capabilities.

Once the role is clear, the next step is to trace the data and the contracts together. An inventory should cover intake forms, case management systems, spreadsheets, messaging apps, cloud storage, and billing platforms, including how information is shared and disposed of. Each outside handler should then be matched to its required BAA. A platform’s inability or refusal to sign one is an immediate gap to address, giving the subsequent risk analysis a concrete boundary.

The documented risk analysis should assess where ePHI lives, who can access it, and the realistic threats, followed by a remediation plan with prioritized timelines. The people named as privacy and security officers should be in charge of that work, even if one person holds both roles. Preparation for the proposed rule can proceed through vendor questions about safeguards and response plans, with BAA templates revisited once a final rule establishes new requirements. The purpose is ultimately client protection. A breach involving vulnerable people can harm trust even without a fine, so handling information with care is part of the nonprofit’s mission and goes beyond a separate administrative task.