Webhook event is sent when an external HIP pushes encrypted health data to your HIU. The Health Information User (HIU) can initiate a consent request through the Consent-API to get care context data. Once consent is validated, the Health Information Provider (HIP) sends the encrypted health data to the HIU.Documentation Index
Fetch the complete documentation index at: https://ekacare-mintlify-changelog-1776733918.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Request
Headers:Eka-Webhook-Signature:<Eka Webhook Signature>Refer: Webhook SignatureContent-Type:application/json
Field Descriptions
data: Contains additional details related to the event.consent_id: Consent id for the data transfertransaction_id: Transaction id for the data flowentries: List of care contexts with encrypted fhir datakey_information: Contains the cryptographic key material and related parameters required for secure ECDH-based key exchange between HIU and HIP.crypto_algThe cryptographic algorithm used for key exchange (e.g., “ECDH”).curveThe elliptic curve used in ECDH key generation (e.g., “Curve25519”, “P-256”).dh_public_keyObject containing the HIU’s public key and related metadata:expiryThe expiration timestamp (in ISO 8601 format) indicating how long the public key is valid.parametersAdditional parameters related to the ECDH key (optional or curve-specific).key_valueThe base64-encoded public key value generated by the HIU.
nonceA 32-byte random nonce (Base64-encoded) generated by the HIU, used to ensure uniqueness in the session key derivation.

