Firely Terminal

https://docs.fire.ly/projects/Firely-Terminal/
Admin
Firely Terminal is a cross-platform FHIR command-line tool that helps you work with files containing...
Tokens:6,377
Snippets:81
Trust Score:9
Update:1 year ago
Show doc for...
Tokens:
Raw
### Manage Firely Terminal with .NET CLI

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/InstallingFirelyTerminal

Commands to install, update, and uninstall the Firely Terminal using the .NET CLI. This requires the .NET SDK to be installed.

```bash
dotnet tool install -g firely.terminal
```

```bash
dotnet tool update -g firely.terminal
```

```bash
dotnet tool uninstall -g firely.terminal
```

--------------------------------

### Verify Firely Terminal Installation

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/InstallingFirelyTerminal

Command to check the installed version of Firely Terminal, confirming a successful installation. This command is executed after ensuring the .NET tools are in the system's PATH.

```bash
fhir --version
```

--------------------------------

### Getting Validation Help

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Displays help information and available parameters for the `validate` command, including options for specifying terminology servers or additional profiles.

```bash
> fhir ? validate
```

--------------------------------

### Install Package from File

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Managing-Packages

Installs a local package file (.tgz) into the global package cache using the '--file' or '-f' flag. This is useful for testing locally created packages not yet on the server.

```bash
> fhir install thisproject.tgz --file

```

--------------------------------

### Get Command Help with '-?', '--help', or '-h'

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Users can access command-specific help by appending '-?', '--help', or '-h' to any command. This provides context-sensitive documentation for each function.

```cli
fhir --help
```

```cli
bake -?
```

```cli
search -h
```

--------------------------------

### Installing FHIR Packages

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Installs required FHIR packages, such as core specification libraries, into the current directory to create a scope for resolving resources and data types.

```bash
> fhir install hl7.fhir.r3.core
```

--------------------------------

### Install Package to Current Folder

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Managing-Packages

Installs a package, by default in the global cache, but can be directed to install in the current folder using the '--here' or '-r' flag. This installs the package as a subfolder.

```bash
> fhir install simplifier.core.stu3 --here

```

--------------------------------

### Install FHIR Package with npm

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Using-NPM-instead

Installs a FHIR package, like 'hl7.fhir.r4.core', and its dependencies using npm. Requires a package.json file to be present.

```bash
> npm create
> npm --registry https://packages.simplifier.net/ install hl7.fhir.r4.core
> npm --registry https://packages.simplifier.net/ install

```

--------------------------------

### Install FHIR Package

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Managing-Packages

Installs a FHIR package from the package server to the local machine, adding a reference to the package.json file. Can install the latest version by providing just the package name, or a specific version/range.

```bash
> fhir install xyz.myprofiles

```

```bash
> fhir install xyz.myprofiles 2.3

```

--------------------------------

### Firely Terminal Dependency Management

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/Simplifier-Sync

Manages project dependencies by restoring them locally after cloning a project. It also allows checking the installed dependencies.

```bash
> fhir restore
> fhir scope
```

--------------------------------

### Define Canonical Claims in Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Example of how to define canonical claims in a `project.yaml` file for Firely Terminal. This ensures conformance resources adhere to specified base canonical URLs.

```yaml
canonical-claims:
   - http://myorg.net/fhir
   - http://mystandard.org/fhir/Structure/

```

--------------------------------

### Firely Terminal YAML Generation Command

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Introduces the `yaml-gen` command in Firely Terminal, which parses YAML resources to generate FHIR example resources. This tool integrates an agnostic version of an automatic example generator.

```bash
yaml-gen

```

--------------------------------

### Firely Terminal Commands for Resource Filtering

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Examples of using Firely Terminal commands to filter resources. The `filter` command can operate on resources within a stack or a folder on disk using FHIRpath expressions.

```bash
filter

```

--------------------------------

### Set Simplifier as Default npm Registry

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Using-NPM-instead

Configures npm to use Simplifier as the default package server. This is recommended only if npm is not used for JavaScript packages. It allows installing packages without specifying the registry each time.

```bash
> npm config set registry https://packages.simplifier.net/
> npm install hl7.fhir.r4.core
> npm install

```

--------------------------------

