Expand description
The access record: what the logging component records “on every access event or group of events” (Regulation (EU) 2025/327 Annex II 3.2).
Annex II 3.2 asks for (a) the healthcare provider or other individuals
that accessed the data, (b) the specific natural person or persons, (c)
the categories of data accessed, (d) the time and date, and (e) the
origin or origins of the data. An AccessRecord carries each, and
beside them the data subject whose data were accessed and the purpose of
use the access was made for, which Art 9(2) asks the patient be told. A
record whose accessor declared an emergency purpose carries the mark
Art 11(5) asks for (emergency).
A record names the patient and the person who accessed their data, so
Debug shows neither, nor any id the classification read: a record
leaves through an AccessSink alone.
Structs§
- Access
Record - One access event (Annex II 3.2).
- Accessor
- Who accessed the data (Annex II 3.2(a), (b)).
- Coded
- A coded value, such as a professional role: a code and the system that defines it.
- Data
Subject - Whose data an access concerned: the patient the request named, each
ehr_idthe access reached, and, for an access over many patients’ data that names none of them, the scope it read. - EhrAt
- One
ehr_idan access reached, at the endpoint that holds it, with whether the patient it belongs to is named. - Origin
- One origin of the data (Annex II 3.2(e)).
- Patient
Identifier - The patient an access concerned, by the identifier the request named and
the namespace that issued it;
Debugshows the namespace alone. - Population
- The scope of a population access: what the access read, when the record names none of the persons whose records it read.
- Professional
- The professional’s identification, as the token the access was authenticated by states it.
- Purpose
- One purpose of use the accessor declared: a code and the system that defines it.
- Relayed
- What a national contact point for digital health relays with a request.
- Relayed
Professional - The health professional a contact point relays (2026/2099 Annex Table 1).
- Relayed
Provider - The healthcare provider a contact point relays (2026/2099 Annex Table 2), where the professional provides the treatment.
- Request
- What the access asked for.
Enums§
- Acting
- Who acts behind the token an access was authenticated by.
- Action
- What the access did to the data.
- Assurance
Level - An assurance level of an electronic identification means, as Regulation (EU) No 910/2014 Art 8(2) names them, lowest first.
- Created
Ehr - The
ehr_idof the EHR a create left at its origin, as the origin’s answer named it. - Insertion
- Who inserted the information a write carried under the data subject’s own grant, as the written data marks it (Art 5).
- Outcome
- How the access ended.
- Patient
Lookup - Whether the patient behind an
ehr_idis named, so a search by the patient’s identifier finds the access (Art 9(1)). - Population
Reason - Why the record of an access over many patients’ data names none of the
ehr_ids whose records it read. - Written
Version - The version a write left at its origin, which is the data a write accessed (Annex II 3.2), as the origin’s answer named it.