Administrator & HOD Guide
Roles
LOSPOR has three user roles:
| Role | Capabilities |
|---|---|
| Member (default) | Record and view their own cases only |
| Head of Department (HOD) | View and edit all cases in their institution; transfer cases to any member of their institution |
| Admin | View and edit all cases across all institutions; approve role requests; manage users |
Requesting HOD role
- Go to Settings (⚙ icon) → Settings → scroll to Security & Access
- Click Request Head of Department role
- Your request is submitted to the LOSPOR administrator
The administrator will review and approve or reject the request.
HOD capabilities
Viewing and editing institutional cases
As an HOD, the dashboard shows all cases in your institution, not just your own. The case owner's name is shown on each row. You can open and edit any case in your institution.
Transferring cases
You can transfer any case in your institution to any member of the same institution, instantly and without requiring their acceptance:
- Find the case on your dashboard
- Click the Hand over / Assign button
- Select the target colleague
- Click Assign now
The transfer is immediate.
Admin panel
Administrators have access to the Admin page (visible in the navigation bar as a shield icon).
Pending role requests
All pending HOD role requests are listed here. For each request:
- Approve — grants the user the HOD role
- Reject — denies the request
User management
A table of all registered users is shown with their name, email, institution, and current role. Administrators can:
- Promote a Member to HOD
- Demote an HOD to Member
Admin roles cannot be changed through the UI.
OMOP CDM export
LOSPOR can export the de-identified / pseudonymised dataset in OMOP CDM v5.4 format for research use. The export is available to admins only.
- Open the Admin panel (shield icon in the navigation bar)
- Scroll to the Research export section
- Click Export JSON for a full OMOP bundle, or Export CSV for a flat multi-table CSV
The export contains: visit_occurrence, condition_occurrence, drug_exposure, measurement, procedure_occurrence, and observation. The export reads normalized rows and active CaseEvent rows, including diagnoses, comorbidities, labs, vitals, intraop glucose, gas settings, bolus drugs, infusions, agents, vascular access, selections, complications, recovery vitals, Aldrete subscores, and provenance/version metadata.
person_id is a deterministic hash of the internal case ID. Direct patient identifiers are not stored or exported. Operational user, institution, and timestamp linkage may exist internally for access control, audit, and governance; research exports are case-level and use month/year only, not exact surgery date.
Drug exposure is sourced from the intraoperative event log and normalized medication rows. Known OMOP concept IDs are exported where confidently mapped through ConceptMap; source-only values preserve ICD-10, LOINC, ATC, INN, or LOSPOR option codes/labels instead of using fake concept IDs.
First administrator
The first administrator account must be set directly in the database. In Supabase:
- Go to your project → Table Editor →
Usertable - Find the user you want to make an admin
- Set their
rolecolumn toADMIN
Subsequent admins can be promoted by existing admins via the Admin panel.