EHR integration

Nobody wants a second dashboard. PodiaScan exposes a read-only API so your practice management or EHR system can pull foot temperature history into the patient's existing record — no extra logins for your staff.

How it works

1. An administrator generates an API key in PodiaScan under Settings → EHR integration. The key is shown once and can be revoked at any time.

2. Your system calls the endpoints below with Authorization: Bearer <key>. Every response is scoped to the clinic that issued the key.

3. Observations are returned as FHIR R4 resources, so most modern systems can map them without custom work. A flat JSON shape and a CSV export are available for systems that cannot. The formatted PDF record is generated inside PodiaScan and can be attached to the patient file.

Endpoints

GET/api/public/ehr/v1/patients

Every patient in your clinic with their reference, last scan date and largest recorded difference.

GET/api/public/ehr/v1/patients/{id}/observations?days=90

The trend window as FHIR R4 Observation resources (body temperature, per zone and side, plus the computed difference). Add &format=json for a flat JSON shape.

GET/api/public/ehr/v1/patients/{id}/summary.csv

One row per scan for systems with no API support — import as a document or spreadsheet.

Base URL: https://podiascan.com. Requests are rate limited and logged per key. No data leaves your clinic's scope.

Example

curl -H "Authorization: Bearer ps_live_..." \
  "https://podiascan.com/api/public/ehr/v1/patients"

curl -H "Authorization: Bearer ps_live_..." \
  "https://podiascan.com/api/public/ehr/v1/patients/PATIENT_ID/observations?days=90"

Clinical positioning

Exported values are readings recorded by clinic staff or patients, with the arithmetic left/right difference. They carry no diagnostic interpretation and should be filed as observations, not as findings.

Clinical safety and intended use

Talk to us about your EHR Clinic platform