Introduction

Thea Health connects primary care practices with specialists through eConsults: a provider asks a clinical question, a specialist answers it asynchronously, and the patient avoids an unnecessary referral or gets a better-prepared one.

The Partner API lets your software do the same thing on behalf of the practices you work with, so clinicians never have to leave your product.

Who it’s for

• Enterprise customers integrating eConsults into their own workflows.
• Software vendors that want to offer eConsults inside their product.

How it works

1. Thea gives your organization a partner key.
2. Each practice connects once. A Thea practice admin approves your organization, and you get a practice key for that practice. See Practices and connections.
3. You match your clinicians to the practice’s Thea roster. See Providers and seats.
4. You send the patient, identified by your own external_id, either with the case or ahead of time.
5. You create a case for a provider, with the clinical question and the specialty, then upload any attachments to it. Thea routes it to a specialist and notifies them.
6. The specialist replies on the case’s message thread. You read and post messages through the API, and Thea sends you a webhook for each change.
7. The case is closed by the provider, or by you on the provider’s behalf, and reopened if more questions come up.

Core resources

Resource	What it represents
Practice	A clinic on Thea. It connects to your organization once, and you get a practice key for it.
Provider	Someone on a practice’s Thea roster: a billable provider, staff, or an admin.
Patient	A patient of one practice, matched within that practice on your external_id, or on name and date of birth. Create one with the case, or ahead of time.
Case	An eConsult: the clinical question, specialties, the specialists who have replied, files, and status.
Message	One entry in a case’s thread, from the provider, practice staff, a specialist, or Thea support.
File	An attachment on a case, uploaded to the case in one request.
Webhook endpoint	An HTTPS URL of yours that receives signed events.

API basics

• Base URL: https://app.theahealth.com/api/partner/v1 (sandbox: https://dev.theahealth.com/api/partner/v1).
• Auth: your partner key in Authorization: Bearer <partner key>, plus Thea-Practice-Key: <practice key> on requests about a practice’s data.
• Format: JSON in and out; errors are problem details.
• IDs are opaque strings and timestamps are ISO 8601 in UTC.

QuickstartCreate a test eConsult in the sandbox.

API referenceEvery endpoint and field.