Skip to content
Ayulex

For hospitals · Ayulex HMIS

Run the hospital on one record.

For medical superintendents, administrators, owners and hospital IT: how Ayulex HMIS fits your operations, how it is deployed and secured, what it connects to, who can do what, and how we take you live.

For your IT team: the technology and security overview is a short PDF you can circulate before a demo.

A patient’s journey, department by department.

Each department keeps its own screens and its own role. What each one records lands on the same patient record, the same bill and the same reports.

  1. Step 1Front office

    Registration

    Register or find the patient, verify their ABHA, and print a wristband.

  2. Step 2Front office and doctor

    OPD

    A token on the waiting-area screen, then the consultation and a prescription checked for allergies and interactions.

  3. Step 3Doctor and laboratory

    Diagnostics

    Lab and radiology orders, barcoded sample labels, and results back on the same record.

  4. Step 4Front office and nursing

    Admission

    A bed assigned from live bed status, and deposits recorded against the stay.

  5. Step 5Nursing and doctors

    Ward care

    Nursing notes and every medicine given, on the record the doctors read.

  6. Step 6Surgical team

    Theatre

    Procedures recorded on the patient’s record, and charged from it.

  7. Step 7Pharmacist

    Pharmacy

    Dispensing from your formulary, with batches and expiry tracked in stock.

  8. Step 8Billing desk and approvers

    Billing

    Charges from the clinical events, each billed once; discounts and refunds need approval.

  9. Step 9Doctor and billing

    Discharge

    The discharge summary on the same record, and the bill settled with a receipt.

Revenue

Charges captured from the clinical event, each billed exactly once; cancelled orders come off the open bill.

Control

Approval rights for discounts, price changes, refunds and cancellations, with a name and a time on each.

Reporting

Occupancy, ALOS, bed turnover, ARPOB, mortality and turnaround times from live records, plus near misses, patient falls and transfusion reactions to NABH’s KPI definitions.

Hosted in India, and rolled out in the order you choose.

Ayulex HMIS is a cloud service. Going live means planning, setup and training, with nothing to install on your own servers.

  • Cloud, in India

    The application and its database run in the Mumbai region. There are no servers for your hospital to buy or maintain.

  • Nothing to install

    Ayulex HMIS runs in Chrome, Edge, Safari or Firefox, and improvements arrive in the browser automatically.

  • Rolled out your way

    We agree with you which modules go live first, what data moves across, and the go-live date.

  • Configured as your hospital

    Departments, wards, beds, tariffs, packages, lab panels, formulary and print formats are set up to match your hospital.

What you’ll need

Equipment most hospitals already have.

Computers
Any desktop or laptop with a current version of Chrome, Edge, Safari or Firefox.
Internet
A stable broadband connection. For critical areas, a second connection from a different provider.
Printers
A4 printers for bills, prescriptions and reports. A label printer for barcoded sample labels and wristbands.
Barcode scanners
Optional. Standard USB scanners that type into the field in focus.
Token display
Optional. Any TV or monitor that can open a web page, for the OPD token screen.

Architecture, access and data retention.

The controls built into Ayulex HMIS, how each is enforced, and where the responsibility sits, written so your IT team can verify each one.

Architecture

  • Application and database in India, in the Mumbai region
  • TLS on every connection, with HSTS preload
  • Database and backups encrypted at rest; automated daily backups
  • Each hospital’s records kept separate; every request limited to the signed-in hospital
  • A strict Content Security Policy, and every input validated on the server

Access

  • Standard roles, and custom roles built from 36 permissions
  • Permissions checked on the server for every request
  • Password plus an authenticator-app code, with bot protection
  • Idle sessions signed out after 15 minutes
  • A deactivated account is blocked at once

Retention and privacy

  • An append-only audit trail, enforced by the database
  • Consents recorded with their purpose, and withdrawals too
  • Aadhaar numbers and one-time codes never stored or logged
  • Responses carrying patient data never cached by browsers or proxies
  • Error reports stripped of identifiers before they are stored

What leaves India, and why

Patient records, bills, files, staff accounts, the audit trail and backups stay in India. Emails such as invitations, WhatsApp messages if you connect your number, the sign-in bot check and the optional AI scribe’s text, with names and identifiers removed, use providers outside India.

A note on certification

NABH accredits hospitals, not software, and the DPDP Act places duties on your hospital as well as on us. Ayulex HMIS gives you the controls and the records those obligations call for. If your evaluation needs a completed security questionnaire, we answer it in writing.

What Ayulex HMIS connects to, and what is still coming.

