BipoAI — Project Status Report

Digital Health Application for Bipolar Disorder Self-Management

Generated: 2026-04-07 Source: Confluence SRS v2.9 + Jira (BA) + Git SRS v2.9 / DFR v3.0
46
Jira Tickets
0%
Completion
12 / 38
SRS Coverage
0
Tickets Done
26
SRS Gaps
◆

1. Executive Summary

BipoAI production development begins 2026-04-07, starting with Sprint-1 (Foundation & Infrastructure). The project has 46 Jira tickets across 4 sprints with 0% completion — all tickets remain in pre-development status (43 Selected for Development, 3 Backlog). The SRS v2.9 and DFR v3.0 are comprehensive and finalized (last updated 2026-03-29), defining 38 functional features across 5 modules.

Current Jira coverage addresses 12 of 38 SRS features (32%), focused on Patient Core (Module 1) and Patient Extended (Module 2). No tickets exist yet for Clinician (Module 3, except Patient Invite), Admin (Module 4), or Researcher (Module 5) features.

The git repository currently contains only the demo prototype (React + Vite); production app scaffolding (React Native + Cloudflare Workers) begins 2026-04-07 with Sprint-1.

⚠
Note: Production development begins 2026-04-07 (Sprint-1). AbEM quarterly reporting target is Q3 2026 — ~3 months to reach operational readiness, at risk given no Admin module tickets exist yet.
▶

2. Current Focus Areas

Development Focus

Active Sprint — Sprint-1 (starting 2026-04-07)

Sprint-1 (22 tickets) — Foundation & Infrastructure must start first:

  • BA-238 / BA-246: Project Scaffolding — React Native Mobile App (SRS: Infrastructure)
  • BA-239 / BA-247: Project Scaffolding — CF Workers Backend (SRS: Infrastructure) — BA-239 still in Backlog
  • BA-249: User Registration & Login — OAuth 2.0 + JWT (SRS: Security NFRs)
  • BA-250: MFA for Clinicians & Admins (SRS: Security NFRs)
  • BA-251: Role-Based Access Control (SRS: Security NFRs)
  • BA-240–BA-245: Database Schema entities (SRS: Data Model)
  • BA-248: CI/CD Pipeline (SRS: Infrastructure)

Key SRS Requirements Being Addressed by Sprint-1

  • Cross-cutting: Infrastructure scaffolding (React Native + Cloudflare Workers)
  • Cross-cutting: Authentication & Security (OAuth 2.0, JWT, MFA, RBAC, TLS, AES-256)
  • Cross-cutting: Database & Data Model (all 24 core entities + 9 study entities + 7 config entities)

Testing Focus

Ready for Testing (Developed)

ℹ
None — no tickets have reached Developed status.

Blocked / Awaiting Dev

All testing is blocked until Sprint-1 items reach Developed status. Sprint-2 features (Onboarding, Check-In, Home Screen) depend on Sprint-1 infrastructure completion.

■

3. SRS Feature Coverage

Coverage 12 / 38 (32%)
Completed 0 / 38 (0%)
Gaps (No Ticket) 26
Module 1

Patient Core

#SRS FeatureSRS RefJira EpicSprintStatusNotes
1OnboardingDFR 1.1BA-257Sprint-2Not Started1 story + 2 sub-tasks
2Daily Check-InDFR 1.2BA-258Sprint-2Not Started1 story + 2 sub-tasks
3Home ScreenDFR 1.3BA-259Sprint-2Not Started1 story + 2 sub-tasks
4InsightsDFR 1.4——Gap (no ticket)Charts, time ranges, phase/zone bars
5Early Warning System (EWS)DFR 1.5——Gap (no ticket)Traffic-light state machine, admin rules
6Phase IdentificationDFR 1.6——Gap (no ticket)Bipolar phase detection, admin rules
Module 2

Patient Extended

