The Amakomaya technology stack
Our platform is built in layers: the products people use, the information systems behind them, the interoperability layer that connects them, and the engineering practices that keep them running.
Digital Health Platforms
Web and mobile products for maternal, child and family health, counselling services, and health service navigation — designed for low-bandwidth conditions and Nepali-language users.
See Amakomaya's products and platform →Health Information Systems
DHIS2-based HMIS implementation, localized data capture, report generation and analytics for facility, municipal and national reporting workflows.
Read the HMIS platform documentation →Healthcare Interoperability
An HL7 FHIR-based interoperability layer and integration middleware that lets separately built systems exchange structured, standards-conformant health data.
Read the FHIR platform documentation →Engineering & Operations
Agile DevSecOps practices, hosting tuned to Nepal's connectivity realities, and an information security management system aligned with ISO/IEC 27001:2022.
Read how we approach information security →Healthcare interoperability
Amakomaya's technology ecosystem is built with modern healthcare interoperability standards, including HL7 FHIR, enabling structured and interoperable health data exchange between the systems that clinicians, programmes and citizens depend on.
Interoperability by design
Exchange is decided long before an API is called. The clinical workflow determines what has to be recorded, the data model determines how, and terminology determines whether the receiving system understands it. The standards come after those answers, not instead of them.
- Clinical workflow
- Data model
- Terminology
- FHIR
- DHIS2 / OCL
- APIs
- Connected health system
Use a global standard where it genuinely fits. Keep a local definition where no suitable international vocabulary exists.
FHIR Platform
Our FHIR environment hosts the resource endpoints and conformance artefacts used by Amakomaya's integrations.
Open the Amakomaya FHIR platform at https://fhir.amakomaya.com
Access to protected resources requires authorisation; no credentials are published on this website.
FHIR v6 upgrade
Amakomaya is upgrading its healthcare interoperability infrastructure toward FHIR v6, creating a stronger foundation for modern digital health data exchange and integration. The upgrade environment runs alongside the current platform so integrations can be validated before they move.
Explore the FHIR v6 upgrade environment at https://fhir.amakomaya.com/v6
The upgrade is in progress: production services continue to run on the current FHIR platform until each integration is migrated.
Integration workflows: OpenFn and n8n
Exchange between systems needs more than an endpoint: records have to be transformed, validated and moved on a schedule or an event. We use OpenFn for digital health and development-sector interoperability — DHIS2 integration, FHIR workflows, database synchronisation and partner reporting — and n8n for broader operational and business-process automation. Which tool runs a workflow depends on the systems involved, the deployment requirements and who maintains it.
From build to running service
A system is delivered when it is being used correctly, not when it passes its last test. These steps are where that difference is won.
- Design
- Build
- Test
- Validate
- Implement
- Train
- Monitor
- Improve
Clinical and user validation
The people who will use the system check that it matches the workflow it was designed for, before it reaches them in production.
Interoperability testing
Conformance checked against the profiles an exchange depends on, so non-conformant data is rejected rather than quietly accepted.
Data quality
Validation rules run against real data, with failures visible and attributable rather than absorbed silently.
Security and usability
Authorisation, access control and audit under an ISMS aligned with ISO/IEC 27001:2022 — alongside whether the interface can actually be used in a busy facility.
Standards we build with
Standards are what make health data portable between systems, institutions and years. These are the ones our engineering and consulting work centres on.
HL7 FHIR
Resource model and RESTful APIs for exchanging clinical and administrative data.
HL7 v2
Messaging still in use across laboratory and hospital systems we integrate with.
ICD
Classification of diseases for reporting, statistics and claims.
SNOMED CT
Detailed clinical terminology for structured documentation.
LOINC
Identifiers for laboratory tests and clinical observations.
OpenHIE
Architecture pattern for national-scale health information exchange.
Planning an integration?
If you are connecting an EMR, laboratory system, registry or programme platform, we can help you map it onto a standards-based exchange model.
Talk to our interoperability team