Quick answer
A useful SNF software RFP connects clinical, assessment, admissions, billing, workforce reporting, interfaces, and data access to the same operating model. Give each essential requirement a defined scenario, included deliverable, acceptance result, and unresolved dependency. Eliminate unacceptable critical gaps before using weighted scores; keep planned capabilities separate from demonstrated scope.
Give respondents the facility they are actually pricing
A 100-bed independent facility with one business-office manager is a different implementation from a regional group with shared billing, even if both request “integrated EHR and revenue cycle.” Begin the RFP with contracted facilities and beds, current census used for planning, roles needing access, shared departments, pharmacy and laboratory partners, legacy archives, and intended rollout scope. Identify which future acquisitions are assumptions rather than approved scope.
The historical HHSC Oahu Region LTC EHR RFP, 2016, sections 2 and 4, is a useful original buyer example: it covers clinical and financial work together, requests implementation and interface detail, and uses buyer-defined scenarios. Its 2016 technology specifications are not a current requirements list. Use its breadth as a reminder to include the entire operation.
Copy this requirements structure into the working RFP
The following is an original illustrative workbook. Replace the synthetic conditions with locally approved tasks. Qualified staff define clinical and payment decisions; the workbook evaluates whether information and responsibility survive those decisions.
| ID and workflow | Scenario the buyer supplies | Deliverable included in proposal | Acceptance result |
|---|---|---|---|
| A1 Admissions | One referral, duplicate update, late arrival | Referral and episode configuration | One referral history; expected and actual arrival remain distinct |
| C1 Clinical handoff | Historical document plus corrected current document | Role-specific chart and document routing | Intended user finds the right version and sees its context |
| M1 Assessment | Prior assessment and current work item | Historical access plus current configuration | Old source status is not presented as a new submission |
| F1 Billing | Approved synthetic payer change and correction | Billing setup and report definitions | Finance can explain episode, dates and downstream output |
| W1 Staffing reporting | Changed employee ID with agency source | Named payroll/PBJ integration scope | Original identifiers, transformations and resulting records traceable |
| I1 Interface | Delivered message with unresolved destination mapping | Monitoring and partner test participation | Technical receipt and unresolved workflow distinguishable |
| X1 Exit | Export with one absent attachment | Export scope, dictionary and correction assistance | Missing object detected; usable corrected package delivered |
Add columns for vendor response, proposed version/module, third-party cost, buyer work, evidence location, result and final disposition. “Supported” without those columns can mean included, separately sold, custom-built or merely planned.
Use availability and importance as separate axes
Require respondents to choose available in proposed version, requires configuration, requires custom work, planned, or excluded. The first two still require evidence; they are not automatic passes. A configured option may require substantial buyer decisions. A planned option may be irrelevant to launch or may block the entire operating sequence.
Classify importance independently: essential gate, scored preference or deferred scope. For example, an untested historical export is not made acceptable by polished documentation screens. Conversely, a preference for a particular chart layout need not eliminate a workable option.
A hypothetical committee gives clinical work 30 points, finance 25, admissions 15, implementation 15 and total cost 15. One proposal earns 86/100 but fails the agreed facility-access boundary; another earns 79 and passes all gates. The scores cannot decide the first proposal's access disposition. Keep it outside the accepted shortlist until the failure is remedied. Any revised operating model must independently satisfy applicable privacy and security obligations and approved access boundaries through appropriate review; those obligations are not discretionary scoring preferences. The weights are invented; adopt weights that reflect your actual operating priorities.
Make the cost of a conditional answer visible
Suppose a required report is available through an external service. The proposal includes its connection but excludes its subscription and weekly reconciliation. Record both dependencies. If local staff estimate 90 minutes each week, that is 78 annual hours before leave coverage or rework. An independent facility may find that burden infeasible even when the quoted software fee fits its budget. A group may centralize the task, but still needs local exception handling.
The planning and transition sections of ONC EHR Contracts Untangled, September 2016 provide contracting background. Have legal and commercial reviewers translate the agreed arrangement into appropriate terms. This workbook is an operational scope record, not contract language or a legal conclusion.
Use references to test the hardest assumption
After demonstrations, ask a relevant reference to describe one recent instance of the workflow still troubling the committee. Establish whether its configuration, interfaces and centralized staffing resemble yours. Ask what internal work was underestimated and which workaround remains. Treat a reported improvement as a lead for a local test, not as your forecast.
Do not ask the reference to disclose resident data or confidential prices. A multi-site reference can still help an independent facility if the committee identifies which reported benefit depends on its regional staffing model. The useful result is a new test or a resolved assumption, not an endorsement quotation.
Hand implementation the same workbook
For every essential row, carry forward the proposed version, evidence, scope inclusion, buyer dependency and acceptance result. Unresolved rows remain visible with their effect on launch. The purchase decision should end with a documented operating model and a concrete list of work still required; implementation should not have to rediscover what a sales answer meant.
Questions & answers
What should a small independent SNF send before a full RFP?
Send a facility profile, essential workflow scenarios, system inventory and pricing assumptions. Use the answers to exclude unsuitable scope before spending scarce clinical and billing time on detailed demonstrations.
How should a committee score planned features?
Keep availability separate from fit. If an essential function is planned, evaluate a demonstrated interim process and its workload, or defer that part of the purchase. A roadmap date alone is not acceptance evidence.
Should every vendor answer hundreds of requirements?
A large inventory can be useful for completeness, but the selection decision needs a shorter set of consequential scenarios. Link detailed requirements to those scenarios so the committee can inspect their combined behavior.
Primary sources
Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.