State of M&A Data Rooms — Q2 2026 Read the report →
Peony LogoPeony

Home Health Accreditation: The Survey-Ready Document Room (ACHC, CHAP, Joint Commission)

Co-founder at Peony. Former M&A at Nomura, early-stage VC at Backed VC, and growth-equity / secondaries investor at Target Global. I write about investors, fundraising, and deal advisors from the deal-side perspective I spent years in.

Home Health Accreditation: The Survey-Ready Document Room (ACHC, CHAP, Joint Commission)

Last updated: August 2026

I'm Sean Yu, co-founder of Peony, and I spend my days looking at how confidential documents move — and, just as often, at how they fail to stay current. Home health accreditation is one of the sharpest versions of that problem I have found. An agency does not pass a survey on the day the surveyor arrives; it passes, or fails, on the state its documents were already in. The policy that was revised but never replaced on the drive, the nurse whose CPR card lapsed two months ago, the QAPI minutes nobody can locate — those are decided long before the opening conference. So the useful way to think about accreditation is not "how do we get ready for the survey" but "how do we make survey-ready the resting state of our documents." That is what this post is about.

Quick answer. Survey-ready is a document state, not an event. The home-health agency that can produce any file, in its current version, with a complete personnel record, on request, has already passed the document half of its survey. ACHC, CHAP, and The Joint Commission are among the accrediting organizations CMS approves for home health under Section 1865(a); all run three-year cycles and survey you against the Medicare Conditions of Participation at 42 CFR Part 484. Those CoPs require you to maintain documentary evidence — 42 CFR 484.65 (QAPI) says the agency must keep evidence of its program and demonstrate its operation. A Peony data room (free, $0) keeps the readiness file behind one always-current, version-controlled link, logs who opened what, and collects credentials inbound — priced per admin, recipients free. Peony is not a credentialing suite or a QMS: it does not verify licenses, run training, or make you compliant.

Where this post sits. This is the sibling of my colleague's GDP Compliance Pack guide — the same discipline for pharmaceutical wholesalers, who face the mirror-image problem of keeping a regulatory pack current and provable to counterparties. If you are a home-health administrator, director of nursing, or compliance lead at a small agency, this post is for you — and there are a lot of you: per MedPAC's March 2024 Report to Congress (Chapter 7), 11,353 home health agencies participated in fee-for-service Medicare in 2022, serving about 2.8 million beneficiaries at a program cost of $16.1 billion. This post is not accreditation consulting, and it does not tell you what your policies should say. It is about the document mechanics underneath readiness — the part that quietly decides whether the survey goes well.

What does "survey-ready as a document state" actually mean?

It means readiness is a property of your files at all times, not an activity you perform before a survey. An agency is survey-ready when it can produce any required document, in its current version, with complete supporting records, the moment someone asks — and stays that way between surveys, not just before them.

The distinction is not semantic. Treat readiness as an event and you get the familiar three-year cliff: documents scatter across drives, binders, and inboxes for thirty-five months, then a frantic assembly project in month thirty-six. Treat it as a state and the work flattens out — you keep one organized, current, openable set all the time, and the survey becomes a demonstration of something that already exists rather than a scramble to build it. The regulation itself assumes the state view. The Medicare Conditions of Participation for home health agencies, codified at 42 CFR Part 484 and titled "Home Health Services," require ongoing programs, not point-in-time exhibits.

Look at the QAPI condition. 42 CFR 484.65 is the "Condition of participation: Quality assessment and performance improvement (QAPI)," and its opening requirement is verbatim: "The HHA must develop, implement, evaluate, and maintain an effective, ongoing, HHA-wide, data-driven QAPI program." The regulation goes further and requires the agency to maintain documentary evidence of its QAPI program and to be able to demonstrate its operation to CMS. Read that clause slowly, because it is the whole thesis in one sentence: the obligation is not merely to run a QAPI program but to hold the documentary evidence of it and demonstrate it on request. That is a document state. If your QAPI evidence is a folder someone has to reconstruct, you are not meeting the spirit of the condition even if the program is real.

