Implementation · the typical plan
Live on your own denials in about two weeks.
Week by week, with what your team does and what we do. The pilot is $5,000, one time, for 25 events - and its result is measured on your recoveries, not on our model.
Week 0
Agreement, BAA and pilot goals
Your team
Sign the pilot agreement and the Business Associate Agreement. Name a revenue-cycle lead and an Epic analyst. Agree the pilot goal: which denials, and the dollars recovered that would count as success.
MeetsCriteria
Stand up your own instance - its own database and application, nothing shared with any other customer. Send the Epic client ID and launch URL, and the security package.
Week 1
Epic activation
Your team
Your Epic analyst activates the MeetsCriteria app for your organization (read-only SMART on FHIR) and adds one launch point in Hyperspace. No change to your Epic build or change-control process.
MeetsCriteria
Load your payers’ current policies and your payer forms and letterhead. Set up administrators; clinicians sign in with Epic, no new passwords.
Week 2
Validation in your environment
Your team
A reviewer and a physician run three test cases end to end in your Epic, from launch to a signed appeal.
MeetsCriteria
Confirm chart access, citations and documents against your data; fix anything specific to your build before go-live.
Weeks 3–12
Pilot on live denials
Your team
Your team works real denials in MeetsCriteria - 25 events: appeals, submissions or action plans. Record the payer’s payment reference when money comes back.
MeetsCriteria
Weekly check-in. The executive summary (recovered against cost, verified against payment) updates as recoveries land.
End of pilot
Readout and decision
Your team
Review the pilot return: dollars recovered against the $5,000 paid, overturn rate, days from denial to appeal.
MeetsCriteria
A written readout on your own numbers. If it isn’t worth continuing, you keep the readout and owe nothing further.
What IT is asked for
Four things, and none of them is an interface build.
Activate one Epic app
Read-only SMART on FHIR, with the scopes listed in the security package. One launch point in Hyperspace.
Review the security package
PHI encryption, audit logging, the AI-vendor boundary and SOC 2 readiness - all on the Security page, current state only.
Sign the BAA
Before any PHI moves, including validation in your environment.
Nothing to host
Your instance runs in our Azure tenant, separate from every other customer. No servers, no interfaces to maintain.
Timings are the typical plan; your Epic change calendar and security review set the real dates. See Security & architecture for what is live today and what is validated during onboarding.
