All use cases
Integration pattern
EHR-Embedded Knowledge
Your users make billing decisions inside your EHR every day — ordering procedures, documenting visits, capturing charges. Embed RCIntel so the right guidance shows up at each step without leaving your product.
For: EHR vendors, practice management systems, charge capture apps
Integration points
EHR workflow
Patient arrives
│
├─ Check-in
│ └─ RCIntel: payer filing rules (available)
│
├─ Provider orders procedure
│ └─ RCIntel: expected payment (available)
│
├─ Visit documented
│ └─ RCIntel: NCCI edits for the codes (available)
│
├─ Charge captured
│ ├─ RCIntel: expected payment for patient (available)
│ └─ RCIntel: PTP + MUE check (available)
│
└─ Claim submitted
└─ RCIntel: pre-submission scrub (Claim Scrubber)What RCIntel replaces in your product
| You currently maintain | RCIntel capability |
|---|---|
| Fee schedule lookup tables | Payment API — available |
| Payer rules database | Payer rules — available |
| NCCI edit tables | Coding edits — available |
| Denial code reference | Denial decode — available |
| Provider directory lookups | NPI lookup — available |
Code example
A React hook for embedding a source-linked payment estimate in your charge capture UI:
typescript — React hook
import { useState, useEffect } from "react";
interface PaymentEstimate {
allowed_amount: number;
source: string;
}
export function usePaymentEstimate(code: string, ccn: string) {
const [estimate, setEstimate] = useState<PaymentEstimate | null>(null);
const [loading, setLoading] = useState(false);
useEffect(() => {
if (!code || !ccn) return;
setLoading(true);
// Call from your server so the API key stays server-side.
fetch(`/api/rcintel/payment?code=${code}&ccn=${ccn}`)
.then((r) => r.json())
.then(setEstimate)
.finally(() => setLoading(false));
}, [code, ccn]);
return { estimate, loading };
}Embed billing knowledge in your EHR
Get a free read-only key and try a payment call, or talk to us about an embedded integration.