pub struct Accessor {Show 13 fields
pub issuer: Option<String>,
pub subject: String,
pub client_id: Option<String>,
pub audience: Option<String>,
pub provider: Option<String>,
pub acting: Option<Acting>,
pub roles: Vec<Coded>,
pub token_id: Option<String>,
pub assurance: Option<AssuranceLevel>,
pub professional: Professional,
pub alt_id: Option<String>,
pub purposes: Vec<Purpose>,
pub relayed: Option<Relayed>,
}Expand description
Who accessed the data (Annex II 3.2(a), (b)).
The person, as the token the access was authenticated by names them, or as a local account names them when no token did, the client they used, and the provider they act for.
Each value is the authentication’s, as the recording system verified it: the record infers none, so the issuer, the client, the acting mode and the assurance level are absent unless the authentication established them.
Fields§
§issuer: Option<String>The issuer that vouched for the person (iss), when a token named
them; None for a user authenticated otherwise, such as by HTTP
Basic.
subject: StringThe person (sub, or the local account).
client_id: Option<String>The client application they used (client_id), when a token named
one.
audience: Option<String>The audience the token named the recording system by.
provider: Option<String>The healthcare provider or other organisation the person acts for.
acting: Option<Acting>Who acts behind the token: the person, or a client application, when the recording system established it.
roles: Vec<Coded>The roles or authorities the person acted under, such as the security
roles of the recording system, which the record writes at
agent[user].role (BALP 1.1.4 §3:5.7.5.4, the IUA subject_role).
token_id: Option<String>The identity of the access token (jti), when it names one.
assurance: Option<AssuranceLevel>The assurance level the authentication reached, when the recording system established one from the token.
professional: ProfessionalThe professional the token names (3.2(b)), who acts in person or whom a client acts for.
alt_id: Option<String>Another identification of the person the token states beside its
sub, such as a professional number a claim of the deployment’s
naming carries.
purposes: Vec<Purpose>Every purpose of use the token declares.
relayed: Option<Relayed>The professional and the provider of another Member State a national contact point relays, marked as asserted by it, when the client is one (Implementing Regulation (EU) 2026/2099 Art 7).