Admin Configuration

Before patients can submit cases, admins configure the catalog and staff mappings. This is separate from the live case journey but required for the service to operate.

Configuration overview

flowchart LR
  subgraph Catalog["Catalog"]
    RT[Review types]
    DC[Disease categories]
  end

  subgraph Staff["Staff mapping"]
    CC[Case coordinators per specialty]
    MD[Doctors mapped to disease categories]
  end

  RT --> Cases[Patient creates case]
  DC --> Cases
  CC --> Assign[Admin assigns coordinator to case]
  MD --> DocAssign[Coordinator assigns specialists]

Review types

Admins define the types of second opinion offered (e.g. standard vs expedited):

• Name, description, price, expected review days
• Active / inactive status
• Used when the patient picks a review type at case creation

Disease categories

Admins define medical specialties / conditions patients can select:

• English and Arabic labels
• Active / inactive status
• Doctor mapping: which specialist doctors are eligible for each category

Case coordinators

Admins configure which doctors can act as case coordinators per specialty:

• One active coordinator mapping per specialty
• List of eligible coordinator doctor IDs
• Used when admin assigns a coordinator to a submitted case

Typical setup order

1. Create review types with pricing and SLA days
2. Create disease categories and map specialist doctors to each
3. Configure case coordinators per specialty
4. Cases can now be submitted and assigned through the normal end-to-end flow

---

Technical reference: configuration endpoints are listed under API Flows → Admin and detailed in API Reference.