SpecsModelExplore
Overview
Actors
External Systems
Clinical Data Product
Clinical Ingestion
HL7 Gateway
FHIR Gateway
Mapping Service
Mapping EngineTerminology ServiceRule Repository
Clinical Data
Analytics & Research
Clinical Apps
Governance & Audit
Mapping Service
Internal structure
Components
Mapping pipeline
Resolve codes
Emit canonical events
SpecsModelExplore
Mapping Service
OverviewGuideLinks and Communications

Mapping Service

The Mapping Service transforms parsed HL7 into the platform’s canonical clinical model, resolving coded values through terminology services before Clinical Data services consume the result.

Why a canonical layer

Hospitals send different field layouts and local codes. Mapping once here keeps Patient Master and Encounter Service free of HL7 specifics.

Internal structure

Could not build diagram for model "example-healthcare".

Components

Mapping Engine

Applies mapping rules from HL7 to canonical.

Terminology Service

Resolves coded values (SNOMED, LOINC).

Rule Repository

Versioned mapping rules.

Mapping pipeline

Load rules

The Mapping Engine fetches versioned rules from the Rule Repository.

Resolve codes

The Terminology Service maps local codes to SNOMED, LOINC and internal enums.

Emit canonical events

Mapped patients, encounters and observations are handed to Clinical Data services.