Mapping every navigation view in the v1 prototype (SolidRock_RN_ClinOS.html) to the production implementation.
| V1 Prototype View | Production Route | Status | Production Improvements |
|---|---|---|---|
| 🏠 Dashboard | portal/staff → RN dashboard (index.tsx) |
Implemented | Live DB data, real visit schedule, badge notifications, role-specific rendering (Admin/CM/RN/HCA) |
| 📇 Client chart | portal/staff/care-recipients.$id |
Implemented | Full demographics, allergies, AHD, DNAR, medications, team, goals — persisted in DB, not hardcoded |
| 📐 Assessments (Waterlow, Braden, MUST, STRATIFY, Morse Falls, Barthel, 4AT, AMTS, Abbey Pain, GDS-4, CFS, Carer Strain) | portal/staff/care-recipients.$id/assessment.$assessmentId |
Implemented | Live scoring, band calculation, DB persistence, e-signature, immutable audit log, version history — all 12 scored tools |
| 📝 Care plans | portal/staff/care-recipients.$id.index (plans tab) |
Implemented | SMART goals, interventions, version history, linked assessments, client + family e-signature, review dates |
| ❤️ Observations (NEWS2) | portal/staff/care-recipients.$id.observations |
Implemented | Full NEWS2 auto-scoring with all 6 parameters, trend chart, sepsis screen flag, immediate escalation trigger |
| 🩹 Wound centre | portal/staff/workspace/wounds |
Implemented | SVG body map for site selection, wound measurements with trend graph (area/L/W/D), tissue grading, exudate, photo consent, compression ABPI |
| 💊 Medications / MAR | portal/staff/care-recipients.$id.emar |
Implemented | eMAR with 5 Rights check, PRN administration recording, high-risk drug flags (anticoagulants), omission logging |
| 🧰 Interventions | portal/staff/care-recipients.$id.interventions |
Implemented | Linked to care plans, RBAC-protected, audit-logged, per-intervention completion tracking |
| 🗂️ Registers (escalations, incidents, referrals, complaints, infections) | portal/staff/registers |
Implemented | All 5 register types live, with status tracking, CAPA actions, open disclosure recording, badge count on nav |
| ✨ AI Assistant | Multiple server functions: $summariseShift, $detectAnomalies, $generateCarePlan |
Implemented | Server-only, auth-gated, no client-side API key exposure — unlike the prototype which calls Claude from the browser |
| 🌙 Shift summary | portal/staff/workspace/shift-summaries |
Implemented | AI-assisted summary, care-given narrative, sent to family portal after sign-off |
| 📊 Analytics | portal/staff/index.tsx (dashboard KPIs) |
Partial | Dashboard KPI tiles are live. A dedicated analytics page is not a separate route in production. Low priority for RN role. |
| 🤝 HCA mode (CarePad engine inside prototype) | Separate portal/staff HCA dashboard + care notes |
Implemented differently | Production separates RN and HCA workflows by role rather than a mode-switch button — this is architecturally superior and RBAC-enforced |
V2 (v2/index.html) introduces two major new clinical instruments not present in V1 or production. Both are first-class features described in Prof's accompanying note (prompt.txt).
This is the holistic multi-domain needs assessment that must be completed at care commencement and at every significant change in a client's condition. It is an HSE regulatory requirement and the gateway document that justifies the level of Home Support awarded.
What V2 implements:
Why it matters: Without this, an RN filling out individual scored tools has no structured framework tying them together. The Comprehensive Assessment is the clinical logic layer that connects all other assessments to a care plan and to HSE funding justification.
A co-produced document written with the client (and family) that captures who the person is — not just their health conditions. HIQA inspectors check for this as evidence of person-centred care. Every carer is expected to read it before their first visit.
What V2 implements:
Why it matters: This is currently missing from production entirely. HIQA will ask to see person-centred profiles during inspections. The absence of Key to Me in the system creates a compliance risk and a gap in the evidence of individualised care.
care-recipients.$id route, following the existing assessment pattern.
Prof's message specifies a 3-section portal structure for all staff roles, plus a long list of required Section 3 features and AI capabilities. Status against each item below.
| Section | Required | Status | Notes |
|---|---|---|---|
| Section 1 Personal Profile |
Name & DOB, Shifts/roster, Schedule, Training | Implemented | Profile, schedule, training/compliance, professional registration all built |
| Section 2 Care Recipients |
Permission-gated access only | Implemented | Protected via authMiddleware + requirePermission + visit-based access patterns |
| Section 3 Portal Essentials |
Full list — see table below | Partially implemented | Core clinical features are live; operational and wellness features are Phase 2+ |
| Feature | Status | Production notes |
|---|---|---|
| Personal Dashboard | ✓ Live | KPI tiles, visit schedule, clinical alerts on landing page |
| Calendar | Partial | Visit schedule exists; no full calendar widget with month/week view |
| Smart Notifications | Partial | Badge counts on nav, clinical alerts banner; no push notifications or smart rules engine |
| Secure Messaging | Phase 2 stub | Route exists at workspace/messages — coming in Phase 2 |
| AI Copilot | ✓ Live | $summariseShift, $detectAnomalies, $generateCarePlan, AI assessment suggestions — all server-only, auth-gated |
| Document Management | Phase 2 stub | Route exists at workspace/documents — coming in Phase 2 |
| Policies Library | Partial | Policy pages exist on public site; not surfaced inside staff portal directly |
| SOP Library | Not built | No SOP module. Could share the Policies Library infrastructure. |
| Mandatory Training | ✓ Live | portal/staff/training — compliance documents, expiry alerts, verification workflow |
| eLearning | Not built | No eLearning module planned yet |
| Competency Records | ✓ Live | portal/staff/account/registration — NMBI/CORU professional body records with verification workflow |
| Digital Forms | Partial | Assessment tools fulfil structured digital forms; no generic form builder |
| Incident Reporting | ✓ Live | Full incident register with severity grading, RCA, CAPA, open disclosure recording |
| Complaints | ✓ Live | Complaints register with grade, response tracking, learning capture, compliments |
| Risk Reporting | ✓ Live | Escalations register with priority, due dates, to/from tracking |
| Audit Checklist | Not built | Not in production; would complement the existing registers |
| Electronic Signatures | ✓ Live | E-signature on assessments, care plans, shift summaries — SHA-256 audit chain |
| Voice Notes | Not built | Browser Web Speech API could power this; not yet planned |
| Offline Mode | Not built | Web app with no PWA/service worker. Important for rural visits with poor connectivity. |
| GPS Visit Verification (50m geofence) | ⚠ CRITICAL GAP | Prof specifically requires that care data is inaccessible unless the RN is within 50 metres of the client's residence. This is not implemented. Care data is currently accessible anywhere after login. This is a clinical governance and data protection requirement, not just a feature. |
| Mileage Recording | Not built | HR/payroll feature; not yet planned |
| Expense Claims | Not built | HR/payroll feature; not yet planned |
| Time Tracking | Partial | Visit tap-in/tap-out workflow exists in care notes; no dedicated timesheet module |
| Digital ID | Not built | Staff photo ID card (in-app). Not yet planned. |
| Performance Dashboard | Not built | Governance/admin has analytics; no individual RN performance view |
| Personal Development Plan | Not built | HR portal scope; not yet planned |
| Appraisal Centre | Not built | HR portal scope; not yet planned |
| CPD Portfolio | Partial | Professional registration tracks NMBI/CORU body; no CPD evidence portfolio |
| Reflective Practice Journal | Not built | NMBI CPD requirement; not yet planned |
| Wellness Hub | Not built | Staff wellbeing feature; not yet planned |
| Leave Management | ✓ Live | portal/staff/hr/leave — full leave request, approval workflow, balance display |
| Payroll Access | Not built | Would require payroll system integration |
| Reward & Recognition | Not built | Compliments are captured in the complaints register; no dedicated feature |
| Internal News Feed | Partial | Announcements array exists in dashboard; no full news feed / post management |
| AI Capability | Status | Production notes |
|---|---|---|
| Writing professional notes | ✓ Live | AI care note drafting in shift summary and care plan generation |
| Summarising care visits | ✓ Live | $summariseShift — AI shift summary sent to family portal |
| Predicting risks | ✓ Live | $detectAnomalies — flags health pattern changes across care notes and observations |
| Detecting missing documentation | Partial | Dashboard shows outstanding docs; no AI-specific "find gaps" function |
| Suggesting evidence-based interventions | ✓ Live | AI care plan suggestion after each assessment; links assessment score to interventions |
| Recommending staffing adjustments | Not built | Governance/ops-level AI feature; not in scope for RN portal |
| Prioritising tasks | ✓ Live | Dashboard priority scoring (NEWS2 trending, wound due, escalations) guides RN's daily order |
| Drafting reports | ✓ Live | AI shift summary, care plan narrative, assessment summary |
| Analysing trends | ✓ Live | NEWS2 trend detection across observations, wound area trend graph |
| Identifying safeguarding concerns | Partial | Safeguarding register exists; no AI auto-detection of safeguarding signals in notes |
| Detecting burnout risks | Not built | Staff wellbeing scope; not yet planned for any portal |
| Forecasting workforce demand | Not built | Governance/ops feature; not in scope for RN portal |
| Monitoring compliance | Partial | Training expiry alerts; no AI compliance monitoring engine |
| Preparing audit reports | Not built | Admin portal has AI content generation; no audit report drafter |
| Assisting with incident investigations | Partial | Incident register has RCA and CAPA fields; no AI to suggest RCA factors |
| Supporting decision-making within authorised role | ✓ Live | All AI features are RBAC-gated; RN AI tools differ from HCA AI tools per role |
Ranked by clinical and regulatory impact. Items 1–3 should be addressed before any HIQA inspection or HSE service commencement.
Prof explicitly stated: "the nurse can't have access to these data or information unless he has arrived or he is within 50 metres to the client's residence." This is currently not enforced. Implementation approach: use the browser Geolocation API on visit start, compare to client address coordinates (Geocoded from Eircode), gate the care record access behind a server function that validates proximity. Requires storing lat/lng per client address and a visit-state machine (pre-visit / in-visit / post-visit). Must also handle GPS unavailability gracefully (manual override with audit reason). This is a data protection and clinical governance requirement.
Build as a new tab or card on care-recipients.$id. The 13 domains, tap-select options, risk indicator count, care-intensity level, auto-tool recommendations, AI narrative summary, and e-signature are all clearly defined in the v2 prototype. Schema addition: one new table comprehensiveAssessment linked to care recipient and authored by RN. Estimated effort: 1–2 days.
Build as a tab on care-recipients.$id alongside the care plan and assessment tabs. 11 editable text sections, co-production contributor tracking, print-friendly layout, and "share to Family Portal" action. Schema addition: one keyToMe table with 11 text columns + updated_at + co-produced_by. Estimated effort: 1 day.
Prof's message specifies the portal nav must visually show 3 sections: (1) Personal Profile, (2) Care Recipients, (3) Portal Essentials. Currently the sidebar is a flat list of Clinical Workspace items. Add visual section dividers and labels to the existing sidebar nav. No backend changes needed — UI-only restructure.
These 5 routes already exist with "Coming in Phase 2" placeholder content. They should remain on the roadmap and be implemented after P1–P4 are complete. Secure Messaging is the highest-impact of the five as it directly affects inter-team communication and care coordination.
Direct confirmation of requirements from Adeniyi's message that are fully live in production.