Home / Solutions / Knowledge / Requirements

✣ Solutions · Knowledge · Requirements

Requirements Packs:

a proof you can hand to a surveyor

Short answer

A Requirements Pack turns a regulation into a map. Every paragraph is a stop. Preppr reads your plans, policies and after-action reports, pulls out the actual values with the page and sentence it found them on, and checks each stop against them. Nothing counts until a person confirms it.

Key facts

Each requirement

Proven · Needs review · Failed · No evidence

Packs

Shipped for major authorities, or generated from your documents

Certificates

Hashed and re-checkable, with or without Preppr

Knowledge · what Preppr has read

Requirements · 42 CFR 482.15

CMS Emergency Preparedness — Hospitals · 19 requirements

a Emergency plan

b Policies and procedures

c Communication plan

d Training and testing

e Emergency power

f Not checkable yet

Data point · traced to the passageCCH’s communications architecture provides primary, secondary, and tertiary pathways at each tier.Central City Hospital EOP Evaluation, p.5
Requirement · 42 CFR 482.15(c)(3)Primary and alternate means of communicatingProven

ProvenNeeds reviewFailedNo evidence

Certificates

d1c59a72…94cd

New plan version

Stops holding

Re-checked

✣ Requirements Packs

A Requirements Pack turnsthe regulation into a map.

Take a regulation like CMS Emergency Preparedness, 42 CFR 482.15. Every paragraph is a stop.

✣ Read and check

Preppr reads your plans, policies and after-action reports,

pulls out the actual values with the page and sentence it found them on, and checks each stop against them.

✣ Your review

Nothing counts until a person confirms it.

Preppr shows you the value, the document and the page, and you say correct or incorrect.

✣ Four states

Each requirement lands in one of four states:

proven, needs review, failed, or no evidence.

✣ Certificate

When the values are confirmed, Preppr issues a certificate.

It names every verified value and the rule it rests on, and carries a hash so anyone can re-check it, with or without Preppr.

✣ Re-checked

It stops holding the moment one of those values changes.

Replace a plan, and the proof gets re-checked.

✣ Requirements Packs

A proof you can hand to a surveyor, an auditor or your board,

with every claim traceable to a page in your own documents.

✣ Requirements Packs

A Requirements Pack turns the regulation into a map.

Take a regulation like CMS Emergency Preparedness, 42 CFR 482.15. Every paragraph is a stop.

✣ Read and check

Preppr reads your plans, policies and after-action reports,

pulls out the actual values with the page and sentence it found them on, and checks each stop against them.

✣ Your review

Nothing counts until a person confirms it.

Preppr shows you the value, the document and the page, and you say correct or incorrect.

✣ Four states

Each requirement lands in one of four states:

proven, needs review, failed, or no evidence.

✣ Certificate

When the values are confirmed, Preppr issues a certificate.

It names every verified value and the rule it rests on, and carries a hash so anyone can re-check it, with or without Preppr.

✣ Re-checked

It stops holding the moment one of those values changes.

Replace a plan, and the proof gets re-checked.

✣ The problem

The spreadsheet says yes because someone typed yes.

Take a regulation like CMS Emergency Preparedness, 42 CFR 482.15. It’s dozens of paragraphs, and each one is something a hospital has to be able to show a surveyor. Most teams track that in a spreadsheet.

app.preppr.ai

The map: 42 CFR 482.15, paragraph by paragraph. Open a stop to see its proof.

What a Requirements Pack does

Read

Preppr reads your plans, policies and after-action reports and pulls out the actual values, with the page and sentence it found them on.

Check

Each requirement lands in one of four states: proven, needs review, failed, or no evidence.

Prove

When a person confirms the values behind a requirement, the stop turns green and Preppr issues a certificate.

app.preppr.ai

Nothing counts until a person confirms it. Preppr shows you the value, the document and the page, and you say correct or incorrect.

The certificate names every verified value and the rule it rests on, and carries a hash so anyone can re-check it, with or without Preppr. It stops holding the moment one of those values changes.

✣ A few other things

Ready for a surveyor, an auditor or your board.

Packs

Shipped or generated

Preppr ships packs for the major authorities and can generate one for the authorities your own documents name, like Joint Commission or EMAP.

Review

Draft until reviewed

A generated pack stays a draft until your compliance lead reviews it. Preppr won’t call anything a compliance finding until then.

Facilities

Every site compared

Multi-facility systems see how many of their sites hold each certificate.

Crosswalks

Other frameworks

Crosswalks show how the same evidence maps to clauses in other frameworks.

The point isn’t a dashboard that says you’re ready. It’s a proof you can hand to a surveyor, an auditor or your board, with every claim traceable to a page in your own documents.

✣ What you get

A proof, not a dashboard.

A map of every paragraph

Values cited to the page and sentence

Four states per requirement

Confirmed by a person

Certificates with a hash

Open-source checker

Re-checked when a plan changes

Evidence pack export

CSV export

Shipped and generated packs

Facility comparison

Crosswalks

Results are filed in your knowledge base, so Ask Preppr can answer “is our evacuation requirement proven, and on what?”

See it with your own plans.

If you’ve ever spent the week before a survey hunting for the sentence that proves you did the thing, this is for you.