Provider Products
Osigu maintains a global catalogue of medications, labs, imaging studies, and procedures. Individual providers only sell/perform a subset of that catalogue — a pharmacy carries the ~2,000 SKUs it actually stocks, a clinic offers the ~120 procedures it actually performs.
The provider product catalogue is that per-provider subset. Every pre-authorization request and every electronic prescription must reference product codes that are (a) present in Osigu's global catalogue, and (b) registered as provider products by your provider.
Why this matters
If you try to issue a pre-authorization for a product_code that isn't in your provider-product list, Osigu returns 422 Validation error with error_code: 071-104 (Product not registered). Register the product first, then retry.
Same applies to prescriptions and to claim line items — a claim can only bill for products the provider has registered.
Endpoints
Only two operations are needed:
| Endpoint | Purpose |
|---|---|
POST /arc/v1/providers/products | Add a product to the provider's catalogue. Body is { "product_code": "..." } referencing an existing entry in Osigu's global catalogue. |
DELETE /arc/v1/providers/products/{productCode} | Remove a product from the catalogue. Doesn't affect historical authorizations/prescriptions/claims. |
To read the current provider-product list, use the catalogue lookup: listProviderProducts under Prescriptions.
Discovery pattern
The typical integration flow at provider onboarding is:
- Fetch Osigu's global medication / procedure catalogues (
listMedications, and equivalents for the other product types). - Cross-reference against your inventory / master data.
- Register your intersection via
registerProviderProduct(once per code). - Persist locally so you don't re-register on every startup.
Related concepts
- Prescriptions — must reference provider products.
- Authorizations — same constraint.
- Claims — same constraint.