OtBooking — data reference
All 18 fields BSuit stores for OtBooking (Healthcare Management), with the record types they refer to.
On this page
#About OtBooking
OtBooking is a record type in the Healthcare Management area of BSuit. This page lists everything BSuit stores for each otbooking — 18 fields. No dedicated page for it was found in the menu; records may be created by other screens, imports or automatic processes.
#Fields
Every field stored for a otbooking. “Stored as” is the technical field name, useful when talking to support or building reports. 5 fields are references to other record types.
| Field | Stored as | Type | Required | Max length | Refers to |
|---|---|---|---|---|---|
| Patient Id | PatientId | Text | No | — | Patient |
| Admission Id | AdmissionId | Text | No | — | Admission |
| Surgeon Id | SurgeonId | Text | No | — | — |
| Ot Room Id | OtRoomId | Text | No | — | OtRoom |
| Ot Procedure Id | OtProcedureId | Text | No | — | OtProcedure |
| Anesthesiologist Id | AnesthesiologistId | Text | No | — | — |
| Scheduled At | ScheduledAt | Date and time | No | — | — |
| Estimated Duration Minutes | EstimatedDurationMinutes | Whole number | No | — | — |
| Status | Status | Text | No | — | — |
| Pre Op Notes | PreOpNotes | Text | No | — | — |
| Anesthesia Type | AnesthesiaType | Text | No | — | — |
| Started At | StartedAt | Date and time | No | — | — |
| Completed At | CompletedAt | Date and time | No | — | — |
| Company Id | CompanyId | Text | No | — | Company |
| Id | Id | Text | No | — | — |
| Created At | CreatedAt | Date and time | No | — | — |
| Updated At | UpdatedAt | Date and time | No | — | — |
| Is Deleted | IsDeleted | Yes / No | No | — | — |
#Where OtBooking is referenced
Other record types point to this one, so changing or removing a record here can affect them:
| Record type | Field |
|---|---|
| PostOpNote | Ot Booking Id |
| PreAuthorization | Ot Booking Id |
#About this guide
Generated from BSuit’s data model on the date shown under “Seen on a running system”. Field names, types and lengths come from the model itself. References are inferred from field names (a field called “Ledger Id” is treated as pointing to Ledger); the model does not declare relationships, so an inferred link can occasionally be wrong or missing.
About this guide
- Status
- Partially reviewed
- Application
- BSuit ERP
- Audience
- Administrators, analysts and support staff
- Owner
- BSuit documentation team
- Reviewer
- Not yet reviewed
- Last verified
- Never
- Checked against
- Generated from source revision a36c7a086 on 2026-10-02
- Seen on a running system
- Not yet
- Help version
- 2026.0.0-preview
- Guide ID
erp:data/hms.otbooking