Skip to content

Releases: CDCgov/dibbs-ecr-viewer

8.0.0

27 Aug 14:20
78a3a29
Compare
Choose a tag to compare

Release Summary

This release introduces new condition search functionality in the library filters and updates the pregnancy information and display. It also includes several fixes to improve data accuracy including name normalization, corrected lab result abnormal tag handling, and smarter filter button behavior.

🚧 Required Infrastructure Changes 🚧

This release requires no new infrastructure changes.

📊 Automated Database Migrations 📊

This release includes an update to the ecr_data in SQL Server to improve support for Unicode characters. Users will be required to call the migrate-db API endpoint.

What's Changed

🏕 Features

Full Changelog: 7.2.0...8.0.0

7.2.0

13 Aug 13:29
ec5c7a2
Compare
Choose a tag to compare

Release Summary

This release implements audit logging for viewing eCRs, and adds UI improvements to several parts of the app, including the filters, admin pages, banners, & pop-up modals. This release also expands travel history section and add exposure contacts information to the Viewer.

🚧 Required Infrastructure Changes 🚧

This release requires no new infrastructure changes.

📊 Automated Database Migrations 📊

This release includes no new database migrations.

What's Changed

🏕 Features

Full Changelog: 7.1.0...7.2.0

7.1.0

30 Jul 16:43
092aca1
Compare
Choose a tag to compare

Release Summary

This release implements audit logging for:

  • user sign-in and sign-out
  • eCR creation
  • eCR search
  • Program area creation, update, and deletion

In addition several UI improvements have been made to program management. On the eCR side, UI improvements have been made to the condition summary and lab result accordions.

🚧 Required Infrastructure Changes 🚧

This release requires no new infrastructure changes.

📊 Automated Database Migrations 📊

This release includes no new database migrations.

What's Changed

🏕 Notable Features

Full Changelog: 7.0.0...7.1.0

7.0.0

17 Jul 19:18
f516751
Compare
Choose a tag to compare

What's Changed

This release removes an unused container (validation) which requires an infrastructure change. These changes will be incorporated into the various AWS, Azure, and GCP releases we support.

This release also adds an auditing system to the eCR viewer which logs user actions to the database.

Release Summary

This release contains many visual updates to the Viewer to bring it in line with general DIBBs styling.

Admins can now filter users by Program Area.

Active Problem Status has been added to the viewer as well as additional social history fields.

Audit logging infrastructure and logs for creating and updating users

🚧 Required Infrastructure Changes 🚧

This is a breaking change for AWS users as we will no longer be deploying the Validation container. Please reference our AWS terraform for updates.

This will also be breaking if VM users attempt manual upgrades. Please upgrade using the Upgrade Wizard to avoid this.

📊 Automated Database Migrations 📊

Migrations must be run for this release to create the necessary database resources for auditing.

🏕️ Features

Full Changelog: 6.0.0...7.0.0

6.0.0

25 Jun 19:36
486a61c
Compare
Choose a tag to compare

What's Changed

THIS IS A BREAKING RELEASE for users using the NON_INTEGRATED or DUAL configurations. Please read more below before installing.

Release Summary

This release introduces user and program management to the eCR Viewer for users using the NON_INTEGRATED or DUAL configurations. Program areas will be created with a selection of conditions, and standard users must be assigned to program areas in order to view eCRs with those conditions. Admins can manage program areas and users via the User management and Program management pages.

Please follow the Setup Guide for instructions on how to initialize an admin user and for more information on admin and standard user roles and permissions.

Along with these features we have included a time-based auto sign-out feature that will require users to log back in after periods of inactivity.

🚧 Required Infrastructure Changes 🚧

This release requires no new infrastructure changes.

📊 Automated Database Migrations 📊

This release includes an update to the ecr_labs and patient_address tables in the extended schema. Users using the extended schema will be required to call the migrate-db API endpoint.

Running migrations will also update the latest conditions reference data from the TES.

🏕 Features

Full Changelog: 5.0.0...6.0.0

5.0.0

04 Jun 18:20
e7a0954
Compare
Choose a tag to compare

Release Summary

THIS IS A BREAKING RELEASE for non-integrated and dual deployments! Please read more below before installing.

This release adds the public health emergency information to the eCR viewer and fixes a bug with the Provider Details section. Additionally, the condition code is now stored on the ecr_rr_conditions table, which requires a database migration. This will be leveraged in the future to enable condition-based authorization for eCR viewing.

🚧 Required Infrastructure Changes 🚧

No infrastructure changes are included in this release

📊 Automated Database Migrations 📊

This release includes an update to the ecr_rr_conditions table and will require calling the migrate-db API endpoint.

What's Changed

🏕 Notable Updates

🤐 Secret Future Features

New Contributors

Full Changelog: 4.0.0...5.0.0

4.0.0

21 May 18:28
8d93745
Compare
Choose a tag to compare

What's Changed

THIS IS A BREAKING RELEASE! Please read more below before installing.

Release Summary

