This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

smart-app-state-server

Required capabilities for App State Server

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

SMART App State	SMART App State profile on Basic resource See App State capability for requirements, usage notes, and examples.
TaskEhrLaunch	Defines a Task that indicates the user should launch an application using the SMART on FHIR EHR launch.
TaskStandaloneLaunch	Defines a Task that indicates the user should launch an application as a standalone application.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Codes for tasks to application launches	Defines codes for Tasks that request launch of SMART applications.
Launch Types for tasks to application launches	Defines Launch Type codes for Tasks that request launch of SMART applications.

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

SMART on FHIR terminology.

Codes used to in profiles related to SMART on FHIR.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Example App State	Example App State
Example Task for EHR Launch	Example Task for EHR Launch
Example Task for Standalone Launch	Example Task for Standalone Launch