Standard API (OpenEMR REST)

Complete guide to OpenEMR's Standard REST API for native OpenEMR resources.

Overview
Prerequisites
Base URL
Authentication
API Endpoints
Patient Portal API
Request/Response Format
Error Handling
Validation
Examples
Swagger Documentation

Overview

The OpenEMR Standard REST API provides access to OpenEMR's native data structures through RESTful endpoints. This API is designed for:

✅ OpenEMR-specific operations - Native data structures
✅ Custom integrations - Direct access to OpenEMR tables
✅ Administrative functions - User management, facilities, etc.
✅ Legacy system integration - Non-FHIR compatible systems

When to Use Standard API vs FHIR API

Use Standard API When	Use FHIR API When
Need OpenEMR-specific data structures	Need healthcare interoperability
Integrating with existing OpenEMR workflows	Building standards-compliant apps
Require direct table access	Need vendor-neutral data model
Administrative/operational tasks	Clinical data exchange
Legacy system integration	SMART on FHIR apps required

Recommendation: For new healthcare applications, use the FHIR API for better interoperability.

Prerequisites

1. Enable Standard API

Navigate to: Administration → Config → Connectors

Enable: ☑ Enable OpenEMR Standard REST API

2. Configure SSL/TLS

Required: All API endpoints require HTTPS/TLS.

Set base URL: Administration → Config → Connectors → Site Address (required for OAuth2 and FHIR)

3. Register API Client

See Authentication Guide for OAuth2 client registration.

Required scopes: At minimum openid + api:oemr + resource-specific scopes.

Example:

openid api:oemr user/patient.rs user/encounter.rs

See Authorization Guide for complete scope listing.

Base URL

Standard API endpoints use the following base URL pattern:

https://{your-openemr-host}/apis/{site}/api

Default Site

https://localhost:9300/apis/default/api

Multisite Example

https://localhost:9300/apis/alternate/api

Endpoint Structure

{base}/[resource]
{base}/[resource]/[id]
{base}/[resource]/[id]/[sub-resource]

Examples:

GET https://localhost:9300/apis/default/api/patient
GET https://localhost:9300/apis/default/api/patient/123
GET https://localhost:9300/apis/default/api/patient/123/encounter

Authentication

All Standard API requests require authentication via Bearer token.

Request Format

bash

curl -X GET 'https://localhost:9300/apis/default/api/patient' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Accept: application/json'

Obtaining Access Token

See Authentication Guide for OAuth2 flows:

Token in Request Header

http

GET /apis/default/api/patient HTTP/1.1
Host: localhost:9300
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9...
Accept: application/json

API Endpoints

Standard API (swagger)

Resource	permissions	Description
Facility	crus	Manage facility/service location information (`facility` table).
Patient	crus	Manage patient demographics and registration (`patient_data` table).
Encounter	crus	Manage patient encounters and visits. (`form_encounter` table).
Soap Note	crus	Manage Encounter Form SOAP Notes (`form_soap` table).
Vitals	crus	Manage Patient Vitals (`form_vitals`,`form_vital_details` table).
Practitioner	rus	Manage practitioner information (`users` table).
Medical Problem	cruds	Manage patient medical problems and conditions (`lists` table).
Allergies	cruds	Manage patient allergies (`lists` table).
Medications	cruds	Manage patient medications (`lists` table).
Surgery Issues	cruds	Manage patient surgical issues (`lists` table).
Dental Issues	cruds	Manage patient dental issues (`lists` table).
Appointments	crus	Manage patient appointments (`pc_event` table).
Lists	rs	Read-only access to lists (`lists` table).
Users	rs	Read-only access to users (`users` table).
Insurance Company	crus	Manage insurance companies (`insurance_data` table).
Patient Documents	crs	Manage patient documents (`documents` table).
Patient Employers	rs	Read-only access to patient employers (`employers` table).
Patient Insurance	crus	Manage patient insurance information (`patient_insurance` table).
Patient Messages	cud	Create patient messages (`patient_messages` table).
Patient Referrals (transactions)	cruds	Manage patient referrals (`lbt_data` table).
Patient Immunizations	rs	Read-only access to patient immunizations (`immunizations` table).
Patient Procedures	rs	Read-only access to patient procedures (`procedure_order`,`procedure_report`,`procedure_result` table).
Drugs	rs	Read-only access to drugs (`drugs` table).
Prescriptions	rs	Read-only access to prescriptions (`prescriptions` table).

Permissions	Description
c	Create resource
r	Read resource
u	Update resource
d	Delete resource
s	Search/List resources

Patient Portal API (swagger)

EXPERIMENTAL - Patient-facing API endpoints.

Enable Portal API

Administration → Config → Connectors

