Clinical evidence from Epic — reconciled against your claims
Read-only FHIR R4 connection to Epic. Encounters, conditions, labs and clinical documents flow into HCC evidence validation, RADV readiness and Healthcare Ask AI.
Connection method
Epic FHIR R4 API with SMART Backend Services (signed JWT; public key registered with your Epic backend app). OAuth2 client credentials and bearer tokens are also supported. Read-only system scopes.
What you can do with Epic
Example queries
Ask in plain English — inferonIQ generates the SQL and returns results.
HCC evidence
"Which reported HCCs lack current-year clinical evidence?"
RADV support
"Show every document supporting HCC 85 for this member"
Coding gaps
"Which members have diabetes complications documented but not coded?"
Suspect conditions
"Which members have pharmacy or lab evidence of a condition nobody documented this year?"
Setup in 4 steps
Register a backend (system) app in Epic and upload its public key / JWKS
Enter your Epic FHIR R4 base URL, client ID and private key
Test Connection reads the CapabilityStatement and lists available resources
Resources are catalogued and ready for Healthcare Intelligence and Ask AI