A FHIR platform for authoring, serving and distributing clinical terminology
Which suite, which mode, how many tests, how often — and can we run it ourselves, against our own installation?
Authoring terminology, serving it and the knowledge work around it are different jobs, so each gets its own product — on one engine, behind one sign-in. Authoring and serving have opposite risk profiles, and their separation is the point: the public surface carries no editing code and no write path to your content of record. They scale, patch and get exposed on separate schedules — and you can use one without the other.
Peers in the same sign-in, each with its own screens. They share one idea with the terminology server: a machine proposes, a person decides, and the record shows which was which.
Terminology is federated by nature — no single server owns SNOMED CT, LOINC, HL7’s vocabularies and your national extensions at once.
mg/dL validates against g/L, a
class of clinical data error terminology servers routinely cannot catch.
| Cost | Free. Apache 2.0 with Commons Clause, no licence fee. Supported by HELEX Solutions Ltd and TalTech |
|---|---|
| Conformance | Every test in HL7’s own suite, in its current form — nightly; re-runnable by you, on your installation |
| FHIR releases | R4 and R5 served from one content set; positioned for R6 — the mount is reserved |
| Architecture | Several products over one proven engine — editor, viewer, wiki, SNOMED authoring, coding discovery, clinical guidelines, FHIR profiling (optional) — in one sign-in |
| Distribution | FHIR Subscriptions and server-to-server syndication, on open standards |
| Tenancy | Multitenancy switched on per installation — organisation and personal workspaces, private by default; one boundary, expressed once |
| Reach | Your content, SNOMED CT, LOINC, HL7 vocabularies, partner servers and published guides — through one endpoint |
| Scale | A full LOINC release — about 3 million rows — in about ninety seconds |
| Publishing | Implementation guides released as standard packages; an installation can host its own package registry |
| Migration | A one-shot tool, not an engagement — a national deployment’s full content set, 68 code systems and 217,786 concepts, in ten and a half minutes; re-runnable, and it changes nothing the second time |
| Trust | Published versions immutable, nothing destroyed, every change attributable |
| Fit | Your identity provider, your brand, your languages, your extensions |
Three steps, none of which needs a proposal cycle.
There is no sales motion to get past. Adopting organisations work with the team directly on migration, on the features their deployment is missing, and on support — free of charge. Write to info@helex-solutions.com.