skills.rest
aks-builds
aks-buildsCOMMUNITY
Explore all skills by this author →
GitHub

terminology-services

Provides healthcare code system validation, FHIR terminology operations, mapping, and reference guidance for engineers.

1|1|Updated May 16, 2026
Search Tags:#FHIR#code systems#healthcare terminologies#terminology services#FHIR terminology operations
One-click install
npx skills add https://github.com/aks-builds/healthcareskills --skill terminology-services
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: terminology-services
Source: https://github.com/aks-builds/healthcareskills/tree/main/skills/terminology-services
Command: npx skills add https://github.com/aks-builds/healthcareskills --skill terminology-services

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive resource for healthcare terminologies and terminology services, offering guidance on code systems, validation, mapping, and more, tailored for software engineering in healthcare.

Core Features & Use Cases

  • Healthcare Code Systems Reference: Comprehensive information on various code systems (SNOMED CT, ICD-10-CM, etc.) with their scope, identifiers, and use cases.
  • FHIR Terminology Operations: Detailed explanations and examples of FHIR terminology operations like $lookup, $validate-code, $expand, $translate, $subsumes, and $closure.
  • Public Terminology Sources: Guidance on accessing public terminology sources like VSAC, UMLS, RxNav, and SNOMED International Browser.
  • Terminology Server Options: Information on various terminology servers including Ontoserver, Snowstorm, HAPI FHIR JPA terminology, and HL7 Terminology Service.

Quick Start

Use the terminology-services skill to retrieve information on SNOMED CT, including its scope, identifier, hierarchy, concept model, and editions.

Frequently Asked Questions about terminology-services

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are FHIR terminology operations and how do they work with healthcare code systems?▼

FHIR terminology operations are standard API interactions like $lookup, $validate-code, $expand, $translate, $subsumes, and $closure used to query, validate, and map healthcare code systems such as SNOMED CT and ICD-10-CM.

How do I validate a code against a healthcare terminology system using FHIR?▼

To validate a code in a healthcare terminology system, you use the FHIR $validate-code operation to check if a specific code exists within a given ValueSet or code system and retrieve its correct definition.

What public terminology sources are available for healthcare engineering?▼

Public terminology sources available for healthcare engineering include VSAC, UMLS, RxNav, and the SNOMED International Browser, which provide access to standardized clinical vocabularies and code systems for integration.

What terminology server options exist for deploying FHIR terminology services?▼

Terminology server options for deploying FHIR terminology services include Ontoserver, Snowstorm, HAPI FHIR JPA terminology, and HL7 Terminology Service, each offering different runtime environments for processing clinical vocabularies.

What is the best way to map codes between different healthcare terminologies?▼

The best way to map codes between different healthcare terminologies is by using the FHIR $translate operation, which executes concept map translations to convert codes from one clinical code system to an equivalent target system.

Do I need expertise in FHIR standards to use terminology services for healthcare engineering?▼

Yes, expertise in FHIR standards and healthcare terminologies is required, because terminology services target healthcare engineers involved in FHIR resource modeling, clinical decision support, and complex terminology mapping.

Related Skills

Explore More Software Engineering Skills→
StanfordSpeziStanfordSpezi
22

fhir-data-model-design

Map clinical concepts to FHIR R4 resources and output a Data Model Specification document.

Official
Advanced
nahisahonahisaho
3

scientific-clinical-standards

Map clinical terminology codes across LOINC, ICD-10/ICD-11, and FHIR.

Community
Advanced
aehrcaehrc
133

hapi-fhir-server

Implement FHIR servers with HAPI FHIR Plain Server framework.

Official
Advanced
maziyarpanahimaziyarpanahi
5.0k

linking-umls-concepts

Map OpenMed clinical entities to UMLS Concept Unique Identifiers via the UTS API.

Community
Advanced