Midwife intake privacy
Where are prenatal history and birth-plan answers stored?
Midwife, doula, and birth-center sites can use booking or clinic plugins for appointments, patient records, and intake forms. Those records can include prenatal history, due dates, birth-plan answers, and emergency contacts you configure. This sample reviews three plugins' documentation. Check which fields you collect, who can open records, where vendor hosts store submissions, and how long booking or patient rows and backups are kept.
Documentation review only. This is not legal advice, clinical 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, patient records, staff permissions, vendor accounts, or backups.
Where prenatal intake answers are stored
Answers stored on your WordPress site
Check which booking or patient 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.
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.
Midwife and birth-center 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 midwifery 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 |
|---|---|---|---|---|---|---|
| BookingPress – Appointment Booking Calendar Documented WordPress appointment booking plugin (version 1.1.28) that names health & wellness and medical & clinic businesses among supported verticals. Custom booking fields with conditional show/hide can collect extra answers with a booking. Prenatal-history, due-date, birth-plan, or emergency-contact questions depend on the fields you configure; they are not fixed midwifery defaults. Appointments are managed on the WordPress site. GDPR-oriented consent instruments are described; retention of booking or intake rows is not specified as a default purge in this source. Optional payment gateways move payment data when enabled. Public booking-form browser hosts are unverified. | Clinic bookings and configured intake fields stored in WordPress | Browser hosts not verified | Not assessed | Not tested |
| |
| KiviCare – Clinic & Patient Management System (EHR) Documented self-hosted clinic EHR (plugin version 4.5.6) with patient records management, encounter (visit) tracking, custom fields, and a patient portal that can expose medical history. Role-based access includes clinic admin, doctor, receptionist, and patient. Which prenatal-history, due-date, birth-plan, or emergency-contact fields you collect depends on the services and custom fields you configure — they are not established as fixed midwifery defaults by the listing. Optional Pro connectors (Google Calendar, SMS/WhatsApp, telemed addons, WooCommerce payments) can send appointment or notification data off-site when enabled; those paths were not assessed as free-version defaults. Retention of patient or encounter rows is not assessed here. Browser hosts for the public booking widgets were not verified for this snapshot. | Patient records, encounters, and medical history stored 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 prenatal-history, due-date, birth-plan, emergency-contact, or consent questions appear depends on the form you build or convert — they are not established as fixed midwifery 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. | Prenatal 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. Prenatal-history, due-date, birth-plan, or emergency-contact 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 or give clinical advice. Review stored records, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress fertility plugin privacy
- WordPress therapy plugin privacy
- WordPress hospice plugin privacy
- All privacy guides
/wp-midwife-plugin-privacy