HCX Protocol
v0.9
v0.6v0.7v0.8v0.7.1v0.9
v0.9
v0.6v0.7v0.8v0.7.1v0.9
  • Summary*
  • Glossary*
  • Context
  • Introduction to HCX*
  • Technical Specifications
    • Open Protocol
      • Registries*
        • QR Code Specifications*
      • Claims Data Exchange (HCX) Protocol
        • Message Flows*
          • Primary Message Flow
          • Additional Message Flows
            • Redirect
            • Forward
            • Intra Cycle Communication*
              • Seeking Supporting Information
              • Seeking Beneficiary Consent
              • Seeking Account Information
            • Relay
            • Third party Information sharing
          • Notifications
            • Categories
            • List of key topics
        • Message Structure
        • API Specifications*
          • Registry APIs
          • Primary Flow APIs
          • Supporting APIs
          • Notification APIs
        • Error Handling
      • Data Security and Privacy
        • Transport Security
        • Message Security and Integrity
        • API Security*
      • Audit and Reporting
    • Digital Network Policies
  • Domain Specifications
    • Domain Data Models
      • Handling Attachments
      • Handling Processing Errors
    • Terminologies
    • Domain Specific Languages (DSLs)
    • FHIR Implementation Guide*
  • Business Policy Specifications
    • Access Control (Roles)*
    • Guidelines for Participant Onboarding*
      • Sandbox process
      • Production onboarding (Go live)*
      • Potential De-boarding scenarios
    • Guidelines for Grievance Redressal
      • Scope of disputes
      • Involved participants
      • Guideline process for dispute resolution
      • Guidelines for leveraging FTA
      • Next steps
    • Guidelines for SLAs and ecosystem satisfaction
    • Guidelines for Operating charges
    • Guidelines for Beneficiary Authentication by Providers/Payors
    • Guidelines for Event audits
    • Reference Templates
      • HCX - Terms of use
      • Payer-Provider addendum
      • Payer-Policyholder addendum
    • Next steps
  • Use cases*
    • OPD
      • Typical Workflows
        • Cashless
        • Reimbursement
      • Mapping to the HCX protocol
        • Cashless
        • Reimbursement
    • IPD
      • Typical Workflows
        • Cashless
        • Reimbursement
      • Mapping to the HCX protocol
        • Cashless
        • Reimbursement
    • Implementation Considerations
  • Contributing to the protocol
  • Future Focus Areas*
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Business Policy Specifications

Guidelines for Participant Onboarding*

Process of onboarding network participants

PreviousAccess Control (Roles)*NextSandbox process

Last updated 1 year ago

Was this helpful?

This section has been enhanced to accommodate the scope and the requirements of , and address the on-ground provider onboarding realities. The key changes include:

  1. Addition of BSP Onboarding Recommendations: To align with the evolving healthcare landscape, recommendations for onboarding Beneficiary Service Platforms (BSPs) have been incorporated.

  2. Enhancement of "Non ABDM enrolled Providers with no ROHINI id": This section has been expanded to encompass a comprehensive approach to provider onboarding. It now includes verification processes involving both public and private payers, reflecting the current industry practice. This update acknowledges the practical realities of onboarding healthcare providers and ensures a more inclusive and adaptable onboarding process within the network.

While the actual onboarding/deboarding process for an HCX ecosystem would be drafted by its operator and agreed upon by its participants, this section outlines key design guidelines and an overall approach to arrive at such a policy.

Key design considerations

Building further from the key design considerations laid out for business policies in the HCX open specifications, the onboarding approach should:

  1. Aim to enable rather than control the participation of the interested ecosystem actors.

  2. Require minimal and necessary information, enough to prove the identity of the participant and enable working of the network. The process requirements should be non-discriminatory and at the same time require enough detail to keep out any frivolous organisations.

  3. Needs to be simple and cost effective enough to encourage participation of entities working with low income segments.

A list of different kinds of participants who would need onboarding into an HCX registry is provided in the section above. Onboarding onto the HCX is envisioned as a two step process:

  1. Sandbox - for compliance testing and certification

  2. Go Live on live instances

Diagrams below depicts the key steps in onboarding process across these two phases: Proposed onboarding process flow; Sections below provide high level description for each of these steps:

Envisioned onboarding process flow

Following subsections provide high level description for each of these phases.

OPD and Reimbursement use cases
Access Control