via Elegante onboarding

First tenant through the automated onboarding pipeline. Yardi source, 4 communities.

StatusOnboarded, refreshing on its own

Live since2026-10-01

Residents223 (215 active)

SourceYardi (FHIR R4 US Core)

Done

Live Yardi data for all 4 communitiesProduction read access since 2026-09-30.
Loaded into FHIR, silver and the warehouseChecked against Yardi: nothing lost, nothing mixed up, no duplicates.
Resident profiles work in Careflows215 active residents, one row each. Profiles and the risk view open.
Residents are in base.dim_resident223 rows. The Yardi notebook fix (2026-10-05) also brought in 45 missing Integrated residents.
Refreshes by itself, and alerts on failureOne weekly job pulls from Yardi and loads (Saturday), warehouse on Sunday, risk view daily.
Occupancy and outcomes tables show the tenantSee the Tables & dashboards tab.

Not done yet

Census and stay tables MichaelFill on the 2026-10-06 refresh (10:30 to 11:00 UTC). Check them after that.
AVON patients, providers and staff EricAlso links each resident to their doctor in Careflows.

Progress

A. Access and setup complete

#	Step	Status	Note
A1	Yardi production read access	Done	Since 2026-09-30. 216 residents at the time, all 4 communities (`1-1`, `3-1`, `4-1`, `5-1`).
A2	Profile the API: resources, volumes, incremental fields	Done	See the Yardi API tab.
A3	Service lines	Done	AL and MC at all 4. No IL.

B. Platform Eric / Michael

#	Step	Status	Note
B1	Careflows tenants (Parties) and AVON medical centers	Done	4 of each, by Eric, 2026-09-21 (CC-1623).
B2	Blob provider and platform flows per community	Done	2026-10-01. `Complete_Pipeline` (warehouse, weekly) and `AI_Risk_Complete_Pipeline` (risk view, daily). The platform wrote all 8 Airflow DAGs.
B3	AVON patients, providers and staff	To do	Eric. Residents already reach Careflows through the automatic import, so this is about AVON users and doctor links.
B4	Organization address and primary contact	To do	Empty on all 4 tenants. Eric, CC-1623.

I. Ingestion and load Michael

#	Step	Status	Note
I1	Airbyte connection to Yardi PROD	Done	11 streams. Connector v6 retries the 5-minute token and server errors.
I2	Load into FHIR and silver (house Yardi transform)	Done	221,292 records at first load. Each community checked twice: silver equals FHIR, and Yardi equals silver.
I3	Delete the 834 old test-load duplicates	Done	2026-10-01. Every one reads back as gone, nothing pointed at them.
I4	Weekly schedule	Done	Yardi pull and load Saturday 17:00, warehouse Sunday 04:00 to 05:30 UTC (moved off Integrated's Saturday slot 2026-10-05), risk view daily 06:00 to 07:15 UTC.
I5	Chain the pull and the load, alert on failure	Done	2026-10-05. One Databricks job, Saturday 17:00 UTC: it starts the Yardi pull, waits, then loads. A failed or near-empty pull stops the job and sends the failure email. Test run green with new data. Airbyte no longer has its own clock.

D. Warehouse Michael

#	Step	Status	Note
D1	`public.dim_tenants` rows	Done	4 rows, active, start date 2026-10-01. Nothing writes this table automatically.
D2	Daily rows, med orders, move-ins	Done	`patient154__v2` through today, 0 duplicates. 5,732 med orders. Move-in on every moved-in resident.
D3	`base.dim_resident`	Done	2026-10-05: 223 rows. The Yardi notebook wrote an old staging table name. Fixed, backfilled once, then proven on all 4 weekly runs.
D4	`tenant_start_date` and `tenant_capacity`	Done	4 rows each. Beds 61, 194, 81, 64.
D5	Dashboard tables show the tenant	In progress	6 show today. About 7 more fill on the 2026-10-06 refresh. See the Tables & dashboards tab.
D6	`active` flag on residents	To do	Empty on every Yardi resident, Integrated too. Census still works, because it uses the room and move-in instead. Ankita, D2b.

E. Dashboards Michael

#	Step	Status	Note
E1	Customer sees only their own data	Done	Careflows adds the tenant filter itself when it opens a dashboard. No Superset rule needed.
E2	Dashboards render the tenant in Careflows	To do	Check after the 2026-10-06 refresh.

F. Close out Michael

#	Step	Status	Note
F1	Data Provider Map	Done	Operator links to this page.
F2	Mark the Yardi cell for via Elegante on the map	To do	One click.
F3	Reusable process	Done	Captured in the `cc-onboard-tenant` skill and its sub-skills.
F4	Decide `saas_rate_pmpm`	To do	Still empty on all 4.
F5	Confirm Tucson Mountains beds	To do	Yardi says 194 beds in 66 rooms. Ask the operator.
F6	Report the rock as 1 live tenant	To do

Outside this onboarding

Notes into a table. Yardi notes are pulled weekly into blob, but nothing reads them yet. Leaves now load into loa_metrics (2026-10-06).
Visit notes into Yardi. Proven on Yardi's TEST site (a vital 2026-09-27, a note 2026-10-02). PROD write is its own project, not part of onboarding.
Incidents and falls. Yardi's AdverseEvent holds staff-entered incidents but has no search. Our weekly reader walks the ids instead (tested on Yardi's sandbox) and starts the week via Elegante approves read on PROD.
Med Quality, falls, leaves, social engagement. Empty for every Yardi customer, Integrated too. Needs new Yardi feeds.
Tenant id on Yardi med passes. All Yardi rows in medication.source_administration have none. Parked.
AI risk ingest steps (Troupe). No owner or key for this operator. The risk view works without them.

