Platform
Intake, matching and facility data in one place
A placement starts as a set of needs and ends as a decision someone has to stand behind. Arara Match keeps the two connected.
Step one
Case intake
A guided intake records what the placement actually requires — care setting, state, urgency, and the specific capabilities the patient needs, each marked required or preferred.
The required/preferred distinction is load-bearing: only a required capability narrows the list. A preference orders it instead, so a nice-to-have can never silently remove the one facility that would have taken the patient.
Patient identifiers are encrypted on entry and never pass through a draft or a session.
Ventilator program
RequiredDialysis, on site
RequiredBehavioural health support
PreferredWithin 25 miles of home address
PreferredAn illustration of case requirements at intake.
Step two
Facility matching
Candidates are filtered to the care setting and state, then ranked. Results come back in three groups rather than one list, and the group a facility lands in is a statement about evidence, not about quality.
Confirms what you need
Every required capability is certified by a source, shown with the issuing body and the date observed.
Needs verifying
No source covers one or more of your requirements here. Still listed, because an unverified facility has not failed anything.
Ruled out by a source
A source covers this facility and does not list the capability. Shown with the count and the reason, never silently dropped.
A required capability only filters when a case marks it required. A capability nobody has verified never counts as satisfying a requirement, and never removes a facility on its own.
Underneath
Facility data
Three layers, kept distinct so you can always see which one an answer came from.
Federal
Every Medicare-certified nursing home in the United States, with CMS quality ratings and certified bed counts, refreshed with each release.
State certification
Where a state publishes what each facility is licensed to operate, we map it to 14 capability types and show it with its source and date. New York today.
Your own knowledge
Your team can record what it knows about a facility. It counts for your hospital, is attributed to the colleague who recorded it, and is never shown to another organization.
- CMS provider file
- June 2026
- NYSDOH certification
- May 8, 2026
- Coverage
- nationwide (CMS), New York (capabilities)
Keeping it moving
Notifications
A case assigned to you, a status change on a case you own, a case that has sat open too long.
Notifications reference the case and link into the application. They never carry a patient detail — there is no parameter through which one could reach a message, which is a property of the interface rather than a rule somebody has to remember.
Boundaries
What it does not do
No record-system integration
There is no interface to Epic, Cerner or any other record system today. Cases are entered in Arara Match.
Not a referral network
It does not send, route or broadcast referrals, and does not hold relationships with facilities. The shortlist leaves with the planner.
Capability depth is New York
Facility coverage is nationwide; certified-capability data is deep in New York and thin elsewhere until more states publish it.
It does not place the patient
It is decision support. The placement is always a human decision, and the record says who made it.
Next step
Walk through it with us
Thirty minutes, using the data for the state you place into.