Download Request a demo

Platform · Interoperability

Interoperability built on open international standards.

Moana stores and exchanges clinical data as FHIR R4, supports SMART on FHIR app launch and FHIR bulk export, and translates HL7 v2 messages to and from FHIR. DICOM, ICD 10, ICD 11, SNOMED CT, LOINC, RxNorm and UCUM keep information meaningful wherever it travels.

A national health information system is never one product: laboratories, imaging, pharmacies, insurers, registries and national platforms must all exchange information reliably.

Request a demo See the standards supported

For ministries, integrators and development partners.

Shown with demonstration data

What it does

FHIR R4 with SMART on FHIR, and more.

  • FHIR R4 server

    Clinical data is available as FHIR R4 resources through a standard API.

  • SMART on FHIR

    Approved third party apps launch inside Moana with the patient in context, using SMART on FHIR.

  • FHIR bulk export

    Whole populations exported in the FHIR bulk data format for analytics and national reporting.

  • HL7 v2 messaging

    The Moana gateway translates HL7 v2 messages to and from FHIR R4 for systems that still speak HL7 v2.

  • Coded terminology

    ICD 10, SNOMED CT, LOINC and UCUM, so a diagnosis or a result means the same thing everywhere.

  • Master patient index

    One identity for each patient across facilities, with possible duplicates held for review.

  • Two way HL7 and FHIR conversion

    Messages convert between HL7 v2 and FHIR R4 in both directions, so older systems can join the network.

  • Full message logging

    Every message in and out is logged, so integrators can trace exactly what was sent and received.

  • DHIS2 reporting

    Aggregate indicators reported to DHIS2 from routine data.

4 modules in Interoperability: FHIR and HL7

  • FHIR R4 Data Hub
  • HL7 v2 Receiver
  • HL7 to FHIR Conversion
  • Message Log

See every interoperability module

Overview

Interoperability: FHIR and HL7

Open standards, so data can move.

A national health information system is never one product. It is laboratories, imaging departments, pharmacies, insurers, registries and national reporting platforms that must exchange information reliably. Moana is designed for interoperability from its data model upward, so it can be the clinical core of that architecture or one participant within it.

Clinical data is available as FHIR R4 resources through a standard API. Approved third party applications launch inside Moana with the patient in context using SMART on FHIR, and whole populations can be exported in the FHIR bulk data format for analytics and national reporting.

For systems that still exchange HL7 v2, the Moana gateway converts messages to and from FHIR R4 in both directions and logs every message for traceability.

Terminology is coded at the point of capture: ICD 10 and ICD 11 for diagnoses, SNOMED CT for clinical findings, LOINC for laboratory tests, RxNorm for medicines and UCUM for units.

A master patient index maintains one identity per person across facilities, with possible duplicates held for review. Aggregate indicators are reported to DHIS2, and the architecture follows OpenHIE patterns.

Standards supported

Specific, so your technical team can check it.

Standards supported by Moana and how Moana uses each one
StandardHow Moana uses it
HL7 FHIR R4Central data hub on HAPI FHIR with 27 standard resource types, including Patient, Encounter, Observation, Condition, MedicationRequest, Immunization, DiagnosticReport, ImagingStudy and Specimen.
SMART on FHIRApproved third party apps launch inside Moana with the patient in context.
FHIR Bulk DataPopulation level export for analytics and national reporting.
HL7 v2ADT, ORM, ORU, SIU and MDM messages over MLLP, with two way conversion to FHIR.
DICOM and DICOMwebMedical imaging through Moana PACS, or through a hospital’s existing PACS.
SNOMED CTClinical terminology, under an affiliate licence.
ICD 10 and ICD 11Diagnoses and cause of death coding.
LOINCLaboratory tests and results.
RxNormMedication terminology.
UCUMUnits of measure for doses and results.
DHIS2Aggregate national reporting, including from the Medical Supply System.
ASTM and HL7Connections to laboratory analysers and instruments.

In the product

Every screen is the real Moana interface, shown with demonstration data.

Shown with demonstration data

Coded diagnoses flowing from the EHR into national programmes.

How data moves

From the point of capture to national reporting.

  1. Coded at captureICD 10 and ICD 11, SNOMED CT, LOINC, RxNorm and UCUM are applied as data is recorded.
  2. One identityThe master patient index keeps one identity per person, with possible duplicates held for review.
  3. Stored as FHIR R4Clinical data is held as FHIR R4 resources, available through a standard API and to SMART on FHIR apps.
  4. Exchanged and loggedThe gateway converts HL7 v2 to and from FHIR R4 and logs every message in and out.
  5. Reported nationallyPopulations export as FHIR Bulk Data, and aggregate indicators are reported to DHIS2.

Outcomes

What changes for your organisation.

  • No vendor lock in

    Data is held and exchanged in open, documented formats.

  • Connects what already exists

    Analysers, PACS, legacy HL7 systems and national platforms join the network.

  • Meaning preserved

    Coded terminology keeps a diagnosis or result consistent across systems.

  • Ready for national architecture

    FHIR, DHIS2 and OpenHIE alignment support ministry integration plans.

Works with

Part of the same platform, coded in open formats.

Part of the same platform

Coded and exchanged in open formats

  • FHIR R4
  • SMART on FHIR
  • FHIR Bulk Data
  • HL7 v2
  • DICOM
  • ICD 10
  • ICD 11
  • SNOMED CT
  • LOINC
  • RxNorm
  • UCUM
  • DHIS2
  • OpenHIE

Who uses it

Built for the people who connect health systems.

  • MinistriesFHIR, DHIS2 and OpenHIE alignment for national integration plans.
  • IntegratorsEvery message logged, so you can trace exactly what was sent and received.
  • Development partnersData held and exchanged in open, documented formats, with no vendor lock in.
  • Third party app teamsApproved apps launch inside Moana with the patient in context, using SMART on FHIR.

Questions

Frequently asked questions.

Ask us something else

Does Moana support SMART on FHIR?

Yes. Approved third party applications can launch inside Moana with the patient in context using SMART on FHIR.

Can Moana exchange data with systems that use HL7 v2?

Yes. The Moana gateway converts HL7 v2 messages to and from FHIR R4 and logs every message.

Does Moana report to DHIS2?

Yes. Aggregate indicators are reported to DHIS2 from routine data.

See Moana with your own workflows.

We will walk your team through the platform using the departments and reports you work with every day.

Request a demoExplore the platform