Amy-Term

Release Notes

Versioned changelog for the Amy-Term terminology platform.

Tip: For full API exploration, use the interactive OpenAPI UI at /docs.

Version 1.0.0 – Production Baseline

Release status: Production Release date: 2025-12-26

Overview

This release establishes a production-grade baseline of the Amy-Term terminology platform. The platform supports national, regional, and institutional deployments, including environments with intermittent or no network connectivity.

Core features

  • Native persistence of CodeSystems, Concepts, ValueSets, and ConceptMaps.
  • FHIR-compatible terminology operations: $lookup, $expand, $translate, $validate-code.
  • Integrated support for ATC (WHO), ATC-GKV (Germany), and SNOMED CT via Snowstorm.
  • Role-based access control (Admin / Viewer).
  • Federation and offline replication.

Supported terminology artifacts

CodeSystems

  • Local CodeSystems managed via Excel uploads and maintained in the internal Postgres store.
  • SNOMED CT via Snowstorm browser/$lookup with branch-aware capabilities and RF2 import hooks.
  • RxNorm (Postgres-backed) for distributor-managed drug terminology when `RXNORM_ENABLED=true`.
  • ATC / ATC-GKV with dedicated browsing tools and FHIR-friendly lookup.

ValueSets

  • Authoring with Tools/Designer and upload-based creation for local ValueSets.
  • SNOMED-based expansions (ECL-based, filter-based) powered by Snowstorm.
  • Bundled federation exports containing ValueSet payloads for downstream nodes.

ConceptMaps

  • Namespace-aware ConceptMap CRUD via Excel/JSON imports.
  • Exploratory translation tooling (ConceptMap/$translate) prepared for future automation.
  • Support for federation capture/export of translation artifacts.

User interface

  • Dashboard with role-aware navigation.
  • Tools & Designer workspace for ValueSet and ConceptMap authoring.
  • ATC Browser with code-level search and FHIR $lookup integration.
  • Federation Capture UI for explicit export control.

Federation

  • Explicit capture of exportable artefacts.
  • Namespace-aware federation.
  • Signed bundle export.
  • Offline bundle application.

API & integration

Interactive OpenAPI / Swagger documentation:

OpenAPI UI
http://localhost:8000/docs

Known limitations

  • OWL reasoning is not enabled in the baseline.
  • High-volume expansions require paging configuration.
  • SNOMED analytics depend on Snowstorm deployment and indexing configuration.

Versioning policy

  • MAJOR – breaking schema or API changes.
  • MINOR – backward-compatible feature additions.
  • PATCH – bug fixes and performance improvements.
Example version labels
$ 1.0.0   # production baseline
$ 1.1.0   # backward-compatible features
$ 1.1.1   # bug fixes
$ 2.0.0   # breaking changes

References

Related documentation pages: