Roadmap

Revision as of 09:12, 11 January 2018 by Kheitmann (talk | contribs)

ART-DECOR Release 2.2 (2018+)

(planned, stay tuned)

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.

  • Coverage
    95% done
    Refactor menu / front end structure SF#178 SF#144
  • Coverage
    90% done
    Document/provide UI guidance for HL7 package creation SF#179
  • Done
      
    According to the ART-DECOR color scheme the "show diagram" buttons all must be green instead of orange (they don't change anything) SF#274

Datasets/Concepts

  • 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
  • To Do
      
    Exceptions for all value domains

Templates/Rules

  • Coverage
    80% done
    Support for FHIR resources and profiles SF#184
  • Coverage
    80% done
    Add support for FHIR profiles to act as like other artefacts regarding Building Block Repositories
  • Done
      
    Support filter on template search by category SF#265
  • Done
      
    Render Vocab Binding differently from individual attribute list in template table view SF#283
  • Coverage
    10% done
    Add diagnostics to schematron engine to support assert/report types/categories of errors/warnings SF#284
  • Done
      
    Allow vocabulary binding strengths for coded template elements according to FHIR: required, e extensible, preferred, example SF#314

Value Set

  • Done
      
    Create concept lists from value sets and propose value sets from concept lists SF#190
  • Coverage
    95% done
    Add "automatic" copyright addition to all value set calls on terminologies that require a license for use
  • Done
      
    Multi-lingual IHE SVS Format Export SF#301
  • Done
      
    Allow vocabulary binding strengths for coded template elements according to FHIR: required, e extensible, preferred, example SF#314

Code system support

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

Building Block Repositories (BBR)

  • Done
      
    Make IHE profile templates (e.g. PCC, XD*Lab) available (now published on IHE Europe ART-DECOR Server)
  • Done
      
    Make list and DECOR representation of IHE profiles templates available (now published on IHE Europe ART-DECOR Server)

Scenarios

  • 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
  • Done
      
    Button to directly invoke the spreadsheet view via RetrievTransaction for datasets and scenarios SF#275

Testing

  • Coverage
    90% done
    Live Runtime Compile LRC Validation
  • Coverage
    60% done
    Instance Fragment Validation IVF
  • Coverage
    70% done
    Refactoring the XIS package SF#161 SF#139 SF#80; move to more general approach, support multiple languages
  • Coverage
    70% done
    Support new validation service. Is code X in valueset Y SF#132
  • Done
      
    Representing Template example generator (whole CDA documents, V3 messages etc.) based on the template editor example fragment generator, along with meta data input such as dates, OIDs etc

Community

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

Project Management

  • Done
      
    Add type of participant to copyright line, defaulting to "author" and allowing additional types "contributor" and "reviewer" to be selected and displayed SF#277

Special features

  • Coverage
    90% done
    Difference analysis of DECOR artefacts (per project, on demand)
  • Coverage
    90% done
    Introduce 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
      
    Logger for changes in datasets, value sets, 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
  • Coverage
    95% done
    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
  • To Do
      
    Add support for subscription on publication sites (ADRAM served)SF#302

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

  • Won't fix
      
    Cancelled: Hierarchy in dataset concept lists SF#186
  • 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

Building Block Repositories (BBR)

  • Done
      
    Make CCDA Release 2 / 2.1 templates available

Value Set

  • 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

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
  • Done
      
    Editor: locking (SF#196), flow, layout

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

  • Done
      
    introduction standards/methodology DECOR (ART_Introduction)
  • To Do
      
    scope/objective/rationale
  • Done
      
    projects (ART_Project_Editor)
  • Done
      
    datasets (ART_Dataset_Viewer and ART_Dataset_Editor)
  • To Do
      
    scenarios (ART_Scenario_Viewer and ART_Scenario_Editor) SF#2
  • Done
      
    value sets (ART_Value_Set_Viewer and ART_Value_Set_Editor)
  • To Do
      
    Solution/documentation of Value sets with or without nullFlavors
  • Done
      
    terminology associations (ART_Terminology_Association_Viewer and ART_Terminology_Association_Editor)
  • Done
      
    templates (ART_Template_Viewer and ART_Template_Editor)
  • Done
      
    issues (ART_Issues)
  • To Do
      
    technical publications for vendors / interface specialists (HTML)
  • To Do
      
    requirements analysis for technical publications for vendors / interface specialists (generate PDF version for deliverables)
  • To Do
      
    implementations of technical publications for vendors / interface specialists (generate PDF version for deliverables)
  • To Do
      
    end user guide ART: part "test tools"
  • To Do
      
    end user guide ART: valuesets
  • To Do
      
    mycommunity introduction
  • To Do
      
    end user guide ART: mycommunity usage
  • To Do
      
    end user guide ART: the rest
  • To Do
      
    Document CLaML schema as used by ART-DECOR SF#192
  • Won't fix
      
    BBR Clearing House, a governance policy what artefacts may be propagated to a repository (quality criteria, prices, etc.) - is a question of the policy of the underlying governance group