So "survey-ready" resolves to a concrete test: can you, right now, open the current version of any policy, any personnel file, and your QAPI evidence, and show who last touched it? If yes, the document half of your survey is already won. If no, you have a project waiting for you — and it will arrive on the accreditor's schedule, not yours.

How does accreditation and Medicare deemed status actually work?

Accreditation by a CMS-approved organization can substitute for a state survey to establish that a home-health agency meets Medicare's requirements — a mechanism CMS calls "deemed status." ACHC, CHAP, and The Joint Commission are among the organizations CMS approves for home health, and all three operate on a three-year cycle. The document burden is set by the underlying Medicare Conditions of Participation, which every accreditor surveys against.

Start with the legal plumbing, because it explains why the document set is what it is. Per CMS, Section 1865(a) of the Social Security Act allows most health care facilities to demonstrate compliance with the Medicare conditions through accreditation by a CMS-approved accrediting organization instead of being surveyed by a State Agency — this is "deemed status." CMS grants that status when a CMS-approved accrediting organization's standards meet or exceed Medicare's and its survey process is comparable to a State Agency's. Deemed-status agencies may still face CMS validation surveys, so accreditation is not a shield from oversight; it is an alternative, rigorous path to demonstrating the same underlying compliance.

Who can play that role for home health? ACHC (Accreditation Commission for Health Care) holds CMS deemed status for home health and states it has maintained that authority since 2006. The Joint Commission is designated by CMS as an approved accreditor for home health, with a deemed-status option under which organizations are evaluated against both Joint Commission standards and the Medicare Conditions of Participation. CHAP (Community Health Accreditation Partner) is a CMS-approved accrediting organization that holds deeming authority from CMS, and its surveys can substitute for federal and state inspections to establish that the Conditions of Participation are met. CMS's own list of approved accrediting organizations names ACHC, CHAP, and The Joint Commission among the organizations whose programs include home health agencies.

One precise wording note, because it is easy to overclaim here: these three are among the accrediting organizations CMS approves for home health — not the only ones. CMS lists nine accrediting organizations overall across care settings. So the honest framing is "ACHC, CHAP, and The Joint Commission are among the CMS-approved accreditors for home health," never "the only three." The point that matters for your documents is what they have in common: all three run three-year cycles and all three survey you against the same 42 CFR Part 484 Conditions of Participation. That is why the readiness file is broadly the same whichever you choose.

Does the choice between ACHC, CHAP, and Joint Commission change the document burden?

At the level of which documents you need to keep ready, less than agencies often assume — because all three survey against the same federal Conditions of Participation on the same three-year cycle. Their standards manuals, survey style, program menus, and process specifics differ, and none of that is a ranking or a recommendation. But the core readiness file is broadly common.

Take the cycle first. ACHC states that "Medicare certification and ACHC Accreditation for home health agencies both operate on a three-year schedule," and advises that renewal preparation begin roughly nine months before expiration. The Joint Commission describes accreditation as a three-year cycle for most organizations. And CHAP accreditation is likewise valid for three years, in line with Medicare requirements. Three years, across all three — which means the "we only touch this every three years" reflex is the same trap regardless of accreditor, and the always-ready file is the same answer.

Now the specialty wrinkle that matters for the persona I most often see — small home-infusion agencies. ACHC runs a dedicated Home Infusion Therapy accreditation program and holds CMS deemed status for home infusion therapy, meaning CMS has approved ACHC to validate eligibility for Medicare reimbursement for that service. ACHC also offers separate Pharmacy and PCAB (compounding pharmacy) accreditation programs, and its infusion pharmacy standards address sterile compounding and reference the USP sterile-compounding chapter. If you run infusion, that dedicated program is a reason ACHC comes up often in the infusion world — but it does not change the underlying truth that the readiness documents trace back to the same Conditions of Participation.

Here is the honest bottom line, hedged deliberately: choose your accreditor on fit, reputation, program menu, and how their survey style suits your team — considerations well beyond a document-tooling post, and ones I am not qualified to rank for you. But do not choose it expecting a materially lighter document load. Policies mapped to standards, complete personnel files, QAPI evidence, an emergency-preparedness plan, and infection-control documentation are the spine of readiness under any of the three. The room that keeps that spine current and provable does the same job underneath, whichever name is on your certificate.

