FHIR R4 Connector
Enrich clinical resources with multimodal AI
A zero-dependency connector that extracts text from FHIR R4 clinical resources and enriches them with Mixpeek's multimodal AI. Supports Patient, Observation, Condition, DocumentReference, DiagnosticReport, Encounter, and MedicationRequest resources with automatic fallback to narrative text for all other types. Returns enrichment as FHIR-compatible extensions and meta tags.
Built for health IT teams, EHR integrators, clinical data engineers, and healthcare AI developers working with FHIR R4 servers.
Get Started
Integrations
Works with any FHIR R4 compliant server or EHR system.
npm install @mixpeek/fhirUse Cases
Clinical document classification and semantic search
Patient record enrichment for care coordination
Diagnostic report analysis and summarization
Healthcare data pipeline enrichment for analytics
MDS 3.0 auto-population from EHR clinical resources for skilled nursing facilities
Features
Example
FHIR Observation Resource
{
"resourceType": "Observation",
"id": "blood-pressure",
"code": { "text": "Blood Pressure" },
"component": [
{ "code": { "text": "Systolic" }, "valueQuantity": { "value": 120, "unit": "mmHg" } },
{ "code": { "text": "Diastolic" }, "valueQuantity": { "value": 80, "unit": "mmHg" } }
]
}Enriched Resource (extensions added)
{
"resourceType": "Observation",
"id": "blood-pressure",
"extension": [
{ "url": ".../enrichment/document-id", "valueString": "doc_abc123" },
{ "url": ".../enrichment/keywords", "valueString": "blood pressure, systolic, diastolic" }
],
"meta": {
"tag": [{ "system": ".../CodeSystem/taxonomy", "display": "Cardiology" }]
}
}Get Started
Integrations
Details
Quick Info
Frequently Asked Questions
Which FHIR resource types are supported?
The connector has dedicated extractors for Patient, Observation, Condition, DocumentReference, DiagnosticReport, Encounter, and MedicationRequest. All other resource types fall back to narrative text extraction from the resource's text.div field.
How is enrichment stored in the FHIR resource?
Enrichment is added as FHIR extensions under the URL prefix https://mixpeek.com/fhir/StructureDefinition/enrichment/ and as meta tags using Mixpeek code systems. This follows the FHIR extensibility framework and can be cleanly stripped using the strip() method.
Does it work with Epic and Cerner?
Yes, the connector works with any FHIR R4 compliant server including Epic, Cerner, and other EHR systems. It processes FHIR resources regardless of their source, just pass the resource JSON to the enrich() method.
Can I process an entire Bundle at once?
Yes, use the enrichBundle() method to process all resources in a FHIR Bundle. Each entry is enriched individually and the results are returned along with the enriched bundle.
Related connectors
Ready to integrate?
Get started with FHIR R4 Connector in minutes. Check out the documentation or explore the source code on GitHub.