Patient and encounter
Identity, coverage, and visit context that other clinical systems can already consume.
FHIR R4 · HL7 · Clinical exchange
Designed to meet the FHIR/HL7 Specification
Global Healthcare Interoperability
A public origin for clinics, partners, and product teams that need one clinical API to move patients, encounters, and care records across systems. Same routes. A specification-first contract.
Specification
Resource shapes, identifiers, and exchange patterns follow the FHIR/HL7 specification so hospitals, EHRs, and digital clinics can connect without a custom translation layer for every partner.
Identity, coverage, and visit context that other clinical systems can already consume.
Notes, observations, and care artifacts exchanged as structured API resources.
Existing Suncture clients keep the same paths. Only the public origin changes.
Interoperability
Use R4 when a deployment needs to sit beside national networks, vendor EHRs, or a custom stack that already expects FHIR-ready APIs. One contract for clinics operating across regions.
Onboard clinicians and share a common patient record across locations.
Give integrators a stable origin instead of a private Cloud Function URL.
Need FHIR-ready APIs on your infrastructure? Write support@suncture.io.
Live origin
Health check
GET https://r4.suncture.io/health
Checking
Public origin
https://r4.suncture.io
Clients call the same paths they used before. Start with /health.
Start
Building for a custom deployment but need FHIR-ready APIs? Contact support at support@suncture.io.