The Healytix Platform

One license. Every capability.

The Healytix Platform connects the systems a hospital already runs, holds them as one FHIR record, and puts clinical AI on top that answers with citations and drafts work for people to approve. A hospital licenses the platform once and switches each capability on when it is ready for it.

How it works

How the capabilities work together

Data enters through Relay, lives in Fabric, and is read by Sage, Conductor and Pulse. Approved actions flow back into the same record.

  1. Your systems
    HIS / EMR · Lab system (LIS) · HL7 feeds · Imaging reports · Scanned PDFs
  2. Spine · Data layer
    Connect
    Relay · Interoperability

    Legacy databases, HL7 feeds and scanned documents in. Validated FHIR out. No migration.

  3. Record
    Fabric · FHIR record store

    One versioned FHIR R4/R5 record per patient, served through SMART on FHIR APIs.

  4. Cortex · Intelligence layer
    Know
    Sage · Clinical knowledge

    Answers from your records, protocols and SOPs, with the exact passages used.

    → Cited answers: Clinicians

  5. Act
    Conductor · Agents & workflows

    Agents draft prior-auth, discharge and claims work, then wait for a named person to approve.

    → Drafted work: A named approver signs

  6. See
    Pulse · Analytics

    Live dashboards, bed and revenue forecasts, and anomaly alerts.

    → Dashboards & alerts: Hospital leadership

  7. Sage gives Conductor its evidence, Pulse alerts can start Conductor workflows, and approved actions are written back to Fabric.
  8. Solutions on the same platform
Healytix Spine · Data layer · Relay + Fabric

Spine: one FHIR record, built from the systems you already run.

Spine connects a hospital's HIS, LIS, imaging, billing and scanned documents and holds them as one longitudinal FHIR record, validated against ABDM and US profiles. It replaces a migration project with a mapping.

  1. 1Connect
    Relay

    Point Relay at existing databases, HL7 feeds and document stores. AI drafts the mapping; your team approves it.

  2. 2Translate
    Relay · Fhirlace engine

    Approved mappings run deterministically. Scanned reports go through OCR and clinical extraction.

  3. 3Record
    Fabric

    Every resource is validated, versioned and stored as one record per patient, isolated per hospital.

  4. 4Serve
    Fabric

    SMART on FHIR APIs and events feed Cortex, CareOps, Lumen and approved partners.

Spine · Connect

Relay

Interoperability

Relay connects legacy databases, HL7 feeds and scanned documents and turns them into validated FHIR resources, without a data migration.

  • Bidirectional Sync
    Maintain real-time consistency between legacy HIS and your modern FHIR data layer.
  • AI Document Intelligence
    Extract structured clinical data from scanned PDFs, lab reports, and handwritten notes.
  • Zero-Code Mapping
    Visually map legacy database fields to FHIR resources using our AI-guided interface.
  • Schema Discovery
    Automatically detect legacy database structures and suggest the best FHIR mappings.
  • Error Replay
    Dead-letter queues for failed messages with one-click fix and replay capabilities.
  • Data Lineage
    Trace every FHIR resource back to the exact HL7 segment or PDF page it originated from.
Relay Ingestion Stream
● LIVE MAPPING
RAW HL7PID|1|8820477...
FHIR Patient
SCN PDFLab_Report_04.pdf
DiagnosticReport

Ingesting 884 records/sec from 14 HIS nodes

Ingestion Protocols
HL7 v2.x, MLLP, DICOM, SFTP
Mapping Engine
AI-Assisted Semantic Mapping
Engine
Fhirlace, deterministic runtime
Output Format
FHIR JSON / XML

Relay runs on the Fhirlace engine. AI drafts each source-to-FHIR mapping at design time and a person approves it; at runtime the mapping is deterministic, so the same input always produces the same resource. Scanned documents go through OCR and clinical extraction, and every resource keeps a pointer back to the segment or page it came from before it is stored in Fabric.

Spine · Record

Fabric

FHIR record store

Fabric stores, validates, versions and serves every patient record as FHIR, so every capability and approved partner reads the same longitudinal record.

  • Native FHIR R4/R5
    No transformation layer needed. Store and query clinical resources in their native schema.
  • Automated Versioning
    Every change creates a new version, so you can see who changed what, when, and restore any earlier state.
  • SMART on FHIR
    Built-in support for third-party app integration using OAuth2 and OpenID Connect.
  • ABDM Connector
    Direct integration with ABHA, PHR, and HIU/HIP milestones out of the box.
  • Terminology Service
    Built-in LOINC, SNOMED-CT, and ICD-10 mapping for semantic interoperability.
  • Real-time Hooks
    Subscribe to resource changes via WebSockets or FHIR Subscriptions.
