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 v2 API

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

Elation Health Notes v2 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 v2. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and a changelog.

This API exposes 13 operations across 7 paths, and defines 158 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.

13 operations 7 paths 158 schemas 3 DELETE5 GET3 PATCH2 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 v2 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 13

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

Notes v2 13
GET
/v2/notes
List Notes V2
list_notes_v2 6 params → 200422
POST
/v2/notes
Create Note V2
create_note_v2 body → 201422
DELETE
/v2/notes/{note_id}
Delete Note By Id V2
delete_note_by_id_v2 1 param → 204422
GET
/v2/notes/{note_id}
Get Note By Id V2
get_note_by_id_v2 1 param → 200422
PATCH
/v2/notes/{note_id}
Update Note By Id V2
update_note_by_id_v2 1 param body → 200422
POST
/v2/notes/{note_id}/amendments
Create Note Amendment V2
create_note_amendment_v2 1 param → 201422
DELETE
/v2/notes/{note_id}/amendments/{amendment_id}
Delete Note Amendment By Id V2
delete_note_amendment_by_id_v2 2 params → 204422
GET
/v2/notes/{note_id}/amendments/{amendment_id}
Get Note Amendment By Id V2
get_note_amendment_by_id_v2 2 params → 200422
PATCH
/v2/notes/{note_id}/amendments/{amendment_id}
Update Note Amendment By Id V2
update_note_amendment_by_id_v2 2 params body → 200422
GET
/v2/notes/{note_id}/doctags
List Note Doctags V2
list_note_doctags_v2 1 param → 200422
PATCH
/v2/notes/{note_id}/doctags
Add Doctag To Note V2
add_doctag_to_note_v2 1 param body → 200422
DELETE
/v2/notes/{note_id}/doctags/{doctag_id}
Delete Doctag V2
delete_doctag_v2 2 params → 204422
GET
/v2/notes/{note_id}/edit
Get Note For Edit V2
get_note_for_edit_v2 1 param → 200422

Schemas 158

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