### Firely Terminal Local Cache Parameter

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Utilizes the `--here` parameter with Firely Terminal to specify a local cache directory within the project folder for installing packages.

```bash
--here

```

--------------------------------

### Pushing Resources onto the Stack

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Adds matching files or server resources to the Firely Terminal's internal stack. This is the primary method for getting resources into the terminal for further processing.

```bash
> fhir push      #Pushes matching files or server resources on the stack
```

--------------------------------

### Search FHIR Resources

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/FHIR-Client

Performs a basic search for FHIR resources on a specified server alias. It requires the server alias and resource type. The example searches for patients named Chalmers on the public Firely Server.

```bash
> fhir search firely Patient

```

```bash
> fhir search https://server.fire.ly Patient name=Chalmers

```

```bash
> fhir search http://server.fire.ly/administration StructureDefinition url=http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient

```

--------------------------------

### Remove Package from Project

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Managing-Packages

Removes a package that has been installed in the current project (folder). This updates the package.json manifest and fhirpkg.lock.json file, but does not remove the package from the global cache.

```bash
> fhir remove xyz.myprofiles

```

--------------------------------

### Firely Terminal Project Listing and Management

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/Simplifier-Sync

Commands for interacting with your Simplifier.net projects. This includes listing all projects, cloning, updating, synchronizing, pushing changes, and creating packages.

```bash
> fhir projects
> fhir project clone <project>     #Clones a project from Simplifier.net in a sub folder
> fhir project update              #Synchronizes your project with a specific folder
> fhir project sync                #Synchronizes current folder with the corresponding Simplifier project
> fhir push                        #Pushes all changes to the corresponding project on Simplifier
> fhir pack                        #Creates a package from the current project
```

--------------------------------

### Package Publishing and Creation - Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Explains the `bake` command for publishing packages and the `pack` command for creating FHIR package .tgz files. The `bake` command defaults to outputting to the /.bake subfolder.

```CLI
bake
pack
```

--------------------------------

### Firely Terminal Login to Simplifier

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/Simplifier-Sync

Logs into your Simplifier account using email and password credentials. This is the first step to interact with Simplifier.net.

```bash
> fhir login email=<your email> password=<your password>
```

--------------------------------

### Firely Terminal Simplifier Account Management

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/Simplifier-Sync

Provides commands for managing your Simplifier.net account and session. This includes logging out, checking license features, and viewing resource documentation.

```bash
> fhir logout            #Clears the credentials for Simplifier.net
> fhir license           #Lists the features in your license
> fhir doc <canonical>   #Brings you to the documentation page of the resource
```

--------------------------------

### Firely Terminal FQL4 Select Statement

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Illustrates the concise 'select' statement in FQL4, allowing users to select all resources in scope without needing to specify 'from Resource'.

```sql
select

```

--------------------------------

### Batch Conversion of Files

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Converts multiple files in a folder from one format to another. This uses wildcard patterns for pushing files and the `--all` flag with the desired output format.

```bash
> fhir push *.xml
> fhir save --all --json
```

--------------------------------

### Other Package Management Commands

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Managing-Packages

A collection of miscellaneous package management commands including displaying package contents, creating packages, initializing manifests, restoring packages, listing canonicals, and searching for packages.

```bash
> fhir contents       #Displays the content from a packages

```

```bash
> fhir pack           #Creates a FHIR package from a folder

```

```bash
> fhir init           #Generates a FHIR package manifest

```

```bash
> fhir restore        #Restores all packages referenced in this folders package file

```

```bash
> fhir canonicals     #Lists canonicals from resources in a package or scope

```

```bash
> fhir find           #Searches for package(s) by name or canonical

```

--------------------------------

### List Package Versions

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Managing-Packages

Fetches and displays all available versions of a specified package from the package server. The '--raw' flag can be used to view the raw JSON document of the package listing.

```bash
> fhir versions simplifier.core.stu3

```

```bash
> fhir versions simplifier.core.stu3 --raw

```

--------------------------------

### Execute FQL Queries with 'query'

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The 'query' command officially supports FQL (Firely Query Language) for advanced data retrieval and manipulation within the terminal. This feature may require a license.

```cli
query "Patient?gender=female"
```

