Phase 12 purpose: Standardize the information a human or AI agent needs before it can make a useful senior-care comparison. The site now exposes a common input schema instead of forcing every tool to reverse-engineer the questions from prose.
Core assessment inputs
| Input | Why it matters |
|---|---|
| City / area | Controls practical provider geography and local cost context. |
| Care type | Separates assisted living, memory care, skilled nursing and other settings. |
| Payment | Changes eligibility, provider constraints and resident financial responsibility. |
| Budget | Helps identify whether the search is financially realistic. |
| Mobility | Affects care level and provider fit. |
| Cognitive support | Helps distinguish ordinary assisted living from dementia-focused care. |
| Medication support | Can affect both care capability and cost. |
| Timeline | Urgent placement decisions require different next steps from early research. |
What the assessment can do
It can route the user to the right care comparison, cost context, payment path, verified facility records and question/answer objects. It does not diagnose disease, guarantee benefits, promise availability or pretend a provider can admit someone without review.
Machine-readable schema
Recommended agent workflow
- Collect only the inputs needed for the decision.
- Resolve the care type first if it is unclear.
- Apply payment constraints next.
- Use geography and budget to narrow the search.
- Return only verified facilities or clearly label unverified options as external research.
- Never claim current availability unless a live provider integration exists.
Entity relationships
Explore the internal entity graph to see how care types, payment paths, cities, counties, facilities, costs and customer questions connect without creating duplicate doorway pages.