HIPAA Compliance for Tribal Health Clinics and IHS Programs

Kevin Henry

HIPAA

Published Updated

9 minutes read
Share this article
HIPAA Compliance for Tribal Health Clinics and IHS Programs

Which tribal health clinics and IHS programs are covered by HIPAA?

HIPAA coverage depends on the organization’s legal and operational role—not simply on whether it serves American Indian and Alaska Native patients. HIPAA generally applies to health plans, health care clearinghouses, and health care providers that conduct specified electronic transactions. The federal definition of a health plan expressly includes the Indian Health Service program under the Indian Health Care Improvement Act (IHCIA). The statutory definition of “health plan” and the IHS guidance to Tribes describe how IHCIA programs operated by Tribes under Title I contracts or Title V compacts may fall within that category.

A tribal clinic may also be a HIPAA-covered health care provider if it furnishes health care and conducts a standard HIPAA transaction electronically. Some organizations may have more than one basis for coverage. Conversely, tribal status, receiving IHS funding, or using an electronic health record does not by itself answer whether a particular legal entity is covered; assess the entity, program, and transactions involved.

IHS programs are subject to HIPAA when acting in covered-entity roles, but HIPAA does not necessarily govern every piece of personal information held by IHS. IHS explains that some records may also be governed by the Privacy Act, 42 CFR Part 2, or other applicable law. Its privacy FAQ distinguishes HIPAA-protected health information from other protected information.

How do electronic claims submissions affect covered entity status?

A health care provider generally becomes a covered entity when it transmits health information electronically in connection with a transaction for which HHS has adopted a HIPAA standard. Examples include electronic claims, eligibility inquiries, and referral authorization requests. This is the key test for many clinics assessing HIPAA covered entity electronic transactions; using email or an electronic record system alone is not the same as conducting a standard transaction.

Using a billing company or other intermediary to submit claims does not necessarily keep a clinic outside HIPAA. HHS explains that a provider can be covered when it conducts standard transactions through a third party on its behalf. See the HHS summary of the HIPAA Privacy Rule and the definitions in 45 CFR § 160.103.

For tribal health organizations, electronic billing may be one coverage route even when the organization’s IHCIA program status provides another. Review which legal entity submits or is responsible for the transactions, whether the transactions are standard HIPAA transactions, and whether any contracted billing arrangement affects the analysis.

What safeguards does the Privacy Rule require for protected health information?

The Privacy Rule requires covered entities to use reasonable and appropriate administrative, technical, and physical safeguards to protect protected health information (PHI) from impermissible use or disclosure and to limit incidental uses and disclosures. The rule sets a flexible standard rather than prescribing one identical set of safeguards for every clinic. See HHS guidance on the Privacy Rule safeguards standard and 45 CFR § 164.530(c).

In practice, a clinic’s protected health information handling procedures should address who may access records, how staff verify a requester’s identity and authority, how records are secured, and how workforce members are trained on applicable privacy policies. The Security Rule adds specific requirements for electronic PHI, including administrative, physical, and technical safeguards; it applies to electronic PHI rather than paper or oral information. See the HHS Security Rule summary.

These safeguards work alongside rules on permitted uses and disclosures, patient access, authorizations, complaints, and other Privacy Rule duties. A privacy policy should not treat the word “safeguards” as a substitute for addressing those separate requirements.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

How can a tribal organization designate health care components under hybrid entity status?

A tribal organization may elect hybrid entity status only if it is a single legal entity that is already a covered entity and performs both covered and non-covered functions. It can then designate one or more health care components for HIPAA purposes. A Tribe and a legally separate clinic or nonprofit are not automatically a single entity simply because they are affiliated or share services; confirm the legal structure before making a designation.

The designation must include any component that would itself meet the definition of a covered entity if it were a separate legal entity. A health care component may also include a component only to the extent that it performs covered functions. The covered entity remains responsible for compliance and must protect PHI when it moves between the health care component and other parts of the organization. See 45 CFR § 164.105 and HHS’s guidance on hybrid entity components.

A carefully scoped health care components policy can identify which services, units, and support functions are included; explain how staff who work across components may use information; and describe controls for shared records, systems, and administrative services. These details help operationalize the designation, but they do not replace the regulatory requirements or the organization’s broader HIPAA policies.

