Coverage, source verification, operational scale, and compliance boundaries all matter. Results and field availability vary by jurisdiction and source.
Start With the Records Your Workflow Needs to Find
Begin with authorized, representative records and the names, dates of birth, addresses, and other inputs your workflow expects to use. Review returned candidates and their source context.
Evaluate Registry Coverage, Not Just Record Count
Record totals do not by themselves establish whether an API covers the jurisdictions or records your workflow needs. Review the published footprint and test the records that matter to your platform.
Verify Official Source Provenance
Look for a practical verification path: available identity context, source references, and a process for reviewing a possible match against the official registry.
Understand Data Freshness and Live Lookup Options
Standard data is continuously synchronized; Extensive Mode performs live registry lookups where available. Those are distinct paths, and availability and timing vary by jurisdiction and source.
Test Name, DOB, Address, and Batch Workflows
Evaluate the supported input patterns your admissions software needs, including name, date of birth, address context, and batch workflows where appropriate.
Evaluate Latency and Production Scale
Review documented response expectations, rate and volume needs, and how the API fits your platform's operational workflow. A production evaluation should reflect real integration conditions.
Review SOC 2 and Enterprise Security Evidence
Ask for current security evidence and review it against your own requirements. Qualified customers can request the applicable Trust Portal materials.
Plan for HIPAA Workflows Where Applicable
Standard access is not HIPAA-compliant and must not carry PHI or ePHI. When an approved Enterprise healthcare workflow is needed, confirm the separately executed BAA and written scope before production use.
Test Vendors With Records You Already Know
Use authorized records and the inputs your workflow will actually supply. Compare candidate results and official source references; do not rely on a marketing claim or a raw record count alone.
SNF Screening API FAQ
Does nationwide coverage mean every field is available everywhere?
No. Public fields, source availability, and update timing vary by jurisdiction.
Should an API decide whether an admission should proceed?
No. The API provides public-record search information; admission decisions and policies remain with the organization.
Where can a platform start?
Review the Skilled Nursing Screening product page and the Search API documentation.
Evaluate the Screening Workflow Your Platform Needs
Review Skilled Nursing Screening, then validate the records and inputs that matter to your admissions software.
Explore Skilled Nursing Screening