HandoutBlock-Input
object
2 properties 1 required
LabOrderBlock-Output
object
2 properties 1 required
FollowupParagraphAttrs
object
1 property
SleepOrderBlock-Input
object
2 properties 1 required
VitalTemperature
object
4 properties
FollowupParagraph-Output
object
3 properties
Handout
object
8 properties 3 required
Injection
object
14 properties 5 required
CardiacOrderSummary
object
11 properties 3 required
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
ProcedureOrderedList-Input
object
3 properties
PulmonaryOrderSummary
object
11 properties 3 required
ImagingOrderBlock-Output
object
2 properties 1 required
AttrsWithRefId
object
Base attrs for any node that carries a stable change-tracking refid.
1 property
el8_note_models__note__sections__shared__TextBlockMarkTypes
string
Formatting marks a text run can carry. Supports bold, italic, strike (strikethrough), and underline.
FollowupListItem-Input
object
3 properties
ContentMap-Input
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
ProcedureSection-Input
object
2 properties
CardiacOrderTest
object
2 properties 2 required
InstructionsListItem-Output
object
3 properties
CptCode
object
3 properties 3 required
FollowupSection-Output
object
2 properties
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
InstructionsParagraph-Output
object
3 properties
VitalPain
object
4 properties
LabOrderBlock-Input
object
2 properties 1 required
PulmonaryOrderBlock-Input
object
2 properties 1 required
ProcedureUnorderedList-Input
object
3 properties
PatientImmunizationAttrs-Input
object
3 properties 2 required
NarrativeListItem-Input
object
3 properties
FollowupUnorderedList-Input
object
3 properties
LabOrderTest
object
3 properties 2 required
VitalBMI
object
2 properties
HandoutBlockAttrs-Input
object
3 properties 2 required
Procedure-Output
object
2 properties 1 required
PatientImmunizationBlock-Output
object
2 properties 1 required
PrescriptionBlockAttrs
object
3 properties 2 required
InstructionsOrderedList-Input
object
3 properties
ImagingOrderBlock-Input
object
2 properties 1 required
ImagingOrderBlockAttrs-Output
object
3 properties 2 required
ElationNoteAmendmentUpdate
object
Request body for updating a sections-based note amendment. All fields optional. contentmap replaces the full stored contentmap. Amendment updates do not suppor…
8 properties
CardiacOrderBlockAttrs-Input
object
3 properties 2 required
ValidationError
object
5 properties 3 required
el8_note_models__note__sections__vitals_section__Vitals
object
11 properties
ReferencedDocument-Output
object
2 properties 1 required
LineBreakInline
object
Hard line break. No attrs, no content.
1 property
VitalWeight
object
4 properties
PatientImmunizationBlock-Input
object
2 properties 1 required
VitalHC
object
4 properties
PulmonaryOrderBlockAttrs-Output
object
3 properties 2 required
HandoutBlock-Output
object
2 properties 1 required
VitalHeight
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
SectionsContent
object
The sections-based note content: layout description + typed section content.
2 properties 2 required
ImmunizationVaccine
object
1 property
NarrativeListItem-Output
object
3 properties
FollowupParagraph-Input
object
3 properties
ReferencedDocumentsSection-Input
object
2 properties
HandoutTypeName
string
Handout kind. Hippo reconciles this into its integer type if needed.
ProcedureOrderedList-Output
object
3 properties
PatientImmunizationAttrs-Output
object
3 properties 2 required
TextInline-Input
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
PulmonaryOrderBlock-Output
object
2 properties 1 required
FollowupOrderedList-Input
object
3 properties
InjectionBlock-Output
object
2 properties 1 required
el8_note_models__note__sections__shared__ReferralSummary
object
11 properties 1 required
PrescriptionSummary
object
17 properties 3 required
NoteLayoutHeader
object
Decorative section divider — display text only, no clinical meaning.
2 properties
SleepOrderSummary
object
10 properties 3 required
Procedure-Input
object
2 properties 1 required
ReferralBlock-Input
object
2 properties 1 required
PulmonaryOrderBlockAttrs-Input
object
3 properties 2 required
InstructionsListItem-Input
object
3 properties
NarrativeParagraph-Output
object
3 properties
VitalsSectionAttrs-Input
object
3 properties
LabOrderBlockAttrs-Input
object
3 properties 2 required
InstructionParagraphAttrs
object
1 property
OrdersSection-Input
object
2 properties
FollowupUnorderedList-Output
object
3 properties
InjectionBlockAttrs-Input
object
3 properties 2 required
ImagingOrderTest
object
2 properties 2 required
FollowupSection-Input
object
2 properties
SleepOrderBlockAttrs-Input
object
3 properties 2 required
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
NarrativeSection-Input
object
2 properties
ProcedureListItem-Output
object
3 properties
VitalsSectionAttrs-Output
object
3 properties
ProcedureUnorderedList-Output
object
3 properties
NoteLayoutBlock
object
A section slot in the layout. type is the section identifier.
1 property 1 required
CODE_TYPE
string
VitalOxygen
object
4 properties
ProcedureParagraph-Output
object
3 properties
InjectionMethod
string
ReferralBlock-Output
object
2 properties 1 required
ElationNoteCreate
object
Request body for creating a sections-based note. The layout is selected by layoutname (e.g. "simplenote"). No content field — the initial contentmap is always…
10 properties 5 required
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
InjectionDoseUnit
string
SleepOrderTest
object
2 properties 2 required
DocumentSignature
object
A signature on a document.
8 properties 5 required
ReferencedDocumentsSection-Output
object
2 properties
ImagingOrderBlockAttrs-Input
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
NoteLayoutColumn
object
2 properties
InjectionBlockAttrs-Output
object
3 properties 2 required
VitalFiO2
object
4 properties
InstructionsParagraph-Input
object
3 properties
CardiacOrderBlock-Output
object
2 properties 1 required
FollowupListItem-Output
object
3 properties
TextInlineMark
object
A single formatting mark applied to a TextInline run.
1 property 1 required
InstructionsSection-Output
object
2 properties
HandoutBlockAttrs-Output
object
3 properties 2 required
ReferralBlockAttrs
object
3 properties 2 required
ProcedureParagraph-Input
object
3 properties
DocumentSignatureRole
string
The role the user is performing when adding a signature to a visit note
LabOrderBlockAttrs-Output
object
3 properties 2 required
VitalHR
object
4 properties
NarrativeOrderedList-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
ProcedureSection-Output
object
2 properties
PulmonaryOrderTest
object
2 properties 2 required
PrescriptionBlock-Input
object
2 properties 1 required
CardiacOrderBlock-Input
object
2 properties 1 required
SleepOrderBlockAttrs-Output
object
3 properties 2 required
ElationNoteUpdate
object
Request body for updating a sections-based note. When contentmap is sent on a base note update, snapshotid is required (from create or GET /notes/{id}/edit) fo…
9 properties
NarrativeOrderedList-Output
object
3 properties
ProcedureAttrs
object
2 properties 1 required
ReferencedDocumentAttrs
object
2 properties 1 required
NarrativeUnorderedList-Input
object
3 properties
InstructionsSection-Input
object
2 properties
InstructionsUnorderedList-Output
object
3 properties
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
PaginatedResponse_NoteMetadata_
object
6 properties 4 required
LabOrderFastingMethod
string
SleepOrderBlock-Output
object
2 properties 1 required
OrdersSection-Output
object
2 properties
NarrativeParagraphAttrs
object
1 property
HTTPValidationError
object
1 property
FollowupOrderedList-Output
object
3 properties
PrescriptionBlock-Output
object
2 properties 1 required
VitalsSection-Output
object
Tier-1 vitals section; attrs mirror VN2 VitalsNode.
2 properties
ReferencedDocument-Input
object
2 properties 1 required
Immunization
object
15 properties 3 required
ProcedureListItem-Input
object
3 properties
NarrativeSection-Output
object
2 properties
VitalsSection-Input
object
Tier-1 vitals section; attrs mirror VN2 VitalsNode.
2 properties
InstructionsOrderedList-Output
object
3 properties
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
CardiacOrderBlockAttrs-Output
object
3 properties 2 required
ImagingOrderSummary
object
10 properties 3 required
VitalRR
object
4 properties
NarrativeUnorderedList-Output
object
3 properties
NarrativeParagraph-Input
object
3 properties
VitalBP
object
5 properties
CreateDoctagRequest
object
10 properties 2 required
InjectionBlock-Input
object
2 properties 1 required
InstructionsUnorderedList-Input
object
3 properties
ProcedureParagraphAttrs
object
1 property
LabOrderSummary
object
10 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

elation-health-notes-v2-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 v2 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.