ALL

Creates or deletes adjustments on a given claim

Medical Network Attachments API

Check on the status of a submitted claim, in real time, with thousands of payers through this RESTful API using JSON. This API can be used as an alternative to the X12 276/277 claim status transaction.

Using artificial intelligence, Claims Lifecycle AI proactively identifies claims at risk for denial and provides a score for a particular payer’s likelihood to deny along with insight based on denial category.

Retrieve valuable claim responses and reports from payers to see claim status updates, remittance advice, and other acknowledgements in order to resolve errors and stay up to date with the most recent information.

Creates a claim in the Change Healthcare Payments system

Seamlessly check a member’s eligibility and health plan benefit details with thousands of payers through our proprietary RESTful API using JSON components. This transaction is an alternative to the ANSI X12 270-271.

This API is for Commercial Pharmacy to mock adjudicate claims and for Real Time Activation to provide new Coupon IDs

Retrieves the claim details for claim or member and payer passed in the request

Patient Responsibility Estimator, or PRE for short, provides real-time estimates of patient out-of-pocket costs to healthcare providers.

Effortlessly check a patient’s pharmacy coverage for benefits details and pricing information for specific drugs with hundreds of payers through our RESTful API using JSON components.

Effortlessly check a patient’s pharmacy eligibility and obtain plan benefit details with hundreds of PBMs through our proprietary RESTful API using JSON components.

Quickly and easily submit professional claims to payers through a RESTful API using JSON. This API can be used as the alternative to the X12 837P transaction.

DEPRECATED: This API is used to obtain an access token, which is required to access other APIs on the platform.

This API is used to obtain an access token, which is required to access other APIs on the platform.

Access a list of payers and partners accepting transactions from our APIs. Find important partner attributes, including partner identifiers, eligibility search options, and more.

Retrieves payment transactions for a given claim

This implementation guide provides implementers with FHIR profiles and guidance to create, use, and share Clinical Notes. This guide is based on FHIR Version 3.0.1.

The Argonaut Data Query Implementation Guide is based upon the core FHIR DSTU2 API and documents security and authorization, data element query of the ONC Common Clinical Data Set and Document query of static documents.

The Argonaut project Provider Directory guide is based upon the FHIR STU3 API and contains the foundation for a robust provider directory. The components developed in this guide are intended to provide a foundation for a central or distributed Provider or Healthcare Directory.

The goal of the Argonaut Questionnaire Project is to develop guidance to support interchange of simple forms based on FHIR Version 3.0.1 and specifically the Questionnaire and QuestionnaireResponse resources.

The Argonaut Scheduling Project is a vendor agnostic specification providing FHIR RESTful APIs and guidance for access to and booking of appointments for patients by both patient and practitioner end users.

This specification describes a 'hook'-based pattern for invoking decision support from within a clinician's workflow. The API supports synchronous, workflow-triggered CDS calls returning information and suggestions as well as launching of a user-facing SMART app when CDS requires additional interaction.

The SMART App Launch Framework connects third-party applications to Electronic Health Record data, allowing apps to launch from inside or outside the user interface of an EHR system.