You will only receive this webhook if you are not storing the health data on Eka servers. If you use Eka’s Upload API to store records, Eka handles data sharing automatically.
- Prepare an ABDM-compliant FHIR bundle for each care context listed in the
care_contextsarray. - Encrypt the FHIR data using the
key_informationprovided in the webhook payload (ECDH-based encryption). - Push the encrypted data to the HIU using the Care Context Data On-Fetch API. Use the
transaction_idfrom this webhook in the on-fetch request.
Request
Headers:Eka-Webhook-Signature:<Eka Webhook Signature>Refer: Webhook SignatureContent-Type:application/json
Field Descriptions
data: Contains additional details related to the event.-
hi_types: Health information types requested by HIU- Available options:
OPConsultation,Prescription,DischargeSummary,DiagnosticReport,ImmunizationRecord,HealthDocumentRecord,WellnessRecord
- Available options:
-
key_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.
-

