Is a pharmacy order health data?
Yes. In Lindenapotheke (C-21/23, October 4, 2024), the Court of Justice held that order data for pharmacy-only medicines is health data, even with no prescription.
GDPR. Data mapping by article.
A GDPR data map is tested on indirect cases: data that reveals a special category without naming it, which the Court of Justice counts as Article 9 data.
By Dipal Panchal, co-founder and CEO · Last reviewed: November 8, 2026
The General Data Protection Regulation, Regulation (EU) 2016/679, has applied since May 25, 2018 (Article 99(2)). It covers personal data processed by organizations established in the EU, wherever the processing happens (Article 3(1)).
Organizations outside the EU are covered when they offer goods or services to people in the EU, or track their behavior there (Article 3(2)). Each member state’s supervisory authority oversees it; a lead authority takes cross-border cases (Article 56), and the European Data Protection Board aligns their approach.
Article numbers below are to the regulation as published in the Official Journal. This page is general information, not legal advice.
How a reviewer labels values found across one company’s EU, US and Indian systems. GDPR applies because each value relates to a person, whatever country issued the identifier.
| Value | Detected type | Label | Reason | Kept or rejected |
|---|---|---|---|---|
| E11.9 in claims.diagnosis | Diagnosis code (ICD-10) | Special category: health, Article 9(1) | Linked to a policyholder ID | Kept |
| Order line: pantoprazole, pharmacy-only | Pharmacy order | Special category: health, Article 9(1) | The Court of Justice treats such orders as health data (C-21/23) | Kept |
| Halal meal flag in canteen.orders | Meal preference | Can reveal religious belief, Article 9(1) | Indirect revelation still counts, the Court held (C-184/20) | Kept |
| IG Metall in payroll.deductions | Trade union membership | Special category, Article 9(1) | A monthly deduction reveals membership | Kept |
| Template in badges.fp_template | Fingerprint template | Special category: biometric, Article 9(1) | The door system uses it to identify each person | Kept |
| 900-12-3456 in us_staff.ssn | US Social Security number | Personal data | US staff records processed by the EU parent; area 900 is never issued | Kept |
| 4923 5871 2608 in vendor_kyc.id_number | Aadhaar number | Personal data | An Indian supplier contact in an EU vendor file; passes the Verhoeff check | Kept |
| E11 in parts.code | Spare-part code | Not personal data | Shares the shape of a diagnosis code; no person is linked | Rejected |
The first two columns are the regulation, pinpointed. The record column recommends what shows you met the obligation: date, owner and source system.
| Article | What it requires | Data it touches | Record that shows it |
|---|---|---|---|
| Article 5(1)(c) and (e) | Collect only what the purpose needs, and keep data identifiable no longer than necessary. | Old exports, test copies, closed accounts | Each field matched to a purpose (5(1)(c)); retention rules checked against the oldest records (5(1)(e)) |
| Article 9 and Article 10 | Special category data only under an Article 9(2) condition; criminal data only under official authority or law. | Health, biometric, union and belief data; vetting results | A dated map, by system, of where each category sits and the condition relied on for each use |
| Article 12(3) and Article 15 | Answer within one month of receipt; extend by two months where necessary, telling the person why within the first month. | Every system that holds the person’s data | A search record: receipt, any extension notice and reply dates; what was searched and left out |
| Article 30 | Keep a record of processing activities with the Article 30(1) contents; Article 30(5) narrows it below 250 staff. | Every system the record names | The record, matched system by system to a dated search |
| Article 32(1) | Security appropriate to the risk, including encryption where appropriate and a process to regularly test and check it. | Stores of personal data, and who can reach them | Dated test reports naming who ran them, and a dated, scoped check of each store’s protection state |
| Article 33(1) | Notify the authority without undue delay and, where feasible, within 72 hours of awareness, unless risk is unlikely. | The affected systems and what they held | The Article 33(5) breach record with awareness and notice times, and a dated list of what the system held |
| Article 35(1) and (3)(b) | Assess high-risk processing before it starts; large-scale special category processing always needs one. | Large stores of Article 9 data | The assessment’s data section, built from a dated search |
| Article 27 | Organizations outside the EU caught by Article 3(2) name a representative in the Union, unless Article 27(2) applies. | Data on people in the EU, held abroad | The signed, dated designation, and the privacy notice that names the representative |
| Article 83(4) and (5) | Article 83(5): up to €20 million or, for an undertaking, 4% of worldwide turnover in the prior financial year if higher. | 83(5) covers Articles 5–7, 9, 12–22 and 44–49; 83(4), up to €10 million or 2%, covers Articles 8, 11, 25–39, 42, 43 | Not a record: the tier depends on the article breached |
Yes. In Lindenapotheke (C-21/23, October 4, 2024), the Court of Justice held that order data for pharmacy-only medicines is health data, even with no prescription.
Yes. In OT (C-184/20, August 1, 2022), the Court held that data revealing a special category indirectly, such as a partner’s name, falls under Article 9(1).
Article 30(5) frees organizations under 250 employees only for occasional, low-risk processing with no Article 9 or 10 data. Omnibus IV, not yet adopted, would raise the line to 1,000 employees.
Rarely, in my experience: consent sits in the collecting application’s tables, and replicas, warehouse loads and spreadsheet copies don’t carry it. Article 7(1) asks you to show it.
Checked on EUR-Lex and the EU institutions’ sites on November 8, 2026. Next review on November 24, 2026, after Parliament’s vote on Omnibus IV.
| Item | Status | Instrument |
|---|---|---|
| GDPR | In force since May 24, 2016; applies since May 25, 2018; EUR-Lex lists no amending act | Regulation (EU) 2016/679, Article 99 |
| Cross-border enforcement procedure | In force since January 1, 2026; applies from April 2, 2027; it doesn’t change the GDPR’s text | Regulation (EU) 2025/2518, Article 37 |
| Omnibus IV | Agreed text: below 1,000 staff, records only for high-risk work; committee approval July 2; plenary due November 23 | COM(2025) 501), procedure 2025/0130(COD) |
| Digital Omnibus | Proposed: breach notice only for high risk, within ninety-six hours; Council mandate October 21, 2026; EP in committee | COM(2025) 837, procedure 2025/0360(COD) |
| Review | Editorial review by Sylox; not reviewed by a lawyer | Last reviewed November 8, 2026 |
IRIS produces evidence for these rows and maps it to GDPR controls; it doesn’t certify compliance. Mapping shows relevance; your auditors judge whether a control is met.
Article 30: the systems in your record, checked against what they hold: IRIS produces part of this, for the sources you connect, by source, table, column or file.
Article 9: where special category data sits: IRIS produces part of this, for the data types IRIS detects, such as diagnosis codes and medications.
Articles 12 and 15: the search record for a request: IRIS produces part of this, connected databases only, not files or mailboxes; the change happens in the source system.
Article 32: who can reach each dataset: IRIS produces part of this, where the source exposes permission data.
Article 32: how stored values are protected: IRIS produces part of this, checks sampled values for encryption, masking or hashing, once activated on your install.
Article 5(2): what each scan covered and couldn’t read: IRIS produces this.
GDPR controls: where evidence is present, missing or deferred: IRIS produces this.
Explore evidenceAn order of work we recommend; GDPR itself sets none. Afterwards, the Article 30 guide checks the whole record against your systems.
Check the record of processing activities against what your systems hold.
The evidence that shows your security measures are tested, store by store.
Evidence on sensitive data that traces to a source, table and scan date.
Yes. GDPR is one of the six frameworks IRIS scores; it shows where evidence for each control is present, missing or deferred. Whether a control is met stays your auditor’s call.
Yes, it logs and searches. IRIS logs access, correction and erasure requests and searches connected databases for the person; your team makes the change in the source system. Capabilities vary by edition.
No. EU national ID formats aren’t among the built-in patterns today; add them as custom patterns. IRIS does recognize payment-card and international bank account (IBAN) numbers.
Yes. IRIS maps what it finds to UK GDPR controls through its unified compliance framework; a scored readiness view isn’t in v1, so ask us if you need one. The UK GDPR page maps each duty and what the Data (Use and Access) Act 2025 changed.
Find the Article 9 data in one system: a free assessment scans one database with a read-only login you create.