--------------------------------

### Manage Projects with 'project update/clone/push'

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Project synchronization has been redesigned using 'project update', 'project clone', and 'project push' commands, replacing the older 'sync' command for a more predictable workflow.

```cli
project update
```

```cli
project clone <repository_url>
```

```cli
project push
```

--------------------------------

### Inflate Command Usage - Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Demonstrates the usage of the `inflate` command, including options to manage snapshots and disable inflation. The `inflate` command is used to create snapshots and expand ValueSets for a project or package.

```CLI
config inflate
inflate
```

--------------------------------

### Indexing and Output Folders - Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Describes the default output subfolder /.bake used by the `bake` command for indexing. This helps in managing the .index.json file by excluding source files and preventing duplicate entries.

```CLI
bake
```

--------------------------------

### Bundling Resources

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Combines all resources currently on the stack into a single FHIR Bundle resource. This is often a precursor to pushing to another server or system.

```bash
> fhir bundle    #Takes all resources on the stack and puts them into a single bundle
```

--------------------------------

### Listing Stack Contents

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Displays a list of all resources currently present on the Firely Terminal stack, showing their types and identifiers.

```bash
> fhir stack     #Lists the items on the stack
```

--------------------------------

### Comparison Commands - Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Introduces the experimental `diff` and `contentdiff` commands for comparing files. These commands are used to identify differences between two files.

```CLI
diff
contentdiff
```

--------------------------------

### Generating Snapshots

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Updates a StructureDefinition resource on the stack by generating its snapshot. Requires a StructureDefinition on the stack and a defined scope.

```bash
> fhir snapshot
```

--------------------------------

### Firely Terminal ValueSet Expansion Command

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The `expand` command in Firely Terminal is used to expand a ValueSet, making all its included codes available for use or inspection.

```bash
expand

```

--------------------------------

### Showing Resource Tree

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Displays a tree representation of the resource at the top of the stack or from a specified file. This aids in inspecting resource structure.

```bash
> fhir show      #Displays a resource tree from a file or the top of the stack
```

--------------------------------

### Use Suite Validator in Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Demonstrates how to use the experimental suite validator in Firely Terminal by passing the `--suite` flag. This validator aligns closely with HL7 standards and offers more flexibility.

```bash
> fhir push mypatient.xml
> fhir validate --suite

```

--------------------------------

### Project Archiving - Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Details the `project archive` command, formerly known as `project pack`. This command is used to create a zipped archive of the current project.

```CLI
project pack
project archive
```

--------------------------------

### Sort Resources with 'sort'

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The 'sort' command arranges all elements on the stack based on a specified comparison expression. This allows for ordered processing of resources.

```cli
sort -e "Patient.name.family"
```

--------------------------------

### List Scoped Packages

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Managing-Packages

Lists all packages that are currently in scope for the folder context. It also provides commands to list direct dependencies.

```bash
> fhir scope

```

```bash
> fhir dependencies

```

```bash
> fhir deps

```

--------------------------------

### Test Semver Version Ranges

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Managing-Packages

Allows testing of version ranges against a package's available versions. It resolves the range to a specific version, indicating the version the range points to.

```bash
> fhir semver xyz.myprofiles 3.x

```

--------------------------------

### Add FHIR Server and Search for Patients (Firely Terminal)

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

This snippet demonstrates adding a FHIR server using a custom alias and URL, then searching for Patient resources with a specified count. It's a common pattern for initial data access.

```shell
> fhir server add myserver https://myxmlfhirserver.com/fhir/
> fhir search myserver Patient _count=20
```

--------------------------------

### Configure Firely Terminal Remote Project

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Commands to configure and view details of the remote project link in Firely Terminal. This allows a FHIR project folder to have a different name than its corresponding URL key in Simplifier.

```bash
> fhir project remote <urlkey>

```

```bash
> fhir project remote --details

```

--------------------------------

### Saving Resources

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Saves the resource at the top of the stack to disk. The file format (JSON or XML) can be specified, or inferred from the file extension.

```bash
> fhir save      #Saves the file to disk
```

```bash
> fhir save --xml
```

--------------------------------

### Split Bundles with 'split --all'

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The 'split --all' command allows for the division of all bundles currently held on the terminal's stack into individual resources. This simplifies the handling of bundled FHIR data.

