Interoperability · FHIR

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.

Your appExcelicare FHIR APIPatient record
GET /fhir/Patient/example-id
1GET https://api.excelicare.com/fhir/Patient/example-id
2Authorization: Bearer <access_token>
3Accept: application/fhir+json
4
5200 OK
6{
7 "resourceType": "Patient",
8 "id": "example-id",
9 "identifier": [{ "system": "https://fhir.nhs.uk/Id/nhs-number", "value": "0000000000" }],
10 "name": [{ "use": "official", "family": "Sample", "given": ["Patient"] }],
11 "gender": "unknown",
12 "birthDate": "1990-01-01",
13 "generalPractitioner": [{ "reference": "Practitioner/example-gp" }]
14}
0+

FHIR resource types supported

0%

Record data reachable via FHIR APIs

0+

Years of healthcare interoperability experience

0/7

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.