This release adds authentication to /api routes. When calling the API to process eCRs, all users will need to pass a bearer token from either Rhapsody or their IDP to access the routes. In this release, it's still possible to save data without authentication directly to the orchestration container, but this will be removed in an upcoming release. Please see the guide, API documentation, and Rhapsody examples for more details about how to use this new release.

This release also adds a new /api/process-ecr route to the eCR Viewer container, which replaces the now deprecated /api/process-zip endpoint. The old process-zip endpoint will also be removed in a coming release. The guide and API documentation have been updated with how to use this new endpoint.

🚧 Required Infrastructure Changes 🚧

There is one environment variable changes associated with the automated migrations. This change is only required for users running the NBS-integrated Viewer.

NBS_API_PUB_KEY: Similar to NBS_PUB_KEY but used for authenticating the /api routes.

📊 Automated Database Migrations 📊

This release includes no new database migrations.

🏕 Features

🤐 Secret Future Features

These features are not available to end users yet, but they will be soon!

Full Changelog: 3.4.0...4.0.0

3.4.0

07 May 16:50
282e966
Compare
Choose a tag to compare

Release Summary

This release adds support for automated database migrations for the non-integrated version of the Viewer. More information about these automated migrations is below.

This release also adds a sign-out button to the application, and added new docs to reference. It also adds basic user management tables to the application, which will be used in user permissions later.

🚧 Required Infrastructure Changes 🚧

There are two environment variable changes associated with the automated migrations. These changes are only required for users running the non-integrated Viewer.

METADATA_DATABASE_SCHEMA: Optional. Possible values are "core" and "extended". Database schema to use for metadata storage. Core has a small subset of Extended. Default value is "extended".
METADATA_DATABASE_MIGRATION_SECRET : Secret needed to apply migrations via the /migrate-db api route. If not set, a random UUID will be assigned by the application and logged to the server.

📊 Automated Database Migrations 📊

This release adds support for Kysely automated database migrations. These add two quality-of-life improvements for implementers of the Viewer:

  1. If the eCR Viewer database isn't up to date with the latest migrations, the application will show an error message
    i. This means you can't get into a state where the data schema version doesn't match the application version.
  2. Instead of running the SQL scripts manually, you'll call a new API endpoint that runs the migrations for you. See API documentation here.

What's Changed

🏕 Features

Full Changelog: v3.2.0...3.4.0

v3.3.1

30 Apr 20:39
ade1d5c
Compare
Choose a tag to compare
v3.3.1 Pre-release
Pre-release

Release Summary

This release adds support for automated database migrations for the non-integrated version of the Viewer. More information about these automated migrations is below.

This release also adds a sign-out button to the application, and added new docs to reference.

🚧 Required Infrastructure Changes 🚧

There are two environment variable changes associated with the automated migrations. These changes are only required for users running the non-integrated Viewer.

METADATA_DATABASE_SCHEMA: Optional. Possible values are "core" and "extended". Database schema to use for metadata storage. Core has a small subset of Extended. Default value is "extended".
METADATA_DATABASE_MIGRATION_SECRET : Secret needed to apply migrations via the /migrate-db api route. If not set, a random UUID will be assigned by the application and logged to the server.

📊 Automated Database Migrations 📊

This release adds support for Kysely automated database migrations. These add two quality-of-life improvements for implementers of the Viewer:

  1. If the eCR Viewer database isn't up to date with the latest migrations, the application will show an error message
    i. This means you can't get into a state where the data schema version doesn't match the application version.
  2. Instead of running the SQL scripts manually, you'll call a new API endpoint that runs the migrations for you. See API documentation here.

🏕 Features

Full Changelog: v3.2.0...v3.3.1

v3.3.0

30 Apr 18:15
4fa9795
Compare
Choose a tag to compare
v3.3.0 Pre-release
Pre-release

Release Summary

This release adds support for automated database migrations for the non-integrated version of the Viewer. More information about these automated migrations is below.

This release also adds a sign-out button to the application, and added new docs to reference.

🚧 Required Infrastructure Changes 🚧

There are two environment variable changes associated with the automated migrations. These changes are only required for users running the non-integrated Viewer.

METADATA_DATABASE_SCHEMA: Optional. Possible values are "core" and "extended". Database schema to use for metadata storage. Core has a small subset of Extended. Default value is "extended".
METADATA_DATABASE_MIGRATION_SECRET : Secret needed to apply migrations via the /migrate-db api route. If not set, a random UUID will be assigned by the application and logged to the server.

📊 Automated Database Migrations 📊

This release adds support for Kysely automated database migrations. These add two quality-of-life improvements for implementers of the Viewer:

  1. If the eCR Viewer database isn't up to date with the latest migrations, the application will show an error message
    i. This means you can't get into a state where the data schema version doesn't match the application version.
  2. Instead of running the SQL scripts manually, you'll call a new API endpoint that runs the migrations for you. See API documentation here.

🏕 Features

Full Changelog: v3.2.0...v3.3.0