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

Devoted Health MedicationKnowledge API

The MedicationKnowledge FHIR resource type

Devoted Health MedicationKnowledge API is one of 23 APIs that Devoted Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include MedicationKnowledge. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 22 operations across 14 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 6.6.0.

Requests are made against a single base URL, https://fhir.devoted.com/fhir.

22 operations 14 paths 2 schemas 1 DELETE10 GET1 PATCH9 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
6.6.0
Base URL
https://api.prod.devoted.com/fhir
Resource Areas
1

Paths & Operations 22

Across 14 paths, the API surfaces 22 operations — 1 DELETE, 10 GET, 1 PATCH, 9 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

MedicationKnowledge 22

The MedicationKnowledge FHIR resource type

GET
/MedicationKnowledge/{id}
read-instance: Read MedicationKnowledge instance
getMedicationKnowledgeById 1 param → 200
PUT
/MedicationKnowledge/{id}
update-instance: Update an existing MedicationKnowledge instance, or create…
putMedicationKnowledgeById 1 param body → 200
DELETE
/MedicationKnowledge/{id}
instance-delete: Perform a logical delete on a resource instance
deleteMedicationKnowledgeById 1 param → 200
PATCH
/MedicationKnowledge/{id}
instance-patch: Patch a resource instance of type MedicationKnowledge by ID
patchMedicationKnowledgeById 1 param body → 200
GET
/MedicationKnowledge/{id}/_history/{version_id}
vread-instance: Read MedicationKnowledge instance with specific version
getMedicationKnowledgeByIdHistoryByVersionId 2 params → 200
GET
/MedicationKnowledge
search-type: Search for MedicationKnowledge instances
getMedicationKnowledge 24 params → 200
POST
/MedicationKnowledge
create-type: Create a new MedicationKnowledge instance
postMedicationKnowledge body → 200
GET
/MedicationKnowledge/_history
type-history: Fetch the resource change history for all resources of type…
getMedicationKnowledgeHistory → 200
GET
/MedicationKnowledge/{id}/_history
instance-history: Fetch the resource change history for all resources of type…
getMedicationKnowledgeByIdHistory 1 param → 200
GET
/MedicationKnowledge/_search
search-type: Search for MedicationKnowledge instances
getMedicationKnowledgeSearch 24 params → 200
GET
/MedicationKnowledge/$validate
Get medication knowledge $validate
getMedicationKnowledge$validate 1 param → 200
POST
/MedicationKnowledge/$validate
Create medication knowledge $validate
postMedicationKnowledge$validate body → 200
GET
/MedicationKnowledge/{id}/$validate
Get medication knowledge by id $validate
getMedicationKnowledgeById$validate 2 params → 200
POST
/MedicationKnowledge/{id}/$validate
Create medication knowledge by id $validate
postMedicationKnowledgeById$validate 1 param body → 200
POST
/MedicationKnowledge/{id}/$meta-delete
Create medication knowledge by id $meta delete
postMedicationKnowledgeById$metaDelete 1 param body → 200
POST
/MedicationKnowledge/{id}/$meta-add
Create medication knowledge by id $meta add
postMedicationKnowledgeById$metaAdd 1 param body → 200
GET
/MedicationKnowledge/$meta
Get medication knowledge $meta
getMedicationKnowledge$meta → 200
POST
/MedicationKnowledge/$meta
Create medication knowledge $meta
postMedicationKnowledge$meta body → 200
GET
/MedicationKnowledge/{id}/$meta
Get medication knowledge by id $meta
getMedicationKnowledgeById$meta 1 param → 200
POST
/MedicationKnowledge/{id}/$meta
Create medication knowledge by id $meta
postMedicationKnowledgeById$meta 1 param body → 200
POST
/MedicationKnowledge/$expunge
Create medication knowledge $expunge
postMedicationKnowledge$expunge body → 200
POST
/MedicationKnowledge/{id}/$expunge
Create medication knowledge by id $expunge
postMedicationKnowledgeById$expunge 1 param body → 200

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

devoted-health-medicationknowledge-api-openapi.yml Raw ↑

Other APIs Devoted Health publishes across the network.

Devoted Health CodeSystem API
Devoted Health Condition API
Devoted Health Encounter API
Devoted Health ExplanationOfBenefit API
Devoted Health List API
Devoted Health Location API
Devoted Health Medication API
Devoted Health OperationDefinition API
Devoted Health Organization API
Devoted Health OrganizationAffiliation API
Devoted Health Patient API
Devoted Health Practitioner API
Where this information came from

This is an independent, third-party profile of Devoted Health MedicationKnowledge 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.