EU Health Data API, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/euridice-org/eu-health-data-api/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: Authentication Service

Raw xml | Download

<ActorDefinition xmlns="http://hl7.org/fhir">
  <id value="authentication-service-eu-api"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ActorDefinition authentication-service-eu-api</b></p><a name="authentication-service-eu-api"> </a><a name="hcauthentication-service-eu-api"> </a><table class="grid"><tr><td><b>Actor: AuthenticationServiceEuApi </b></td><td>Authentication Service</td><td>Type: system </td></tr><tr><td colspan="3"/></tr></table></div>
  </text>
  <url
       value="http://hl7.eu/fhir/health-data-api/ActorDefinition/authentication-service-eu-api"/>
  <version value="1.0.0-ballot"/>
  <name value="AuthenticationServiceEuApi"/>
  <title value="Authentication Service"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-11-05T11:19:50+00:00"/>
  <publisher value="HL7 Europe"/>
  <contact>
    <name value="HL7 Europe"/>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.eu"/>
    </telecom>
  </contact>
  <description
               value="The Authentication Service authenticates an end user, directly or through a Wallet or upstream
identity provider, and supplies an authentication result trusted by the Health Data API Authorization Server.
It does not grant API access or issue API access tokens in this role. This IG-defined role is not
a formal IHE IUA or SMART actor. It MAY be grouped with the
[Health Data API Authorization Server](ActorDefinition-eu-authorization-server-eu-api.html) in one implementation;
the interface between separate implementations is deployment-defined, not an interoperable
transaction specified by this IG. No ID token or token exchange is required by the actor split.
See [authentication and authorization groupings](actors.html#authentication-and-authorization-groupings)
and [Authorization](authorization.html#authentication-and-api-authorization)."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="150"/>
      <display value="Europe"/>
    </coding>
  </jurisdiction>
  <copyright
             value="Copyright HL7 Europe. Licensed under Creative Commons public domain (CC0 1.0)."/>
  <type value="system"/>
</ActorDefinition>