#SRS FeatureSRS RefJira EpicSprintStatusNotes
712-Week Therapeutic CourseDFR 2.1BA-273Sprint-4, 5Not Started1 story (Backlog), no sub-tasks yet
8InterventionsDFR 2.2BA-274Sprint-4Not Started1 story (Backlog), no sub-tasks yet
9Medication TrackingDFR 2.3BA-275Sprint-4Not StartedNo stories/sub-tasks yet
10Ulysses ContractDFR 2.4BA-276Sprint-4Not StartedNo stories/sub-tasks yet
11Suicide Risk ScreeningDFR 2.5BA-277Sprint-4Not StartedGrouped under Safety & Crisis epic
12Crisis ScreenDFR 2.6BA-277Sprint-4Not StartedGrouped under Safety & Crisis epic
13Privacy & ConsentDFR 2.7BA-278Sprint-4Not StartedNo stories/sub-tasks yet
14Clinician Code SharingDFR 2.8BA-260Sprint-2, 4Not StartedGrouped under Patient-Clinician Connection
Module 3

Clinician Features

#SRS FeatureSRS RefJira EpicSprintStatusNotes
15Patient InviteDFR 3.1BA-260Sprint-2, 4Not StartedGrouped under Patient-Clinician Connection
16Patient TriageDFR 3.2——Gap (no ticket)Urgency-sorted patient list
17Patient DetailDFR 3.3——Gap (no ticket)Life Chart, check-in history, medications
18Trialogue DashboardDFR 3.4——Gap (no ticket)Shared warning signs, approval workflow
19Auto-NotificationsDFR 3.5——Gap (no ticket)Email on Alert/screening trigger
20Feedback LoopDFR 3.6——Gap (no ticket)EWS/Phase accuracy feedback
21Adverse Event ReportingDFR 3.7——Gap (no ticket)Structured form, immutable
22Clinician SettingsDFR 3.8——Gap (no ticket)Notification prefs, weekly digest
Module 4

Admin & Super Admin

#SRS FeatureSRS RefJira EpicSprintStatusNotes
23Platform OverviewDFR 4.1——Gap (no ticket)KPI dashboard
24Clinician & Researcher MgmtDFR 4.2——Gap (no ticket)Applications, approval, documents
25Metric BuilderDFR 4.3——Gap (no ticket)Check-in metric configuration
26Warning Rule EngineDFR 4.4——Gap (no ticket)IF/THEN rules for EWS
27Phase ID EngineDFR 4.5——Gap (no ticket)IF/THEN rules for phase detection
28Check-in Schedule ConfigDFR 4.6——Gap (no ticket)Per-study time slots
29Study & Content MgmtDFR 4.7——Gap (no ticket)Studies, course content upload
30AI ConfigurationDFR 4.8——Gap (no ticket)Expectation files, comparison
31ComplianceDFR 4.9——Gap (no ticket)GDPR audit, MDR tracking
32Admin ManagementDFR 4.10——Gap (no ticket)Super admin only
33AI Analysis LayerDFR 4.11——Gap (no ticket)Clinical intelligence, not patient-facing
34Post-Approval MonitoringDFR 4.12——Gap (no ticket)EWS/Phase accuracy tracking
35AbEM Quarterly ReportingDFR 4.13——Gap (no ticket)BfArM metrics, target Q3 2026
Module 5

Researcher Features

#SRS FeatureSRS RefJira EpicSprintStatusNotes
36Researcher PortalDFR 5.1——Gap (no ticket)Anonymized data, k-anonymity
37AI-Powered AnalyticsDFR 5.2——Gap (no ticket)Expected vs actual comparison
38ExportDFR 5.3——Gap (no ticket)CSV/FHIR R4, k-anonymity
Cross-Cutting

Infrastructure

#AreaJira EpicSprintStatusNotes
AFoundation & InfrastructureBA-235Sprint-1Not StartedRN + CF Workers scaffolding, CI/CD
BAuthentication & SecurityBA-236Sprint-1Not StartedOAuth 2.0, JWT, MFA, RBAC, encryption
CDatabase & Data ModelBA-237Sprint-1Not Started40 entities (24 core + 9 study + 7 config)
⚙

4. Sprint Progress

Sprint-1: Foundation — Active

Starting 2026-04-07 Branch: to be created
0%

22 tickets — 0 Done • 0 In Progress • 21 Selected for Development • 1 Backlog

