We are excited to announce the release of ABAC Server 2.0, which brings significant advancements in flexibility and decision-making capabilities. We also have several additional updates across the platform, as many of the components received improvements and fixes across the board, so keep reading to learn about everything new.
New ABAC Server 2.0
The release of ABAC Server 2.0 introduces scriptable data ingress, replacing the current plugin infrastructure and leveraging the Data Streamto detect and react to changes. The new ABAC Server also supportssynchronous script execution from ABAC policies. Additionally, policies can now invoke one another as subroutines, making them more structured and maintainable.
These enhancements allow for complex computations and external system interactions within policy evaluations. Please refer to product documentation, which now also includes information on the ABAC Server’s REST API.
What else is new?
- EHR Server now has support for simplified data formats (FLAT and STRUCTURED) on the standardised openEHR API. It heavily utilises cachingwhen form resources are served. On the administrative API, reindexing of only a particular EHR or a set of compositions can be triggered to make it easier to diagnose stale index problems.
- The Demographics server has seen performance improvements in various important cases, such as manipulating resources with a significant number of references, like Groups, among various bug fixes.
- The Validator server can now store metadata about the validation scripts to allow for easier manageability.
- The Dashboard server no longer periodically polls the Auditor to refresh the data but rather listens to the Data Stream to invalidate data from the auditing. This reduces both the latency between new data arriving and that being reflected on the dashboards and also the system load because the data is refreshed much less often.
- The terminology adapter now supports disjunctive queries (“OR” operation) between terms.
Looking ahead
While Distributed Authentication 2.0.0 was released with a new claim mapping structure, we are holding off on major announcements, as version 3.0.0 is on the horizon with even more transformative changes. We are also looking forward to support for streaming the query results in the Demographics Server, just like the EHR Server has been able to do for a long time now.
Please refer to the Release notes of each component (linked above) for more details on the issues fixed and features added. For all platform components, the minimum required Java version is now 17.
Stay tuned for future updates, and feel free to contact us if you have any questions – we are here to help!
