nuri-integration-spec

Public integration specification for NURI — Teh Tarik Digital's Neural Unified Reasoning Intelligence (preview version) platform for Malaysian hospitals, clinics, and residential care facilities. Describes the administrative and integration boundary through which external systems connect to a NURI deployment: facility onboarding, HL7/FHIR stream registration, webhook event subscription, module configuration, alert channel setup, and MOH-ready audit log export.

What NURI does

NURI functions as a digital twin for frontline clinical and care teams. It handles voice-activated documentation, real-time vitals and incident monitoring, NEWS2 early-warning scoring, automated shift handover generation, and care scheduling — deployed on-premise or within Malaysian cloud regions, with clinical data never leaving the Facility's environment.

Designed specifically for the Malaysian care landscape: MOH-aligned documentation standards, Bahasa Malaysia voice processing, PDPA 2010 (as amended 2024) compliant architecture, and a localized medical LLM trained on Malaysian clinical domain data.

What's here

openapi.yaml — the administrative and integration contract covering:

• Facility registration — deployment onboarding, type, locale, module selection, MOH code
• HL7/FHIR endpoint registration — FHIR R4 and HL7 v2.x stream registration for HIS, EMR, bedside monitor gateways, and nurse call infrastructure; inbound, outbound, and bidirectional
• Webhook event subscriptions — subscribe to alert escalation, handover readiness, module state changes, and system health events; payload envelope documented (clinical content never included)
• Module configuration — enable/disable and configure NURI's six clinical modules
• Alert channel configuration — Teams webhook, email, SMS gateway, and nurse call system routing by severity and shift role
• Audit log export — date-range exports in CSV, JSON, or MOH-formatted PDF for compliance review
• System health — subsystem status endpoint for Facility IT monitoring

This spec covers the integration boundary only. It does not describe NURI's internal clinical data schema, AI reasoning pipeline, NEWS2 scoring logic, or per-patient digital twin structure. No patient or resident data appears in this spec.

Quickstart

Validate the spec:

npx @redocly/cli lint openapi.yaml

Preview as interactive docs:

npx @redocly/cli preview-docs openapi.yaml

Integration overview

Facility Systems                    NURI Deployment
─────────────────                   ───────────────────────────────
HIS / EMR          ←── FHIR R4 ──→  HL7/FHIR Integration Layer
Bedside monitors   ──── HL7 v2.x ─→  Vitals Monitoring Module
Nurse call system  ←── alerts ────   Alert Router
MS Teams / SMS     ←── webhooks ──   Webhook Event Bus
MOH audit system   ←── export ────   Audit Log Module
Facility IT        ←── /health ───   System Health

Supported FHIR R4 resource types

Encounter · Observation · MedicationRequest · MedicationAdministration · Condition · Procedure · DocumentReference · Communication · AllergyIntolerance · CarePlan · ServiceRequest · DiagnosticReport · Appointment

Supported HL7 v2.x message events

ADT_A01 · ADT_A02 · ADT_A03 · ADT_A08 · ORU_R01 · ORM_O01 · MDM_T02 · SIU_S12 · SIU_S15

Webhook event types

Event	Description
alert.escalation_triggered	Clinical alert escalated to duty personnel
alert.escalation_resolved	Alert resolved or dismissed
alert.news2_threshold_breached	NEWS2 score crossed a configured threshold
alert.missed_task_flagged	Scheduled care task missed
handover.draft_ready	Shift handover summary compiled and ready for review
handover.confirmed	Handover confirmed by incoming shift
handover.overdue	Handover not confirmed within configured window
module.state_changed	Module enabled, disabled, or entered degraded state
integration.endpoint_degraded	HL7/FHIR endpoint connectivity lost
integration.endpoint_recovered	HL7/FHIR endpoint connectivity restored
audit.export_ready	Requested audit log export ready for download
system.health_degraded	One or more NURI subsystems degraded
system.health_recovered	All subsystems returned to healthy state

Clinical modules

Module ID	Description
voice_documentation	Voice-dictated clinical notes, transcription, and structuring
vitals_monitoring	Real-time telemetry ingestion, anomaly detection, trend analysis
news2_scoring	Automated NEWS2 early-warning scoring and deterioration alerts
handover_generation	Cross-department shift handover summary compilation
care_scheduling	Round scheduling, medication tracking, missed-task alerts
ecosystem_dashboard	Centralised facility occupancy, acuity, and staff allocation view

Compliance

• PDPA 2010 (as amended 2024) — sensitive personal data (Section 40) safeguards applied at platform level
• MOH-aligned — documentation standards, escalation workflows, and audit log format
• Data residency — all clinical processing contained within the Facility's own environment; no external data transmission
• Audit logging — cryptographic audit trail for all system, configuration, and access events; exportable for MOH and governance review

See the full data governance details at tehtarik.digital/nuri/privacy/

Deployment tiers

Tier	Scope	From
Ward / Unit	Single ward, clinic, or care unit (up to 40 beds)
Facility / Department	Up to 5 connected care blocks
Enterprise Hospital / Network	Unlimited deployment areas
MOH / State Framework	Multi-facility institutional	Custom proposal

Pilot programme open — apply at tehtarik.digital/nuri

Learn more

tehtarik.digital/nuri