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

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.

  • Coverage
    20% done
    Refactor menu / front end structure SF#178 SF#144
  • Coverage
    90% done
    Document/provide UI guidance for HL7 package creation SF#179

Datasets/Concepts

  • To Do
      
    Exceptions for all value domains
  • Coverage
    40% done
    Support for creating new dataset in ART (scratch/existing) SF#152
  • To Do
      
    Support binding a concept/valueDomain to an identification system (scratch/existing) SF#127

Templates/Rules

  • To Do
      
    Add support for FHIR profile viewing
  • To Do
      
    Add support for FHIR profiles to act as like other artefacts regarding Building Block Repositories

Code system support

  • Coverage
    40% done
    Solution for code system authoring, release management SF#177

Testing

  • Coverage
    70% done
    Refactoring the XIS package SF#161 SF#139 SF#80; move to more general approach, support multiple languages
  • To Do
      
    Support new validation service. Is code X in valueset Y SF#132

Building Block Repositories (BBR)

  • Coverage
    10% done
    BBR Clearing House, a governance policy what artefacts may be propagated to a repository (quality criteria, prices, etc.)
  • Coverage
    10% done
    Make IHE profile templates (e.g. PCC, XD*Lab) available
  • Coverage
    90% done
    Make CCDA Release 2 templates available
  • To Do
      
    Make list and DECOR representation of IHE profiles templates available

