Difference between revisions of "Roadmap"
(→Datasets/Concepts) |
(→ART-DECOR Release 2.0 (2016+)) |
||
Line 3: | Line 3: | ||
* {{ProgressBar |20}} Refactor menu / front end structure [https://sourceforge.net/p/artdecor/tickets/178/ SF#178] [https://sourceforge.net/p/artdecor/tickets/144/ SF#144] | * {{ProgressBar |20}} Refactor menu / front end structure [https://sourceforge.net/p/artdecor/tickets/178/ SF#178] [https://sourceforge.net/p/artdecor/tickets/144/ SF#144] | ||
* {{ProgressBar |90}} Document/provide UI guidance for HL7 package creation [https://sourceforge.net/p/artdecor/tickets/179/ SF#179] | * {{ProgressBar |90}} Document/provide UI guidance for HL7 package creation [https://sourceforge.net/p/artdecor/tickets/179/ SF#179] | ||
+ | |||
+ | ==Datasets/Concepts== | ||
+ | * {{TAGTODO}} Exceptions for all value domains | ||
+ | * {{ProgressBar |40}} Support for creating new dataset in ART (scratch/existing) [https://sourceforge.net/p/artdecor/tickets/152/ SF#152] | ||
+ | * {{TAGTODO}} Support binding a concept/valueDomain to an identification system (scratch/existing) [https://sourceforge.net/p/artdecor/tickets/127/ SF#127] | ||
+ | |||
+ | ==Templates/Rules== | ||
+ | * {{TAGTODO}} Add support for FHIR profile viewing | ||
+ | * {{TAGTODO}} Add support for FHIR profiles to act as like other artefacts regarding Building Block Repositories | ||
+ | |||
+ | ==Code system support== | ||
+ | * {{ProgressBar|40}} Solution for code system authoring, release management [https://sourceforge.net/p/artdecor/tickets/177/ SF#177] | ||
+ | |||
+ | ==Testing== | ||
+ | * {{ProgressBar |70}} Refactoring the XIS package [https://sourceforge.net/p/artdecor/tickets/161/ SF#161] <span style="text-decoration: line-through;">[https://sourceforge.net/p/artdecor/tickets/139/ SF#139]</span> <span style="text-decoration: line-through;">[https://sourceforge.net/p/artdecor/tickets/80/ SF#80]</span>; move to more general approach, support multiple languages | ||
+ | * {{TAGTODO}} Support new validation service. Is code X in valueset Y [https://sourceforge.net/p/artdecor/tickets/132/ SF#132] | ||
+ | |||
+ | ==Building Block Repositories (BBR)== | ||
+ | * {{ProgressBar|10}} BBR Clearing House, a governance policy what artefacts may be propagated to a repository (quality criteria, prices, etc.) | ||
+ | * {{ProgressBar|10}} Make IHE profile templates (e.g. PCC, XD*Lab) available | ||
+ | * {{ProgressBar|90}} Make CCDA Release 2 templates available | ||
+ | * {{TAGTODO}} Make list and DECOR representation of IHE profiles templates available | ||
+ | |||
+ | ==Scenarios== | ||
+ | * {{TAGTODO}} Editor: locking ([https://sourceforge.net/p/artdecor/tickets/196/ SF#196]), flow, layout | ||
+ | * {{TAGTODO}} Implement creating and maintaining Transaction “Defaults” (typical scenarios) [https://sourceforge.net/p/artdecor/tickets/8/ SF#8] [https://sourceforge.net/p/artdecor/tickets/12/ SF#12] [https://sourceforge.net/p/artdecor/tickets/119/ SF#119] [https://sourceforge.net/p/artdecor/tickets/17/ SF#17] | ||
+ | * {{ProgressBar|10}} Support restricting valuesets/conceptList in a scenario [https://sourceforge.net/p/artdecor/tickets/107/ SF#107] | ||
+ | |||
+ | ==Value Set== | ||
+ | * {{ProgressBar |50}} Create concept lists from value sets and propose value sets from concept lists [https://sourceforge.net/p/artdecor/tickets/190/ SF#190] | ||
+ | |||
+ | ==Community== | ||
+ | * {{TAGTODO}} Publication support for communities [https://sourceforge.net/p/artdecor/tickets/134/ SF#134] | ||
+ | * {{TAGTODO}} Add support for valueset annotation [https://sourceforge.net/p/artdecor/tickets/135/ SF#135] | ||
+ | |||
+ | ==Special features== | ||
+ | * {{TAGTODO}} Support for FHIR resources and profiles [https://sourceforge.net/p/artdecor/tickets/184/ SF#184] | ||
+ | * {{ProgressBar| 50}} Difference analysis of DECOR artefacts (per project) | ||
+ | * {{TAGTODO}} Logger for changes in datasets, valuesets, 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] | ||
+ | * {{TAGTODO}} Support for HL7 V3 data types R2 [https://sourceforge.net/p/artdecor/tickets/140/ SF#140] | ||
+ | * {{TAGTODO}} Support for partial publications (filtering) [https://sourceforge.net/p/artdecor/tickets/189/ SF#189] | ||
+ | * {{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}} Refactor OID Viewer [https://sourceforge.net/p/artdecor/tickets/193/ SF#193] | ||
+ | * {{TAGTODO}} Refactor OID Manager [https://sourceforge.net/p/artdecor/tickets/194/ SF#194] | ||
+ | * {{TAGTODO}} Refactor OID Requests [https://sourceforge.net/p/artdecor/tickets/195/ SF#195] | ||
+ | * {{TAGTODO}} Add a formal approval mechanism for transactions, and possibly dataset subtrees [https://sourceforge.net/p/artdecor/tickets/201// SF#201] | ||
+ | |||
+ | ==Role Based Access to DECOR== | ||
+ | * {{ProgressBar |40}} Implement 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: | ||
+ | {| class="artdecor" border="1" width="100%" | ||
+ | |- | ||
+ | ! | ||
+ | ! 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 | ||
+ | |+ '''Table: Role Based Access setup for DECOR''' | ||
+ | |} | ||
=ART-DECOR Release 1.8 (February 2016)= | =ART-DECOR Release 1.8 (February 2016)= |
Revision as of 12:00, 20 February 2016
Contents
ART-DECOR Release 2.0 (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.
- Coverage20% doneRefactor menu / front end structure SF#178 SF#144
- Coverage90% doneDocument/provide UI guidance for HL7 package creation SF#179
Datasets/Concepts
- To Do
- Coverage40% doneSupport for creating new dataset in ART (scratch/existing) SF#152
- To Do
Templates/Rules
- To Do
- To Do
Code system support
- Coverage40% doneSolution for code system authoring, release management SF#177
Testing
- Coverage70% doneRefactoring the XIS package SF#161 SF#139 SF#80; move to more general approach, support multiple languages
- To Do
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
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.8 (February 2016)
- Done
- Done
- Done
- Done
Datasets/Concepts
- To Do
- Won't fix
- 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