IDENTITY & TRUST CONNECTORS
Healthcare Professional Identity
3 of 6Verify and link patients, professionals, organizations and trust frameworks while keeping authentication, identity proofing and authorization separate.
Pro Santé Connecte-CPSRPPSLuxTrustProfessional RegistriesMembershipsScopes
Trusted Verification
Verify through official identity providers and registries.
Multiple Professional Types
Support doctors, pharmacists, nurses and other professionals.
Identity Linking
Link external professional identity to Mediloop users and memberships.
Controlled Access
Authentication does not automatically grant clinical permissions.
Professional Identity Architecture
1
External Sources
PSC/e-CPS, RPPS, LuxTrust and national registries
2
Verification
Validate assertion, identifier and professional status
3
Linking
Link to Mediloop user and professional profile
4
Membership Context
Organization/tenant membership and role
5
Authorization
Scopes, permissions, consent and policy
Verification Flow
1
Authenticate
Trusted IdP or certificate
2
Resolve Registry
Lookup authoritative professional record
3
Validate Status
Active profession, specialty and identifiers
4
Link Account
Controlled mapping to Mediloop user
5
Authorize
Membership and scope evaluation
National Systems
| Country / system | Purpose | Typical use | Status |
|---|---|---|---|
| France — Pro Santé Connect / e-CPS | Professional authentication | Sign-in / trusted assertion | Country integration |
| France — RPPS | Professional registry | Identifier, profession, status | Registry adapter |
| Luxembourg — LuxTrust | Trusted digital identity | Authentication / certificates | Country integration |
| Luxembourg professional registries | Professional verification | Status and attributes | Registry adapter |
| Other EU systems | Future federation | Cross-border professional trust | Planned/evolving |
Professional Data
Professional identifier and issuing authority
Profession / specialty / qualifications
Active/inactive status and validity dates
Organization affiliations where authoritative
Certificate / assurance metadata where applicable
Source and last verification timestamp
APIs & Examples
httpCopy
# Illustrative professional-link contract
POST /v1/identity/link
Authorization: Bearer <token>
{
"provider":"pro-sante-connect",
"externalId":"RPPS12345678901",
"professionalType":"doctor",
"tenantId":"tenant_123",
"autoLink":false
}The public contract is illustrative until the Identity API is frozen. Do not auto-grant role or clinical scopes from authentication alone.
Security & Compliance
Revalidate professional status periodically and on security-sensitive actions
Do not infer organization membership from identity alone
Do not expose platform-admin capabilities in public docs
Log identity assertion, registry lookup and linking decisions
Handle certificate/token expiry and revocation
Use least privilege and tenant-aware authorization
Developer Integration Surface
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| Identity provider | OIDC / national assertion | Authenticate professional | Country-specific |
| Registry | RPPS / LU professional registry | Verify status and attributes | Country adapter |
| Professional API | verify / link / revalidate | Mediloop identity lifecycle | Versioned when frozen |
| Authorization | membership + scopes | Grant application permissions | Mediloop core |
Next Steps
Select national identity source
Register application/credentials
Implement verification and account linking
Map organization membership separately
Test status changes and revocation