Difference between revisions of "Roadmap"
(mycommunity) |
(edited layout) |
||
Line 1: | Line 1: | ||
=2013= | =2013= | ||
==Data Set== | ==Data Set== | ||
− | * | + | * {{TAGDONE}} Viewer and Editor final and fully functional |
− | + | ||
==Scenario== | ==Scenario== | ||
− | * | + | * {{TAGDONE}} Viewer and Editor final and fully functional |
− | |||
− | |||
− | |||
− | |||
==Value Set== | ==Value Set== | ||
− | * | + | * {{TAGDONE}} Viewer final and fully functional |
− | * | + | * {{TAGTODO}} Editor basics as grid input of a value set, also for corrections |
− | * | + | * {{TAGDONE}} Advanced/intelligent input of a value set with search and link to well-known terminology (code systems) |
− | * | + | * {{TAGTODO}} Create conceptlist concept association |
==Templates== | ==Templates== | ||
− | * | + | * {{TAGDONE}} Viewer |
− | * | + | * {{TAGTODO}} Editor |
− | * | + | * {{TAGDONE}} List of and concept for commonly used templates, like CDA document/header/section/entry level templates etc. See adbbr1. |
+ | =2014= | ||
==Issues== | ==Issues== | ||
− | * | + | * {{TAGDONE}} Restructuring of Viewer, multiple sort and filter options |
− | * | + | * {{TAGDONE}} Creation of issues fully functional (add author correctly, add issue to end of list, appropriate users are able to add new issues) |
− | * | + | * {{TAGTODO}} When creating issue, directly assign to person |
==Documentation== | ==Documentation== | ||
− | * | + | * {{TAGTODO}} introduction standards/methodology DECOR |
− | * | + | * {{TAGTODO}} scope/objective/rationale |
− | * | + | * {{TAGTODO}} projects |
− | * | + | * {{TAGTODO}} datasets |
− | * | + | * {{TAGTODO}} scenarios |
− | * | + | * {{TAGDONE}} value sets |
− | * | + | * {{TAGTODO}} Solution/documentation of Value sets with or without nullFlavors |
− | * | + | * {{TAGTODO}} terminology associations |
− | * | + | * {{TAGDONE}} templates |
− | * | + | * {{TAGTODO}} issues |
− | * | + | * {{TAGTODO}} technical publications for vendors / interface specialists (HTML) |
− | * | + | * {{TAGTODO}} requirements analysis for technical publications for vendors / interface specialists (generate PDF version for deliverables) |
− | * | + | * {{TAGTODO}} implementations of technical publications for vendors / interface specialists (generate PDF version for deliverables) |
− | * | + | * {{TAGTODO}} end user guide ART: part "test tools" |
− | * | + | * {{TAGTODO}} end user guide ART: valuesets |
− | * | + | * {{TAGTODO}} mycommunity introduction |
− | * | + | * {{TAGTODO}} end user guide ART: mycommunity usage |
− | * | + | * {{TAGTODO}} end user guide ART: the rest |
==Special features== | ==Special features== | ||
− | * | + | * {{TAGTODO}} Difference analysis of DECOR artefacts (per project) |
− | * | + | * {{TAGTODO}} Logger for changes in datasets, valuesets, templates |
− | * | + | * {{TAGDONE}} Building Blocks Repository (BBR) @ art-decor.org |
− | * | + | * {{TAGTODO}} BBR Clearing House |
− | * | + | * {{TAGTODO}} Make IHE templates (e.g. PCC) available |
− | * | + | * {{TAGTODO}} Make CCDA 1.1, 2 templates available |
− | * | + | * {{TAGTODO}} Make list and DECOR representation of IHE profile templates available |
− | |||
==New features== | ==New features== | ||
− | * | + | * {{TAGDONE}} My Community DECOR |
− | * | + | * {{TAGDONE}} Building Block Repositories (BBR), hierarchies, multiple BBRs |
==Templates== | ==Templates== | ||
− | * | + | * {{ProgressBar|90}} Implement Template Editor |
− | * | + | * {{TAGDONE}} Offer MIF derived template templates as a starting point for new templates (CDA) |
− | * | + | * {{TAGDONE}} Implement creating and maintaining Template Associations |
− | * | + | * {{TAGDONE}} Qualification of artefact relationships |
==Terminologies== | ==Terminologies== | ||
− | * | + | * {{TAGDONE}} Implementation of external value set refs |
− | * | + | * {{ProgressBar|50}} Implement creating and maintaining Terminology Associations |
− | * | + | * {{ProgressBar|80}} Improve Value set editor |
==Issues== | ==Issues== | ||
− | * | + | * {{ProgressBar|90}} Subscribe/Unsubscribe (automatic and manually) to issues |
− | * | + | * {{TAGDONE}} Email notification |
==Scenarios== | ==Scenarios== | ||
− | * | + | * {{TAGTODO}} Editor: flow, layout |
− | * | + | * {{TAGTODO}} Implement creating and maintaining Transaction “Defaults” (typical scenarios) |
==Identifications== | ==Identifications== | ||
− | * | + | * {{TAGTODO}} List of Codesystem ids |
− | * | + | * {{TAGTODO}} List of Value Set ids |
− | * | + | * {{TAGDONE}} List of Template ids |
− | * | + | * {{TAGDONE}} OID register, re-sync with published ISO 13582 |
==Concepts== | ==Concepts== | ||
− | * | + | * {{TAGTODO}} Exceptions for all value domains |
− | * | + | * {{TAGDONE}} Concept list @refs to be implemented |
− | * | + | * {{TAGDONE}} One XML Database Collection structure per project |
− | |||
− | |||
− | |||
==Role Based Access to DECOR== | ==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: | + | * {{TAGTODO}} 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: |
{| class="artdecor" border="1" width="100%" | {| class="artdecor" border="1" width="100%" | ||
|- | |- | ||
Line 137: | Line 130: | ||
|+ '''Table: Role Based Access setup for DECOR''' | |+ '''Table: Role Based Access setup for DECOR''' | ||
|} | |} | ||
− | * | + | ==Application generation== |
+ | |||
+ | =2014+= | ||
+ | * {{TAGTODO}} IHE metadata DECOR data set for XDS | ||
+ | * {{TAGTODO}} Hierarchy in conceptlists |
Revision as of 13:46, 7 November 2013
Contents
2013
Data Set
- Done
Scenario
- Done
Value Set
- Done
- To Do
- Done
- To Do
Templates
- Done
- To Do
- Done
2014
Issues
- Done
- Done
- To Do
Documentation
- To Do
- To Do
- To Do
- To Do
- To Do
- Done
- To Do
- To Do
- Done
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
- To Do
Special features
- To Do
- To Do
- Done
- To Do
- To Do
- To Do
- To Do
New features
- Done
- Done
Templates
- Coverage90% doneImplement Template Editor
- Done
- Done
- Done
Terminologies
- Done
- Coverage50% doneImplement creating and maintaining Terminology Associations
- Coverage80% doneImprove Value set editor
Issues
- Coverage90% doneSubscribe/Unsubscribe (automatic and manually) to issues
- Done
Scenarios
- To Do
- To Do
Identifications
- To Do
- To Do
- Done
- Done
Concepts
- To Do
- Done
- Done
Role Based Access to DECOR
- To Do
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 |
Application generation
2014+
- To Do
- To Do