Blog ·
Jira HIPAA compliance: what Atlassian covers, and the reviews you still own
Jira HIPAA compliance is possible on Jira Cloud, with conditions. Atlassian will sign a Business Associate Agreement (BAA) for Jira on the Standard, Premium and Enterprise plans, and Free and trial plans are not eligible. After signing, you tag the app, follow Atlassian's HIPAA Implementation Guide, and keep protected health information (PHI) out of the places that guide names. That gets the tool ready. It does not do the recurring work HIPAA asks of your organisation, such as the risk analysis, the access reviews and the periodic evaluation. This guide covers both halves: the setup Atlassian requires, and a way to make the recurring reviews arrive as tickets on time.
Statements about Atlassian's HIPAA programme are as of October 2026, read from Atlassian's own trust and support pages. This is a practical guide, not legal advice. Your compliance officer decides what your obligations are.
Is Jira HIPAA compliant? #
No software is HIPAA compliant on its own, and Atlassian says so plainly. Its support page on HIPAA puts it this way:
It's important to remember that HIPAA compliance is a shared responsibility between Atlassian and you. Completing these steps won't automatically guarantee your compliance with HIPAA, you must also ensure that you follow HIPAA best practices.
What Atlassian offers is a set of protections and a contract. Its trust page lists, among other things, security measures for protecting PHI, "an annual HIPAA Security Attestation, Gap Assessment, and Security Risk Analysis", and the regular review of its own HIPAA policies. Those cover Atlassian's side. Your side is how you configure and use the product, and the administrative work the Security Rule expects from any covered entity or business associate.
Which plans and apps can sign a BAA #
As of October 2026, Atlassian's HIPAA Implementation Guide says it can sign BAAs for these cloud apps:
| App | BAA available? |
|---|---|
| Jira | Yes, Standard, Premium and Enterprise |
| Jira Service Management | Yes, Standard, Premium and Enterprise |
| Confluence | Yes, Standard, Premium and Enterprise |
| Jira Product Discovery | Yes, Standard, Premium and Enterprise |
| Rovo (Search, Chat, Agents, in-app AI) | Yes, activated through a support ticket |
| Any app on a Free or trial plan | No |
| Atlassian Government Cloud | Not available |
Two details matter for planning. The BAA page says you must have a BAA in place before PHI is uploaded. And on Standard and Premium you request it yourself from Atlassian Administration, while Enterprise customers go through their Atlassian representative.
The setup Atlassian asks for #
Atlassian's support pages list three steps, in this order:
- Sign the BAA. An organisation admin goes to Atlassian Administration, then Security, Data protection, HIPAA compliance, and selects Sign a BAA. The form asks for your legal name, the signatory and their email, and your organisation's address. The signatory receives the agreement by email and has 90 days to execute it; after that the link expires and you go through Atlassian Support.
- Tag the apps that will hold PHI, so they are identified and treated under the HIPAA configuration.
- Configure each app following the HIPAA Implementation Guide.
If you subscribe to a collection that includes apps outside the HIPAA programme, the guide says to deactivate those apps. Its example is the Customer Service Management app in the Service Collection.
Where PHI must never go #
This is the part of the guide most worth printing for your Jira admins. It tells customers to:
Ensure that you don't input PHI into Atlassian Support tickets, surveys, or any metadata or naming fields (such as Confluence Space Names, file names, AI agent names/references, and Jira App configurations).
In practice that means:
- Project names, board names and filter names stay generic. "Cardiology intake" is fine. A patient name in a filter title is not.
- Automation rules must not email PHI. The guide makes Jira admins responsible for ensuring automation rules are not configured to send email notifications that include PHI.
- App configurations carry no PHI. Anything you type into a Marketplace app's settings screen counts.
- Support tickets to Atlassian describe the problem without the patient data in it.
The guide also says that Jira and Jira Service Management can keep email and push notifications on, because Atlassian now supports notification templates that leave out content that could contain PHI. Confluence push notifications, by contrast, must be turned off.
Third-party apps are your call #
This catches teams out. The guide says the BAA you sign with Atlassian covers only the eligible Atlassian apps, and that you are responsible for configuring HIPAA needs for every third-party app integrated with them, "including having a signed Business Associate Agreement (BAA) with all relevant third-party apps."
So before you install any Marketplace app on a site that holds PHI, ask two questions:
- Will this app read, store or send PHI? An app that reads issue content, exports data or posts to another service probably will.
- If it does, will the vendor sign a BAA? If not, keep the app off the HIPAA-tagged site, or make sure nothing it touches contains PHI.
That applies to the scheduling apps in this guide too, ours included. A recurring rule's title and description are app configuration in the guide's sense, and the tickets it creates carry whatever text the template holds. Write templates with no PHI in them, and put patient details, if they belong in Jira at all, in tickets your staff fill in by hand.
The recurring work HIPAA asks for #
The tool setup happens once. The Security Rule's administrative safeguards keep coming back. The U.S. Department of Health and Human Services summary of the Security Rule says a regulated entity must implement procedures to "regularly review its records to track access to ePHI and detect security incidents", "periodically evaluate the effectiveness of security measures", and "regularly reevaluate potential risks to ePHI". It also describes a "periodic technical and non-technical assessment" of how well policies and procedures meet the rule.
None of those come with a reminder. A typical calendar looks like this; the cadence is your organisation's decision, so treat this column as an example to adjust:
| Review | Example cadence | What goes wrong without a ticket |
|---|---|---|
| Information system activity review (access logs, audit logs) | Monthly | Odd access goes unnoticed until it is an incident |
| User access review (who can see PHI-holding projects) | Quarterly | Leavers and role changes keep access they should not |
| Security risk analysis update | Yearly, and after major changes | The analysis describes a system you no longer run |
| Evaluation of policies and procedures | Yearly | Policies drift from practice |
| Security awareness training reminder | Yearly | Nobody chases staff who did not complete it |
| Contingency plan and backup restore test | Yearly | The first restore attempt happens during an outage |
| Business associate agreement inventory | Yearly | A vendor touching PHI has no BAA on file |
A recurring review should create its own ticket, assigned and dated, before it is due. A spreadsheet or one person's calendar is a single point of failure, and an auditor will ask for evidence that each review happened, not only that you meant to do it.
Three ways to make the reviews create tickets #
| By hand | Jira Automation scheduled rule | Recurring Work Items for Jira | |
|---|---|---|---|
| Effort | Every ticket, every cycle | One rule per review, written once | One rule per review, chosen from a form |
| Schedule | Whoever remembers | Fixed rate or cron expression | Daily, weekly, or monthly on a day or a weekday, every N months |
| Lives in | Somebody's calendar | The automation rules list | The compliance project itself |
| Evidence a run happened | The ticket, if it was made | The rule's audit log | Run history: created, skipped or failed, with the reason |
By hand #
Workable for a small practice with five or six dates a year. One person owns the calendar and clones last cycle's ticket. Our Jira task template guide makes those clones quick. The weak point is the owner's holiday.
Jira Automation #
A scheduled rule can create a work item at a fixed rate or on a cron expression. It covers most of the calendar above. Two cautions apply here: a date like "the first working day of the quarter" is awkward in cron (see our Jira cron expression guide), and rule runs count toward your plan's automation usage, explained in Jira Automation pricing. And as above, the rule must not send PHI by email.
A scheduling app #
Recurring Work Items for Jira creates issues on a schedule, with rules scoped to one project. A compliance team's calendar lives inside the compliance project instead of a site-wide rules list other admins edit, and a project administrator turns it on for that project alone. Remember the third-party rule above: confirm with your compliance officer before installing any app on a HIPAA-tagged site, and keep its templates free of PHI.
Set up the review calendar #
Whichever tool you choose, the setup is the same shape. With Recurring Work Items it runs like this:
- Create a compliance project with no PHI in its name, its issues or its templates. It tracks that a review happened and links to where the evidence lives.
- Turn the app on for that project only.
- Create one rule per review. A quarterly access review is a monthly rule repeating every 3 months; a yearly risk analysis repeats every 12 months.
- Pick the day, such as "the 1st" or "the first Monday of the month".
- Set working days and holidays, then choose Move it to the next working day under If it falls on a non-working day, so a review that would land on a weekend moves to a working day: a new rule runs on the day it falls on, holiday or not.
- Title each cycle distinctly with tokens, for example
Quarterly access review {{now.year}}, so last quarter's ticket and this quarter's never get confused. - Fill in the template: the owner, a due date a set number of days after the run, a label such as
hipaa-review, and a description naming the safeguard and the checklist to follow. - Add subtasks where the review has steps: export access list, compare to roster, remove stale access, record sign-off.
The run history then answers the auditor's first question, which is whether the review ticket was raised, and the ticket's own history answers the second, which is who closed it and when.
When the manual way is enough #
A scheduled calendar pays off once the reviews outgrow one person's memory. You may not need one if:
- you are a small practice with a handful of dates you already track reliably;
- you run a dedicated compliance platform that assigns and evidences these reviews already;
- Jira holds no PHI and no compliance work, and is only used by your software team.
In that last case, the simplest HIPAA answer for Jira is to keep PHI out of it entirely.
FAQ #
Is Jira HIPAA compliant? Atlassian will sign a BAA for Jira on Standard, Premium and Enterprise plans, and provides an implementation guide. Compliance itself is shared: Atlassian covers its side, and you are responsible for configuration and your own safeguards.
Can I use Jira Free for PHI? No. As of October 2026 Atlassian says Free and trial plans are not eligible to sign a BAA, and a BAA must be in place before PHI is uploaded.
Does Atlassian's BAA cover Marketplace apps? No. The implementation guide says the BAA covers only the eligible Atlassian apps, and that you need BAAs with relevant third-party apps yourself.
Can Jira remind us about HIPAA reviews? Not from a date field on its own. A scheduled rule, in Jira Automation or an app like Recurring Work Items for Jira, can create each review ticket ahead of its due date. Our Jira for legal teams guide covers the wider compliance calendar.