Creating CodeSystems for DSF Processes

Creating CodeSystems for DSF Processes

Sometimes it is necessary to create custom CodeSystem resources. For example, when defining the type of an Input Parameter. CodeSystems for the DSF differ from regular CodeSystems in that some element's values are managed by the DSF BPE server. The following template can be populated with custom values:

<CodeSystem xmlns="http://hl7.org/fhir">
    <meta>
        <tag>
            <system value="http://dsf.dev/fhir/CodeSystem/read-access-tag" />
            <code value="ALL" />    
        </tag>  
    </meta>
    <url value="http://dsf.dev/fhir/CodeSystem/my-code-system" />       <!--dummy value-->
    <!-- version managed by bpe -->
    <version value="#{version}" />
    <name value="My CodeSystem" />      <!--dummy value-->
    <title value="My CodeSystem Title" />       <!--dummy value-->
    <!-- status managed by bpe -->
    <status value="unknown" />
    <experimental value="false" />
    <!-- date managed by bpe -->
    <date value="#{date}" />
    <publisher value="DSF" />       <!--dummy value-->
    <description value="CodeSystem with codes for me" />        <!--dummy value-->
    <caseSensitive value="true" />
    <hierarchyMeaning value="grouped-by" />
    <versionNeeded value="false" />
    <content value="complete" />
    <concept>
        <code value="my-code" />        <!--dummy value-->
        <display value="My Code" />     <!--dummy value-->
        <definition value="My code used for myself" />      <!--dummy value-->
    </concept>
</CodeSystem>

Dummy values should be replaced with appropriate values. Elements managed by the DSF BPE server should not be changed. More codes can be added by defining more concept elements.

When building a plugin, the CodeSystem is expected to be in src/main/resources/fhir/CodeSystem of the Java project.

Related Topics

Adding Task Input Parameters to Task Profiles, CodeSystem, Creating ValueSets for DSF processes, ValueSet