We use Google Analytics and a Meta advertising pixel on our public site only — never on the clinical application. You can opt out at any time via “Cookie settings” in the footer. See our privacy policy.

CardioBridge API

File & trace requirements

A few rules keep traces interpretable and avoid avoidable returns.

Accepted file types

fileType
application/pdf
pdf

A PDF export of the ECG. Most common.

image/png
image

A PNG image of the trace.

image/jpeg
image

A JPEG image of the trace.

Maximum file size

Each ECG file may be up to 20 MB. The app blocks larger files before upload, and the /emr-inbound push endpoint rejects them — it returns a fileError and leaves the intake in needs_completion so you can resubmit a smaller file.

Keep files small
A clear PDF or a cropped image of an ECG is typically well under 5 MB. If you're close to the limit, export a compressed PDF or a right-sized image rather than a full-resolution photo of a screen.

Trace quality

Submit one ECG per intake. Provide a clear 12-lead or single-lead trace with legible calibration and minimal artefact. Crop to the trace and avoid low-resolution photos of screens.

Returned jobs

If a trace is illegible or too low-quality to interpret, the cardiologist marks the job returned with a reason, and a returned webhook is sent. To resubmit, create a new intake with a better trace — reusing the same external_id is safe and recommended for traceability.

returned event
{
  "event": "returned",
  "reference": "CB-000123",
  "reason": "Better-quality trace required"
}