Records API
Records API
Turn paper-based patient records into validated, FHIR R4-compliant data your EMR, HMS, or partner system can import in one call.
How it works#
You send Pierflow scanned pages. Pierflow returns structured patient records — already mapped to FHIR R4 — ready to import.
Behind the API, every page is normalised, extracted, validated, and either auto-approved or routed to human review when confidence is low. Your integration sees a single, consistent response shape — you don't need to handle any of the underlying pipeline.
Who it's for#
| You are… | What you use the Records API for |
|---|---|
| EMR / EHR vendor | Activate hospital and clinic clients by pulling their historical paper records into your platform on day one. |
| HMS vendor | Make HMS go-lives meaningful — the platform isn't empty when your customer switches on. |
| Hospital or clinic group | Migrate decades of records into your chosen digital system without manual data entry. |
| Diagnostic lab | Lift archived lab result sheets into a structured, searchable record set. |
| Insurer / HMO | Reconcile member coverage with documented care from provider archives. |
| Government or public health programme | Population-level digitisation of facility records for analytics and continuity of care. |
What you get back#
For every approved record, you receive a FHIR R4 Bundle containing the relevant resources — typically Patient, Encounter, Observation, Condition, and MedicationRequest. For batch consumption, records are assembled into Import Packages you download as a single ZIP.
Standards-aligned by default