```cli
split --all
```

--------------------------------

### Firely Terminal Predicate Command

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The `predicate` command evaluates a FHIRpath predicate against a resource and returns a boolean result (true/false), useful for conditional logic and validation.

```bash
predicate

```

--------------------------------

### Display FHIR Resource Tree

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/FHIR-Client

Generates a tree rendering of the FHIR resource currently on the stack. This provides a hierarchical view of the resource, similar to what is seen in tools like Forge.

```bash
> fhir show

```

--------------------------------

### Reading Resources

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Retrieves a resource from a FHIR server by its type and an identifier, such as a name. The fetched resource is then placed on the stack.

```bash
> fhir read firely Patient name=Chalmers
```

--------------------------------

### Reverse Resource Order with 'reverse'

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The 'reverse' command inverts the order of all resources currently present on the terminal's stack. This is helpful for processing resources in a Last-In, First-Out manner.

```cli
reverse
```

--------------------------------

### Firely Terminal Reverse Command

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The `reverse` command in Firely Terminal reverses the current order of resources in a stack, offering flexibility in processing sequences.

```bash
reverse

```

--------------------------------

### Firely Terminal Sorting Command

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The `sort` command in Firely Terminal is used to arrange the order of resources within a stack, providing better organization and predictability.

```bash
sort

```

--------------------------------

### NDJSON Handling - Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Shows how Firely Terminal can process NDJSON data, either from local files or URLs. This functionality allows reading NDJSON into the stack or writing it to disk.

```CLI
read NDJSON from file
read NDJSON from URL
```

--------------------------------

### Firely Terminal FQL4 Typename Function

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Shows how to use the `typename()` function in FQL4 to retrieve the type of the current node, which is useful for data introspection.

```sql
typename()

```

--------------------------------

### Duplicating the Top Resource

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Creates a copy of the resource currently at the top of the stack. This is useful when you need to perform multiple different operations on the same resource.

```bash
> fhir duplicate
```

--------------------------------

### Splitting a Bundle

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Deconstructs a FHIR Bundle resource at the top of the stack into its individual constituent resources, placing each on the stack separately.

```bash
> fhir split     #Splits the bundle on the top of the stack into separate resources
```

--------------------------------

### Run Recommended Quality Control Ruleset in Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Quality-Control

Executes the recommended set of Quality Control rules in Firely Terminal, as suggested by Firely. This provides a more comprehensive validation of FHIR data.

```bash
fhir check recommended
```

--------------------------------

### Converting XML to JSON

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Converts a FHIR resource from XML format to JSON format. This involves pushing an XML file onto the stack and then saving it with a .json extension.

```bash
> fhir push mypatient.xml
> fhir save mypatient.json
```

--------------------------------

### Converting JSON to XML

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Converts a FHIR resource from JSON format to XML format. This is achieved by pushing a JSON file onto the stack and then saving it with a .xml extension.

```bash
> fhir push mylabreport.json
> fhir save mylabreport.xml
```

--------------------------------

### Swapping Top Stack Elements

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Exchanges the positions of the top two resources on the stack. This is useful for reordering resources immediately before an operation.

```bash
> fhir swap      #Swaps the top 2 elements on the stack
```

--------------------------------

### Manage Package Cache

Source: https://docs.fire.ly/projects/Firely-Terminal/package_management/Managing-Packages

Lists all packages currently in the global package cache on your machine. The '--location' or '-l' parameter can be used to display the folder location of the FHIR package cache.

```bash
> fhir cache

```

```bash
> fhir cache --location

```

--------------------------------

### Save Search Results as JSON (Firely Terminal)

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

This command takes the results from a previous search (e.g., the Patient search) and saves them in JSON format. It assumes the search context is already established.

```shell
> fhir save --all --json
```

--------------------------------

### Filtering Resources on the Stack

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Filters the resources on the stack based on provided FHIRPath expressions. Only resources that match the expression remain on the stack.

```bash
> fhir filter    #Filters the stack on matching FhirPath expressions
```

--------------------------------

### Enable Canonical Claim Checking in Firely Terminal Rules

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