KeyTypeSummaryStatus
BA-235EpicFoundation & InfrastructureSelected for Dev
BA-236EpicAuthentication & SecuritySelected for Dev
BA-237EpicDatabase & Data ModelSelected for Dev
BA-238StoryProject Scaffolding — RN Mobile AppSelected for Dev
BA-239StoryProject Scaffolding — CF Workers BackendBacklog
BA-240StoryDB Schema — User & Profile EntitiesSelected for Dev
BA-241StoryDB Schema — Check-In & Clinical EntitiesSelected for Dev
BA-242StoryDB Schema — Connection & Consent EntitiesSelected for Dev
BA-243StoryDB Schema — Study & Course EntitiesSelected for Dev
BA-244StoryDB Schema — Configuration & Audit EntitiesSelected for Dev
BA-245StorySeed Data — Default MetricsSelected for Dev
BA-246StoryProject Scaffolding — RN Mobile AppSelected for Dev
BA-247StoryProject Scaffolding — CF Workers BackendSelected for Dev
BA-248StoryCI/CD PipelineSelected for Dev
BA-249StoryUser Registration & Login (OAuth 2.0 + JWT)Selected for Dev
BA-250StoryMFA for Clinicians & AdminsSelected for Dev
BA-251StoryRole-Based Access Control (RBAC)Selected for Dev
BA-252StoryTLS 1.2+, AES-256 Encryption & Session MgmtSelected for Dev
BA-253Sub-taskFE: User Registration & LoginSelected for Dev
BA-254Sub-taskBE: User Registration & LoginSelected for Dev
BA-255Sub-taskFE: MFA for Clinicians & AdminsSelected for Dev
BA-256Sub-taskBE: MFA for Clinicians & AdminsSelected for Dev
Notes:
  • BA-238 and BA-246 appear to be duplicate stories for RN Mobile App scaffolding
  • BA-239 and BA-247 appear to be duplicate stories for CF Workers Backend scaffolding
  • BA-239 is the only Sprint-1 item still in Backlog

Sprint-2: Patient Core Features

Not Started Blocked by Sprint-1
0%

16 tickets — 0 Done • 0 In Progress • 16 Selected for Development

KeyTypeSummaryStatus
BA-257EpicPatient OnboardingSelected for Dev
BA-258EpicDaily Check-InSelected for Dev
BA-259EpicHome ScreenSelected for Dev
BA-260EpicPatient-Clinician ConnectionSelected for Dev
BA-261StoryHome ScreenSelected for Dev
BA-262StoryDaily Check-InSelected for Dev
BA-265StoryPatient Onboarding FlowSelected for Dev
BA-266StoryPatient Invite — Clinician Code GenerationSelected for Dev
BA-263Sub-taskFE: Daily Check-InSelected for Dev
BA-264Sub-taskBE: Daily Check-InSelected for Dev
BA-267Sub-taskFE: Patient Onboarding FlowSelected for Dev
BA-268Sub-taskBE: Patient Onboarding FlowSelected for Dev
BA-269Sub-taskFE: Home ScreenSelected for Dev
BA-270Sub-taskBE: Home ScreenSelected for Dev
BA-271Sub-taskFE: Patient Invite — Clinician Code GenSelected for Dev
BA-272Sub-taskBE: Patient Invite — Clinician Code GenSelected for Dev

Sprint-4: Patient Extended & Clinical Features

Not Started Blocked by Sprint-1, 2
0%

9 tickets — 0 Done • 0 In Progress • 7 Selected for Development • 2 Backlog

KeyTypeSummaryStatus
BA-260EpicPatient-Clinician ConnectionSelected for Dev
BA-273Epic12-Week Therapeutic CourseSelected for Dev
BA-274EpicInterventionsSelected for Dev
BA-275EpicMedication TrackingSelected for Dev
BA-276EpicUlysses ContractSelected for Dev
BA-277EpicSafety & CrisisSelected for Dev
BA-278EpicPrivacy & ConsentSelected for Dev
BA-279Story12-Week Course — Structure & ProgressionBacklog
BA-280StoryInterventions — Zone & Phase CardsBacklog
Notes:
  • 4 epics (BA-275, BA-276, BA-277, BA-278) have no child stories yet — need backlog grooming
  • Sprint-3 has no tickets assigned
  • Sprint-5 only contains BA-273 (shared with Sprint-4)
