bench get-app https://github.com/mykelu/mindwellos_erpnext15

[![Listed on Frappe Gems](https://frappegems.com/api/method/frappe_gems.seo.badge?app=mykelu%2Fmindwellos_erpnext15)](https://frappegems.com/gems/apps/mykelu/mindwellos_erpnext15)

MindWellOS ERPNext

ERPNext v15 / Frappe v15 implementation of the MindWellOS healthcare platform

Episode-Centered · Governance-First · PHI-Conscious · Persona-Driven

Architecture • System Diagram • Clinical Model • Dependency Model • Deployment • Setup • Roadmap

--- MindWellOS ERPNext is a **greenfield ERPNext-native implementation of the MindWellOS healthcare platform**, designed to support episode-centered care continuity, governance-first workflows, and a Philippines-first rollout. The platform preserves the clinical continuity chain: ```text Patient → Episode → Encounter → Orders → Timeline → Follow-up → Outcomes ``` ## What this Repository Is This repository is a greenfield architecture aligned to the canonical MindWellOS PRD and SRS, implemented using: - Frappe Framework v15 - ERPNext v15 - ERPNext Healthcare - custom MindWell domain app `mindwellos_erpnext` It preserves: - episode-centered care continuity - governance-first workflows - PHI minimization - persona-first UX - traceability from requirement to evidence Canonical persona references for all builds: - /Users/mykelu/Documents/devops/mindwellos_specification/docs/management/PERSONA_CATALOG.md - /Users/mykelu/Documents/devops/mindwellos_specification/docs/management/PERSONA_KPI_OWNERS.md CI secrets (persona drift check): - `MINDWELLOS_SPEC_REPO` (git URL of the spec repository) - `MINDWELLOS_ERPNEXT_REPO` (git URL of the ERPNext implementation repository) --- # Architecture Overview MindWellOS ERPNext follows an ERPNext-native-first architecture. Native ERPNext capabilities are used wherever possible. Custom MindWell modules extend ERPNext only where product requirements demand additional functionality. The platform is designed around: - episode-centered clinical continuity - governance-first workflows - PHI minimization - persona-first UX - traceability of requirements to implementation - Philippines-first deployment and compliance hardening --- # System Architecture ```mermaid flowchart TB subgraph Users A1[Clinicians] A2[Front Desk] A3[Care Coordinators] A4[Patients / Guardians] A5[Administrators] end subgraph Experience Layer B1[ERPNext Desk] B2[Patient Portal] B3[Mobile / Offline Apps] end subgraph MindWell Domain Layer C1[Episode Management] C2[Consent & Governance] C3[Care Team Coordination] C4[Patient Timeline] C5[Follow-up Orchestration] C6[Risk Engine] C7[CareClub Entitlement] end subgraph ERPNext Core D1[Patient Records] D2[Appointments] D3[Healthcare Services] D4[Billing & Accounting] D5[Inventory / Pharmacy] D6[HR Management] end subgraph Integration Layer E1[Claims Adapters] E2[Government Reporting] E3[FHIR / Interoperability] E4[External Systems] end subgraph Infrastructure F1[Frappe v15] F2[ERPNext v15] F3[MariaDB] F4[Bench Runtime] F5[Multi-site Deployment] end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B2 A5 --> B1 B1 --> C1 B1 --> C2 B1 --> C3 B1 --> C4 B1 --> C5 B2 --> C4 B3 --> C4 C1 --> D1 C3 --> D1 C5 --> D2 C7 --> D4 D1 --> E1 D4 --> E2 E1 --> E3 E3 --> E4 D1 --> F1 F1 --> F2 F2 --> F3 F2 --> F4 F4 --> F5 ``` --- # Clinical Domain Model ```mermaid flowchart LR P[Patient] E[Episode] A[Appointment] EN[Encounter] O[Orders] TL[Timeline Entry] FU[Follow-up Task] OUT[Outcome] CT[Care Team Assignment] CR[Consent Record] RISK[Risk Engine] REF[Referral] CC[CareClub Membership] P --> E P --> A P --> CR P --> CC E --> EN E --> CT E --> TL E --> FU E --> OUT E --> REF E --> RISK A --> EN EN --> O EN --> TL EN --> RISK EN --> OUT CR --> EN CT --> EN TL --> FU FU --> OUT CC --> O ``` --- # ERPNext Native + Custom App Dependency Model ```mermaid flowchart TB subgraph ERPNext_Native[ERPNext Native] N1[Patient] N2[Practitioner] N3[Appointment] N4[Healthcare Service] N5[Billing] N6[Stock / Pharmacy] N7[HR] N8[Portal] end subgraph MindWell_Custom_App[MindWell Custom App] C1[Episode] C2[Consent Record] C3[Care Team Assignment] C4[Patient Timeline] C5[Follow-up Task] C6[Risk Engine] C7[Outcome Tracking] C8[Referral] C9[CareClub] C10[Offline Intake] C11[Claims Model] C12[Gov Reporting Adapter] C13[Traceability Model] end N1 --> C1 N1 --> C2 N1 --> C3 N1 --> C4 N3 --> C1 N3 --> C5 N5 --> C11 N6 --> C11 C1 --> C4 C1 --> C5 C1 --> C6 C1 --> C7 C1 --> C8 C4 --> C5 C5 --> C7 C9 --> C11 ``` --- # Deployment and Tenancy Model ```mermaid flowchart TB subgraph Global_Engineering[Global Engineering] G1[Source Repo] G2[CI / QA] G3[Architecture Governance] end subgraph PH_Cell[PH Cell] PHB[Bench Runtime] PH1[Site: Clinic A] PH2[Site: Clinic B] PHDB[(MariaDB)] end G1 --> G2 G2 --> G3 G3 --> PHB PHB --> PH1 PHB --> PH2 PH1 --> PHDB ``` --- # Clinical Continuity Model MindWellOS is designed around a clinical continuity chain: ```text Patient -> Episode -> Encounter -> Orders -> Timeline -> Follow-up -> Outcomes ``` This continuity model drives: - care coordination - governance controls - timeline tracking - follow-up orchestration - outcomes measurement --- # Repository Structure ```text mindwellos_erpnext15/ ├── README.md ├── AGENTS.md ├── MEMORY.md ├── CODEX_BOOTSTRAP_INSTRUCTIONS.md ├── assets/ │ ├── banner/ │ ├── logo/ │ └── social/ ├── docs/ │ ├── architecture/ │ ├── execution/ │ ├── governance/ │ └── quality_assurance/ └── apps/ └── mindwellos_erpnext/ ├── hooks.py ├── modules.txt ├── patches.txt ├── api/ ├── config/ ├── public/ ├── templates/ ├── tests/ └── mindwellos_erpnext/ ├── fixtures/ ├── episodes/ ├── governance/ ├── timeline/ ├── followup/ ├── risk/ ├── careclub/ ├── mindwell_integrations/ ├── mindwell_healthcare/ ├── offline/ ├── security/ ├── access/ ├── shared/ └── tests/ ``` --- # Development Setup Install Bench: ```bash pip install frappe-bench ``` Initialize Bench: ```bash bench init mindwell-bench --frappe-branch version-15 cd mindwell-bench ``` Create Site: ```bash bench new-site mindwell.local ``` Install ERPNext: ```bash bench get-app --branch version-15 erpnext bench --site mindwell.local install-app erpnext ``` Install Custom App: ```bash bench get-app mindwellos_erpnext bench --site mindwell.local install-app mindwellos_erpnext ``` For bench-integrated details, see [ERPNext15_APP_GENERATION_AND_SITE_BOOTSTRAP.md](docs/architecture/ERPNext15_APP_GENERATION_AND_SITE_BOOTSTRAP.md). --- --- # Canonical Basis This implementation is strictly governed by the **MindWellOS Canonical Specifications**. These documents are included in the repository to serve as the immutable source of truth for all clinical, financial, and security behaviors. - **Core Specs**: [docs/specifications/core/](docs/specifications/core/) (PRD, SRS, Data Model) - **Clinical Standards**: [docs/specifications/clinical/](docs/specifications/clinical/) (Nursing, Physician, Pharmacy) - **Governance & Privacy**: [docs/specifications/governance/](docs/specifications/governance/) (Security, Compliance) - **Finance & Controls**: [docs/specifications/finance/](docs/specifications/finance/) (Revenue Cycle, Internal Controls) - **Design Guardrails**: [docs/specifications/design/TRAUMA_INFORMED_UX_GUARDRAILS.md](docs/specifications/design/TRAUMA_INFORMED_UX_GUARDRAILS.md) --- # Development Workflow --- # Roadmap - **Phase R1-R3: Hardened Compliance & Statutory Integration [COMPLETED]** - Immutable BIR CAS hash-chaining and PH statutory deductions (SSS/PH/PI). - PhilHealth PECWS 3.0 automation (CF4/eSOA) and DOH Annual Report mapping. - **Phase R4-R6: Ecosystem & Advanced Compliance [COMPLETED]** - HL7 FHIR R4 clinical mapping and BIR Form 2307 automated generation. - SSS R-3 and PhilHealth RF-1 reporting workpapers. - PhilHealth OAuth2 gateway migration and GAMOT package validation. - **Phase R7-R9: Privacy Hardening & Final Audit [COMPLETED]** - NPC-compliant PHI Access Audit Log and encrypted-at-rest narratives. - HL7 FHIR R4 longitudinal clinical history bundling. - 100% verified 1:1 DocType mapping against canonical MindWellOS specifications. - **Phase R10-R11: Operational Readiness & Golden Data [COMPLETED]** - UI Workflows for encounter lifecycle and regulatory Print Formats (Rx/Clinical Summary). - Ingestion of 300+ canonical Philippine records. - **Phase 18: Final PH Operational Hardening & PWA V3 [COMPLETED]** - Automated PhilHealth eSOA (SC/PWD logic) and mission sync idempotency. - Compliance Dashboard "Print Readiness" auditing. - **Phase 19: Clinical Intelligence & Advanced Analytics [COMPLETED]** - Clinical Outcome Prediction dashboard and Relapse Risk scorer. - Intervention Success Map (geospatial population analytics). --- ## Project Kanban & Status Dashboard ### Current Sprint Progress (Philippines Compliance) | Proposed | In Progress | Testing/QA | Completed ✅ | | :--- | :--- | :--- | :--- | | PWA V3 | Regional Multi-site | UAT Sign-off | **BIR CAS Chaining** | | HL7 V2 Integration | | Regression Suite | **PhilHealth PECWS 3.0** | | | | | **HL7 FHIR R4 Bundling** | | | | | **PHI Access Audit** | | | | | **PH Statutory Payroll** | | | | | **Operational Workflows** | | | | | **Print Ready eSOA/Rx** | ### Key Metrics - **Canonical Spec Status:** 100% AUDITED (Parity Complete) - **Compliance Health:** GREEN (100% Hardened) - **Operational Readiness:** 100% PILOT-READY - **Intelligence Maturity:** LEVEL 3 (Predictive Ready) ### Recent Technical Updates (Git-style) - `feat(analytics)`: Implement **Clinical Outcome Prediction** engine and **Intervention Success Map** for high-fidelity pilot insights. - `feat(ops)`: Finalize **PhilHealth eSOA** with multi-tier SC/PWD discount logic and eSOA PDF print formats. - `feat(sync)`: Implement **Mission Sync Idempotency** for PWA field operations (Receipt ledgers). - `feat(audit)`: Conduct comprehensive **Parity Audit vs Canonical Specifications**; 1:1 mapping verified. - **Advanced Analytics Hub**: Real-time PHQ-9/GAD-7 drift detection and geospatial efficacy mapping active. - **PWA v3 & HL7 v2 Bridge**: Hardened background sync and automated machine result parsing implemented. ### Next Milestones 1. **Philippines Rollout Hardening**: Complete bench validation, smoke tests, and p