Roadmap 20

ART-DECOR Release 2.0 (2016 to 2019)

Note that some features have been 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:

Table: Role Based Access setup for DECOR

	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