◉

5. Epic Progress

EpicKeyStoriesSub-tasksDoneIn ProgressRemainingCompletion
Foundation & InfrastructureBA-23550005
0%
Authentication & SecurityBA-23644008
0%
Database & Data ModelBA-23760006
0%
Patient OnboardingBA-25712003
0%
Daily Check-InBA-25812003
0%
Home ScreenBA-25912003
0%
Patient-Clinician ConnectionBA-26012003
0%
12-Week Therapeutic CourseBA-27310001
0%
InterventionsBA-27410001
0%
Medication TrackingBA-27500000
0%
Ulysses ContractBA-27600000
0%
Safety & CrisisBA-27700000
0%
Privacy & ConsentBA-27800000
0%
☷

6. Branch Status

Production (main)

  • Last commit: ab38585 Add project-status skill config with verified Atlassian settings
  • Contains: Demo prototype only (React + Vite). No production app code.
  • 7 merged PRs (2026-02-09 to 2026-02-12): demo UI, design system, SRS/project plan docs (since deleted)

Testing/QA (develop)

✗
Does not exist. No develop branch has been created.

In Development

⊘
Development starting 2026-04-07. develop and sprint-1 branches to be created as first step.

Stale Branches (fully merged, can be cleaned up)

BranchStatus
claude/create-srs-project-plan-ja2WuFully merged to main, 0 commits ahead
origin/claude/analyze-ux-docs-irZsSFully merged to main, 0 commits ahead
origin/claude/ux-design-analysis-BptHfFully merged to main, 0 commits ahead

Tags/Releases

None

✓

7. Open Bugs

✓
No bugs found in the project.
⚠

8. Risks & Gaps

SRS Coverage Gaps (26 features with no Jira tickets)

  • Patient Core: Insights (1.4), EWS (1.5), Phase Identification (1.6) — these are critical MVP features with no tickets
  • Clinician (entire module except Patient Invite): Triage (3.2), Patient Detail (3.3), Trialogue (3.4), Auto-Notifications (3.5), Feedback Loop (3.6), Adverse Events (3.7), Settings (3.8)
  • Admin (entire module): All 13 features (4.1–4.13) including Metric Builder, Rule Engines, Compliance, AbEM Reporting
  • Researcher (entire module): Portal (5.1), AI Analytics (5.2), Export (5.3)

Sprint Planning Issues

  • Sprint-3 is empty — no tickets assigned
  • Sprint-4 epics without stories: Medication Tracking (BA-275), Ulysses Contract (BA-276), Safety & Crisis (BA-277), Privacy & Consent (BA-278) have epics but no child stories or sub-tasks — need backlog grooming
  • Possible duplicate stories: BA-238/BA-246 (RN scaffolding) and BA-239/BA-247 (CF Workers scaffolding) appear to be duplicates under BA-235

Development Readiness

  • Branching setup needed: develop and sprint-1 branches must be created as the first action (strategy: main → develop → sprint-N)
  • No CI/CD pipeline: BA-248 is planned but not started — should be an early Sprint-1 deliverable
  • No production code yet: Repository contains only the demo prototype; production scaffolding (React Native + CF Workers) is the immediate priority

Regulatory Timeline Risk

⚠
AbEM quarterly reporting target is Q3 2026 (SRS 4.13) — development starting 2026-04-07 leaves ~3 months to reach operational readiness, which is at risk given no Admin module tickets exist.
EWS and Phase ID are safety-critical features with no Jira tickets yet.
★

9. Summary Metrics

MetricValue
Total SRS Functional Features38
Features with Jira tickets12 (32%)
Features completed (Done)0 (0%)
Total Jira tickets46
Tickets Done0
Tickets In Progress0
Tickets Selected for Development43
Tickets in Backlog3
Open Bugs0
Sprints Planned4 (Sprint-1, 2, 4, 5)
Sprint-3Empty (no tickets)
Current SprintSprint-1 (starting 2026-04-07)
Development Start Date2026-04-07
SRS Version2.9 (2026-03-29)
DFR Version3.0 (2026-03-29)
Production Branchesmain only (develop + sprint-1 to be created)
Stale Branches3 (fully merged, cleanable)