WeHub Term

Map it, validate it,
serve it.

WeHub Term is the terminology server for healthcare integrations. Load SNOMED CT, ICD-10 and LOINC, map your local codes to them, and serve it all over a FHIR terminology API.

Get it onMicrosoft Marketplace

Terminology server

It's all in here

Code systems

Import the official code systems, or author your own. Local and custom systems work exactly like the standards same tools, same standing.

Value sets

Pick codes directly, or set the rules and let it resolve. Either way it stays accurate as the underlying terminology changes.

Concept maps

Link concepts across systems to design a map.

Hosted standards

Fresh from the source

Always the latest

Each official release is pulled straight from the publisher, validated and versioned on the way in. You're always on the latest.

The big ones are here

SNOMED CT, ICD-10, LOINC and more, hosted and kept current plus your own local and custom systems alongside.

Fast at scale

Designed to stay fast as your terminology grows, with no trade-off in accuracy.

FHIR API

A complete, conformant engine

The full terminology operation set, plus standard resource access complete and standards-conformant, with nothing stubbed out.

Full operation set

$lookup, $validate-code, $expand, $subsumes, $translate and $closure.

Full CRUD

Create, read, update and delete resources over the standard FHIR REST API.

Self-describing

Every capability is declared in a live CapabilityStatement you can check yourself.

See CapabilityStatement →

Governance

Versioned, validated, ready to serve

Keep canonical URLs, definitions and updates clear as clinical teams maintain the terminology their integrations rely on.

Version history

Track each release and update so downstream integrations know exactly what they are using.

Validation first

Validate metadata, concepts and status before terminology is made active.

Standards and local codes

Run official, local and custom code systems side by side in one terminology workspace.

Servers

Cardiology clinical team

Active

/fhir/cardiology

Code systems

4

Value sets

7

Concept maps

2

Concepts

1,842

Renal pathways

Active

/fhir/renal

Code systems

6

Value sets

3

Concept maps

4

Concepts

3,225

Maternity records

Active

/fhir/maternity

Code systems

2

Value sets

1

Concept maps

0

Concepts

428

Workforce management

Draft

/fhir/workforce

Code systems

2

Value sets

1

Concept maps

0

Concepts

428

Deploy

Run Term where your data lives

Same FHIR terminology API and the same code systems in each.

Your Azure tenant

Runner

Inside your own Azure tenant. Data never leaves.

See the footprint
Air-gapped · HSCN

Self Hosted

Your infrastructure, air-gapped or HSCN.

See the footprint

FAQ

Common questions

WeHub Term is a FHIR R4 terminology server for healthcare integrations. It hosts SNOMED CT, ICD-10 and LOINC alongside your own local and custom code systems, and serves them all over the standard FHIR terminology API, so your integrations look up, validate and translate codes from one place.

SNOMED CT, ICD-10 and LOINC are hosted and kept current. Each official release is pulled from the publisher, then validated and versioned on the way in. You can also import other official code systems or author your own, and local systems work with the same tools as the national standards.

The full terminology operation set: $lookup, $validate-code, $expand, $subsumes, $translate and $closure. You also get create, read, update and delete over the standard FHIR REST API. Every capability is declared in a live CapabilityStatement, so you can check conformance yourself before you integrate.

Yes. Build concept maps that link concepts in your local code systems to their equivalents in SNOMED CT, ICD-10 or any other hosted system. Your integrations then call $translate to convert a local code to the standard one at run time, instead of holding mapping tables in each interface.

Each release is versioned when it arrives, and Term keeps a version history so downstream integrations know exactly which version they use. Metadata, concepts and status are validated before any terminology is made active. Value sets defined by rules resolve against the current release, so they stay accurate as the terminology changes.

Three ways. Managed, hosted by WeHub on Azure in the UK, with UK data residency (UK South) and per-customer tenant isolation. Runner, inside your own Azure tenant, deployed from Microsoft Marketplace, so terminology requests stay within your boundary. Or Self Hosted, on your own infrastructure. The same FHIR API is available in each.

More answers in the WeHub FAQ

Ready when you are

Stand up a terminology server on your own systems.

We'll deploy WeHub Term in the infrastructure your data has to stay in, loaded with the code systems your integrations rely on.