📒
HCX Protocol
v0.7
v0.7
  • Summary
  • Context
  • Introduction to HCX
  • Approach
    • Design Principles
    • Key Specifications
    • Governance
  • Technical Specifications
    • Open Protocol
      • Registries
      • Health Claims 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
    • 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
    • Guidelines for Event audits
    • Guidelines for Beneficiary Authentication by Providers/Payors
  • Contributing to the specifications
  • Future Roadmap
Powered by GitBook
On this page
  1. Technical Specifications
  2. Open Protocol
  3. Data Security and Privacy

Transport Security

TLS as default mode of communication

All communications between health claims exchange(s) and participating entities are expected to be done using Transport Layer Security. Therefore all APIs are expected to work only as HTTPS in the production environments.

PreviousData Security and PrivacyNextMessage Security and Integrity

Last updated 3 years ago