Frequently Asked Questions
The Humana Data Exchange is an interoperability platform accelerating innovation in healthcare with products like the API Explorer and Synthetic Data.
Software developers, data scientists, and product team stakeholders in the healthcare industry can all benefit from using the Humana Data Exchange.
Signing up for the Humana Data Exchange allows you to access the full extent of our product offerings. You can use more in-depth datasets, collaborate with your team, receive personal guidance from Humana, and much more as a registered user of the Humana Data Exchange
Yes, you must create an account for each product you’d like to use. For example, you would need one account for the API Explorer and another account for Synthetic Data to access each product.
No, there is no cost associated with the Humana Data Exchange. All of our product offerings are free of charge.
Yes, you need to be a part of a legal entity recognized by your country or region to use the Humana Data Exchange.
FHIR is standard for the electronic exchange of healthcare information created by Health Level Seven International (HL7). “FHIR aims to simplify implementation without sacrificing information integrity. It leverages existing logical and theoretical models to provide a consistent, easy to implement, and rigorous mechanism for exchanging data between healthcare applications.”
View Humana’s FHIR Conformance and Compatibility Statement
The CMS Interoperability and Patient Access final rule (CMS-9115-F) “places new requirements on Medicaid and CHIP managed care plans, state Medicaid and CHIP fee-for-service programs, and Qualified Health Plans (QHP) issuers on the Federally-facilitated Exchanges (FFEs) to improve the electronic exchange of health care data, and streamline processes related to prior authorization.”
This requires all participating organizations and programs to increase patient access to electronic medical information and improve data exchange between patients, providers and payers.
For more information on the parameters of this ruling, please visit the CMS website