Test scenarios only run in our QA environment (
api-qa.silnahealth.com). They are never triggered in production.How It Works
The workflow is the same as production (see Document Validation Overview):- Create a patient plan with a member number that contains a scenario code (see Member Number Format)
- Create a prior authorization for that patient plan
- Update the prior authorization with documents attached to the document types you want validated
- Poll Get Prior Authorization with
with_requirements=trueuntil the status isDATA_REQUESTEDorALL_REQUIRED_DATA_RECEIVED - Read
required_data.documents[].document_validation_batchand fetch the rule results with Get Document Validation Batch
What stays the same as production
- The rules that run, their names, and the
reasontext for each rule result - The prior authorization status after validation:
ALL_REQUIRED_DATA_RECEIVEDwhen every rule passes, otherwiseDATA_REQUESTEDwithrequirement_satisfied: false - Overriding validations with
document_validation.enabled: falseorskip_document_intelligence: true
Member Number Format
AddDV followed by a two-digit scenario code anywhere in the member number:
A_PA01_DV02_11:
- The Benefits Check QA Testing Guide reads the leading
Aand the trailing insurance code (11) - The Prior Authorization QA Testing Guide reads
PA01 - Document Validation reads
DV02
Member numbers without a
DV code, or with an unknown code, run a normal document validation.
Scenarios
Mixed results (03)
The failing rules depend on the document type, so you see a realistic partial failure:
For example, a
REFERRAL validated with clinician, time frame, and diagnosis rules returns:
No results (04)
Use this scenario to test how your integration handles a validation that produces no rule results. The batch result is PASSED, each document validation has empty passed_rules, failed_rules, and rule_results, and the prior authorization moves to ALL_REQUIRED_DATA_RECEIVED.