Scribd
Upload
3 views2 pages

Python HiMS Project Question

The document outlines a user story for validating patient registration data in the HiMS software, emphasizing the need for accurate and complete patient records. It details acceptance criteria including mandatory fields, format validation, duplicate record checks, and real-time error messages. The business value highlights improvements in billing accuracy, patient safety, and compliance with healthcare standards.

Uploaded by

mr.sushant.official.002
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views2 pages

Python HiMS Project Question

The document outlines a user story for validating patient registration data in the HiMS software, emphasizing the need for accurate and complete patient records. It details acceptance criteria including mandatory fields, format validation, duplicate record checks, and real-time error messages. The business value highlights improvements in billing accuracy, patient safety, and compliance with healthcare standards.

Uploaded by

mr.sushant.official.002
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

**User Story: Patient Registration Data Validation in HiMS Software**

**Title:** Accurate Patient Details Validation During Registration in HiMS

**As a** front desk executive / registration staff,


**I want** the HiMS software to validate patient details while entering information,
**So that** patient records are accurate, complete, and error-free for treatment, billing, and
reporting.

### Acceptance Criteria:

1. **Mandatory Fields Validation**

* System should require essential fields like:

* Patient Name
* Age / Date of Birth
* Gender
* Mobile Number
* Address
* Unique Patient ID / Aadhaar (if applicable)

2. **Format Validation**

* Mobile number must be exactly 10 digits


* Email (if entered) must follow valid email format
* Date of Birth cannot be a future date
* Age should auto-calculate from DOB

3. **Duplicate Record Check**

* System should alert if the same patient already exists based on:

* Mobile number
* Aadhaar number
* Name + DOB combination

4. **Dropdown / Controlled Inputs**

* Gender, Blood Group, Marital Status, and State should be selected from predefined lists
to avoid manual entry errors

5. **Real-Time Error Messages**

* Invalid or missing data should display clear messages (e.g., “Please enter a valid mobile
number”)

6. **Data Security & Privacy**


* Sensitive fields should be securely stored
* Access to edit patient demographics should be role-based

7. **Save Restriction**

* Record cannot be submitted until all validation rules pass

### Business Value:

* Reduces duplicate patient records


* Improves billing and insurance accuracy
* Enhances patient safety through correct identification
* Supports compliance with healthcare data standards

### Example Scenario:

**Given** the registration staff is entering a new patient,


**When** an invalid mobile number or duplicate Aadhaar is entered,
**Then** the system should immediately notify the user and prevent submission until
corrected.

You might also like