HIPAA · For security and compliance leads with US healthcare customers
Ready before the first patient record arrives.
EA drafts your HIPAA risk analysis and safeguard policies from what you already hold. It lists each security clause in a customer’s business associate agreement beside the safeguard that covers it. Your HIPAA Security Officer approves the programme before the customer goes live.
Try EA free. No card needed.
Organisations that run work on EA
The work
A rule written for US hospitals now reaches your systems.
Patient data takes many routes
Through your platform, your backups, your support desk and your logs. The risk analysis has to follow each route to its end.
Each agreement reads differently
US customers tend to send their own business associate agreement, each asking for safeguards in its own words. And each subcontractor that touches the data needs one from you.
Go-live is already in the diary
The customer’s start date is set, and the safeguards behind the agreement need to be in place, and written down, by then.
Finish the programme once, and each new US customer starts from it.
What EA does
The programme, safeguard by safeguard.
From the first map of patient data to the customer’s agreement, EA drafts and your team decides.
01 / 05
- EA
Reads your system inventory, architecture diagrams and supplier list, and lists each place patient data is created, received, stored or sent. Knowledge Library
Your teamThe Platform Engineering Lead confirms the map, including the systems nobody had written down.
- EA
Drafts the risk analysis for each system on the map, and the safeguard policies from your existing security policies, with the source beside each section.
Your teamThe HIPAA Security Officer rates each risk and decides how it is treated.
- EA
Sends one request per owner for the records behind their safeguards, such as access reviews, audit log reviews and training records, follows up, and keeps each reply with its safeguard. EA Agent
Your teamOwners attach the records they already keep, rather than writing anything new for HIPAA.
- EA
Marks each safeguard it can’t yet evidence, such as a new reporting database that isn’t in the risk analysis, or a backup host with no agreement on file, which the rule requires before a subcontractor handles patient data.
Your teamThe owner closes the gap, or the HIPAA Security Officer records the decision. For the backup host, Legal Counsel sends the agreement.
- EA
Lists each security clause of the customer’s business associate agreement beside the safeguard and record in your programme that covers it: the incident reporting and subcontractor terms every agreement carries, and those the customer adds. Marks a clause “Needs evidence” where none does. Approvals
Your teamThe HIPAA Security Officer approves the risk analysis, the policies and each safeguard’s evidence, and settles the customer’s terms with Legal Counsel.
See a risk analysis drafted from your own systems.
Book a demoBetween customers
The programme moves when your systems do.
A new system
The rule asks for the evaluation again whenever operations change, so when a system will hold patient data, tell EA and it drafts the update to the map and the risk analysis for the HIPAA Security Officer.
The periodic evaluation
On the date your HIPAA Security Officer sets, EA starts the evaluation from the last approved evidence, and goes back to an owner only where a record has lapsed or a policy has changed.
Six years of documentation
Each version keeps its date and its approver, so for six years after a policy stops applying you can show what applied and when.
A customer’s questionnaire
When a US customer sends its HIPAA security questionnaire, EA drafts the answers from the risk analysis, policies and evidence your HIPAA Security Officer has already approved. See how EA completes customers’ security reviews
- Document
- Risk analysis
- Version
- 3 Current
- Approved by
- HIPAA Security Officer, 14 October 2026, 15:20
- Version 2
- Approved 9 April 2026
- Version 1
- Approved 2 October 2025
EA’s own security
Your risk analysis, behind a door you control.
A risk analysis lists your systems and their weak points, so who sees it is your decision. The programme runs on the documents that describe patient data, so patient records don’t need to go into EA. We ran our own ISO 27001 certification on EA: read how it ran on the ISO 27001 page.
- Hosted your way
EA’s cloud in a region you choose, hybrid options or on-premises. Data never used to train the models EA runs on.
- Access
Single sign-on, which you can enforce, and an access list for each workspace.
- Support access
EA staff see your data only in a time-limited window you open.
- Testing
An independent firm runs a penetration test on EA every year.
- Security contact
EA’s security team is at security@eaglobal.ai.
In the demo, see a sample agreement’s security clauses, each beside the safeguard that covers it.
Book a demoFAQ
What business associates ask us.
If you create, receive, maintain or transmit patient data for a US covered entity, you are likely its business associate, and the definition expressly includes legal, accounting and consulting services. Your counsel decides; EA then runs the programme that follows.
By describing it. The risk analysis can say that application logs keep a patient’s identifier for 30 days, or that a monthly export goes to the customer’s clinical team, without a single log line or export file in EA.
EA writes from your own policies, settings and records, with the source beside each line. Where a safeguard has no record behind it, say encryption on staff laptops with no device report to show it, EA marks it “Needs evidence” and leaves it for its owner.
Your consultant keeps advising on scope and safeguards. EA drafts the documents and gathers the records, so the programme is up to date whenever they next look at it.
Yes. Your ISO 27001 policies or Cyber Essentials answers already cover much of the same ground, so hand them to EA as they are, and our Customer Success team helps with exports from other platforms. Plans differ by the number of autofills, the workspaces you need and the size of your knowledge library; see the pricing page.
Changes were proposed in January 2025. As at 12 November 2026 no final rule had been published, and the Department of Health and Human Services says the current rule remains in effect meanwhile, so EA drafts against it.
Your next US customer’s go-live, without the programme still to build.
From mapping patient data to your HIPAA Security Officer.
Where HIPAA meets the rest of your work.
Related solutions
- SOC 2The report many US customers ask for, run from the same controls and records.Security and IT
- ISO 27001Policies and control evidence much of the HIPAA programme can start from.Security and IT
- PCI DSSCard data rather than patient data, with an attestation due each year.Security and IT




