This
page
is
part
of
the
FHIR
Specification
(v3.3.0:
(v3.5.0:
R4
Ballot
2).
#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
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: | 3.5.0 |
| Name: | SmartCapabilities |
| Title: | SmartCapabilities |
| Definition: |
Codes
that
define
what
the
server
is
capable
|
| 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:
This value set includes codes from the following code systems:
http://hl7.org/fhir/smart-capabilities
http://terminology.hl7.org/CodeSystem/smart-capabilities
This
expansion
generated
03
Apr
19
Aug
2018
This value set contains 14 concepts
Expansion
based
on
http://hl7.org/fhir/smart-capabilities
http://terminology.hl7.org/CodeSystem/smart-capabilities
version
3.3.0
3.5.0
All
codes
from
system
http://hl7.org/fhir/smart-capabilities
http://terminology.hl7.org/CodeSystem/smart-capabilities
| Code | Display | Definition |
| launch-ehr | EHR Launch Mode |
support
for
SMART’s
EHR
Launch
|
| launch-standalone | Standalone Launch Mode |
support
for
SMART’s
Standalone
Launch
|
| client-public | Public Client Profile |
support
for
SMART’s
public
client
profile
(no
client
|
| client-confidential-symmetric | Confidential Client Profile |
support
for
SMART’s
confidential
client
profile
(symmetric
client
secret
|
| sso-openid-connect | Supports OpenID Connect |
support
for
SMART’s
OpenID
Connect
|
| context-passthrough-banner | Allows "Need Patient Banner" |
support
for
“need
patient
banner”
launch
context
(conveyed
via
need_patient_banner
token
|
| context-passthrough-style | Allows "Smart Style Style" |
support
for
“SMART
style
URL”
launch
context
(conveyed
via
smart_style_url
token
|
| context-ehr-patient | Allows "Patient Level Launch Context (EHR)" |
support
for
patient-level
launch
context
(requested
by
launch/patient
scope,
conveyed
via
patient
token
|
| context-ehr-encounter | Allows "Encounter Level Launch Context (EHR)" |
support
for
encounter-level
launch
context
(requested
by
launch/encounter
scope,
conveyed
via
encounter
token
|
| context-standalone-patient | Allows "Patient Level Launch Context (STANDALONE)" |
support
for
patient-level
launch
context
(requested
by
launch/patient
scope,
conveyed
via
patient
token
|
| context-standalone-encounter | Allows "Encounter Level Launch Context (STANDALONE)" |
support
for
encounter-level
launch
context
(requested
by
launch/encounter
scope,
conveyed
via
encounter
token
|
| permission-offline | Supports Refresh Token |
support
for
refresh
tokens
(requested
by
offline_access
|
| permission-patient | Supports Patient Level Scopes |
support
for
patient-level
scopes
(e.g.
|
| permission-user | Supports User Level Scopes |
support
for
user-level
scopes
(e.g.
|
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 |