B. As receptionist, I want to capture demographic data of patient, so that I can save accurate patient data

[ramilsalihar]

Backend Acceptance Criteria:

API and Data Handling:

API Endpoints for Demographic Data:

Develop API endpoints enabling secure and efficient handling of patient demographic data entry and retrieval.

Data Sanitization and Validation:

Implement stringent data validation and sanitization methods on received demographic inputs to maintain data integrity.

Secure Data Storage:

Store patient demographic data securely in the database, adhering to privacy and security regulations (e.g., HIPAA).

Data Validation and Maintenance:

Consistency and Accuracy Checks:

Periodically validate stored demographic data for consistency and accuracy, ensuring alignment with entered information.

Backup and Recovery Procedures:

Implement backup mechanisms and recovery procedures to prevent data loss and maintain accessibility of patient demographic records.

Audit Trails and Logging:

Log access and modifications to patient demographic data for auditing and tracking purposes, ensuring accountability and security.

Frontend Acceptance Criteria:

User Interface for Demographic Data Entry:

Intuitive Data Entry Fields:

Design an intuitive user interface featuring fields for capturing demographic data of patients: name, surname, telephone number, address, date of birth.

Clean and Accessible Layout:

Arrange the interface layout for easy navigation and efficient entry of patient demographic information.

Real-time Data Validation:

Implement real-time validation to ensure accuracy and completeness of entered demographic details.

User Assistance and Guidance:

Include tooltips or hints guiding receptionists on the required information for each field.

Real-time Data Validation:

Mandatory Field Validation:

Ensure mandatory fields are clearly marked and validated in real-time to prompt completion before submission.

Data Format and Consistency Checks:

Validate data formats (e.g., date of birth) and ensure consistency across entered demographic details.

Error Handling and Feedback:

Provide immediate feedback with clear error messages if there are discrepancies or missing essential information.

ID	Field Name	Data Type	Status
1	name	String	Required
2	surname	String	Required
3	telephone number	int	Required
4	address	String	Required
5	date of birth	String	Required
6	gender	String	Required
7	marital status	String	Required
8	emergency contact	String	Optional

[oneku16]

which fields can be changed after registration? for example: fitst_name last_name phone_number ... please specify @aydanuwa @lulanovl