1. Reference
  • Getting started
    • Welcome to Cardioexplorer
    • Core Concepts
    • Developer Quickstart & Resources
  • Guides
    • FHIR Client Integration Guide
    • Integration Strategy Guide
    • Cardiac Data Requirements & Gap Analysis
  • Reference
    • API Objects & Models
    • Error Reference
  • Resources
    • Changelog
    • Frequently Asked Questions
Guides
API References
Guides
API References
  1. Reference

API Objects & Models

Every reusable object the API returns, defined once — with a one-glance JSON example above each field table.

ApiResponse envelope#

Authentication endpoints wrap payloads in a standard envelope:
{ "status": "success", "message": "…", "errors": null, "data": { } }
FieldTypeDescription
statusstring"success" or "error"
messagestringHuman-readable summary of the outcome
errorsobject · nullPer-field validation errors (field name → array of messages)
dataobject · nullThe payload — shape depends on the endpoint

GapAnalysis#

Returned by Generate draft test. Full semantics in Cardiac Data Requirements.
{
  "success": true,
  "draftTestId": "1e7adfef-4ffa-4e9b-bde5-49c1f1ab06ae",
  "itemsMapped": 30, "itemsRejected": 1, "itemsMissing": 1,
  "rejectedItems": [ { "entryUrl": "urn:uuid:…", "rejectionReason": "…", "conceptName": "…", "resourceType": "Observation" } ],
  "missingItems": [ { "conceptId": 3004249, "name": "Systolic blood pressure" } ]
}
FieldTypeDescription
successbooleanWhether the draft was created
draftTestIdstring (GUID)ID of the created test — use for run / result / report calls
itemsMappedintegerParameters recognized and stored (max 32)
itemsRejectedintegerEntries refused — unknown code, invalid status, or out-of-range value
itemsMissingintegerExpected parameters absent from the bundle
rejectedItemsarrayOne entry per rejection: entryUrl (the bundle entry's fullUrl), rejectionReason, plus conceptId, conceptName, code, vocabularyId, resourceType, valueNumber, valueText, unit
missingItemsarrayMissing parameters, each with conceptId and name

TestResult#

Returned by Run CCSTest and Get CCSTest result.
{
  "testId": "901804f2-566f-4dc4-af33-7beb6432073c",
  "patientId": "2307",
  "riskScore": 0.4990, "riskLevel": "High",
  "recommendation": "Coronary CT angiography (CCTA) … is recommended",
  "completedAt": "2026-07-20T19:08:40Z",
  "warnings": [], "expectedPrevalence": 0.14
}
FieldTypeDescription
testIdstring (GUID)The CCS test identifier
patientIdstringPatient identifier from your FHIR bundle
riskScorenumber (0–1)Model output — probability-like coronary risk score
riskLevelstring"Low" · "Intermediate" · "High" — localized via language
recommendationstringESC-guideline-based clinical recommendation, localized
completedAtstring (ISO 8601)When the model run completed
warningsarray of stringValidation warnings (empty on a clean run)
expectedPrevalencenumberPopulation baseline for comparison (e.g. 0.14)

Organization#

Embedded in the Obtain access token response under data.organization.
{
  "organizationId": "550e8400-…", "organizationName": "Organization Name",
  "contactEmail": "admin@organization.com", "accessLevel": 2,
  "isActive": true, "rateLimitPerHour": 1000,
  "allowedIpAddresses": "10.0.0.0/8", "totalApiCalls": 2847
}
FieldTypeDescription
organizationIdstring (GUID)Unique organization identifier
organizationNamestringDisplay name
contactEmailstringAdministrative contact
accessLevelintegerFeature tier granted to the organization
isActivebooleanWhether the account can authenticate
rateLimitPerHourintegerHourly API call allowance
allowedIpAddressesstring (CIDR)IP allowlist, if configured
totalApiCallsintegerLifetime call counter
createdAt / updatedAt / lastAccessedAtstring (ISO 8601)Account timestamps

PdfReport#

Returned by Get PDF Report (base64 variant).
{
  "status": "success", "message": "PDF report generated successfully",
  "pdfContent": "JVBERi0xLjQK…",
  "ccsTestId": "b4f1a1d4-…",
  "filename": "CardioExplorer_Report_b4f1a1d4_20260720.pdf"
}
FieldTypeDescription
status / messagestringStandard envelope fields
pdfContentstring (base64)The PDF file, base64-encoded (~33% larger than the binary)
ccsTestIdstring (GUID)Test the report belongs to
filenamestringSuggested filename

Error object#

Non-2xx responses use one of two shapes — see the Error Reference for codes, causes and resolutions.
{ "status": "error", "message": "Invalid client credentials", "errors": null, "data": null }
{ "warnings": [ "SystolicBloodPressure is required" ] }
ShapeUsed byFields
Envelope errorAuthentication endpointsstatus: "error", message, errors (per-field), data: null
Simple errorCCS endpointsmessage — or warnings[] on validation failures

Related pages: Error Reference · Cardiac Data Requirements · Core Concepts — Questions? info@explorishealth.com
Previous
Cardiac Data Requirements & Gap Analysis
Next
Error Reference
Built with