HIPAA privacy officer: what the rule requires, who needs one and what it costs
HIPAA requires every covered entity to designate a privacy official (45 CFR 164.530(a)).[1] The Security Rule separately requires covered entities and business associates to identify a security official (45 CFR 164.308(a)(2)).[2] "HIPAA privacy officer" is the common name for the first role.
This guide is for US health tech companies, practices and their vendors. It covers what the rule says, who it applies to, how the role compares with a GDPR data protection officer (DPO), and what published fractional privacy officer services cost. If you also serve patients or users in the EU, the GDPR DPO self-check gives a rough first answer on whether you need a DPO as well.
What does a HIPAA privacy officer do?
The Privacy Rule's administrative requirements set out two designations in 164.530(a)(1):[1]
- Privacy official. "A covered entity must designate a privacy official who is responsible for the development and implementation of the policies and procedures of the entity."
- Contact person or office. A covered entity must also designate a contact person or office responsible for receiving complaints, and able to give further information about matters covered by the entity's notice of privacy practices (164.520).
Under 164.530(a)(2), the covered entity must document these designations as required by paragraph (j).[1]
The Security Rule adds a separate role. Under "assigned security responsibility", a covered entity or business associate must identify the security official responsible for developing and implementing the Security Rule's policies and procedures (164.308(a)(2)).[2] The two provisions are separate. Neither text says the two roles must be held by different people.
Who must have a HIPAA privacy officer?
The privacy official rule applies to covered entities. 45 CFR 160.103 defines a covered entity as:[3]
- a health plan;
- a health care clearinghouse; or
- a health care provider who transmits any health information in electronic form in connection with a transaction covered by the HIPAA rules.
A business associate is different. Under the same section, it is a person who, on behalf of a covered entity and other than as a member of its workforce, creates, receives, maintains or transmits protected health information for a regulated function or activity (such as claims processing, data analysis, billing or practice management), or provides certain services involving protected health information, such as legal, actuarial, accounting, consulting, data aggregation, management, administrative, accreditation or financial services.[3]
Many health tech and SaaS vendors that serve hospitals, practices or health plans may be business associates rather than covered entities. Which one you are depends on the definitions, so check them against your business with a HIPAA lawyer. The practical difference:
- Covered entity: must designate a privacy official and a complaints contact (164.530(a))[1] and identify a security official (164.308(a)(2)).[2]
- Business associate: must identify a security official (164.308(a)(2)).[2] The privacy official requirement in 164.530(a) is written for covered entities.[1]
Can a HIPAA privacy officer be outsourced or fractional?
The rule says a covered entity must "designate" a privacy official.[1] The text of 164.530(a) does not say the official must be an employee, and it does not address outsourcing either way. It also does not set qualifications for the role.
Fractional privacy officer services exist. North Privacy Advisors, for example, publishes "Fractional Chief Privacy Officer" retainers for healthcare practices and small and mid-sized businesses (prices below).[7] Whether a particular arrangement meets your HIPAA obligations is a question for a HIPAA lawyer. The covered entity, not the vendor, carries the obligation to designate the official.
The GDPR is more explicit for its own role: Article 37(6) says a DPO may be a staff member or work under a service contract.[4] The guide to DPO as a service and outsourced DPOs explains that model.
HIPAA privacy officer vs. GDPR data protection officer
They are different roles under different laws. A company that handles health data of both US and EU patients may need both.
| HIPAA privacy official | GDPR data protection officer | |
|---|---|---|
| Legal basis | 45 CFR 164.530(a)[1] | GDPR Articles 37 to 39[4] |
| Who must have one | Every covered entity | Controllers and processors that meet an Article 37(1) trigger, or where national law requires one |
| Main duty | Developing and implementing the entity's privacy policies and procedures | Informing and advising, monitoring compliance, advising on DPIAs, cooperating with the supervisory authority (Art. 39) |
| Independence | No GDPR-style independence rules in 164.530(a) | No instructions on the tasks, no dismissal or penalty for doing them, reports to highest management (Art. 38(3)); no conflict of interests (Art. 38(6)) |
| Staff or external | The text says "designate" and does not address it | Staff member or service contract (Art. 37(6)) |
| Contact details | A contact person or office for complaints; designations documented | Published and communicated to the supervisory authority (Art. 37(7)) |
Because the DPO must avoid conflicts of interests (Art. 38(6)), check before giving one person both roles that their other duties do not conflict with the DPO tasks. The EDPB-endorsed DPO guidelines give senior management roles as examples that can conflict.[5]
Health tech companies with EU patients or users
A US health tech company can be subject to the GDPR as well as HIPAA. Under GDPR Article 3(2), the GDPR applies to a company outside the EU that offers goods or services to people in the EU or monitors their behavior there.[4]
- Health data is a special category. Article 9 treats data concerning health, genetic data and biometric data used to identify a person as special categories of personal data, with stricter conditions for processing.[4]
- When a DPO becomes mandatory. If your core activities consist of processing special category data on a large scale, Article 37(1)(c) requires a DPO.[4]The DPO guidelines give a hospital processing patient data as an example of large-scale processing, and an individual physician's patient data as an example that is not. They also list fitness and health tracking via wearables as an example of regular and systematic monitoring.[5]
- EU representative. With no EU establishment, you usually also need an EU representative under Article 27. The exemption in Article 27(2) does not cover large-scale processing of special category data.[4] See the guide to the GDPR Article 27 representative.
Read when US companies need a DPO under GDPR for the full rules.
What do fractional privacy officer services cost?
Few providers publish prices for HIPAA privacy officer services. North Privacy Advisors does, in US dollars, checked 20 November 2026: Fractional Chief Privacy Officer retainers of $2,500, $3,500 and $5,000 per month, with a 3-month minimum.[7] These are privacy officer services for healthcare practices and small businesses, not GDPR DPO plans.
| Provider | Plan | Price (USD) | What's included | Source |
|---|---|---|---|---|
| North Privacy Advisors | Fractional Chief Privacy Officer, Starter | $2,500 / monthPublished as: $2,500 per month. | For most solo practices and 1–2 location clinics (healthcare practices and SMBs).Monthly retainer; 3-month minimum. | Price page: North Privacy Advisors, checked |
| North Privacy Advisors | Fractional Chief Privacy Officer, Standard | $3,500 / monthPublished as: $3,500 per month. | For multi-location practices and complex vendor stacks.Monthly retainer; 3-month minimum. | Price page: North Privacy Advisors, checked |
| North Privacy Advisors | Fractional Chief Privacy Officer, Premium | $5,000 / monthPublished as: $5,000 per month. | For specialty groups, 3+ locations and high-risk profiles.Monthly retainer; 3-month minimum. | Price page: North Privacy Advisors, checked |
| North Privacy Advisors | HIPAA Risk Analysis | $750 | HIPAA risk analysis, listed separately on the provider's site. | Price page: North Privacy Advisors, checked |
One provider is not a market. For GDPR DPO services, the index of published outsourced DPO prices lists plans from 9 providers, each with its source and date.
Frequently asked questions
Is a HIPAA privacy officer required?
Yes, for covered entities. 45 CFR 164.530(a) says a covered entity must designate a privacy official responsible for developing and implementing its privacy policies and procedures, and a contact person or office for complaints. Both designations must be documented.[1]
Do business associates need a HIPAA privacy officer?
The privacy official rule in 164.530(a) is written for covered entities. The Security Rule in 164.308(a)(2) requires both covered entities and business associates to identify a security official.[1][2]
Can the HIPAA privacy officer be outsourced?
The rule says a covered entity must designate a privacy official. It does not say the official must be an employee, and it does not address outsourcing. Ask a HIPAA lawyer whether a specific arrangement meets the rule.[1]
Is a HIPAA privacy officer the same as a GDPR DPO?
No. They come from different laws with different duties. The GDPR DPO has tasks set by Article 39 and independence protections in Article 38. 164.530(a) contains no GDPR-style independence rules for the privacy official.[1][4]
Does a health tech company with EU users need a DPO?
It may. Health data is a special category under GDPR Article 9. If the GDPR applies and the core activities involve processing health data on a large scale, Article 37(1)(c) requires a DPO.[4]
Next steps
- Check whether GDPR may also require a DPO (seven yes/no questions).
- Learn how outsourced DPO services work.
- Compare published DPO prices, with sources.
- Building software for health care customers? See GDPR compliance for SaaS companies.
Sources
- 45 CFR 164.530, HIPAA Privacy Rule administrative requirements (eCFR) (accessed )
- 45 CFR 164.308, HIPAA Security Rule administrative safeguards (eCFR) (accessed )
- 45 CFR 160.103, HIPAA definitions (eCFR) (accessed )
- Regulation (EU) 2016/679 (General Data Protection Regulation), official text on EUR-Lex (accessed )
- Article 29 Working Party, Guidelines on Data Protection Officers (WP243 rev.01), endorsed by the EDPB (accessed )
- Article 29 Working Party, Guidelines on Data Protection Officers (WP243 rev.01), full text (PDF) (accessed )
- North Privacy Advisors, Fractional Chief Privacy Officer (price page) (accessed )