Skip to main content

Classification (via DVS)

When you upload a support file via the v1 endpoint, you tell RCM exactly what type the document is (support_file_code=TISS_GUIDE). RCM trusts you and skips straight to validation.

When you upload via v2 with support_file_code omitted, RCM doesn't know either — so it asks DVS (Document Validation Service). DVS reads the file and returns the document type it identifies, or a failure code if it can't return a reliable answer. RCM then persists the detected support_file_code on the support file record and proceeds to validation.

Why classification matters​

The support_file_code determines:

  1. Which DVS extraction schema is applied (a TISS guide and a pathology report have very different field sets).
  2. Which rule set runs during validation (the rules for OPME_REQUEST are different from those for MEDICAL_ORDER).

Misclassifying a document gives misleading validation rejections — the rules look for the wrong fields. So if you're confident about the type, pass it explicitly via v1. If you're not, let DVS decide via v2.

How DVS classifies​

OSIGU's DVS is documented at dvs-docs.osigu.com. It reads each document and returns the best-matching support_file_code from the catalogue configured for your (country, agreement_code). The evaluation is content-aware — DVS looks at the actual structure and text inside the document, not at file metadata or filename.

When DVS can't return a result it considers reliable, it emits a LOW_CONFIDENCE failure code instead of guessing. Treat that as a signal to either re-upload a cleaner copy of the document, or to fall back to the v1 endpoint with an explicit support_file_code if you actually know what the document is.

What you'll see​

For a v2 upload, you'll get one of these webhooks:

  • DOCUMENT_CLASSIFICATION_COMPLETED — RCM persisted the detected type and associated the document. RCM then runs validation. A DOCUMENT_VALIDATION_* webhook follows in another 10–30 seconds.
  • DOCUMENT_CLASSIFICATION_FAILED — DVS couldn't classify confidently. The file sits in UNCLASSIFIED state. No validation event will follow. You either re-upload a clearer scan, upload with the correct support_file_code via v1, or contact OSIGU support if the document type isn't in the catalogue for your agreement.

See Webhook events → Classification for the full payload, including the alternatives list and the reason_code for failures.