eClaims and Preauth APIs

Preauth Doctor Consent

Endpointhttps://ilm-dev.dha.go.ke/uat-middleware/api/v1

Endpoints for doctor consent in preauthorization.

Resend doctor request

POST

https://ilm-dev.dha.go.ke/uat-middleware/api/v1

/claims/doctor-consent

Resends a doctor approval request. Choose the request shape that matches the context: preauthorization, emergency claim, or EMT claim. The request_type must match the chosen shape.

Related documentation: Resend Doctor Consent, Preauth Doctor Consent

Resend doctor request › Headers

X-Facility-Id

string

Facility Registry (FR) code identifying the facility. Required when authenticating with a service-account token.

Example: FID-47-115307-8

X-Facility-Id-Type

string

Type of identifier supplied in X-Facility-Id. Currently only fr-code is supported.

Example: fr-code

Resend doctor request › Request Body

oneOf

Exactly one variant must match.

Decision Table

Variant	Matching Criteria
	type = object · requires: practitioner_registration_number, request_type, consent_token +1 more
	type = object · requires: request_type, consent_token, intervention_code +5 more
	type = object · requires: service_type, request_type, emergency_claim_id +5 more

Properties for Resend Preauth Doctor Request:

Resend a doctor approval request for a preauthorization.

practitioner_registration_number

string · required

Registration number of the doctor whose approval is being requested. Example is dummy data.

Example: A00000

request_type

string · enum · required

Type of doctor request. Use PREAUTH_DOCTOR_APPROVAL_REQUEST for preauthorizations.

Enum values:

PREAUTH_DOCTOR_APPROVAL_REQUEST

Example: PREAUTH_DOCTOR_APPROVAL_REQUEST

consent_token

string · required

Patient consent token authorising the doctor request.

Example: K5HLPJVDNV

intervention_code

string · required

SHA intervention code the request is issued against.

Example: SHA-11-001

Resend doctor request › Responses

Doctor request resent successfully

Standard success response format for all successful operations.

object

@Description Response data payload containing operation details @Example {"status": "success"}

message

string

@Description Success message describing the operation result @Example "Visit has been successfully started"

POST/claims/doctor-consent

curl --request POST \
  --url https://ilm-dev.dha.go.ke/uat-middleware/api/v1/claims/doctor-consent \
  --header 'Content-Type: application/json' \
  --data '
{
  "practitioner_registration_number": "A00000",
  "request_type": "PREAUTH_DOCTOR_APPROVAL_REQUEST",
  "consent_token": "K5HLPJVDNV",
  "intervention_code": "SHA-11-001"
}
'

shell

Example Request Body

{
  "practitioner_registration_number": "A00000",
  "request_type": "PREAUTH_DOCTOR_APPROVAL_REQUEST",
  "consent_token": "K5HLPJVDNV",
  "intervention_code": "SHA-11-001"
}

json

Example Responses

{
  "data": {},
  "message": "message"
}

json

application/json

Billing ePrescriptions