Data standards
FHIR R4 mapping
Every canonical resource is bidirectionally mapped to its FHIR R4 equivalent. You can keep working in the Pierflow shape, or pull FHIR-native representations when you need them.
FHIR is the lingua franca of health data exchange. Pierflow speaks both — its own concise shapes by default, FHIR R4 when you need to cross system boundaries.
Canonical ↔ FHIR#
| Pierflow resource | FHIR R4 resource |
|---|---|
| Plan | InsurancePlan |
| Policy | Coverage |
| Member | Patient |
| Provider | Organization + Location + Practitioner |
| Claim | Claim + ClaimResponse |
| Encounter (Phase 2) | Encounter |
| Authorisation | CoverageEligibilityRequest + Response |
Retrieving as FHIR#
Append ?format=fhir to any GET request, or use the /v1/fhir/* endpoints for fully FHIR-native interaction.
FHIR support is read-only in MVP. FHIR-native writes ship in v1.2.