0% found this document useful (0 votes)
9 views8 pages

Field Validation Low Level Requirement

The document outlines validation rules for various patient admission fields including First Name, Date of Birth, Gender, Aadhaar Number, ABHA Number, Allergies, Address, Email, Emergency Contact Name, Emergency Contact Phone, and Insurance Policy Number. Each field has specific requirements regarding mandatory status, character restrictions, length restrictions, and error handling protocols. The guidelines aim to ensure data accuracy and consistency during patient admissions.

Uploaded by

kalamage.s2t
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views8 pages

Field Validation Low Level Requirement

The document outlines validation rules for various patient admission fields including First Name, Date of Birth, Gender, Aadhaar Number, ABHA Number, Allergies, Address, Email, Emergency Contact Name, Emergency Contact Phone, and Insurance Policy Number. Each field has specific requirements regarding mandatory status, character restrictions, length restrictions, and error handling protocols. The guidelines aim to ensure data accuracy and consistency during patient admissions.

Uploaded by

kalamage.s2t
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Admit Patient Screen

Field: First name, Last name

Validation Rules:

Mandatory: First name is a required field.


Character Restrictions:
It should contain only alphabetic characters (A-Z, a-z).
Optionally include hyphens (-), apostrophes ('), or spaces.
Length Restrictions:

 Minimum length of [X] characters (e.g., 2 characters).


 Maximum length of [X] characters (e.g., 50 characters).

Case Sensitivity: First name can be entered in uppercase, lowercase,


or a combination.
Special Character Restrictions: No special characters other than
hyphens, apostrophes, and spaces are allowed.
Error Handling:

 Display a clear error message if the first name field is empty or


invalid.
 Provide specific feedback on the validation error (e.g., "First
name must contain only letters").

Field: DOB

Validation Rules:

Mandatory: Date of birth is a required field.

Format:

 Must be in a specific format (e.g., MM/DD/YYYY, DD/MM/YYYY,


YYYY-MM-DD).
 Ensure consistent format throughout the system.

Date Range:
 Must be a past date.
 Should fall within a reasonable age range (e.g., 0 to 120 years
old).

Leap Year Compatibility: Validate February 29th for leap years.


Error Handling:

 Display clear error messages for invalid date formats, future


dates, or dates outside the allowed range.
 Provide specific feedback on the validation error (e.g., "Invalid
date format", "Date cannot be in the future").

Field: Gender

Validation Rules

 Mandatory: Gender is a required field.


 Allowed Values:
o Define a list of acceptable gender values (e.g., Male,
Female, Other, Prefer Not to Say).
o Consider incorporating additional gender options to be
inclusive.
 Case Sensitivity: Gender values can be entered in uppercase,
lowercase, or a combination of both (depending on your
system's requirements).
 Error Handling:
o Display a clear error message if the gender field is empty
or the selected value is not valid.
o Provide specific feedback on the validation error (e.g.,
"Please select a valid gender option").

Field: Aadhaar Number Validation

Validation Rules

 Mandatory: Aadhaar number is a required field in relevant


forms.
 Length: Exactly 12 digits.
 Data Type: Numeric only (0-9).
 Check Digit: While the exact check digit algorithm is not
publicly disclosed, it's essential to implement a robust
validation mechanism to verify the number's authenticity.
 Error Handling:
o Display clear error messages for invalid Aadhaar numbers
(e.g., incorrect length, non-numeric characters, invalid
check digit).
o Provide guidance on the correct format of the Aadhaar
number.

Field: ABHA Number

Validation Rules

Mandatory: ABHA number is a required field in relevant forms.


Length: Exactly 14 digits.
Data Type: Numeric only (0-9).
Check Digit: While the specific check digit algorithm for ABHA
numbers might not be publicly disclosed, it's essential to implement
a robust validation mechanism to verify the number's authenticity.
Error Handling:

 Display clear error messages for invalid ABHA numbers (e.g.,


incorrect length, non-numeric characters, invalid check digit).
 Provide guidance on the correct format of the ABHA number.

Field : Allergies

Validation Rules

 Standardized Terminology: Use standardized terminology for


allergens (e.g., SNOMED CT, ICD-10) to ensure consistency and
data interoperability.
 Allergen Specificity: Encourage users to provide as much detail
as possible about the allergen (e.g., specific type of pollen, food
allergen).
 Cross-Sensitivity: Consider allowing for the input of cross-
reactive allergens (e.g., latex allergy may also include avocado
allergy).

Error Handling:

 Invalid Allergens: Provide error messages for invalid or non-


existent allergens.
 Missing Information: Prompt the user to provide additional
details if the allergy information is incomplete.

Field: Address

Validation Rules

Mandatory Fields:

 Address Line 1, City, State/Province, and ZIP/Postal Code are


typically mandatory.
 Address Line 2 and Country might be optional depending on
specific requirements.

Data Format Validation:

 Address Line 1 & 2:

Can contain alphanumeric characters, spaces, hyphens, periods, and


other address-specific characters (e.g., apartment number, floor,
building name).

Maximum length should be defined based on system requirements.

City:

Can contain alphanumeric characters, spaces, and hyphens.


Maximum length should be defined based on system requirements.

State/Province:

Can be alphanumeric or use standard state/province abbreviations.

Validate against a list of valid states/provinces.

ZIP/Postal Code:

Numeric format (with potential for dashes or spaces depending on


country-specific standards).

Validate against ZIP/postal code format for the specified country.

Country:

Use a standardized country code (e.g., ISO 3166-1 alpha-2) or a list of


valid countries.

Error Handling:

Provide clear error messages for invalid address components (e.g.,


incorrect ZIP code format, missing city).

Field: Email

Validation Rules

Mandatory: Email address is a required field.

Format:

 Must adhere to the standard format: [email protected].


 Should contain an "@" symbol separating the username and
domain.
 The domain part must contain at least one dot (.).

Character Restrictions:
 Allowed characters include letters (a-z, A-Z), numbers (0-9),
periods (.), underscores (_), and hyphens (-).
 No spaces or special characters are allowed.

Length Restrictions:

 Maximum length of the email address should be defined (e.g.,


255 characters).

Error Handling:

 Display a clear error message for invalid email addresses.


 Provide specific feedback on the validation error (e.g., "Invalid
email format").

Field: Emergency Contact Name Validation

Validation Rules

 Mandatory: Emergency contact name is a required field.


 Character Restrictions:
o Should contain alphabetic characters (A-Z, a-z).
o Can optionally include hyphens (-), apostrophes ('),
periods (.), and spaces.
 Length Restrictions:
o Minimum length of [X] characters (e.g., 2 characters).
o Maximum length of [X] characters (e.g., 50 characters).
 Case Sensitivity: Emergency contact name can be entered in
uppercase, lowercase, or a combination of both.
 Error Handling:
o Display a clear error message if the emergency contact
name field is empty or invalid.
o Provide specific feedback on the validation error (e.g.,
"Invalid characters in emergency contact name").
Field: Emergency Contact Phone

Validation Rules

 Mandatory: Emergency contact phone number is a required


field.
 Format:
o Allow for various phone number formats (e.g., (123) 456-
7890, 123-456-7890, 1234567890).
o Consider allowing for international phone numbers (with
country codes).
 Length:
o Define a reasonable range for phone number lengths
(e.g., minimum 7 digits, maximum 15 digits).
 Character Restrictions:
o Allow only numbers (0-9), hyphens (-), parentheses (), and
plus signs (+).
 Error Handling:
o Display clear error messages for invalid phone number
formats (e.g., incorrect length, invalid characters).
o Guide the acceptable phone number format .

Field: Insurance Policy Number

Validation Rules:

 Mandatory: Required field.


 Data Type: Alphanumeric or numeric (depending on insurance
provider).
 Length: Minimum [X] characters, maximum [X] characters.
 Format: May require specific format (e.g., check digits, alpha-
numeric patterns).
 Error Handling:
o Display a clear error message if the field is empty or
invalid.
o Provide guidance on the correct format if applicable.

You might also like