Difference between revisions of "Roadmap"
| Line 4: | Line 4: | ||
<div style="text-align: right"><i>– Happily, your ART-DECOR Expert Team and ART-DECOR Open Tools</i></div> | <div style="text-align: right"><i>– Happily, your ART-DECOR Expert Team and ART-DECOR Open Tools</i></div> | ||
| − | |||
=Current Roadmaps= | =Current Roadmaps= | ||
Revision as of 16:34, 2 March 2020
ART-DECOR Releases 2.x and Future Releases on 3.x
We have made many update since 2018 (see Releases) but did not continue to tell you about our plans for the next time and near future (aka roadmap). We will update our roadmap very soon for Release 2.x and also for 3.0 (to appear in 2021 with lots of new features). Thanks to all our customers for their patience, you will be surprised...
– Happily, your ART-DECOR Expert Team and ART-DECOR Open Tools
Current Roadmaps
-
ART-DECOR® Release 3.0 Apr 2021Major Topics: Moving towards microservices, Finalization of the UI / UX migration, Better Scalability, Higher reliability of services, New architecture of the Centralized ART-DECOR Terminology Services (CADTS), More FHIR Support (Profiling)
Detail here -
ART-DECOR® Release 2.6 Aug 2020Major Topics: New architecture of the Centralized ART-DECOR Terminology Services (CADTS), New UX/UI
Detail here -
ART-DECOR® Release 2.2 May 2020Major Topics: Datasets/Concepts, Templates/Rules, Value Set, Scenarios, FHIR Support, Testing, External Services Support, Role Based Access to DECOR
Detail here
Older Roadmaps
Click on "Expand" to see details of the respective roadmap.
ART-DECOR® Release 2.0
ART-DECOR Release 2.0 (2016 to 2019)
Note that some features have been postponed after prioritizing.
- Coverage95% doneRefactor menu / front end structure SF#178 SF#144
- Coverage90% doneDocument/provide UI guidance for HL7 package creation SF#179
- DoneAccording 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
- Coverage40% doneSupport for creating new dataset in ART (scratch/existing) SF#152
- To DoSupport binding a concept/valueDomain to an identification system (scratch/existing) SF#127
- To DoExceptions for all value domains
Templates/Rules
- Coverage80% doneSupport for FHIR resources and profiles SF#184
- Coverage80% doneAdd support for FHIR profiles to act as like other artefacts regarding Building Block Repositories
- DoneSupport filter on template search by category SF#265
- DoneRender Vocab Binding differently from individual attribute list in template table view SF#283
- Coverage10% doneAdd diagnostics to schematron engine to support assert/report types/categories of errors/warnings SF#284
- DoneAllow vocabulary binding strengths for coded template elements according to FHIR: required, e extensible, preferred, example SF#314
Value Set
- DoneCreate concept lists from value sets and propose value sets from concept lists SF#190
- Coverage95% doneAdd "automatic" copyright addition to all value set calls on terminologies that require a license for use
- DoneMulti-lingual IHE SVS Format Export SF#301
- DoneAllow vocabulary binding strengths for coded template elements according to FHIR: required, e extensible, preferred, example SF#314
Code system support
- Coverage40% doneSolution for code system authoring, release management SF#177
Building Block Repositories (BBR)
- DoneMake IHE profile templates (e.g. PCC, XD*Lab) available (now published on IHE Europe ART-DECOR Server)
- DoneMake list and DECOR representation of IHE profiles templates available (now published on IHE Europe ART-DECOR Server)
Scenarios
- To DoImplement creating and maintaining Transaction “Defaults” (typical scenarios) SF#8 SF#12 SF#119 SF#17
- Coverage10% doneSupport restricting valuesets/conceptList in a scenario SF#107
- DoneButton to directly invoke the spreadsheet view via RetrievTransaction for datasets and scenarios SF#275
Testing
- Coverage90% doneLive Runtime Compile LRC Validation
- Coverage60% doneInstance Fragment Validation IVF
- Coverage70% doneRefactoring the XIS package SF#161 SF#139 SF#80; move to more general approach, support multiple languages
- Coverage70% doneSupport new validation service. Is code X in valueset Y SF#132
- DoneRepresenting 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
Project Management
- DoneAdd 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
- Coverage90% doneDifference analysis of DECOR artefacts (per project, on demand)
- Coverage90% doneIntroduce history storage of DECOR artefacts (template, value set, scenarios/transactions), re-write history mechanism for dataset concepts later to follow the same rules
- To DoLogger for changes in datasets, value sets, templates, with connection to ADANS for change notifications
- Coverage80% doneSupport for v2.xml SF#185 SF#174
- To DoSupport for HL7 V3 data types R2 SF#140
- Coverage95% doneSupport for partial publications (filtering) SF#189
- To DoImplement user settings that remember UI status SF#104
- To DoUpdate/change rich text editor feature set SF#188 SF#50
- To DoRefactor OID Viewer SF#193
- To DoRefactor OID Manager SF#194
- To DoRefactor OID Requests SF#195
- To DoAdd a formal approval mechanism for transactions, and possibly dataset subtrees SF#201
- To DoAdd support for subscription on publication sites (ADRAM served)SF#302
Role Based Access to DECOR
- Coverage40% doneImplement 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 |
ART-DECOR® Release 1.8
ART-DECOR Release 1.8 (February 2016)
- DoneIHE metadata DECOR data set for XDS SF#187
- DoneExpand multi lingual editing support for content SF#156
- DoneUpgrade to eXist-db 2.2
- DoneUpgrade to Orbeon >=4.5 (related SF#99)
Datasets/Concepts
- Won't fixCancelled: Hierarchy in dataset concept lists SF#186
- DoneImplement state machine on datasets SF#191 (Related SF#180)
Templates
- DoneOrganize template tree views by classification always SF#197
- DoneAdd a button "set status to cancelled" in template view dialog for editors, similar to "set to status "active" SF#209
- DoneUse cache and then go to internet on template prototype selection situations SF#207
- DoneAllow association of template elements from BBR templates with own project concepts SF#208
- DoneIn 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
- DoneUse id as a link instead of the name of the template in the uses / used by list SF#237
Building Block Repositories (BBR)
- DoneMake CCDA Release 2 / 2.1 templates available
Value Set
- DoneIn 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
ART-DECOR Release 1.0 (2014)
Building Block Repositories (BBR)
- DoneRepository capabilities for commonly used value sets and templates as well as data set elements
- DoneCDA 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-)
- DoneCaching of external BBRs for performance improvements
- DoneBuilding Blocks Repository (BBR) @ art-decor.org
- DoneMake CCDA Release 1.1 templates available
System Services
- DoneADANS ART-DECOR Automatic notifier system
- DoneADRAM ART-DECOR Release and Archive Manager
- DoneADRESH ART-DECOR Refresh Service for sanbox projects and BBR caching
Issues
- DoneRestructuring of Viewer, multiple sort and filter options
- DoneCreation of issues fully functional (add author correctly, add issue to end of list, appropriate users are able to add new issues)
- DonePossibility to directly assign an issue to a person when creating an issue
- DoneSubscribe/Unsubscribe (automatic and manually) to issues
- DoneEmail notification (through ADANS)
Value Set
- DoneEditor basics as grid input of a value set, also for corrections
Special features
- DoneMy Community DECOR
- Coverage80% doneSupport of v2.xml and v2 data types
Templates
- DoneImplement Template Editor
- DoneOffer MIF derived template templates as a starting point for new templates (CDA)
- DoneImplement creating and maintaining Template Associations
- DoneQualification of artefact relationships
Terminologies
- DoneImplementation of external value set refs
- DoneImplement creating and maintaining Terminology Associations
- DoneImprove Value set editor
Scenarios
- DoneRedesign of Editor
- DoneEditor: locking (SF#196), flow, layout
Identifications
- DoneList of Codesystem ids
- DoneList of Value Set ids
- DoneList of Template ids
- DoneOID register, re-sync with published ISO 13582
Concepts
- DoneConcept list @refs to be implemented
- DoneOne XML Database Collection structure per project
Application generation
- DoneFirst implementation of application generation based on ART-DECOR artefacts
Testing
ART-DECOR® Release 0.9
ART-DECOR Release 0.9 (2013)
Data Set
- DoneViewer and Editor final and fully functional
Scenario
- DoneViewer and Editor final and fully functional
Value Set
- DoneViewer final and fully functional
- DoneAdvanced/intelligent input of a value set with search and link to well-known terminology (code systems)
Templates
- DoneViewer
- DoneEditor
ART-DECOR® Documentation
Documentation
- Doneintroduction standards/methodology DECOR (ART_Introduction)
- To Doscope/objective/rationale
- Doneprojects (ART_Project_Editor)
- Donedatasets (ART_Dataset_Viewer and ART_Dataset_Editor)
- Donescenarios (ART_Scenario_Viewer and ART_Scenario_Editor) SF#2
- Donevalue sets (ART_Value_Set_Viewer and ART_Value_Set_Editor)
- To DoSolution/documentation of Value sets with or without nullFlavors
- Doneterminology associations (ART_Terminology_Association_Viewer and ART_Terminology_Association_Editor)
- Donetemplates (ART_Template_Viewer and ART_Template_Editor)
- Doneissues (ART_Issues)
- To Dotechnical publications for vendors / interface specialists (HTML)
- To Dorequirements analysis for technical publications for vendors / interface specialists (generate PDF version for deliverables)
- To Doimplementations of technical publications for vendors / interface specialists (generate PDF version for deliverables)
- To Doend user guide ART: part "test tools"
- To Doend user guide ART: valuesets
- To Domycommunity introduction
- To Doend user guide ART: mycommunity usage
- To Doend user guide ART: the rest
- To DoDocument CLaML schema as used by ART-DECOR SF#192
- Won't fixBBR 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