Skip to main content

Release Notes - Analytics API

Release notes for Analytics API. If you have any questions, please contact your support organization, and they will contact Bliksund.

To get the best performance and security, we recommend running the latest version. Planned releases are added to the table below with an estimated release date. This is our current best estimate, and the date may change.

To see which versions of EWA, Analytics Data Processing and Analytics API work together, see Version Compatibility. Changes to the documentation itself are listed in Documentation Notes.

Versions​

VersionRelease DateRelease NotesConfigurationEnd of Support DateComments
v1.4.132026.10.12v1.4.13 Release NotesConfiguration-Recommended version
v1.3.22026.06.18v1.3.2 Release Notes--Internal-only release
v1.1.02025.10.28v1.1.0 Release NotesWindows guide2026.12.31Known issue
v1.0.22025.09.12v1.0.2 Release NotesWindows guide2026.09.12No longer supported
v1.0.12025.07.02v1.0.1 Release Notes-2026.07.02No longer supported

v1.4.13​

Moves the Main Report to the Serve endpoint, with paging and a summary, adds a Lookups endpoint, and requires authentication on every endpoint.

Notes

  • The Main Report response now contains paging information and a list of items, instead of a plain list limited to 5000 rows. Integrations that read the Main Report must be updated.
  • All requests must include the API key, including GET requests and GraphQL introspection. Only /v1/ping, /v1/healthz and loading the GraphiQL page work without it. Clients that relied on this now get 401.
  • ewa_core.fact_records has no oxygen column since Analytics Data Processing v2.1.0. The skOxygen field on fact_records in /graphql is kept so existing queries still work, but it is deprecated and always empty.
  • Requesting two or more fields in one query is not supported. Such a query returns an error in the errors list, but the API keeps running and other requests are not affected. Request each field in a separate query.

Features

  • Field main_report added to /serve/graphql, used by the Main Report in EWA Insight: full filter set, page-number paging, and nested drugs, interventions and personnel data.
  • Field main_report_summary added, with aggregation panels for the Main Report.
  • New /lookups/graphql endpoint with the lookup lists used by the Main Report filters. The same lists are still available in /graphql.
  • Main Report CSV export reintroduced (GET /v1/reports/main-report/export).
  • See Configuration for the endpoints that are built for EWA Insight.

Bug fixes

  • /v1/healthz and fact_records in /graphql no longer fail with Invalid column name 'sk_oxygen'.
  • Log messages from all parts of the API are written to the console and the log files. Earlier, many of them were lost.

Security patches

  • Authentication is required on all endpoints, see Notes.

Other changes

  • Logging uses the same LOG__* settings as Analytics Data Processing v2.6.0, including LOG__CONSOLE__FORMAT for JSON output. See Configuration.
  • The version is written to the log when the service starts, and returned by GET /.

v1.3.2​

Adds the Serve endpoint (experimental). Internal-only release.

Notes

  • This release was only used for internal testing, and was never published.

Features

  • New Serve layer endpoint (experimental).
  • The NOT_CONTAINS filter operator is available for all filterable fields.

Bug fixes

  • Fixed errors on concurrent requests to the Clean and Core endpoints.

Security patches

  • Security patches for package vulnerabilities.

Other changes

  • Improved logging.

v1.1.0​

Makes all Clean and Core tables available through the API.

Features

  • All tables in schema ewa_clean are available in the API. See Clean Table Descriptions.
  • All tables in schema ewa_core are available in the API. See Core Table Descriptions. The Core layer is an early version, and larger changes can happen in later releases.

Security patches

  • Uses ODBC Driver 18 for SQL Server.
  • Database connections are always encrypted.
  • Security patches.

Known issues

  • Several requests at the same time to the Clean and Core endpoints can fail. Fixed in v1.3.2.
  • Database passwords containing special characters such as @, #, :, / or ? are not escaped, so the API cannot connect to the database.
  • With Analytics Data Processing v2.1.0 or later, /v1/healthz always reports the API as unhealthy, and fact_records in /graphql fails with Invalid column name 'sk_oxygen'. The other endpoints work. Fixed in v1.4.13.

v1.0.2​

A security and stability release.

Bug fixes

  • Fixed issues when starting the API.

Security patches

  • Upgraded to Python 3.13 to fix a sqlite3 vulnerability.

Other changes

  • Improved logging to file for on-premises installations.

v1.0.1​

The first version, with the endpoints used by the Main Report.

Notes

  • Analytics Data Processing must be installed for the API to work. The API must be installed and running for the Main Report in Insight to work.