Difference between revisions of "Roadmap"

(update)
(mycommunity)
Line 42: Line 42:
 
* [2014] end user guide ART: part "test tools"
 
* [2014] end user guide ART: part "test tools"
 
* [2014] end user guide ART: valuesets
 
* [2014] end user guide ART: valuesets
 +
* [2014] mycommunity introduction
 +
* [2014] end user guide ART: mycommunity usage
 
* [2014] end user guide ART: the rest
 
* [2014] end user guide ART: the rest
  

Revision as of 13:20, 7 November 2013

2013

Data Set

  • [DONE] Viewer and Editor final and fully functional

Scenario

  • [DONE] Viewer and Editor final and fully functional

Scenario Test Set

  • Viewer and Editor final and fully functional

[No longer applicable: see test-tools]

Value Set

  • [DONE] Viewer final and fully functional
  • [2013] Editor basics as grid input of a value set, also for corrections
  • [DONE] Advanced/intelligent input of a value set with search and link to well-known terminology (code systems)
  • [todo] Create conceptlist concept association

Templates

  • [DONE] Viewer
  • [2013] Editor
  • [DONE] List of and concept for commonly used templates, like CDA document/header/section/entry level templates etc. See adbbr1.

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)
  • [2014] When creating issue, directly assign to person

Documentation

  • [2014] introduction standards/methodology DECOR
  • [2014] scope/objective/rationale
  • [2014] projects
  • [2014] datasets
  • [2014] scenarios
  • [DONE] value sets
  • [2014] Solution/documentation of Value sets with or without nullFlavors
  • [2014] terminology associations
  • [DONE] templates
  • [2014] issues
  • [2014] technical publications for vendors / interface specialists (HTML)
  • [2014] requirements analysis for technical publications for vendors / interface specialists (generate PDF version for deliverables)
  • [2014] implementations of technical publications for vendors / interface specialists (generate PDF version for deliverables)
  • [2014] end user guide ART: part "test tools"
  • [2014] end user guide ART: valuesets
  • [2014] mycommunity introduction
  • [2014] end user guide ART: mycommunity usage
  • [2014] end user guide ART: the rest

Special features

  • [2014] Difference analysis of DECOR artefacts (per project)
  • [2014] Logger for changes in datasets, valuesets, templates
  • [DONE] Building Blocks Repository (BBR) @ art-decor.org
  • [2014] BBR Clearing House
  • [2014] Make IHE templates (e.g. PCC) available
  • [2014] Make CCDA 1.1, 2 templates available
  • [2014] Make list and DECOR representation of IHE profile templates available
  • [2014+] IHE metadata DECOR data set for XDS

New features

  • [DONE] My Community DECOR
  • [DONE] Building Block Repositories (BBR), hierarchies, multiple BBRs

Templates

  • [90% 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
  • [50% DONE] Implement creating and maintaining Terminology Associations
  • [80% DONE] Improve Value set editor

Issues

  • [90% DONE] Subscribe/Unsubscribe (automatic and manually) to issues
  • [DONE] Email notification

Scenarios

  • [2014] Editor: flow, layout
  • [2014] Implement creating and maintaining Transaction “Defaults” (typical scenarios)

Identifications

  • [2014] List of Codesystem ids
  • [2014] List of Value Set ids
  • [DONE] List of Template ids
  • [DONE] OID register, re-sync with published ISO 13582

Concepts

  • [2014] Exceptions for all value domains
  • [DONE] Concept list @refs to be implemented
  • [2014+] Hierarchy in conceptlists
  • [DONE] One XML Database Collection structure per project

Documentation

2014

Role Based Access to DECOR

  • 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. 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
  • application generation