Integrations
How Nuvae works with Epic, Oracle Health (Cerner) and Meditech
Nuvae works alongside your EHR rather than replacing it. Contract analysis and Medicare benchmarking need only your contract files, so they work for any hospital. Claim-based modules read the standard 837 claim and 835 remittance files that Epic, Oracle Health (Cerner) and Meditech hospitals already exchange through their billing system or clearinghouse. Deeper EHR connections, such as clinical documents for appeals, are scoped per customer.
What Nuvae reads, module by module
| Module | Data it uses | Integration needed to start |
|---|---|---|
| Payer contract intelligence | Contract and amendment files (PDF) | None: upload the contracts |
| Government rates and percent of Medicare | Published CMS and state rate schedules | None: maintained by Nuvae's rate agents |
| Expected reimbursement and underpayment | 837 claims and 835 remittances | EDI file feed from your billing system or clearinghouse |
| Eligibility verification (newer) | Scheduled visits; payer eligibility responses | Visit schedule; payer APIs, with portal and phone fallback |
| Prior authorization (rolling out in phases) | Payer notification and authorization tracking | Scoped per customer |
| Denials and appeals | 835 denial codes, claim data, clinical documentation for clinical denials | Remittance feed; EHR connection for clinical documents scoped per customer |
Why standard transactions matter
Hospitals on Epic, Oracle Health (Cerner) and Meditech all send X12 claims and receive remittances, typically through their billing system and a clearinghouse. Building the claim-based modules on those standard files keeps the work outside the EHR: no custom code inside it and no change to its configuration.
Nuvae does not write back to the EHR today. Its findings come back to your team in the Nuvae workspace, and appeal letters are routed to staff for approval rather than sent automatically. Ask us which EHR connections are live today for the module you need.
How to verify any vendor's EHR integration claim
- Ask for named hospitals live on your EHR and version, using the same module you are buying.
- Ask exactly which data flows are used: which X12 transactions, HL7 or FHIR interfaces, and in which direction.
- Ask who builds and maintains the interface, and how much of your IT team's time it takes.
- Ask for a sample of real output (a priced claim, a flagged underpayment, a drafted appeal) produced from your EHR's data format.
- Ask what happens when your EHR upgrades or your clearinghouse changes.
- Separate what is live today from what is on the roadmap, in writing.
Typical rollout
A full rollout usually runs in phases over about three months: discovery, connecting the data feeds, then contracts, denials and front-end modules in turn. The contract module can start in parallel from the first week because it only needs the contract files.
Frequently asked questions
- Does Nuvae work with Meditech hospitals?
- Contract analysis and Medicare benchmarking work for any hospital, Meditech included, because they need only the contract files. Claim-based modules use the standard 837 and 835 files Meditech hospitals already exchange through their billing system or clearinghouse; we confirm the feed during discovery.
- Does Nuvae write data back into Epic or Cerner?
- No. Nuvae does not write back to the EHR today. It reads data and returns its findings to your team in the Nuvae workspace.
- What can we start with before any IT work?
- Payer contract analysis and Medicare benchmarking. Upload the contracts and amendments and Nuvae builds the rate matrix, with every figure linked to the source page.