How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Elation Health Notes API

The Notes API from Elation Health — 3 operation(s) for notes.

Elation Health Notes API is one of 126 APIs that Elation Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Notes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and a changelog.

This API exposes 6 operations across 3 paths, and defines 123 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://sandbox.elationemr.com/api/2.0.

6 operations 3 paths 123 schemas 1 DELETE3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.app.elationemr.com/api/2.0
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Elation Health Notes API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (RequireAuthentication). It accepts HTTP bearer tokens (RequirePracticeAuthorization). It accepts HTTP bearer tokens (RequirePracticeAuthorizationOrHippoAdmin).

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Notes 6
GET
/notes
List Notes
list_notes 6 params → 200422
POST
/notes
Create Note
create_note body → 201422
DELETE
/notes/{note_id}
Delete Note By Id
delete_note_by_id 1 param → 204422
GET
/notes/{note_id}
Get Note By Id
get_note_by_id 1 param → 200422
PATCH
/notes/{note_id}
Update Note By Id
update_note_by_id 1 param body → 200422
GET
/notes/{note_id}/amendments/{amendment_id}
Get Note Amendment By Id
get_note_amendment_by_id 2 params → 200422

Schemas 123

The contract defines 123 schemas that model the data the API accepts and returns. The most detailed are ElationNote (19 properties), Note (17 properties), PrescriptionSummary (17 properties), Immunization (15 properties). Each schema is shown below with its type and property counts.

