NHA / ABDM approval
Production credential activation and milestone sign-off depend on NHA/ABDM processes - not claimed as completed on this website.
ABDM integration
ABDM-ready workflows in APSYS-Tejas
APSYS-Tejas includes ABDM-ready architecture for Indian healthcare providers preparing structured digital health exchange. ABDM sandbox integration is in progress and subject to NHA/ABDM approval.
Overview
Designed for M1, M2 and M3 workflows
APSYS-Tejas supports identity linking, care-context handling, consent-based data exchange, auditability, and secure configuration aligned with ABDM integration milestones.
Current readiness: APSYS-Tejas includes ABDM-oriented architecture and workflow hooks for M1, M2, and M3 milestones. Sandbox integration and validation are in progress at APSYS INDIA Pvt. Ltd.
Pending official validation
What remains before production ABDM exchange
Sandbox validation
Integration scenarios, callback handling, and document exchange paths are being exercised in ABDM sandbox environments.
Regulatory alignment
Hospital-specific policies, consent capture, and audit retention must align with applicable regulatory and institutional requirements at go-live.
FT / WASA audit
External functional testing and web application security assessment are planned before production-facing ABDM exchange.
HTC demo / audit
APSYS-Tejas is being prepared for required demonstration and audit steps linked to ABDM milestone readiness.
Remediation evidence
Audit observations, fixes, configuration proof, and workflow evidence will be documented before any production claim.
Important: 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 or production approval on this page.
Implementation support
How APSYS supports ABDM rollout with APSYS-Tejas
Readiness assessment
Review hospital registration, OPD/IPD workflows, document types, and consent touchpoints against planned ABDM milestones.
Sandbox configuration
Configure APSYS-Tejas endpoints, credentials, and test patients in ABDM sandbox with APSYS technical support.
Staff training
Train front desk, clinical, and IT teams on ABHA linking, care-context steps, and consent-aware sharing within existing Tejas screens.
Production activation
After official validation, migrate to production credentials with phased module activation and audit review.
For ABDM-specific communication, email abdm@apsys.in or contact APSYS INDIA Pvt. Ltd. through the corporate contact page.
Documents & evidence
Traceability and audit-friendly exchange
Event logging
ABDM-related requests, callbacks, and sharing events are designed for traceable hospital audit review.
FHIR R4 alignment
Structured clinical document paths follow FHIR R4-oriented exchange patterns within controlled workflows.
Consent records
Consent request and approval steps are tied to patient context - not anonymous bulk export.
Configuration control
Production vs sandbox settings are separated so test activity does not contaminate live patient operations.
Milestone 1
Patient identity and intake
ABHA verification and linking
Verify patient ABHA details and link hospital records where applicable.
Registration integration
Registration workflows support ABDM-ready identity capture and matching.
Scan & Share intake
QR-based patient arrival support for front-desk queue workflows.
Milestone 2 HIP
Health information provider
Patient ABDM profile
Maintain ABDM-linked profile information within controlled patient workflows.
Care context linking
Link hospital visits, encounters, and records to patient care contexts.
Consent-based sharing
Exchange health information through consent-oriented, auditable workflows.
FHIR R4 documents
Structured clinical document exchange using FHIR R4-aligned workflows.
Milestone 3 HIU
Health information user
Consent request
Request patient consent for permitted health information access.
Health information request
Initiate requests after valid consent workflow completion.
Received record review
Review received records inside controlled hospital access workflows.
Audit trail
Traceable events for requests, callbacks, sharing, and review.
Disclaimer
ABDM integration and readiness features are under sandbox validation and subject to NHA/ABDM approval, production credential activation, and applicable regulatory requirements. APSYS INDIA Pvt. Ltd. does not claim ABDM approval, NHA certification, or ABDM production-ready status unless and until official approval or certificate is published by the relevant authority and communicated by APSYS.
Hospital customers should treat ABDM go-live as a joint implementation between the institution, APSYS, and NHA/ABDM processes - not as an automatic switch bundled with standard HMIS licensing.