Facility Assessment Without Re-Entering Data

Somewhere on every administrator's desk there is a document that describes the facility: how many residents, what conditions they have, who is on staff and what they are licensed to do, which contracts are in place, what equipment the building depends on, and how the floor is covered across shifts. It is the CMS-required facility assessment. And almost every number in it is a number the facility was already keeping somewhere else.

Why repost the data you already have?

That question is the whole reason we built Facility Assessment the way we did. The regulation asks a facility to describe itself accurately. It does not ask anyone to maintain a second, slowly-diverging copy of the census in a word processor. But that is what the annual assessment has become at most buildings — and the copy in the document is always the one that goes stale.

What §483.71 actually asks for

Under 42 CFR §483.71, a long-term care facility must conduct and document a facility-wide assessment covering its resident population, the resources it needs to care for that population competently, and its capacity in an emergency. It has to be reviewed and updated at least annually, and again whenever something material changes — a new service line, a new wing, a shift in acuity.

Read the required content closely and the pattern jumps out. The assessment wants resident census and diagnoses. It wants staff roles, licensure and competencies. It wants contracts and arrangements. It wants equipment, services and physical environment. It wants staffing and coverage. Every one of those is operational data a running facility already tracks — because you cannot admit a resident, schedule a nurse, renew a certification or sign a vendor agreement without recording it somewhere first.

The pain point nobody names out loud

Ask an administrator what the facility assessment costs them and they rarely say "a week in January." They say something closer to the truth: it costs them all year, in small amounts, because they are keeping the same facts in two places at once.

A resident is admitted with a diagnosis — recorded in the roster. Six months later the assessment's condition tally still reflects last year's population. A nurse's license renews — recorded in certifications. The assessment still lists the old expiration. A contract lapses, a piece of equipment is retired, a unit's coverage pattern changes. Each of those is captured properly in the system that owns it, and each of them silently invalidates a line in a document nobody will open again until the next survey window.

Then a surveyor asks for the assessment, and the reconstruction begins: pulling the census, re-counting conditions, chasing down which certifications are current, hunting for the contract list. Not because the facility does not know these things. Because the document was built as a snapshot rather than a view.

The fix: derive it, don't retype it

MyLTC Apps ships the assessment as the twelve structured sections the regulation expects — facility information, resident factors, staff competencies, environment, buildings, equipment, services, personnel, contracts, health IT, risk, and summary. You fill in an assessment rather than designing one from a blank page.

The difference is what happens inside those sections. Any part that describes data the facility already keeps is drawn live from the module that owns it and marked with a "live from" chip so anyone reading knows exactly where the number came from:

Resident census and demographics — from your resident roster, not a typed count.
Licenses and certifications — from the certification tracker that already warns you before they expire.
Staff competencies — from the competency records staff complete during the year.
Staffing and shift coverage — from the shift calendar and its coverage targets.
Contracts and mutual-aid agreements — from the contract register, including executed agreements with neighboring facilities.
Equipment and assets — from the asset manager, tagged by building.
QAPI program, compliance status, and committee meetings — from the modules that run them.

Nothing is copied into the assessment. It is read at the moment the document is opened or printed. There is one copy of every fact, which means the assessment cannot drift out of date between reviews — because there is nothing to drift from. Update a resident's record and the assessment's population picture changed with it.

What you still type is the part that is genuinely yours: the narrative, the judgment, the annotation beneath a live block explaining what the facility does about what the number shows. That is the work worth an administrator's afternoon. Re-keying a headcount is not.

Condition tallies that do their own arithmetic

Resident acuity is where hand-built assessments go wrong most often. Conditions overlap — one resident can be on the dementia line, the fall-risk line and the wound-care line at once — so summing the counts and treating the total as the population produces percentages that are quietly nonsense.

In MyLTC Apps you record counts against the live roster and the percentages compute themselves. Overlapping condition metrics divide by an explicit resident total rather than by the sum of overlapping categories, so the acuity picture the assessment reports is arithmetically honest. Nobody is doing percentage math in the margin of a printout, and nobody has to notice that the categories add to 140%.

The regulatory reporting calendar

The assessment is not the only thing a facility owes the outside world. Alongside it sits a reference calendar of external filings — PBJ staffing submissions, NHSN reporting, ombudsman transfer and discharge notices, OSHA 300A posting, and the requirements specific to your state — each showing the next date it comes due.

Those dates are computed from each requirement's real cadence rather than a generic annual nudge. A quarterly filing shows the deadline for the quarter that just closed, which is the one actually in front of you — not one a full period away. And the calendar reports what is coming due without ever labeling anything overdue, because the filing itself happens outside the app and we will not assert a compliance verdict we have no basis for.

A review log, so the annual review is a record

§483.71 expects review and update at least annually. In practice, that expectation is often met by someone remembering they looked at it. Every review and update in MyLTC Apps is stamped into a running log with the date and the person who did it — and a quality or governing-body meeting can record the review straight from its agenda, so the meeting is the review, documented as it happens.

Just as importantly, the app reports what the log actually contains. With no entries, it says no review is recorded — not "non-compliant," and not a reassuring blank. The strongest honest statement is the one it makes.

Mixed campuses: the assessment covers one building

A campus with a hospital and a long-term care wing has a real problem here: §483.71 covers the long-term care building, and a document that counts the hospital's staff, equipment and shift coverage is describing the wrong facility.

Facility Assessment scopes to the building it actually covers. Staff, equipment, certifications, shifts and quality data filter to that wing, and every scoped section names the scope it used so the choice is visible rather than buried. Records carrying no building tag are disclosed as their own line — never silently dropped, never silently counted in. Single-building facilities never see any of it.

The survey-ready document

When a surveyor asks, one "full document" view stacks every section — manual answers, live data and annotations together — and prints as a clean copy you hand across the desk. It is generated from the current record at the moment you print it, not reassembled from fragments the week before a visit.

And because every source discloses itself, an empty one says so by name — "no contracts recorded in Manage Contracts" — rather than printing a blank that reads to a surveyor as a clean bill of health. Unanswered items surface as a worklist you can actually work. The document never claims an absence of data as a fact about your facility.

One copy of every number

The principle underneath all of this is simple enough to state in a sentence: a fact should live in exactly one place, and everything else should read it. That is why the roster feeds the assessment instead of being transcribed into it, why the percentages compute themselves, and why the printed document is a view rather than a file.

Your facility already knows its census, its acuity, its licensure, its contracts, its equipment and its coverage. The assessment's job is to describe that accurately — not to make you say it a second time and then keep both versions true.