FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.smart-multi-server-auth
Resource TypeCodeSystem
IdCodeSystem-smart-auth-information-CodeSystem.json
FHIR VersionR4
Sourcehttps://build.fhir.org/ig/bvdh/smart-multi-auth/CodeSystem-smart-auth-information-CodeSystem.html
URLhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystem
Version0.1.0
Statusdraft
Date2026-07-09T19:55:19+00:00
NameSmartAuthInformationCodeSystem
TitleCodes for SMART authorization
Realmuv
Authorityhl7
Description-
Contentcomplete

Resources that use this resource

ValueSet
hl7.fhir.uv.smart-multi-server-auth#currentSmartCapabilitiesSmart Capabilities
hl7.fhir.uv.smart-multi-server-auth#currentSmartEndpointCapabilitiesSmart associated_endpoints capabilities
hl7.fhir.uv.smart-multi-server-auth#currentsmart-grant-typesGrant types supported by SMART-on-FHIR
hl7.fhir.uv.smart-multi-server-auth#currentsmart-token-endpoint-auth-methodsSmart Token Endpoint Auth Methods supported by SMART-on-FHIR

Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: CodeSystem smart-auth-information-CodeSystem

This code system http://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystem defines the following codes in an undefined hierarchy:

LvlCodeDisplay
1endpoint-capabilities Endpoint Capabilities
2  smart-app-state Endpoint storing smart app state resources
1capability Capabilities of the server
2  launch-ehr support for SMART’s EHR Launch mode
2  launch-standalone support for SMART’s Standalone Launch mode
2  authorize-post support for POST-based authorization
2  client-public support for SMART’s public client profile (no client authentication)
2  client-confidential-symmetric support for SMART’s symmetric confidential client profile (“client secret” authentication). See Client Authentication Symmetric.
2  client-confidential-asymmetric support for SMART’s asymmetric confidential client profile (“JWT authentication”). See Client Authentication Asymmetric.
2  sso-openid-connect support for SMART’s OpenID Connect profile
2  context-banner support for “need patient banner” launch context (conveyed via need_patient_banner token parameter)
2  context-style support for “SMART style URL” launch context (conveyed via smart_style_url token parameter). This capability is deemed experimental. Launch Context for EHR Launch
2  context-ehr-patient support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter)
2  context-ehr-encounter support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter) Launch Context for Standalone Launch
2  context-standalone-patient support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter)
2  context-standalone-encounter support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter) Permissions
2  permission-offline support for “offline” refresh tokens (requested by offline_access scope)
2  permission-online support for “online” refresh tokens requested during EHR Launch (requested by online_access scope). This capability is deemed experimental, providing the input to a scope negotiation that could result in granting an online or offline refresh token (see Scopes and Launch Context).
2  permission-patient support for patient-level scopes (e.g., patient/Observation.rs)
2  permission-user support for user-level scopes (e.g., user/Appointment.rs)
2  permission-v1 support for SMARTv1 scope syntax (e.g., patient/Observation.read)
2  permission-v2 support for SMARTv2 granular scope syntax (e.g., patient/Observation.rs?category=http://terminology.hl7.org/CodeSystem/observation-category|vital-signs) App State (Experimental)
2  launch-token support for issuing launch tokens.
2  token-exchange-openid support for token exchange using an open id token
2  token-exchange-accesstoken support for token exchange using an access token
2  token-exchange-launchtoken support for token exchange using a launch token
1grant-type Lists the grant-types supported
2  authorization_code when SMART App Launch is supported
2  client_credentials Indicates upport for SMART Backend Services.
2  urn:ietf:params:oauth:grant-type:token-exchange Indicates support for token-exchange according to RFC8693
1token_endpoint_auth_methods Supported token endpoints
2  client_secret_post
2  client_secret_basic
2  private_key_jwt
1smart_associated_endpoints Smart associated_endpoints capabilities
2  token-reuse Authorization credentials can be retrieved by retrieving a access token for multiple audiences.
2  token-exchange Authorization credentials can be retrieved using token exchange.
2  smart-open-id-connect Authorization credentials can be retrieved using OpenID Connect with SMART on FHIR extensions.

Source1

{
  "resourceType": "CodeSystem",
  "id": "smart-auth-information-CodeSystem",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "url": "http://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystem",
  "version": "0.1.0",
  "name": "SmartAuthInformationCodeSystem",
  "title": "Codes for SMART authorization",
  "status": "draft",
  "date": "2026-07-09T19:55:19+00:00",
  "publisher": "HL7",
  "contact": [
    {
      "name": "HL7",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fhiri"
        }
      ]
    },
    {
      "name": "HL7 International / FHIR infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg/index.cfm"
        }
      ]
    },
    {
      "name": "Bas van den Heuvel",
      "telecom": [
        {
          "system": "email",
          "value": "bas.van.den.heuvel@philips.com",
          "use": "work"
        }
      ]
    },
    {
      "name": "Josh Mandel"
    },
    {
      "name": "Michel Donnelly"
    },
    {
      "name": "Rashid Kolaghassi"
    }
  ],
  "description": "-",
  "content": "complete",
  "count": 38,
  "concept": [
    {
      "code": "endpoint-capabilities",
      "display": "Endpoint Capabilities",
      "concept": [
        {
          "code": "smart-app-state",
          "display": "Endpoint storing smart app state resources"
        }
      ]
    },
    {
      "code": "capability",
      "display": "Capabilities of the server",
      "concept": [
        {
          "code": "launch-ehr",
          "display": "support for SMART’s EHR Launch mode"
        },
        {
          "code": "launch-standalone",
          "display": "support for SMART’s Standalone Launch mode"
        },
        {
          "code": "authorize-post",
          "display": "support for POST-based authorization"
        },
        {
          "code": "client-public",
          "display": "support for SMART’s public client profile (no client authentication)"
        },
        {
          "code": "client-confidential-symmetric",
          "display": "support for SMART’s symmetric confidential client profile (“client secret” authentication). See Client Authentication Symmetric."
        },
        {
          "code": "client-confidential-asymmetric",
          "display": "support for SMART’s asymmetric confidential client profile (“JWT authentication”). See Client Authentication Asymmetric."
        },
        {
          "code": "sso-openid-connect",
          "display": "support for SMART’s OpenID Connect profile"
        },
        {
          "code": "context-banner",
          "display": "support for “need patient banner” launch context (conveyed via need_patient_banner token parameter)"
        },
        {
          "code": "context-style",
          "display": "support for “SMART style URL” launch context (conveyed via smart_style_url token parameter). This capability is deemed experimental. Launch Context for EHR Launch"
        },
        {
          "code": "context-ehr-patient",
          "display": "support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter)"
        },
        {
          "code": "context-ehr-encounter",
          "display": "support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter) Launch Context for Standalone Launch"
        },
        {
          "code": "context-standalone-patient",
          "display": "support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter)"
        },
        {
          "code": "context-standalone-encounter",
          "display": "support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter) Permissions"
        },
        {
          "code": "permission-offline",
          "display": "support for “offline” refresh tokens (requested by offline_access scope)"
        },
        {
          "code": "permission-online",
          "display": "support for “online” refresh tokens requested during EHR Launch (requested by online_access scope). This capability is deemed experimental, providing the input to a scope negotiation that could result in granting an online or offline refresh token (see Scopes and Launch Context)."
        },
        {
          "code": "permission-patient",
          "display": "support for patient-level scopes (e.g., patient/Observation.rs)"
        },
        {
          "code": "permission-user",
          "display": "support for user-level scopes (e.g., user/Appointment.rs)"
        },
        {
          "code": "permission-v1",
          "display": "support for SMARTv1 scope syntax (e.g., patient/Observation.read)"
        },
        {
          "code": "permission-v2",
          "display": "support for SMARTv2 granular scope syntax (e.g., patient/Observation.rs?category=http://terminology.hl7.org/CodeSystem/observation-category|vital-signs) App State (Experimental)"
        },
        {
          "code": "launch-token",
          "display": "support for issuing launch tokens."
        },
        {
          "code": "token-exchange-openid",
          "display": "support for token exchange using an open id token"
        },
        {
          "code": "token-exchange-accesstoken",
          "display": "support for token exchange using an access token"
        },
        {
          "code": "token-exchange-launchtoken",
          "display": "support for token exchange using a launch token"
        }
      ]
    },
    {
      "code": "grant-type",
      "display": "Lists the grant-types supported",
      "concept": [
        {
          "code": "authorization_code",
          "display": "when SMART App Launch is supported"
        },
        {
          "code": "client_credentials",
          "display": "Indicates upport for SMART Backend Services."
        },
        {
          "code": "urn:ietf:params:oauth:grant-type:token-exchange",
          "display": "Indicates support for token-exchange according to RFC8693"
        }
      ]
    },
    {
      "code": "token_endpoint_auth_methods",
      "display": "Supported token endpoints",
      "concept": [
        {
          "code": "client_secret_post"
        },
        {
          "code": "client_secret_basic"
        },
        {
          "code": "private_key_jwt"
        }
      ]
    },
    {
      "code": "smart_associated_endpoints",
      "display": "Smart associated_endpoints capabilities",
      "concept": [
        {
          "code": "token-reuse",
          "display": "Authorization credentials can be retrieved by retrieving a access token for multiple audiences."
        },
        {
          "code": "token-exchange",
          "display": "Authorization credentials can be retrieved using token exchange."
        },
        {
          "code": "smart-open-id-connect",
          "display": "Authorization credentials can be retrieved using OpenID Connect with SMART on FHIR extensions."
        }
      ]
    }
  ]
}