Skip to main content
Use this guide to test your Document Validation integration in our QA environment. By setting a specially formatted member number on a patient plan, you control the validation results Silna returns for the documents you upload to a prior authorization: every rule passes, every rule fails, a realistic mix, or no results.
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):
  1. Create a patient plan with a member number that contains a scenario code (see Member Number Format)
  2. Create a prior authorization for that patient plan
  3. Update the prior authorization with documents attached to the document types you want validated
  4. Poll Get Prior Authorization with with_requirements=true until the status is DATA_REQUESTED or ALL_REQUIRED_DATA_RECEIVED
  5. Read required_data.documents[].document_validation_batch and fetch the rule results with Get Document Validation Batch
When a scenario code is present, Silna does not read the uploaded files. It returns the scenario’s results for the same validation rules that a real validation would run. You can upload any PDF. The rules come from the payor and provider rule sets for that document type, the same as in production. Document types with no validation rules are not validated.

What stays the same as production

  • The rules that run, their names, and the reason text for each rule result
  • The prior authorization status after validation: ALL_REQUIRED_DATA_RECEIVED when every rule passes, otherwise DATA_REQUESTED with requirement_satisfied: false
  • Overriding validations with document_validation.enabled: false or skip_document_intelligence: true

Member Number Format

Add DV followed by a two-digit scenario code anywhere in the member number:
This format works with the other QA testing guides too. In A_PA01_DV02_11: So one test patient plan can drive a benefits check test, document validation results, and a prior authorization outcome. 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.