Scenarios

  • To Do
      
    Editor: locking (SF#196), flow, layout
  • To Do
      
    Implement creating and maintaining Transaction “Defaults” (typical scenarios) SF#8 SF#12 SF#119 SF#17
  • Coverage
    10% done
    Support restricting valuesets/conceptList in a scenario SF#107

Value Set

  • Coverage
    50% done
    Create concept lists from value sets and propose value sets from concept lists SF#190

Community

  • To Do
      
    Publication support for communities SF#134
  • To Do
      
    Add support for valueset annotation SF#135

Special features

  • To Do
      
    Support for FHIR resources and profiles SF#184
  • Coverage
    50% done
    Difference analysis of DECOR artefacts (per project)
  • To Do
      
    Logger for changes in datasets, valuesets, templates, with connection to ADANS for change notifications
  • Coverage
    80% done
    Support for v2.xml SF#185 SF#174
  • To Do
      
    Support for HL7 V3 data types R2 SF#140
  • To Do
      
    Support for partial publications (filtering) SF#189
  • To Do
      
    Implement user settings that remember UI status SF#104
  • To Do
      
    Update/change rich text editor feature set SF#188 SF#50
  • To Do
      
    Refactor OID Viewer SF#193
  • To Do
      
    Refactor OID Manager SF#194
  • To Do
      
    Refactor OID Requests SF#195
  • To Do
      
    Add a formal approval mechanism for transactions, and possibly dataset subtrees SF#201

Role Based Access to DECOR

  • Coverage
    40% done
    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:
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)

  • Done
      
    IHE metadata DECOR data set for XDS SF#187
  • Done
      
    Expand multi lingual editing support for content SF#156
  • Done
      
    Upgrade to eXist-db 2.2
  • Done
      
    Upgrade to Orbeon >=4.5 (related SF#99)

Datasets/Concepts

  • To Do
      
    Exceptions for all value domains
  • Won't fix
      
    Cancelled: Hierarchy in dataset concept lists SF#186
  • Coverage
    40% done
    Support for creating new dataset in ART (scratch/existing) SF#152
  • To Do
      
    Support binding a concept/valueDomain to an identification system (scratch/existing) SF#127
  • Done
      
    Implement state machine on datasets SF#191 (Related SF#180)

Templates

  • Done
      
    Organize template tree views by classification always SF#197
  • Done
      
    Add a button "set status to cancelled" in template view dialog for editors, similar to "set to status "active" SF#209
  • Done
      
    Use cache and then go to internet on template prototype selection situations SF#207
  • Done
      
    Allow association of template elements from BBR templates with own project concepts SF#208
  • Done
      
    In the id list form offer a link to the respective versions, in addition to the usual direct link to the object by id SF#236
  • Done
      
    Use id as a link instead of the name of the template in the uses / used by list SF#237

Testing

  • Coverage
    70% done
    Refactoring the XIS package SF#161 SF#139 SF#80; move to more general approach, support multiple languages
  • To Do
      
    Support new validation service. Is code X in valueset Y SF#132

Code system support

  • Coverage
    40% done
    Solution for code system authoring, release management SF#177

Building Block Repositories (BBR)

  • Coverage
    10% done
    BBR Clearing House, a governance policy what artefacts may be propagated to a repository (quality criteria, prices, etc.)
  • Coverage
    10% done
    Make IHE profile templates (e.g. PCC, XD*Lab) available
  • Coverage
    90% done
    Make CCDA Release 2 templates available
  • To Do
      
    Make list and DECOR representation of IHE profile templates available

Scenarios

  • To Do
      
    Editor: locking (SF#196), flow, layout
  • To Do
      
    Implement creating and maintaining Transaction “Defaults” (typical scenarios) SF#8 SF#12 SF#119 SF#17
  • Coverage
    10% done
    Support restricting valuesets/conceptList in a scenario SF#107

Value Set

  • Coverage
    50% done
    Create concept lists from value sets and propose value sets from concept lists SF#190
  • Done
      
    In the id list form offer a link to the respective versions, in addition to the usual direct link to the object by id SF#236

Community

  • To Do
      
    Publication support for communities SF#134
  • To Do
      
    Add support for valueset annotation SF#135

Special features

  • To Do
      
    Support for FHIR resources and profiles SF#184
  • Coverage
    50% done
    Difference analysis of DECOR artefacts (per project)
  • To Do
      
    Logger for changes in datasets, valuesets, templates, with connection to ADANS for change notifications
  • Coverage
    80% done
    Support for v2.xml SF#185 SF#174
  • To Do
      
    Support for HL7 V3 data types R2 SF#140
  • To Do
      
    Support for partial publications (filtering) SF#189
  • To Do
      
    Implement user settings that remember UI status SF#104
  • To Do
      
    Update/change rich text editor feature set SF#188 SF#50
  • To Do
      
    Refactor OID Viewer SF#193
  • To Do
      
    Refactor OID Manager SF#194
  • To Do
      
    Refactor OID Requests SF#195
  • To Do
      
    Add a formal approval mechanism for transactions, and possibly dataset subtrees SF#201

Role Based Access to DECOR

  • Coverage
    40% done
    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:
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.0 (2014)

Building Block Repositories (BBR)

  • Done
      
    Repository capabilities for commonly used value sets and templates as well as data set elements
  • Done
      
    CDA R2 prototype BBR containing all model derived templates of the original CDA standard Release 2 with document/header/section/entry level templates and value sets (ad1bbr-)
  • Done
      
    Caching of external BBRs for performance improvements
  • Done
      
    Building Blocks Repository (BBR) @ art-decor.org
  • Done
      
    Make CCDA Release 1.1 templates available

System Services

  • Done
      
    ADANS ART-DECOR Automatic notifier system
  • Done
      
    ADRAM ART-DECOR Release and Archive Manager
  • Done
      
    ADRESH ART-DECOR Refresh Service for sanbox projects and BBR caching

Issues

  • Done
      
    Restructuring of Viewer, multiple sort and filter options
  • Done
      
    Creation of issues fully functional (add author correctly, add issue to end of list, appropriate users are able to add new issues)
  • Done
      
    Possibility to directly assign an issue to a person when creating an issue
  • Done
      
    Subscribe/Unsubscribe (automatic and manually) to issues
  • Done
      
    Email notification (through ADANS)

Value Set

  • Done
      
    Editor basics as grid input of a value set, also for corrections

Special features

  • Done
      
    My Community DECOR
  • Coverage
    80% done
    Support of v2.xml and v2 data types

Templates

  • Done
      
    Implement Template Editor
  • Done
      
    Offer MIF derived template templates as a starting point for new templates (CDA)
  • Done
      
    Implement creating and maintaining Template Associations
  • Done
      
    Qualification of artefact relationships

Terminologies

  • Done
      
    Implementation of external value set refs
  • Done
      
    Implement creating and maintaining Terminology Associations
  • Done
      
    Improve Value set editor

Scenarios

  • Done
      
    Redesign of Editor

Identifications

  • Done
      
    List of Codesystem ids
  • Done
      
    List of Value Set ids
  • Done
      
    List of Template ids
  • Done
      
    OID register, re-sync with published ISO 13582

Concepts

  • Done
      
    Concept list @refs to be implemented
  • Done
      
    One XML Database Collection structure per project

Application generation

  • Done
      
    First implementation of application generation based on ART-DECOR artefacts

Testing

ART-DECOR Release 0.9 (2013)

Data Set

  • Done
      
    Viewer and Editor final and fully functional

Scenario

  • Done
      
    Viewer and Editor final and fully functional

Value Set

  • Done
      
    Viewer final and fully functional
  • Done
      
    Advanced/intelligent input of a value set with search and link to well-known terminology (code systems)

Templates

  • Done
      
    Viewer
  • Done
      
    Editor

Documentation