Skip to main content

Release Notes

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

To ensure the best performance and security, we recommend using the latest version of our software. Here is an overview of the support status and the compatibility with the different EWA versions. When we have a planned upcomming Analytics release we will put it in the overview with an estimated release week, and information about the new content will be described in the overview for that version number. Note that this is our current best guess for the time of release, and deviations may occur

Supported versions (containers based and SaaS)​

This is applicable for customers using either the SaaS solution or customers running local docker containers

Version NumberRelease DateRelease NotesSupport StatusEnd of Support DateCompatible EWA versionStatus
v2.2.xEstimated: Week 50 2025v2.2.0 Release Notes--> EWA v32.0.0Beta
v2.1.02025.09.24v2.1.0 Release NotesSupported-> EWA v32.0.0Stable
v2.0.12025.09.04v2.0.1 Release NotesSupported-> EWA v32.0.0Stable
v2.0.02025.06.26v2.0.0 Release NotesSupported-> EWA v32.0.0Stable
v1.7.32025.09.09v1.7.3 Release NotesSupported-> EWA v32.0.0Stable

Supported versions (non containers based)​

This is applicable for customers running local windows installations

Version NumberRelease DateRelease NotesSupport StatusEnd of Support DateCompatible EWA versionStatus
v2.2.0Estimated: Week 50 2025v2.2.0 Release Notes--> EWA v32.0.0Beta
v2.1.02025.10.28v2.1.0 Release NotesSupported-> EWA v32.0.0Stable
v2.0.12025.09.04v2.0.1 Release NotesSupported-> EWA v32.0.0Beta
v2.0.02025.06.26v2.0.0 Release NotesSupported-> EWA v32.0.0Beta
v1.7.32025.09.09v1.7.3 Release NotesSupported-> EWA v32.0.0Stable
v1.7.22025.02.17v1.7.2 Release NotesSupported-> EWA v32.0.0Stable

v2.2.0​

Features

  • Reason for mission beeing deleted
  • Form ID to be able to connect copied Forms together

v2.1.0​

Features

  • Added table ewa_core.dim_patients
  • Added more columns in table ewa_core.bridge_locations

Security improvements:

  • Uses ODBC Driver 18 for SQL Server
  • Force encrypted db connection
  • Security patches

v2.0.1​

Seacurity improvements:

  • Upgrading to Python 3.12 and sqlite3 to v3.50.4. Both Python and sqlite3 version can be checked in the log file.
  • Improved handling of secrets (see installation guide)

v2.0.0​

Updates to table names: All tables connected to a records starts with ewa_clean.records_

  • ewa_clean.records_billable_information
  • ewa_clean.records_contagion
  • ewa_clean.records_drugs
  • ewa_clean.records_gcs
  • ewa_clean.records_infusions
  • ewa_clean.records_interventions
  • ewa_clean.records_locations
  • ewa_clean.records_miscellaneous_information
  • ewa_clean.records_miscellaneous_medical
  • ewa_clean.records_missions
  • ewa_clean.records_news2
  • ewa_clean.records_oxygen
  • ewa_clean.records_retts
  • ewa_clean.records_sats
  • ewa_clean.records_sepsis
  • ewa_clean.records_time
  • ewa_clean.records_patients
  • ewa_clean.records_personnel
  • ewa_clean.records_urgency_levels

Updates to column names to make it easier to understand:

  • ewa_clean.records_locations.id -> ewa_clean.records_locations.location_id
  • ewa_clean.records_locations.municipality_or_country -> ewa_clean.records_locations.municipality
  • ewa_clean.records_patients.id -> ewa_clean.records_patients.patients_id

