Hospitalidée · Pro Santé Connect · Digital health
Connecting Hospitalidée to Pro Santé Connect with RPPS account matching
Delegating professional identity verification to PSC, keeping existing accounts and testing both authentication methods: the CPS smart card and the e-CPS mobile app.
Explore Hospitalidée
Client case study · External technical lead engagement
Hospitalidée needed a trusted way to identify healthcare professionals signing in to existing accounts, without building its own verification process. The integration connected Hospitalidée to Pro Santé Connect and matched verified identities to accounts using RPPS.
Requirement
Give healthcare professionals access to existing accounts without verifying every identity in-house
Hospitalidée is a French platform dedicated to patient reviews and the online presence of healthcare professionals and organisations. Professionals have an account where they can manage their visibility and reputation, including responding to reviews.
Email-and-password login did not provide enough assurance for professional access. Pro Santé Connect verifies identity against data from the French Health Directory and lets the user choose between a physical CPS smart card and the e-CPS mobile app. The platform can rely on an already verified professional identity instead of creating a document-checking process.
Assignment
Deliver the integration as the external technical lead without replacing the existing account model.
- Implement the Pro Santé Connect OpenID Connect flow.
- Match the verified identity to an existing account using RPPS.
- Validate CPS smart card and e-CPS sign-in with ANS test equipment.
Identity decision
Use RPPS for account matching and treat the sub claim as a protocol identifier
OpenID Connect provides a sub claim that identifies the user at the identity provider. Hospitalidée needed a stable professional identifier already present on the relevant accounts, so it used RPPS to link the PSC identity to an application account.
Pro Santé Connect verifies the person’s identity and returns their professional attributes. Hospitalidée then finds the corresponding account, creates its own session and applies its authorisation rules.
Delegated identity
PSC authenticates the professional by CPS smart card or e-CPS and returns information from French health registries.
Application key
Hospitalidée uses RPPS to find the existing account. The sub claim remains a protocol-level identifier.
Local session
Once the account is matched, the application issues and controls the user session itself.
Application-owned access
PSC verifies identity; Hospitalidée continues to own authorisation and business rules.
In March 2026, ANS changed the sub claim format to a purely technical UUID, separate from the business identifier. No Hospitalidée accounts had to be migrated because account matching already relied on RPPS.
Implemented sign-in flow
From the login screen to a professional account in five steps
The integration uses OpenID Connect, the identity layer built on OAuth 2.0. The application redirects the browser to PSC. The professional uses a CPS smart card and reader or confirms the request in the e-CPS mobile application.
After successful authentication, PSC redirects the browser to the registered callback URL with an authorization code. A mature OIDC client library verifies state, exchanges the code, then validates the ID Token signature, its iss and aud claims, expiry and nonce before normalising the returned professional attributes. The server then uses RPPS to find the account and create a local session.
1 · Hospitalidée
The professional requests access to an account and the browser is redirected to Pro Santé Connect.
2 · Pro Santé Connect
PSC presents the available sign-in methods and handles the OIDC authentication step.
3 · CPS smart card or e-CPS
Physical card, reader and PIN, or confirmation of the request in the mobile application.
4 · Hospitalidée callback
The server verifies state, exchanges the code and validates the ID Token invariants before building the normalised identity.
5 · Identity → account → session
Hospitalidée finds the professional account by RPPS, then issues its own session.
type Rpps = string & { readonly __brand: 'Rpps' }
type NormalizedPscIdentity = {
rpps: Rpps
}
async function openProfessionalSession(
identity: NormalizedPscIdentity,
) {
const account = await professionalAccounts.findUniqueByRpps(identity.rpps)
if (!account) throw new Error('Unknown RPPS')
return sessions.create({
accountId: account.id,
authenticatedBy: 'psc',
})
}This type represents the normalised identity after the OIDC tokens have been validated. Only a validated RPPS value receives this branded type; the account is then retrieved through a unique RPPS index. Matching does not depend on the format of the sub claim.
Integration
Validate both sign-in methods with ANS test equipment
The technical lead engagement covered coordination with ANS, environment configuration and validation of both sign-in methods. Tests went beyond simulated OIDC responses and included CPS test cards and readers as well as e-CPS test identities.
01
Obtain integration environment access
The service is registered with ANS, which provides the access and settings required for initial integration tests.02
Configure the OpenID Connect client
Callback URLs and client settings are kept separate by environment using the values supplied during onboarding.03
Verify CPS smart card sign-in
CPS test cards and matching readers are used to check the login screen, card detection and PIN entry.04
Verify e-CPS sign-in
e-CPS test identities in the sandbox and the mobile app reproduce login confirmation without a physical card.05
Keep a reusable test setup
Byrds Consulting’s Editors and Integrators Agreement with ANS provides continued access to test cards and readers for future digital health integrations.
Acceptance testing covers the redirect to PSC, both sign-in methods and the return to Hospitalidée, alongside simulated HTTP exchanges.
Outcomes
Verified professional identity without an in-house document-checking process
The delivered sign-in flow lets healthcare professionals access their Hospitalidée account using a CPS smart card or e-CPS. The platform delegates identity verification to Pro Santé Connect and avoids requesting and checking professional documents itself.
Hospitalidée uses the RPPS returned by PSC to find the existing account. The application continues to manage the session and permissions.
What was delivered
Four capabilities were delivered and tested end to end.
- PSC login for Hospitalidée professional accounts, with account linking based on RPPS.
- Both sign-in methods: CPS smart card and e-CPS mobile app.
- A clear separation between PSC identity and local permissions.
- A test setup with CPS cards, readers and e-CPS identities.
Why the sub claim change required no migration
Hospitalidée kept the sub claim at the OIDC layer and used RPPS as its account key. When the sub claim format changed in 2026, that separation avoided an account migration.
Official sources and client context
- Hospitalidée. Public overview of the patient review platform and its services for healthcare professionals.
- Pro Santé Connect. Agence du Numérique en Santé. Service overview, identity verification and the CPS smart card and e-CPS sign-in methods.
- Pro Santé Connect technical documentation. Agence du Numérique en Santé. OpenID Connect flow, environments, tokens and the 2026 change to the sub claim.
- CPS technical foundation. Agence du Numérique en Santé. Documentation and ordering process for test CPS cards used in integrations.
- Editors and Integrators Agreement. Agence du Numérique en Santé. ANS framework for editors and integrators accessing services and test equipment.