Overview
This release focuses on improving the functionality and stability of ETO's Referral APIs, TouchPoints, and HMIS data handling. Key updates include the completion of Referral Rejection and Retraction API endpoints, enhancements to Internal Referral processing, and critical fixes to TouchPoints and API endpoints that impact user workflows and integrations.
Enhancements
Referral API Improvements
We've expanded the ETO Referral API with new Rejection and Retraction endpoints, making integrations of complete referral workflows into their applications easy and efficient. These additions enhance API usability, reduce manual intervention, and offer greater consistency when managing referral decisions programmatically. Whether you're building custom tools or automating service coordination, these updates streamline the experience for engineering teams and end users alike.
Implemented Retraction Functionality: The RetractReferral endpoint has been implemented to allow users to programmatically retract an existing referral. This includes proper status updates in the database.
Implemented Rejection Functionality: A new RejectReferral endpoint has been added to support rejecting a referral with contextual reasoning. This update ensures accurate referral management and supports downstream reporting.
Fixes
ETO HMIS | Project Entry HUD Assessments Missing in Data Pull
Previously, some databases experienced missing Project Entry HUD Assessments from the IncomeBenefits.csv export due to timestamp mismatches between response creation and program enrollment. This fix ensures that enrollment identifiers are correctly generated, even when times are offset, so these Assessments correctly appear in the export.
ETO API | 500 Error on GetCollection Endpoint
Certain Collection Types previously triggered a 500 server error when accessing the GetCollection API due to null or disabled fields being incorrectly processed. We've resolved this critical error by adding a null check to prevent future failures.
TouchPoint Element | E-Signature Element Causing Robot Error
We addressed a defect that previously triggered an error when saving or viewing a multi-Participant TouchPoint response where the e-Signature element was left blank. This update ensures e-Signature elements are handled safely regardless of conditional visibility or Required status.
Internal Referrals | Referrals Failing with Auto-Accept Enabled
Previously, referrals to programs with "Auto-Accept Internal Referrals" enabled were not processed correctly. Now, Participant enrollment proceeds as expected and forms missing a "Projected Start Date" field have added resilience.