Skip to main content

Shefa documentation

Shefa is a self-hosted platform for pharmacies, drug warehouses and patients in Syria. This site collects the project's design documents and the knowledge base the team uses to decide what Shefa should do.

What is here​

Shefa​

  • Technical document: roles and business logic, then architecture and technology. This is the design Shefa is built from.
  • Reference materials: what the collected reference files contain (the Syrian drug bank, price bulletins, leaflet templates, the German pharmacy-software manuals) and which ideas in them are not yet in the technical document.

IXOS knowledge base​

A functional description of a mature German pharmacy system, IXOS by Pharmatechnik, written from its public online help (2,485 pages, read in full). It is a clean-room specification: every chapter describes in our own words what a feature does, the data it needs, its rules and its outputs. It copies no text, screenshots or code.

The 32 chapters are grouped by business area:

AreaChapters
Platform and glossaryDesktop, users and workstations, printing, system care, a German-English term glossary
Point of sale and prescriptionsSelling at the till, prescription and e-prescription sales, payment and till closing, pricing and pickups, prescription management, delivery service and patient apps
Invoicing and receivablesCustomer orders and delivery notes, invoices, dunning, open items, cost estimates
Compounding and blisteringExtemporaneous preparations, bulk compounding, substitution therapy, patient blister packs
Drug information and clinical checksDrug database structure, interaction and patient-risk checks, medication management
Customers and other contactsCustomer records, suppliers, staff and roles, care homes, doctors, branches
Items, search and stockItem master, search and alternatives, stocktaking, robots, assortment control
PurchasingWant lists, carts, supplier orders, goods receipt, returns, purchasing rules and storage
Pricing, discounts and loyaltyPrice lists and calculation, discount models, coupons, loyalty programme
Office, analytics and complianceAnalytics and KPIs, report generator, statutory registers, document archive, accounting and audit exports
System administration and add-onsCompany data, print forms, security, notes and tasks, cash device, add-ons
Settings referenceEvery configuration parameter with its scope, effect and default

How to read a chapter​

Every chapter has the same 14 sections: purpose, key terms, data model, features, workflows, business rules, configuration, roles, integrations, printouts, dependencies, portability notes, open questions and source pages.

Each feature carries a tag:

  • [GENERIC]: useful in any country's pharmacy system.
  • [DE-SPECIFIC]: exists because of German law, insurance or infrastructure. These come with a line stating the general idea underneath, the part that could carry over to Syria.

Where the help was vague or contradicted itself, the chapter says so under Open questions instead of guessing.