HL7 Terminology
2.0.0 - Publication
This page is part of the HL7 Terminology (v2.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/smart-capabilities |
Version: | 0.1.0 |
Name: | SmartCapabilities |
Status: | Draft as of 2020-02-24T12:41:39+11:00 |
Definition: | Codes that define what the server is capable of. |
Publisher: | HL7 (FHIR Project) |
Committee: | FHIR Infrastructure |
OID: | 2.16.840.1.113883.4.642.3.1018 (for OID based terminology systems) |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/smart-capabilities
This value set contains 14 concepts
Expansion based on SmartCapabilities v0.1.0 (CodeSystem)
All codes from 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). |
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 |
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) |
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 |
History
Date | Action | Custodian | Author | Comment |
2020-10-14 | revise | Vocabulary WG | Grahame Grieve | Reset Version after migration to UTG |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |