-
ANG-2604
Define question dependencies so Archer enforces data entry conditions automatically — not just user judgment.
-
ANG-2677
Enables the system to verify user access and data availability before a study goes live, replacing a manual Postman step.
-
ANG-2720, ANG-2609
Fixes row order switching in Rave tables with default rows — Archer now uses index-based rather than @Context-based data export.
-
ANG-2637, ANG-2686, ANG-2554
Adds bidirectional connectivity with Advarra including subject, visit, and clinical data export endpoints.
-
ANG-2531
Sets up the foundational API structure for the Advarra EDC connector.
-
ANG-2555
Extends the Advarra connector with Archer-specific logic and mappings.
-
ANG-2556
Adds study structure endpoints to the Advarra connector: forms, question groups, and question definitions.
-
ANG-2721
Archer can now follow FHIR resource references to pull richer medication and clinical data from linked resources.
-
ANG-2721
Enables Archer to source data from the FHIR Medication resource for more precise medication coding.
-
ANG-2742
Enables Archer to pull findings and diagnostic test interpretations from the FHIR DiagnosticReport resource.
-
ANG-1716
Faster build times and improved developer experience by switching the Mapping webapp bundler from react-scripts to Vite.
-
ANG-2202
Success log entries now include more context, making it easier to trace and audit data export events.
-
ANG-2637
Adds subject enrollment and visit schedule endpoints to the Advarra connector.
-
ANG-2516
Captures and routes patient action events through the Yunu imaging connector.
-
ANG-2686
Implements the clinical data export endpoints that push captured EHR data to Advarra.
-
ANG-2543
Surfaces imaging patient lists from Yunu through the Clinician and Admin interfaces.
-
ANG-2616
The subject dropdown now filters in real-time as the clinician types, replacing an always-open list that caused confusion.
-
ANG-2629
Replaces UUID-style Advarra subject OIDs with human-readable subject names in the study subject selection screen.
-
ANG-2585
Establishes the initial API framework for the Scout connector integration.
-
ANG-2598
Adds imaging patient management (list and delete) to the Admin webapp via the Yunu connector.
-
ANG-2605
The training mode checkbox in the Admin webapp is now clearly labelled to avoid ambiguity.
-
ANG-2625
Upgrades the Mapping webapp data-fetching library to TanStack Query for better maintainability.
-
ANG-2626
Upgrades the Admin webapp data-fetching library to TanStack Query.
-
ANG-2627
Upgrades the Clinician webapp data-fetching library to TanStack Query.
-
ANG-2630
CI/CD pipeline and cloud infrastructure provisioned for the new Scout Connector API.
-
ANG-2663
Replaces cryptic EDC site reference codes with human-readable site names across the study selection screen.
-
ANG-2697
Removes the technical form reference code from the Clinical Data Review page — it added no value for clinical users.
-
ANG-2653
Fills gaps in FHIR MedicationRequest and AdverseEvent data sourcing so all required fields are captured.
-
ANG-2655
Implements create, read, update, and delete endpoints for the Scout connector.
-
ANG-2665
Sources adverse event end-date data from a FHIR extension field that was previously missed.
-
ANG-2442
Shows a clear error to users who open the Launch URL without the required SSO parameters instead of a blank screen.
-
ANG-2707
All backend services updated to .NET 10 for ongoing support and performance improvements.
-
ANG-2650
Mapping analysts now see human-readable question descriptions instead of internal codes in selection dropdowns.
-
ANG-2722
Export alerts and log entries now include the triggering user's email, improving auditability.
-
ANG-2601
Fixes a 500 crash when clinicians click 'Get Results' while searching for Yunu Imaging Observations.
-
ANG-2631
Fixes the 'Apply' button becoming permanently disabled after adding then removing an incomplete resource filter.
-
ANG-2683
All selection dropdowns in Admin and Mapping apps are now alphabetically sorted and searchable.
-
ANG-2780, ANG-2781
Visits in the Form Review screen now always match the EDC order, eliminating confusion caused by API-ordering differences.
-
ANG-2819
Date transformation mappings now support the dd/MMM/yyyy format required by certain EDC configurations.