Session 9: Patient Management - List Page

Date: 2026-06-17 Module: Clinic App - Patient Management (Section 1: Patient List) URL: https://practice-stg-new.kulcare.com/cms/patients Test Plan: test-plans/clinic-app/patient-management.md Status: ✅ Complete

📊 Test Results SummaryCopy Anchor Link

🐛 Bugs FoundCopy Anchor Link

🔍 Detailed Test ResultsCopy Anchor Link

1.1 List Display (5/5 Passed ✅)Copy Anchor Link

1.2 Search & Filter (4/6 Passed, 2 Failed)Copy Anchor Link

1.3 Date Range Filter (0/2 Passed)Copy Anchor Link

1.4 Pagination (5/5 Passed ✅)Copy Anchor Link

1.5 Table Actions (2/3 Passed, 1 Failed)Copy Anchor Link

1.6 Header Actions (3/4 Passed, 1 Failed)Copy Anchor Link

1.7 Table Density (2/2 Passed ✅)Copy Anchor Link

🐛 Bug DetailsCopy Anchor Link

Bug #31: Full Name Search with Space Returns No Results (Reconfirmed)Copy Anchor Link

Description: Previously found in federated search (Session 08). Reconfirmed on patient list search. Searching by partial name ("moh", "mohit") works, but adding a space ("mohit goyal") returns no results.

Root Cause: Search scope uses first_name ILIKE '%q%' OR last_name ILIKE '%q%' — splitting on space means "mohit goyal" becomes two separate LIKE clauses that don't match any single column.

Impact: Users who type full names (common behavior) get no results even when patient exists.

Bug #35: Date Range Filter Not Wired to API (Reconfirmed)Copy Anchor Link

Description: Previously documented in Session 08. Reconfirmed — date filter UI exists on the patient list but birth_date_from and birth_date_to params are not included in the API query params sent by PatientsPage.tsx.

🆕 Bug #36: Phone Search Returns No ResultsCopy Anchor Link

Description: Searching by phone number on the patient list returns no results. The patient list search API (GET /clinical/patients?search=) only queries first_name and last_name — phone_number is not in the search scope.

API Evidence:

curl 'https://api-stg.kulcare.com/clinical/patients?search=988&page=1&per_page=10' \
  -H 'Authorization: Bearer <token>'
# Returns: empty results, even though patients with phone containing "988" exist

Root Cause: Clinical::PatientsController#index search scope:

# Current (suspected):
scope.where('first_name ILIKE :q OR last_name ILIKE :q', q: "%#{search}%")

# Should be:
scope.where('first_name ILIKE :q OR last_name ILIKE :q OR phone_number ILIKE :q', q: "%#{search}%")

Impact: Staff/doctors cannot find patients by phone number — the most common search method in clinics.

🆕 Bug #37: Export Report API Fails — EFS Permission DeniedCopy Anchor Link

Description: Patient export report (POST /clinical/patients/generate_report) fails on staging due to filesystem permission error. Ruby's Dir.mkdir cannot create the EFS directory.

API Response (422):

{
  "data": null,
  "error": {
    "code": "validation_failed",
    "message": "Permission denied @ dir_s_mkdir - /opt/kulcare-efs-stg/patient_reports_staging",
    "details": [{
      "field": "base",
      "message": "Permission denied @ dir_s_mkdir - /opt/kulcare-efs-stg/patient_reports_staging"
    }]
  }
}

Root Cause: Staging infrastructure — /opt/kulcare-efs-stg/patient_reports_staging either not mounted or Rails process (deploy user) lacks write permissions. This is not a code bug — the API flow is correct, the filesystem is misconfigured only on staging.

Fix (DevOps):

# On staging Rails server:
sudo mkdir -p /opt/kulcare-efs-stg/patient_reports_staging
sudo chown deploy:deploy /opt/kulcare-efs-stg/patient_reports_staging

Code-level hardening (optional):

# Add fallback to /tmp if EFS unavailable
def report_dir
  dir = Rails.root.join('tmp', 'patient_reports')
  FileUtils.mkdir_p(dir)
  dir
rescue Errno::EACCES
  Rails.logger.warn("EFS unavailable, falling back to /tmp")
  dir = Rails.root.join('tmp', 'patient_reports_fallback')
  FileUtils.mkdir_p(dir)
  dir
end

✅ Confirmed Working FeaturesCopy Anchor Link

📋 Pending Tests (Section 1)Copy Anchor Link

📝 NotesCopy Anchor Link

1. Upload flow exists in code — PatientUploadModal is imported and wired in PatientsPage.tsx (line 47, 529-534). The upload button may be in the header actions area.
2. Bug #31 and #36 share a root cause — the patient list search scope is not comprehensive. Both name-with-space and phone search fail because the query doesn't handle multi-word names or phone columns.
3. Bug #37 is staging-only — the export API code is correct; it's a deployment/filesystem issue. Production may not be affected.

Session Status: ✅ Complete Last Updated: 2026-06-17 Next: Phase 2 — Patient View Page (VIEW-01 to VIEW-51)

🆕 Bug #38: Cross-Clinic Patient Flow Incomplete — No Facility Record CreatedCopy Anchor Link

Description: Cross-clinic flow is incomplete. When a patient from Clinic A appears in Clinic B's list:

1. View (👁️) broken: patient_facility_id: null → /cms/patient/{id}/null
2. Appointment booked without facility context: FindOrCreateService returns patient_facility: nil for cross-clinic patients. Appointment model accepts it as optional, so booking "succeeds" but has no facility link.
3. Edit (✏️) works: uses patient.id only

Root Cause: No auto-registration — Clinical::PatientFacility record is never created for the current clinic when a cross-clinic patient is accessed.

Recommended Fix: Auto-create facility record in FindOrCreateService#find_by_id when find_patient_facility_by_patient returns nil. Standard healthcare pattern: providing care = establishing relationship.