Submit the reply to a share request with the data push URL and the encryption key
Acts as the callback endpoint for the PHR application.
After the initial request, the HIU responds to this callback with the data push URL and the encryption key required for securely transferring the user's health records.
The HIU makes this call after receiving the share request on its /api/v3/patient-record/share bridge endpoint. The transactionId is the one that request carried, and response.requestId is that request's REQUEST-ID. The HIE-CM forwards the body to the PHR app's /api/v3/patient-record/on-share callback. JWT access token issued by the ABDM session API after successful validation of client id and secret. Random UUID, a v4 style guid, unique per request. ISO 8601 timestamp of when the request was initiated. Identifier of the health information user to which the request was intended. Suffix of the consent manager to which the request was intended. sbx in the sandbox, abdm in production. The data push URL and the encryption key. The transactionId the share request carried. The HIU's URL the PHR app posts the encrypted records to. The REQUEST-ID of the share request this answers. Accepted. The HIE-CM forwards the data push URL and key to the PHR app's on-share callback.Authorizations
Authorizationbearer tokenRequiredHeaders
REQUEST-IDstringRequiredTIMESTAMPstringRequiredX-HIU-IDstringRequiredX-CM-IDstringRequiredBody
hiRequestobjectRequiredhiRequest.transactionIdstringRequiredhiRequest.dataPushUrlstringRequiredhiRequest.keyMaterialobjectRequiredresponseobjectRequiredresponse.requestIdstringRequiredResponses
202
Callbacks
- After this call, ABDM posts Receive the HIU's data push URL and encryption key, as the PHR app. to
/api/v3/patient-record/on-share. Open the callback. - After this call, ABDM posts Receive the encrypted records at the data push URL, as the HIU. to
/health-information/transfer. Open the callback.