> ## Documentation Index
> Fetch the complete documentation index at: https://help.elationhealth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Promoting Interoperability (MIPS 2024) - Enabling exchange under the Trusted Exchange Framework and Common Agreement (TEFCA)

> This article describes enabling exchange under the Trusted Exchange Framework and Common Agreement (TEFCA) for the MIPS Promoting Interoperability performance category.

<Note>
  This Help Center Article is no longer relevant for the current calendar year. This Help Center Article is retained in the event of an audit for fidelity of information to align with changes over time and so we keep this article hosted. If you are looking for current calendar year information please ensure the calendar year is included in the title of the Help Center Article.
</Note>

## Measure Details

This measure is an alternative measure in the Health Information Exchange Objective in the Promoting Interoperability category and is not a required measure. The alternate measures for this are:

* [Sending & Receiving Health Information](/articles/Promoting-Interoperability-MIPS-HIE-Sending-Receiving-Health-Information) (2 measures with performance numerator/denominator metrics)
* [Bi-Directional Exchange](/articles/Promoting-Interoperability-MIPS-HIE-Bidirectional-Exchange) (attestation to engagement of a bidirectional exchange)

## Measure Parameters

The MIPS eligible clinician or group must attest to the following:

* Participating as a signatory to a Framework Agreement (as that term is defined by the Common Agreement for Nationwide Health Information Interoperability as published in the Federal Register and on ONC’s website) in good standing (that is, not suspended) and enabling secure, bi-directional exchange of information to occur, in production, for every patient encounter, transition or referral, and record stored or maintained in the EHR during the performance period, in accordance with applicable law and policy.
* Using the functions of CEHRT to support bi-directional exchange of patient information, in production, under this Framework Agreement.

## Elation Workflows

For 2024, there are no workflows in Elation to meet this measure. We recommend using the workflows detailed in one of the following two measures that Elation does support for the Health Information Exchange Objective:

* [Health Information Exchange (HIE) - Sending & Receiving Health Information](/articles/Promoting-Interoperability-MIPS-HIE-Sending-Receiving-Health-Information)
* [Health Information Exchange (HIE) - Bi-Directional Exchange](/articles/Promoting-Interoperability-MIPS-HIE-Bidirectional-Exchange) (for customers using Elation’s Carequality connection only)

Elation is currently not a QHIN and recognized under TEFCA. In the future Elation may have integrations with QHINs that would satisfy this measure.

## Additional Information

[2024 MIPS Promoting Interoperability Measure Specifications](https://qpp-cm-prod-content.s3.amazonaws.com/uploads/2650/2024MIPSPISpecifications.zip)

## Related Articles

* [MIPS (2024)- Promoting Interoperability Category](/articles/Promoting-Interoperability-MIPS-2024)
* [Promoting Interoperability (MIPS) - Health Information Exchange (Sending & Receiving)](/articles/Promoting-Interoperability-MIPS-HIE-Sending-Receiving-Health-Information)
* [Promoting Interoperability (MIPS) - Health Information Exchange (HIE) - Bi-Directional Exchange](/articles/Promoting-Interoperability-MIPS-HIE-Bidirectional-Exchange)
* [MIPS (2024) Overview](/articles/MIPS-2024-Overview)
* [MIPS (2024)- Quick Start Guide](/articles/MIPS-2024-Quick-Start-Guide)