Hospital & Clinic Operating System
Run Your Clinic.
Control the Whole Operation.
One operating system for the people, patients and workflows behind your healthcare facility.
ClinicMasterBD brings branches, departments, staff access, OPD, admissions, beds, operation theatre workflows and connected healthcare services into one hospital and clinic operating system designed for Bangladesh.
Green Valley Medical Centre
Branch: Dhanmondi
OPD Queue
Active
Live outpatient flow
Beds
18 / 24
Occupied
Admissions
4 Today
Inpatient entries
OT
2 Scheduled
Theatre workflow
Departments
- A-104Medicine · Dr. R. HaqueIN CONSULTATION
- A-105Cardiology · Dr. S. AlamWAITING
- B-012Orthopaedics · Dr. M. KarimCALLED
Organization
One institution, one flow
Branches
Multiple facility locations
Departments
Structured clinical work
Staff Access
Personal accounts, not shared
OPD & IPD
Outpatient to admission
Beds & OT
Facility resources in view
The problem
A Healthcare Facility Becomes Difficult to Control When Every Department Works Separately.
This is not a staff problem. Facility teams work hard inside systems that were never connected to each other — so information has to be re-collected, re-asked and remembered instead of shared.
- Patient registration may happen in one place while doctor schedules live somewhere else.
- OPD queues are managed separately from the records they belong to.
- Admission records may still depend on paper registers.
- Bed availability becomes hard to know instantly.
- Staff access is difficult to control when logins are shared.
- Departments run disconnected processes that never meet.
- OT schedules may be maintained manually in a notebook.
- Billing and chargeable services become fragmented across counters.
- Management lacks one operational view of the institution.
The solution
One Institution. One Operational Flow.
ClinicMasterBD treats a facility as a single operational chain instead of a collection of unrelated tools. Each stage hands context to the next.
- 01Organization
Represent the healthcare organization itself.
- 02Branches
Operate multiple facility locations where applicable.
- 03Departments
Structure clinical and administrative work.
- 04Staff
Give individuals authorized access according to their responsibilities.
- 05Patient entry
Register or identify the patient within the institutional workflow.
- 06OPD / IPD
Manage outpatient consultation flow and admission workflows.
- 07Bed / OT / Services
Coordinate institutional resources.
- 08Discharge / continuing care
Connect relevant information to the broader patient journey where supported.
Context travels forward
Registration, department, doctor, queue position, admission and chargeable services stay attached to the same institutional journey.
Every stage is configurable
Departments, facility resources and staff responsibilities are set up to match how your clinic or hospital actually runs.
Operational, not clinical replacement
ClinicMasterBD organizes facility operations. Clinical judgement always remains with your doctors and clinical teams.
One view for management
Owners and managers can see the institution rather than reconstructing it from separate registers.
Organization & multi-branch
One Organization Can Operate More Than One Facility.
A healthcare organization can be represented as an organizational structure with branches under it. Each branch can carry its own departments, staff, clinical activity and operational resources.
Organization structure
ClinicMaster Health Group
Organization
Dhanmondi Branch
5 departments · OPD + IPD
Uttara Branch
3 departments · OPD
Mirpur Branch
4 departments · OPD + OT
Each branch carries its own operations
Departments, authorized staff, clinical activity and operational resources can be defined per branch so locations do not have to share one undifferentiated setup.
Architectural capability, not an entitlement claim
Multi-branch operation describes what the system is designed to support. Commercial entitlement — including how many branches a subscription includes — will be finalized and published later.
A single clinic is a first-class case
One organization with one facility is fully supported. Branch structure only becomes relevant when a facility grows into more locations.
Departments
Structure Work Around Real Departments.
Departments give the institution a structured way to organize doctors, staff, workflows and patient services. Department configuration is intended to reflect your facility rather than a fixed template.
Department map
- MedicineOPD-heavy consultation flow
- CardiologySpecialist consultation
- OrthopaedicsConsultation + OT workflow
- GynaecologyOPD + admission workflow
- PaediatricsOutpatient consultation
Configurable, not fixed
Departments should appear and behave the way your facility defines them — a diagnostic clinic, a specialty center and a medium hospital do not need the same structure.
Departments anchor the workflow
Doctors, schedules, OPD queues, admissions and services all attach to a department, which is what makes institutional reporting meaningful.
Staff & access control
Every Staff Member Gets the Access They Need.
ClinicMasterBD is designed around personal staff accounts rather than shared passwords. Access is permission-based institutional access: a person holds a membership in the organization, and that membership carries the responsibilities they are authorized to perform.
Access model
- 01Person
An identified individual with their own account.
- 02Membership
That person belongs to your organization.
- 03Role / permission
The membership carries authorized responsibilities.
- 04Authorized work
Only the work allowed for that responsibility.
One institution does not mean one shared password.
Access should follow responsibility
Staff see and perform the work allowed for their responsibilities.
- Owner / AdministratorInstitutional administration
- ManagerOperational oversight
- DoctorClinical workflow
- Reception / Front deskPatient and appointment workflow
- Authorized staffAssigned facility work
Responsibilities are presented as permission-based institutional access. The specific permissions available to a facility depend on configuration, and internal authorization architecture is not published.
OPD
Make Outpatient Flow Visible.
OPD is one of the busiest parts of a clinic or hospital. ClinicMasterBD is designed to connect patient entry, department and doctor context, and the institutional outpatient workflow, so the front desk and the consultation room are looking at the same flow.
- 01Patient arrives
Front desk receives the patient.
- 02Registration
Register or identify the patient record.
- 03Department / doctor
Route to the right clinical context.
- 04Queue
Position becomes visible to staff.
- 05Consultation
Doctor works with patient context in place.
- 06Next service / exit
Diagnostics, pharmacy, admission or discharge.
OPD operations — Medicine
Waiting
illustrative
In consultation
illustrative
Completed
illustrative
- M-021Dr. R. Haque · MedicineIN CONSULTATION
- M-022Dr. R. Haque · MedicineCALLED
- M-023Dr. N. Chowdhury · MedicineWAITING
- M-020Dr. N. Chowdhury · MedicineCOMPLETED
Counts shown here are illustrative and are not published as company statistics.
Patient queue
Know Who Is Waiting — And Where.
Queue visibility helps reception, doctors and patients understand where the consultation flow currently stands. ClinicMasterBD shows queue status rather than predicting exact waiting times.
Queue board
| Token | Patient | Doctor / Department | Status |
|---|---|---|---|
| C-108 | Patient A | Dr. S. Alam · Cardiology | WAITING |
| C-107 | Patient B | Dr. S. Alam · Cardiology | CALLED |
| O-045 | Patient C | Dr. M. Karim · Orthopaedics | IN CONSULTATION |
| P-013 | Patient D | Dr. F. Rahman · Paediatrics | COMPLETED |
Statuses shown: WAITING · CALLED · IN CONSULTATION · COMPLETED. Patient names are fictional placeholders; no real patient information is displayed.
IPD & admission
From Admission to Bed — Keep the Inpatient Journey Connected.
When a patient requires admission, ClinicMasterBD shifts the workflow from an outpatient interaction into an inpatient journey, so the ward, the bed and the services attached to that stay all belong to the same operational record.
- 01Patient
Existing or newly registered patient record.
- 02Admission
The inpatient workflow is opened.
- 03Ward / unit
Assign to a configured inpatient area.
- 04Bed
Occupy a specific facility resource.
- 05Care
Facility services recorded against the stay.
- 06Discharge
Close the stay and release the resource.
One continuing record
The admission connects to the same patient context that entered through OPD instead of starting a separate paper trail.
Resources stay accountable
Ward, unit and bed assignment are treated as operational resources with a current state.
Operational language
ClinicMasterBD coordinates admission workflow and facility resources. Clinical care decisions remain entirely with your clinical team.
Discharge is part of the flow
Closing a stay releases the resource and leaves the institutional record intact for continuing care where supported.
Bed management
Know Which Beds Are Available.
Bed availability should be visible as an operational resource rather than managed from memory or a register at one desk. ClinicMasterBD keeps ward, cabin and bed status visible from the records your staff maintain.
Ward A — bed grid
Bed A01
AVAILABLEBed A02
OCCUPIEDBed A03
OCCUPIEDBed A04
AVAILABLEBed A05
OCCUPIEDBed A06
CLEANINGBed A07
RESERVEDBed A08
AVAILABLE
Cabin / ward concept
Different Inpatient Spaces. One Operational View.
- CabinsPrivate configured rooms
- General WardShared inpatient area
- Special UnitHigher-dependency area
These are configured facility resources. Not every hospital or clinic has the same inpatient structure, so groupings are defined by the facility rather than assumed.
Operation theatre
Coordinate OT Work Without a Separate Notebook.
This is an operational scheduling and status workflow: what is planned, who is involved, when it happens and where it currently stands. ClinicMasterBD does not provide clinical, surgical, anaesthesia or medical safety guidance.
OT schedule — Theatre 1
- 09:00Patient EDr. M. Karim · OrthopaedicsCOMPLETED
- 11:30Patient FDr. T. Islam · SurgeryIN OT
- 14:00Patient GDr. A. Sultana · GynaecologySCHEDULED
- 16:30Patient HDr. T. Islam · SurgerySCHEDULED
- 01Request / plan
The theatre requirement is raised.
- 02Schedule
Time, theatre and team are coordinated.
- 03Preparation
Operational readiness is tracked.
- 04OT
Status reflects work in progress.
- 05Completion
Outcome status closes the schedule entry.
Doctors within the facility
Doctors Should Fit Into the Facility Workflow — Not Work Around It.
A doctor working inside your facility should find their department, their schedule and their patient context already in place. ClinicMasterBD coordinates institutional doctor activity, while SebaOne may provide broader connected doctor and patient workflows where integrated.
- 01Doctor
An authorized personal staff account.
- 02Department
Clinical context inside the facility.
- 03Schedule
When the doctor is available at this branch.
- 04OPD patient
Queue hands over the right patient.
- 05Consultation
Work happens with context already attached.
- 06Prescription / test
Next services flow from the consultation.
- 07Follow-up
The journey continues rather than restarting.
Chamber reality respected
Doctors often consult inside a facility on specific days and hours. Schedules are designed around that rather than assuming full-time employment.
Institutional coordination
The facility keeps its own operational record of doctor activity within its departments.
No shared database
Where SebaOne integration is enabled, systems connect through approved workflows. They remain separate systems with separate data.
Clinical authority unchanged
Prescribing and clinical decisions remain the doctor's. ClinicMasterBD carries the operational context around them.
Shift & staff operations
Healthcare Runs in Shifts.
ClinicMasterBD is designed to support structured shift-based staff operations as the facility workflow expands. This section describes product direction for shift structure, not biometric attendance or payroll.
Morning
07:00 – 15:00
- Reception · 2 assigned
- Medicine · duty staff
- Ward A · assigned staff
Afternoon
15:00 – 23:00
- Reception · 1 assigned
- Cardiology · duty staff
- OT support · assigned staff
Night
23:00 – 07:00
- Front desk · 1 assigned
- Ward A · duty staff
- Emergency support · assigned
Assignments show department, responsibility and shift window — not attendance records.
Diagnostic services
Diagnostics Can Be Part of the Facility Journey.
Facilities can operate their own diagnostic services or connect to PathologyMaster through supported workflows where configured.
- 01Doctor / OPD
A test is required during the facility interaction.
- 02Test request
The request is recorded against the patient journey.
- 03Diagnostic service
In-house service, or a connected laboratory where configured.
- 04Result
The result returns through the supported workflow.
- 05Patient / doctor
Result reaches the clinical context that asked for it.
System-to-system connection
ClinicMasterBD
Hospital & Clinic OS
Facility operations and laboratory operations remain independent systems, connected through approved workflows where configured. There is no shared database.
Billing & financial workflow
Billing That Follows the Facility Workflow
ClinicMasterBD is designed to connect chargeable facility services, billing records, discounts and payment workflows as the commercial layer is enabled.
Bill structure
- ConsultationMedicine · OPDillustrative
- Bed / CabinWard A · 2 daysillustrative
- ServiceFacility serviceillustrative
- DiagnosticWhere connectedillustrative
- DiscountPer configured permissionillustrative
Services stay attached to the record
Consultation, bed or cabin occupancy, facility services and connected diagnostics belong to the same institutional journey the patient actually travelled.
Controlled discount workflows
Authorized users may need to apply discounts. This is designed to happen according to configured permissions and facility policy — not as unrestricted staff authority.
Progressive payment enablement
Payment capabilities can be connected as supported commercial services are enabled for the facility.
Pharmacy integration
Connect Prescription and Pharmacy Workflows Where Appropriate.
Hospital-attached or connected pharmacy workflows can integrate with PharmacoBD where supported. Availability and fulfilment are not guaranteed and depend on configured services.
- 01Doctor
Consultation within the facility.
- 02Prescription
Recorded in the clinical workflow.
- 03Pharmacy service
In-house or connected pharmacy.
- 04PharmacoBD
Where the integration is enabled.
PharmacoBD
Pharmacy OS
Pharmacy operations remain an independent system. Prescription-to-pharmacy movement happens only through approved integration workflows that the facility has configured.
pharmacobd.comManagement dashboard
See the Institution, Not Just One Counter.
An executive operational view puts outpatient activity, admissions, facility resources, theatre schedule and staffing in one place, so management is reading the institution rather than assembling it.
Executive operational view — Dhanmondi Branch
OPD Activity
Active
Outpatient flow in progress
Current Admissions
illustrative
Open inpatient stays
Bed Occupancy
18 / 24
Ward + cabin resources
Scheduled OT
2
Theatre entries today
Active Departments
5
Configured departments
Staff on Duty
illustrative
Current shift assignment
Services Requiring Attention
illustrative
Operational follow-up
Owner / admin control
Give Owners Control Without Managing Every Task Personally.
An owner or administrator should be able to shape the institution — how it is structured, who is authorized and what is visible — without becoming the person who processes every counter transaction.
Owner / administrator scope
- Organization settings
- Branches
- Departments
- Authorized staff
- Institutional access
- Facility configuration
- Operational visibility
ClinicMasterBD does not make clinical decisions for owners or clinical teams. It organizes the operational structure they define.
Manager workflow
Delegate Operations Without Giving Away the Whole System.
Managers can be assigned appropriate operational responsibility according to configured permissions, using their own personal account and authorized organization membership.
Delegation
Personal account · authorized membership · configured permissions
Shared admin password
Untraceable, unscoped, impossible to withdraw cleanly
Delegation is not the same as sharing the owner's login.
Why ClinicMasterBD is different
More Than Hospital Billing Software.
A hospital is not one workflow. It is many workflows that need to understand each other.
Disconnected institution
- Patient registerSeparate
- Appointment systemSeparate
- Queue on paperSeparate
- Staff listSeparate
- Bed registerSeparate
- OT notebookSeparate
- Billing counterSeparate
- DiagnosticsSeparate
ClinicMasterBD
- 01Organization
- 02Branch
- 03Department
- 04Staff
- 05Patient
- 06OPD / IPD
- 07Bed / OT / Services
- 08Institutional record
Extraordinary capabilities
Built Around How a Healthcare Facility Actually Operates
01
Multi-branch organization
Operate multiple healthcare facilities within one organizational structure where enabled.
02
Department structure
Organize clinical and operational work by department, configured to your facility.
03
Personal staff identities
Avoid shared institutional passwords by giving staff their own authorized accounts.
04
Permission-based operations
Match access to staff responsibility rather than opening the whole system to everyone.
05
Connected OPD flow
Patient entry, queue and consultation exist within one institutional journey.
06
IPD + bed context
Connect admission to facility resources such as wards, cabins and beds.
07
OT workflow
Coordinate operation theatre scheduling and operational status.
08
Healthcare ecosystem connectivity
Connect appropriate laboratory, pharmacy and patient/doctor workflows through approved integrations.
Patient continuity
The Facility Is One Part of the Patient's Healthcare Journey.
Where approved integration exists, relevant facility interactions can connect to the broader patient healthcare journey. Not every institutional record automatically enters SebaOne — this happens only where connected, where authorized, and through supported workflows.
ClinicMasterBD
Facility interaction
Registration, OPD consultation, admission, facility resources and chargeable services inside your clinic or hospital.
SebaOne
Doctor + patient healthcare journey
The longitudinal healthcare journey that continues beyond a single facility visit, where the patient and doctor are connected.
sebaone.orgStandalone operation
ClinicMasterBD Works as Its Own Facility System.
A clinic or hospital can use ClinicMasterBD independently for its facility operations. SebaOne, PathologyMaster and PharmacoBD are optional integrations — ecosystem participation is never required.
Run independently
Organization, branches, departments, staff access, OPD, admissions, beds and OT workflows all work without any other product connected.
Connect when it helps
Enable laboratory, pharmacy or patient-journey connections only if your facility wants them.
Withdraw without breaking
Because systems stay independent with no shared database, your facility operations remain intact whether or not an integration is enabled.
Ecosystem
Independent Healthcare Systems. Connected When Care Requires It.
Each product is independently deployable and operable. There is no shared database, and information moves only through approved integration workflows.
Bangladesh-first
Designed Around Healthcare Facilities in Bangladesh
ClinicMasterBD is built for the practical realities of how facilities here actually run, rather than adapted from a template built for another market.
- Private clinics operating with lean teams
- Doctor chambers running inside the facility
- OPD-heavy daily operations
- Receptionist and front-desk driven registration
- Wards and cabins as distinct inpatient spaces
- BDT-oriented commercial workflows
- Shift-based facility operation
- In-house or connected diagnostic and pharmacy services
- Branch-based healthcare organizations
Security & tenant isolation
Institutional Access Needs Clear Boundaries.
Access in ClinicMasterBD is designed around personal staff accounts, organization boundaries and permissions that follow responsibility.
- Personal staff accounts rather than shared institutional logins
- Organization membership as the basis of access
- Role and permission-based access to facility work
- Branch and resource boundaries where configured
- Protected patient context inside the facility
- Auditable actions where supported
- Secure, approved integrations only
Plans
Plans for Clinics and Hospitals
Commercial plans will be published once finalized.
What we can say today
- ClinicMasterBD is designed for clinics, hospitals, diagnostic clinics and specialty centers.
- Multi-branch operation is an architectural capability; entitlement will be defined commercially.
- Billing and payment workflows are enabled progressively as the commercial layer is completed.
- Ecosystem integrations are optional and depend on configuration.
FAQ
Questions Clinic and Hospital Owners Ask
Bring Your Entire Facility Into One Operational View.
Branches, departments, staff, OPD, admissions, beds and institutional workflows — organized through one healthcare facility operating system.