Status Application

Live checks for platform services · Last checked: —
0 Up 0 Down
Checking
Waiting for refresh.
Last checked: —
Checking
Waiting for refresh.
Last checked: —
Checking
Waiting for refresh.
Last checked: —
Checking
Waiting for refresh.
Last checked: —
Checking
Waiting for refresh.
Last checked: —

MWR Clinical Trial Platform — Engineering Update

· Scope: January deliverables & current status · Capacity: 1 engineer (end-to-end across platform)
Stability & production hardening CI/CD & release safety Security / compliance Validic integrations in progress
Key throughput (January to date) Numbers reflect work managed as sole developer across 6 repos
112
Closed PRs (BE+FE)
Features, fixes, refactors, release prep
Delivery
80+
Jira tickets created/managed
Triaged, prioritized, tracked to release
Execution
1,073
GitHub Actions runs (2025)
Automated build/test/deploy cycles
Automation
3,808
Actions minutes (2025)
CI activity supporting safe releases
Reliability
60+
Azure resources (staging+prod)
IaC, monitoring, cost & security
Operations

Platform usage / scale signals

Data storage: 823 GB · Call minutes: 142,964 (≈ 2,383 hrs) · SD composed archiving: 58,655 mins

Tech-debt reduction

Net simplification: ~1.1 lines deleted for every line added (cleanup + dependency modernization from contractor handoff).

Latest highlights (staging → main) Key changes & impact
  • Recording pipeline modernization: simplified Vonage voice/IVR recording flow, auto-uploaded media to Azure, and removed legacy recording toggles/callbacks.
  • Database change control: disabled auto schema sync; moved to migration-driven releases for safer promotions.
  • Security + CI/CD hygiene: cleaned pipeline/config secrets, standardized Node 22 workflow, and tightened health checks.
  • Data quality improvements: refined coaching assessment export filtering and extended direct-auth token validity to 1 day.
  • Operational cleanup: reduced noisy logging, streamlined event handling, and simplified storage URL normalization.
Status: staging release candidate ready; awaiting merge/push window approval Focus next: Validic staging MVP & device validation
Notable high-impact merges (detail) Representative examples
  • API + recordings: Vonage voice/IVR recording flow simplified, auto-upload to Azure added, legacy recording flags/callbacks removed.
  • Infra + CI/CD: migration-driven deploys enabled, Key Vault + IaC secrets cleanup, pipeline health checks and tooling standardized.
Risk areas: recording pipeline + migration enforcement require smoke testing + close monitoring on release
Staging merge timeline Jul 2025 → Jan 2026
  1. Jul–Aug 2025
    Security + infra hardening — Key Vault work, Pusher removal, CI pipeline normalization, and environment config cleanup.
    Outcome: tighter secrets posture and more reliable deploy flow.
  2. Sep 2025
    Region + data stability sweep — SQL region experiments, rollbacks, export filtering improvements, and noisy logging reduced.
    Outcome: settings validated and stability preserved.
  3. Mid Jan 2026
    Release hygiene — migration-driven deploys enabled, CI health checks tightened, and security scanning workflow refined.
    Outcome: safer promotions with explicit DB change control.
  4. Late Jan 2026
    Recording pipeline refresh — Vonage voice/IVR recording flow simplified, auto-uploaded media to Azure, and legacy callbacks removed; token TTL extended.
    Outcome: more reliable recording capture + easier support access.
Work delivered (PRs by repository) Jan-to-date closed PR counts
Includes 6 primary repos: Portal UI, API, Trial Website, Lab Analytics API, Event Scheduler, plus platform maintenance work.
Operational signals Scale + platform activity
Release quality checklist (detail) Pre-prod gate
  • Smoke test voice/video (1:1 + conference), recording start/stop, and export paths.
  • Run DB migrations in staging and validate no schema drift.
  • Validate Key Vault access + deployment pipelines in staging.
  • Monitor post-release: auth errors, call failures, migration logs, queue backlogs.
Next 2–4 weeks (roadmap) Near-term outcomes
  • Validic integration MVP in staging: user creation + nightly syncs for device data; begin staged QA.
  • Integrations enablement: progressively validate Fitbit / Oura / CGM (Abbott approval flow in progress) as device testing completes.
  • Clinical trial website deployment: finalize media/asset compression pipeline (video/image) → deploy to CDN with secure login + metrics.
  • Production promotion: schedule staging → prod merge window; execute smoke tests; release with heightened bug reporting.
  • Onboarding support (Ben start 2/16): AD + permissions; study/IRB access prerequisites; set cadence for daily scrums & reporting.
Target: Validic MVP usable in staging within the next few weeks Constraint: single-developer bandwidth; sequencing is key
Needs / blockers What I need from the team
  • Device access for integration testing: Fitbit + Abbott CGM (and/or Oura) in office, plus test accounts where applicable.
  • Approval for staging → production push: select merge window and confirm release owner / comms plan.
  • Bug reporting during rollout: ask study teams to report issues quickly post-release (don’t assume it’s “known”).