Link the systems your practice uses
Arintra reads charts and returns codes through your EHR API. No exports, extra logins, or middleware to maintain.
EHRs we support
EHR connections use FHIR R4 when available. Systems that adopted FHIR later can use their legacy API endpoints.
Links when charts are signed through the eCW SMART on FHIR gateway. Handles ambulatory encounters, including wellness, acute, and chronic care management.
Accesses charts and writes codes through the athenaNet open API. Supports athenaClinicals and athenaOne. Codes return directly to the billing module queue.
Epic support is in development for ambulatory workflows using SMART on FHIR. Contact us to hear when the integration becomes ready.
Planned for solo and small-group specialty practices using DrChrono. Intended coverage includes dermatology, podiatry, and other specialty groups. Tell us if you use this EHR.
Available to Kareo-based practices. Covers chart parsing and code write-back to the Kareo billing module for final claim submission.
Available to specialty practices using EMA, especially dermatology and ophthalmology. Arintra's parsing logic accounts for EMA's specialty-specific chart structure.
Billing connections downstream
Arintra sends codes to your EHR billing module. Your current clearinghouse workflow then processes claims without altering the submission pipeline.
What occurs after chart signing
After a provider finalizes an encounter, the EHR sends Arintra's ingestion endpoint a FHIR notification. For non-FHIR EHRs, Arintra polls webhooks at intervals set during setup.
Arintra retrieves structured fields, including diagnoses, procedures, vitals, and meds, plus free-text HPI, assessment, and plan. The complete encounter document runs in a HIPAA-compliant ephemeral compute context and is not retained after code assignment.
CPT and ICD-10 codes and modifiers are assigned and checked against payer rules. The code set returns to the encounter through the EHR write API. Round-trip processing finishes in under three minutes from chart finalization.
Codes land in the billing module as if entered by a human coder. Your biller reviews, adjusts if needed, and submits. No new system login.
Connect during one onboarding call
You do not need to provision API keys yourself or work through developer documentation. Our onboarding team configures EHR API credentials, sets the billing module write-back target, and validates test encounters before go-live.
For most ambulatory practices, technical integration finishes within one business day after the onboarding call. The first live codes appear in the billing module as encounters are processed that same day.
Request Early AccessIs your EHR supported?
Send a note and we will verify compatibility with your stack. Our onboarding team manages technical setup, so you do not need an IT resource to begin.