72.1.1Register a Provider System

Provider systems must be registered with an Identity Provider (IdP) to authenticate and receive necessary claims. There are two registration options depending on the IdP:

1. Option 1: Using Smile IdP (SMART_OUT) – when Smile acts as the IdP and issues tokens.
2. Option 2: Using Payer's IdP (SMART_IN) – when a Payer's IdP issues tokens and Smile validates them.

Note: To complete the provider system registration workflow, ensure that the corresponding Organization and Group resources are created in the FHIR repository. These resources are required for the Provider Access API to associate the registered provider system with its attributed members.

72.1.1.1Option 1: Using Smile IdP (`SMART_OUT`)

1. In the Smile Web Admin Console (with administrator access), navigate to: Users & Authorization → OpenID Connect Clients → Add Client.
2. Create a SMART Client Definition with the following required information:
   • Client ID: unique identifier for the provider system
   • Client secret / JWT: used for token authentication
   • Allowed scopes: permissions for FHIR API access (e.g., user/*.*)
   • Redirect URIs / audience: specify if required for token issuance 3. Save the SMART Client Definition and assign it to SMART_OUT.

72.1.1.2Option 2: Using Payer's IdP (`SMART_IN`)

1. In the Smile Web Admin Console (with administrator access), navigate to: Users & Authorization → OpenID Connect Servers → Add Server.
2. Create a SMART Server Definition with the following required information:
   • Issuer URL: identifies the Payer's IdP
   • JWKS endpoint: public keys for token signature verification
   • Token endpoint: where Smile requests access tokens 3. Reference this SMART Server Definition to SMART_IN for validation.
3. Register each provider system in the Payer's IdP:
   • Client ID: unique identifier for the provider system
   • Client secret / JWT: used for token authentication
   • Allowed scopes: permissions for FHIR API access