Page tree
Skip to end of metadata
Go to start of metadata

This page gathers together links for tools that work with or on profiles for FHIR. Tools are categorised into several functional categories:

Editing / Authoring Profiles

The following choices exist for editing profiles

  • By hand
    • Use a schema drive editor against Profile.xsd in the FHIR schemas
    • start with an existing profile (look for the link under the structure definition on the page for the resource)
    • edit the profile as you see fit
    • Note: profiles are full rich description of the content, and so they're pretty hard to edit by hand. You can do this but it's not the intention

Use of spreadsheets is no longer recommended (except for certain HL7-internal profiles) and hand editing is tedious and error prone. Generally, choose one of the other approaches.

Validating Resources against Profiles

You can validate a resource against a profile in several different ways.

  • On the web
    • On the Validation page of Simplifier.net you can, after creating a free account, validate any resource against the core FHIR specification or any published FHIR package.
      • Simplifier.net also allows you to store and validate one FHIR project for free. Other features require a paid subscription.
  • Via API
    • You can use the [validation] interaction on any of the Public Test Servers or your own FHIR server instance.
      • use a RESTful client like [POSTman], or write code to do this in the background
      • post the resource as described by the validation operation, and tag it with the profile you wish it to be tested against (see below)
      • most servers require the profile to be hosted on the server itself
  • On the command line
  • In code

Marking that a resource conforms to a profile

See the explanation of meta.profile in the section on resource metadata. Note that this is only a conformance claim and no guarantee that the resource actually conforms. Every server can test these claims, test resources against any other profile and can update the values in meta.profile accordingly.

Publishing Profiles

FHIR resources can be published as a stable, coherent set called a FHIR Package (see the NPM Package Specification).

This should generally be accompanied by documentation, called an Implementation Guide.

Finding Packages and Implementation Guides

All publicly available FHIR packages are available in https://registry.fhir.org. For more information see FHIR Package Registry User Documentation.

Implementation Guides can be found from the link on their package page or on the Implementation Guide Registry (fhir.org).

Creating and publishing Packages and Implementation Guides

  • On the command line
  • On the web
    • Simplifier.net provides a webinterface for creating packages and Implementation Guides. Free for one project.
      • See the documentation on Creating packages. Packages will automatically be added to the FHIR Registry on publishing.
      • See the documentation on Creating Implementation Guides. Implementation guides can be hosted or exported and self-hosted (paid).
  • Other



  • No labels