Medication Prior Auth Webhook
When using the ePA solution in Akute, an organization can set up webhooks in Akute to be sent when there is an update to a prior auth (PA) request.
Webhooks can be set up in the Settings->Developer section in Akute.
The PA webhook contains many fields detailing information about the PA meta data (e.g. case id), PA history, and PA status. Below is documentation explaining the data structure and the meaning of the fields.
case_id
status
enum:
0: "unknown", 1: "requested", 2: "not required", 3: "closed", 4: "deferred", 5: "action required", 6: "pending", 7: "approved", 8: "denied", 9: "appeal requested", 10: "cancel requested", 11: "canceled", 12: "cancel denied", 13: "error", 14: "deleted", 15: "partially denied", 16: "in process"
pharmacy_type
enum:
0: "Unknown", 1: "Retail", 2: "MailOrder", 3: "SpecialtyPharmacy", 4: "LongTermCarePharmacy", 5: "Any", 6: "TwentyFourHourPharmacy", 7: "FaxPharmacy", 8: "EPCS", 9: "InHouseDispensing", 10: "Compounding", 11: "DME", 12: "Kiosk", 13: "SupportsDigitalSignature", 14: "FaxPharmacyExternal"
closed_reason
enum:
0: "Unknown", 1: "ElectronicPriorAuthNotSupported", 2: "Other", 3: "PriorAuthNotRequired", 4: "CannotFindMatchingPatient", 5: "PatientNotEligible", 6: "PriorAuthDuplicateApproved", 7: "PriorAuthDuplicateInProgress", 8: "ClosedByPayer", 9: "ClosedByProvider", 10: "ClosedByMember", 11: "AttachmentTypeNotSupported", 12: "PrescriberNotAllowedToSubmitPAReqest", 13: "ResponseInconsistentWithQuestion", 14: "ReceiverNotPAProcessorForThisPatient", 15: "ReceiverNotPAProcessorForPatientMedicationCombo", 16: "DuplicateDenied", 17: "ProviderRespondedAfterDeadlineToReply", 18: "ProductNotCoveredByThisPlanPriorAuthorizationNotAvailable", 19: "PrescriptionWithinPrescribingLimitsPriorAuthorizationNotRequiredForPatientMedication", 20: "CoverageLimitsMayExistForQuantityAndOrDaysSupply", 21: "CoverageLimitsHaveBeenExceededExceptionNotAvailable", 22: "ActivePAOnFile", 23: "SubmittedProductCodeIsNotValid"