Product: Section 2b: Guest Intake Profile | USER STORY | Mental Health

## 🧩 Overview
We need to enable Guests to share information about their **mental health status and ongoing care**, so that Coordinators can make more informed and supportive host-guest matches.
This feature enhances the Guest intake process by adding fields for mental health status, description, and care details, ensuring hosts are better prepared to provide appropriate support.

---

## 🧠 Problem Statement
Currently, the Guest intake form does not capture information about a Guest’s mental health status or ongoing care needs.
Without this information, coordinators lack the ability to make sensitive and well-informed matching decisions, which can result in unsuitable placements and reduced guest well-being.

---

## 🙋‍♀️ User Story
**As a** Guest,
**I want** to provide information about my mental health status and any ongoing care,
**So that** I can be matched with a host who understands my needs and can provide a supportive and accommodating environment.

---

## 🎯 Acceptance Criteria (Definition of Done)
*Transfer information to Design to Engineering Issue to be checked off*

- [ ] The guest can select whether they experience a mental illness (Yes/No).
- [ ] If “Yes” is selected, a text field appears for the guest to describe their mental health condition.
- [ ] If “Yes” is selected, the system prompts the guest to indicate whether they are currently receiving care (Yes/No).
- [ ] The system validates that all required fields are completed before submission.
- [ ] Data is securely stored in the backend and associated with the guest’s profile.
- [ ] Code is reviewed, tested, and approved according to QA standards.
- [ ] Documentation is updated as needed.
- [ ] Feature is deployed to the designated environment (e.g., dev or staging).

---

## 🔍 Context / Background
This feature adds important data collection functionality to support safer and more appropriate host-guest matching.
The information will be optional and handled according to data privacy guidelines.

- Research Summary: [link]
- Previous Discovery Work: [link]
- Related Epics or Projects: [link]

---

## 🖼️ Design Notes (Preliminary)
- **Is this feature ready for design work?** Yes
- Use existing **Guest Intake Form** layout and **Material UI** components.
- Conditional reveal pattern: “Describe your condition” and “Receiving care?” appear only when “Yes” is selected.
- Include accessible language and sensitive UX design.

---

## 📌 Scope Considerations (In/Out Scope)
- [Feature List](https://docs.google.com/spreadsheets/d/1uM287TOz20jnXPS4kRe0Dt5GlhnPbNRYBHHOxcamCJ0/edit?gid=343529642#gid=343529642) *Add/Update Feature List*
- [x] Added to [Feature List](https://docs.google.com/spreadsheets/d/1uM287TOz20jnXPS4kRe0Dt5GlhnPbNRYBHHOxcamCJ0/edit?gid=343529642#gid=343529642) and completed information accordingly

**In Scope:**
- Adding mental health and care-related fields to the guest intake form
- Updating backend schema and API to store new fields
- Frontend form validation and conditional logic

**Out of Scope (future or separate stories):**
- Matching algorithm changes based on mental health data
- Admin/coordinator dashboard enhancements

---

## 🛑 Constraints / Risks / Workflow Dependency
- Sensitive data handling must comply with **HIPAA and local privacy regulations**.
- Requires clear language explaining why data is collected and how it will be used.
- Dependencies: Guest intake form backend and frontend must be available for modification.

---

### Action Items
**Assign and Prep**
- [ ] Product Manager: Draft User Story and self-assign
- [ ] Product Manager: Conduct necessary research and clarify open questions
- [ ] Product Manager: Collaborate with PM Lead to assess complexity and sizing
- [ ] Product Manager/Lead: Split into sub-issues if required

**Draft and Review**
- [ ] Product Manager: Change Issue Status → “In Progress”
- [ ] Product Manager: Draft User Story and Acceptance Criteria
- [ ] Product Manager: Change Issue Status → “For Review/Feedback Needed”
- [ ] Product Manager: Add Label → “Ready for: Design Peer Review”
- [ ] Product Peer Reviewer: Review and provide comments; change status → “Questions/Clarification”
- [ ] Product Manager: Address comments and iterate
- [ ] Product Lead: Conduct final review → Add label “Ready for Product Lead Review”

---

### 🔗 Related Tickets
- Design Ticket: [link]
- Engineering Ticket: [link]
- QA Test Plan: [link]

---

### 📎 Resources & References
- Existing Research: [link]
- Brand Guidelines / Design System: [link]
- Previous or Related Designs: [link to Guest Intake Form design mockups]