Skip to main content
POST
Create Prior Auth Route

Overview

This endpoint is designed to streamline the submission of prior authorization requests for medications or treatments. It requires various key pieces of information about the patient, including demographics, insurance details, and the prescription in question. Additionally, the submission should include supporting evidence, such as visit notes, lab results, and intake forms, to justify the need for the prescribed medication or treatment.

How to Use

To effectively use this endpoint, please ensure the following information is included in your request:
  • Patient Demographics: Essential details such as the patient’s name, date of birth, and contact information.
  • Prescriber Information: Details about the prescribing healthcare provider, including the prescriber’s name, NPI (National Provider Identifier), contact information, and practice or facility details.
  • Insurance Details: A photo or scan of the patient’s insurance card (preferably front and back), including the group number, payer, membership number and RX details. If an image is not available, or the patient provided extra information not on their card (such as rx codes) you can also provide this structured data in the API.
  • Prescription Information: Detailed data on the prescribed medication or treatment, such as drug name, dosage, and administration instructions.
  • Evidence: Critical supporting documents and data such as visit notes and laboratory results. This section is particularly versatile, allowing for a variety of formats and contents to support the authorization request.
Given the diverse nature of medical records and evidence, our API is built to accommodate a wide range of data formats. Structured data can be filled into predefined fields, while unstructured data, such as additional JSON content about the patient, can be included in the content block within the evidence objects. This flexibility ensures that even non-standardized data can be effectively utilized in the prior authorization process.
We highly recommend you talk to a member of your company who actively submits prior authorizations when collecting the data for this endpoint. For the system to work effectively, we require the exact same data that those staff members currently have access to. A great test is to collect the data and see if the staff member is able to use that data alone to submit a new prior authorization through your existing system.

Response

After submitting a request, the system processes the data and returns a response indicating either the successful reception of the request or detailing any errors or additional information needed. Our advanced AI algorithms will analyze the provided information, including any uploaded files or scans, extracting and utilizing relevant details to facilitate the authorization process.

Building the Integration

We suggest taking the following approach when integrating:
  1. Make the API request for all prior authorizations that you need to submit, and let us handle coverage on our end. We’d recommend not feature flagging or limiting this to certain patients. Using this approach allows us to work with your ops team to resolve unsupported scenarios while giving you a complete view of which requests Develop Health can process.
  2. If you receive an error code, fallback to your company’s existing process for handling prior authorizations. We’ll gradually reduce the number of errors you receive as we expand to 100% coverage.
As a developer reading these docs we understand it might be difficult to know what data to provide and how best to structure it. Please know that we at Develop Health are here to help! A member of our engineering team will happily work with you to ensure you’re providing the right data in the right format.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Represents a request for creating a prior authorization for a medication. This includes detailed information about the patient, their diagnosis, prescribed medication, evidence supporting the need for treatment, insurance details, and responses to relevant questionnaires.

diagnoses
Diagnosis · object[]
required

Clinical diagnoses for the patient in ICD-10 format. i.e. 'E66.9'

patient
Patient · object
required

Demographic information for the patient

provider
Provider · object
required

Details of the healthcare provider who created the prescription.

evidence
EvidenceItem · object[]

A collection of evidence items supporting the authorization request. Any supporting evidence that doesn't belong in the other predefined fields can be added here.

insurance
InsuranceDocument · object[]

Insurance information for the patient. We will extract the required information from the insurance card images you provide. Please provide both the front and the back of the card. This is optional if you provide insurance_content, but highly recommended to ensure best results.

insurance_content
Insurance Content · object

Insurance information for the patient. Values provided here will be used in combination with those extracted from any insurance cards provided. We recommend providing this information when available to ensure best results. If you provide both insurance and insurance_content, the values provided here will be used and the values extracted from insurance will be used as a fallback.

prescription
CodedPrescription · object

Represents a prescription issued by a healthcare provider. This is an alternative to the Prescription model that is more closely aligned with NCPDP standards and helps reduce any confusion on the payer-side. Prefer this model over Prescription when NDCs are available.

pharmacy
Pharmacy · object

Information about the pharmacy where the prescription will be filled.

questionnaires
Questionnaire · object[]

List of questionnaires. This is the best place to send structured Q&A format data, such as intake forms, etc.

visit_notes
VisitNote · object[]

List of visit notes.

ndp_submission
PriorAuthRequestNDPSubmission · object

Configuration for processing the prescription associated with this PA request.

This field should only be provided when a prescription has been sent to Develop Health's non-dispensing pharmacy.

resubmission_info
PriorAuthRequestResubmissionInfo · object

Information provided when resubmitting a prior authorization request.

appeal_details
Appeal Details · object

Details for submitting an appeal of a previously denied prior authorization. When provided, the request will be processed as an appeal.

mock_result
PriorAuthMockResultApproved · object

Represents a mock result for a prior authorization request.

priority
enum<integer>
default:2

Specifies the priority of the prior authorization request. This is used to determine the order in which requests are processed. Lower values indicate higher priority.

Available options:
0,
1,
2,
3
trigger_benefit_verification
Trigger Benefit Verification · object

If provided and enabled, triggers a benefit verification to check drug coverage before the PA proceeds.

Response

Successful creation of a prior authorization

Models the response received upon creating a prior authorization request.

status
default:success
Available options:
success
error
Error · object

Error payload of the response, containing details of the error that occurred during the creation of the prior authorization request.

data
Data · object

Data payload of the response, containing details of the created prior authorization request, or None if the request was unsuccessful.