Elation Health

Elation Health Vitals API

The Vitals API from Elation Health — 5 operation(s) for vitals.

GitHub OpenAPI
Business capability
Clinical Documentation Management BC-2830

Operations 10

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 /vitals/{id}/ Look up a vitals record (legacy) · Get Vital #
Ask an LLM
“Can I pull one set of recorded vitals by id from the older unversioned endpoint?”
“What does the legacy vitals path return for a single reading?”
Tell an agent
Fetch legacy vitals record {id}.
Open vitals reading {id} from the original route.
GET /vitals/ Search vitals by patient or note (legacy) · Find Vitals #
Ask an LLM
“Can I find the vitals attached to a specific visit note on the legacy path?”
“Does the old vitals search filter by patient and practice?”
Tell an agent
Find legacy vitals for patient {patient}.
Search old-route vitals recorded on visit note {visit_note}.
POST /vitals/ Record vitals for a patient (legacy) · Create Vitals #
Ask an LLM
“What must I send to record a patient's blood pressure and weight through the legacy endpoint?”
“Can the old create call attach vitals to a visit note?”
Tell an agent
Record legacy vitals for patient {patient} at practice {practice}: blood pressure {bp}, heart rate {hr}.
Add old-route vitals with height {height} and weight {weight} to visit note {visit_note} for patient {patient}.
PATCH /vitals/:id/ Patch a vitals record (legacy PATCH) · Update Vitals #
Ask an LLM
“Is there a legacy PATCH for correcting part of a vitals record?”
“Can I fix one vitals value through the old unversioned PATCH?”
Tell an agent
Patch the legacy vitals record with the corrected values.
Apply a partial correction to vitals through the old PATCH route.
PUT /vitals/:id/ Replace a vitals record (legacy PUT) · Update Vitals #
Ask an LLM
“Which legacy PUT overwrites a full set of vitals?”
“Do I have to resend temperature, oxygen and respiratory rate when replacing vitals on the old path?”
Tell an agent
Replace legacy vitals for patient {patient} with temperature {temperature}, oxygen {oxygen} and respiratory rate {rr}.
Overwrite old-route vitals at practice {practice} with head circumference {hc}.
GET /api/2.0/vitals/ List a patient's vitals · List Vitals #
Ask an LLM
“How do I list the vitals recorded for one patient?”
“Can I page and sort v2.0 vitals for a practice?”
Tell an agent
List v2.0 vitals for patient {patient}, ordered by {order_by}.
Show vitals recorded on non-visit note {non_visit_note}.
POST /api/2.0/vitals/ Record a new set of vitals · Create Vital #
Ask an LLM
“Can I record pain score and BMI percentile with vitals in API v2.0?”
“What's required to save a patient's vitals in the current API?”
Tell an agent
Record v2.0 vitals for patient {patient} at practice {practice} with pain {pain} and temperature {temperature}.
Save BMI {bmi} and BMI percentile {bmi_percentile} for patient {patient} at practice {practice}.
GET /api/2.0/vitals/{id}/ Get one vitals record · Retrieve Vital #
Ask an LLM
“What does a single v2.0 vitals record include?”
“Can I see custom observations saved with a vitals reading?”
Tell an agent
Retrieve v2.0 vitals record {id}.
Show all measurements and custom observations in vitals {id}.
PATCH /api/2.0/vitals/{id}/ Correct part of a vitals record · Partially Update Vital #
Ask an LLM
“Can I fix just the weight on a vitals record in v2.0?”
“Is there a partial update to sign off on recorded vitals?”
Tell an agent
Change the weight on vitals {id} to {weight}.
Mark v2.0 vitals {id} signed by {signed_by} on {signed_date}.
PUT /api/2.0/vitals/{id}/ Replace a vitals record · Update Vital #
Ask an LLM
“Which v2.0 call fully replaces a vitals record?”
“Must patient and practice be resent when replacing vitals?”
Tell an agent
Replace vitals {id} for patient {patient} at practice {practice}.
Do a full v2.0 PUT on vitals {id} with custom observations {custom_observations}.

Documentation

📖
Documentation
https://docs.elationhealth.com/docs/oauth
📖
APIReference
https://docs.elationhealth.com/reference/get-token
📖
Documentation
https://docs.elationhealth.com/reference/scopes
📖
Documentation
https://docs.elationhealth.com/docs/api-overview
📖
APIReference
https://docs.elationhealth.com/reference
📖
APIReference
https://docs.elationhealth.com/reference/insurance-eligibility
📖
APIReference
https://docs.elationhealth.com/reference/message-threads
📖
Documentation
https://docs.elationhealth.com/docs/webhooks
📖
APIReference
https://docs.elationhealth.com/reference/event-subscriptions
📖
Documentation
https://help.elationhealth.com/articles/rest/overview/api-overview
📖
APIReference
https://help.elationhealth.com/api-reference
📖
Authentication
https://help.elationhealth.com/articles/rest/overview/oauth

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/openapi/elation-health-vitals-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-vitals-collection-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-patched-vitals-collection-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-paginated-vitals-collection-list-schema.json

Other Resources

🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/asyncapi/elation-health-events-webhooks.yml
🔗
OAuthScopes
https://help.elationhealth.com/articles/rest/overview/scopes
🔗
ChangeLog
https://help.elationhealth.com/articles/rest/changelog/changelog

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-vitals-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.

GitHub Google LinkedIn

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

OpenAPI Specification

elation-health-vitals-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Elation Health Vitals API
  version: '1.0'
  description: 'Operations tagged Vitals 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 (32 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/openapi/elation-health-vitals-api-openapi.yml