Features:

  • Added core layer. Note: This is an early stage, and tables and columns might have bigger changes in later releases without keeping track of the versions

  • Added serve layer. Note: This is an early stage, and tables and columns might have bigger changes in later releases without keeping track of the versions

  • Added the column predecessor to ewa_clean__configurable_mission_types, which is the id of the predecessor mission types (in the context of time of creation).

  • Added new table ewa_clean.history_of_presenting_complaint_legacycontaining the old History of Illness entries for backward compatibility reasons. The new History of Presenting Complaint data is already available in the forms tables.

  • Added table ewa_clean.unknown_patient_id_types, containing labels for identification types of otherwise unknown patients found in ewa_clean.records_patients.unknown_patient_identification_type.

  • Added column unknown_patient_identification_type_name with the type value from ewa_clean.unknown_patient_id_types in table ewa_clean.records_patients.

  • If you have installed and tested AnalyticsDataProcession the configuration for BLIKSUND_TRANSFORM_FULL_ON_START should be set to True. Then the tables will be deleted, and new ones are created.

  • Because of these name changes, outdated tables that are no longer used can accumulate, creating clutter and making the database harder to navigate. Refer to the installation guide for a script that deletes these tables and keeps the database clean.

v1.7.3​

Seacurity improvements:

  • Upgrading sqlite3 to v3.50.4. Both Python and sqlite3 version can be checked in the log file.

v1.7.2​

Bug fixes:

  • Make sure that also records with column ewa_clean.records.emcc_mission_id equal to NULL are included
  • Update the column type for record_id to int in all tables
  • ewa_clean.form_configuration_elements.form_configuration_section_id holds the correct IDs

Removed columns:

  • Column ewa_clean.pr_medical_record_crews.name, use ewa_clean.pr_users.full_name instead
  • Column ewa_clean.missions.emmc_mission_id, use ewa_clean.missions.emcc_mission_id instead

Note for installation:

  • If you have installed and tested AnalyticsDataProcession the configuration for BLIKSUND_TRANSFORM_FULL_ON_START and BLIKSUND_LOAD_FULL_ON_START should be set to True. Then the tables will be deleted, and new ones are loaded.

v1.7.0​

Features:

  • Added table ewa_clean.retts_priority_levels
  • Added table ewa_clean.sats_priority_levels

Bug fixes:

  • Disable trying to sending anonymous statistics
  • Deactivate load of measurements

Note for installation:

If you have installed and tested AnalyticsDataProcession the configuration for BLIKSUND_TRANSFORM_FULL_ON_START should be set to True. Then the tables will be deleted, and new ones are loaded.

v1.6.4​

Changes to clean layer:

  • All column types datetime2 are changed to datetimeoffset(7) to make sure that timezone information are included
  • Type for column ewa_clean.emcc_tickets.full_emcc_mission_id_updated_at is changed from varchar(max) to datetime2
  • Name for table ewa_clean.resources changed to ewa_clean.records_resources_stations to indicate that this is the resource and station information filled out in the record
  • Bug fix for missing data in ewa_clean.sats.gcs so that it now includes all data
  • Added table ewa_clean.resources, which includes all resources registered in the system
  • Added table ewa_clean.resource_type
  • Added column ewa_clean.locations.latitude
  • Added column ewa_clean.locations.longitude
  • Added column ewa_clean.news2.scoring_params_id
  • Added column ewa_clean.news2.scoring_params_item_id
  • Added column ewa_clean.news2.scoring_params_item_score
  • Added column ewa_clean.news2.scoring_params_item_text
  • Added column ewa_clean.news2.scoring_params_title
  • Added column ewa_clean.patients.unknown_patient_identification_number
  • Added column ewa_clean.patients.unknown_patient_identification_type
  • Added column ewa_clean.stations.deleted_at
  • Added column ewa_clean.organization.deleted_at
  • Added column ewa_clean.configurable_mission_types.deleted_at

Other changes:

  • Default value for BLIKSUND_LOAD_BATCH_SIZE is changed from 500 to 10000
  • Bug fix to make sure that many duplicates of measurements are not loaded

Note for installation:

  • If you have installed and tested AnalyticsDataProcession the configuration for BLIKSUND_TRANSFORM_FULL_ON_START and BLIKSUND_LOAD_FULL_ON_START should be set to True. Then the tables will be deleted, and new ones are loaded. Note that the load time might be longer than before due to the full load of all tables.
  • See Installation Guide for more information

v1.4.0​

Added to clean layer:

  • Table ewa_clean.measurements. This is a table that contains information about various measurement records taken from patients.
  • Table ewa_clean.measurement_types. This is a table (from a dbt seed) that contains the different types of measurements, and their id.
  • Column ewa_clean.sats.triage_tews_selected_params_id
  • Column ewa_clean.sats.triage_tews_selected_params_title
  • Column ewa_clean.sats.triage_tews_selected_params_item_id
  • Column ewa_clean.sats.triage_tews_selected_params_item_text
  • Column ewa_clean.sats.triage_tews_selected_params_item_score

