Who it serves
Multi-specialty hospitals, district hospitals, nursing homes, day-care centres, and clinic chains standardising operations across locations.
APSYS-Tejas
Digital healthcare operations for modern Indian hospitals
APSYS-Tejas is a modular HMIS, EMR and EHR platform built for fast registration, OPD/IPD workflows, billing, pharmacy, inventory, clinical records, audit trails, and ABDM-ready hospital operations.
General Description
One platform from registration to discharge
APSYS-Tejas brings together HMIS (Hospital Management Information System), EMR/EHR-style clinical documentation, and financial operations so that front desk, doctors, nurses, billing, pharmacy, laboratory, radiology, and administration work from shared, auditable records.
The product is built around real Indian hospital workflows: UHID-based patient identity, OPD token and consultation flows, admission and bed management, service-wise billing with payor and package support, receipt and ledger discipline, and department workbenches that acknowledge orders before results or issues are posted.
Hospitals can start with registration, OPD, and billing - then add pharmacy, laboratory, radiology, MRD, HR, and ABDM-ready exchange as departments become ready. The same saffron-themed experience runs on web browsers, desktop clients, and mobile apps for selected frontline roles.
What it replaces
Disconnected registers, duplicate data entry between billing and clinical areas, and manual reconciliation between receipts, services, and department fulfilment.
How teams adopt it
Phased module rollout with role-based menus, department masters, and training-friendly screens aligned to APSYS implementation support.
Designed from real healthcare operations
Healthcare experience shaped the workflow logic
APSYS-Tejas is shaped by more than 20 years of healthcare institutional experience. The product focuses on practical Indian hospital workflows such as UHID registration, OPD/IPD movement, billing discipline, pharmacy issue, department workbenches, role-based access, audit trails, and ABDM-ready architecture.
APSYS-Tejas is developed through APSYS's human-led, AI-assisted product methodology, where AI accelerates development but healthcare workflow logic, validation, and final product decisions remain human-directed.
Indian hospital workflows
Registration, consultation, admission, billing, pharmacy, diagnostics, MRD, and reporting are treated as connected workflows.
Human-led decisions
Workflow logic, business rules, testing, validation, and release acceptance remain under human product direction.
ABDM-ready caution
ABDM architecture is readiness-oriented, with sandbox validation in progress and subject to NHA/ABDM approval.
Technical Details
Enterprise-ready architecture for care environments
- Client channels
- Web application, Windows Desktop client, and Mobile apps (Android / iOS) for selected operational roles
- API layer
- REST API for Desktop, Mobile, and third-party integration - consistent validation and authorization across channels
- Data platform
- Microsoft SQL Server with structured transactional schema, audit-friendly activity tracking, and configurable masters
- Security model
- Role- and resource-based access, special rights for sensitive financial actions, session control, and user activity logs
- Billing & finance
- OPD/IPD invoicing, receipt management, refunds, payor/corporate billing, ledger pools (Hospital-OP / Hospital-IP), and settlement workflows
- Deployment
- On-premises or customer-hosted infrastructure; modular licensing aligned to departments and user roles
- Integration posture
- ABDM-ready identity and consent architecture; department workbenches for Lab, Radiology, Pharmacy, and queue/token routing
- User experience
- APSYS saffron / rising-sun theme for visual continuity between public site and live hospital applications
Core Modules
Foundation modules every hospital needs first
These modules form the operational backbone - patient identity, clinical front door, inpatient coordination, money flow, records, and people management.
Patient Registration
OPD Consultation
IPD Admission / Transfer / Discharge
Billing & Receipts
Pharmacy
Laboratory
Radiology
MRD
HR
ABDM Integration
Registration & patient master
UHID creation, demographic capture, quick search, visit linkage, and front-desk intake integrated with billing and clinical modules.
- Duplicate detection and family linkage
- Document attachment support
- ABDM-ready identity fields where enabled
OPD consultation & queue
Consultation registration, doctor worklists, clinical notes, prescriptions, and token/queue routing to service areas.
- Department and doctor-wise scheduling hooks
- Bill-to self / payor on consultation billing
- Integration with laboratory, radiology, and pharmacy orders
ATD / IPD admission
Admission requests, bed allocation, transfers, nursing notes context, and discharge planning with billing continuity.
- Ward, bed category, and sponsor/payor mapping
- Advance receipts and final bill preparation
- Pharmacy issue and service posting to inpatient account
Billing & finance
OPD and IPD invoicing, receipt collection, refunds, adjustments, corporate/payor rules, and ledger-aware receive payment.
- Service-wise and package billing
- Partial service cancellation with refund voucher discipline
- Invoice settlement and statement export
EMR / EHR
Clinical documentation, consultation notes, prescriptions, and encounter-linked records shared across OPD and IPD workflows.
- Doctor worklists and structured clinical notes
- Prescription and order linkage to pharmacy, lab, and radiology
- Encounter history on the patient record
Audit & role-based security
Role- and resource-based access, special rights for sensitive financial actions, user activity logs, and audit-friendly operational records.
- Department-scoped menus and permissions
- Financial action guards and activity tracking
- Controlled access to clinical and billing data
MRD & documents
Medical Records Department workflows - file movement, issue/return tracking, and controlled hospital document handling.
HR & attendance
Employee master, attendance capture, and administrative reporting support linked to hospital operational roles.
Add-On Modules
Clinical and supply-chain depth when you are ready
Add-on modules extend Tejas into inventory-aware pharmacy operations and diagnostic departments - with workbench acknowledgement before fulfilment.
Inventory & pharmacy
Store-wise stock, batch/expiry control, purchase inward, OPD pharmacy sale, IPD patient issue, and returns - with billing and ledger posting on sale.
- Available-stock search with batch picker
- OPD walk-in and patient-linked pharmacy billing
- IPD issue to admission with final-bill integration
- Purchase, transfer, adjustment, and opening stock (as licensed)
Laboratory
Lab order lines from OPD/IPD, sample collection workflow, result entry, verification, and worklist-driven department processing.
- Order acknowledgement before sample/processing
- Result reporting with audit trail
- Billing linkage to originating consultation or admission
Radiology
Radiology orders, reporting drafts, verification states, and imaging department coordination tied to patient encounters.
- Status-driven workbench (ordered -> reported -> verified)
- Integration with billing and clinical orders
- Department guardrails on service cancellation
Implementation note: Add-on modules are licensed and deployed according to hospital readiness. APSYS helps sequence pharmacy, laboratory, and radiology go-lives after core registration and billing stabilise.
Additional Feature
Confidential Patient Privacy
Policy-based privacy controls that protect patient identity across reports, worklists, portals, notifications, and dispatch records - built around the principle of minimum necessary disclosure.
APSYS-Tejas includes a dedicated confidential patient privacy feature designed for hospitals, labs, and diagnostic centres that handle sensitive services, VIP patients, medico-legal cases, and privacy-critical reports.
Selected patients, encounters, or services can be handled under a masked identity or confidential case code. Instead of exposing full patient details everywhere, APSYS displays only the minimum required information - confidential case code, masked patient name, age, gender, and sample/report number. Sensitive details like real name, mobile number, address, guardian name, and Aadhaar/ABHA identifiers are hidden from routine screens and outputs.
VIP Patient Privacy
The patient's real identity is protected by using a masked patient profile across routine workflows. Actual identity can be accessed only by authorised users with proper audit logging.
Service-Specific Privacy
For sensitive tests or procedures, APSYS generates a confidential service case code. Reports and workflow screens use this code while preserving clinically necessary details like age and gender.
Applicable workflows: Sensitive lab tests, psychiatry, infertility, HIV/STD testing, medico-legal cases, VIP care, and other hospital-defined confidential procedures.
Masked identity
Confidential case codes replace real patient names across reports, worklists, portal views, and dispatch records.
Permission-controlled reveal
Full identity reveal is gated behind role-based permissions with complete audit trail of who accessed what and when.
Minimum necessary disclosure
Each user sees only the information required for their role - care, reporting, filing, or communication - nothing more.
Purpose: To help healthcare organisations protect patient dignity, confidentiality, and trust while maintaining safe clinical and operational workflows.
ABDM Integration
Prepared for Ayushman Bharat Digital Mission
APSYS-Tejas includes ABDM-ready architecture for M1 (identity and ABHA linking), M2 (consent-based health information sharing as HIP), and M3 (health information request as HIU) - with FHIR R4-aligned document exchange, audit trails, and sandbox/production configuration separation.
Current status: ABDM sandbox integration in progress. Subject to NHA/ABDM approval, production credential activation, and applicable regulatory requirements.
Implementation Roadmap
How hospitals adopt APSYS-Tejas
A structured, phased approach so your departments adopt at a pace that sticks - no big-bang disruptions.
Phase 1: Registration + OPD + Billing
Patient registration (UHID), OPD consultation, and billing/receipt workflows go live first - the operational backbone every hospital needs.
Phase 2: IPD + Pharmacy
Once core is stable, add inpatient admission, transfer, discharge, and pharmacy stock and dispensing - one department at a time with APSYS training support.
Phase 3: Lab + Radiology + MRD
Activate laboratory order-to-result, radiology workbenches, and medical records department workflows as clinical departments stabilise.
Phase 4: ABDM readiness and integration
Configure ABDM-oriented identity linking, care-context exchange, and consent workflows as operational maturity and regulatory readiness grow - subject to NHA/ABDM approval.
Why hospitals choose APSYS-Tejas
Built for Indian hospital reality
Indian hospital focus
Designed for Indian hospitals, nursing homes, and multi-speciality centres - UHID, payor billing, and front-desk reality
Role-based permissions
Role and resource-based permission structure - doctors, nurses, billing, pharmacy each see only their responsibility
Audit-friendly billing
Receipt-first collection, refund discipline, and traceable adjustments aligned with hospital audit expectations
Modular deployment
Start with core modules and expand department by department - suitable for phased rollout without replacing the core
FAQ
Common questions about APSYS-Tejas
Can we start with OPD and billing only?
Yes. Most hospitals begin with registration, OPD consultation, and billing/receipt workflows, then add IPD, pharmacy, laboratory, radiology, and MRD as departments stabilise.
Does APSYS-Tejas support Web and Desktop?
Yes. APSYS-Tejas supports web browsers, Windows Desktop client, and mobile apps for selected operational roles - all backed by the same REST API.
Is APSYS-Tejas ABDM approved?
APSYS-Tejas includes ABDM-ready architecture. ABDM integration and readiness features are under sandbox validation and subject to NHA/ABDM approval, production credential activation, and applicable regulatory requirements. APSYS does not claim completed NHA/ABDM certification unless officially available.
Where is patient data stored?
APSYS-Tejas is deployed on-premises or on customer-hosted infrastructure. Patient data stays within the hospital's own servers and network - APSYS does not host patient data on shared cloud platforms.
APSYS-Tejas
Plan your hospital rollout with APSYS INDIA Pvt. Ltd.
Discuss module sequencing, department workbenches, billing rules, and ABDM preparation with our team.