We list what is built, what is optional and what is in development, because you will be asked the same questions by assessors.

  • ABHA verification and creation

    ABDM Milestone 1

    Built

    The desk verifies a patient’s ABHA, or creates one from Aadhaar, with a one-time code sent to the patient’s mobile. A verified ABHA is marked on the chart, and Aadhaar numbers are never stored.

  • Sharing and fetching records

    ABDM Milestones 2 and 3

    In development

    Sharing records with the patient’s consent, and fetching them from other providers, build on the same ABDM client and FHIR interface.

  • Read API for your systems

    HL7 FHIR R4

    Built

    Patient, Encounter, MedicationRequest and Observation, with diagnoses in ICD-10 or ICD-11 and vitals in LOINC with UCUM units. Read-only keys are issued and revoked by your administrator, and every record released is in the audit trail.

  • Writing through the API

    HL7 FHIR R4

    In development

    Builds on the same interface and its controls.

  • Patient messages

    WhatsApp Business

    Optional

    Booking codes, confirmations and reminders, if the hospital connects its own WhatsApp number.

  • Devices

    Scanners, label printers, screens

    Supported

    Standard USB barcode scanners, label printers for sample labels and wristbands, and any screen that opens a web page for the token display.

Roles, permissions and an audit trail no one can edit.

People see and do what their work requires. Administrators start from standard roles and can build custom ones from 36 individual permissions.

  • Front office can bill; only approvers can give discounts, change prices or issue refunds
  • The audit trail records who opened a chart and who changed what, with the time, IP address and device
  • Filter it by date, user, action or record, for NABH and DPDP accountability reviews
  • Staff are added, changed and deactivated by your own administrators
Default permissions of the standard roles in Ayulex HMIS
PermissionAdministratorDoctorNurseFront officeLab technicianPharmacistWard assistant
View patient recordsAllowedAllowedAllowedAllowedAllowedAllowedNot allowed
Prescribe medicinesAllowedAllowedNot allowedNot allowedNot allowedNot allowedNot allowed
Record medicines givenAllowedNot allowedAllowedNot allowedNot allowedNot allowedNot allowed
Enter lab resultsAllowedNot allowedNot allowedNot allowedAllowedNot allowedNot allowed
Dispense medicinesAllowedNot allowedNot allowedNot allowedNot allowedAllowedNot allowed
Create bills, collect paymentsAllowedNot allowedNot allowedAllowedNot allowedNot allowedNot allowed
Approve discounts and refundsAllowedNot allowedNot allowedNot allowedNot allowedNot allowedNot allowed
Update bed statusAllowedNot allowedAllowedNot allowedNot allowedNot allowedAllowed
Read the audit trailAllowedNot allowedNot allowedNot allowedNot allowedNot allowedNot allowed

Default permissions of the standard roles, taken from the product. Administrators can change them.

From signed agreement to first patient.

Four stages, each with a written result. Here is what we do, what we need from your side, and how support continues after go-live.

  1. Stage 1

    Discovery

    What we do

    • We walk through each department with its head: registration, OPD, wards, theatres, diagnostics, pharmacy and billing.
    • We review your tariffs, packages, bed layout, print formats and approval rules.
    • We agree which modules go live first, what data moves across, and the go-live date.

    What we need from you

    • A project lead who can make decisions
    • An hour with each head of department
    • Your tariff list and sample bills, reports and prescriptions

    Result: A written scope and a dated plan.

  2. Stage 2

    Configuration

    What we do

    • Departments, doctors, schedules, wards and beds are set up to match your hospital.
    • Service rates, packages, lab panels with reference ranges and your formulary are loaded.
    • Roles and staff accounts are created, and print formats matched to your letterhead.

    What we need from you

    • Your current price list and packages
    • A staff list with each person’s role
    • Sign-off on print formats

    Result: Your hospital configured and checked by your heads of department, with a setup checklist in the app for anything left.

  3. Stage 3

    Migration and training

    What we do

    • Patient details, doctors and opening stock with batches and expiry come across, from your current system or spreadsheets.
    • Each role is trained on its own screens, in small groups and by shift.
    • Real scenarios from your hospital are rehearsed, from registration to discharge.

    What we need from you

    • Data exports from your current system
    • Staff released for their training sessions

    Result: Staff who have practised their own day’s work on Ayulex HMIS.

  4. Stage 4

    Go-live and support

    What we do

    • We choose a go-live day and hour with you, away from your busiest periods.
    • We stay close to your teams through the first days on the new system.
    • We review the first weeks with your administrators and fine-tune the configuration.

    What we need from you

    • A champion in each department who knows the system best

    Result: A hospital running on one record, with support by phone and email from then on.

  • Support after go-live

    By phone and email once you are live, and your configuration changes with you as the hospital grows.

  • Updates without installations

    Improvements arrive in the browser. There is nothing to install or update on your computers.

  • Your data stays yours

    Your hospital owns its records. Systems you authorise read them through the FHIR interface, with keys you issue.

A demo built around your hospital.

We set up Ayulex HMIS with your departments, tariffs and print formats, and walk your team through the day they would have on it.

Your departments

Registration to discharge, in the order your patients move.

Your IT team’s questions

Hosting, access, audit and integrations, answered directly and followed up in writing.

Your go-live plan

If it fits, discovery ends with a written scope and a dated plan.

Technology and security overviewPDF for your IT and compliance teamsDownload

Already a customer? Sign in to Ayulex HMIS

Request an Ayulex HMIS demo

A walkthrough built around your departments, tariffs and print formats.

Departments, current software, or what you’d like the demo to cover.

We reply by email. No mailing lists.