fabric · Patient/88204771
✓ Validated: FHIR R4 + ABDM IG profile
// Patient Resource Mapping
"resourceType": "Patient",
"id": "88204771",
"active": true,
"name": [
{ "use": "official", "family": "Reyes" }
],
// Version ID: 12 (Stable)
// Last updated: 2.1s ago
Storage Status: Nominal142ms latency
Data Standard
FHIR R4 / R5 Native
Storage Engine
PostgreSQL with JSONB / Citus
Scaling
Horizontal, partitioned
Built For
ABDM, HIPAA, DPDP

Fabric is the persistence half of Spine. Relay hands it validated FHIR resources; Fabric stores them in PostgreSQL with row-level tenant isolation, keeps every version, and serves them through SMART on FHIR APIs and subscriptions. Cortex and the solutions read from Fabric and write their outputs back to it, so there is one record, not one copy per product.

Healytix Cortex · Intelligence layer · Sage + Conductor + Pulse

Cortex: clinical AI that knows your hospital and acts with sign-off.

Cortex reads the record held in Spine. Sage answers with sources, Conductor runs agent workflows that stop for approval, and Pulse watches the numbers. They share one runtime, one access policy and one evidence record.

  1. 1Know
    Sage

    Hybrid retrieval over the record and your protocols, with every claim checked against a cited passage.

  2. 2Act
    Conductor

    Agents draft the work, gathering evidence through Sage, and wait at an approval state.

  3. 3See
    Pulse

    Dashboards, bed and revenue forecasts, and anomaly alerts that can start a Conductor workflow.

  4. 4Prove
    Evidence record

    Sources, policy, model version and approver are written for every answer and action.

Cortex · Know

Sage

Clinical knowledge

Sage indexes the patient record, your protocols, SOPs and the content you license, and answers questions with the exact passages it used. If nothing supports an answer, it says so.

  • Grounded Clinical AI
    Every sentence in an answer must be supported by a retrieved passage, or it is removed. If nothing supports an answer, Sage says so.
  • Natural Language Search
    Ask complex questions like 'How many patients had troponin spikes after surgery?'
  • Protocol Indexing
    Upload your hospital's SOPs and clinical guidelines for instant staff reference.
  • Source Attributions
    Every answer comes with clickable links to the exact source document or resource.
  • Privacy First
    Runs on-premise or in your private cloud with open-weight models you choose. Patient documents stay inside your network.
  • Trend Analysis
    Identify emerging clinical patterns across thousands of patient discharge summaries.
“Last troponin trend for Patient 88204”
AI
Patient 88204 shows a downward troponin trend over the last 48 hours.
Source [1]
Cardiology Summary

“...troponin-I decreased from 0.42 to 0.09 ng/mL over 48 hours. No new ischemic changes on repeat ECG...”

Source [2]
Lab Results Table

“...2026-04-10: 0.42 | 2026-04-11: 0.18 | 2026-04-12: 0.09...”

Embedding Model
Med-Specialized Vectors
Search Type
Hybrid (Semantic + Keyword)
Context Window
Up to 128k Tokens
Privacy
Air-gapped LLM support

Sage runs a five-stage retrieval pipeline: structure-aware ingestion, hybrid search (semantic plus exact keyword, because drug names and lab codes must match exactly), reranking, evidence verification, and a cited answer. Conductor agents use the same pipeline to gather evidence, so an agent's draft and a clinician's question are grounded the same way.

Cortex · Act

Conductor

Agents & workflows

Conductor runs agent workflows such as prior authorization, discharge planning and claims follow-up as state machines that stop for a named person to approve.

  • Prior-Auth Packets
    Agents gather cited clinical evidence through Sage, assemble the packet, and submit it after a clinician signs.
  • Discharge Orchestration
    Coordinate between pharmacy, billing, and transport for faster bed turnaround.
  • Clinical Alert Routing
    Intelligently route critical lab results based on doctor availability and specialty.
  • Visual Designer
    Drag-and-drop interface for building complex clinical and administrative workflows.
  • Intervention Logic
    Configure exactly when an agent should pause and wait for a human clinician's approval.
  • Performance Monitoring
    Real-time dashboard showing ROI and time-saved for every autonomous workflow.
