Clinical platform + partner API

The clinical system, with an interface you can inspect.

TrueEHR is the clinical system of record behind TrueEval. The public developer reference exposes the integration contract before you talk to sales.

Read the developer reference Scope an integration
Partner API · v1.7

Endpoints

GET/patients
GET/visits
POST/intake
GET/fhir

Patient resource

200 OK
{
  "contract_version": "v1.7",
  "resourceType": "Bundle",
  "type": "searchset",
  "entry": [{
    "resource": {
      "resourceType": "Patient",
      "id": "ptn_••••••"
    }
  }]
}

15

Documented endpoints

11

Webhook events

4

Integration scopes

FHIR R4

Resource access

C-CDA 2.1

Document export

HMAC-SHA256

Webhook signing

v1.7

Current contract

Architecture

Keep the brand layer. Connect the regulated layer.

The interface separates the customer-facing experience from the clinical responsibilities that belong inside the medical-group model.

Layer 01

Your experience

Brand, acquisition, commerce, and the commercial relationship.

Layer 02

Partner interface

Scoped requests, versioned responses, signed events, and export paths.

Layer 03

Clinical system

Visits, prescribing workflows, records, labs, pharmacy coordination, and oversight.

Technical proof

Four claims a technical buyer can challenge.

Portable clinical records

FHIR R4 resources, C-CDA 2.1 documents, and a patient-bundle export path make record portability an interface question, not a sales promise.

FHIR R4 · C-CDA 2.1

Versioned integration contract

Responses carry a contract version and the developer reference publishes endpoint shapes, scopes, rate limits, and limitations.

"contract_version": "v1.7"

Signed operational events

Eleven events cover intake, visits, prescriptions, labs, chart review, and payments, with HMAC-SHA256 signing and retry behavior.

X-Signature: HMAC-SHA256

Scoped access

API keys carry explicit scopes and are hashed at rest. The partner boundary exposes only the contracted interface.

Scopes · rate limits · audit trail
Inspect endpoint and payload details

Event contract

Subscribe to the workflow instead of polling for it.

Signed events cover the clinical and operational moments a partner experience needs to respond to.

SignedRetriedVersionedScoped
Event stream
patient.intake_started#01
patient.intake_completed#02
visit.completed#03
prescription.dispatched#04
lab_kit.shipped#05
lab_kit.delivered#06
lab_results.available#07
chart_review.completed#08
payment.collected#09
payment.failed#10
commission.settled#11

Integration paths

The platform does not require one front end.

TrueEval experience

Use the clinical platform and patient experience.

TrueEHR, scheduling, clinical workflows, records, and the supported operating layer are configured for the program.

Connected front end

Keep your brand experience and connect it.

Your app remains customer-facing while the supported API and event contract connect it to clinical operations.

Clinical layer

Scope the medical group around an existing stack.

Focus the engagement on providers, oversight, visits, prescribing, records, and state-aware workflows.

Published boundaries

  • No public uptime or throughput SLA
  • No public self-service sandbox
  • No certification claim beyond what is expressly published
  • Availability and scope depend on the engagement

Bring your architecture to the first call.

We will map what stays, what connects, what the medical group operates, and which interfaces need technical diligence.

Scope the integration Developer reference