Endpoint for creating authorizations using biometrics or OTP.
Retrieve an existing authorization
Retrieves existing authorizations. All query params are OPTIONAL and act as a one-of search: look up by token, by patient_id, or by guid. Supply whichever identifier you have.
Related documentation: Get Authorizations
query Parameters
tokenConsent token for the authorization (one-of search)
patient_idBeneficiary id (one-of search) Dummy example — obtain a real value from the Patient Search API.
guidAuthorization GUID (one-of search)
Headers
X-Facility-IdFacility Registry (FR) code identifying the facility. Required when authenticating with a service-account token.
X-Facility-Id-TypeType of identifier supplied in X-Facility-Id. Currently only fr-code is supported.
Retrieve an existing authorization › Responses
Authorizations retrieved successfully
authCodeauthorizationReasonauthorizationTypeauthorizingDeviceOsbeneficiarybeneficiaryCodebeneficiaryJoinDatebeneficiaryNamebeneficiaryNumberbeneficiarySchemebenefitTypebiometricMatchLogIdcreated_bydateAuthorizedekycTokenendDateexpiryguardianguididisBiometricsDischargeAuthorizationisCompleteisElectiveisEmergencyisOpenlabelneedsPreauthnotesoverallPreauthFinalisedparentAuthorizationparentTypeproviderproviderFidproviderNamerequestedBysessionTypeshaGuidshaVerificationRequestIdstatustokenupdated_byworkStationIdReject a pending biometrics authorization
Rejects an existing pending biometrics authorization. The consent_token supplied in the path is the token returned on the created authorization object.
Related documentation: Reject Authorization
path Parameters
consent_tokenToken returned on the created authorization
Headers
X-Facility-IdFacility Registry (FR) code identifying the facility. Required when authenticating with a service-account token.
X-Facility-Id-TypeType of identifier supplied in X-Facility-Id. Currently only fr-code is supported.
Reject a pending biometrics authorization › Responses
Authorization rejected
messageCreate a new authorization (OTP or biometrics)
Creates a new authorization by capturing patient consent via OTP or biometrics. Use the OTP strategy for standard outpatient and inpatient consent; use the biometrics strategy (eKYC or fingerprint) when the facility has a registered hardware agent. The same endpoint is used across claims creation and consent workflows.
Related documentation: Start Visit Workflow, Biometrics Integration
Create a new authorization (OTP or biometrics) › Request Body
Decision Table
| Variant | Matching Criteria |
|---|---|
| type = object · requires: patient_id, service_type, otp +1 more | |
| type = object · requires: agent_id, authorizing_device_os, ekyc_provider_id +9 more |
patient_idThe patient's Client Registry identifier. Dummy example — obtain a real value from the Patient Search API.
service_typeType of service being authorized.
otpOne-time password delivered to the patient's registered phone number.
interventionsList of intervention codes for the services being requested in this visit.
Create a new authorization (OTP or biometrics) › Responses
Authorization created successfully
authCodeauthorizationReasonauthorizationTypeauthorizingDeviceOsbeneficiarybeneficiaryCodebeneficiaryJoinDatebeneficiaryNamebeneficiaryNumberbeneficiarySchemebenefitTypebiometricMatchLogIdcreated_bydateAuthorizedekycTokenendDateexpiryguardianguididisBiometricsDischargeAuthorizationisCompleteisElectiveisEmergencyisOpenlabelneedsPreauthnotesoverallPreauthFinalisedparentAuthorizationparentTypeproviderproviderFidproviderNamerequestedBysessionTypeshaGuidshaVerificationRequestIdstatustokenupdated_byworkStationId