What is actually in the always-ready file?

The always-ready file is the standing set of documents a surveyor's review reaches: policies mapped to standards, personnel files, QAPI evidence, your emergency-preparedness plan, and infection-control and clinical-record documentation. Kept current and organized, it is the document half of your survey — assembled once and maintained, not rebuilt each cycle.

The Conditions of Participation give the file its skeleton. Beyond the QAPI condition at 42 CFR 484.65, two more are worth naming precisely because they anchor whole document domains. 42 CFR 484.102 is the "Condition of participation: Emergency preparedness," and its opening requirement is verbatim: "The Home Health Agency (HHA) must comply with all applicable Federal, State, and local emergency preparedness requirements." And 42 CFR 484.115 is the "Condition of participation: Personnel qualifications," which sets minimum education, licensing, and experience standards for staff. The CoPs also address clinical records, patient rights, and infection prevention as document domains — I am describing those generically on purpose, because I will not attach a section number I have not verified.

Here is the shape of the file most agencies end up maintaining:

DomainWhat lives hereWhat it proves
Policies and proceduresYour policy set, organized to mirror the standardsYou operate to documented procedures mapped to the CoPs
Personnel filesLicense, CPR, TB and health screening, competency evaluation, job description, orientation — one file per staff memberEach person meets 484.115 personnel qualifications, provably
QAPI evidenceProgram description, performance data, project records, governing-body involvementThe documentary evidence 484.65 requires you to maintain and demonstrate
Emergency preparednessYour emergency plan, risk assessment, training and exercise recordsCompliance with the 484.102 emergency-preparedness condition
Infection controlInfection-prevention program, surveillance, related trainingThe infection-prevention domain of the CoPs
Accreditation and licensureCurrent accreditation certificate, state license, Medicare certificationYour legal and accreditation standing at a glance

survey-ready as a document state — the always-ready file vs the three clocks that break it

The value of holding this as one organized set is not that it is exotic — it is that it is always openable. A room lets you produce any single item, in its current version, on request, without emailing it or hunting a drive. That is the difference between "we have all of this somewhere" and "here it is." Access is logged, so you also know who opened which document and when. Peony organizes and serves this file; it does not tell you which standards apply, author your policies, or make the file complete for you — that judgment stays with your compliance lead.

What are the three clocks that break readiness?

Three moving clocks quietly erode a readiness file between surveys: expirables that lapse silently, versions that drift as documents are edited, and the accreditation cycle itself running down in the background. Each one turns a current file into a stale one without anybody deciding it should. Naming them is how you defend against them.

Clock one — expirables. Licenses, CPR cards, TB tests, competency evaluations, and health screenings all have expiry dates, and the file is only as current as the earliest one. This is the loudest pain I hear from small agencies: a nurse's CPR lapsed in the spring, nobody noticed, and it surfaces during a personnel-file review in the fall. The fix is structural — every expirable lives in its personnel file, tagged with its date, and you treat the nearest date as the thing that breaks readiness. A room holds the actual documents and logs access; the tracking discipline stays yours, and if you want automated primary-source verification, that is a credentialing suite's job, not a document room's.

Clock two — versions. Every policy update is a chance for the file to fork. The instant a policy exists as more than one copy — final-v2 in one folder, an emailed draft in an inbox, the "real" one on someone's desktop — nobody can say which is current, and a surveyor may be handed the wrong one. Version drift is caused by copies, full stop. The defense is one file behind one stable address: when the policy changes, you replace the file, not create a sibling. A room is built for this — the link stays constant while the document behind it updates, and every change is logged.

Clock three — the cycle. The three-year accreditation clock runs whether or not you are watching it, and ACHC advises starting renewal prep well before expiration. The danger is not the deadline; it is treating the deadline as the moment readiness begins. If the file is a standing state, the cycle is a non-event — you demonstrate what already exists. If it is a project, the cycle is a cliff. The whole point of the always-ready file is to convert the third clock from an alarm into a formality.

Every one of these clocks has the same underlying cause: documents that are current at one moment silently stop being current, and no single system is responsible for noticing. A room does not manage your compliance calendar or verify anything for you. What it does is remove the copy-drift clock entirely and make the expirable and cycle clocks visible, because the current version is the only version and access is on the record.

How do you make personnel files provably complete?

By building every file the same way, so completeness is visible at a glance and a gap announces itself. A personnel file is "provably complete" when a surveyor can open it, see the identical structure they saw in the last file, and find each required element in its expected place — current, dated, and openable. Sameness is the mechanism; the room is where it lives.

The standard behind this is 42 CFR 484.115, the personnel-qualifications condition, which sets minimum education, licensing, and experience standards for staff. Your file has to evidence that each person meets those standards — not assert it, evidence it. That means the license that proves current licensure, the competency evaluation that proves capability, the health and TB records, the job description, and the orientation record, each present and current. The persona I write for typically has fifteen to thirty nurses' files to keep this way, which is small enough to do well and large enough that ad-hoc folders fall apart.

The discipline that makes it provable is monotony. Use one folder template per staff member and never deviate: same sections, same order, every file. When a surveyor pulls three files in a row and each has the identical layout, two things happen — they build confidence quickly, and you can spot a missing element before they do, because a gap in a uniform structure is obvious where a gap in a bespoke folder is invisible. This is where expirables and personnel files intersect: the earliest-expiring document in each file is the one that dictates whether that file is currently complete, so the same date-tagging that defends against clock one also keeps the file survey-ready.

A data room keeps each file organized, version-controlled, and access-logged, and lets you produce any single file on request without emailing it — you open the current one in front of the surveyor. Two honest boundaries. Peony does not verify the credentials — it does not check a license against a state board or run primary-source verification; a credentialing platform does that, and I will not pretend a document room does. And Peony does not decide who is qualified — that judgment is yours. What the room gives you is completeness made visible and provable: the right structure, the current documents, and a record of access. That is the document contribution to a personnel review, and it is a real one, but it is not the whole of credentialing.

What happens during the survey event and plan of correction?

The survey is a demonstration of the document state you have maintained, conducted onsite through observation, interview, and document review — and if the surveyor finds a gap, you respond with a plan of correction, which itself has to be evidenced with documents. A well-kept readiness file makes the event a production exercise rather than an excavation, and gives the plan of correction somewhere to live.

ACHC describes its onsite survey as conducted through observations, interviews, and document review with ongoing question-and-answer, structured as an opening conference, the onsite survey, and a closing conference where general observations and findings are discussed. At the CMS guidance level, the State Operations Manual Appendix B is CMS's Guidance to Surveyors for Home Health — a pointer worth knowing, though I will not quote specific tag numbers from it. The practical shape for your documents: during the review, the surveyor asks for specific items — a named nurse's current license, the QAPI evidence, a particular policy — and the difference between a smooth survey and a rough one is whether you can open the current version immediately or have to go find it. This is precisely where the always-ready file pays for itself.

When findings do land, the response is a plan of correction, and the timeline is worth stating carefully as an accreditor-specific process rather than a universal rule. For an ACHC survey, ACHC provides its final report within 10 business days of the last day of survey, and any plan of correction must be submitted within 30 days of the final survey report. Treat that 10-day report / 30-day plan-of-correction timing as ACHC's stated process — I am not generalizing it across every accreditor, because I verified it specifically for ACHC. The document angle is the important part: a plan of correction is not a promise, it is an evidenced commitment. You have to show what you changed — the revised policy, the completed training, the new competency records — and that evidence has to be produced, dated, and organized.

This is where a room earns its place at both ends of the event. Going in, it lets you produce any requested document in its current version on demand. Coming out, it is where the plan-of-correction support artifacts live — the revised documents and the records that prove the fix happened, each version-controlled and access-logged, so when you demonstrate correction you are opening evidence rather than assembling it. Peony does not write your plan of correction or judge whether a deficiency is cured — that is your quality work. It holds the documents that make the correction provable.

How do you share the outbound pack with referral sources, pharmacies, and payers?

