Patient management
The Patient 360 service — every patient, visit and document persisted in the unified data model and exposed through the backend API.
RUCJA · HOSPITAL OPERATIONS PLATFORM · BUILT BY HIREQEDComposable modules
on one data model.
RUCJA is a hospital operations platform built by HireQED — composable modules on a unified Patient 360 data model and backend API, with real-time patient monitoring, connected-device telemetry, lab and pathology report parsing, role-based access control and end-to-end encryption.
Unified Patient 360 data model Real-time device telemetry Encrypted in transit & at rest
Mon 11
Chemo cycle 2
Lab review
Tue 12
Iron infusion
Pre-meds
Wed 13
CBC + RGCC
Follow-up
Thu 14
EC infusion
Fri 15
Shiitake support
Recovery review
Backend API
Unified data model · RBAC
Real-time layer
Device telemetry · live charts
PLATFORM MODULESComposable modules,
Composable modules,
one backend.
Each module is a service on the shared backend API and unified Patient 360 data model — composed together so every workflow reads and writes one source of truth.
Reports & documents
Encrypted upload and storage pipeline for lab reports and clinical documents, attached to the patient record.
Lab intelligence
PDF-parsing service that extracts each parameter and plots it as time-series against history and treatment markers.
Scheduling & protocols
Treatment-protocol engine generating recurring, dependency-aware calendar events with conflict detection.
Billing & payments
Invoicing service with an approval state machine and webhook-synced Zoho Books integration.
Patient request routing
Category-based routing engine that assigns each request to a role queue with full audit trail.
Device readings
Real-time telemetry layer ingesting BP, SpO₂, weight and temperature from paired Bluetooth devices, charted with threshold alerts.
Role-based access
RBAC layer with granular per-role permissions, patient-scoped roles and end-to-end audit logging.
AI ARCHITECTUREThree AI pipelines
Three AI pipelines
wired into the data model.
Each AI capability is a service on the platform — speech-to-protocol generation, audio transcription and indexing, and a retrieval-augmented assistant — all grounded in the unified Patient 360 data model.
Voice → Protocol
Speech-to-protocol generation pipeline.
A speech-to-text and LLM pipeline parses a free-text clinical instruction into a structured treatment protocol. The model output is mapped to the scheduling engine’s event schema — recurrences, intervals and dependencies — and written to the patient calendar through the backend API.
- Natural-language parsing — transcription feeds an LLM that emits a structured, schema-validated protocol.
- Multi-step plan expansion — recurring cycles, infusions, pre-meds and follow-ups expanded into discrete calendar events.
- Human-in-the-loop review — generated events are editable, reorderable and removable before they are committed.
- Constraint checks — the scheduling engine validates conflicts, prep windows and resource availability before commit.
🎙 “Schedule chemo cycles starting Monday, 6 cycles weekly, with pre-meds and a Wednesday lab follow-up.”
Protocol generated4 events · 6 weeks
Cycle 1 — ChemoMon · 10:00
Cycle 2 — ChemoMon · +1w
Pre-meds + salineTue · 9:30
Lab follow-upWed · 11:00
LAB PARSING ENGINEPDF parsing into
PDF parsing into
time-series data.
The lab service parses Pathology (CBC) and RGCC oncology report formats. Each uploaded PDF is extracted into structured parameters, normalized against reference ranges, persisted to the data model and rendered as a time-series overlaid with treatment events.
- Treatment-event overlay — therapies from the protocol engine are joined to lab readings on a shared timeline.
- Reference-range normalization & alerts — out-of-range values are flagged and surfaced through the real-time layer.
- RGCC sensitivity/resistance parsing — drug-pick findings extracted into a structured, ranked dataset.
- Role-scoped read view — a read-only, mobile-rendered projection of the same dataset, scoped by RBAC.
13.4g/dL▲ 3.6 since MarNormal 12–16
Treatments overlaid on the timeline — so the doctor sees exactly what moved the parameter.
BPSpO₂TempWeight
Reading received from connected device · just now
98%Oxygen saturation● Normal
Latest
98%
Average
97%
Min
95%
Max
99%
REAL-TIME PATIENT MONITORINGEvery device, every
Every device, every
reading, live.
RUCJA pairs connected and wearable devices over Bluetooth and streams readings to the backend API in real time. Each measurement is persisted to the patient record, charted as a time-series against reference ranges, and emits threshold alerts on the real-time layer — fused with lab, pathology and RGCC report analysis for one continuously updated picture.
- Vitals from connected & wearable devices — blood pressure, blood glucose, heart rate, SpO₂, temperature, weight and single-lead ECG ingested via the mobile SDK.
- Report-driven monitoring — pathology (CBC) and RGCC findings analyzed and joined to live vitals on a shared timeline.
- Time-series with reference bands — every reading stored as time-series and rendered against normal ranges.
- Threshold-based alerts — out-of-bounds values emit events on the real-time layer for the care team.
- Single source of truth — patient and clinician clients read the same record over the API.
Blood pressure · BPM Blood glucose · glucometer Heart rate & pulse SpO₂ · pulse oximeter Temperature · thermometer Weight · smart scale ECG · single-lead Respiratory rate
INTEGRATIONS & CLIENTSA Zoho-synced billing service
A Zoho-synced billing service
and native mobile clients.
The billing service integrates with Zoho Books over its API and webhooks, while two native mobile clients — clinician and patient — run on the same backend API and data model as the web app.
Billing & Zoho
Zoho Books integration & invoicing service.
- Zoho Books API integration — customers, invoices and status synced bidirectionally via webhooks.
- Patient payment flow — patients submit proof through the app; status updates propagate over the real-time layer.
- Approval state machine — finance verifies proof and transitions an invoice through verify/paid/reject states.
- Partial-payment ledger — multiple claims tracked against one invoice with a computed running balance.
Mobile apps
Native iOS & Android clients on the same API.
- Two native clients — separate clinician and patient apps for iOS and Android, both consuming the backend API.
- Clinician app — schedule, patients, reports and voice-note capture backed by the shared data model.
- Patient app — reports, appointments, payments, device pairing and the Ruchika assistant.
- Push notification service — real-time events delivered to devices via platform push channels.
ARCHITECTUREFour layers,
Four layers,
one platform core.
RUCJA is engineered by HireQED as a layered, cloud-native platform: server-rendered and native clients over a single backend API and data model, with a real-time layer and platform-wide security and integrations.
Client layer
Web & native clients
Server-rendered Next.js / React web app plus native iOS and Android clients. Every surface is a thin client that authenticates and reads through the backend API.
API layer
Backend API & data model
A single backend API over the unified Patient 360 data model. Every module — patients, scheduling, labs, billing, devices — is a service exposed on this API.
Real-time layer
Events & telemetry
A real-time layer streams device telemetry, alerts and status changes to connected clients, and fans out push notifications to mobile devices.
Platform layer
Security & integrations
RBAC, end-to-end encryption and audit logging across every request, plus outbound integrations such as Zoho Books synced over API and webhooks.
One source of truth. Every client and module reads and writes the same unified data model through the backend API — no divergent copies, no out-of-sync state.
TECHNICAL FAQHow the platform
How the platform
is built.
Architecture, data model, security and integrations — the engineering questions about how RUCJA is constructed.
RUCJA is a layered, cloud-native platform: server-rendered Next.js / React web clients and native iOS / Android clients sit over a single backend API and a unified Patient 360 data model, with a real-time layer for telemetry, alerts and push delivery.
Every module — patients, scheduling and protocols, labs, devices, billing and request routing — is a service that reads and writes the same unified data model. Each client reads one source of truth through the backend API rather than maintaining separate copies.
Data is encrypted in transit (TLS) and at rest. A role-based access control (RBAC) layer scopes every read and write, including patient-scoped roles, and an end-to-end audit log records every access. The platform can be deployed to a chosen hosting region.
RBAC supports arbitrary roles scoped to specific modules and to subsets of patients, and roles can be tagged to request-routing categories. Permissions are enforced at the API layer and surfaced through the admin console.
The lab service parses Pathology (CBC) and RGCC oncology PDF formats, extracts each parameter into structured fields, normalizes against reference ranges, persists to the data model, and renders the result as a time-series with treatment-event overlays.
Billing integrates with Zoho Books over its API and webhooks for bidirectional invoice and status sync. The device layer ingests Bluetooth telemetry through the mobile SDK, and the AI services compose speech-to-text, an LLM and retrieval over the patient record.
BUILT BY HIREQED
Hospital operations, engineered end-to-end.
Composable modules, one data model, real-time by design. Quite Easily Done.
RUCJA is one of HireQED's health-technology products — built on the same engineering foundations of unified data models, real-time infrastructure and security by design that run across our platform.