Developer Resources

If you build apps that connect with our systems, this page gives you what you need to get started. We follow federal CMS rules and use national standards to help our members safely share their health information.

If you have questions or need help, we’ll point you to the right resources along the way.

How our APIs work

We offer FHIR‑based APIs that follow CMS Interoperability and Patient Access requirements.

These APIs are delivered through 1Up Health, our technology partner. Even though 1Up Health hosts the platform, we remain the payer of record and the steward of our members’ data.

Connecting to BCBST Patient Access and Provider Directory APIs

Developers can use 1upHealth APIs to create applications that interact with BlueCross electronic health data available from BlueCross BlueShield of Tennessee—including clinical and claims data—using the FHIR standard. 1upHealth provides a common RESTful API with access to 10,000+ health centers within their growing network.

1upHealth's API fully supports FHIR® and provides rich programmatic access to electronic medical record data for patients and the companies and institutions who serve them. The available data includes patient demographics, labs, medications, observations, procedures, allergies, and much more.

The 1upHealth platform is HIPAA compliant. Click here to create an account and get started:

Login or Create a Developer Account

The following data is available through the BlueCross BlueShield of TN/1upHealth FHIR API: Patient Access and Provider Directory API endpoints

Additional help can be accessed here: 1upHealth Help Center

Do you have more questions?

For more information about interoperability for app developers, please visit the CMS Interoperability page: https://www.cms.gov/priorities/burden-reduction/overview/interoperability

If you have questions about connecting to BCBST FHIR APIs via 1upHealth, please send any questions in an email with a contact name, company name, app title, to BCBST_Interoperability_Support@bcbst.com.

We may be directed to give your application access to patient identifying information that is protected by 42 CFR Part 2 (the federal Confidentiality of Substance Use Disorder Patient Records). By registering with our API, you acknowledge and agree that you have received the prohibition on redisclosure notice that 42 CFR part 2 prohibits unauthorized disclosure of these records.