

Step 1: fiscal code entry
Farmaci IGEA adds a private area to your WordPress site where registered patients of a facility using the IGEA CRM by S0ft.it can request the repetition of drugs they were already prescribed.
Patients identify themselves with their Italian fiscal code (validated with check digit and “omocodia” support) and confirm their identity with a one-time password sent via SMS. They then see their prescription history (deduplicated by AIC code, configurable depth), choose a quantity for each drug, add optional notes for the doctor and submit the request.
Every request goes into review: it is stored on the CRM with status “in_revisione” and must be approved or rejected by the doctor from the CRM backend. The plugin never generates prescriptions by itself. The patient’s phone number on file (the one verified via OTP) is stored with each request for audit purposes.
SEND_FARM with fallback body) and/or SMS, configurable on the CRMThe API key never leaves the server: the patient’s browser only talks to WordPress, which forwards requests to the CRM. Nonce on every call, field whitelisting, session tokens issued only after OTP verification, every requested drug re-validated server-side against the patient’s own prescription history, rate limiting per IP and per patient.
This plugin is a connector: it requires an installation of the IGEA CRM by S0ft.it, reachable over HTTPS, with the farmaci_api.php endpoint, the SQL script (farmaci.sql) executed, and an SMS provider configured for the OTP codes. Without the CRM the plugin has no standalone functionality. More about the CRM: www.s0ft.it.
This plugin sends data to the IGEA CRM server configured by the site administrator (URL and API key in the plugin settings). The data transmitted is what the patient enters in the form (fiscal code, verification codes, selected drugs and quantities, notes) plus the visitor’s IP address, used exclusively for anti-abuse rate limiting and access logging. No data is ever sent to S0ft.it or to any third party by this plugin: the destination server is chosen and operated by the site owner.