Difference between revisions of "Roadmap"
(→ART-DECOR Release 2.0 (2016+)) |
|||
Line 1: | Line 1: | ||
=ART-DECOR Release 2.0 (2016+)= | =ART-DECOR Release 2.0 (2016+)= | ||
− | =ART-DECOR Release 1.8 ( | + | =ART-DECOR Release 1.8 (February 2016)= |
Note that ART-DECOR 2.0 is currently in planning phase. The list below depicts the wish list before prioritization. Some features may be postponed after prioritizing. | Note that ART-DECOR 2.0 is currently in planning phase. The list below depicts the wish list before prioritization. Some features may be postponed after prioritizing. | ||
Revision as of 09:14, 11 February 2016
Contents
ART-DECOR Release 2.0 (2016+)
ART-DECOR Release 1.8 (February 2016)
Note that ART-DECOR 2.0 is currently in planning phase. The list below depicts the wish list before prioritization. Some features may be postponed after prioritizing.
- To Do
- Coverage90% doneDocument/provide UI guidance for HL7 package creation SF#179
- Done
- To Do
- Done
- Done
Datasets/Concepts
- To Do
- To Do
- Coverage40% doneSupport for creating new dataset in ART (scratch/existing) SF#152
- To Do
- Done
Templates
- Done
- Done
- Done
- Done
- Done
- Done
Testing
- Coverage70% doneRefactoring the XIS package SF#161 SF#139 SF#80; move to more general approach, support multiple languages
- To Do
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.)
- Coverage10% doneMake IHE profile templates (e.g. PCC, XD*Lab) available
- Coverage90% doneMake CCDA Release 2 templates available
- To Do
Scenarios
- To Do
- To Do
- Coverage10% doneSupport restricting valuesets/conceptList in a scenario SF#107
Value Set
- Coverage50% doneCreate concept lists from value sets and propose value sets from concept lists SF#190
- Done
Community
Special features
- To Do
- Coverage50% doneDifference analysis of DECOR artefacts (per project)
- To Do
- 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
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.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
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