Known Gaps — Handover Materials
This page consolidates everything that was absent, incomplete, or explicitly blank in the handover materials delivered by MWE (Elevare Group). Each gap includes where to look to recover the information.
Client Documents
Source PDF: 3.2 Home Health Onboarding Documents/client documents/NHC _ Home Health Employees Onboarding Documents (Client) - Client Documents.pdf
| Gap | What is known | What is missing | Where to look |
|---|---|---|---|
| HCC Admission Document names | 7 documents exist; all have validation rules | Canonical names not listed | novahomecareapi/templates/forms/ and Form model fixtures/admin |
| HHP Admission Document names | 10 documents exist; 2 are admin-only manual uploads | Canonical names not listed | Same as above |
| v5.0.0 client doc additions | 6 new docs added for both HCC and HHP | Names not listed | Same as above |
| v5.1.0 compliance document type names | 5 new types added with dual-signature flow | Names not listed | Same as above; or 3.1 Functional Documentation/NHC _ v5.1.0 - Functional Specification Document (Client).pdf (names may be buried in the spec body) |
Employee Documents
Source PDF: 3.2 Home Health Onboarding Documents/employee documents/NHC _ Home Health Employees Onboarding Documents (Client) - Employee Documents.pdf
| Gap | What is known | What is missing | Where to look |
|---|---|---|---|
| Application Document names | 8 documents exist, required for all applicants | Names not listed | novahomecareapi/templates/forms/ and Form model fixtures |
| Home Care Onboarding document names | 23 documents exist | Names not listed | Same as above |
| v5.0.0 employee doc additions | 13 new docs added | Names not listed | Same as above |
Notifications
Source PDF: 3.3 NHC _ Notifications/NHC _ Notifications by Flow - Employee Flow.pdf
| Gap | Detail | Where to look |
|---|---|---|
| Notifications #1–#16 (Employee Flow) | Exist in the source PDF but were not transcribed into this docs site | Read pages 1–6 of the source PDF directly |
| Notification #19 | Row was blank in the source document — MWE provided no content | Ask MWE |
| Client notification flow | Not included in handover zip | Ask MWE |
| Admin notification flow | Not included in handover zip | Ask MWE |
| Marketer notification flow | Not included in handover zip | Ask MWE |
Referral / Marketer Flow
The Marketer/Referral flow was not documented in any delivered spec. Sections 3.3–3.5 of the main functional specification (3 Functional Documentation/NHC _ Portal Functional Specification Document (Client-Provisional).pdf) were empty placeholder stubs with no content.
| Gap | Where to look |
|---|---|
| Referral submission flow | Read portals frontend source under the MARKETER role routes |
| Referral tracking / status updates | Same |
| Admin referral management | Same; or Django API views scoped to referrals |
| Marketer-specific notifications | See Notifications gap above |
Functional Spec — Empty Sections
The following sections of the main functional spec (3 Functional Documentation/NHC _ Portal Functional Specification Document (Client-Provisional).pdf, 77 pages) were present as headings only, with no content:
- Section 3.2.23
- Section 3.2.24
- Section 3.3
- Section 3.4
- Section 3.5
It is unknown what these sections were intended to cover. Ask MWE for a complete version of the spec, or infer from the codebase.
Per-Organization Service Types
Only Aurora Home Health (Minnesota) was explicitly confirmed as Home Health only in the handover materials. The service type configuration for the remaining 12 organizations was not stated per-org in any delivered document.
| What is known | What is missing | Where to look |
|---|---|---|
| Aurora Home Health = HH only | Service type for the other 12 orgs | Query the Organization model in the database (service_types field or equivalent); or confirm with MWE |
Until confirmed, all non-Aurora orgs are assumed HC + HH based on context. Do not rely on this assumption for feature-gating logic.