Registration & Identity

Establish a shared patient identity to support any patient-specific data exchange. Manage registration functions.

Web Services and Other Integrations

Other services to negotiate, establish, or verify patient identity include the following.

Eligibility Query

This bi-directional real-time query is used to verify eligibility with clearinghouses and payors. It uses ANSI X12 270/271 transactions.
Current integrations include...
  • AccuReg
  • Aetna
  • Anthem
  • Availity
  • Change Healthcare
  • Cigna
  • Experian Health
  • Gateway EDI
  • Group Health Cooperative (Seattle)
  • HDX
  • Health Alliance Plan
  • HealthCare Fiscal Management Inc.
  • Healthcare IP
  • HealthPartners
  • Highmark
  • InstaMed
  • Loxogon
  • MedAssets
  • Medicaid Minnesota
  • Medicaid New York
  • Medicaid Pennsylvania
  • Medicaid Texas
  • Medicaid Washington
  • Medicaid Wisconsin
  • Medicare
  • NEHEN
  • nThrive
  • Optima
  • Optum
  • Pelitas (formerly DCS Global)
  • Physicians Plus
  • Post-n-track Eligibility
  • Preferred One
  • Provider Advantage
  • Quadax
  • Recondo Technology
  • RelayHealth
  • Rycan
  • The Advisory Board Company
  • The SSI Group
  • TransUnion
  • Tricare
  • TriZetto Provider Solutions, a Cognizant Company
  • United Healthcare
  • Unity
  • UPMC Health Plan
  • VisionShare (ABILITY Network)
  • WayStar
  • WNY HealtheNet

Outgoing Admission Notification

This bidirectional X12 278 interface is used to notify a payor or health plan that a patient has been admitted. The request can be done real-time or in batches.
Current integrations include...
  • Aetna
  • Experian Health
  • Loxogon
  • HealthCareIP
  • Pelitas (formerly DCS Global)
  • Post-N-Track
  • United Healthcare

Patient + Practitioner explore the specExplore the technical specs

This basic FHIR service covers data about persons (or, technically, animals, although despite all our jokes about cows, we aren't really pursuing) receiving care or other health-related services. It focuses on the demographic information necessary to support administrative, financial, or logistic purposes. We support search, read, and create interactions for Patient, and search and read interactions for Practitioner.

Outgoing Family Medical History read the specRead the technical specs

Supports comprehensive risk assessment following the HL7 Version 3 Implementation Guide for Family History/Pedigree Interoperability, Release 1 - US Realm April 2013. This interface uses the XML message format.

Incoming Family Medical History read the specRead the technical specs

Receives responses to the Outgoing Family Medical History interface, a comprehensive risk assessment following the HL7 Version 3 Implementation Guide for Family History/Pedigree Interoperability, Release 1 - US Realm April 2013. Enhancements in a future version will allow this interface to operate as an independent standalone interface with additional workflows. This interface uses the XML message format.