Why health buyers ask for ISO 27001
When a hospital, clinic network or health department buys your software, it is trusting you with patient records, referrals, results or care plans. A breach harms patients directly and lands on the buyer’s reputation as well as yours. Their procurement and security teams have to show they assessed you properly, and an ISO 27001 certificate from an accredited certification body is the most widely recognised evidence they can file.
The requests come from several directions:
- Public health services. State and territory health departments and their hospital networks apply their government’s cyber security policy to suppliers. In NSW, for example, the whole-of-government cyber security policy mandates the Essential Eight for agencies, and local health districts extend security requirements to their ICT vendors. Tenders commonly list ISO 27001 as a condition or a scored criterion. See ISO 27001 for government tenders.
- Private hospital groups, pathology, radiology and large practices. These buyers run their own supplier risk programs and send long security questionnaires. A certificate and Statement of Applicability answer most of the questions at once. See how to answer security questionnaires faster.
- Secure data environments and research. Health data platforms ask for evidence of a recognised security standard. NSW Health’s requirements for secure data environments, for instance, list ISO 27001, IRAP and the Essential Eight among the acceptable standards.
- Private health insurers. They are APRA-regulated, so CPS 234 obliges them to assess the security of any third party that manages their information assets. See CPS 234 vs ISO 27001.
The laws and frameworks beside ISO 27001
The Privacy Act and APP 11
Health information is sensitive information under the Privacy Act 1988, which means stricter rules on collection, use and disclosure. Australian Privacy Principle 11 requires you to take reasonable steps to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure, and to destroy or de-identify it when you no longer need it. Since the 2024 amendments, APP 11 states expressly that reasonable steps include technical and organisational measures.
The small business exemption doesn’t help most health tech companies. A business that provides a health service and holds health information is covered whatever its turnover. A pure software vendor should check its own position, but its customers are covered, and their contracts will require you to protect the information to their standard.
The Privacy Act doesn’t name ISO 27001. The OAIC’s guidance on reasonable steps describes governance, risk assessment, access control, incident response and destruction of data, and an ISO 27001 ISMS covers all of them with documented evidence. That matters if your practices are ever examined after a breach. See Australia’s new cyber and privacy laws for the recent changes.
Notifiable data breaches
Under the Notifiable Data Breaches scheme, an eligible data breach is one likely to result in serious harm to the people affected. If you suspect one, you must assess it promptly (within 30 days), and if it is eligible, notify the OAIC and affected individuals as soon as practicable. The OAIC treats health information as a kind of information more likely to cause serious harm if it is compromised. Your incident procedure needs those steps built in, and your customer contracts need a notification timeframe that lets the data holder meet its own obligations.
State health records laws
Victoria, NSW and the ACT have their own health records laws: the Health Records Act 2001 (Vic), the Health Records and Information Privacy Act 2002 (NSW) and the Health Records (Privacy and Access) Act 1997 (ACT). They can apply to private sector organisations as well as public bodies. Record them as legal requirements in your ISMS under control 5.31 and check the security and retention obligations they add.
My Health Record
If your software connects to My Health Record through the B2B Gateway, the Australian Digital Health Agency’s security conformance profile for connecting systems applies. It sets mandatory and recommended requirements drawn from the Australian Government Information Security Manual and aligned with the Essential Eight, covering authentication, access to systems, encryption, secure application and web development, application hardening, patching, and backup and restoration. Some requirements are tested as part of conformance; others are organisational and you declare compliance with them. Externally hosted and SaaS products face extra requirements, including that internet-accessible parts of the system should be independently penetration tested.
ISO 27001 doesn’t replace the profile, and the profile doesn’t give you a certificate. They fit well together: the controls the Agency asks for map onto Annex A, and an ISMS keeps them working between conformance assessments. Check the Agency’s developer portal for the current version of the profile and its test specification before you plan.
My Health Record also has its own breach scheme under the My Health Records Act. Registered healthcare provider organisations and contracted service providers must report breaches involving the system to the System Operator, and private sector participants report to the OAIC as well. Where a breach falls under that scheme, the Privacy Act NDB scheme doesn’t also apply.
Essential Eight, IRAP and medical devices
Public health buyers often ask about your Essential Eight maturity as well as ISO 27001. The two answer different questions: ISO 27001 shows you manage security systematically, the Essential Eight shows specific technical mitigations are in place. See Essential Eight vs ISO 27001. Federal health agencies, and some state buyers of cloud services holding sensitive data, ask for an IRAP assessment against the Information Security Manual instead of or as well as a certificate. If your software is regulated as a medical device, the TGA’s requirements apply separately, and ISO 27001 doesn’t satisfy them.
ISO 27701 for privacy
ISO 27001 protects information. It doesn’t, on its own, show that you handle personal information lawfully, minimise what you collect, respect consent or support access and correction requests. ISO/IEC 27701:2025 does. It is now a standalone privacy information management standard that shares the ISO 27001 structure, so you can run one integrated system and one combined audit. For health tech companies that act as processors for hospitals, or that collect health information directly from patients, it is a strong addition once ISO 27001 is in place. See ISO 27001 vs ISO 27701 and our ISO 27701 service.
Scoping a health tech ISMS
Scope to what your health customers rely on. For most health tech companies that is the product, the cloud platform it runs on, the data flows to and from clinical systems, and the people who build, support and administer it. If you also run a separate consumer app or a non-health product line, you can leave it out, but the boundary must be real: shared accounts, shared databases or shared support staff pull it back in.
Three things deserve care when you set the scope:
- Where health information lives. Map every place it goes: production, backups, analytics, support tools, logs, test environments and any offshore locations. Buyers ask where data is stored and who can access it from where, and some contracts require Australian hosting.
- Integrations. HL7 or FHIR interfaces, secure messaging, My Health Record and practice management integrations all carry health data and belong in scope.
- Your role. Are you a processor running a hospital’s data, or do you collect from patients directly? The answer changes your privacy obligations and the controls you need.
The scoping decisions behind a cloud product are covered in ISO 27001 for SaaS companies; health tech adds the data mapping above.
The Annex A controls under most scrutiny
Every applicable control matters at audit, but health buyers and auditors press hardest on these. For what each control involves, see the Annex A controls explained.
| Area | Annex A controls | What gets checked |
|---|---|---|
| Access to patient data | 5.15 Access control, 5.18 Access rights, 8.2 Privileged access rights, 8.3 Information access restriction, 8.5 Secure authentication | Who in your company can see patient records, why, and how that is approved, reviewed and removed. MFA for all administrative and support access |
| Logging and monitoring | 8.15 Logging, 8.16 Monitoring activities | Whether you record who viewed or changed patient records, protect those logs and actually review them |
| Suppliers and cloud | 5.19 to 5.22 supplier controls, 5.23 Cloud services | Hosting, messaging, analytics and support tools that touch health data, their locations and the security terms you hold with them |
| Test data and masking | 8.11 Data masking, 8.33 Test information | Whether real patient data is used in development or testing, and how it is masked or de-identified if so |
| Deletion and retention | 8.10 Information deletion, 7.14 Secure disposal or re-use of equipment | How you delete records at contract end or on request, including from backups, while meeting health records retention rules |
| Backup and continuity | 8.13 Information backup, 5.30 ICT readiness for business continuity, 8.14 Redundancy | Restore testing and recovery times. Clinical systems that are down affect care, so buyers ask about availability as much as confidentiality |
| Privacy and legal | 5.31 Legal, statutory, regulatory and contractual requirements, 5.34 Privacy and protection of PII | A register naming the Privacy Act, state health records laws and My Health Record obligations, and how each is met |
| Incidents | 5.24 to 5.28 incident management | An incident procedure that handles NDB assessment, the My Health Record scheme and customer notification timeframes |
Penetration testing isn’t named in ISO 27001, but for a health product with internet-facing endpoints it is effectively expected by buyers, and the Agency says My Health Record connections should be tested. See does ISO 27001 require penetration testing?
Common mistakes
- Treating health data like any other customer data. A risk assessment that rates patient records the same as marketing contacts won’t survive a hospital’s review or an auditor’s questions. Rate the harm to patients, not just to the business.
- Production data in test. Copying the production database to staging to reproduce a bug is common and is exactly what control 8.11 and buyers look for.
- Support access with no trail. Support staff who can open any patient record without approval or logging is the finding health buyers most dislike.
- Missing the legal register. Listing only “the Privacy Act” and leaving out state health records laws and My Health Record obligations leaves clause 4.2 and control 5.31 incomplete.
- Assuming the certificate answers everything. Health buyers still send their own questionnaires and ask about Essential Eight maturity, hosting location and breach notification. Prepare those answers alongside the certificate.
- Deletion that ignores backups and retention. Promising to delete everything at contract end can conflict with health records retention rules. Agree in the contract who keeps what, and for how long.
Building a legal register and incident procedure that line up the Privacy Act, state health records laws and My Health Record is one of the harder parts of a health tech ISMS, and it is a part we often take on for clients.
Effort and timing
Health tech doesn’t change the standard, but it adds legal requirements and raises the bar on access, logging and data handling evidence. A small or medium company can often be audit-ready in about eight weeks; see how long ISO 27001 takes. Effort depends mainly on scope, how many systems hold health data and how much is already documented. Our guide to what drives ISO 27001 cost explains the factors.
Next step
If you are building your ISMS yourself, ISO 27001 requires internal audits to be objective and impartial, so staff can do them only if they aren’t auditing their own work. That is why many small teams bring in an independent internal auditor before certification. To talk through a hospital’s or health department’s requirements, book a free 30-minute consultation, or see how our ISO 27001 service works.
