R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4

4.3.13.426 Code System http://terminology.hl7.org/CodeSystem/smart-capabilities

Vocabulary Work Group Maturity Level: 0Informative Use Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/smart-capabilities
Version:3.5.0
Name:SmartCapabilities
Title:SmartCapabilities
Definition:

Codes that define what the server is capable of.

Committee:??
OID:2.16.840.1.113883.4.642.1.1265 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

Codes that define what the server is capable of.

This code system http://terminology.hl7.org/CodeSystem/smart-capabilities defines the following codes:

CodeDisplayDefinition
launch-ehr EHR Launch Modesupport for SMART’s EHR Launch mode.
launch-standalone Standalone Launch Modesupport for SMART’s Standalone Launch mode.
client-public Public Client Profilesupport for SMART’s public client profile (no client authentication).
client-confidential-symmetric Confidential Client Profilesupport for SMART’s confidential client profile (symmetric client secret authentication).
sso-openid-connect Supports OpenID Connectsupport 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 Tokensupport for refresh tokens (requested by offline_access scope).
permission-patient Supports Patient Level Scopessupport for patient-level scopes (e.g. patient/Observation.read).
permission-user Supports User Level Scopessupport for user-level scopes (e.g. user/Appointment.read).

 

See the full registry of code systems defined as part of FHIR.


Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code