Naming fixes applied:

  • Column ewa_clean.cardiac_arrest_forms.first_heart_rythm renamed to ewa_clean.cardiac_arrest_forms.first_heart_rhythm.
  • Column ewa_clean.cardiac_arrest_forms.prehospital_thrombolosis renamed to ewa_clean.cardiac_arrest_forms.prehospital_thrombolysis.

Note for installation:

  • If you have installed and tested AnalyticsDataProcession the configuration for BLIKSUND_TRANSFORM_FULL_ON_START should be set to True. Then the tables will be deleted, and new ones are loaded.
  • See Installation Guide for more information
  • Be aware that measurements are now added to the export. This table may consist of many rows, which can make the first run of this version slower.

v1.3.1​

Added to clean layer:

  • Table ewa_clean.emcc_tickets. This is a table containing ticket data related to EMCC missions, including mission IDs, urgency levels, and dispatch code information.
  • Table ewa_clean.records_emcc_tickets. This is the table that will bridge the EMCC tickets to their associated records.
  • Table ewa_clean.codes_status. This is a table (from a dbt seed) that contains the different statuses and their respective codes for a mission.
  • Table ewa_clean.checklist_configuration_items. Table for the configuration of checklists.
  • Table ewa_clean.checklist_response_items. Table for the responses to a checklist.
  • Column ewa_clean.missions.mission_resource_id
  • Column ewa_clean.missions.emcc_mission_id

Upcoming deprecations:

  • Column ewa_clean.pr_medical_record_crews.name will be deleted after 2025.02.01. Use ewa_clean.pr_users.full_name instead.
  • Column ewa_clean.missions.emmc_mission_id will be deleted after 2025.02.01. Use ewa_clean.missions.emcc_mission_id instead.

Fixes applied:

  • Column ewa_clean.missions.dispatch_code now contains the dispatch code.

Note for installation:

  • If you have installed and tested AnalyticsDataProcession the configuration for BLIKSUND_TRANSFORM_FULL_ON_START should be set to True. Then the tables will be deleted, and new ones are loaded.
  • See Installation Guide for more information

v1.2.0​

  • Table ewa_clean.cardiac_arrest_forms with information from cardiac arrest forms filled out is added to the Clean layer.
  • Table ewa_clean.urgency_levels is added to the the Clean layer.
  • Table ewa_clean.record_urgency_levels is added to the Clean layer. This is the table that will bridge the urgency levels to the records.
  • Column ewa_clean.pr_users.full_name is added to the Clean layer.
  • Column ewa_clean.pr_medical_record_crews.name will be deprecated after 2025.02.01. Use ewa_clean.pr_users.full_name instead.
  • Improve incremental load time for ewa_clean.drugs, ewa_clean.locations and ewa_clean.time.
  • Column type for ewa_clean.oxygen.quantity and ewa_clean.infusions.amount are changed from float to nvarchar(max).

Note for installation: If you have installed and tested AnalyticsDataProcession the configuration for BLIKSUND_TRANSFORM_FULL_ON_START should be set to True. Then the tables will be deleted, and new ones are loaded. See Installation Guide for more information.

v1.1.0​

  • Added organizations and stations to schema ewa_clean, in order to see which record that belongs to which organization/health trust See Table Description.
  • Removed some tables related to personnel registration and configurable mission type from stage in order to increase transformation time and reduce storage cost. No changes in ewa_clean for this tables.

Note for installation: If you have installed and tested AnalyticsDataProcession the configuration for BLIKSUND_TRANSFORM_FULL_ON_START should be set to True. Then the tables will be deleted, and new ones are loaded. See Installation Guide for more information.

v1.0.3​

Initial version. See Model Description and Table Description.

Note for installation: This service will replace FormModuleData. If you have installed and tested FormModuleData the configuration for BLIKSUND_TRANSFORM_FULL_ON_START should be set to True. Then the Forms tables will be deleted, and new ones are loaded. See Installation Guide for more information.