HealthDataStore (FHIR & DICOM as a Service)

Overview

Every AI application in healthcare begins with data — clinical notes, lab results, medical images, EHR records, etc.

The challenge is storing and accessing that data safely, interoperably, and compliantly.

ByteEngine HealthDataStore is your FHIR and DICOM backend-as-a-service. It gives you instant, scalable access to healthcare data APIs — without worrying about servers, compliance, or infrastructure.

You can think of it as:

Firebase for Healthcare Data — but built on FHIR and DICOM.

What is HealthDataStore?

HealthDataStore is a fully managed data layer for healthcare apps. It powers:

• FHIR Servers: For structured clinical data (patients, encounters, observations, etc.)
• DICOM Servers: For imaging data (X-rays, MRIs, CTs, etc.)

ByteEngine hosts and manages these stores in secure, compliant environments (HIPAA/GDPR-ready).

Each HealthDataStore can be:

• Global, US-resident, or EU-resident
• Linked to your AI Workers or Pipelines
• Queried directly via REST APIs or FHIR search

FHIR Server — Overview

FHIR (Fast Healthcare Interoperability Resources) is the standard for healthcare data exchange. ByteEngine provides FHIR-native APIs out of the box — so you can store, search, and update healthcare data using a modern REST API.

Example Use Case

You're building an AI symptom checker. The app needs to save user data like age, symptoms, diagnosis, and treatment plans. Instead of designing your own schema, you use ByteEngine's FHIR Patient, Observation, and Condition resources. Your app automatically becomes interoperable with hospitals and EHR systems.

Creating a FHIR Server

Via the Dashboard (UI Example)

1. Log in to your ByteEngine Console.
2. Go to HealthDataStore → Create New Store.
3. Select FHIR Server.
4. Choose your region (Global, US, or EU).
5. Name your FHIR server (e.g., my-fhir-dev).
6. Click Create.

In under 10 seconds, your FHIR API endpoint is ready.

Visual Placeholder: [Screenshot: "Create FHIR Server" UI showing name, region selector, and compliance info]

Via API

curl -X POST https://api.engine.boolbyte.com/api/fhirserver/create \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
        "name": "my-fhir-dev",
        "region": "global",
        "fhirVersion": "R4",
        "type": "serverless"
      }'

Response:

{
  "success": true,
  "data": {
    "id": "store_9837fh",
    "name": "my-fhir-dev",
    "region": "global",
    "fhirVersion": "R4",
    "infrastructure": "serverless",
    "status": "running",
    "endpoint": "https://fhir.global.byteengine.health/fhir/my-fhir-dev",
    "apiKey": "sk-...",
    "createdAt": "2024-01-15T10:00:00.000Z"
  }
}

You can now send FHIR resources to this endpoint!

Via JavaScript SDK

import { EngineClient } from '@boolbyte/engine';

const client = new EngineClient({ apiKey: 'YOUR_API_KEY' });

// Create a FHIR server
const fhirServer = await client.dataStore.createFhirStore({
  name: 'my-fhir-dev',
  region: 'global',
  fhirVersion: 'R4',
  type: 'serverless'
});

console.log('FHIR Server created:', fhirServer.data.endpoint);

Adding and Querying Data

Create a Patient Resource

curl -X POST https://fhir.global.byteengine.health/fhir/my-fhir-dev/Patient \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "Content-Type: application/fhir+json" \
  -d '{
    "resourceType": "Patient",
    "name": [{"family": "Doe", "given": ["John"]}],
    "gender": "male",
    "birthDate": "1980-05-05"
  }'

Response:

{
  "id": "patient-1",
  "resourceType": "Patient",
  "created": "2024-01-15T10:00:00.000Z"
}

Query Patients by Name

curl -X GET "https://fhir.global.byteengine.health/fhir/my-fhir-dev/Patient?name=Doe" \
  -H "Authorization: Bearer <ACCESS_TOKEN>"

Real-world Example

A startup building a chronic disease management app uses ByteEngine's FHIR API to store blood pressure and heart rate readings from wearable devices. Their AI worker subscribes to new Observation resources, detects anomalies, and alerts the patient's clinician — all automatically.

DICOM Server — Overview

DICOM (Digital Imaging and Communications in Medicine) handles imaging data such as:

• X-rays
• CT scans
• MRIs
• Ultrasound images

ByteEngine's DICOM Server provides DICOMweb-compatible APIs — so you can upload, store, and retrieve images directly from your PACS or AI pipeline.

Creating a DICOM Server (UI)

1. Go to HealthDataStore → Create New Store.
2. Select DICOM Server.
3. Choose your region and storage size.
4. Click Create.

All images are stored in encrypted, HIPAA/GDPR-compliant storage.

Visual Placeholder: [Screenshot: "Create DICOM Server" UI with encryption and compliance badges]

Upload a DICOM File

curl -X POST https://dicom.global.byteengine.health/dicom/my-dicom-server/studies \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "Content-Type: application/dicom" \
  --data-binary @chest-xray.dcm

Retrieve Study Metadata

curl -X GET https://dicom.global.byteengine.health/dicom/my-dicom-server/studies \
  -H "Authorization: Bearer <ACCESS_TOKEN>"

Response Example:

[
  {
    "StudyInstanceUID": "1.2.840.113619.2.55.3.604688431.781.1573724372.467",
    "PatientName": "John Doe",
    "Modality": "CT",
    "StudyDate": "2024-01-15"
  }
]

Real-world Example

A radiology company uploads DICOM scans to ByteEngine. An AI Worker automatically processes each image using a pre-trained model (e.g., fracture detection). The results are converted into a FHIR DiagnosticReport, linked to the corresponding Patient resource, and made available via FHIR API.

Integrating with AI Workers & Pipelines

Every HealthDataStore can connect directly to your AI Workers and Pipelines.

Example:

# workflow.yaml
name: "Radiology Report Workflow"
trigger:
  type: "new-dicom-upload"
  store: "my-dicom-server"

steps:
  - worker: "fracture-detector"
    input: "@dicom:latest"
  - transform: "to-fhir:DiagnosticReport"
  - output: "my-fhir-dev"

Whenever a new scan is uploaded, the workflow automatically runs AI inference, generates a report, and stores it in FHIR.

Compliance Integration

When you create a HealthDataStore, compliance is automatically applied:

Region	Compliance	Data Protection
US	HIPAA	AES-256 encryption, BAA available
EU	GDPR	Data subject rights, deletion API
Global	Pseudonymized	Multi-region AI access

No manual configuration required — ByteEngine enforces compliance-by-default.

Monitoring & Auditing

Each FHIR and DICOM server includes:

• Access logs
• Audit trails
• Usage analytics (queries, inferences, file storage)
• Region-level activity reports

UI Placeholder: [Screenshot: "FHIR Server Dashboard" with API usage chart and access logs panel]

Summary

Feature	FHIR Server	DICOM Server
Purpose	Clinical data (structured)	Imaging data (binary)
Standard	HL7 FHIR R4/R5	DICOMweb
Access	REST API, SMART-on-FHIR	REST API, DICOMweb
Compliance	HIPAA, GDPR	HIPAA, GDPR
Integration	AI Workers, Workflows, Pipelines	AI Workers, Workflows, Pipelines

Next Steps

Next Section → AI Workers — Building and Running Healthcare AI Agents

Learn how ByteEngine's AI Workers let you create, orchestrate, and automate reasoning and inference in your healthcare applications.

• Health Data Store API Reference - Complete API documentation
• FHIR Usage Examples - Hands-on FHIR operations
• AI Integration - Connect AI Workers to your health data
• Quick Start Guide - Build your first healthcare application