Workflow: Prior-Auth Automation
AGENT RUNNING
Trigger
Analysis
Packet Assembly
Payer API Call
Assembly Agent v2.1
Fetching medical necessity from Fabric...
Agent Type
State-machine based Agents
Tooling
FHIR API, Payer API, SMS/Mail
Governance
Human-in-Loop Controls
Audit
Full Traceability per step

Each Conductor workflow is a state machine with explicit transitions. Approval points are states the workflow cannot leave without a human decision, so 'ask a doctor' is enforced by the runtime, not suggested in a prompt. Agents wake on events from Healytix Spine, gather evidence through Sage, and write every step to the evidence record.

Example Conductor workflows, and who signs off
Prior authorization

Assembles the medical-necessity packet with evidence from Sage and tracks it to a decision.

✓ Clinician signs
Discharge

Plans discharge across pharmacy, billing and transport, then schedules follow-up calls.

✓ Care team approves
Coding & claims

Surfaces missed codes and assembles NHCX or payer claims with documentation gaps flagged.

✓ Billing reviews
Documentation

Drafts the encounter note from the consultation and the chart.

✓ Doctor signs note
Triage & scheduling

Prioritizes incoming patients and fills cancellations across providers and rooms.

✓ Nurse or front desk confirms
Pharmacy

Reconciles medications at admission and discharge and checks doses.

✓ Pharmacist verifies
Cortex · See

Pulse

Analytics

Pulse turns the live record into dashboards, bed and revenue forecasts, and anomaly alerts for hospital leadership. An alert can start a Conductor workflow.

  • Real-time Command Center
    Live visibility into every department's performance and patient flow.
  • Predictive Bed Mgmt
    Forecast bed occupancy up to 72 hours ahead to plan admissions and staffing.
  • Revenue Cycle Intel
    Instantly identify billing bottlenecks and insurance denial patterns to improve cash flow.
  • Anomaly Detection
    AI automatically flags unusual clinical patterns or suspicious billing activities.
  • Custom Report Builder
    Create and schedule executive reports for your board with one click.
  • Multi-facility View
    Aggregate data across your entire hospital network into a single global view.
Real-time Intelligence
24H
LIVE
Occupancy
92%
Revenue
₹4.2M
▲ 12.4%
Data Source
Fabric event stream
Visualization
High-density SVG Dashboards
Predictive Models
LSTM / Prophet for Occupancy
Alerting
Multi-channel (Slack, WA, In-app)

Pulse reads the Fabric event stream into time-series aggregates kept apart from the transactional store, so dashboards and forecasts never slow down clinical systems. Anomalies it flags can start a Conductor workflow, which closes the loop from seeing a problem to acting on it.

Solutions

Ready-made on the platform

Solutions are the platform pre-configured for a care setting, so a hospital can go live faster.

Why it matters

What changes for the hospital

No data migration

Legacy systems keep running. Relay reads them in place and keeps the FHIR record in sync.

Answers you can check

Every Sage answer lists the passages behind it, and says so when the record is silent.

Agents with a stop sign

Conductor approval points are states a workflow cannot leave without a person, not prompt instructions.

One evidence trail

Questions, agent steps and Pulse alerts land in the same audit record.

Bought by CIOs, CTOs, CMOs, COOs, Medical Directors, Revenue Cycle Leaders

Under the hood

Proprietary engines

Fhirlace
Interoperability engine · In platform

Points at a hospital's existing database and serves it as a FHIR R4 API. No migration, no second copy of the data.

Powers Relay, Fabric
DeepDx
Lab intelligence engine · In clinical validation

Reads lab results as a pattern over time against the patient's own baseline, not one value against a generic range.

Powers Pulse, Lumen
omegaX
Clinical risk & domain AI · In clinical validation

Risk models for high-burden conditions plus domain-expert AI, designed so that institutional data never leaves the hospital.

Powers Sage, Conductor, Lumen
HIPAA READYABDM READYDPDP READYSOC 2 READY

Designed against these frameworks and deployed on-premise or in your private cloud. Current certification and audit status is shared during security review.

See the platform on your own systems.

Bring a list of what you run today. We will map it against Relay and Fabric and show which Cortex workflows are worth switching on first.