By putting the outbound packet behind one access link instead of emailing PDFs — so it stays current, and you have a record of who opened it. Accreditation does not only produce documents you hold for a surveyor; it produces a packet that referral sources, specialty pharmacies, and payers ask for repeatedly. That outbound flow has the same currency-and-proof problem as everything else, and the same fix.

The pattern is familiar from the GDP Compliance Pack — the same discipline for pharmaceutical wholesalers, who must present a regulatory pack to every counterparty and keep it current after each inspection. For a home-health agency, the outbound packet is your accreditation certificate, state license, key policies, insurance, and whatever credentials a referral source or specialty pharmacy requires to work with you. The failure mode is identical to the internal one: you email the packet as a zip, it freezes at the moment of sending, and the day your accreditation is renewed or a policy changes, every emailed copy is stale in an inbox you cannot reach.

Behind a link, the mechanics do the work. You assemble the packet in a room and share a single access link, gated behind the counterparty's terms if you want. When a document changes, you replace the file behind the link once, and every counterparty holding it opens the current version next time — no re-emailing everyone. Dynamic watermarking stamps each copy with the viewer's identity, so a forwarded document is traceable. Page-analytics record who opened the packet and when — the delivery record email cannot produce. And when a relationship ends, you revoke access. The inbound direction works the same way: when a specialty pharmacy or payer needs credentials from you, or you need to collect documents from a new referral partner, a single upload link gathers everything in one place, tied to that counterparty and timestamped, instead of an email thread with five attachments.

On compliance posture, let me be exact, because health data invites overclaiming. Peony is GDPR, CCPA, and HIPAA compliant. That is the claim, and I will not stretch it further — I am not going to make representations about specific contractual instruments here. And the practical boundary that keeps agencies out of trouble: patient charts belong in your EHR, not in a document room. The outbound pack is business documents — certificates, policies, credentials, insurance — not clinical records. Keep protected health information in the system built for it, and use the room for the accreditation and business documents it is built for.

Do you need a compliance suite, a QMS, a room, or a drive?

Different tools for different jobs, and a small agency often wants more than one. A compliance-and-credentialing suite automates training and license workflows; a QMS runs your policy lifecycle and quality machinery; a document room keeps the readiness file organized, current, and shareable; a shared drive does almost none of this reliably. Knowing which is which is how you avoid both overbuying and the drive-and-binder chaos.

Let me concede the lanes I do not own, plainly, because pretending otherwise would not help you. Platforms like MedTrainer bundle compliance, credentialing, and learning in a single suite — per its own site, that includes credentialing management, healthcare policy and document management, a learning management system with role-specific onboarding, incident reporting, safety-plan templates, and payer enrollments. Suites like that own workflow automation, training assignments, and credentialing — including the primary-source license verification a document room simply does not do. A QMS or eQMS, separately, owns your SOP lifecycle, CAPAs, and change control. If you need training assignments tracked, licenses verified against boards, or a managed policy-approval workflow, those are the tools, and Peony is not one of them.

So where does a document room fit, honestly? It is the document layer: the readiness file kept organized, version-controlled, access-logged, and shareable with a surveyor, referral source, pharmacy, or payer. It is what makes survey-ready a state — one current copy per document, provable access, no version drift — and it is the outbound-and-inbound channel for the packs above. Many small agencies run training and credentialing in a suite (or a disciplined manual process) and use a room purely for the always-ready file and the outbound packet. The two are complementary, not competing: the suite verifies and trains; the room organizes, versions, and proves.

A concrete example of a room used exactly this way: Access Home Care Solutions, an ACHC-accredited home-infusion provider with an intrathecal-pump-therapy specialty, runs its accreditation and compliance documents in Peony rooms. That is the shape of the fit — a small, specialized, accredited agency using the room as the organized, shareable home for its readiness documents, alongside whatever it uses to verify credentials and manage its quality system. And the shared drive? It fails at every clock: copies multiply, versions drift, nothing is access-logged, and "who opened this" is unanswerable. A drive is where readiness goes to quietly expire. Being clear about these boundaries is exactly why the 6,800+ customers who use Peony know what job it is doing — organizing and proving documents — and what it is not.

What does a survey-ready document setup cost?

