NovaHub: Curated Data for Every Application
Your CRM, HIS, EMR, and AI agents all need the same thing -- curated, resolved, intelligence-ready patient data in real time. NovaHub delivers it. Register a dataset, get an API. No custom code, no integration projects. Real-time data from DataCloud to any application.
Publisher-Subscriber Data Flow
DataLake publishes datasets via Arrow Flight gRPC. NovaHub subscribes, builds optimized shards, and atomically swaps them in. The old data serves requests until the new data is ready. Zero downtime.
Core Capabilities
We optimized for three things: throughput, correctness, and operational simplicity. In that order.
Generic Path-Based API
One route pattern: GET /api/v1/{dataset}/{query_key}/{value}. It dynamically routes to any configured dataset. Register a new dataset in DataLake and the endpoint appears. No code change.
Identity Resolution Engine
Hospital sends a UHID, we resolve it to the golden MDM ID on the fly. Multi-level identity resolution means one identity dataset powers every endpoint.
Inline Filtering Engine
Rich operators across Boolean, Number, String, Date, and Timestamp types. Supports transforms like lower, upper, floor, ceil, year, month, and more -- all type-safe.
Columnar Serialization
Purpose-built columnar format optimized for clinical datasets with nested structures. Dramatically faster writes and smaller storage footprint compared to JSON -- benchmarked on production data, not synthetic tests.
Arrow Flight Streaming
Incremental batch streaming for datasets exceeding 2 GB. Configurable batch sizes keep memory bounded while maximizing throughput over gRPC.
Zero-Downtime Atomic Updates
During a data rebuild, the old version stays live. If the build crashes, old data is intact. If it succeeds, the swap is instant. The API never serves partial or inconsistent data.
Two-Phase Architecture
API Server runs as multiple replicas for horizontal scale. Scheduler runs as a single instance for coordination. Clean separation of concerns with independent scaling.
Config-Driven Extensibility
Register a new dataset in DataLake. NovaHub auto-syncs it, generates the route, starts serving. No code changes, no deployments. This is how we ship new data products in hours.
Engineering Deep Dive
For technical teams evaluating NovaHub. Measured on production workloads with real clinical data.
Columnar vs JSON Serialization
Measured on a 115,906-record clinical dataset with nested structures.
Shard Build Performance
8-shard dataset with partition pruning (skip irrelevant data segments) enabled.
One Route, Every Dataset
We wrote hundreds of hand-coded routes before we figured this out. One generic endpoint pattern handles them all.
GET /api/v1/{dataset}/{query_key}/{value}The path parameters are fully dynamic. When a new dataset is registered in DataLake, NovaHub automatically creates the data store, generates the FK resolution mappings, and starts serving the route -- no code change, no redeployment.
/api/v1/patient_360/uhid/P-10042Full patient profile by hospital UHID
/api/v1/lab_results/mrn/MRN-88210Lab history by medical record number
/api/v1/care_gaps/mdm_id/MDM-5519Open care gaps by golden MDM identity
GET /api/v1/lab_results/uhid/P-10042?filter=test_date.gte.2024-01-01&filter=result_value.between.80,120&filter=test_name.ilike.%glucose%Identity Resolution Engine
A patient has a UHID at one hospital, an MRN at another, a phone number in the CRM. NovaHub resolves all of them to one golden identity in a single hop.
Technology Stack
Boring choices that work. We picked for latency and operational simplicity, not resume-driven development.
Also available as a product
NovaHub Powers Data Intelligence
Use NovaHub's real-time API layer to serve curated clinical data to your existing CRM, HIS, or EMR -- without adopting the full THB platform.
Explore Data IntelligenceCurated Data for Any Application. Zero Custom Code.
Register a dataset. Get an API endpoint. Deliver intelligence-ready patient data to your CRM, HIS, or AI agents. Come see it running.