← PBJConnectCONTENT HISTORY
WHAT CHANGED
Update to PBJConnect
Snapshot Nov 21, 2026 · 00:17 UTC · version 0.1.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save PBJConnect and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Compare saved daily PCC operational occupancy, PCC billable ledger census, facility-recorded census, and CMS-published census using PBJConnect, with differences and coverage.",
"included_files": [],
"name": "census-reconciliation",
"skill_md_contents": "---\nname: census-reconciliation\ndescription: Compare saved daily PCC operational occupancy, PCC billable ledger census, facility-recorded census, and CMS-published census using PBJConnect, with differences and coverage.\n---\n\n1. Call `connection_status` and resolve requested facilities with `list_facilities`.\n2. Use `census_reconciliation` with an explicit inclusive date range of at most 366 days. Split longer requested history into non-overlapping windows. Request each facility page until complete.\n3. Keep PCC physical occupancy and PCC billable ledger census separate. Compare them with facility-recorded and CMS-published daily census only on dates with known, compatible evidence.\n4. Preserve `null` as unknown. Never fill missing days with zero or a neighboring day's value. Present known patient-day totals with their covered-day counts and requested-day counts.\n5. Include retrieval time, replication freshness when known, connector status, and incomplete or provisional classification flags. A record revision time is not proof of replication freshness.\n6. Identify the largest returned discrepancies and their dates. Explain whether they are genuine count differences or missing/incomplete evidence. Do not invent a reason for a discrepancy.\n\nThe tool reads saved daily summaries and does not start a new SQL pull. If the connector is offline, report the age of saved data. Resident drilldown is not available through this plugin. MDS-derived census may be unavailable; do not substitute PCC ledger counts for it or call them CMS-accepted MDS census.\n\nFor staffing analysis, name the denominator and exclude unverified occupancy days from confirmed calculations. Do not claim that a census comparison alone establishes staffing compliance. The portal provides the detailed reconciliation workflow.\n"
}SHA-256 of public snapshot: 663b09ace17b7968b0b9eed0b711e59abdab7f01310188e12c443f23fbf89520