HL7 Terminology (THO)
5.3.0 - Publication International flag

This page is part of the HL7 Terminology (v5.3.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: SmartCapabilities

Official URL: http://terminology.hl7.org/ValueSet/smart-capabilities Version: 0.1.0
Draft as of 2020-02-24 Responsible: HL7 (FHIR Project) Computable Name: SmartCapabilities
Other Identifiers: id: urn:oid:2.16.840.1.113883.4.642.3.1018

Codes that define what the server is capable of.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

This value set contains 14 concepts

Expansion based on codesystem SmartCapabilities v0.1.0 (CodeSystem)

CodeSystemDisplayDefinition
  launch-ehrhttp://terminology.hl7.org/CodeSystem/smart-capabilitiesEHR Launch Mode

support for SMART’s EHR Launch mode.

  launch-standalonehttp://terminology.hl7.org/CodeSystem/smart-capabilitiesStandalone Launch Mode

support for SMART’s Standalone Launch mode.

  client-publichttp://terminology.hl7.org/CodeSystem/smart-capabilitiesPublic Client Profile

support for SMART’s public client profile (no client authentication).

  client-confidential-symmetrichttp://terminology.hl7.org/CodeSystem/smart-capabilitiesConfidential Client Profile

support for SMART’s confidential client profile (symmetric client secret authentication).

  sso-openid-connecthttp://terminology.hl7.org/CodeSystem/smart-capabilitiesSupports OpenID Connect

support for SMART’s OpenID Connect profile.

  context-passthrough-bannerhttp://terminology.hl7.org/CodeSystem/smart-capabilitiesAllows "Need Patient Banner"

support for “need patient banner” launch context (conveyed via need_patient_banner token parameter).

  context-passthrough-stylehttp://terminology.hl7.org/CodeSystem/smart-capabilitiesAllows "Smart Style Style"

support for “SMART style URL” launch context (conveyed via smart_style_url token parameter).

  context-ehr-patienthttp://terminology.hl7.org/CodeSystem/smart-capabilitiesAllows "Patient Level Launch Context (EHR)"

support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter).

  context-ehr-encounterhttp://terminology.hl7.org/CodeSystem/smart-capabilitiesAllows "Encounter Level Launch Context (EHR)"

support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter).

  context-standalone-patienthttp://terminology.hl7.org/CodeSystem/smart-capabilitiesAllows "Patient Level Launch Context (STANDALONE)"

support for patient-level launch context (requested by launch/patient scope, conveyed via patient token parameter).

  context-standalone-encounterhttp://terminology.hl7.org/CodeSystem/smart-capabilitiesAllows "Encounter Level Launch Context (STANDALONE)"

support for encounter-level launch context (requested by launch/encounter scope, conveyed via encounter token parameter).

  permission-offlinehttp://terminology.hl7.org/CodeSystem/smart-capabilitiesSupports Refresh Token

support for refresh tokens (requested by offline_access scope).

  permission-patienthttp://terminology.hl7.org/CodeSystem/smart-capabilitiesSupports Patient Level Scopes

support for patient-level scopes (e.g. patient/Observation.read).

  permission-userhttp://terminology.hl7.org/CodeSystem/smart-capabilitiesSupports 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
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

History

DateActionAuthorCustodianComment
2020-10-14reviseGrahame GrieveVocabulary WGReset Version after migration to UTG
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.