One concept, one code
“Acute infarction”, “AMI” and “myocardial infarction” are the same concept. Coded with SNOMED CT, it means the same at the hospital, the clinic and the laboratory.
Terminology
Kivú Terminology
Terminology services to centralize clinical vocabularies — SNOMED CT included — with validation, expansion and semantic normalization.
What it solves
Codes get validated in every system, and differently
When each application keeps its own copy of the catalogues, the same test is coded two ways and nobody can say which version governs. The correction arrives once the data has already been published.
Capabilities
SNOMED CT as a service
CodeSystem / ValueSet
Code validation
ValueSet expansion
Semantic normalization
SNOMED CT as a service
The reference clinical terminology, available to all your systems
SNOMED CT is the most comprehensive clinical terminology in the world: diagnoses, findings, procedures, organisms and substances, each with a unique identifier and logical relationships to the others. Kivú Terminology makes it available as a shared service, so your applications query it instead of each keeping its own copy.
Hierarchies that roll up
Every concept knows its “parents”. That lets you group data at any level — all ischemic heart disease, for example — without listing hundreds of codes.
Value sets per use case
Each form, profile or integration uses only the part of the terminology that applies to it, defined once as a ValueSet and shared by everyone.
How it works
Your systems ask; the service answers with the same criteria for all of them
Your systems
- Health record
- Laboratory
- Imaging
- Applications and integrations
Kivú Terminology
- SNOMED CT
- CodeSystem and ValueSet
- Code validation
- ValueSet expansion
- Semantic normalization
Outcome
- Data coded the same everywhere
- Errors caught before publishing
- Comparable, reusable information
Use cases
Where a shared terminology service makes a difference
Clinical data capture
Form pick lists come from expanded value sets, so staff choose among valid concepts instead of typing free text.
Validation at integration
Before a resource is published or exchanged, each code is validated against the value set that applies to it.
Normalizing local codes
Each system's own catalogs are brought to SNOMED CT concepts, so data from different sources can be joined.
Laboratory, imaging and pathology
Results, findings and diagnoses coded consistently across centers, as Costa Rica's national roadmap sets out.
HL7 FHIR guides
The profiles of an implementation guide state which value set applies to each element, and the service resolves them.
Registries and analytics
With data coded in SNOMED CT, cohorts, indicators and national registries are built on the same meaning.
Where it fits
Services where this component can show up
As one option among several. The service neither depends on Kivú nor assumes it.
This component is an option, not a requirement: Meddyg's services can be delivered on your own infrastructure, on a third party's, or with Kivú components.