HCX Protocol
v0.8
v0.8
  • Summary
  • Context
  • Introduction to HCX
  • Approach
    • Design Principles
    • Key Specifications
    • Governance
  • Technical Specifications
    • Open Protocol
      • Registries
      • Claims Data Exchange (HCX) Protocol
        • Exchange Protocol
        • Message Structure
        • API Structure
        • Error Handling
      • Data Security and Privacy
        • Transport Security
        • Message Security and Integrity
        • API Security
      • Audit and Reporting
      • Notifications
        • Terminology
        • Categories
        • API specifications
        • List of key topics
        • Future considerations
      • Third party Information sharing
    • Digital Network Policies
  • Domain Specifications
    • Domain Data Models
      • Handling Attachments
      • Handling Processing Errors
    • Terminologies (Code sets or Metadata standards)
    • Domain Specific Languages (DSLs)
    • Implementation Guide
  • Business Policy Specifications
    • Access Control (Roles)
    • Guidelines for Participant Onboarding
    • 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
  • Contributing to the specifications
  • Future Roadmap
Powered by GitBook
On this page
  • Key resources
  • Contributing to the specs

Was this helpful?

Edit on GitHub

Contributing to the specifications

Key resources and guidelines to contribute

PreviousNext stepsNextFuture Roadmap

Last updated 2 years ago

Was this helpful?

As mentioned in the governance section, hcx-specifications are fundamental to the success of the envisioned claims network. Specifications need to create consensus amongst a broad base of health system stakeholders to ensure that they can act as this common foundation. Current specifications are a result of collaborative effort from many committed volunteers.

We look forward to further strengthening the collaboration with border participation. Sections below provide the key resources and mechanisms to contribute to the specifications.

Key resources

Key resources for this version (v0.8) are available as follows:

  • is the reader friendly published documentation for the current version.

  • Source code for documentation and specifications is available in .

  • Discussions about the specifications are in the github repo’s and on the .

Contributing to the specs

Enhancement requests/ideas/suggestions/questions

Please use the github discussion forum to ask questions, make suggestions, and raise enhancement requests. You can also participate in the existing discussion by appropriately commenting on the discussions of your interest.

Raising issues

Issues can be raised to bring attention to any shortcoming in the specifications ( e.g. API specifications, Domain Data specifications - eObjects, Documents, Value Sets, Implementation Guide etc.) using one of the following mechanisms:

  1. A confirmed issue can be raised as a github issue against the repo .

  2. If unsure about the issue, it can be raised as a discussion in GitHub or Discord with the community and can be converted to an issue on confirmation.

We aim to make hcx-specifications one of the best open community projects with your help. In order to achieve this, we expect the participants to follow and adhere to the while participating in the forum.

If for some reason, you cannot raise issues using github, you can also send them via email to .

However, to get the best assistance from the community, get timely responses and benefit everyone from the observations, we strongly encourage everyone to use the github forum. Please use to sign up for a free github account, if you dont already have one. You can then write to us at with your github id to include you as a part of the github community for the hcx-specifications.

This specification document can also be downloaded as a PDF for offline consumption. Instructions to download specifications as a PDF are available .

This GitBook documentation
this GitHub repo
discussion forum
discord server
here
GitHub's community Guidelines
GitHub Community Forum Code of Conduct
contact@hcxprotocol.io
these instructions
contact@hcxprotocol.io
here