Page Comparison

...

<kmm:kmMetadataList xsi:schemaLocation="org.opencds.km.metadata.v1_0 ..\schema\OmgDssKmMetadata.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:kmm="org.opencds.km.metadata.v1_0">
  <kmMetadata>
    <identifier scopingEntityId="edu.utah" businessId="SCIP_VTE_2" version="2014.0.0" />
    <purpose language="en">SCIP VTE Rule</purpose>
    <explanation language="en">some explanation of the KM</explanation>
    <executionEngine>org.opencds.service.drools.v55.DroolsAdapter</executionEngine>
    <dataModel>org.opencds.vmr^VMR^1.0</dataModel>
    <knowledgeModulePrimaryProcessName>PrimaryProcess</knowledgeModulePrimaryProcessName>
  </kmMetadata>
  …
</kmm:kmMetadataList>

The knowledge module metadata is used by OpenCDS to determine which knowledge module will be used for processing the vMR input.

Two important pieces of information are critical: the edu.utah^SCIP_VTE_2^2014.0.0.pkg element and the knowledgeModulePrimaryProcessName element.

The attributes of the identifier element must match the file name of the knowledge module.  E.g., for the identifier in the example above, the file name of the knowledge module will be

edu.utah^SCIP_VTE_2^2014.0.0.pkg

The knowledgeModulePrimaryProcessName must be consistent with the name attribute of the process tag in the bpmn2 file (the asset in the Processes section of Guvnor).

All other fields (with the exception of purpose and explanation, should remain the same.

Export/Import Process

The steps involved for importing a Knowledge Module into OpenCDS are are as follows:

1. If you are using new concepts, add them to the relevant folder within the conceptMappingsSpecifications folder (see Concept Mappings).
2. If your Knowledge Module supports one or more Code Systems that are not currently specified in OpenCDS configuration, add them to openCDSCodeSystems.xml (see OpenCDS Code Systems).
3. If your Knowledge Module supports one or more concept types that are not currently specified in OpenCDS configuration, add them to supportedConceptsConfigFile.xml (see Supported Concepts).
4. New Knowledge Module
   
   1. If the knowledge module is new, export it from Guvnor and place the downloaded binary package into the knowledgeModules folder (see Configuration Overview).
   2. Add an entry for the new knowledge module in knowledgeModules.xml (see Knowledge Modules).
5. Replacing an Existing Knowledge Module
   
   1. If the knowledge module already exists and you want to replace it with changes made in Guvnor, you may replace the existing module; be sure the file name is consistent with the previous instance (see Configuration Overview).
6. Restart OpenCDS (v1.1.5 and earlier).

...