d_s_bisht/devsofttech_hms_ci4
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
9d568463f1
devsofttech_hms_ci4/ABDM_M2_TEST_SESSION_HANDOVER.md

7.4 KiB
Raw Blame History

ABDM M2 Test Session Handover & Verification Guide

Date: 2026-09-30
Branch: main
Latest Commits:

  • 6bd2430 — fix(abdm-m1): sanitize otp error text, hide bridge request id, add beneficiary name to consent
  • a33b376 — feat(abdm-m2): add HIP link modal and care context discovery on patient registration
  • ccd5909 — docs: remove technical URLs, database fields and developer codes from user help guide
  • f7c3052 — feat(abdm-m2): enable care context discovery and direct linking for invoice records
    Live Environment: demo.e-atria.net (10.8.0.1 / /var/www/html/hms_etria)

1. Executive Summary

This session verified and configured end-to-end readiness for ABDM Milestone 2 (M2) testing across all supported Health Information (HI) types:

  1. OPConsultRecord (OPD Consultations & Prescriptions)
  2. DiagnosticReportRecord (Laboratory & Radiology Reports)
  3. DischargeSummaryRecord (IPD Discharge Summaries)
  4. ImmunizationRecord (Vaccination Records)
  5. InvoiceRecord (OPD, IPD, and General Charges Invoices)

All features have been unit tested (57/57 tests passing, 495 assertions), committed, pushed to origin/main, and deployed live to https://demo.e-atria.net/.

2. Key Changes Implemented

A. Patient Registration & ABHA Management Integration

  • File: Patient_V.php
    • Included partials/abdm_hip_link_modal.php on the Patient Registration view so the HIP link modal can be opened from registration screens.
    • Added hidden input_abha_address to form.form1 so ABHA addresses are seamlessly submitted and saved to patient_master.
    • Added a dedicated 4th card under Patient Management → ABHA Management tab:
      • Link Records to ABHA (HIP) button (openAbdmHipLinkModal())
      • Send Deep Link SMS button (openAbdmHipSmsModal())

B. Instant Care Context Discovery for New Patients

  • File: AbdmGateway.php
    • Updated findCareContextsForPatient() to query opd_master in addition to opd_prescription.
    • Previously, a care context was only discoverable after a doctor wrote a prescription or finalized a lab report.
    • Now, as soon as an OPD consultation appointment / slip is created at the reception desk, the visit is instantly discoverable and linkable as OPD-{patientId}-S{opdId}-{YYYYMMDD} with title OPConsultRecord - Dr. {DoctorName} - {Date}.
    • Added unit test testDiscoversOpdMasterVisitWhenPrescriptionNotCreated in CareContextDiscoveryTest.php.

C. 14-Digit ABHA Number & @sbx Address Dual Resolution

  • File: AbdmGateway.php
    • Enhanced hipPatientCareContexts() so that if an ABHA address field contains a 14-digit numeric ABHA ID (or formatted XX-XXXX-XXXX-XXXX), it queries both abha_address and abha_id in patient_master.

D. Invoice Care Context Discovery & Direct Linking

  • Files: AbdmTaskBoard.php, task_board.php, AbdmGateway.php, abdm_hip_link_modal.php
    • Integrated HI Type: InvoiceRecord care contexts on the ABDM Work Task Board Invoice panel.
    • Linked patient_master to retrieve abha_id / abha_address across OPD, IPD, and Charges invoices.
    • Auto-generated standard care contexts: INVOICE-OPD-{billId}-{date}, INVOICE-CHG-{billId}-{date}, INVOICE-IPD-{billId}-{date}.
    • Enabled the Link Context button on invoice rows with complete task context (task_type: 'invoice_publish', source: invoiceSource, entity_id: billId).
    • Added NRCES-compliant Invoice FHIR Bundle bridge push (share_invoice_source_bundle) directly upon linking from the modal.
    • Added dynamic DOM updates on the Task Board table row to reflect LINKED status, update badges, and show care context references immediately upon link confirmation.
    • Added unit test testDiscoversInvoiceCareContextWhenInvoiceTaskRequested in CareContextDiscoveryTest.php.

E. M1 Feedback Updates (Retained & Verified)

  • Normalized invalid OTP error alerts strictly to "Incorrect OTP" (or attempts exceeded message).
  • Removed internal Bridge Request ID: REQ-... from user-facing screens.
  • Added healthcare worker declaration and beneficiary name consent input field before Aadhaar OTP dispatch.

3. M2 Testing Step-by-Step Walkthrough

Step 1: Register Patient & Create Visit Slip

  1. Open Patient Management → New Person on https://demo.e-atria.net/.
  2. Register patient with Mobile Number, Name, Gender, DOB.
  3. On patient record screen, click Appointment For OPD and assign a doctor to generate the OPD slip.
  4. Care context OPD-{patientId}-S{opdId}-{YYYYMMDD} is now live and linkable.

Step 2: Test HIP-Initiated Linking (Method 4 Demographic Auth)

  1. In patient profile or ABHA Management, click Link Records to ABHA (HIP) (or click Link Context on any Task Board card).
  2. Enter the patient's ABHA address (e.g., user@sbx).
  3. Patient demographics (Full Name, Gender, YOB) are pre-filled/verified.
  4. Select the care contexts (OPD consultation, invoice, lab/radiology, discharge summary).
  5. Click Link Selected Records (Demographic Auth).
  6. The gateway returns a JWT Link Token and links the care context to the ABHA account.

Step 3: Test Deep Link SMS (sms/notify2)

  1. On the same modal, switch to Deep Link SMS (sms/notify2) tab.
  2. Confirm the 10-digit mobile number and click Send Deep Link SMS.
  3. ABDM dispatches an SMS with an app deep link to the patient's mobile device.

Step 4: Test User-Initiated Discovery & Linking (from ABHA PHR App)

  1. Open the ABDM Sandbox ABHA / PHR app on a smartphone.
  2. Search for the facility: Dev Softtech (Facility ID: IN0510000871).
  3. Search by patient mobile number or ABHA address.
  4. Select the discovered care contexts and request OTP.
  5. Verify OTP to confirm the linking.

Step 5: Test Health Record View (FHIR Bundles in PHR App)

  1. Doctor submits clinical notes/prescription in OPD Prescription editor (or saves findings in Radiology Report Editor, or prints/generates an Invoice).
  2. In the PHR app, tap on the linked hospital and tap Fetch Records / Pull Records.
  3. The HMS generates and transfers the encrypted FHIR bundle (OPConsultRecord, DiagnosticReportRecord, or InvoiceRecord).
  4. Patient views findings, medications, and invoices directly in the PHR app.

4. Test Suite & Verification Results

# Full PHPUnit Suite Execution
php vendor/phpunit/phpunit/phpunit --no-coverage

# Result
OK (57 tests, 495 assertions)
Tests: 57, Assertions: 495, Failures: 0. 100% PASS.

5. Deployment Commands Reference

# Windows deployment to remote server (10.8.0.1)
& "C:\Program Files\PuTTY\plink.exe" -ssh -batch -pw "bishT@9720958717H" root@10.8.0.1 "cd /var/www/html/hms_etria && git pull origin main && php spark cache:clear"