DRAFT SMART Guidelines L3 SOP, published by TBD. This is not an authorized publication; it is the continuous build for version 0.2.1). This version is based on the current content of https://github.com/DigitalSQR/smart-ig-starter-kit and changes regularly. See the Directory of published versions

Code Systems

Code Systems are created when new codes need to be defined A special case of code system is when existing codes need to be complemented - for example adding designations in different languages to codes, or adding relationships between vaccine codes.

Inputs:

• L2 DAK

Outputs:

• CodeSystem resources in input/codesystems or input/fsh/codesystems

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:

• no QA issues in the publisher

Change tracking

Tooling:

Tool	Usage	Doc
Sushi
OCL
tx.fhir.org

Informative examples

Known issues and dependencies: