# Known limitations — important

This deliverable is an initial functional milestone, not the complete enterprise system described in the master prompt. Implemented: Laravel project structure; login/logout; baseline role membership and role middleware; facility CRUD; patient registration/list/search/profile/edit; draft encounter creation; encounter signing/locking; audit event persistence; basic database-driven dashboard.

Not implemented: the remaining specialist workflows (nursing charting, pharmacy inventory/dispensing, LIS, ANC/MCH, immunisation schedules, emergency triage, referrals, appointments/queues, finance/general ledger, HR, inventory, surveillance, document management, full performance management); granular permission editor; MFA; password reset UI; patient duplicate matching beyond search; amendment workflow; clinical observations/vitals; clinical protocol engine; validated EWS/CDSS; AI model registry/predictions; PWA/offline sync; FHIR/ICD/LOINC/DHIS2 integrations; PDF/Excel exports; complete test suite; production hardening. No clinical thresholds or AI outputs are fabricated. The database dashboard only reports data that exists in the implemented tables.

Before real-world clinical use, complete clinical governance, security/privacy assessment, independent code review, comprehensive testing, data migration planning and professional Nigerian clinical protocol approval.


Milestone 2 source additions: appointment scheduling/status management, encounter observation entry, transfer request/review, and append-only signed-encounter amendment requests. These are not yet backed by executed integration tests. Transfer approval is a tracked authorisation decision only; it deliberately does not silently rewrite the patient's originating registration facility. Destination-side longitudinal access still needs a dedicated consented access-grant model and policy tests.

Approved transfers now grant destination-facility patient registry/profile visibility through an explicit query scope; the originating facility remains the registration facility. Cross-facility record access remains limited to approved transfer relationships and elevated LCDA roles, but requires formal privacy/consent review and dedicated access-policy tests before production.


Milestone 3 source additions: pharmacy stock/prescription/dispensing, laboratory request/result/verification, maternal/ANC records, child health/immunisation administration, emergency triage and referral workflows. These have not been run against MySQL or covered by executed integration tests. The pharmacy does not yet enforce a formulary, allergy/interaction checking or pharmacist clinical review. Lab critical values are staff-marked and do not trigger an independently validated alert service. Maternal risk and triage priority are staff-entered, not algorithmically assessed. Immunisation entries are recordkeeping only; no national schedule engine is claimed.


Milestone 4 source additions: inventory and supplier records, staff directory/attendance/leave requests, private document uploads, surveillance notifications/review, facility indicator entry, invoices/payments and double-entry manual journals. These remain unverified against a live MySQL database. Full procurement, AP supplier bill workflow, payroll, leave approval, document retention/classification governance, bank reconciliation, tax rules, budgets, period close, financial statements and statutory reporting are not yet implemented. Facility indicator values are manually submitted and are not automatically certified performance metrics.


Milestone 5 source additions: executive command centre, configurable clinician-approved alert rules, manual observation-rule evaluation, alert acknowledgement/resolution, AI model/version registry, validation metadata, fairness/subgroup and calibration record fields, AI incident reporting and prediction human-review endpoint. No trained or deployed AI model, prediction generation, automated deterioration score, validated adult/paediatric/obstetric scoring, model drift detection or explainability engine is supplied. Clinical rules must be formally approved and independently clinically validated before activation. Dashboard metrics only cover the selected implemented tables and must not be interpreted as complete LCDA public-health statistics.


Milestone 6 source additions: limited read-only FHIR R4 facade (Patient and Encounter only), terminology mapping table/search (no terminology dataset bundled), DHIS2 dataValueSet preview/optional outbound adapter, PWA static asset shell, IndexedDB inventory stocktake queue and idempotent conflict-aware synchronisation. This is not full FHIR conformance or a live DHIS2 integration until external mappings, endpoint configuration, credentials and conformance tests are supplied. Offline queue is intentionally restricted to inventory stocktakes and does not cache patient or clinical information. Browser storage is not a secure clinical repository. No background sync guarantee is assumed; the app retries when connectivity returns while the signed-in page is open.


Milestone 6 interoperability/offline source: limited read-only FHIR R4 facade for Patient and Encounter; local ICD-10/LOINC mapping table with no bundled code sets; DHIS2 export adapter requiring validated UIDs and credentials; installable PWA shell; IndexedDB queue for inventory stocktake only; server idempotency and stale-snapshot conflict records. This does not constitute complete HL7 FHIR conformance or an operational DHIS2 deployment. The browser does not cache patient records or clinical notes. Offline operations require a user session to synchronise and are not guaranteed to run in the background. No browser security or penetration test has been performed.


Milestone 6 interoperability/offline source: limited read-only FHIR R4 facade for Patient and Encounter; local ICD-10/LOINC mapping table with no bundled code sets; DHIS2 export adapter requiring validated UIDs and credentials; installable PWA shell; IndexedDB queue for inventory stocktake only; server idempotency and stale-snapshot conflict records. This does not constitute complete HL7 FHIR conformance or an operational DHIS2 deployment. The browser does not cache patient records or clinical notes. Offline operations require a user session to synchronise and are not guaranteed to run in the background. No browser security or penetration test has been performed.


Additional security-hardening source includes user account administration, restricted role assignment, first-login password change enforcement and audit-log viewing. MFA is still not implemented; password reset and account recovery flows need a configured mail service; role/permission granularity remains role-based rather than a complete permission matrix. Audit logs are stored in the application database and require production-grade append-only protection, restricted DBA access and external log retention controls.


Phase 8 adds source-level access-control hardening, but it is not a substitute for an independently reviewed permission matrix or penetration test. Some operational role policies still need LCDA stakeholder confirmation. MFA, secure account recovery, email verification, device/session management, tamper-evident audit export and automated security monitoring remain outstanding.


Phase 11 review: the custom duplicate personal-access-token migration has been removed; Sanctum's package migration must be present after Composer package discovery. Patient and Facility models now use SoftDeletes to align with schema. No migration execution or runtime test has been possible in the current environment.


Phase 14 adds procurement, supplier bill/AP recording, basic payroll, leave approval, manual bank reconciliation, patient consent events, privacy request tracking and records retention review. These are basic administrative workflows, not complete procurement/ERP/payroll/bank-feed or legal-compliance systems. Payroll statutory calculations are not implemented. No automatic patient-record destruction occurs. Full financial accounting integration, three-way matching, budget controls, tax and statutory payroll validation, bank feeds, and independent privacy/legal review remain required.


Phase 15 adds basic automated GL posting, budget commitment/expenditure, GRN and PO/GRN/bill total-level matching. This is not full statutory accounting: opening balances, period closing/locks, reversals, accruals, tax/withholding, complete payroll statutory rules and complete balance sheet/cash-flow statements remain unimplemented. Supplier invoice matching is total-value rather than line-by-line. Payroll expenditure is posted to staff costs but is not tied to a budget allocation. Runtime and migration execution remain pending.


Phase 16 adds period close/opening balance source workflows, government finance activity summaries, tender evaluation, procurement approval limits, supplier scorecards, data quality issue tracking and audit CSV export. Financial statements are not certified statutory IPSAS/IFRS statements; tendering is not a full e-procurement portal; data quality scans are not clinical decision support. All runtime tests, migrations, policy validation and independent audits remain outstanding.


Phase 17 adds rule-based public-health count signals and role-based clinical alert escalation queues. These are not epidemiological outbreak detection, automatic external notifications or clinical triage engines. Maternal/child/immunisation metrics are recorded activity counts, not coverage rates. AI monitoring metrics are manually entered, not automatically computed or independently validated. Thresholds and clinical protocols require professional approval. Runtime testing remains pending.


Phase 18 adds DHIS2 outbox queuing with manual HTTPS dispatch, limited read-only FHIR R4 resources, configured-rule immunisation due lists, maternal follow-up tasks and opt-in-gated SMS reminder queue. DHIS2 dispatch is not a background worker and requires target import verification. FHIR is not full profile conformance. No immunisation schedule defaults are seeded. SMS is not sent; no gateway is configured. All migration, PHPUnit, external integration and delivery tests remain pending.


Phase 19 adds lockfile-driven Docker build, queue and scheduler containers, database queue tables, API throttling, staging deployment script, encrypted backup/restore scripts and operational runbook. `composer.lock` remains absent and Docker is unavailable in the build environment, so image/container runtime was not built or tested. Queue worker is not yet wired to automatically dispatch SMS or DHIS2 outboxes. External log aggregation, WAF, TLS, secret manager, off-site immutable backups, restore drills and independent security review remain operational requirements.


Phase 20 establishes an acceptance test harness and execution matrix. The PHPUnit base class was missing and is now added. Feature tests are authored but not executed here. The current environment lacks Composer, Docker, PDO SQLite, PDO MySQL and a staging URL; all Laravel runtime, migration, end-to-end and external integration results remain pending.


Phase 20 automated acceptance remains pending. Static PHP/JS/shell/config/route/schema checks pass, but feature test source has not run. Do not treat 18 test files as passing tests. Full Composer, PHPUnit, MySQL migration, Docker, HTTP, external interoperability, SMS and restore acceptance require a provisioned staging environment.


Phase 21 adds release-candidate hardening, SQLite test connection, signed-only FHIR Encounter exposure, password-change session rotation and a fail-closed staging gate. No Composer lock, Docker build, PHPUnit, MySQL migration, HTTP staging test, penetration test or clinical/privacy sign-off has been completed in this environment.

\nPhase 22 staging deployment/runtime acceptance remains blocked in the current environment. Composer, composer.lock, vendor, Docker, MySQL, PDO SQLite/MySQL extensions, required PHP extensions, .env and staging URL are unavailable. A Docker testing profile and fail-closed staging runner are included, but migrations, PHPUnit, container runtime and HTTP smoke tests have not been executed.
