Module map 

The deployment’s category map: which categories the data under a template or an archetype belong to (Regulation (EU) 2025/327 Annex II 3.2(c)).

No adopted act and no openEHR specification ties a template or an archetype to an Art 14(1) category, so the deployment declares it: each template id and each archetype id maps to a set of categories, or to none, the deployment’s statement that the data under it are of no category. The crate ships no map. A template key wins over an archetype key for the same object, because a template is the clinical context the archetype is used in (no specification governs the map: our own design).

A key is compared exactly by default. Declared with Matching::OpenEhr, the map compares template and archetype ids as openEHR BASE asks of every composite identifier: case-insensitively, while the evidence keeps each id as the access named it (BASE Release 1.3.0, Base Types, Identification Package, “Composite Identifiers and Case”). Archetype keys are held to the ARCHETYPE_ID grammar of the same package either way.

The map’s CategoryMap::canonical text is the same for the same declarations in any order, so a digest of it names the map a record was classified under.

Structs

CategoryMap

The deployment’s category map.

MapErrors

Every defect of a refused map declaration, in table and key order.

Enums

Declared

One declaration as a configuration writes it: the word none, or a list of categories.

MapError

Why a map was refused.

Mapping

What a key maps to.

Matching

How a map compares an id with its keys.

Table

The two tables a map keys on.

Constants

NONE

The word a declaration uses for data of no category.