Elation Health Message Threads API

The Message Threads API from Elation Health — 7 operation(s) for message threads.

Operations 13

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /message_threads/{id} Get a message thread (Get endpoint) · Get Message Thread #
Ask an LLM
“How do I fetch a patient message thread by its id with the Get Message Thread call?”
“Can I read a care-team message thread's members and messages?”
Tell an agent
Get message thread {id} using the Get Message Thread endpoint.
Fetch the messages in thread {id}.
GET /message_threads/ Find message threads by patient or date · Find Message Threads #
Ask an LLM
“Can I find message threads for a patient within a document date range?”
“Which message threads were documented after a given date at my practice?”
Tell an agent
Find message threads for patient {patient}.
Find threads at practice {practice} documented after {document_date__gt}.
POST /message_threads/ Start a message thread with a sender · Create Message Thread #
Ask an LLM
“How do I start a new message thread about a patient with a named sender?”
“Can I flag a new message thread as urgent when I create it?”
Tell an agent
Start a message thread for patient {patient} from sender {sender} at practice {practice}, dated {document_date}, charted {chart_date}.
Open an urgent thread from {sender} about patient {patient} in practice {practice} on {document_date} charted {chart_date} flagged {is_urgent}.
PATCH /message_threads/{id}/ Update a thread's urgency or members · Update Message Thread #
Ask an LLM
“Can I mark an existing message thread urgent after the fact?”
“How do I add members to a message thread that already exists?”
Tell an agent
Mark message thread {id} urgent: {is_urgent}.
Set the members of thread {id} to {members} on the legacy endpoint.
DELETE /message_threads/{id}/ Delete a message thread (legacy) · Delete Message Thread #
Ask an LLM
“How do I remove a message thread using the older delete call?”
“Can a message thread be deleted once it's created?”
Tell an agent destructive · confirm first
Delete message thread {id} with the legacy Delete Message Thread call.
Remove thread {id} from the patient chart via the legacy endpoint.
POST /message_threads/ [WIP] Create a message thread (WIP endpoint) · Create Message Thread [WIP] #
Ask an LLM
“Is there a work-in-progress version of the create message thread call?”
“Can I create a thread with the WIP endpoint without naming a sender?”
Tell an agent
Using the WIP endpoint, create a thread for patient {patient} at practice {practice} dated {document_date}, charted {chart_date}.
Create a WIP message thread for {patient} in {practice} with messages {messages}, document date {document_date}, chart date {chart_date}.
DELETE /message_threads/{id}/ [WIP] Delete a message thread (WIP endpoint) · Delete Message Thread [WIP] #
Ask an LLM
“Does the work-in-progress API have its own message thread delete?”
“Can I delete a thread through the WIP endpoint?”
Tell an agent destructive · confirm first
Delete thread {id} via the WIP endpoint.
Use the work-in-progress delete to remove message thread {id}.
GET /api/2.0/message_threads/ List message threads with paging · List Message Threads #
Ask an LLM
“Can I page through all message threads with limit and offset?”
“How do I list threads sorted by document date on or before a cutoff?”
Tell an agent
List message threads, {limit} per page.
List threads for patient {patient} documented on or before {document_date__lte}, sorted by {order_by}.
POST /api/2.0/message_threads/ Create a message thread for signing · Create Message Thread #
Ask an LLM
“Can I create a message thread already signed by a provider?”
“What's the minimum to create a new message thread in a patient chart?”
Tell an agent
Create a thread for patient {patient} at practice {practice} dated {document_date} with chart date {chart_date}.
Create a thread for {patient} in {practice}, dated {document_date}, charted {chart_date}, signed by {signed_by}.
DELETE /api/2.0/message_threads/{id}/ Delete a message thread · Delete Message Thread #
Ask an LLM
“How do I delete an existing message thread from the chart?”
“Is deleting a message thread permanent?”
Tell an agent destructive · confirm first
Delete existing message thread {id}.
Destroy v2.0 message thread {id}.
GET /api/2.0/message_threads/{id}/ Retrieve a message thread · Retrieve Message Thread #
Ask an LLM
“Where can I retrieve a message thread including who signed it?”
“Can I retrieve a thread's delivery date by id?”
Tell an agent
Retrieve message thread {id}.
Retrieve who signed thread {id} and when.
PATCH /api/2.0/message_threads/{id}/ Partially update a message thread · Partially Update Message Thread #
Ask an LLM
“Can I change only the signer or signed date on a message thread?”
“Can I partially update a thread's chart date in the v2.0 API without resending everything?”
Tell an agent
Partially update thread {id} with signed date {signed_date}.
Change the chart date of thread {id} to {chart_date}.
PUT /api/2.0/message_threads/{id}/ Replace a message thread · Update Message Thread #
Ask an LLM
“Can I fully replace a message thread's patient, practice and dates?”
“Which fields are required to overwrite a whole message thread?”
Tell an agent
Replace thread {id} with patient {patient}, practice {practice}, document date {document_date} and chart date {chart_date}.
Overwrite thread {id} for {patient} at {practice}, dated {document_date}, charted {chart_date}, delivered {delivery_date}.

Documentation

Specifications

Schemas & Data

Other Resources

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/elation-health:elation-health-message-threads-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

elation-health-message-threads-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Elation Health Message Threads API
  version: '1.0'
  description: 'Operations tagged Message Threads across 2 of this provider''s published API definitions: elation-api-settings.json, elation-health-api-full-openapi.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://sandbox.elationemr.com/api/2.0
- description: Sandbox Server
  url: https://sandbox.elationemr.com
- description: Production Server
  url: https://api.app.elationemr.com
tags:


# --- truncated at 32 KB (34 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/openapi/elation-health-message-threads-api-openapi.yml