Integrations
Works with the systems your site already runs
Patientrig connects to EHRs and CTMS platforms through standard APIs — no custom middleware, no data migration, no replacing what already works. Configuring a new site takes hours, not weeks.
INTEGRATION ECOSYSTEM
Connected Systems
Eight integrations, one ranked shortlist
Each integration is tested against the current API version of the named system. Connection configuration is guided through the Patientrig setup flow.
SMART on FHIR / EpicCare connection via Epic's Patient and Observation endpoints. Reads demographics, ICD-10 diagnoses, LOINC-coded lab values, medication history, and active problem lists. Requires Epic App Orchard registration for your institution's MyChart instance. Setup is guided; most sites complete API credential configuration within two business days.
R4 FHIR API integration with Oracle Cerner, with optional CDS Hooks configuration for in-workflow candidate alerts. Supports Condition, Observation, MedicationRequest, and AllergyIntolerance resources. Requires Oracle Cerner SMART on FHIR app registration for your institution.
athenaNet REST API integration targeting ambulatory practice networks and independent specialty groups. Pulls structured problem lists, encounter-level diagnoses, recent lab results, and active medication lists. Well-suited for community-based research sites and independent practices not running Epic or Cerner.
Two-way integration: pulls protocol documents from Vault, pushes pre-screen candidate records back. Enables coordinators to stay in their existing CTMS workflow.
Read access to Rave EDC subject records for sites running concurrent trials. Identifies subjects already enrolled elsewhere to prevent duplicate screening contacts.
REDCap API integration for sites using REDCap as a patient registry or screening database. Maps REDCap fields to FHIR-equivalent resources for criteria evaluation.
Read access to Florence eBinders for protocol document retrieval. Patientrig can ingest the current approved protocol and consent forms directly from the site's eBinder, ensuring the criteria being scored match the IRB-approved version rather than a coordinator's local copy.
Any HL7 FHIR R4 compliant endpoint connects to Patientrig directly without custom middleware. Useful for sites with regional EHR implementations, multi-hospital networks with mixed systems, or institutions piloting FHIR-native data platforms. Patientrig queries standard FHIR resource types — no proprietary extensions required.
Ready to connect?
Integration setup takes hours, not sprints.
Our team walks your IT and clinical ops contacts through API credential setup. Most sites are running queries within 48 hours of first contact.