Roadmap 22
Contents
ART-DECOR Release 2.2 (spring 2020)
Note that some features will be postponed after prioritizing.
Datasets/Concepts
- Coverage80% doneSupport for creating new dataset in ART (scratch/existing), backend done, better UI support to follow SF#152
- To Do
- To Do
Templates/Rules
- Coverage80% doneSupport for FHIR resources and profiles SF#184
- Coverage80% doneAdd support for FHIR profiles to act as like other artefacts regarding Building Block Repositories
- Coverage10% doneAdd diagnostics to schematron engine to support assert/report types/categories of errors/warnings SF#284
Value Set
Nothing new planned for this release
Code system support
- Coverage40% doneSolution for code system authoring, release management SF#177
Building Block Repositories (BBR)
Done
Add better statistics function
Scenarios
- To Do
- Coverage10% doneSupport restricting valuesets/conceptList in a scenario SF#107
FHIR Support
- Coverage90% doneFHIR R4 support including export of value sets, code systems, logical models, identification schemes, concept maps
Testing
- Coverage90% doneLive Runtime Compile LRC Validation
- Coverage60% doneInstance Fragment Validation IVF
- Coverage70% doneRefactoring the XIS package SF#161 SF#139 SF#80; move to more general approach, support multiple languages
- Coverage70% doneSupport new validation service. Is code X in valueset Y SF#132
Special features
- Coverage90% doneDifference analysis of DECOR artefacts (per project, on demand)
- Coverage80% doneSupport for v2.xml SF#185 SF#174
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- Done
- Done
External Services Support
- Done
- Coverage90% doneADAWIB allows processing artefacts of very large governance groups
- Coverage50% doneADAWIB allows to export to Confluence environments
- Coverage10% doneADAWIB allows to export to WordPress environments
Role Based Access to DECOR
- Coverage60% doneImplement more fine grained role based access to DECOR. As is currently the case, everyone regardless of role, has read access. You need to be someone with a specific background to gain write access too. You need to be appointed specially to also perform certain tasks such as finalizing a dataset/value set/template. This last category of tasks is dubbed authorization. The exact user stories behind each role and maybe a better name then "authorize" is to be determined. This proposal should also include xis (and xis-admin?), governance groups and communities. Proposal:
read/write | authorize | |
---|---|---|
decor-admin | all | all |
dataset-editor | dataset | |
dataset-admin | dataset | dataset |
terminology-editor | terminology | |
terminology-admin | terminology | terminology |
scenario-editor | scenario | |
scenario-admin | scenario | scenario |
templates-editor | templates | |
templates-admin | templates | templates |
issues-editor | issues | issues |