Difference between revisions of "Roadmap"
(→ART-DECOR Release 2.0 (2016+)) |
(→Special features) |
||
Line 50: | Line 50: | ||
* {{ProgressBar| 70}} Difference analysis of DECOR artefacts (per project, on demand) | * {{ProgressBar| 70}} Difference analysis of DECOR artefacts (per project, on demand) | ||
* {{ProgressBar |50}} Introduce history storage of DECOR artefacts (template, value set, scenarios/transactions), re-write history mechanism for dataset concepts later to follow the same rules | * {{ProgressBar |50}} Introduce history storage of DECOR artefacts (template, value set, scenarios/transactions), re-write history mechanism for dataset concepts later to follow the same rules | ||
− | * {{TAGTODO}} Logger for changes in datasets, | + | * {{TAGTODO}} Logger for changes in datasets, value sets, templates, with connection to ADANS for change notifications |
* {{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] |
Revision as of 13:08, 10 December 2016
Contents
ART-DECOR Release 2.0 (2016+)
Note that ART-DECOR 2.0 is currently in planning/developing phase. The list below depicts the wish list, support or feature requests received before prioritization. Some features may be postponed after prioritizing.
- Coverage20% doneRefactor menu / front end structure SF#178 SF#144
- Coverage90% doneDocument/provide UI guidance for HL7 package creation SF#179
- Done
Datasets/Concepts
- Coverage40% doneSupport for creating new dataset in ART (scratch/existing) 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
- To Do
- Done
- Coverage10% doneAdd diagnostics to schematron engine to support assert/report types/catgeories of errors/warnings SF#284
Value Set
- Coverage50% doneCreate concept lists from value sets and propose value sets from concept lists SF#190
Code system support
- Coverage40% doneSolution for code system authoring, release management SF#177
Building Block Repositories (BBR)
- Coverage10% doneBBR Clearing House, a governance policy what artefacts may be propagated to a repository (quality criteria, prices, etc.)
- Done
- Done
Scenarios
- To Do
- Coverage10% doneSupport restricting valuesets/conceptList in a scenario SF#107
- Done
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
- To Do
- To Do
Community
Project Management
- Done
Special features
- Coverage70% doneDifference analysis of DECOR artefacts (per project, on demand)
- Coverage50% doneIntroduce history storage of DECOR artefacts (template, value set, scenarios/transactions), re-write history mechanism for dataset concepts later to follow the same rules
- To Do
- Coverage80% doneSupport for v2.xml SF#185 SF#174
- To Do
- Coverage70% doneSupport for partial publications (filtering) SF#189
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
Role Based Access to DECOR
- Coverage40% 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 |
ART-DECOR Release 1.8 (February 2016)
- Done
- Done
- Done
- Done
Datasets/Concepts
- Won't fix
- Done
Templates
- Done
- Done
- Done
- Done
- Done
- Done
Building Block Repositories (BBR)
- Done
Value Set
- Done
ART-DECOR Release 1.0 (2014)
Building Block Repositories (BBR)
- Done
- Done
- Done
- Done
- Done
System Services
- Done
- Done
- Done
Issues
- Done
- Done
- Done
- Done
- Done
Value Set
- Done
Special features
- Done
- Coverage80% doneSupport of v2.xml and v2 data types
Templates
- Done
- Done
- Done
- Done
Terminologies
- Done
- Done
- Done
Scenarios
- Done
- Done
Identifications
- Done
- Done
- Done
- Done
Concepts
- Done
- Done
Application generation
- Done
Testing
ART-DECOR Release 0.9 (2013)
Data Set
- Done
Scenario
- Done
Value Set
- Done
- Done
Templates
- Done
- Done
Documentation
- Done
- To Do
- Done
- Done
- To Do
- Done
- To Do
- Done
- Done
- Done
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do