INDUSTRY FIELD GUIDE
Continuing care retirement community transition data for AI
A retirement community can provide several levels of service.
NAICS 623311 · Continuing Care Retirement Communities
A retirement community can provide several levels of service. A proposal, reservation and effective transfer record may appear in the same file. Medicare provides long-term care information and the Census classification identifies continuing care retirement communities separately. Medicare long-term care overview · U.S. Census 2022 NAICS manual
Invent two levels using abstract labels and a mock unit change. Include a tentative reservation for one date and a signed transfer effective later. Ask which date the documents support and whether a planned service started. Score effective date, authorized sign-off and incomplete evidence independently.
Use original forms and generic locations. Exclude actual resident information, contracts, care needs, payment records and facility access details. Keep care and eligibility decisions with qualified staff.
Describe a fictional service transition sample
Original Fiund exercise
A tentative reservation date is different from an effective service transfer
Two abstract service levels and generic location aliases form an invented administrative timeline. No resident, care need, contract, payment or access detail is represented.
| Record | Source | What it records |
|---|---|---|
| RT1 | Proposal and reservation | Fictional record R proposes level L2; tentative reservation at location B starts day 10. Proposal unsigned. |
| RT2 | Signed mock transfer | R transfer from L1/location A to L2/location B effective day 14. Explicitly supersedes proposed start date. |
| RT3 | Service event log | No separate L2 service-start event or completion record supplied. Requested as-of date day 12. |
Question for the model
What transition date is authorized by the supplied document, and does the day-12 packet establish that L2 service has started?
Show the reference answer and checks
RT2 documents an effective transfer date of day 14, replacing RT1's tentative day-10 reservation date. For day 12, that transfer is still future-dated, and RT3 supplies no separate L2 start event. Preserve the signed future transition and lack of current start evidence rather than treat a reserved location or proposal as completed service. The fixture does not evaluate care needs, eligibility or an actual resident's placement.
- Using a tentative reservation as the actual service-transfer date.
- Inferring service commencement from a future signed transfer without a matching event.
Fields to preserve
- Record alias and abstract levels
- Defines the transition.
- Reservation versus effective date
- Separates planned stages.
- Authorization and start-event evidence
- Supports the limited status summary.
Test another case
Move the review date to day 15 but retain no start event. Require the transfer's effective date to be recognized while actual service occurrence remains unverified.
Use original forms and generic places. Exclude residents, care records, contracts and facility access; qualified staff retain care and eligibility decisions.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.