Less than most agencies expect, because the pricing model is per admin with recipients free. Peony is free to start at $0; the Business plan is $30 per admin per month; and the Data Room plan — which adds dynamic watermarking and unlimited rooms — is $52 per admin per month on annual billing. For a small home-health agency, the operative fact is that you pay for internal admin seats, not for the people you share with.

That model is what makes this affordable for the persona I write for. A nurse-owned agency with one or two people administering the readiness file pays for one or two seats. Every surveyor you open a document for, every referral source or specialty pharmacy you send the outbound packet to, and every partner you collect credentials from is free — recipients and viewers do not cost anything. So the bill scales with your admin team, not with how many counterparties or surveyors touch your documents, which for an agency with a handful of admins and a wide referral network is exactly the right shape. On the Data Room plan you also get unlimited rooms, so separating the internal readiness file from an outbound pack, or keeping a distinct room per line of business, does not multiply the cost.

The tier most agencies land on is Data Room, at $52 per admin per month, and the reason is watermarking. When you share your accreditation certificate or a credentialing packet, dynamic watermarking stamps each copy with the viewer's identity, so a forwarded document points back to who opened it. That traceability, plus unlimited rooms and the version control that keeps one current copy per document, is what turns a document setup into a survey-ready one. To size it against the wider market rather than take my word for it, my colleagues maintain a virtual data room cost guide and a roundup of affordable virtual data rooms. The honest summary: a survey-readiness document setup is comfortably within a small agency's software budget, and the per-admin-recipients-free model is why 6,800+ customers run controlled sharing on Peony without the bill scaling with their audience.

Frequently Asked Questions

How do we track nurse licenses, CPR cards, and TB tests so nothing expires without anyone noticing?

The failure is that expiration dates live in people's heads or a spreadsheet nobody opens. Put every expirable in the personnel file it belongs to, tag each with its expiry date, and treat the earliest date as the one that breaks readiness. A document room holds the actual license, CPR card, and TB result behind an access-logged link, so when a surveyor asks for a specific nurse's current RN license you open the current one, not last cycle's. Peony organizes and version-controls those files and logs who opened them, but it does not verify a license against a state board or run primary-source verification — a credentialing suite does that. The room is where the proof lives; the tracking discipline and the verification stay yours or your credentialing vendor's.

How do we organize personnel files so we can prove to a surveyor that every file is complete and current?

Build one file per staff member, with the same folder structure every time: license, CPR, TB and health screening, competency evaluation, job description, and orientation record. Sameness is the point — a surveyor pulling three files in a row should find the identical layout, so a gap is obvious to you before it is to them. 42 CFR 484.115 sets personnel qualification standards, so the file has to evidence that each person meets them. A data room keeps each file organized, version-controlled, and access-logged, and lets you produce any single file on request without emailing it. Peony does not verify the credentials or decide who is qualified — that judgment is yours; the room makes completeness visible and provable.

How do we map our policies and procedures to ACHC standards — and keep the mapping current?

Keep one folder that mirrors the standards, and store each policy where its standard would look for it, so the map and the documents are the same object. The reason mapping drifts is that the policies live in one place and the crosswalk in another, and they fall out of sync. When a policy is revised, replace the file in its mapped location once; the map stays true because there is only one copy. ACHC accreditation for home health runs on a three-year schedule, and preparation should start well before expiration, so the mapping is a standing state, not a pre-survey project. A room gives you version control and one current copy per policy. Peony does not author the policies or certify the mapping — it keeps the mapped set current and openable.

Every policy update turns into version chaos on the shared drive — how do we keep one current version?

Version chaos comes from copies. The moment a policy exists as final-v2-USE-THIS.docx in three folders and two inboxes, nobody can say which is current. Keep one file behind one stable link, and when the policy changes, replace the file behind that link instead of making a new copy. Everyone who opens the link sees the current version; there is no second copy to go stale. A data room is built for exactly this — the address stays constant, the document behind it updates, and every version change is logged. Peony holds the single current copy and records who opened it and when. It does not manage your SOP lifecycle or approvals workflow — that is a QMS job — but it kills the many-copies problem that creates the chaos.

