Support referral review
Use the available identifiers and context your admissions workflow already collects, then route possible matches for review.
Give admissions teams fast, source-verified registry screening inside the workflows they already use. Offenders.io powers screening infrastructure for leading post-acute platforms, with enterprise-scale APIs and approved healthcare workflows.
Bring source-verified registry screening into the admission and referral workflows your team already manages, without treating a possible match as an outcome.
Use the available identifiers and context your admissions workflow already collects, then route possible matches for review.
Access registry coverage spanning 184 U.S. registry jurisdictions. Records and available fields vary by jurisdiction and source.
Offenders.io supports screening infrastructure and source review. Your organization remains responsible for policies, eligibility, and admission decisions.
Offer post-acute customers a documented, repeatable screening path that fits their operational systems. Pair screening results with source review and clear handoffs instead of opaque, one-off checks.
Read the skilled nursing screening guide for a practical overview of the workflow and jurisdiction-aware considerations.
Screening infrastructure used across skilled nursing workflows.
Possible matches need context. Offenders.io helps teams identify candidate public registry records and review available source details, so a registry entry, a linked record, and a confirmed identity are never treated as the same thing.
Standard data is continuously synchronized; Extensive Mode performs live registry lookups where available. Source availability and update timing vary by jurisdiction.
Use a documented API for application workflows or Batch Processing for CSV-based, repeatable screening at scale.
Connect screening infrastructure to the operational surfaces your customers and admissions teams already use.
Use Batch Processing when a CSV-based workflow fits better than one record at a time.
Review the SNF screening API guide alongside the product documentation before selecting an integration path.
Approved Enterprise customers can use HIPAA-compliant workflows under a separately executed Business Associate Agreement. Standard self-service and trial access are not HIPAA workflows and must not receive PHI or ePHI.
Enterprise teams can discuss their approved workflow, data handling, and BAA requirements before production use.
Discuss Enterprise / HIPAA Requirements →Controls and audit evidence are available for qualified customer review through the Trust Portal.
Visit Trust & SecurityThere is no universal screening mandate or one-size-fits-all operational rule. Requirements, source availability, and review expectations vary by jurisdiction, facility, and use case.
Use screening infrastructure to support your organization’s own lawful policies and workflows. Confirm the applicable requirements with your own legal and operational teams.
Teams choose a source-aware, integration-ready screening layer that can scale with admissions operations while preserving clear review and compliance boundaries.
Search across 184 U.S. registry jurisdictions with jurisdiction-aware expectations for data and field availability.
Use official registry references where available and preserve the distinction between a possible match and a confirmed identity.
Choose the documented integration path that fits individual admissions workflows or repeatable lists.
Answers about skilled nursing screening workflows, source verification, and Enterprise access.
Start with standard API access or talk with our team about Enterprise and approved HIPAA workflows.