Everything you need to know about APSYS-Tejas

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 or SaaS platforms. The hospital retains full physical and logical control over its database.

No. APSYS INDIA Pvt. Ltd. does not sell, rent, or share patient or health data with any third party. Healthcare organizations remain solely responsible for lawful collection, processing, and sharing in their operations. The only external data exchange is through ABDM consent-based workflows, and that too is initiated and controlled by the hospital.

Access is governed by a role-based and resource-based permission model. Each user is assigned roles (doctor, nurse, billing staff, pharmacist, lab technician, etc.) and can only see menus, screens, and data relevant to their responsibility. Sensitive financial actions require additional special-rights approval. Department-scoped menus ensure that clinical, billing, pharmacy, and administrative staff operate in isolated workspaces.

Yes. APSYS-Tejas records user activity logs across clinical, billing, and administrative workflows. Important actions - such as record modifications, financial transactions, refunds, cancellations, and permission changes - are tracked with timestamps and user identity so that they are traceable during hospital audits and compliance reviews.

APSYS-Tejas uses HTTPS (TLS/SSL) for all data in transit between client applications and the server. Data at rest is protected by the database server's encryption capabilities (SQL Server Transparent Data Encryption where configured by the hospital IT team). Sensitive configuration values such as connection strings and ABDM credentials are stored using encrypted configuration mechanisms.

User passwords are hashed and never stored in plain text. Authentication follows secure session management practices. The hospital's IT team controls password policies, session timeout settings, and account lockout rules as part of their infrastructure governance.

No, unless explicitly permitted. Department-scoped menus and permissions ensure that pharmacy staff see pharmacy workflows, lab technicians see lab workflows, and billing staff see billing screens. Cross-department access requires specific role and resource permissions configured by the hospital administrator.

The hospital administrator can deactivate or remove user accounts immediately. Deactivated users lose all access to the system. Their past activity remains in audit logs for compliance and traceability, but they cannot log in or access any data.

APSYS-Tejas uses Microsoft SQL Server, which supports automated backups, point-in-time recovery, and replication. The hospital's IT team configures backup schedules, retention policies, and disaster recovery procedures as part of their infrastructure management. APSYS provides guidance on recommended backup practices during implementation.

Patient data enters through the Registration module at the front desk. A UHID (Unique Hospital Identification) is created with demographics, contact details, and identity documents. This single patient record is then linked to all subsequent visits, consultations, admissions, and billing transactions across the hospital.

When a patient visits OPD: (1) Front desk creates a consultation registration and assigns a token/queue position, (2) The doctor records clinical notes, prescriptions, and orders for lab/radiology/pharmacy, (3) Orders route to respective department workbenches for acknowledgement and fulfilment, (4) Billing captures consultation charges and service fees, (5) Receipts are collected and posted to the financial ledger.

For inpatient admissions: (1) An admission request is raised and a bed is allocated based on ward/category, (2) Nursing context is established for the admission, (3) Service orders (pharmacy issues, lab orders, radiology orders) are posted to the inpatient account, (4) Advance receipts are collected, (5) At discharge, a final bill is prepared with all posted services, and settlement workflows handle payor/corporate billing adjustments.

When a doctor places an order (lab test, radiology investigation, or pharmacy prescription), it appears on the respective department's workbench. The department staff acknowledges the order before processing. Lab technicians collect samples and enter results; radiology staff create reports; pharmacy staff dispense medicines. Each step is tracked and linked back to the originating consultation or admission.

Every clinical service (consultation, lab test, radiology investigation, pharmacy dispensing, procedure) generates a billable service line. These are automatically linked to the patient's billing account - OPD invoices for outpatients, and admission-level service posting for inpatients. Billing staff do not need to re-enter clinical details; the connection is maintained through shared patient and encounter references.

Under normal operations, no. All clinical and billing data stays within the hospital's on-premises infrastructure. Data leaves the hospital network only in two scenarios: (1) ABDM consent-based exchange, where the patient explicitly consents to sharing specific health records, and (2) Mobile app access for authorized staff connecting from outside the hospital network through secured API endpoints.

Pharmacy maintains store-wise stock with batch and expiry tracking. When a prescription is dispensed - either OPD walk-in sale or IPD patient issue - stock is deducted, billing is posted, and the transaction is linked to the patient record. Purchase inward, inter-store transfers, and returns are tracked with complete audit trails. Ledger posting on sale integrates with the hospital's financial records.

Lab results are entered by technicians against specific order lines, verified by authorized staff, and then linked to the patient's encounter history. Radiology reports follow a similar workflow: ordered, reported, verified. Results are accessible to the treating doctor through the patient's EMR/EHR record and to the patient through printed reports. All result entries carry audit trails with timestamps and user identity.

The Medical Records Department (MRD) module tracks physical file movement - issue, return, and location of patient folders. It manages document control workflows including discharge summaries, case sheets, and medico-legal records. MRD does not alter clinical data; it manages the physical and administrative custody of hospital records.

APSYS-Tejas includes ABDM-ready architecture with sandbox integration in progress. 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.

APSYS-Tejas is designed for three ABDM milestones: M1 (Identity) - ABHA verification and linking during registration; M2 (HIP) - care-context linking and consent-based health information sharing as a Health Information Provider; M3 (HIU) - requesting and receiving patient health records as a Health Information User, with controlled access and audit trails.

ABDM data exchange in APSYS-Tejas is designed around patient consent. A consent artefact is created specifying what data can be shared, with whom, and for how long. Only after consent approval does the system package and transmit health records. This is not bulk export - each sharing event is tied to a specific patient, purpose, and consent record, with full audit trails.

FHIR R4 (Fast Healthcare Interoperability Resources, Release 4) is an international standard for structuring clinical data exchange. APSYS-Tejas uses FHIR R4 as a translation layer for ABDM exchange - hospital data stored in APSYS entities is mapped to FHIR-compliant documents when sharing through ABDM workflows. FHIR is used for interoperability, not as the internal storage format.

Yes. ABDM exchange workflows require internet connectivity to communicate with the ABDM gateway and other participating health facilities. However, core hospital operations (OPD, IPD, billing, pharmacy, lab) continue to function on the local network even if internet connectivity is temporarily unavailable.

Scan & Share is an ABDM-aligned feature that allows patients to share their ABHA profile via a QR code at the hospital front desk. The registration staff scans the QR code to pull patient identity details, reducing manual data entry and linking the visit to the patient's national health identity. This feature is part of Milestone 1 readiness.

Yes. ABDM sharing is consent-driven and controlled. The hospital configures which types of clinical documents (discharge summaries, prescriptions, diagnostic reports) are available for sharing. Only records explicitly linked to care contexts are shareable, and each sharing event requires valid patient consent. The hospital administrator can review ABDM configuration and audit sharing activity.