Healthcare

FHIR resources as Delta tables

DeltaForge parses FHIR JSON, XML, NDJSON, and RDF/Turtle resources directly into Delta tables. Query clinical data with SQL. Your data stays on your infrastructure.

JSON, XML, NDJSON, and RDF/Turtle encoding formats
Common FHIR R4 and R5 resources
Runs on your infrastructure; PHI never leaves your network
FHIR Patient (JSON) { "resourceType": "Patient", "id": "pat-12345", "name": [{ "family": "Smith", "given": ["John"] }], "birthDate": "1985-04-12" } FHIR Observation (XML) <Observation> <status value="final"/> <valueQuantity .../> </Observation> parse DeltaForge FHIR parser R4 / R5 store healthcare.fhir_patients id | family_name | given | birth_date | ... Query with SQL SELECT id, family_name, birth_date FROM healthcare.fhir_patients WHERE birth_date > '1980-01-01'

Resource categories

Common FHIR R4 and R5 resources parsed into Delta tables

Patient and encounter

Patient, Encounter, EpisodeOfCare, Practitioner, Organization, Location.

Clinical findings

Observation, Condition, Procedure, DiagnosticReport, AllergyIntolerance, Immunization.

Medications

Medication, MedicationRequest, MedicationAdministration, MedicationDispense.

Care planning

CarePlan, CareTeam, Goal, ServiceRequest, Appointment.

Financial

Claim, ClaimResponse, Coverage, ExplanationOfBenefit.

Documents and bundles

Bundle, DocumentReference, Composition, Consent.

Encoding formats

Parse FHIR resources from any standard serialization

JSON

application/fhir+json, including nested extensions and reference resolution.

XML

application/fhir+xml with full namespace and attribute handling.

NDJSON

Newline-delimited JSON for bulk export from EHR systems.

RDF/Turtle

Linked-data format for semantic web and terminology integration.

Bring FHIR into your lakehouse

Parse clinical resources directly into Delta tables on your own infrastructure.

Get Community License Read Documentation