Hospice intake privacy
Where are hospice intake answers stored?
Hospice and palliative-care intake forms can collect patient-condition notes, family contacts, visit schedules, and bereavement follow-ups. This sample reviews three plugins' documentation. Check which questions you collect, who can open submissions, where vendor hosts store answers, and how long records and backups are kept.
Documentation review only. This is not legal advice, or a HIPAA, GDPR, or other compliance assessment.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, visit records, staff permissions, vendor accounts, or backups.
Where intake answers are stored
Intake answers stored on your WordPress site
Check which intake or booking fields you enable, who can open entries, and how long records and backups are kept. Notification emails can also copy the same answers off-site.
Intake answers stored by a vendor
Some tools send intake submissions into a vendor cloud vault. Review access and retention there. A browser scan cannot inspect those stored submissions.
Hospice intake setups
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
Three plugins reviewed from public documentation. Specialty hospice EMR SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress Documented WordPress appointment booking plugin (version 5.7.4) marketed for clinics and healthcare practices among other service businesses. The listing describes collecting patient information with custom fields, managing appointments and customer information from the agent dashboard, and a customer dashboard for bookings. Bookings and customer records are managed inside WordPress on the free plan. Which condition, family-contact, or care-coordination questions appear depends on the custom fields you configure — they are not established as fixed hospice defaults by the listing. Optional payment processors (Stripe, PayPal, Razorpay) and Pro connectors (Google Calendar, SMS/WhatsApp) can send booking or notification data off-site when enabled; those paths were not assessed as required free-version behavior. Retention of appointment or customer rows is not assessed here. Browser hosts for the public booking form were not verified for this snapshot. | Visit bookings and configured patient fields stored in WordPress | Browser hosts not verified | Not assessed | Not tested |
| |
| Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder Documented self-hosted form builder (plugin version 6.2.15) with submitted entries managed in WordPress, CSV/Excel/ODS/JSON export, optional auto-delete of entries, and a GDPR agreement field. Which patient-condition, family-contact, visit, or bereavement questions appear depends on the fields you configure — the listing does not establish fixed hospice intake defaults. Optional AI Form Builder sends only form-description prompts (plus site URL/title) to ai.fluentforms.com and states visitor submissions are never sent on that path. Review who can open Entries, whether exports or notification emails leave the site, uninstall retention, and backups. Browser hosts for public forms were not verified for this snapshot. | Configured hospice intake answers stored as form entries on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| HIPAAtizer Documented WordPress embed for the HIPAAtizer SaaS (plugin version 1.3.10). The listing states Protected Health Information collected through embedded forms is stored in vendor cloud vaults, not as ordinary WordPress form-entry tables; forms are added via Gutenberg block, shortcode, or embed after connecting a HIPAAtizer account. Which patient-condition, family-contact, visit, or bereavement questions appear depends on the form you build or convert — they are not established as fixed hospice intake defaults by the listing. This row describes the documented storage path only and does not assess legal or regulatory compliance status. Review vendor account access, retention, and any BAA or plan terms separately. Browser hosts for the embed were not verified for this snapshot. | Hospice intake form submissions stored in a vendor cloud vault | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Patient-condition questions often depend on the fields you configure. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess legal compliance status. Review stored records, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 10, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-hospice-plugin-privacy