Compliance & Security
GDPR, FHIR R4 and Clinical Documentation: What Irish Practices Need to Know
Moving clinic letters onto a digital platform raises fair questions about data protection and interoperability. This guide explains the essentials of GDPR and FHIR R4 in plain language, and lists the questions to ask any vendor.
By MedWave Team5 min read
Key takeaways
- Health data is a special category of personal data under GDPR and needs a higher standard of protection.
- Your practice is normally the data controller; a documentation platform acts as a data processor under a written agreement.
- Ask every vendor where data is stored, how it is secured, who can access it, and how you get it out again.
- FHIR R4 is the interoperability standard that keeps patient records portable between systems.
A clinic letter is one of the most sensitive documents a practice produces. It names a patient, describes their condition and records what was decided. So when a practice considers moving letter production onto a digital platform, two questions come up straight away: is the data protected, and can it move with the patient record?
The first question is answered by data protection law, chiefly the GDPR. The second is answered by interoperability standards, of which FHIR R4 is the most widely adopted. This guide covers the essentials of both for Irish consultants, GPs and practice managers.
Why health data is treated differently under GDPR
GDPR places "data concerning health" in a group of special categories of personal data. Processing this kind of data is prohibited unless a specific condition applies, such as the provision of health care by a professional who is bound by confidentiality. In practical terms, you need a lawful basis for processing and you are expected to protect the data to a higher standard.
In Ireland, the GDPR is supplemented by the Data Protection Act 2018, and the Data Protection Commission is the supervisory authority. It is the body you would notify in the event of a reportable breach, and the body a patient can complain to.
Controller and processor: who is responsible for what
GDPR distinguishes between two roles. The data controller decides why and how personal data is processed. The data processor handles data on the controller's behalf.
When a practice uses a documentation platform, the practice or consultant is normally the controller for patient data and the platform provider is the processor. Article 28 of the GDPR requires a written contract between the two, usually called a Data Processing Agreement (DPA). It sets out what the processor may do with the data, the security measures in place, and what happens to the data when the contract ends.
Two points follow from this. Choosing a vendor does not transfer your responsibilities as controller, and a vendor that cannot produce a DPA is not one you should be sending patient data to.
Seven questions to ask any documentation vendor
- Where is patient data stored and processed? Data kept within Ireland or the EU/EEA is the simplest position. Transfers outside the EEA are allowed only with additional safeguards.
- Will you sign a Data Processing Agreement? Ask to see it before you sign up, not after.
- How is data secured? Look for encryption, access controls and regular security assessments. GDPR requires security that is appropriate to the risk.
- Who can see what? Role-based access means a secretary, a consultant and an administrator each see only what their role requires.
- Is there an audit trail? You should be able to show who created, viewed, changed and sent a record. This supports the GDPR principle of accountability.
- Can data be exported and deleted? You will need both to respond to patient requests for access or erasure, and to leave the vendor if you ever choose to.
- What happens if there is a breach? A processor must tell you without undue delay. As controller, you may then have to notify the Data Protection Commission within 72 hours.
Do you need a Data Protection Impact Assessment?
A Data Protection Impact Assessment (DPIA) is a structured way of identifying and reducing the privacy risks of a new way of processing data. GDPR requires one where processing is likely to result in a high risk to individuals, and large-scale processing of health data is one of the examples it gives.
Whether a DPIA is mandatory for your practice depends on the scale and nature of what you do. The Data Protection Commission publishes guidance on DPIAs that will help you decide. Even where it is not strictly required, introducing a new system for patient data is a sensible moment to document the risks and the measures you have taken.
What FHIR R4 is, and why it matters
FHIR (Fast Healthcare Interoperability Resources) is a standard from HL7 for exchanging healthcare information between systems. It describes clinical and administrative data as "resources", such as a patient, a practitioner or a document, each with a defined structure. Release 4, known as R4, was the first release to include normative content, which is why it has become a common baseline for integrations.
For a practice, the benefits are practical rather than technical:
- Portability. Records held in a standard structure can be exported and read by other systems, so you are not locked in to one supplier.
- Integration. A FHIR-compliant platform is easier to connect to an electronic health record, which reduces re-keying and the errors that come with it.
- Future readiness. As health systems invest in shared records, standards-based data is far easier to bring with you.
How MedWave approaches compliance
MedWave was designed for Irish healthcare, with these requirements in mind from the start:
- Clear roles. MedWave acts as a data processor and you remain the data controller for patient data, under a Data Processing Agreement.
- Data location. Data is stored in Ireland where possible, and we aim to keep healthcare data within the EU/EEA.
- Security. Encryption, access controls and regular security assessments.
- Accountability. Role-based access for doctors and secretaries, with an audit trail on every letter.
- Interoperability. Patient records are FHIR R4 compliant, with secure data export.
You can read the detail on our GDPR and data protection page and in our privacy policy. Compliance is always shared: a platform can support your obligations, but your own policies, training and access practices matter just as much.
Next steps
If you are comparing documentation tools, use the seven questions above as a checklist and ask each vendor to answer them in writing. To see how the workflow itself fits into a clinic, read our practical guide to automated medical letters, or contact us with any data protection questions about MedWave.