What documents will the surveyor actually ask for during an ACHC site visit?

ACHC describes its onsite survey as observations, interviews, and document review, structured as an opening conference, the survey, and a closing conference. In practice the document review reaches your policies mapped to standards, personnel files with current licenses and competencies, QAPI evidence, your emergency-preparedness plan, and infection-control and clinical-record documentation. The exact requests are set by the surveyor and the standards, so treat the list as the whole readiness file rather than a fixed checklist. A room lets you produce any of it on request — pull the current version of a named file in front of the surveyor instead of hunting a drive. Peony organizes and serves the documents; it does not tell you which standards apply or make the file complete for you.

Is the pre-survey scramble every three years normal, and how do other small agencies stay survey-ready in between?

It is common, but it is a symptom, not a requirement. ACHC accreditation runs on a three-year schedule and ACHC advises starting renewal prep well ahead of expiration, which tells you readiness is meant to be continuous, not a fire drill. The scramble happens when documents are only assembled for the survey; agencies that avoid it keep the readiness file current all year — one organized, version-controlled set that is always openable. 42 CFR 484.65 requires the agency to maintain documentary evidence of its QAPI program and demonstrate its operation, which is inherently ongoing. A room makes continuous readiness the low-effort default: you update files as they change, so there is no cliff. Peony holds that always-ready set; the compliance work itself stays yours.

How do we share a compliance or credentialing packet securely with a specialty pharmacy or referral source?

Put the packet behind one access link instead of attaching PDFs to email. Your accreditation certificate, key policies, insurance, and the credentials a referral source or specialty pharmacy asks for sit in a room, and you send a single link — gated behind their terms if you want. When your accreditation is renewed or a document changes, you swap the file behind the link and they open the current one, not last year's. You also get a log of who opened what and when, which email cannot give you. This is the same discipline a pharmaceutical wholesaler uses to share its GDP compliance pack. Peony keeps the outbound packet current and provable; the receiving party still runs their own verification, and the room does not do that for either side.

ACHC vs CHAP vs Joint Commission — does the choice change the document burden for a small home-infusion agency?

At the document level, less than you might expect. ACHC, CHAP, and The Joint Commission are among the accrediting organizations CMS approves for home health, all operate on a three-year cycle, and all survey you against the same Medicare Conditions of Participation at 42 CFR Part 484. So the core readiness file — policies mapped to standards, personnel files, QAPI evidence, emergency preparedness — is broadly the same whichever you choose. Their standards manuals, survey style, and process specifics differ, and this is not a ranking or a recommendation. If you run home infusion, note ACHC also has a dedicated Home Infusion Therapy program. Whichever accreditor you pick, the document room that keeps the file current and provable does the same job underneath.

Do we need a MedTrainer-style compliance suite or a full QMS, or is a document room enough for a small agency?

They do different jobs and you may want both. Platforms like MedTrainer bundle compliance, credentialing, and training in one suite — they own workflow automation, training assignments, and credentialing that a document room does not. A QMS manages your policy lifecycle, CAPAs, and internal quality machinery. Peony does none of that and I would not pretend otherwise. What a data room handles is the document layer: keeping the readiness file organized, version-controlled, access-logged, and shareable with a surveyor, pharmacy, or payer. Many small agencies run training and credentialing in a suite, or a disciplined manual process, and use a room purely for the always-ready file and outbound packs. Match the tool to the job — the room is for documents and evidence of sharing, not for running training or verifying licenses.

What should this cost — is there a survey-readiness document setup under $50 a month?

Close, and the pricing model matters more than the sticker. Peony is free to start at $0. The Business plan is $30 per admin per month, and the Data Room plan — which adds dynamic watermarking and unlimited rooms — is $52 per admin per month on annual billing. The detail that fits a small agency is per-admin pricing with recipients free: you pay for your internal admin seats, and every surveyor, referral source, or specialty pharmacy you share with is free. A nurse-owned agency with one or two admins is not paying enterprise money for a survey-ready file. The Data Room tier is the one most agencies want, because watermarking each shared copy with the viewer's identity makes a leaked document traceable.

Sources