Production Readiness Statement

One-page operational and governance readiness statement for regulated healthcare environments.

Summary Functional Operational Security Deployment Fitness

Scope: This statement describes the baseline production controls and operating assumptions for Amy-Term. Local organisational policies (identity governance, network security, change control, and incident management) remain required.

Statement metadata

Statement date: 2025-12-26 Release baseline: 1.0.0 Target: Regulated healthcare

Executive summary

Amy-Term is a production-ready terminology management and federation platform designed for regulated healthcare environments. It supports terminology governance, FHIR-compatible API access, controlled authoring, and offline-capable replication.

Primary deployment patterns include:

Centralised national or enterprise service with role-based authoring and controlled publication.
Regional replicas receiving signed content bundles (store-and-forward) for offline or intermittent connectivity.

OpenAPI UI

http://localhost:8000/docs

Functional readiness

Terminology lifecycle

Create, import, browse, and manage CodeSystems.
ValueSet authoring and curation via Tools & Designer.
ConceptMap authoring and curation for translation workflows.
Namespace-aware governance for multi-region or multi-tenant models.

FHIR operations

FHIR-style terminology operations: $lookup, $expand, $translate, $validate-code.
ATC workflows (WHO) and ATC-GKV browsing and lookup.
SNOMED CT connectivity through Snowstorm (external dependency).

Example: terminology calls

$ curl -s "http://localhost:8000/fhir/CodeSystem/$lookup?system=http://fhir.de/CodeSystem/atc-gkv&code=A02AA05"
$ curl -s "http://localhost:8000/fhir/ValueSet/$expand?url=http://example.org/fhir/ValueSet/my-valueset"

Operational readiness

PostgreSQL persistence with documented backup and restore procedures.
Role-based access control and session-based UI authentication.
Deterministic export controls via explicit federation capture (no implicit bulk export).
OpenAPI documentation available for integrators at /docs.

Example: health check

$ curl -s "http://localhost:8000/health/live"

Security readiness

Separation of viewer capabilities from admin-only authoring and federation actions.
Federation bundles support signing and verification (HS256 baseline).
Explicit selection of exportable artefacts; no implicit export of all content.
Namespace isolation supports multi-region governance.

Important: HS256 is acceptable as a baseline, but for multi-organisation federation you should move to asymmetric signing (for example Ed25519) with per-node keys, rotation, and revocation.

Deployment readiness

Supports centralised deployments and regional replicas.
Supports offline installations through store-and-forward bundle transfer.
Suitable for Ministries of Health, hospital networks, and research infrastructures.

Documentation entry points

$ http://localhost:8000/documentations
$ http://localhost:8000/docs

Statement of fitness

Amy-Term is fit for production use in healthcare environments, subject to standard organisational governance, operational controls, and security policies.