Updated March 01, 2018
We will create quarterly minor releases on the following schedule:
- EtherCIS v1.2: June 1st, 2018
- EtherCIS v1.3: Q3 2018
- EtherCIS v1.4: Q4 2018
- EtherCIS v1.5: Q1 2019
As a rule of thumb, we introduce CRs fixes (and PRs wherever applicable) into releases as well as new features and enhancements depending on various factors such as requirements from projects, users suggestions, things we want to do (because we think they are cool) etc.
In between, whenever needed, we will release patches to fix critical issues as required. Patches are not intended to introduce new features/enhancements. Nevertheless GitHub code base will be updated in between to allow intermediary cut to be produced locally.
The following are some kind of pre-announcements and should be considered as tentative schedule for the above releases.
- Changes in building EtherCIS and Continuous Integration (merge from Seref Arikan great contribution). This will also enable creating Docker images to easily deploy runtime environment.
- EtherCIS libraries in Maven Central
- HTTPS support
- Support of JWT and implementation of authorization (RBAC)
- Enhancing resultset export (refactoring): JSON, XML, CSV etc.
- AQL enhancements
- smart type cast
- array querying
NB. As of this version, the build tool will be Maven only. The reason is that we simply don't have the resources to deal with multiple build strategy.
Objective: integrate the required enhancements/functions for secure and measurable real-life deployment
- Structural Access Control Roles: definition, administration (HELM-ACT)
- DB based template caching and referential integrity (HELM-ACT)
- Operational Template Administration: maintenance, cache management (HELM-ACT)
- JWT administration (HELM-ACT)
- JMX administration (HELM-ACT)
- Cluster Configuration + administration
- Secure DB access (HELM-COM, HELM-ACT)
- EHR Erasure incl. audit log (HELM-PER)
- Contribution signing support (HELM-PER required for GDPR compliance)
- Finalize audit log (HELM-TRA)
- Consent Based access control (HELM-PER)
- openEHR REST API v1.0 conformance
- Demographic (RM) support in AQL with DB integration
- More AQL enhancements (nesting, stored queries, arithmetic, ADL matching)
- EXISTS operator
- Full text search on embedded jsonb fields (f.e. medical notes)
- Canonical JSON composition CRU + optimized persistence processing
Much to discuss still, what's come to mind are possibly:
- DB sharding
- Full text search (used for narratives in composition)
- openEHR DIRECTORY
- openEHR TASK
- Non committed composition (draft composition)
- TBD