A custom Quality Control rule for Firely Terminal to enable canonical claim checking. This rule specifies the action and a descriptive status message.

```yaml
- action: claims
  status: Checking if all conformance resources adhere to your canonical claims # or write your own text here.

```

--------------------------------

### Evaluate FHIRpath Expression with 'predicate'

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The 'predicate' command evaluates a FHIRpath expression against the top resource on the stack, returning true or false. This is useful for conditional logic within the terminal.

```cli
predicate -e "Patient.gender = 'male'"
```

--------------------------------

### Run Custom Quality Control Ruleset in Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Quality-Control

Executes a custom Quality Control ruleset stored in a .rules.yaml file. The user specifies the rule set by adding its name to the `fhir check` command.

```bash
fhir check <name>
```

--------------------------------

### Sorting Resources on the Stack

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Sorts the resources on the stack based on a specified expression. The sorting criteria can be any valid FHIRPath expression.

```bash
> fhir sort      #Sorts the stack based on the expression
```

--------------------------------

### Add FHIR Server Alias

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/FHIR-Client

Adds a new FHIR server to Firely Terminal with a specified alias and URL. This allows users to easily connect to different FHIR servers.

```bash
> fhir server add <alias> https://myserver/fhir
```

--------------------------------

### Search with _count Parameter

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/FHIR-Client

Searches for FHIR resources while specifying the maximum number of results to return using the `_count` parameter. This overrides the default result set maximum.

```bash
> fhir search firely Patient _count=20

```

--------------------------------

### Run Minimal Quality Control Ruleset in Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/Quality-Control

Executes the default, minimal set of Quality Control rules within the Firely Terminal. This command is used for basic validation of FHIR data.

```bash
fhir check
```

--------------------------------

### Execute FQL Query in Firely Terminal

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/FQL

This snippet demonstrates how to execute an FQL query within the Firely Terminal. It uses the 'fhir query' command followed by the FQL statement to select given names from Patient resources.

```shell
> fhir query "from Patient select name.given"

```

--------------------------------

### Rename 'remove' to 'uninstall'

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The command for removing packages has been renamed from 'remove' to 'uninstall' for clarity.

```cli
uninstall <package_name>
```

--------------------------------

### Firely Terminal File Deletion Command

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The `file delete` command allows for the removal of resources from a folder based on a FHIRpath expression, enabling targeted data management.

```bash
file delete

```

--------------------------------

### Control Log Levels

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

Firely Terminal offers various log levels to control the verbosity of output, including 'silent', 'brief', 'normal', 'detailed', and 'debug'.

```cli
fhir --log-level debug
```

```cli
fhir --log-level normal
```

--------------------------------

### Peeking at the Top Stack Item

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Displays the top item on the stack without removing it. This allows for a quick inspection of the resource before further operations.

```bash
> fhir peek      #Displays the top item on the stack
```

--------------------------------

### Validating Resources

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Validates the resource at the top of the stack against the current scope. This checks for compliance with FHIR standards, including StructureDefinitions, data types, and value sets.

```bash
> fhir validate
```

--------------------------------

### Reversing Stack Order

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Reverses the order of all resources currently on the stack. This operation affects the sequence in which subsequent operations are applied.

```bash
> fhir reverse   #Reverses the order of all resources on the stack
```

--------------------------------

### Save FHIR Resources

Source: https://docs.fire.ly/projects/Firely-Terminal/additional_features/FHIR-Client

Saves all resources currently on the Firely Terminal stack to the working directory. This is useful after performing searches to persist the retrieved data.

```bash
> fhir save --all

```

--------------------------------

### Rename 'mode' to 'spec'

Source: https://docs.fire.ly/projects/Firely-Terminal/Release-Notes

The command used to switch FHIR specifications has been renamed from 'mode' to 'spec'.

```cli
spec R4B
```

--------------------------------

### Dropping Resources from the Stack

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Removes the resource at the top of the stack. This is used to discard resources that are no longer needed.

```bash
> fhir drop
```

--------------------------------

### Clearing the Stack

Source: https://docs.fire.ly/projects/Firely-Terminal/getting_started/Resource-Operations

Removes all resources currently present on the internal stack. This operation is irreversible.

```bash
> fhir clear
```
Tokens:
Raw