Difference between revisions of "Roadmap"
(→2012) |
|||
Line 81: | Line 81: | ||
*One XML Database Collection structure per project | *One XML Database Collection structure per project | ||
==Documentation== | ==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: | ||
+ | {| 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''' | ||
+ | |} |
Revision as of 13:35, 6 November 2013
2012
Data Set
- Viewer and Editor final and fully functional
Scenario
- Viewer and Editor final and fully functional
Scenario Test Set
- Viewer and Editor final and fully functional
Value Set
- Viewer final and fully functional
- Editor basics as grid input of a value set, also for corrections
- Advanced/intelligent input of a value set with search and link to well-known terminology (code systems)
Templates
- Viewer
- Editor
- List of and concept for commonly used templates, like CDA document/header/section/entry level templates etc.
Issues
- Restructuring of Viewer, multiple sort and filter options
- Creation of issues fully functional (add author correctly, add issue to end of list, appropriate users are able to add new issues)
Documentation
- introduction standards/methodology DECOR
- scope/objective/rationale
- projects
- datasets
- scenarios
- value sets
- templates
- issues
- technical publications for vendors / interface specialists (HTML)
- requirements analysis for technical publications for vendors / interface specialists (generate PDF version for deliverables)
- implementations of technical publications for vendors / interface specialists (generate PDF version for deliverables)
- end user guide ART: part "test tools"
- end user guide ART: the rest
Special features
- Difference analysis of DECOR artefacts (per project)
- Building Blocks Repository (BBR) @ art-decor.org and Clearing House
- Make IHE templates (e.g. PCC) available
- Make list and DECOR representation of IHE profile templates available
- IHE metadata DECOR data set for XDS
2013
Finalize/freeze DECOR 12 Format
New features
- My Community DECOR
- Building Block Repositories (BBR), hierarchies, multiple BBRs
Templates
- Implement Template Editor
- Offer MIF derived template templates as a starting point for new templates
- Implement creating and maintaining Template Associations
- Qualification of artefact relationships
- Ability to determine allowed nullFlavors for all types of value domains
- Solution/documentation of Value sets with or without nullFlavors
Terminologies
- Implementation of external value set refs
- Implement creating and maintaining Terminology Associations
- Improve Value set editor
- Code system editor for small code systems
Issues
- Subscribe/Unsubscribe (automatic and manually) to issues
- Email notification
Scenarios
- Editor: flow, layout
- Solution for ignore hierarchy of Concepts in Concept Groups (e.g. for queries)
- Implement creating and maintaining Transaction “Defaults” (typical scenarios)
Identifications
- List of Codesystem ids
- List of Value Set ids
- List of Template ids
- OID register, re-sync with published ISO 13582
Concepts
- Exceptions for all value domains
- Concept list @refs to be implemented
- Structure
- 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 |