About & experience

I understand operations from the inside — then redesign what gets in the way.

My work sits between operations, analysis and digital product design. I began in pharmacy and healthcare operations, where the problems were practical ones: stock, purchasing, workflows, service delivery, compliance and what management could actually see. Solving them increasingly meant analysing the process and the data underneath — and, where the available tools were not enough, designing and building better ones.

Healthcare operations · Business analysis · Digital solutions

Portrait of Rasha Elbashir

Where the work starts

Problem before tool

Most operational problems are handed over already framed as a technology request — a dashboard, a system, an automation. The useful question is usually the one underneath it: what is the operation actually trying to do, and where does it break.

Years of running the operation rather than advising on it is what makes that question answerable. I know what a stock count feels like at the end of a shift, what happens to a workflow when one person is away, and why a report that is technically correct still gets ignored. That is not sentiment about frontline experience — it is the difference between designing for how work is described and designing for how it happens.

Five things have to hold together for an operational problem to end in something that works. I have done all five, which is why the recommendation and the build are not separated here.

Domain knowledge

Healthcare and pharmacy operations understood from direct practice — not from a requirements document written by someone who has never dispensed anything.

Analysis

Working through operational and commercial information until what is actually happening is visible, rather than what is assumed to be happening.

Process design

Mapping the workflow as it runs: the roles, the decisions, the evidence, the approvals, and the exceptions that the official version leaves out.

Digital solution design

Turning those findings into a practical system — a workflow, a tool, an analysis or a product — shaped around the operation rather than around the software.

Implementation

Building it, running real scenarios through it and correcting what implementation exposes. A recommendation nobody implements has not solved anything.

How the work changed

Practice → analysis → building

The move from practice to analysis to building was not a change of career. Each stage was an answer to a problem the previous stage kept running into.

From 2008 Sudan

Practice

Hospital and community pharmacy. The problems here are immediate and physical: what is on the shelf, what has expired, what a patient needs that is not there. Nothing about them is abstract, which is a useful place to start from.

2012 – 2016 Sudan

Running the operation

Pharmacy management: responsibility widened from dispensing to the service itself — staff, medicines, purchasing, coordination. This is the point at which operational problems stop being someone else’s to solve.

From 2017 Oman

The same problems, a different system

Pharmacy practice, then associate leadership, inside a different healthcare system with different rules and expectations. Seeing familiar operational problems recur under unfamiliar conditions is what first suggested they were patterns rather than local faults.

2021 – Apr 2026 Oman

Leading a hospital pharmacy

Outpatient pharmacy leadership: service delivery, inventory and purchasing, governance and compliance, staff and workflow coordination, and the management reporting all of it had to feed. The deepest operational exposure of the sequence — and the period that raised most of the questions this portfolio answers.

May 2026 – Present Oman

Analysis, governance and building

Business development, governance and analysis in healthcare distribution and operations — and, alongside it, designing and building the systems the earlier stages kept asking for. The operational understanding did not become less relevant when the work became analytical. It became the reason the analysis is worth anything.

Experience

Category and country

The record behind the progression. Organisations are described by category and country rather than named.

May 2026 – Present

Business Development & Governance

Healthcare Distribution & Operations · Oman

  • Business development and governance work across healthcare distribution and operations.
  • Operational and commercial analysis supporting management decisions, alongside the design and development of digital solutions for the workflows involved.

2021 – Apr 2026

Head of Pharmacy

Hospital Pharmacy · Oman

  • Leadership of an outpatient pharmacy service: service delivery, staffing and workflow coordination.
  • Inventory and purchasing responsibility, governance and compliance obligations, and the operational reporting management decisions depended on.

2019 – 2020

Associate Head

Pharmacy operations · Oman

  • Shared responsibility for day-to-day pharmacy operations and service continuity.
  • Coordination across the operational, inventory and compliance sides of the service.

2017 – 2019

Pharmacist

Pharmacy practice · Oman

  • Pharmacy practice within a different healthcare system, its own regulatory framework and its own operational conventions.

2012 – 2016

Pharmacy Manager

Pharmacy & healthcare operations · Sudan

  • Management responsibility for a pharmacy service: staff, medicines and day-to-day operational coordination.
  • Inventory and purchasing decisions, and the operational judgement they required.

From 2008

Hospital & Community Pharmacist

Hospital and community pharmacy · Sudan

  • Frontline pharmacy practice across hospital and community settings.

Where I work best

By problem, not by tool

Not a list of everything I have touched — the categories of problem where the combination of operational knowledge, analysis and building is worth more than any one of them alone.

Operational intelligence

Fragmented operational and commercial information turned into something a manager can act on: what to stop buying, what is trapped, what needs attention now.

Workflow & process design

Work that crosses functions and loses its status in the middle. Mapping the responsibilities, evidence, approvals and execution path so a case cannot quietly stall.

Healthcare business analysis

Operational, commercial and governance information that is usually held apart, connected far enough to show what one side is doing to the other.

Digital product & system design

Real workflows translated into practical tools and platforms — designed around how an operation runs rather than fitting the operation to the software.

Implementation & validation

Building it, testing it against real operating scenarios and refining it until the result holds up in daily use rather than in a demonstration.

Tools, grouped by what they are for. They are instruments, not the argument.

Analysis & decision support

Excel · Power BI · Python

Workflow & automation

Google Workspace · Apps Script

Digital products

Web applications · APIs · databases

The projects in this portfolio show that progression in practice.

View selected work →

Education & development

Education

Bachelor of Pharmacy

University of Khartoum · 2005

Continuing development

Areas I have been studying alongside the work. Listed as study rather than as qualifications — where a certification is not verified, this page does not imply one.

  • Healthcare quality
  • Data analytics & Power BI
  • Health informatics
  • Python for analysis

Contact

Have an operational problem worth solving?

Describe the problem — the friction, the missing visibility, the process that keeps breaking. If I can help, I'll tell you how I'd approach it. If I can't, I'll say so.