Patient Recruitment Marketing Agency Security Risk Assessment Checklist
Use this checklist to examine how your agency and its clients collect, access, use, transmit, and retain patient information. Whether HIPAA applies depends on the parties’ roles and activities—not simply on whether a project involves healthcare or recruitment.
How to inventory patient information and assess security risks
Start by identifying whether your work involves protected health information (PHI), including electronic PHI (ePHI). Record what information is collected—such as names, contact details, medical information, eligibility answers, or recruitment status—and why it is used. Identify which organization creates, receives, maintains, or transmits it, and whether the agency handles it on behalf of a HIPAA covered entity or another business associate.
Map the full data path, from an advertisement or referral source through landing pages, patient recruitment forms, CRM systems, analytics tools, email platforms, file transfers, backups, and subcontractors. Include data stored in test accounts, exports, logs, and support tickets. Note where data resides, who can access it, how it moves, and when it is deleted.
The HIPAA Security Rule risk analysis covers potential risks and vulnerabilities to the confidentiality, integrity, and availability of all ePHI an organization creates, receives, maintains, or transmits. HHS says there is no single required method or template. Document the systems and information in scope, relevant threats and vulnerabilities, existing safeguards, likelihood and impact of potential events, and the resulting risk priorities. Link each priority to a remediation action, accountable owner, target date, and follow-up review. See HHS guidance on HIPAA Security Rule risk analysis and its explanation of risk analysis and risk management.
- Inventory systems, applications, devices, vendors, and locations that handle ePHI.
- Map data flows, including third-party tags, integrations, exports, and backups.
- Assess threats such as account compromise, misdirected files, excessive access, loss of a device, and unintended disclosure through web technologies.
- Prioritize risks based on potential impact and likelihood; document why a risk is accepted, reduced, transferred, or avoided.
- Reassess after material changes to campaigns, systems, vendors, or operations.
What safeguards should a business associate agreement require?
If an agency performs services for a covered entity that involve creating, receiving, maintaining, or transmitting PHI on the entity’s behalf, the agency may be a business associate and generally needs a written HIPAA business associate agreement (BAA). A BAA is not required just because an agency markets healthcare services; the parties’ actual functions and PHI access matter. An agency should establish its subcontractor arrangements before allowing subcontractors to handle PHI. See HHS guidance on business associates.
The BAA should set the permitted and required uses and disclosures of PHI, prohibit other uses and disclosures, require appropriate safeguards, and require the agency to report impermissible uses, disclosures, and security incidents. It must also address subcontractors that handle PHI, cooperation with applicable individual rights requests, access to relevant records for HHS oversight, termination for material violations, and return or destruction of PHI when the agreement ends if feasible. See HHS’s required BAA provisions.
Distinguish the BAA’s legal requirements from additional contract protections you negotiate. Consider defining approved systems and data flows, security-review evidence, incident contacts, a prompt notice deadline shorter than the federal outer limit where appropriate, investigation cooperation, deletion verification, and advance notice of subcontractor changes. A BAA does not itself authorize every marketing use or disclosure of PHI; the Privacy Rule’s separate requirements still apply.
How to secure access to patient data and marketing systems
Use unique accounts, strong authentication, and permissions limited to each person’s work. Role-based access control (RBAC) can help assign permissions by job function, but it is an implementation approach—not a phrase the Security Rule specifically requires. Review access when responsibilities change and promptly disable accounts when workers or vendors no longer need them. Avoid shared credentials, unrestricted administrator accounts, and routine use of production PHI in testing.
Set up audit logging for relevant systems and review logs for unusual access, exports, permission changes, and failed sign-ins. Use secure file-transfer methods and protect ePHI with encryption at rest and in transit where reasonable and appropriate based on the risk analysis. Under the Security Rule, encryption implementation specifications are addressable: an organization must assess whether they are reasonable and appropriate and, if not, document its decision and implement an appropriate alternative where applicable. Encryption alone does not replace access, integrity, availability, or incident safeguards. See the HHS summary of the HIPAA Security Rule.
- Separate production accounts and data from test environments; use de-identified or synthetic test data when practical.
- Require individual accounts and review privileged access on a defined schedule.
- Protect devices and exports, and establish secure processes for remote access and file sharing.
- Document encryption decisions and any alternative safeguards selected through risk analysis.
How to audit tracking pixels and advertising data flows
Audit every tag, pixel, software development kit, analytics integration, and advertising conversion tool on recruitment pages. Inspect what each technology receives, including URL paths and query strings, form fields, page events, identifiers, IP addresses, and referral data. Test forms and confirmation pages in a controlled environment, review network requests, and verify whether sensitive fields or identifiers are sent to outside platforms.
A tracking pixel may create a disclosure concern when data sent to a third party includes PHI. Do not assume that a vendor’s general privacy settings or a BAA with the agency makes a pixel safe. Review the actual data flow, the purpose of each disclosure, the recipient’s role, and whether the disclosure is permitted. Disable unnecessary tags on pages that collect or expose patient information, block sensitive form values from analytics, and document approved configurations.
Apply the legal context carefully: HHS’s tracking-technology bulletin states that HIPAA applies when data collected or disclosed through tracking technologies includes PHI. However, HHS also notes that a federal district court vacated the portion of its guidance that treated an IP address linked to a visit to an unauthenticated public webpage about a specific health condition or provider as automatically triggering HIPAA obligations. Do not treat every visit to a public health webpage as PHI; assess the actual information, context, and data flow. See HHS guidance on online tracking technologies.
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk AssessmentWhat patient authorizations are required for marketing use?
Before using or disclosing PHI for a communication that qualifies as marketing under HIPAA, confirm whether a valid authorization is required and whether a narrow exception applies. The Privacy Rule generally requires an individual’s authorization for marketing uses or disclosures, subject to limited exceptions. When an authorization is required, it must be written in plain language and include the required information, such as what information will be used or disclosed, who may use or disclose it, who may receive it, its expiration, and the individual’s right to revoke. If the covered entity receives remuneration from a third party for the marketing communication, the authorization must state that fact. See HHS marketing guidance.
Do not assume that a standard lead-form checkbox, general website consent, or BAA is a valid HIPAA authorization. Confirm that the form and workflow meet the applicable authorization requirements, retain the signed authorization as required, and route patient authorization revocation requests to the covered entity. Revocation generally must be in writing and becomes effective when the covered entity receives it; it does not undo actions already taken in reliance on a valid authorization. See HHS guidance on revoking an authorization.
Patient recruitment for research needs separate analysis; it is not automatically the same thing as marketing under HIPAA. HHS says the preparatory-to-research provision may allow a covered entity’s workforce researcher to identify potential participants without removing PHI from the entity. An outside researcher generally cannot use that provision to contact prospective participants; an IRB or Privacy Board may grant a partial waiver of authorization for recruitment in appropriate circumstances. Confirm the applicable HIPAA, research, and institutional requirements before sharing a recruitment list. See HHS guidance on research recruitment under HIPAA.
How to assess vendors and prepare for security incidents
List every vendor and subcontractor that can access PHI or systems containing it. For each, record the service provided, data accessed, access method, storage location, subcontractors, security contact, and contract status. Determine whether the vendor is acting as a business associate or subcontractor for the work at issue, and put the required written assurances in place before sharing PHI. A BAA with the agency does not automatically cover an advertising platform or another downstream provider.
Maintain a response plan that identifies who receives alerts, who can contain an incident, how evidence is preserved, and how the agency promptly informs the covered entity. Include suspected misdirected files, compromised accounts, lost devices, malware, and unexpected pixel transmissions. The HIPAA Breach Notification Rule requires a business associate to notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 calendar days after discovery; the parties may agree to a shorter contractual deadline. See the HHS Breach Notification Rule guidance.
What to review during retention and agency offboarding
Set retention and deletion periods for campaign files, form submissions, exports, test data, logs, and backups according to the BAA, the client’s instructions, and other applicable legal or contractual requirements. Do not assume HIPAA sets one universal retention period for every patient record. HIPAA does require specified Security Rule documentation to be retained for six years from its creation or the date it was last in effect, whichever is later; that documentation rule is not a general six-year retention mandate for all PHI.
When the agency relationship ends, revoke user accounts, API keys, tokens, and vendor access; transfer required records in an agreed usable format; remove tags and integrations; and return or destroy PHI if feasible. If return or destruction is infeasible, the BAA must extend its protections to the retained information and limit further uses and disclosures to the purposes that make return or destruction infeasible. Keep a record of completed access removal, transfers, and deletion or any documented exception. See HHS guidance on PHI after a business associate relationship ends and the Security Rule documentation requirements.
In short, a reliable security review maps PHI from collection through deletion, documents and prioritizes risks, limits access, checks every advertising data flow, confirms the right BAA and authorizations, and verifies that incident and offboarding procedures work in practice.
FAQs
When should a patient recruitment marketing agency sign a business associate agreement?
When the agency performs services for a HIPAA covered entity or business associate and, on its behalf, creates, receives, maintains, or transmits PHI, the parties generally need a BAA before the agency handles that information. Whether the agreement is required depends on the actual service and data access, not just the agency’s title. See HHS business associate guidance.
Can advertising pixels collect protected health information from patient recruitment forms?
Yes. A pixel or other tracking technology may transmit PHI if the information it collects or sends identifies an individual and relates to health information. Audit the actual requests and payloads, prevent unnecessary transmission of form values or identifiers, and assess each disclosure under HIPAA. HHS has also noted that a court vacated part of its guidance concerning IP addresses linked to visits to certain unauthenticated public webpages, so a webpage visit alone should not be treated as automatically establishing PHI. See HHS online tracking guidance.
What must a risk assessment document and prioritize?
It should cover the ePHI in scope; the systems and data flows that create, receive, maintain, or transmit it; relevant threats and vulnerabilities; existing safeguards; and the likelihood and potential impact of risks. It should prioritize risks and connect them to mitigation decisions and follow-up. HHS does not prescribe one universal risk-analysis method or scoring template. See HHS risk-analysis guidance.
How should patient data be handled when an agency contract ends?
Follow the BAA: return or destroy PHI if feasible, including PHI held by relevant subcontractors. If return or destruction is infeasible, document the reason, continue protecting the retained PHI under the BAA, and limit further use or disclosure to the purpose that makes deletion or return infeasible. Also revoke access and credentials, transfer required records, and document completed offboarding. See HHS guidance on termination and PHI.
Table of Contents
- How to inventory patient information and assess security risks
- What safeguards should a business associate agreement require?
- How to secure access to patient data and marketing systems
- How to audit tracking pixels and advertising data flows
- What patient authorizations are required for marketing use?
- How to assess vendors and prepare for security incidents
- What to review during retention and agency offboarding
- FAQs
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk Assessment