Skip to main content
The Website Services team at NHS England are testing early designs to understand how you find information. Your views will help us check our ideas work. Sign up to take part in our user research.

NHS England Terminology Server environments

An overview of the Terminology Server environments and how FHIR terminology resources move through them before publication.

The NHS England Terminology Server has four environments for developing, testing and publishing FHIR terminology resources (code systems, value sets and concept maps).

Image of the Terminology Server with icons representing the authoring environment, staging environment, general use (production 1) environment and direct care clinical use (production 2) environment

What this image shows

FHIR terminology resources can be created in the authoring environment or in third-party authoring systems.

The resource is then moved to the staging environment where it is assured (tested).

Once assured, it can be moved to general use (production 1) and direct care clinical use (production 2) environments where the resource is published (made available).

The environments are:

  1. Authoring
    For developing FHIR terminology resources.
  2. Staging
    For testing FHIR terminology resources.
  3. General use (production 1)
    For publishing FHIR terminology resources to be read by any user or system.
  4. Direct care clinical use (production 2)
    For publishing FHIR terminology resources to be read by live clinical systems that support direct care.

There is also a syndication server for retrieving available releases for use in local terminology servers or similar systems and for receiving notifications of new resources.

Each environment and the syndication server can be seen as an endpoint (the URL that people and systems use to connect to read or author FHIR terminology resources). By changing the endpoint you're changing the environment you're connecting to.

To access these, see How to access.


Authoring environment

Authoring is used in a similar way to a traditional development environment.

FHIR terminology resources can be authored using tools such as Snapper or uploaded from external systems such as TRUD. Users with the appropriate permissions can also create new resources and Communities.

Once in authoring, users control access to resources using Communities. When ready, they can promote resources to staging for testing.


Staging environment

Staging is similar to a traditional test environment.

When a FHIR terminology resource is created, either in authoring or externally, it can be loaded into staging so it can be assured in a production-like environment.

Staging allows owners to review the resource and assess its impact on related resources.

Once the owner is satisfied with the resource in staging, it can be promoted to the general use (production 1) and direct care clinical use (production 2) environments.


General use (production 1) and direct care clinical use (production 2) environments

There are two production environments:

  • General use (production 1)
  • Direct care clinical use (production 2)

Both environments contain the same FHIR terminology resources but are designed for different purposes.

General use (production 1) environment

This is a high-performance, general-use environment for analytical and back-end functions. It can also be used for system development and resource-intensive activities, such as data migration.

Direct care clinical use (production 2) environment

This is also a high-performance environment, reserved for live systems that support direct care (see what we define as direct care). This helps maintain the capacity and performance needed for direct care services.
 

Last edited: 16 October 2026 2:08 pm