Difference between revisions of "Roadmap 22"
(→Value Set) |
(→Special features) |
||
Line 35: | Line 35: | ||
* {{ProgressBar |80}} Support for v2.xml [https://sourceforge.net/p/artdecor/tickets/185/ SF#185] [https://sourceforge.net/p/artdecor/tickets/174/ SF#174] | * {{ProgressBar |80}} Support for v2.xml [https://sourceforge.net/p/artdecor/tickets/185/ SF#185] [https://sourceforge.net/p/artdecor/tickets/174/ SF#174] | ||
* {{TAGTODO}} Support for HL7 V3 data types R2 [https://sourceforge.net/p/artdecor/tickets/140/ SF#140] | * {{TAGTODO}} Support for HL7 V3 data types R2 [https://sourceforge.net/p/artdecor/tickets/140/ SF#140] | ||
− | |||
* {{TAGTODO}} Implement user settings that remember UI status [https://sourceforge.net/p/artdecor/tickets/104/ SF#104] | * {{TAGTODO}} Implement user settings that remember UI status [https://sourceforge.net/p/artdecor/tickets/104/ SF#104] | ||
* {{TAGTODO}} Update/change rich text editor feature set [https://sourceforge.net/p/artdecor/tickets/188/ SF#188] [https://sourceforge.net/p/artdecor/tickets/50/ SF#50] | * {{TAGTODO}} Update/change rich text editor feature set [https://sourceforge.net/p/artdecor/tickets/188/ SF#188] [https://sourceforge.net/p/artdecor/tickets/50/ SF#50] | ||
Line 43: | Line 42: | ||
* {{TAGTODO}} Add a formal approval mechanism for transactions, and possibly dataset subtrees [https://sourceforge.net/p/artdecor/tickets/201// SF#201] | * {{TAGTODO}} Add a formal approval mechanism for transactions, and possibly dataset subtrees [https://sourceforge.net/p/artdecor/tickets/201// SF#201] | ||
* {{TAGTODO}} Add support for subscription on publication sites (ADRAM served)[https://sourceforge.net/p/artdecor/tickets/302/ SF#302] | * {{TAGTODO}} Add support for subscription on publication sites (ADRAM served)[https://sourceforge.net/p/artdecor/tickets/302/ SF#302] | ||
+ | * {{TAGTODO}} Logger for changes in datasets, value sets, templates, with connection to ADANS for change notifications | ||
* {{TAGDONE}} Introduce history storage of DECOR artefacts (template, value set, scenarios/transactions), re-write history mechanism for dataset concepts later to follow the same rules | * {{TAGDONE}} Introduce history storage of DECOR artefacts (template, value set, scenarios/transactions), re-write history mechanism for dataset concepts later to follow the same rules | ||
− | * {{ | + | * {{TAGDONE}} Support for partial publications (filtering) [https://sourceforge.net/p/artdecor/tickets/189/ SF#189] |
==Role Based Access to DECOR== | ==Role Based Access to DECOR== |
Revision as of 15:37, 2 March 2020
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
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
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 |