
PRODUCT SPECIFICATION — Q2 2026
The patient portal and alumni app we wish Kipu already provided. Powered by Team Recovery's white-label platform, integrated tightly with Kipu EMR. Every feature reads from or writes back to Kipu — or it is not worth building.
TARGET USERS
IOP/OP/MAT and Spravato/TMS-eligible individuals, many justice-involved and Medicaid recipients. This group has low portal and email use but high smartphone engagement. The app meets them where they already are.
A post-discharge community for ongoing support, event participation, recovery milestones, and serving as a referral source. Case studies show alumni referral readmissions can double within 6 months.
MDs, therapists, case managers, and peer support specialists who will primarily interact with app-generated data within the Kipu EMR — not a separate dashboard. The goal is zero additional systems for staff to manage.
CORE MODULES
Every module is designed to either read data from Kipu or write data back into Kipu, ensuring a single source of truth and supporting the Golden Thread of treatment documentation from admission through discharge and beyond.
HIPAA/42 CFR Part 2 compliant 1:1 and small-group messaging between clients and care team. Push notifications for new messages, overdue assessments, and safety check-ins.
KIPU INTEGRATION
Custom "App Message" note type in Clinical tab. Message threads logged and referenceable in patient chart. Staff signatures preserved.
Personal schedule view with groups, individual sessions, med management, and Spravato/TMS monitoring blocks. Group track schedule and alumni event calendar with RSVP.
KIPU INTEGRATION
Enterprise Scheduler hard blocks, appointment-specific docs, alerts for open assessments at check-in. Confirmations flow back to update appointment status.
Push consents, biopsychosocial, ROI, safety plan, and financial forms to client's device pre-admission. E-sign in app and submit directly to Kipu tabs.
KIPU INTEGRATION
Forms land in Consents, Clinical, Financial tabs. Demographics, payor, and emergency contacts auto-populate structured fields. Zero re-entry.
Auto-push BAM-R (30d), PHQ-9/GAD-7 (15d), PCL-5 (admission), Recovery Capital. Gamified reminders, streaks, and completion rewards.
KIPU INTEGRATION
Auto-enrollment rules, ChartCheck for incomplete assessments. Results feed to Assessments tab and AI chart snapshots. Outcome trends in progress note templates.
Moderated community wall, recovery tracker, milestone celebrations, alumni events RSVP, and a trackable "refer a friend" capture feature.
KIPU INTEGRATION
Alumni patient flag in Kipu. Custom alumni referral type for ROI tracking. Post-discharge outcome tracking opt-in.
SOS button with tap-to-call for Jade House crisis line and 988. View and edit safety plan synced from Kipu. Clear 42 CFR Part 2 logic for crisis messaging.
KIPU INTEGRATION
Safety plan form with mobile sync. Patient Flag (High Interest/SI risk). Crisis event logging to patient chart.
Secure upload of court docs, IDs, labs, Rx, probation paperwork, and FMLA forms. Auto-route to the correct Kipu tab with staff review task triggers.
KIPU INTEGRATION
Tab-specific upload rules. ChartCheck for missing documents. Task triggered for staff review and acknowledgment.