How should clinics document hybrid entity policies and excluded public health activities?

A covered entity must maintain a written or electronic record of its hybrid entity designation and keep that documentation for six years from its creation or the date it was last in effect, whichever is later. The designation should accurately identify the health care component or components and include every component that must be included under the regulation. See the documentation requirements in 45 CFR § 164.105(c).

When a tribal organization performs public health work as well as covered health care functions, assess the functions and legal boundaries rather than treating all public health activity as automatically outside HIPAA. A public health unit may be outside the designated health care component if it does not perform covered functions or support that makes it part of the component. But the covered health care component still must follow HIPAA when it uses or discloses PHI, including when sharing information with a public health authority. The Privacy Rule permits certain disclosures to public health authorities authorized by law, subject to the applicable conditions in 45 CFR § 164.512(b).

As a practical step, document the organization’s legal structure, component boundaries, responsible officials, workforce access rules, shared-service arrangements, and how information may move between covered and non-covered functions. Review the designation when organizational responsibilities or program operations change. These are useful governance practices for keeping the record accurate, not additional federal documentation fields imposed by the hybrid-entity rule.

Which IHS procedures govern HIPAA forms and health information handling?

For IHS employees and facilities, the Indian Health Manual’s Part 2, Chapter 7 sets out IHS procedures addressing the HIPAA Privacy Rule, the Privacy Act, the HITECH Act, the IHS Notice of Privacy Practices, required forms, and procedures for transmitting or receiving information by fax. It also covers processes such as authorizations, access to records, accounting for disclosures, and verifying the identity or authority of people requesting PHI. The Indian Health Manual’s Health Information Management chapter addresses record confidentiality, authorized access, and staff responsibilities.

IHS procedures are IHS policy; they do not automatically serve as a tribal organization’s own policies. Tribal and urban health facilities can use IHS materials as references and adapt forms to their own legal and operational requirements. IHS California Area guidance specifically encourages Tribal and Urban facilities to modify federal-facility forms for local use with the organization’s legal counsel. Check the date and status of any form before adopting it: the IHS forms and policies page lists a forms collection with an August 2019 expiration date, so that collection should not be assumed current without verification.

For IHS workforce members, current IHS privacy training guidance also says to use approved secure transmission methods for electronic PHI and to access records only as needed for assigned duties. Tribal organizations should establish their own applicable policies, training, and incident-reporting procedures, taking into account HIPAA, the HITECH Act, the Privacy Act where applicable, 42 CFR Part 2 where applicable, Tribal law, and their specific agreements.

In short, determine coverage based on the organization’s legal status and transactions, protect PHI with safeguards suited to actual operations, and document any hybrid entity boundaries in writing. Use current IHS procedures as a reference where appropriate, while ensuring each tribal organization’s own policies match its responsibilities.

FAQs

Are IHS programs covered by HIPAA?

Yes, IHS programs are subject to HIPAA when they operate in a covered-entity role. The HIPAA definition of health plan includes the Indian Health Service program under the IHCIA, and IHS may also have provider-related obligations. HIPAA does not necessarily apply to every type of personal information IHS maintains; the Privacy Act, 42 CFR Part 2, and other rules may also apply.

Can a tribal health clinic become a HIPAA covered entity by submitting electronic claims?

Yes. A health care provider that transmits claims electronically in connection with a standard HIPAA transaction is generally a covered entity. Having a billing company submit claims on the clinic’s behalf does not automatically remove that responsibility. Electronic communications that are not standard HIPAA transactions, such as ordinary email, do not by themselves establish covered-provider status.

Can tribal health organizations use hybrid entity status?

Yes, if the organization is a single legal entity that is a covered entity and also performs non-covered functions. It must designate its health care components and include components that would independently qualify as covered entities. The designation must be documented and retained for the period required by 45 CFR § 164.105.

What IHS procedures apply to HIPAA forms and health information handling?

IHS employees and facilities should consult the Indian Health Manual’s Part 2, Chapter 7 for HIPAA, Privacy Act, HITECH, notice, form, and information-transmission procedures, along with Part 3, Chapter 3 for health information management responsibilities. Tribal and urban facilities may adapt IHS materials for local use, but should verify that forms are current and review local policies with appropriate legal counsel.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Related Articles