SYSTEM 01 / PRODUCTION SYSTEMS · CURRENT ROLE
A pharmacy network is an operating environment: members, payments, schedules, staffing and data all have to work together.
Conceptual architecture
Ollama interprets natural-language duty rules. Validated constraints feed the OR-Tools CP-SAT solver; interpretation and allocation are separate stages.
Member services · Payments · Scheduling
Staffing · Internal operations
OPERATIONAL CONTEXT
The Istanbul Chamber of Pharmacists operates production systems serving 6,000+ pharmacies and managing 35,000+ drug records. Within this environment, my work covers backend services, integrations, reporting and annual duty scheduling.
MY RESPONSIBILITY
I develop backend services, third-party integrations and reporting, and troubleshoot production issues. I also designed an annual duty scheduling engine using Node.js, Python/FastAPI, Ollama and OR-Tools CP-SAT to turn natural-language rules into validated constraints.
Human rules. Validated constraints. A scheduling model.
Conceptual scheduling flow, with human review as an operational consideration.
DECISIONS & RATIONALE
The scheduling engine converts natural-language duty rules with Ollama, validates the resulting constraints and passes them to OR-Tools CP-SAT. This separates interpretation from the constraint model used for annual allocation.
Payment and SMS integrations connect pharmacy services to external providers. The backend also handles external-data retrieval, caching, geospatial rules and transactional batches.
I troubleshoot Linux/Nginx issues affecting systems used by the pharmacy network, alongside developing the application backend.
Working with scheduling rules or connected operational services? Let’s talk about your system.