This update brings an update to patient overview, system fixes and API changes.
Updated patient overview page
We updated the patient overview page layout to emphasize the room status and the current alerts. In subsequent updates, live view will be only available to system administrators.
Fixes & Improvements
- We significantly improved the Ouva backend related to the platform's scalability.
- We fixed an issue that improved responsiveness in the patient view.
- We fixed a bug that caused an incorrect device offline notification during an ongoing patient transfer.
- We resolved an issue where the loading indicator would prematurely disappear if the initial query failed.
- We fixed a bug caused by the URL character limit imposed by the database.
- We fixed a bug that allows sending resolution-related fields in a notification update endpoint invocation.
- We fixed a major bug related to integrations caused by our services not being able to access headers while consuming messages.
- We fixed a bug that prevented wander risk flag persistence via the API patient session endpoints.
- We updated sensor URL-related DTO validation for all API endpoints to allow longer URL strings.
- We removed unique name constraints for room and department records in the patient service since all third parties can now use reference key-based requests instead of previously used name-based requests.
- We implemented a new filter to log all incoming HTTP requests for services with RESTful APIs.
- We implemented a new endpoint to retrieve an active patient session, if it exists, by its related patient reference key.
- We implemented URL validation to ensure third-party clients do not send malformed URLs.
- We implemented OAuth2.0 token-based authentication in the API client's integration service to enable integrations with OAuth2.0-enabled third parties.
- We implemented custom token-based authentication in the integration client for clients that require it.
- We implemented a token refresh mechanism in the client integration service with an authentication timeout.
- We implemented a configurable patient session validation mechanism in the person-metadata adapter service for person-metadata messages sent from the ML side so that the service can differentiate between related/unrelated messages. This will allow us to deploy in a clustered mode for pilot setups (See pilot PoC deployment)
- We implemented a new endpoint to fetch all active patient sessions.
- We also improved existing patient session-related GET endpoints to include room and sensor data in them.
- We also improved existing room-related GET endpoints to include sensor data in them.
- We improved patient session-related endpoints to allow deleted (soft delete) records to be reused.