Modern, API-first health data exchange
FHIR R4 is the primary way external systems integrate with Excelicare. It's resource-based, token-authenticated, and built for both real-time and bulk access.
FHIR as the primary integration surface
If a system can speak FHIR R4, it can read and write to the Excelicare platform.
FHIR R4 REST APIs
Standard RESTful endpoints for reading and writing structured clinical resources over HTTPS.
Resource-Based Model
Data is exposed as discrete, well-defined resources such as Patient, Encounter, Observation, and more.
OAuth 2.0 & SMART-Style Access
Token-based authentication and scoped access, aligned with SMART on FHIR access patterns.
Bulk Data Export
Asynchronous bulk export for population-level extracts, without hammering the transactional APIs.
Subscriptions for Real-Time Updates
Subscribe to resource changes and receive notifications as clinical events happen.
Sandbox & Conformance Testing
A sandbox environment and published CapabilityStatement for partners to test against before go-live.
Resources exposed today
A representative set of the FHIR resources available. Coverage is extended as new integration needs are scoped.
- Patient
- Encounter
- Observation
- Condition
- MedicationRequest
- MedicationStatement
- DiagnosticReport
- AllergyIntolerance
- Appointment
- DocumentReference
- Practitioner
- Organization
- CarePlan
- Immunization
- ImagingStudy
- Coverage
A familiar request, a structured response
Illustrative example. Actual responses depend on your deployment's resource configuration and scopes.
GET https://api.excelicare.com/fhir/Patient/example-idRequestAuthorization: Bearer <access_token>Token-securedAccept: application/fhir+json 200 OKResponse{ "resourceType": "Patient",FHIR resource "id": "example-id", "identifier": [{ "system": "https://fhir.nhs.uk/Id/nhs-number", "value": "0000000000" }],Identifier "name": [{ "use": "official", "family": "Sample", "given": ["Patient"] }],Name "gender": "unknown", "birthDate": "1990-01-01", "generalPractitioner": [{ "reference": "Practitioner/example-gp" }]Linked resource}FHIR resource types supported
Record data reachable via FHIR APIs
Years of healthcare interoperability experience
API availability
FHIR questions, answered
Talk to us about your FHIR integration
Book a session with our interoperability team to review your resource and scope requirements.

