| 开发者 | apiganti |
|---|---|
| 更新时间 | 2026年7月15日 00:33 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
docs/{PATIENT_ID}/referti/ and registered with the PUSHReferto() helper, which updates the referti table and notifies the patient by email and/or SMS according to the plugin settings.
Main features
PubblicaReferto()), or after N daysreferti_api.php endpoint, the referti_push.php helper, the SQL script (referti.sql) executed, and — for OTP and SMS notifications — an SMS provider configured. Without the CRM the plugin has no standalone functionality. More about the CRM: www.s0ft.it.
External services
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 or password) plus the visitor's IP address, used exclusively for anti-abuse rate limiting and access logging. Downloaded reports travel from your CRM server to the patient's browser through your WordPress site. 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.
referti-igea folder to /wp-content/plugins/.referti_api.php and referti_push.php into the ajax/ folder (next to orari.php), edit the API key, token secret and WordPress origin at the top of referti_api.php, and run the referti.sql script on the CRM database.[referti_crm] shortcode to that page.PUSHReferto($patientId, $fileName, $meta) after exporting each report file to docs/{patientId}/referti/. In "approval" visibility mode, call PubblicaReferto($reportId) to publish and notify.SEND_REF email template in the CRM templates_email table to customize the notification (placeholders: [nome] [cognome] [nominativo] [cf] [email] [cellulare] [tiporeferto] [descrizione] [specialita] [datareferto] [datadisponibile] [password] [linkreferti]).No. It is a connector for the IGEA CRM by S0ft.it: report files, patient records, email and SMS sending all live on the CRM. The plugin provides the private area on the website and the secure connection.
On the CRM server, in docs/{PATIENT_ID}/referti/. They are streamed to the patient through WordPress only after identity verification and an ownership check; they are never copied to the WordPress server.
It is generated by PUSHReferto() the first time a report is published for that patient (when the access method includes the password) and delivered in the notification email. Only a hash is stored. If lost, the patient can use the SMS code (when enabled) or the secretary can regenerate it with the rigenera_password option of PUSHReferto().
No. The reports area is reserved for patients already in the CRM archive: registration happens at the facility (or through the Prenotazioni IGEA plugin).
Reports are health data: the plugin verifies the patient's identity before any access, never exposes clinical details in SMS, and logs every login and download with date and IP on the CRM. Overall compliance depends on the site owner's privacy policy and processes.
Create the SEND_REF template in the CRM templates_email table (same mechanism as Prenotazioni IGEA). If the template does not exist, a built-in fallback body is used which, for confidentiality, does not include the clinical description of the report.