FHIR Platform Suite — Setup & Deployment Guide

What you're deploying

Five files. Two platforms. One shared messaging bridge — all running in the browser with no backend.

Repository layout

All five files go in the root of your repository. No subfolders needed.

How messages flow between platforms

1Create a GitHub Repository

You need a free GitHub account and a new public repository.

2Upload Your Files

Option A — Web Upload (no Git needed, recommended)

Option B — Git Command Line

# 1. Clone your empty repository
git clone https://github.com/YOUR_USERNAME/fhir-platform.git
cd fhir-platform

# 2. Copy your 5 downloaded files into this folder, then:
git add index.html client.html vendor.html fhir-bridge.js .nojekyll README.md
git commit -m "Initial release — FHIR Platform Suite"
git push origin main

3Enable GitHub Pages

https://YOUR_USERNAME.github.io/fhir-platform/

4Verify Deployment

Open your Pages URL. You should see:

Test the complete message flow

Do this in the same browser on the same device. Open both platform tabs first.

Downloading files on both sides

Browser storage limits

Total localStorage across all browsers is typically 5–10 MB. The landing page shows live usage. Click Clear All Data to reset if you hit the limit during testing.

Connecting to a real FHIR server

The bridge's localStorage layer handles real-time tab-to-tab messaging. For durable storage on a real FHIR server, use the built-in REST client in each platform:

On the Client Platform

Go to Settings → Server Config. Enter your FHIR base URL and authentication. Use the Raw Editor to POST ServiceRequests directly to the server.

On the Vendor Platform

Go to Settings → Vendor Configuration. Configure the client endpoint URL. Use the FHIR Composer to POST DiagnosticReport bundles directly.

Recommended open FHIR servers for testing

Cross-device messaging

Option 1 — Use a real FHIR server (recommended)

Both platforms can POST/GET from the same HAPI FHIR instance. Client sends ServiceRequest → Vendor polls for new ServiceRequests → Vendor POSTs DiagnosticReport → Client polls for results.

Option 2 — Add a WebSocket relay

Replace the BroadcastChannel calls in fhir-bridge.js with WebSocket events. A free Node.js server on Railway or Render can act as a relay in under 50 lines.

Option 3 — FHIR Subscriptions (R4B / R5)

FHIR R4B and R5 define a Subscription resource that pushes notifications via webhook or WebSocket when new resources arrive. This is the production-grade path.

// Example: replace BroadcastChannel in fhir-bridge.js with WebSocket
const ws = new WebSocket('wss://your-relay.onrender.com');

function submitOrder(fhirResource, attachmentMetas) {
  // ... existing localStorage code stays ...
  ws.send(JSON.stringify({ event: 'NEW_ORDER', envelope }));
  return envelope;
}

ws.onmessage = (e) => {
  const msg = JSON.parse(e.data);
  if (msg.event === 'NEW_RESULT') resultCallbacks.forEach(cb => cb(msg.envelope));
};

Common issues and fixes