Features
Ready to get started? Upgrade now
| Entry | Professional | Team | Enterprise | |||||
|---|---|---|---|---|---|---|---|---|
| Build FHIR Resources | ||||||||
| Dynamic FHIR resource rendering |
Dynamic FHIR resource renderingSimplifier’s dynamic FHIR rendering automatically chooses the best view for each resource type. Profiles are displayed as a logical tree showing element names, flags, cardinality, types and constraints, with separate tabs for details, mappings, table view and raw XML/JSON. Value sets and code systems display their expansions and codes in concise tables. Related resources are linked. Within implementation guides you can embed renderings using statements like {{tree}}, {{table}}, {{json}} or {{xml}} to insert a resource’s tree, table, JSON or XML representation.
You can even embed Simplifier’s renderer in external websites via an iframe; on Enterprise plans that embed can be shown without the “powered by Simplifier” logo. |
|||||||
| Import JSON and XML as files or via the FHIR API |
Import JSON and XML as files or via the FHIR APISimplifier’s Import feature lets you ingest FHIR resources into a project using several methods. You can upload individual resources or bundled JSON/XML files, including zipped archives. The upload form also accepts pasted JSON/XML code and can split bundled resources into separate entries. If your data lives elsewhere, you can fetch resources directly from any FHIR server via a GET request or a FHIR search query, or post them using any FHIR client. |
|||||||
| Audit log and change tracking |
Audit log and change trackingSimplifier’s audit log and change tracking provides complete traceability for your FHIR resources and projects. Every event—such as resource creation, update or deletion—is recorded with the user who made the change, the timestamp, the resource and action, and the origin of import. The project log lists all modifications across the project and allows you to subscribe via Atom feed for notifications. At the resource level, the history tab stores each version of the resource; a diff viewer lets you compare any two versions side by side in XML or JSON, highlighting differences and enabling you to track evolution and ensure accountability. |
|||||||
| Online resource editor for FHIR Shorthand |
Online resource editor for FHIR ShorthandSimplifier’s Online Resource Editor for FHIR Shorthand offers convenient in-browser editing of FHIR resources in FSH, XML or JSON. The editor, available via project menus, supports syntax highlighting, live validation and dynamic rendering for FSH files. It can also convert FSH into JSON with a Generate button. The environment is zero installation; you can manage multiple .fsh files, handle package dependencies, and see immediate visualization of changes as you type.
For XML and JSON resources, the editor also provides syntax highlighting and validation, making modeling easier directly in your browser. |
|||||||
| Forge, the world’s leading desktop editor for FHIR resources |
Forge, the world’s leading desktop editor for FHIR resourcesForge is a desktop application that provides a graphical interface for creating, editing and validating FHIR conformance resources. Its feature-rich GUI lets modelers build and manage profiles, extensions, logical models, search parameters and operation definitions by constraining base resources, adding slices or extensions and binding value sets. Forge also generates snapshots and offers real-time validation against FHIR specifications and custom rules. Users can fetch and publish profiles from/to FHIR servers or registries and synchronize projects with Simplifier with a single click. Widely adopted by organizations worldwide, Forge remains the most comprehensive desktop tool for FHIR resource modeling. It runs natively on Windows, and on macOS or Linux via a virtual machine. |
|||||||
| FQL Playground |
FQL PlaygroundThe FQL playground lets you run powerful queries across your FHIR metadata. The Firely Query Language blends familiar SQL syntax with JSON field definitions and FHIRPath expressions, letting you retrieve, filter and project data from any resource. A pipeline of from/where/select clauses turns hierarchical resources into tabular results for implementation guides or dashboards. On paid plans you can embed queries in your documentation using <fql> tags.
Use the playground to gain insights, detect inconsistencies and publish custom tables—turning raw FHIR data into actionable intelligence. |
|||||||
| FHIRPath Playground |
FHIRPath PlaygroundThe Simplifier FHIRPath playground lets you write and test FHIRPath expressions against any FHIR resource. FHIRPath itself is a lightweight, path-based language for navigating and extracting data from hierarchical FHIR models, supporting traversal, selection and filtering operations. FHIRPath functions such as exists() and count() help determine whether elements exist or how many there are. This allows you to build invariants in your profiles or validation rules in Quality Control.
Simplifier’s playground lets you load resources from different FHIR packages and projects, choose a version and experiment with expressions, including functions like hasValue() and resolve().
|
|||||||
| YamlGen (example generation) Playground |
YamlGen (example generation) PlaygroundYamlGen is a Simplifier playground that converts concise YAML into complete FHIR resources. Instead of manually composing extensive JSON or XML, you can define profiles or examples in standard YAML, using accelerators like Patient/4 or name.given to set IDs and nested properties.
The playground supports automatic data generation via $auto functions and can produce multiple resources from a single instruction. This makes it ideal for quickly creating example data and prototypes.
Try the YamlGen playground to transform simple YAML into structured FHIR content and accelerate your modeling workflow. |
|||||||
| GitHub Integration |
GitHub IntegrationSimplifier’s GitHub integration links your project to a GitHub branch or repository, so your project is updated automatically on every push. During setup you authorize the connection, select a repository and branch, and choose strategies for invalid or deleted files. Simplifier then fetches the resources, and subsequent pushes update, add or remove them automatically. Include/exclude patterns control which folders or file types are imported. A webhook lets you manage implementation guides in GitHub, with changes pushed back to Simplifier. Streamline collaboration and publish with confidence. |
|||||||
| Metadata Expressions editor |
Metadata Expressions editorSimplifier’s metadata expressions editor lets you customize how each resource’s metadata is derived and displayed. Using FHIRPath expressions, you can specify the Title, Description, UrlKey, Workflow status or FilePath for each resource type. Expressions follow the Resource.Property: FHIRPath convention and may combine values using functions like glue() or operators such as | and +. The editor supports comments and generic expressions for all resources.
Harness metadata expressions to provide meaningful context across your projects. |
|||||||
| Custom resource workflow |
Custom resource workflowCustom resource workflows let organizations define additional lifecycle statuses for resources, beyond FHIR’s standard From the organization settings you can create a custom workflow and specify status names that align with the underlying FHIR statuses. When enabled, search results show the custom workflow status next to each resource, and clicking it reveals all possible statuses and explanations. Use custom workflows to communicate resource maturity clearly and manage publishing processes within your team. |
|||||||
| Firely Terminal, the command line FHIR tool |
Firely Terminal, the command line FHIR toolFirely Terminal is your cross-platform command-line companion for FHIR development. Built on the open-source Firely .NET SDK, it automates validation, packaging, conversion and publication of FHIR resources on Windows, macOS and Linux. With its internal resource stack you can build pipelines to push, read, filter, bundle or save resources and interact directly with FHIR servers using CRUD commands. Firely Terminal also serves as a full FHIR package manager, supports FQL queries, and integrates seamlessly with Simplifier.net and GitHub Actions for CI/CD. Designed for scripting and automation, it brings speed, consistency and quality assurance to every step of your FHIR workflow. |
|||||||
| Validate | ||||||||
| Validator playground |
Validator playgroundSimplifier’s Validation playground offers several ways to ensure your FHIR assets comply with the standard and your own profiles. You can paste any resource into the validator, choose a FHIR version or package as context, and get a list of errors, warnings and messages with inline JSON and XML highlighting and filter controls. The same validator is available on every resource or snippet in a project, allowing authors to validate against the full dependency context. On paid plans, Quality Control extends this with bulk validation across every resource in a project, plus custom FHIRPath-based rules for business-specific checks. |
|||||||
| Quality Control Engine |
Quality Control EngineSimplifier’s Quality Control engine lets you run a comprehensive quality audit across your project. It executes a series of rule-based checks covering validation, naming conventions, canonical uniqueness and dependency integrity, and records issues in the project’s Issues tab for follow-up. You can run built-in “minimal” or “recommended” rulesets or add your own YAML rules. Rules can filter on specific files or resource types and use FHIRPath predicates to enforce business conventions. Actions include unique to ensure values (such as canonicals) are distinct, same to verify consistent metadata across resources, assert to unit-test expected error codes, and dependencies to analyze package versioning and completeness.
Using Quality Control helps ensure internal consistency and complete metadata, and avoids publishing surprises. |
|||||||
| Document | ||||||||
| Live Editor |
Live EditorSimplifier’s Live Editor is a browser-based, syntax-highlighted Markdown editor for implementation guides. From the Guides tab you create an IG, organize it into folders and pages, and work swiftly in a three-pane workspace—tree navigation, editor and live preview. In settings you define the title, privacy and style, and choose whether to draw resources from packages or your live project. Markdown pages can embed resource trees, JSON or tables using {{tree}}, {{json}} and other tags, plus dynamic FQL tables. YAML headers set topics or language for a page, and tree widgets let you choose diff, snap or hybrid views.
|
|||||||
| Implementation Guide Hosting |
Implementation Guide HostingSimplifier’s Implementation Guide hosting removes the burden of setting up your own web server. When you create or edit an IG, the platform automatically hosts the generated pages, giving your audience a permanent, shareable URL and making your guide discoverable by the FHIR community. Hosting is integrated with version management: you can publish snapshot releases of your guide and control who sees draft or final versions. If you prefer, you can export the guide as a static website and host it elsewhere. The hosted environment includes live preview and private/public options, saving you time and infrastructure costs. |
|||||||
| Export for self-hosting |
Export for self-hostingOn Simplifier’s paid plans you can take your guide off-platform. The export feature lets you download the entire implementation guide—including all pages and embedded resources—as a static HTML website with one click. This self-contained package can then be hosted anywhere, giving you full control over distribution without relying on Simplifier’s hosting service. |
|||||||
| Advanced scripting (FQL, PlantUML, YamlGen) |
Advanced scripting (FQL, PlantUML, YamlGen)Simplifier’s IG editor supports advanced scripting to make your documentation more dynamic and expressive. You can add FQL queries to generate live tables from your FHIR resources. These FQL statements are written in Markdown blocks; the editor evaluates them at refresh and can save them as reusable snippets across pages. The editor also accepts PlantUML scripts via <plantuml> tags, letting you embed automatically rendered diagrams alongside your IG content.
YamlGen converts concise YAML into complete FHIR resources. Instead of manually composing extensive JSON or XML, you can define profiles or examples in standard YAML, using accelerators like Patient/4 or name.given to set IDs and nested properties.
Together, these scripting features enable rich, data-driven guides. |
|||||||
| Custom Design |
Custom DesignOn paid plans, Simplifier offers several professionally designed templates for implementation guides. The three default templates—Ballotable, Tree Table and Two-Level Menu—come with HTML placeholders that render titles, versions, breadcrumb navigation and page indexes. Team plan users can customize these templates by adjusting the CSS and inserting optional placeholders for navigation bars or footers. The “Custom Layout” option opens a CSS editor, where you can edit the master HTML template and style sheet to alter colors, fonts or navigation styles and even add your own logo. You can reset to the original CSS or download it for comparison. |
|||||||
| Embedded resources outside of Simplifier |
Embedded resources outside of SimplifierSimplifier’s embedded rendering lets you display live FHIR resources on your own site without having to build a renderer. All users can generate an embeddable URL— https://www.simplifier.net/embed/render?id=<project>/<resource>—and include it inside an <iframe> tag on any page.
The service renders the resource as a tree, XML or table directly from Simplifier’s engine, so visitors always see the latest version. Projects must be public for the embed to work, and you can adjust the height and width of the iframe to fit your layout, making it easy to enrich your own website or documentation with authoritative FHIR content. Embedded renderings carry a “powered by Simplifier” logo; on Enterprise plans this logo can be removed for fully unbranded rendering. |
|||||||
| Publish | ||||||||
| Package generation wizard |
Package generation wizardThe package generation wizard lets you convert your project into a compliant FHIR package in just a few steps. From the Releases tab you can click Create new package, enter a name, a version number (SemVer format), a description and release notes, and indicate whether it’s a pre-release. The wizard then compiles your profiles, extensions and examples into the proper folder structure and publishes them to Simplifier’s npm-compatible package server. If you include a package.bake.yaml file, you can precisely control what goes into the package—include or exclude snapshots, select specific resources and even transform FSH files into JSON.
The highest version automatically receives a latest tag and every published package remains available, giving partners confidence that your data contracts will be discoverable and reusable.
|
|||||||
| Custom build pipelines (Bake) |
Custom build pipelines (Bake)The Bake functionality lets you script customized build pipelines to assemble FHIR packages and other publications. A Bake script is written in YAML and consists of one or more pipes made up of filters and actions. Each pipe reads from an input bucket, applies filters (like selecting active conformance resources or example instances) and executes actions such as generating content, transforming formats, moving files or adding snapshots. You can generate resources from YamlGen or FSH scripts using the yamlgen and fsh actions, convert XML to JSON with transform, create snapshots and merge or move files between buckets.
A typical pipeline moves active profiles and examples into a staging bucket, generates resources, transforms them to JSON, then adds a package.json and creates an index file.
Bake scripts give precise control over your package’s contents and structure, making it easy to automate releases and ensure compliance. |
|||||||
| Versioned Implementation Guides (Published guides) |
Versioned Implementation Guides (Published guides)The Published Guides feature lets you release static snapshots of an implementation guide, separate from the live, editable version. A published guide is versioned and disconnected from your source project, so you can publish ballot or final releases without affecting ongoing work. The typical workflow is to create a FHIR package, change your IG’s scope to that package to verify it, then publish a snapshot and switch back to editing. Each version can be made public or private, read-only or overwritable, and set as the default guide for your URL. |
|||||||
| Canonical resolver |
Canonical resolverThe canonical resolver turns a resource’s unique FHIR canonical into a working URL for human-readable documentation. Every resource and project can have its own documentation URL; when someone enters the canonical into the https://simplifier.net/resolve endpoint, they are redirected to that page, falling back to the resource’s Simplifier page if no custom URL is set.
The resolver accepts parameters for FHIR version, scope and package version. You can even host a forwarding script on your own domain to pass canonical requests to Simplifier’s resolver, ensuring consistent, discoverable links to your FHIR artifacts. |
|||||||
| Collect Feedback | ||||||||
| Community feedback |
Community feedbackCommunity feedback lets you capture and curate public comments on your projects and guides. Enabling issue tracking adds an Issues tab to each resource, where users can post new issues, read existing conversations and filter them by status. Issues may be logged at resource or project level and commenters automatically follow discussions; you can also subscribe to new issues and updates via an Atom feed. This turns your documentation into a living dialogue with the community. |
|||||||
| Limit feedback to team only |
Limit feedback to team onlyYou can fine-tune who participates in feedback. Issue tracking is enabled in the project settings, with two scope controls: one determines whether issues are visible to all Simplifier users or only your project members; the other decides who can create or reply to issues—any logged-in user or just team members. After turning issue tracking on, you can limit visibility so that only project members see community-reported issues. This allows a team to keep discussions private and maintain focus while still using Simplifier’s feedback tools. |
|||||||
| Subscribe to newly reported issues |
Subscribe to newly reported issuesSimplifier makes following discussions easy. When you report or comment on an issue, you’re automatically subscribed to updates, but you can also manage this manually. Each issue has a bell icon that lets you subscribe to or unsubscribe from notifications for that thread. To receive alerts whenever a new issue is filed across an entire project, go to the project page, click Subscribe in the upper-right corner and choose Subscribe to new issues. You can also grab the project’s Atom feed URL and paste it into any feed reader to stay informed about all changes. |
|||||||
| Custom issue statuses |
Custom issue statusesThe enhanced issue-tracking interface lets you replace generic open/closed statuses with your own workflow stages, such as “triaged”, “under review” or “feedback addressed”. Firely configures these statuses to match your governance and quality processes. Once activated, they appear in the Issues tab so you can assign, filter and track feedback easily. Combined with controls over who can see and post issues, customized issue statuses bring order and clarity to collaborative feedback. |
|||||||
| Collaboration | ||||||||
| Synchronization API |
Synchronization APIEvery project becomes a FHIR server accessible via a base URL, and Simplifier’s synchronization API allows you to keep a local folder in sync with the project. This means multiple team members can work offline and synchronize their contributions through Firely Terminal or Forge, then share them with the team. |
|||||||
| Share snippets and permanent URLs |
Share snippets and permanent URLsTo share work quickly, users can create a snippet by pasting a FHIR resource and sharing the link. Each uploaded resource also gets a permanent URL, making it easy to reference resources in emails, guides or publications. |
|||||||
| Public or private projects |
Public or private projectsProjects can be made public or private in the Manage menu. Private projects let teams work on intellectual property or drafts without exposing them to the community. Owners also choose whether project resources should be published to the HL7 FHIR Registry. |
|||||||
| Create a team |
Create a teamAs a project owner you can invite team members. Assign each member a role—Admin, Writer or Reader—that determines whether they can view resources, edit them, use the IG editor, synchronize content or manage the team. Rights can be changed later, so responsibilities can evolve. |
|||||||
| Enterprise teams |
Enterprise teamsAn enterprise license allows you to create multiple teams. A managing team has the same rights as the license owner and can create projects or manage other project teams. Project teams can be assigned to projects without each member having to accept an invitation. This helps large organizations organize collaborators and apply team-wide permissions in one step. |
|||||||
| Organization Portal |
Organization PortalThe organization portal is a public landing page designed to showcase your FHIR work to the wider community. The portal lists all your organization’s projects so visitors can easily find your profiles, implementation guides or packages. It also supports endorsement lists: curated collections of other projects you want to promote, created in the Endorsed projects tab and shown on the portal page. Because the portal is publicly accessible, it provides a central, branded hub where partners, customers and the FHIR community can discover and follow your organization’s FHIR initiatives. |
|||||||
| News |
NewsTo engage with stakeholders, you can post updates or announcements via the News tab, and these articles appear on the portal’s main page. |
|||||||
Browse through the features of Simplifier
Select a feature on the left to find out more.