DocumentSignature
object
A signature on a document.
8 properties 5 required
ReferralBlock-Output
object
2 properties 1 required
NarrativeParagraphAttrs
object
1 property
VitalTemperature
object
4 properties
FollowupParagraphAttrs
object
1 property
SleepOrderSummary
object
10 properties 3 required
FollowupUnorderedList-Output
object
3 properties
el8_note_models__note__content__base_node__Node__NodeAttrs
object
4 properties
PulmonaryOrderBlock-Output
object
2 properties 1 required
Procedure-Output
object
2 properties 1 required
VitalBP
object
5 properties
AttrsWithRefId
object
Base attrs for any node that carries a stable change-tracking refid.
1 property
NarrativeOrderedList-Output
object
3 properties
NoteLayoutColumn
object
2 properties
ReferencedDocumentAttrs
object
2 properties 1 required
TwoColumnLayoutNode-Output
object
3 properties
VitalsSectionAttrs-Output
object
3 properties
ImmunizationVaccine
object
1 property
HTTPValidationError
object
1 property
AiGenerationInfo
object
2 properties
PrescriptionSummary
object
17 properties 3 required
NoteUpdate
object
10 properties
LabOrderBlock-Output
object
2 properties 1 required
HandoutBlockAttrs-Output
object
3 properties 2 required
InstructionsListItem-Output
object
3 properties
VitalHR
object
4 properties
ColumnLayoutNode-Output
object
3 properties
ProcedureSection-Output
object
2 properties
InstructionsOrderedList-Output
object
3 properties
DocumentNodeChild-Input
Note
object
A full representation of a note. Do not use this for endpoints that return notes in bulk. Use NoteMetadata for that instead.
17 properties 7 required
LineBreakInline
object
Hard line break. No attrs, no content.
1 property
VitalFiO2
object
4 properties
ProcedureParagraphAttrs
object
1 property
ColumnLayoutNode-Input
object
3 properties
ElationNoteAmendment
object
Full representation of an EN2.1 sections-based note amendment. Analogous to NoteAmendment for legacy DocumentNode notes. previouscontent is populated after the…
15 properties 9 required
InjectionBlock-Output
object
2 properties 1 required
NarrativeSection-Output
object
2 properties
PulmonaryOrderTest
object
2 properties 2 required
FollowupParagraph-Output
object
3 properties
ReferencedDocumentData
object
Structured reference to a hippo document (e.g. a lab/imaging report). Mirrors the VN1 reference-bullet payload: id is the report/document id, labresultid ident…
4 properties 1 required
FollowupListItem-Output
object
3 properties
VitalBMI
object
2 properties
NarrativeParagraph-Output
object
3 properties
InstructionsSection-Output
object
2 properties
CptCode
object
3 properties 3 required
PatientImmunizationAttrs-Output
object
3 properties 2 required
DocumentNodeChild-Output
LabOrderTest
object
3 properties 2 required
DocumentSignatureRole
string
The role the user is performing when adding a signature to a visit note
Attachment
object
A file attached to a note. Attachments are modeled as a top-level field on the note (not as note content) per the Simple Note 2.1 spec: they carry no positioni…
6 properties 4 required
CODE_TYPE
string
DocumentNode-Output
object
3 properties
HandoutBlock-Output
object
2 properties 1 required
CardiacOrderBlockAttrs-Output
object
3 properties 2 required
TextInline-Output
object
Plain text run. This node has NO attrs: both text and marks are top-level keys. This is the one deliberate exception to the type/attrs/content rule documented…
3 properties
HandoutTypeName
string
Handout kind. Hippo reconciles this into its integer type if needed.
ContentMap-Output
object
Typed map from section type to its content. All sections are optional. Keys match section type wire values (NodeType): lowercase single words (e.g. narrative,…
7 properties
Injection
object
14 properties 5 required
ImagingOrderTest
object
2 properties 2 required
TextInlineMark
object
A single formatting mark applied to a TextInline run.
1 property 1 required
ProcedureParagraph-Output
object
3 properties
el8_note_models__note__sections__shared__ReferralSummary
object
11 properties 1 required
ImagingOrderBlock-Output
object
2 properties 1 required
ReferralBlockAttrs
object
3 properties 2 required
Immunization
object
15 properties 3 required
ImagingOrderBlockAttrs-Output
object
3 properties 2 required
InstructionsParagraph-Output
object
3 properties
ImagingOrderSummary
object
10 properties 3 required
InjectionMethod
string
PaginatedResponse_NoteMetadata_
object
6 properties 4 required
NoteLayoutBlock
object
A section slot in the layout. type is the section identifier.
1 property 1 required
VitalOxygen
object
4 properties
el8_note_models__note__sections__shared__TextBlockMarkTypes
string
Formatting marks a text run can carry. Supports bold, italic, strike (strikethrough), and underline.
OrdersSection-Output
object
2 properties
ProcedureOrderedList-Output
object
3 properties
VitalPain
object
4 properties
ReferencedDocumentsSection-Output
object
2 properties
NarrativeListItem-Output
object
3 properties
ProcedureAttrs
object
2 properties 1 required
SleepOrderTest
object
2 properties 2 required
FollowupOrderedList-Output
object
3 properties
ValidationError
object
5 properties 3 required
LabOrderSummary
object
10 properties 4 required
Doctag
object
A doctag is an identifier that can be applied to a document. This implementation of doctag mirrors VN1's coded document tag
11 properties 5 required
CardiacOrderBlock-Output
object
2 properties 1 required
el8_note_models__note__sections__vitals_section__Vitals
object
11 properties
NoteLayoutHeader
object
Decorative section divider — display text only, no clinical meaning.
2 properties
SectionsContent
object
The sections-based note content: layout description + typed section content.
2 properties 2 required
InstructionsUnorderedList-Output
object
3 properties
VitalRR
object
4 properties
SleepOrderBlockAttrs-Output
object
3 properties 2 required
Layout
object
Structural description of a note. name identifies the template (e.g. "simplenote", "soap"). content lists columns (1 for single-column, 2 for two-column). Each…
2 properties 1 required
NoteAmendment
object
Full representation of a note amendment fetched from the DB Note Amendment is a clone of Note and is analogous to a VisitNoteEdit for a Visit Note 1
15 properties 8 required
InstructionParagraphAttrs
object
1 property
VitalHC
object
4 properties
VitalWeight
object
4 properties
ElationNote
object
Full representation of a sections-based note returned by the API. content holds the sections-based structure: layout (structural description) and contentmap (t…
19 properties 9 required
DocumentNode-Input
object
3 properties
PulmonaryOrderBlockAttrs-Output
object
3 properties 2 required
LabOrderFastingMethod
string
ProcedureUnorderedList-Output
object
3 properties
InjectionBlockAttrs-Output
object
3 properties 2 required
VitalsSection-Output
object
Tier-1 vitals section; attrs mirror VN2 VitalsNode.
2 properties
PrescriptionBlock-Output
object
2 properties 1 required
PrescriptionBlockAttrs
object
3 properties 2 required
PulmonaryOrderSummary
object
11 properties 3 required
NarrativeUnorderedList-Output
object
3 properties
NoteCreate
object
10 properties 4 required
ProcedureListItem-Output
object
3 properties
SleepOrderBlock-Output
object
2 properties 1 required
FollowupSection-Output
object
2 properties
PatientImmunizationBlock-Output
object
2 properties 1 required
CardiacOrderTest
object
2 properties 2 required
TwoColumnLayoutNode-Input
object
3 properties
InjectionDoseUnit
string
CardiacOrderSummary
object
11 properties 3 required
ReferencedDocument-Output
object
2 properties 1 required
LabOrderBlockAttrs-Output
object
3 properties 2 required
Handout
object
8 properties 3 required
AnyNodeContent
object
Placeholder for node content, eliminating cycles in OpenAPI schema generation. This should be replaced with any node content type when calling the API
NoteMetadata
object
A lightweight version of Note that omits certain fields for performance reasons, specifically for use with endpoints that return notes in bulk.
12 properties 7 required
VitalHeight
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

elation-health-notes-api-openapi.yml Raw ↑

Other APIs Elation Health publishes across the network.

Elation Health Allergies API
Elation Health Appointments API
Elation Health Authentication API
Elation Health Billing API
Elation Health Insurance API
Elation Health Lab Orders API
Elation Health Medications API
Elation Health Messaging API
Elation Health Patients API
Elation Health Physicians API
Elation Health Practices API
Elation Health Problems API
Where this information came from

This is an independent, third-party profile of Elation Health Notes API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.