Extend ActivityDefinition for Process->Plugin relationship #188
Description
ActivityDefinitions currently contain the following information attributes:
"url": "http://medizininformatik-initiative.de/bpe/Process/feasibilityRequest",
"version": "1.0",
"name": "FeasibilityRequest",
"title": "Feasibility Request",
"subtitle": "Feasibility Request Process",
"status": "active",
"experimental": false,
"date": "2022-06-07",
"publisher": "MII",
as this example shows the direct relationship with the plugin a process belongs to has to be inferred or guessed and is not made explicit.
This means that when querying the ActivityDefinitions of a site it is difficult to get an overview of the installed plugins.
Related Problem
Describe the Solution You’d Like
The information about which plugin a process belongs to should be part of the activity definition - ideally with the version of the plugin.
Two conceivable ways to solve this are either:
- adding an extension to the ActivityDefinition which contains the information about the plugin and its version
- via naming convention and making the plugin part of the name. as in e.g.: pluginName-pluginVersion_processName-processVersion