Records API
Capture options
Pierflow supports several capture channels. Pick the one that fits the facility and call the same Ingest endpoint regardless.
Whatever path the pages take to get to Pierflow, they end up on a single ingest queue. Your integration only needs to consume the downstream Patients and Import Package endpoints.
Mobile capture#
The simplest path to live: facility staff use the Pierflow capture web app on any modern phone. The app guides them through capturing each page, labelling the document type, and assigning it to a batch. Pages upload directly to the ingest queue.
| Requirement | Detail |
|---|---|
| Device | Any phone with a back camera and a modern browser (iOS 16+, Android 10+) |
| Connectivity | Works offline; queued uploads resume on reconnect |
| Setup | Single magic-link sign-in for facility staff. No app store install required. |
Direct upload (server-to-server)#
Partners with existing scanning workflows can POST images or PDFs directly to the Ingest endpoint. This is also how you'd wire a Document Management System or an archive crawler into Pierflow.
Scanner integrations Roadmap#
Integration with desktop and network scanners (high-volume document scanners, multifunction printers) is on the roadmap. While we finish validating that surface, mobile capture and direct upload cover the same workflows — the API your team builds against doesn't change.
Same response shape, every channel