INTEGRATION ARCHITECTURE
The Jade House Recovery App sits between the client and the Kipu EMR, with Team Recovery's platform serving as the middleware layer. The Kipu Circle partnership handles the core assessment and outcomes data flow. Direct Kipu API access ($250/month per instance, 41 endpoints) enables the deeper integrations for forms, scheduling, and document routing.
The critical unknown is the boundary between what the Circle partnership covers and what requires direct API development. This must be confirmed with both Kipu and Team Recovery before any build begins.
Existing partnership integration. Survey and outcomes data already flows back to Kipu.
Likely covers: Assessments (BAM-R, PHQ-9, GAD-7, PCL-5), gamified check-ins, community engagement, push notifications
Unknown: Whether messaging, forms, and document uploads are included
41 endpoints, ~$250/month per instance.
GET
Demographics, appointments, assessments, documents
POST
New patients, appointments, messages, documents, safety plans
PATCH
Update patient info, appointment status, assessment completion
HIPAA + 42 CFR Part 2. All data transmission encrypted. BAA required from Team Recovery that explicitly covers 42 CFR Part 2. All messaging, documents, and assessments auditable, attributable, and exportable.
CLIENT JOURNEY
Every touchpoint in the first 30 days of a client's journey, showing exactly where data flows between the Jade House App and Kipu EMR. This is the workflow we will present to Team Recovery and Kipu to validate feasibility.
Calls Jade House crisis line OR walks in (zero waitlist promise)
Admissions creates patient in Kipu, assigns Episode (IOP/OP/MAT track)
KIPU EMR
Patient object created, Episode opened
Sends intake packet to client's phone via app
Consents (ROI, HIPAA, 42 CFR Part 2, app messaging consent)
Biopsychosocial intake form, Safety plan, Financial/insurance forms
Client completes and e-signs in app
KIPU EMR
Forms land in Consents, Clinical, Financial tabs; demographics auto-populate
Arrives for same-day intake, checked in via app or Kipu scheduler
Completes admission assessments while waiting: BAM-R, PHQ-9, GAD-7, PCL-5, Recovery Capital
KIPU EMR
Appointment marked "Arrived"; results auto-feed to Assessments tab, visible in AI chart snapshot
Reviews Kipu chart (forms, assessments auto-populated)
Completes clinical intake note using Kipu AI
Assigns client to care team (MD, therapist, case manager, peer)
KIPU EMR
Intake note logs to Clinical tab, Golden Thread starts. Care team assignment; app messaging enabled
Reviews app-submitted safety plan, assessments (PHQ-9, GAD-7, PCL-5)
Completes psych eval, adds diagnoses, prescribes MAT (Suboxone/Sublocade)
If Spravato/TMS eligible: REMS enrollment in Kipu custom form
KIPU EMR
Diagnoses → Problem List → Treatment Plan (Golden Thread). REMS form → Medical tab; 2-hour monitoring blocks added
Push notification: "Your schedule for Week 1 is ready"
App calendar shows: Group therapy (IOP: 9 hrs/week), individual session, med management, Spravato session
Client RSVPs/confirms in app
KIPU EMR
All appointments pulled from Enterprise Scheduler. Status updated; scheduler reflects confirmations
Sends secure message: "How are you feeling after Day 1?"
Client responds: "Good, but anxious about Spravato tomorrow"
KIPU EMR
Message logs to Clinical tab as "App Message" note type. Response appended to thread in chart
Push notification: "Time for your PHQ-9 check-in (3-assessment streak!)"
Completes PHQ-9 in app with gamified streak tracker
Dr. Phillips reviews AI chart snapshot: "PHQ-9 improved from 18→12"
KIPU EMR
PHQ-9 results auto-feed, ChartCheck clears "overdue". AI includes outcome trend in progress note template
Uploads court paperwork (probation check-in form) via app
Case manager reviews in Kipu, marks complete
KIPU EMR
Document auto-routes to Legal tab. Task triggered → reviewed → closed
Completes second BAM-R via app (30-day auto-enrollment)
Therapist uses Kipu AI to draft progress note: "BAM-R improved 15%, maintain IOP"
KIPU EMR
BAM-R compared to baseline; trend visible in outcomes dashboard. Progress note linked to Treatment Plan (Golden Thread intact)
Pre-admission
Forms push to app → submit → land in Kipu tabs (no re-entry)
Admission
Assessments in app → results to Kipu Assessments tab → visible in AI snapshots
Scheduling
Kipu scheduler → app calendar; app confirmations → Kipu appointment status
Messaging
Staff message (Kipu or app) → client app → response logs to Kipu chart
Outcomes
App push → client completes → Kipu outcomes dashboard + AI chart snapshot
Documents
Client uploads → Kipu tab + staff task → review/sign in Kipu
FEATURE ROADMAP
Each feature assessed against the current Team Recovery + Kipu Circle stack and ranked by implementation readiness. Items marked "Needs Discovery" require answers to open questions below before they can move to "Launch Ready."
Core Team Recovery feature. Threads referenceable in Kipu.
Triggered by Kipu events via Team Recovery.
Team Recovery reads schedule data from Kipu.
Requires Enterprise Scheduler API to update status directly.
Team Recovery supports this natively.
Requires PATCH endpoints for demographics and insurance.
Requires API endpoint specifying target document tab.
Core advertised Kipu Circle integration.
Results write back to patient assessment record.
Core Team Recovery features, app-only.
Writing referral back to Kipu requires API access.
Simple in-app feature, no Kipu integration needed.
Requires document GET and POST/PATCH API access.
Team Recovery supports this natively.
Requires API endpoint specifying target tab.
No clear Kipu API endpoint for task creation. Workaround: notification.
9
Launch Ready
7
Needs Discovery
1
Post-Launch
OPEN QUESTIONS
These questions must be resolved before committing engineering resources. The answers will determine the scope, cost, and timeline of the entire project.
Can you provide a copy of your BAA? Does it explicitly cover 42 CFR Part 2 for SUD data, or only HIPAA?
Can clinical staff manage all patient messaging and review app-generated data entirely from within Kipu EMR? Or does it require a separate Team Recovery dashboard?
Is the core integration (pushing assessment data back to Kipu) included in your platform fee, or does it require a separate Kipu API subscription at $250/month?
When a client confirms an appointment, does it update the specific appointment in the Enterprise Scheduler? When a document is uploaded, can we route it to a specific tab? How are message threads stored in Kipu?
All-in monthly/annual cost for a single-location, 150-patient capacity IOP/OP program including core app, outcomes tracking, and alumni features. Break down setup fees vs. recurring.
Confirm the full scope of the existing Kipu Circle integration. What data objects can be read/written without direct custom API development?
Does the API provide endpoints to programmatically confirm, cancel, or update the status of a patient's appointment?
Can the API place a completed, signed form into a specific custom tab? E.g., a signed ROI landing directly in the "Consents" tab?
Can the API populate discrete structured fields (First Name, DOB, Insurance Policy Number), or is it limited to attaching a PDF?
Can we get a personalized developer sandbox to test API calls and integration workflows before committing to the full build?
NEXT STEPS
Confirm Kipu Circle Partnership Scope
Clarify with Team Recovery which features are covered under the existing Circle integration vs. what requires direct Kipu API development. This is the critical dependency for scoping and pricing.
Schedule Discovery Calls
Coordinate separate technical calls with Team Recovery (platform capabilities, white-label customization) and Kipu (API access, BAA requirements, 42 CFR Part 2 compliance).
Validate Workflow with Clinical Team
Walk Dr. Phillips and the clinical leads through the Day 0–30 client journey to confirm the workflow matches actual intake, assessment, and treatment processes.
Review Portal Prototype
The interactive prototype demonstrates the proposed client experience. Use it as a reference point during partner discussions.
Prepared for Jade House Recovery — February 2026
Last Updated: February 15, 2026