This page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4
FHIR Infrastructure Work Group | Maturity Level: 0 | Informative | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/smart-capabilities |
Version: | 4.3.0-snapshot1 |
Name: | SmartCapabilities |
Title: | SmartCapabilities |
Definition: | Codes that define what the server is capable of. |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.3.1018 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
http://terminology.hl7.org/CodeSystem/smart-capabilities
This expansion generated 20 Dec 2021
This value set contains 14 concepts
Expansion based on SmartCapabilities v4.3.0-snapshot1 (CodeSystem)
All codes in this table are from the system http://terminology.hl7.org/CodeSystem/smart-capabilities
Code | Display | Definition |
launch-ehr | EHR Launch Mode | support for SMART’s EHR Launch mode. |
launch-standalone | Standalone Launch Mode | support for SMART’s Standalone Launch mode. |
client-public | Public Client Profile | support for SMART’s public client profile (no client authentication). |
client-confidential-symmetric | Confidential Client Profile | support for SMART’s confidential client profile (symmetric client secret authentication). |
sso-openid-connect | Supports OpenID Connect | support for SMART’s OpenID Connect profile. |
context-passthrough-banner | Allows "Need Patient Banner" | support for “need patient banner” launch context (conveyed via need_patient_banner token parameter). |
context-passthrough-style | Allows "Smart Style Style" | support for “SMART style URL” launch context (conveyed via smart_style_url token parameter). |
context-ehr-patient | Allows "Patient Level Launch Context (EHR)" | support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter). |
context-ehr-encounter | Allows "Encounter Level Launch Context (EHR)" | support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter). |
context-standalone-patient | Allows "Patient Level Launch Context (STANDALONE)" | support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter). |
context-standalone-encounter | Allows "Encounter Level Launch Context (STANDALONE)" | support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter). |
permission-offline | Supports Refresh Token | support for refresh tokens (requested by offline_access scope). |
permission-patient | Supports Patient Level Scopes | support for patient-level scopes (e.g. patient/Observation.read). |
permission-user | Supports User Level Scopes | support for user-level scopes (e.g. user/Appointment.read). |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
Source | 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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |