0.1.0 - ci-build

SMARTapplaunchmultiserverauthentication, published by HL7. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/jmandel/smart-multi-auth/ and changes regularly. See the Directory of published versions

ValueSet: Smart Capabilities

Official URL: http://hl7.org/fhir/uv/smart-multi-server-auth/ValueSet/SmartCapabilities Version: 0.1.0
Draft as of 2024-12-09 Computable Name: SmartCapabilities

References

Logical Definition (CLD)

Generated Narrative: ValueSet SmartCapabilities

This value set includes codes based on the following rules:

This value set excludes codes based on the following rules:

 

Expansion

Generated Narrative: ValueSet

Expansion based on codesystem Codes for SMART authorization v0.1.0 (CodeSystem)

This value set contains 24 concepts

CodeSystemDisplay
  launch-ehrhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for SMART’s EHR Launch mode
  launch-standalonehttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for SMART’s Standalone Launch mode
  authorize-posthttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for POST-based authorization
  client-publichttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for SMART’s public client profile (no client authentication)
  client-confidential-symmetrichttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for SMART’s symmetric confidential client profile (“client secret” authentication). See Client Authentication Symmetric.
  client-confidential-asymmetrichttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for SMART’s asymmetric confidential client profile (“JWT authentication”). See Client Authentication Asymmetric.
  sso-openid-connecthttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for SMART’s OpenID Connect profile
  context-bannerhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for “need patient banner” launch context (conveyed via need_patient_banner token parameter)
  context-stylehttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for “SMART style URL” launch context (conveyed via smart_style_url token parameter). This capability is deemed experimental. Launch Context for EHR Launch
  context-ehr-patienthttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter)
  context-ehr-encounterhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter) Launch Context for Standalone Launch
  context-standalone-patienthttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter)
  context-standalone-encounterhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter) Permissions
  permission-offlinehttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for “offline” refresh tokens (requested by offline_access scope)
  permission-onlinehttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport 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).
  permission-patienthttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for patient-level scopes (e.g., patient/Observation.rs)
  permission-userhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for user-level scopes (e.g., user/Appointment.rs)
  permission-v1http://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for SMARTv1 scope syntax (e.g., patient/Observation.read)
  permission-v2http://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for SMARTv2 granular scope syntax (e.g., patient/Observation.rs?category=http://terminology.hl7.org/CodeSystem/observation-category|vital-signs) App State (Experimental)
  launch-tokenhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for issuing launch tokens.
  token-exchange-openidhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for token exchange using an open id token
  token-exchange-accesstokenhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for token exchange using an access token
  token-exchange-launchtokenhttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemsupport for token exchange using a launch token
  smart-app-statehttp://hl7.org/fhir/uv/smart-multi-server-auth/CodeSystem/smart-auth-information-CodeSystemEndpoint storing smart app state resources

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code