Integrations
Systems Gaine has mapped and integrated.
Every system on this list has been mapped to the Gaine ontology, integrated and run through the platform. The work done for one client is the starting point for the next client that runs the same system.
40+ systems, grouped by what they do.
Unless marked, a system connects by reconciled change files, event notifications or the platform API — chosen per client and per system. A further 30 to 40 systems consume change files formatted for them.
Direct API connector built by Gaine
Core administration
- HealthRules Payer — direct API connector
- Facets — direct API connector
- QNXT — direct API connector
- EZ-CAP — direct API connector
- Metavance
- PowerSTEPP
- HealthSherpa
- Wipro Member360
Provider data and credentialing
- symplr — direct API connector
- Availity
- MDStaff
- IntelliCred
Clinical and interoperability
- EpicReconciled change files
- InterSystems
- CareEvolution
- Orion Health
Life sciences
- VeevaFiles and extracts
- IQVIAFiles and extracts
- Datavant
- Komodo Health
- HealthVerity
- Definitive Healthcare
- Symphony Health
CRM, data and enterprise platforms
- Salesforce — direct API connector
- Snowflake
- Workday
- HealthTrio
- Microsoft Dynamics 365
- BlueDocs
EMPI, identity and MDM
- Verato
- Reltio
- Informatica
- Profisee
Paid reference sources
- LexisNexis — direct API connector
- Melissa Data — direct API connector
- ABMS — direct API connector
- CAQH
- NCOA
- Death registry
Public reference sources
- NPPES
- DEA
- PECOS
- FDA
- USPS
Clients have connected many more of their own — mainframes, departmental databases, systems built in-house. The integration layer is open and configurable, so a system does not have to be on a list to be connected.
Product names are trademarks of their owners, listed to show interoperability, not endorsement.