Amakomaya Nepal FHIR Implementation Guide
2.0.0 - ci-build Nepal

Amakomaya Nepal FHIR Implementation Guide - Local Development build (v2.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## Code Systems

Code Systems are created when new codes need to be defined

In particular, each SMART guideline will have a guideline-level code system defined with codes for all the concepts defined in the guideline (i.e. all the concepts defined in the data dictionary).

In addition, sometimes existing code systems need to be completed, for example adding designations in different languages to codes, or adding relationships between vaccine codes.

### Inputs

- L2 DAK

### Outputs

- CodeSystem resources

### Activities

The creation of a CodeSystem is typically driven by the following needs:

- When a ValueSets requires codes that are not in yet available from a CodeSystem
- When a mapping (e.g. a ConceptMap) requires codes that are not yet available from a CodeSystem

- When a new property must be added to a concept in a codesystem, using a supplement CodeSystem

- Care should be taken before creating codesystems. As the SMART ImplementationGuides and FHIR ecosystems evolve, the necessary codes are available and shared.
  - One exception is the internal codes for the data elements in the DAK (e.g. the unique concept `IMMZ.C.DE1`). These are created for every new element in a logical model.

This is the overview of the activities and related artifacts used:

### Output Criteria / Definition of Done

- Appropriate CodeSystem resources are defined

### Terminology Code Systems

The following code systems have been defined for this Implementation Guide:

- Application Mode for Amakomaya App
- Amakomaya Identifier Types
- Nepal Administrative Location Codes
- Tele Call Consent Categories

For the complete list of terminology code systems, please refer to the Artifacts section.