Skip to content

Why Ayulex

What changes when your hospital moves to Ayulex HMIS.

For the people choosing a hospital system: what Ayulex HMIS gives administrators, an evaluation sheet your committee can work through line by line, and the questions worth asking any HMIS vendor, including us.

For administrators

Built for the people accountable for the hospital.

Medical superintendents, CEOs and finance heads answer for revenue, risk and quality. These are the parts of Ayulex HMIS built for them.

01

Revenue that does not leak

Charges are captured from the clinical event itself: the consultation, the lab or imaging order, the dispensed medicine, the surgery, the transfusion, each bed-day. An event is billed once even if it is recorded twice, and a cancelled order comes off the open bill.

  • Charges captured as care happens
  • Every event billed exactly once
  • Cancelled orders removed from the open bill
  • A receipt for every rupee in or out

02

Control without chasing people

Approval rights decide who may discount, re-price, refund or cancel. Every action carries a person's name and the time, and when someone leaves, deactivating their account blocks sign-in at once.

  • Approvals for discounts, refunds and cancellations
  • Personal accounts with authenticator sign-in
  • Deactivation that takes effect immediately
  • An audit trail no one can edit

03

Numbers you can stand behind

Management and quality indicators come from live records with unit-tested formulas, for any period you choose. Near misses, patient falls and transfusion reactions are calculated to NABH's 6th-edition KPI definitions.

  • Bed occupancy, ALOS, bed turnover and ARPOB
  • Mortality, LAMA and patient-safety rates
  • ER door-to-doctor time, lab and imaging turnaround
  • Revenue and payer mix, with daily trends

04

Less to run

There is no server room to maintain, nothing to install and no upgrade project. Backups, security updates and new features are handled for you.

  • Runs in Chrome, Edge, Safari or Firefox
  • Automated, encrypted daily backups
  • Updates delivered automatically
  • Hosted in India, Mumbai region

Evaluation sheet

For your evaluation committee.

The requirements hospital committees ask about most, answered against what Ayulex HMIS does today and marked built, partial, planned or target. Numbered, so your team can refer to them.

Records and care

  1. 1.1One patient record across departmentsBuilt

    One record from registration to discharge; every department works on the same patient, so nothing is typed twice.

  2. 1.2Medication safety while prescribingBuilt

    Each medicine is checked against recorded allergies, current medicines and duplicates, using fixed rules that give the same answer every time.

  3. 1.3Bedside medication checkBuilt

    The wristband barcode carries the admission number, which the bedside medication check scans before a dose.

  4. 1.4Critical resultsBuilt

    Values are flagged high, low or critical against reference ranges, and released only after verification.

  5. 1.5Surgical safety checklistBuilt

    The WHO checklist is completed item by item before each phase (sign in, time out, sign out) can be signed.

Money

  1. 2.1Charge captureBuilt

    Consultations, tests, imaging, medicines, surgery and bed-days post to the bill as they happen, each exactly once; cancelled orders come off the open bill.

  2. 2.2Control of discounts and refundsBuilt

    Discounts, price changes, refunds and cancelled bills need approval rights, and each one is in the audit trail.

  3. 2.3Payments and receiptsBuilt

    UPI with the amount in the QR code, card, cash or cheque, with a receipt for every rupee in or out.

  4. 2.4Insurance and government schemesPartial

    TPA, insurer, PM-JAY, CGHS and ECHS claims are recorded and tracked from pre-authorisation to settlement. Submission happens on each payer's portal.

Control and compliance

  1. 3.1Audit trailBuilt

    Chart openings and every change are recorded with the person, time and device; the database rejects edits and deletions.

  2. 3.2Access controlBuilt

    Personal accounts, authenticator-app sign-in, role permissions, sign-out after 15 idle minutes, and deactivation that takes effect at once.

  3. 3.3ABHA verification (ABDM M1)Built

    Verify a patient's ABHA, or create one from Aadhaar, during registration. Aadhaar numbers are never stored. Not yet certified by the National Health Authority.

  4. 3.4Health record sharing (ABDM M2, M3)Planned

    Consent-based sharing with other providers, built on the FHIR interface below.

  5. 3.5InteroperabilityPartial

    An HL7 FHIR R4 read interface with API keys each hospital issues and revokes. Writing records through it is not available.

  6. 3.6Patient privacy (DPDP Act 2023)Built

    Consents recorded with their purpose and withdrawable; waiting screens show token numbers only; identifiers removed before text reaches the optional AI scribe.

