See the care journey, not an isolated encounter.
Organise authorised encounters, medicines, reports, allergies and follow-up information into a reviewable timeline while retaining source and date context.
Back to Nalan IntelligenceNalan for Hospitals & Labs adds intelligence
Hospitals, laboratories & health-tech platforms
Nalan for Hospitals & Labs adds intelligence
to the systems your teams trust.
Nalan is being designed as an embedded artificial intelligence (AI) layer for hospitals, laboratories, hospital management information system (HMIS) vendors, laboratory information system (LIS), laboratory information management system (LIMS) and laboratory management information system (LMIS) platforms, and electronic medical record (EMR) teams. It brings permissioned context and reviewable assistance into existing workflows.
Software development kit (SDK) preview plannedIntegration scope will be validated with design partners before launch.
01HMIS · LIS/LIMS · LMIS02Role-aware intelligence03SDK preview planned
Answer first
What is Nalan for Hospitals and Labs?
Nalan for Hospitals & Labs is Doxyte's integration programme for adding conversational and analytical intelligence to existing hospital management information systems, laboratory information systems and electronic medical record software. Rather than asking teams to replace their core systems, the planned software development kit and connector layer are intended to place reviewable summaries, contextual actions and natural-language access inside familiar workflows.
Inside the clinical workflow
Give teams context without making them leave the system.
A role-aware view can bring authorised laboratory and clinical information closer to review while keeping source records, professional judgement and the host platform in control.
Designed around the workflow
What Nalan can help teams
understand and organise.
Each capability begins as a defined use case with its own data, validation, permissions and review requirements. Release status is confirmed during discovery.
Bring relevant context closer to the moment of care.
Prepare role-aware summaries for clinicians and care teams, with links back to the underlying source and clear AI-generated status.
Make complex result histories easier to review.
Structure authorised laboratory reports, show configured trends and surface items that require professional attention.
Important boundaryNalan does not diagnose a condition from a laboratory result.
Ask the system a workflow question.
Planned interfaces can help authorised users locate information or begin an approved action without navigating disconnected screens.
Make Nalan feel native to your product.
The planned SDK is intended to support embedded chat, summaries and contextual actions shaped around the host system's identity, roles and design.
Make the next handoff easier to see.
Support configured follow-up, communication and task-routing pathways while preserving clinical and operational ownership.
Developer preview planned
An adaptable foundation for the Nalan SDK.
This structure can evolve into developer documentation, sandbox access and integration management when the SDK becomes available. For HMIS, LIS, LIMS and LMIS companies, Nalan is intended to extend existing software rather than replace it.
Nalan components
Embedded conversation, summary and contextual-action interfaces for supported host products.
Connector layer
Mappings for supported patient, encounter, order, result and document structures.
Policy layer
Facility roles, user permissions, consent, purpose and retention rules around every integration.
Observability
Source traceability, human edits, exceptions, performance monitoring and audit events.
Implementation workspace
Environment setup, credentials, test data, documentation and launch checks.
Versioned capabilities
A clear release status for every model, connector and supported workflow.
A governed path to production
Start with the use case.
Keep every handoff visible.
Discover
Define users, systems, decisions, handoffs and the exact problem to solve.
Map
Document identities, data contracts, application programming interfaces (APIs), permissions and system ownership.
Configure
Apply role access, consent logic, source requirements and workflow boundaries.
Embed
Place Nalan components inside the relevant HMIS, LMIS, EMR or laboratory experience.
Validate
Test with representative data and users before any production expansion.
Observe
Monitor performance, exceptions, human corrections and system changes.
Governance is a product capability
Designed for accountable intelligence.
These boundaries guide product design and discovery. The final controls must be validated for the organisation, population, workflow and applicable obligations before production use.
Read Doxyte's security approach ↗Scoped system access
Every integration has an approved purpose, authorised roles and defined data boundaries.
Source-aware outputs
Summaries and signals retain provenance, freshness and appropriate uncertainty.
Clinical validation
Clinical outputs require validation for the intended setting and professional review before use.
No silent replacement
Nalan complements the host system and clearly marks AI-generated information.
Primary reference points
Built with standards and current obligations in view.
These official sources inform the direction of the experience. They do not constitute a certification, regulatory approval or a substitute for implementation-specific legal, clinical or scientific review.
Reference set reviewed 31 July 2026.01
ABDM FHIR R4 implementation guideThe official Ayushman Bharat Digital Mission implementation guide based on HL7 Fast Healthcare Interoperability Resources Release 4.
↗02LOINC®Official information on the terminology standard for health measurements, observations and documents.
↗03Ayushman Bharat Digital Mission (ABDM)Official information on Ayushman Bharat Health Account (ABHA) services, consent and ABDM sandbox integration.
↗04Digital Personal Data Protection Act, 2023The official Act governing digital personal-data processing in India.
↗05Digital Personal Data Protection Rules, 2025The notified Indian rules and phased implementation framework for digital personal data.
↗Questions, answered plainly
Before Nalan enters the workflow.
What is a healthcare AI SDK for HMIS, LIS, LIMS and LMIS platforms?
It is a set of integration components that can add approved AI-assisted experiences, such as summaries, contextual search or guided actions, to an existing hospital or laboratory system.
Will Nalan replace our existing HMIS, LIS/LIMS, LMIS or EMR?
No. The planned approach is designed to extend existing systems while the vendor or healthcare organisation continues to control its core workflows and records.
Which healthcare data sources can be connected?
Potential sources include supported patient, encounter, order, result, document and operational systems. Actual availability depends on documented interfaces, permissions and implementation scope.
Which interoperability standards could the planned SDK support?
The SDK is being designed around documented healthcare interfaces, including Fast Healthcare Interoperability Resources (FHIR) where appropriate and current Ayushman Bharat Digital Mission (ABDM) implementation guidance. Depending on the interface and implementation guide, laboratory observations and diagnostic reports may use LOINC®, while clinical concepts may use SNOMED CT. Mapping, terminology licensing, attribution, versioning and conformance must be verified for every production integration.
What is LOINC® and why is it relevant to laboratories?
LOINC® (Logical Observation Identifiers Names and Codes) is an international standard for identifying health measurements, observations and documents. In supported ABDM and FHIR workflows, it can help systems identify which laboratory test or observation a result refers to. LOINC does not validate, interpret or diagnose from that result.
Is the Nalan SDK available today?
The SDK developer preview is planned. Doxyte can currently discuss architecture, use cases and design-partner participation.
How should AI-generated clinical information be used?
It should be clearly marked, traceable to its inputs and reviewed by an appropriately qualified professional before it affects care.
Can Nalan diagnose a condition from laboratory results?
No. It may help organise authorised result information for review, but diagnosis and treatment decisions remain with qualified healthcare professionals.
Build into the systems you already own
Design the Nalan SDK with a real hospital, lab or platform workflow.
We are interested in focused design partnerships with HMIS vendors, LIS/LIMS and LMIS providers, hospital IT teams and digital-health platforms.
Discuss an SDK partnership ↗