Getting Started

  • Introduction
  • Concepts & Glossary
  • Quickstart
  • Authentication

API Reference

  • Endpoints
  • Error Handling
  • Versioning

Guides

  • Code Examples
  • FHIR R4 Integration
  • Integration Patterns
  • Going to Production

Medical Content

  • Knowledge Base

Tools

  • Interactive Sandbox
  • API Status

Resources

  • FAQ
  • Changelog
  • Support
Developers

Loading documentation…

Concepts & Glossary
PearMedica Logo

The clinical intelligence layer built for African healthcare. Empowering providers with AI-driven triage and decision support.

For Hospitals

  • PearCare EHR
  • Hospitals & Clinics
  • HMOs & Insurers
  • Pricing

For Developers

  • Documentation
  • API Reference
  • Symptom Assessment
  • Quickstart Guide
  • Code Examples

Company

  • About Us
  • Contact
  • Blog
  • Careers

Legal

  • Privacy Policy
  • Terms of Service
  • Security & Compliance
  • NDPA Compliance
Built to NDPA 2023
AES-256 Encryption
Audit Logging

© 2026 PearMedica. All rights reserved.

Status
Developer Portal

The PearMDx Engine, as a Clean API

PearMDx is the same clinical intelligence engine that powers the PearCare platform — available to your application as a clean REST API. Post symptoms, get back a structured differential diagnosis, triage level, and follow-up questions. This is everything you need to integrate it: API documentation, code examples, and an interactive sandbox.

Get StartedAPI Reference

The Same Engine That Powers PearCare

Hospitals run the PearMDx engine through the PearCare EHR, with no code required. Developers reach the very same engine through this API. One core, two front doors.

One Engine, Two Front Doors

The PearMDx clinical engine reaches developers through this REST API and hospitals through the PearCare platform. Same reasoning, same knowledge base, same safety net — exposed two ways.

Clinical Intelligence as an API

Post symptoms and demographics, get back a differential diagnosis, a triage level, follow-up questions, red flags, and recommended investigations — structured JSON your application can act on directly.

Built for African Healthcare

The engine is tuned for African disease prevalence and local symptom terminology, with location-aware weighting — not a generic Western model wrapped in an endpoint.

Documentation

Quickstart

Integrate in under 5 minutes with JavaScript, Python, or cURL.

API Reference

Complete documentation for all 13 documented v1 endpoints, including FHIR R4.

Code Examples

Copy-paste examples for assessment, parsing, and conversational flow.

Interactive Sandbox

Test API calls live in your browser with pre-filled requests.

What the Engine Does

Behind every PearMedica API call is PearMDx — a retrieval-augmented clinical decision support engine grounded in a curated African knowledge base, with multiple independent safety layers ensuring clinical reliability.

Emergency Detection

A rules-based safety layer flags life-threatening symptom combinations immediately — before the full assessment completes — so red flags surface first. It is designed to minimise missed critical presentations, with ongoing validation under clinical governance.

African Disease Intelligence

Assessments are grounded in a curated knowledge base built for conditions prevalent across Africa — 30 conditions fully modelled for MVP, with the knowledge base expanding toward broader African coverage. Not generic Western training data.

6-Layer Validation

Every AI output passes through a 6-layer safety net of independent checks — including hallucination detection, emergency pattern matching, and WHO-guideline compliance — before reaching your application. No single point of failure.

Smart Triage

4-level urgency scoring — Emergency, Urgent, Routine or Self-Care — with nearest-facility recommendations based on patient location.

Graceful Degradation

If the AI engine is temporarily unavailable, PearMDx serves safe rule-based responses and reports its status via the health endpoint — your integration degrades gracefully instead of failing hard.

PearMDx Chatbot

Built-in AI clinical assistant available to staff via PearCare. Answers questions about patients, assessments, and clinical protocols using real facility data.

What You Can Build

The API is language-agnostic — any stack that can make an HTTP request works. Here is what teams build on it.

Triage Kiosks & Symptom Checkers

Pre-assess patients at registration or in a 24/7 mobile symptom checker, then route them to the right level of care.

Telemedicine Pre-Consultation

Capture and structure the patient story before the clinician joins, so consultations start with a differential already in hand.

Clinical Decision Support

Surface differentials, red flags and recommended investigations inside your existing EHR or nursing-intake workflow.

FHIR-Native Integrations

Send and receive standard FHIR R4 Bundles against /v1/fhir/assess, with a published CapabilityStatement for auto-discovery.

Integration in 3 Lines

javascript
// Assess patient symptoms with one API call
const response = await fetch('https://api.pearmedica.com/v1/assess', {
method: 'POST',
headers: {
'Authorization': 'Bearer sk_live_your_api_key',
'Content-Type': 'application/json',
},
body: JSON.stringify({
patient: { age: 28, sex: 'female', location: 'lagos_nigeria' },
evidence: [
{ id: 's_fever', choice_id: 'present', duration_days: 3 },
{ id: 's_headache', choice_id: 'present', severity: 'severe' },
],
}),
});
const { conditions, triage, next_question } = await response.json();
// → conditions: [{ name: "Malaria", probability: "high", ... }]
// → triage: { level: "urgent", recommended_action: "..." }

Don't want to build the integration yourself?

The same engine ships fully wired into PearCare — a complete EHR with outpatient records, billing, inpatient, pharmacy and a patient portal — no code required.

Explore PearCare EHR