Management

  1. 4.1Quality and management indicatorsBuilt

    Occupancy, ALOS, ARPOB, LAMA, mortality and turnaround times for any period, from live records. Near misses, patient falls and transfusion reactions follow NABH's 6th-edition KPI definitions; NABH's other KPIs are not calculated yet.

  2. 4.2Today's operations at a glanceBuilt

    A live dashboard of queues, beds, emergency, diagnostics, pharmacy and collections, and what needs attention.

IT and ownership

  1. 5.1Where data is hostedBuilt

    India, in the Mumbai region: the application and the database. E-mail, WhatsApp, the sign-in bot check and the optional AI scribe use services outside India, listed in the Trust Center.

  2. 5.2What the hospital must installBuilt

    Nothing. A current browser on the computers you already have.

  3. 5.3BackupsBuilt

    Automated, encrypted daily backups: a restore can lose up to 24 hours of work today.

  4. 5.4Point-in-time recoveryPlanned

    Restores to within minutes of an incident, in place of daily snapshots.

  5. 5.5AvailabilityTarget

    99.95% a month: a published target, not a contractual service level.

Before you choose

Ten questions to ask any HMIS vendor.

Take them to every demonstration, including ours. These are our answers.

  1. 01

    Where exactly is our patient data stored?

    AyulexIn India, in the Mumbai region: both the application and the database. Some features send data to services outside India: e-mail, WhatsApp messages, the sign-in bot check and the optional AI scribe. The Trust Center lists each one and what it receives.

  2. 02

    Can anyone edit or delete the audit trail? Does it record who viewed a chart?

    AyulexNo one can edit or delete it: the database rejects the attempt. And yes, opening a chart is recorded as well as every change.

  3. 03

    Can counter staff give a discount without approval?

    AyulexNo. Discounts, price changes, refunds and cancellations need approval rights.

  4. 04

    How are charges captured, and can one be billed twice?

    AyulexFrom the clinical event itself, and no: each consultation, order, dispense or bed-day is billed once, even if it is recorded twice.

  5. 05

    Are prescriptions checked for allergies and interactions?

    AyulexYes, as each medicine is added, using fixed rules that give the same answer every time.

  6. 06

    Is ABHA verification built in, or sold separately?

    AyulexBuilt in at registration: verify an ABHA, or create one from Aadhaar, and Aadhaar numbers are never stored. This is ABDM milestone M1, which the National Health Authority has not certified yet. Record sharing (M2 and M3) is planned.

  7. 07

    How are our quality indicators calculated?

    AyulexFrom live records, with formulas covered by automated tests. Three follow the KPI definitions in NABH's 6th-edition standards: near misses, patient falls per 1,000 inpatient days and transfusion reactions per 100 units transfused. Occupancy, length of stay, bed turnover and turnaround times are standard hospital statistics rather than NABH KPIs.

  8. 08

    Does staff sign-in support two-step verification?

    AyulexYes: authenticator-app codes, and automatic sign-out after 15 minutes without activity.

  9. 09

    Which features use AI, and what do they see?

    AyulexOnly the optional scribe. The names on the patient's record and identifying numbers are removed automatically before any text is sent; that can miss an identifier that is not on the record.

  10. 10

    How do other systems get our data?

    AyulexThrough the HL7 FHIR R4 interface, with API keys your hospital issues and can revoke.

Up front

What we tell every hospital before it signs.

Trust starts with knowing the limits as well as the strengths.

ABDM

ABHA verification and creation (milestone M1) is built in, and not yet certified by the National Health Authority. Consent-based record sharing (M2 and M3) is planned.

Internet connection

Ayulex HMIS needs a connection to save work. If it drops, screens keep the last loaded data on view and say so, and the app reconnects by itself. Your downtime procedure, agreed before go-live, covers the time in between.

Accreditation

NABH accreditation is awarded to hospitals, not to software. We provide the records and indicators your assessors will look for.

Recovery point

Backups are daily today, so a restore can lose up to 24 hours of work. Point-in-time recovery, to within minutes, is being introduced.

Insurance claims

Claims are recorded and tracked against the bill in Ayulex, but submitted on each insurer's or scheme's own portal.

AI

Only the optional scribe uses AI. It removes identifiers automatically, which can miss some, and the doctor reviews everything it drafts. Safety checks are rules, not predictions.

See Ayulex HMIS on your own workflows.

Tell us about your hospital and we will tailor the demonstration to your departments, your tariffs and the way your teams work today.

Write to us

support@ayulex.com

We reply by e-mail.

TiLi Center, 2nd Floor, MV119 JL BuildingMission Veng, AizawlMizoram 796005, India

Already a customer? Sign in to your hospital