Learn how to use active ERPat modules through role-based instructions, standard operating procedures, field legends, standards, compliance reminders, and step-by-step workflows. Every guide is synchronized from the owning module and versioned whenever its instructions change.
Showing 7 of 395 synchronized guides.
Administer the ERPat Pharmacy module: the full permission families and who should hold them, branch-profile operating rules, the two advanced sub-toggles, the pharmacist-on-duty gate, data-privacy controls, the audit trail, cron jobs, dashboard widgets, the dual read-only API, migrations and the demo seeder.
Counter SOPs for the ERPat Pharmacy module: start a pharmacist duty session, capture and validate a prescription, dispense with FEFO stock issue and the correct Senior/PWD statutory discount, print the BIR receipt, and run the controlled-register and cold-chain routines.
Answers to common ERPat Pharmacy questions and fixes: a hidden menu, greyed-out buttons, a pharmacist who won't go on duty, why a prescription won't validate, why patient IDs are masked, why Controlled Drugs is hidden, and the configured-vs-certified distinction, plus a glossary and support notes.
Set up the ERPat Pharmacy module from scratch: run the migration, enable the module and its two advanced sub-toggles, grant the right permissions, add a branch profile, record your FDA LTO and pharmacist credentials, then follow a beginner path through catalog, prescriptions and dispensing.
Overview of the ERPat Pharmacy module: a Philippine retail-drugstore compliance and dispensing layer covering FDA/PRC compliance, drug catalog, prescriptions, FEFO dispensing with Senior/PWD statutory discounts, the controlled register, and quality & safety.
Data and screen reference for the ERPat Pharmacy module: the menu items and routes, every permission key, the controllers behind each screen, the main database tables, the cron jobs and dashboard widgets, and the integration and end-user API endpoints.
The live-file evidence behind the ERPat Pharmacy user guide: exactly which manifest, changelog, config, controller, helper and job files were read so every statement in this documentation traces to the shipped module source.