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

ModMed Clinical Data/Clipboard API

Clinical Data/Clipboard details

ModMed Clinical Data/Clipboard API is one of 43 APIs that ModMed publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Clinical Data/Clipboard. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

This API exposes 18 operations across 12 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 3.4.3_FINAL.

Requests are made against a single base URL, https://stage.ema-api.com/ema-dev/firm/apiportal/ema.

18 operations 12 paths 2 schemas 12 GET3 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.4.3_FINAL
Base URL
https://stage.ema-api.com/ema-dev/firm/apiportal/ema
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

ModMed Clinical Data/Clipboard API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

  • BearerAuth — OAuth2 access token (JWT). Obtain it via the legacy password grant or the new clientcredentials flow (see the Authentication guide), then send as Authorization…
  • ApiKeyAuth — Shared sandbox API key (public sandbox only). Send as the x-api-key header. Zt9tXPIgz17uxEU6gkZPWa3ZAFhZOqm04oEDHC1f

Paths & Operations 18

Across 12 paths, the API surfaces 18 operations — 12 GET, 3 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Clinical Data/Clipboard 18

Clinical Data/Clipboard details

GET
/fhir/v2/AllergyIntolerance/{id}
Retrieve AllergyIntolerance details for an AllergyIntolerance ID
1 param → 200400401403404422429500
PUT
/fhir/v2/AllergyIntolerance/{id}
Update AllergyIntolerance resource
1 param body → 200400401403404422429500
GET
/fhir/v2/AllergyIntolerance
Retrieve AllergyIntolerance resources by the specified search criteria
1 param → 200400401403404422429500
POST
/fhir/v2/AllergyIntolerance
Create AllergyIntolerance resource
body → 200201400401403404422429
GET
/fhir/v2/Condition/{id}
Retrieve Condition details for an ID
1 param → 200400401403404422429500
PUT
/fhir/v2/Condition/{id}
Update Condition resource
1 param body → 200400401403404422429500
GET
/fhir/v2/Condition
Retrieve Condition resources by the specified search criteria
1 param → 200400401403404422429500
POST
/fhir/v2/Condition
Create Condition resource
body → 200201400401403404422429
GET
/fhir/v2/DiagnosticReport/{id}
Retrieve DiagnosticReport for an ID
1 param → 200400401403404422429500
GET
/fhir/v2/DiagnosticReport
Search DiagnosticReport by certain parameters
7 params → 200400401403404422429500
GET
/fhir/v2/FamilyMemberHistory/{id}
Retrieve FamilyMemberHistory details for an ID
1 param → 200400401403404422429500
GET
/fhir/v2/FamilyMemberHistory
Retrieve FamilyMemberHistory resources by the specified search criteria
3 params → 200400401403404422429500
GET
/fhir/v2/MedicationStatement/{id}
Retrieve MedicationStatement details for a Medication Statement ID
1 param → 200400401403404422429500
PUT
/fhir/v2/MedicationStatement/{id}
Update MedicationStatement resource
1 param body → 200400401403404422429500
GET
/fhir/v2/MedicationStatement
Retrieve MedicationStatement resources by the specified search criteria
3 params → 200400401403404422429500
POST
/fhir/v2/MedicationStatement
Create MedicationStatement resource
body → 200201400401403404422429
GET
/fhir/v2/ServiceRequest/{id}
Retrieve ServiceRequest for an ID
1 param → 200400401403404422429500
GET
/fhir/v2/ServiceRequest
Search ServiceRequests by certain parameters
10 params → 200400401403404422429500

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

FHIR-XML-RESOURCE
object
A FHIR resource
FHIR-JSON-RESOURCE
object
A FHIR resource

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

modernizing-medicine-clinical-data-clipboard-api-openapi.yml Raw ↑

Other APIs ModMed publishes across the network.

ModMed Allergy Intolerance API
ModMed Appointments and Slots API
ModMed Authentication API
ModMed Capability Statement API
ModMed Care Plan API
ModMed Care Team API
ModMed Charges/Financial API
ModMed Condition API
ModMed Coverage API
ModMed Device API
ModMed Diagnostic Report API
ModMed Document Reference API
Where this information came from

This is an independent, third-party profile of ModMed Clinical Data/Clipboard 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.