Frequently Asked Questions

A connector is a software component or tool that enables healthcare applications to communicate and share data with ABDM / NHCX Server. It bridges diverse platforms, ensuring interoperability and seamless integration. Connectors standardize data formats and protocols, facilitating efficient and secure data exchange. 

There are two types of the Connectors

A] Certified connector:

Certified connectors are standalone products with UI and workflow.

e.g. ABDM Certified PHR that includes Q management workflow and UI for scanning the QR. This type needs a limited customisation ( say only registration module ) of HIS System that they co-exist with OR

e.g. NHCX Certified Claim Processor for Hospitals. This uses scanning and importing function for the claim documents and addresses revenue cycle management for the hospitals.

B] Connector enabling the Client’s system that gets certified by NHA. This is a pass-through service layer that essentially passes messages back and forth complying with the interoperability standards. This service layer can be on -prem or on web. The client system incorporates this pass-through service as a part of their product and solution and obtains certification from NHA / empaneled agencies.

OneHCX Connector Suite has the following independent Connector modules available:

OneHCX –  ABDM Connector  – for enabling compliance Milestones M1, M2, M3

OneHCX – NHCX Connector (CP) – For enabling Care Providers to connect to NHCX

OneHCX – NHCX Connector (I) – For enabling Insurance / TPA / Claim Aggregators.

Domain knowledge:  The OneHCX Connector inherits know-how on health informatics and ABDM digital framework / compliance wherewithal from its parent organizations with established credentials of enabling 130+ Healthcare IT companies ( ABDM integrators ). We therefore know the difficulties and challenges faced by integrators of diversified tech stacks and architectures of their products.

Simplified OneHCX APIs: The Connector facilitates healthcare applications by providing APIs  with lesser complexity of creation of FHIR bundles, encryption, asynchronous API calls etc. Healthcare applications consumes these simplified APIs to exchange data, and the Connector communicates with the ABDM ecosystem. In certain scenarios, OneHCX aggregates multiple back and forth calls that are purely technical in nature and provides a single API call  for a use-case / compliance scenario where the ABDM /NHCX server may require multiple calls.

Reduced manpower for integration: Use of OneHCX reduces 60-80% of man days necessary for certification and on-going efforts in terms of retaining the compliance amid the fast-changing ABDM framework.

Yes, with OneHCX, it is mostly a one-time exercise. As long as the data schema/ elements remain the same, any new version released by ABDM / NHCX will get automatically adopted by corresponding new version of OneHCX. However, if a new data element is included, a marginal effort may be needed additionally by the Subscriber.

The incentives associated with ABDM, the limits / qualifiers for the transactions and other criteria are entirely for NHA to decide and implement. The scheme is in the public domain, on ABDM website. OneHCX does not take any responsibility or does not promise anything about the incentivization by NHA.

Annual subscription of OneHCX includes updates that ensure compliance with ABDM updates. Optional upgrades that may offer additional features / new use cases are chargeable. OneHCX will ensure backward compatibility of versions for ABDM V3.0 or later and as long as ABDM does not declare the versions obsolete.

Data will be stored in AWS S3. Versioning and encryption used with RSA_2048,  no direct access via console, and multi region replication. It therefore complies with the latest security norms available and it gets WASA tested as per NHA norms before the application goes in the ABDM / NHCX production environment. OneHCX subscription agreement covers data privacy related points as per DPDP act. 

The Connector offers annual subscription on SaaS basis, that includes certain free transaction and beyond a limit, the charges are applicable per-additional-transaction.

If the Subscriber ensures that the resources and the responses / communication is provided in a timely manner then the functional certification is possible typically in 45-60 days for each module.