☑ Enable OpenEMR Patient Portal REST API (EXPERIMENTAL)

Base URL

https://localhost:9300/apis/default/portal

Resource	permissions	Description
Patient	r	Get logged in patient's demographics and info.
Encounter	rs	Get logged in patient's encounters and visits.
Appointment	rs	Get logged in patient's appointments.

Permissions	Description
c	Create resource
r	Read resource
u	Update resource
d	Delete resource
s	Search/List resources

Authentication

Patients must have API credentials generated by their clinician:

Navigate to patient demographics
Click API Credentials button
Generate credentials for patient

See Authentication Guide for OAuth2 flows:

Patients authenticate using Password Grant with user_role=patient.

Limitations

⚠️ Portal API is experimental:

Limited endpoint coverage
Subject to changes
Use FHIR API with patient/* scopes instead

Request/Response Format

Standard Response Format

All Standard API responses use a consistent format:

json

{
  "validationErrors": [],
  "internalErrors": [],
  "data": <result>
}

Fields:

validationErrors - Array of validation errors (client-side)
internalErrors - Array of server errors
data - Response payload (object for single result, array for multiple)

Success Response

Single Resource:

json

{
  "validationErrors": [],
  "internalErrors": [],
  "data": {
    "id": "1",
    "uuid": "90cde167-7b9b-4ed1-bd55-533925cb2605",
    "fname": "John",
    "lname": "Smith"
  }
}

Multiple Resources:

json

{
  "validationErrors": [],
  "internalErrors": [],
  "data": [
    {"id": "1", "fname": "John", "lname": "Smith"},
    {"id": "2", "fname": "Jane", "lname": "Doe"}
  ]
}

Error Response

Validation Error:

json

{
  "validationErrors": [
    "The fname field is required.",
    "The DOB field must be a valid date."
  ],
  "internalErrors": [],
  "data": []
}

Internal Error:

json

{
  "validationErrors": [],
  "internalErrors": [
    "Database connection failed"
  ],
  "data": []
}

Error Handling

HTTP Status Codes

Code	Meaning	Common Causes
200	OK	Successful GET/PUT/PATCH request
201	Created	Successful POST request
400	Bad Request	Invalid request format
401	Unauthorized	Missing or invalid token
403	Forbidden	Insufficient scopes
404	Not Found	Resource doesn't exist
422	Unprocessable Entity	Validation error
500	Internal Server Error	Server error

Common Errors

401 Unauthorized

json

{
  "error": "invalid_token",
  "error_description": "The access token is missing"
}

Solution: Include Authorization: Bearer TOKEN header

403 Forbidden

json

{
  "validationErrors": [],
  "internalErrors": ["Insufficient scope for requested resource"],
  "data": []
}

Solution: Request appropriate scopes during authorization

404 Not Found

json

{
  "validationErrors": [],
  "internalErrors": ["Resource not found"],
  "data": []
}

Solution: Verify resource UUID exists

422 Validation Error

json

{
  "validationErrors": [
    "The fname field is required.",
    "The DOB must be a date in the format Y-m-d."
  ],
  "internalErrors": [],
  "data": []
}

Solution: Fix request data validation errors

Validation

UUID Format

All UUIDs must be valid UUID v4 format:

90cde167-7b9b-4ed1-bd55-533925cb2605

Date Format

All dates use ISO 8601 format:

YYYY-MM-DD

Example: 2024-01-15

Examples

Example 1: Create Patient

bash

curl -X POST 'https://localhost:9300/apis/default/api/patient' \
  -H 'Authorization: Bearer eyJ0eXAiOiJKV1Qi...' \
  -H 'Content-Type: application/json' \
  --data '{
    "title": "Mr",
    "fname": "John",
    "lname": "Smith",
    "DOB": "1980-01-15",
    "sex": "Male",
    "street": "123 Main St",
    "city": "Boston",
    "state": "MA",
    "postal_code": "12345",
    "phone_home": "555-1234",
    "email": "[email protected]"
  }'

Example 2: Search Patients

bash

curl -X GET 'https://localhost:9300/apis/default/api/patient?lname=Smith&city=Boston' \
  -H 'Authorization: Bearer eyJ0eXAiOiJKV1Qi...'

Example 3: Get Patient Encounters

bash

curl -X GET 'https://localhost:9300/apis/default/api/patient/90cde167-7b9b-4ed1-bd55-533925cb2605/encounter' \
  -H 'Authorization: Bearer eyJ0eXAiOiJKV1Qi...'

Example 4: Create Appointment

bash

curl -X POST 'https://localhost:9300/apis/default/api/appointment' \
  -H 'Authorization: Bearer eyJ0eXAiOiJKV1Qi...' \
  -H 'Content-Type: application/json' \
  --data '{
    "pc_catid": "5",
    "pc_title": "Annual Physical",
    "pc_duration": "1800",
    "pc_eventDate": "2024-02-15",
    "pc_startTime": "09:00:00",
    "pc_facility": "1",
    "pid": "1"
  }'

Example 5: Upload Document

bash

curl -X POST 'https://localhost:9300/apis/default/api/patient/90cde167-7b9b-4ed1-bd55-533925cb2605/document' \
  -H 'Authorization: Bearer eyJ0eXAiOiJKV1Qi...' \
  -F 'file=@/path/to/lab-results.pdf' \
  -F 'path=Lab Reports' \
  -F 'date=2024-01-15'

Example 6: Add Allergy

bash

curl -X POST 'https://localhost:9300/apis/default/api/patient/90cde167-7b9b-4ed1-bd55-533925cb2605/allergy' \
  -H 'Authorization: Bearer eyJ0eXAiOiJKV1Qi...' \
  -H 'Content-Type: application/json' \
  --data '{
    "title": "Penicillin",
    "begdate": "2020-01-15",
    "diagnosis": "Allergy to penicillin",
    "severity_al": "severe",
    "reaction": "Hives"
  }'

Example 7: Record Vitals

bash

curl -X POST 'https://localhost:9300/apis/default/api/patient/90cde167-7b9b-4ed1-bd55-533925cb2605/vital' \
  -H 'Authorization: Bearer eyJ0eXAiOiJKV1Qi...' \
  -H 'Content-Type: application/json' \
  --data '{
    "date": "2024-01-15",
    "bps": "120",
    "bpd": "80",
    "weight": "180",
    "height": "70",
    "temperature": "98.6",
    "pulse": "72",
    "respiration": "16"
  }'

Swagger Documentation

Interactive Testing

Test Standard API endpoints interactively with Swagger UI:

https://your-openemr-install/swagger/

Navigate to the standard section in Swagger UI.

Online Demos

Test against live demo instances:

Demo Portal: https://www.open-emr.org/wiki/index.php/Development_Demo
Click: "API (Swagger) User Interface" link

Configure Swagger OAuth

Set your client's redirect URI to:

<OpenEMR base URI>/swagger/oauth2-redirect.html

Example:

https://localhost:9300/swagger/oauth2-redirect.html

Next Steps:

Review Authentication for OAuth2 setup
See Authorization for scope details
Learn about FHIR API for standards-based integration
Check Developer Guide for advanced topics

Support:

Community Forum: https://community.open-emr.org/
GitHub Issues: https://github.com/openemr/openemr/issues
API Development Thread: https://community.open-emr.org/t/v6-authorization-and-api-changes-afoot/15450

Recommendation: For new integrations, consider using the FHIR API for better interoperability and standards compliance.

Documentation Attribution

Authorship

This documentation represents the collective knowledge and contributions of the OpenEMR open-source community. The content is based on:

Original documentation by OpenEMR developers and contributors
Technical specifications from the OpenEMR codebase
Community feedback and real-world implementation experience

AI Assistance

The organization, structure, and presentation of this documentation was enhanced using Claude AI (Anthropic) to:

Reorganize content into a more accessible modular structure
Add comprehensive examples and use cases
Improve navigation and cross-referencing
Enhance clarity and consistency across documents

All technical accuracy is maintained from the original community-authored documentation.

Contributing

OpenEMR is an open-source project. To contribute to this documentation:

Report Issues: GitHub Issues
Discuss: Community Forum
Submit Changes: Pull Requests

Last Updated: November 2025 License: GPL v3

For complete documentation, see Documentation/api/

Standard API (OpenEMR REST)

Standard API (OpenEMR REST)

Table of Contents

Overview

When to Use Standard API vs FHIR API

Prerequisites

1. Enable Standard API

2. Configure SSL/TLS

3. Register API Client

Base URL

Default Site

Multisite Example

Endpoint Structure

Authentication

Request Format

Obtaining Access Token

Token in Request Header

API Endpoints

Standard API (swagger)

Patient Portal API (swagger)

Enable Portal API

Base URL

Authentication

Limitations

Request/Response Format

Standard Response Format

Success Response

Error Response

Error Handling

HTTP Status Codes

Common Errors

Validation

UUID Format

Date Format

Examples

Example 1: Create Patient

Example 2: Search Patients

Example 3: Get Patient Encounters

Example 4: Create Appointment

Example 5: Upload Document

Example 6: Add Allergy

Example 7: Record Vitals

Swagger Documentation

Interactive Testing

Online Demos

Configure Swagger OAuth

Documentation Attribution

Authorship

AI Assistance

Contributing