Project

General

Profile

Actions

Gaps #92845

open

OPD > Registration > Incorrect “No Patient Record Found” Message When Searching for Merged (Secondary) MRN

Added by Nur'Ain Binti Karim 7 months ago. Updated 3 months ago.

Status:
Tested
Priority:
Critical
Category:
M OPD
Target version:
-
Start date:
10/04/2026
Due date:
% Done:

90%

Estimated time:
Dev Due date:
12/08/2026
Release date to QA:
13/08/2026
Issue released on:
Dev
Function:
Standard

Description

Issues Description :
- During the patient registration process, when a user enters a secondary MRN (Medical Record Number) that has already been merged with a primary MRN, the system currently does not provide any notification or guidance.

Step to reproduce
1.Login System
2.Navigate to > OPD
3.Click on Registration
4.Click on find the secondary's MRN patient.
5.Observe screen > When searching for a secondary (merged) MRN during registration, the system displays “No patient record found.”
There is no indication that the MRN has been previously merged with a primary MRN.
This may mislead users into thinking the record does not exist.

Expectation:
- When a secondary MRN is entered, the system should detect that the MRN has already been merged.
- Display a clear prompt or validation message such as: “This MRN has already been merged with XXXXX. Please use the primary MRN instead.”


Files

Actions #1

Updated by Nur'Ain Binti Karim 7 months ago

  • Category set to M OPD
Actions #2

Updated by Nur'Ain Binti Karim 7 months ago

  • Description updated (diff)
Actions #3

Updated by Kierthini Nethi 4 months ago

  • Issue released on Dev added
  • Issue released on deleted (NA)
  • Function Standard added
Actions #4

Updated by Daniyal Ansari 4 months ago

  • Assignee changed from Daniyal Ansari to Rohit Jadhav
  • Dev Due date set to 03/08/2026
Actions #5

Updated by Rohit Jadhav 4 months ago

  • Assignee changed from Rohit Jadhav to Prathmesh Sargar
Actions #6

Updated by Daniyal Ansari 4 months ago

  • Dev Due date changed from 03/08/2026 to 05/08/2026
Actions #7

Updated by Daniyal Ansari 3 months ago

  • Dev Due date changed from 05/08/2026 to 12/08/2026
  • Release date to QA set to 13/08/2026
Actions #8

Updated by Prathmesh Sargar 3 months ago

From backend Side it was fix now getting proper message like wise

Actions #9

Updated by Prathmesh Sargar 3 months ago

  • Assignee changed from Prathmesh Sargar to Shweta Sandip Waghmare

Please do needful changes from frontend side

Actions #10

Updated by Shweta Sandip Waghmare 3 months ago

  • Assignee changed from Shweta Sandip Waghmare to Tejashri Tanaji Jagtap
Actions #11

Updated by Tejashri Tanaji Jagtap 3 months ago

  • Status changed from New to Assigned
Actions #12

Updated by Tejashri Tanaji Jagtap 3 months ago

  • Status changed from Assigned to Coded
Actions #13

Updated by Jayadeep kasukurthi 3 months ago

  • Status changed from Coded to QA
Actions #14

Updated by Jayadeep kasukurthi 3 months ago

  • Assignee changed from Tejashri Tanaji Jagtap to Mangesh Pangrekar
Actions #15

Updated by Manisha Kadam 3 months ago

Working now as per description
Display a clear prompt or validation message such as: “This MRN has already been merged with XXXXX. Please use the primary MRN instead.” - PASS

See attached video

Actions

Also available in: Atom PDF