Timed updates

Date	What changed
2026-10-06 (evening)	Leaves of absence now load into `loa_metrics`: 461 leave-days for the 4 communities (334 of them hospital), from May 2026. Feeds the leave and hospitalization dashboards from the next refresh. Integrated (3 Yardi communities, about 3,950 leaves) follows on its next run.
2026-10-06 (later)	Notes and incidents added to the weekly Yardi job. The incident reader reads ids in order (proven on Yardi's sandbox, 33 falls) and waits for Yardi to enable read on PROD; via Elegante must approve that. Leaves design drafted: Integrated alone has 3,956 Yardi leaves we drop today.
2026-10-06	Yardi turned on AdverseEvent, Practitioner, CareTeam, Immunization, CarePlan and Goal for TEST. Tested: 4 work, CareTeam is empty, and AdverseEvent cannot be searched and holds nothing. No Yardi customer (Integrated included) has incidents today. Asked Yardi for PROD access and how to get staff-entered incidents. 3 more test notes written to Yardi TEST for Yardi to check in their UI. Leaves of absence found in Yardi visit records (236 since May, 156 hospital). One-off pull of every endpoint the weekly pull skips: 3,656 notes with their text, now in blob. Every PROD endpoint is pulled. Asking Yardi for incidents (`AdverseEvent`).
2026-10-05	Residents reach `base.dim_resident` (223), after a one-word fix in the Yardi notebook. Weekly warehouse runs moved to Sunday. Careflows checked: 215 active residents, no duplicates. Yardi pull chained into the load job, test run green.
2026-10-03	First scheduled weekly cycle. Pull and load green. Canyons warehouse run missed (platform error at start), rerun 2026-10-05.
2026-10-02	Start-date and bed rows added. First note written to Yardi TEST (HTTP 201).
2026-10-01	Platform flows for all 4 communities. All 8 Airflow DAGs green. Resident profiles open in Careflows. Old duplicates deleted.
2026-09-30	Production Yardi access. First PROD pull (219,203 records). All 4 communities loaded into FHIR and silver and checked.
2026-09-27	Write-back proven: one vital written to Yardi TEST (HTTP 201). `dim_tenants` rows in.
2026-09-21	Careflows tenants and AVON medical centers created (Eric).
2026-09-16	First Airbyte pull from the TEST site lands in blob.
2026-09-15	Yardi access unblocked: the fix was a new endpoint id, not new keys.

Where via Elegante data lives

Read-only check, 2026-10-05.

Source table	via Elegante	Status
`base.dim_resident`	223 residents (Canyons 56, Highlands 36, Foothills 39, Mountains 92)	Has data
`public.patient154__v2`	133,878 daily rows, through today, 0 duplicates	Has data
`base.dim_moveinout`	215 moved-in residents	Has data
`medication.fct_medication_orders`	5,732 orders, 0 duplicates	Has data
`public.dim_tenants`, `tenant_start_date`, `tenant_capacity`	4 rows each	Has data
WorkBench `Residents` (Careflows profiles)	216, refreshed daily	Has data
`medication.source_administration`	Med passes land, but with no tenant id (all Yardi customers)	Partial

Showing via Elegante now (6)

Dashboard table	PROD dashboard	via Elegante rows
`public.fact_daily_residents_mv`	Community Overview Dashboard	7,657
`public.tenant_occupancy_mv`	Community Overview Dashboard	7,657
`public.pe_falls_mv`	Care Performance Dashboard	52 (falls read 0: no Yardi incident feed)
`public.pe_hospitalizations_mv`	Care Performance Dashboard	52 (reads 0: no Yardi incident feed)
`public.pe_outcomes_metrics_monthly_mv`	Care Performance Dashboard	52
`public.tenant_table`	none on PROD	4

Fill on the 2026-10-06 refresh (9)

These read base.dim_resident, filled 2026-10-05 after that day's refresh. Integrated shows in the first 7. The last 2 are empty for Integrated too, so check them.

Dashboard table	PROD dashboard	Integrated rows today
`public.resident_daily_list_mv`	Community Overview Dashboard	574,531
`public.resident_daily_status_mv`	none on PROD	574,531
`public.tenant_periodic_census_mv`	Community Overview Dashboard	22,850
`public.tenant_daily_census_mv`	none on PROD	19,416
`public.resident_stay_mv`	none on PROD	1,223
`public.resident_event_list_mv`	Community Overview Dashboard	1,133
`public.tenant_month_census_mv`	none on PROD	223
`public.pe_average_resident_tenure_mv`	Care Performance Dashboard	0, check
`public.pe_tenant_cohort_retention_mv`	Care Performance Dashboard	0, check

Not refreshed by any job (8)

Frozen for every tenant. None is on a PROD dashboard.

Dashboard table	PROD dashboard	Integrated rows today
`medication.patient_med_count_v3_mv`	none on PROD	58,682
`medication.patient_week_med_count_hybrid_mv`	none on PROD	48,268
`medication.patient_week_med_count_mv`	none on PROD	48,268
`medication.polypharma_kpi_v2_mv`	none on PROD	614
`medication.polypharma_kpi_v3_mv`	none on PROD	624
`medication.polypharma_weekly_hybrid_mv`	none on PROD	498
`public.resident_daily_status_p154_mv`	none on PROD	563,753
`public.tenant_periodic_census_p154_mv`	none on PROD	3,151

Empty for every Yardi customer (29)

Integrated is empty here too. These need new Yardi feeds, outside this onboarding.

Dashboard table	PROD dashboard	Why it stays empty
`incident.fct_incident_events_mv`	none on PROD	No Yardi incident feed; No Yardi leave feed
`medication.fct_infection_medication_monthly_mv`	none on PROD	Integrated (Yardi) is empty here too
`medication.high_risk_med_dash_mv`	none on PROD	Med groups not built for Yardi
`medication.medication_errors_and_administrations_mv`	none on PROD	No Yardi med-error feed; Med orders feed for Yardi (medication_testing) not built
`medication.medication_errors_monthly_weekly_mv`	Med Quality Dashboard	No Yardi med-error feed
`medication.medication_groups_weighted_average_mv`	Med Quality Dashboard	Med groups not built for Yardi
`medication.medication_orders_mv`	Med Quality Dashboard	Med orders feed for Yardi (medication_testing) not built
`medication.pe_med_groups_mv`	none on PROD	Med groups not built for Yardi
`medication.pe_med_refusals_unavailability_mv`	none on PROD	Med orders feed for Yardi (medication_testing) not built
`medication.pe_polypharma_mv`	none on PROD	Med groups not built for Yardi; No Yardi polypharmacy weeks feed
`medication.polypharma_dash_mv`	none on PROD	No Yardi polypharmacy weeks feed
`medication.polypharma_kpi_mv`	Med Quality Dashboard	No Yardi polypharmacy weeks feed
`medication.polypharma_resident_list_mv`	Med Quality Dashboard	No Yardi polypharmacy weeks feed
`medication.tenant_filter_mv`	none on PROD	No Yardi med-error feed; Med groups not built for Yardi; Med orders feed for Yardi (medication_testing) not built; No Yardi polypharmacy weeks feed; Med passes land without a tenant id
`medication.tenant_period_filter_mv`	none on PROD	No Yardi med-error feed; Med groups not built for Yardi; Med orders feed for Yardi (medication_testing) not built; No Yardi polypharmacy weeks feed; Med passes land without a tenant id
`medication.tenant_table_med_quality`	none on PROD	No Yardi med-error feed; Med groups not built for Yardi; No Yardi polypharmacy weeks feed
`medication.unavailable_and_refused_periodic_mv`	Med Quality Dashboard	Med orders feed for Yardi (medication_testing) not built
`public.fall_aggregate_mv`	none on PROD	No Yardi incident feed
`public.fall_rate_dash_mv`	none on PROD	No Yardi incident feed; No Yardi leave feed
`public.falls_mv`	none on PROD	No Yardi incident feed
`public.incident_events_mv`	Med Quality Dashboard	No Yardi incident feed
`public.leave_of_absence_mv`	Community Overview Dashboard	No Yardi incident feed; No Yardi leave feed
`public.pe_residents_on_leave_monthly_mv`	Care Performance Dashboard	No Yardi leave feed
`public.resident_mla_mv`	none on PROD	No Yardi leave feed
`social.fct_resident_visits_mv`	none on PROD	No visits source
`social.wellbeing_activity_attendance_mv`	Social Engagement Dashboard	No social engagement source
`social.wellbeing_social_engagement_index_mv`	Social Engagement Dashboard	No social engagement source
`social.wellbeing_ucla_loneliness_mv`	Social Engagement Dashboard	No loneliness survey source
`social.wellbeing_visitation_mv`	Social Engagement Dashboard	No social engagement source

How we connect

Yardi EHRxConnect, FHIR R4 US Core. Production property since 2026-09-30, read only. The TEST property is a frozen copy from 2026-09-08 and is used only for write tests.

Item	Value
Token	`POST {host}/{instance}/identity/connect/token`, client credentials, scope `APIvR4`
Token lifetime	300 seconds. Refresh about every 4 minutes on a long pull
API base	`{host}/{instance}/Webservices/FHIR/R4USCore/{guid}/{Resource}`
Headers	`Accept: application/fhir+json`, `Authorization: Bearer {token}`
Resident reference on a write	A bare id like `56843-2`, not `Patient/56843-2`
Delete	Not supported. Anything we write stays

What we can do on each endpoint

Access from each site's own /metadata, checked 2026-10-06 21:05 UTC. Highlighted rows differ between TEST and PROD. Click an endpoint to see every pull and push we have done, and where the data lands. Every endpoint open to us on PROD has now been pulled at least once. AdverseEvent, Practitioner, CareTeam, Immunization, CarePlan and Goal were turned on for TEST on 2026-10-06 and tested the same day.

Endpoint	TEST	PROD
Incidents · 0 pulls, 0 pushes, tested	create read	not available
Test 2026-10-06 TEST: Create and read by id only. Every search returns 400. No incidents found: 129 ids in Yardi's documented shape (`n-33`) all 404, and nothing references one. Yardi's own example is a fall-sensor alert, so it may only hold incidents created through the API, not staff-entered reports. Asked Yardi (2026-10-06). Lands in: Weekly task ready since 2026-10-06: reads incident ids in order (`1-33`, `2-33`, ...), tested on Yardi's sandbox (33 falls). Starts pulling the week Yardi enables read on PROD
Notes · 1 pull, 3 pushes	read create search	read search
Pull 2026-10-06 PROD: 3,656 (2,695 progress notes, 961 daily logs), then 3,681 in the first weekly-task run · one-off pull Push 2026-09-28 TEST: empty probe and 1 test note → 400, notes were off Push 2026-10-02 TEST: 1 test visit note → 201, id 1494-28029 Push 2026-10-06 TEST: 3 test notes: short, special characters, long → 201 x3, ids 1495 to 1497-28029 Lands in: Blob (`Prod_Ingestion/viaElegante_extra/`), pulled weekly since 2026-10-06. Nothing reads it yet
Note text · 1 pull, 0 pushes	not available	read
Pull 2026-10-06 PROD: 3,656 note texts, 0 failures, then 25 new in the first weekly-task run · one-off pull Lands in: Blob (`Prod_Ingestion/viaElegante_extra/`), new note texts pulled weekly since 2026-10-06. Nothing reads it yet
Stays and leaves of absence · 4 pulls, 0 pushes	read create search	read create search
Pull 2026-09-16 TEST: 667 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 790 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 821 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 828 · Airbyte job 16845, weekly chain test Lands in: FHIR only. Holds 236 leaves of absence (156 hospital) since May 2026. No warehouse table yet
Staff and doctors · 0 pulls, 0 pushes, tested	read search	not available
Test 2026-10-06 TEST: Works. 729 staff and doctors; search by name and community; read by id 200. Lands in: Not pulled. Asking Yardi to turn it on for PROD
Care team per resident · 0 pulls, 0 pushes, tested	read search	not available
Test 2026-10-06 TEST: Works, but needs a resident filter, and returns no care team for any of the 223 residents. Residents also have no `generalPractitioner`, so there is no resident-to-doctor link yet. Asked Yardi. Lands in: Not pulled. Empty on TEST
Vaccines · 0 pulls, 0 pushes, tested	read search	not available
Test 2026-10-06 TEST: Works. 81 vaccines (TB, flu, COVID, pneumococcal) for 44 residents, 2021 to 2026; search by resident, date and last-changed date. Lands in: Not pulled. Asking Yardi to turn it on for PROD
Care plans · 0 pulls, 0 pushes, tested	read search	not available
Test 2026-10-06 TEST: Works. 334 care plans (active, completed, revoked, draft), June to September 2026; every filter works. Lands in: Not pulled. Asking Yardi to turn it on for PROD
Care plan goals · 0 pulls, 0 pushes, tested	read search	not available
Test 2026-10-06 TEST: Works. 15,846 goals, about 92 per resident; search by resident and status. Lands in: Not pulled. Asking Yardi to turn it on for PROD
Vitals · 4 pulls, 1 push	read create search	read search
Pull 2026-09-16 TEST: 25,369 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 36,643 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 38,501 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 39,328 · Airbyte job 16845, weekly chain test Push 2026-09-27 TEST: 1 body weight, labeled test → 201, id 44451-8 Lands in: FHIR and Careflows only. No warehouse table
Residents · 4 pulls, 0 pushes	read search	read search
Pull 2026-09-16 TEST: 223 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 216 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 221 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 221 · Airbyte job 16845, weekly chain test Lands in: FHIR and Careflows; warehouse `base.dim_resident`, `dim_moveinout`, `patient154__v2`
Communities, rooms, beds · 4 pulls, 0 pushes	read search	read search
Pull 2026-09-16 TEST: 576 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 618 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 618 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 618 · Airbyte job 16845, weekly chain test Lands in: FHIR; the bed count went into `tenant_capacity` by hand
Diagnoses · 4 pulls, 0 pushes	read search	read search
Pull 2026-09-16 TEST: 3,949 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 4,077 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 4,097 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 4,097 · Airbyte job 16845, weekly chain test Lands in: FHIR only
Allergies · 4 pulls, 0 pushes	read search	read search
Pull 2026-09-16 TEST: 549 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 582 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 586 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 586 · Airbyte job 16845, weekly chain test Lands in: FHIR only
Med passes · 3 pulls, 0 pushes	read search	read search
Pull 2026-09-30 PROD: 162,589 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 170,538 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 177,139 · Airbyte job 16845, weekly chain test Lands in: FHIR; warehouse `medication.source_administration` (no tenant id)
Med orders · 4 pulls, 0 pushes	read search	read search
Pull 2026-09-16 TEST: 5,947 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 6,586 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 6,721 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 6,740 · Airbyte job 16845, weekly chain test Lands in: FHIR; warehouse `medication.fct_medication_orders`
Med list · 4 pulls, 0 pushes	read search	read search
Pull 2026-09-16 TEST: 5,947 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 6,586 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 6,721 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 6,740 · Airbyte job 16845, weekly chain test Lands in: FHIR only
Drug details · 0 pulls, 0 pushes	read	read
Nothing pulled or pushed yet. Lands in: Not fetched on its own: every med record carries its drug details inline, so the weekly pull has them
Diet orders · 4 pulls, 0 pushes	read search	read search
Pull 2026-09-16 TEST: 119 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 209 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 211 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 211 · Airbyte job 16845, weekly chain test Lands in: FHIR only
Insurance · 4 pulls, 0 pushes	read search	not available
Pull 2026-09-16 TEST: 302 · Airbyte job 15202, first pull Pull 2026-09-30 PROD: 307 · Airbyte job 16373, first PROD pull Pull 2026-10-03 PROD: 310 · Airbyte job 16664, weekly Pull 2026-10-05 PROD: 310 · Airbyte job 16845, weekly chain test Lands in: FHIR only
Communities as organizations · 1 pull, 0 pushes	read search	read search
Pull 2026-09-16 TEST: 10 · Airbyte job 15202, first pull Lands in: TEST only. On PROD our load builds it from the community Location
API settings · 1 pull, 0 pushes	not available	read search
Pull 2026-10-06 PROD: 3 · one-off pull Lands in: Blob only
API settings · 1 pull, 0 pushes	not available	read search
Pull 2026-10-06 PROD: 6 · one-off pull Lands in: Blob only

What we are asking Yardi for

Yardi turned these on for TEST (notes 2026-10-02, the rest 2026-10-06). We tested each one and asked for PROD on 2026-10-06. Results per endpoint are in the drop-downs above.

Resource	What the doc says it does	What we need it for	Status
DocumentReference	Create and read Progress Notes (`11506-3`), Daily Logs (`51855-5`) and documents	Visit notes into the Yardi chart. Chris's goal. One test note is built and dry-run tested, script `03_scripts/yardi_note_writeback.py`	On for TEST
AdverseEvent	Create and read by id, no search	Incidents and falls. No Yardi customer has incidents today	Needs search, and staff-entered incidents
Practitioner, Immunization, CarePlan, Goal	Read and search	Doctors, vaccines, care plans	Work on TEST, PROD asked
CareTeam	Read and search by resident	Link residents to their doctors	Empty on TEST, asked why
RelatedPerson, ServiceRequest	No operations / not enabled	Nothing for now	Not asked

Everything we have written to Yardi

Append a row for every write. There is no Delete, so this table is the full record of our footprint in their system.

When (UTC)	Resource	What	Result
2026-09-27 16:59	`Observation`	One body weight for one resident, repeating their last recorded value, labeled as a Centered Care integration test	201, id `44451-8`, read back and found in search
2026-09-28 13:10	`DocumentReference`, `AdverseEvent`	Empty probes to prove the resources are off. No resident, no content	400 Invalid Resource, nothing created
2026-09-28 13:14	`DocumentReference`	The full test visit note (Progress Note `11506-3`), same resident as the vital	400 Invalid Resource, nothing created. Notes are off until Tom enables them
2026-10-02 17:49	`DocumentReference`	The same test visit note, TEST site, after Yardi enabled create on notes	201, id `1494-28029`. Read back 200: Progress Note, Clinical Note, right resident, our first line stored. Full text not readable on TEST (no `Binary` there). Yardi to confirm it shows in their UI
2026-10-06 14:20	`DocumentReference`	3 more labeled test visit notes, TEST site, same resident: a short one, one with special characters and lists, and a long one (about 40 lines)	201 x3, ids `1495-28029`, `1496-28029`, `1497-28029`. Read back 200, right resident. Yardi to confirm all 4 in their UI