R4 Ballot #1 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.3.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.1.1018 Value Set http://hl7.org/fhir/ValueSet/smart-capabilities

FHIR Infrastructure Work Group Maturity Level: 0Informative Use Context: Any

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/smart-capabilities
Name: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 ResourceXML / JSON

This value set is used in the following places:

4.3.1.1018.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.1.1018.2 Expansion

This expansion generated 03 Apr 2018

This value set contains 14 concepts

Expansion based on http://hl7.org/fhir/smart-capabilities version 3.3.0

All codes from system http://hl7.org/fhir/smart-capabilities

CodeDisplayDefinition
launch-ehrEHR Launch Modesupport for SMART’s EHR Launch mode
launch-standaloneStandalone Launch Modesupport for SMART’s Standalone Launch mode
client-publicPublic Client Profilesupport for SMART’s public client profile (no client authentication)
client-confidential-symmetricConfidential Client Profilesupport for SMART’s confidential client profile (symmetric client secret authentication)
sso-openid-connectSupports OpenID Connectsupport for SMART’s OpenID Connect profile
context-passthrough-bannerAllows "Need Patient Banner"support for “need patient banner” launch context (conveyed via need_patient_banner token parameter)
context-passthrough-styleAllows "Smart Style Style"support for “SMART style URL” launch context (conveyed via smart_style_url token parameter)
context-ehr-patientAllows "Patient Level Launch Context (EHR)"support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter)
context-ehr-encounterAllows "Encounter Level Launch Context (EHR)"support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter)
context-standalone-patientAllows "Patient Level Launch Context (STANDALONE)"support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter)
context-standalone-encounterAllows "Encounter Level Launch Context (STANDALONE)"support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter)
permission-offlineSupports Refresh Tokensupport for refresh tokens (requested by offline_access scope)
permission-patientSupports Patient Level Scopessupport for patient-level scopes (e.g. patient/Observation.read)
permission-userSupports User Level Scopessupport 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:

LvlA 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
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