Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What are the APIs a Provider/Payer needs to develop to integrate with HCX? #198

Open
saurabh-singh-17 opened this issue Jul 7, 2022 · 2 comments

Comments

@saurabh-singh-17
Copy link
Collaborator

No description provided.

@saurabh-singh-17
Copy link
Collaborator Author

Providers can make below listed calls to HCX which HCX will verify for primary checks (List of checks is available in Error codes ) and if all checks pass then it will be forwarded to the Payor System.

   /v1/coverageeligibility/check
   /v1/preauth/submit
   /v1/claim/submit
   /v1/paymentnotice/on_request

A provider system should accept following APIs calls from HXC:

  /v1/coverageeligibility/on_check
   /v1/preauth/on_submit
   /v1/claim/on_submit
   /v1/paymentnotice/request

Notifications and search APIs to come soon and specs will be updated at 0.8 version

@saurabh-singh-17
Copy link
Collaborator Author

Payors can make below listed calls to HCX which HCX will verify for primary checks (List of checks is available in Error codes ) and if all checks pass then it will be forwarded to the Provider System.

  /v1/coverageeligibility/on_check
   /v1/preauth/on_submit
   /v1/claim/on_submit
   /v1/paymentnotice/request

A payor system should accept following APIs calls from HXC:

   /v1/coverageeligibility/check
   /v1/preauth/submit
   /v1/claim/submit
   /v1/paymentnotice/on_reques

More information available at https://docs.swasth.app/hcx-specifications/hcx-technical-specifications/open-protocol/key-components-building-blocks/api-structure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant