Self-hosted patient surveys and health questionnaires

Running patient feedback and outcome questionnaires on your own servers keeps ePHI under your safeguards, but only if hosting, access, encryption, retention and vendor contracts are designed for it. This page covers what to decide and which open-source platforms fit.

On this page

Why self-hosted patient surveys need a HIPAA-first build

For most provider and health research teams collecting patient feedback or outcome questionnaires that contain ePHI, self-hosting LimeSurvey is the most direct fit, because the responses, the respondent identifiers and the exports can all stay on servers your organization or its contracted hosting provider controls. LimeSurvey Community Edition is free to download and self-host, and survey data stays on the server you run it on. The decision is less about the software and more about who can reach that server, how it is configured and what evidence you can produce later. The HIPAA Security Rule (45 CFR Part 164 Subpart C) applies to covered entities, meaning health plans, health care clearinghouses and covered health care providers, and to their business associates, for all ePHI they create, receive, maintain or transmit. Two points matter for survey planning. First, there is no HIPAA certification: HHS states that no Security Rule standard requires certifying compliance and does not recognize private certifications, so any vendor badge is not proof on its own. Second, if a SaaS survey vendor will handle ePHI on your behalf, it is a business associate and you need a business associate agreement that requires Security Rule compliance, flows the same terms to its subcontractors, and commits it to report security incidents. Confirm that agreement exists before any patient data enters a hosted form.

A HIPAA-first survey build differs from a general survey because of three design areas. Identifiers and answers should be separated or minimized, so the questions that carry clinical content are not stored alongside names or record numbers unless the workflow needs them. Access should follow the care team's need to know, with administrator, designer and reviewer roles scoped per survey and unique user identification for every account. Retention and deletion rules must be written down, enforced on the server and tested, including how exports and backups are handled. Each of these maps to standards in Appendix A to Subpart C, such as unique user identification and automatic logoff in the technical safeguards, which an implementation partner can translate into configuration and evidence. The platform comparison and deployment options are covered in the sections below.

Which HIPAA requirements shape a patient survey build

This table maps the HIPAA Security Rule requirements that shape a patient survey build to what each one asks for and what it means in practice. Read the middle column for the obligation and the last column for the build decision and the evidence to prepare. The main takeaway: addressable specifications still require a documented assessment and decision, so no addressable safeguard can be skipped silently.

RequirementWhat it asks forWhat it means for the build
Unique user identification (45 CFR 164.312(a)(2)(i))Required. Each user is identified and tracked by a unique name or number.Named accounts for every staff member, no shared logins, and role-based access per care team. Evidence: user register and role matrix.
Emergency access procedure (45 CFR 164.312(a)(2)(ii))Required. Documented steps to reach ePHI during an emergency.A written break-glass process for survey data during outages, with named approvers and periodic test records.
Automatic logoff (45 CFR 164.312(a)(2)(iii))Addressable. Electronic sessions end after a period of inactivity.Session timeouts on admin consoles and response review screens. Document the interval chosen, or the equivalent measure if you deviate.
Encryption and decryption (45 CFR 164.312(a)(2)(iv))Addressable. A mechanism to encrypt and decrypt ePHI.Encryption at rest for the survey database, file storage and backups, with key management recorded. Confirm the method with your hosting team.
Transmission security (45 CFR 164.312(e))Protects ePHI sent over electronic networks, including encryption where addressable.TLS for respondent and staff traffic, secured email notifications, and no ePHI in plain-text exports sent by unsecured channels.
Audit controls (45 CFR 164.312(b))Mechanisms that record and examine activity in systems holding ePHI.Logs for logins, response views, exports, and configuration changes, with retention and a named reviewer.
Addressable specifications (45 CFR 164.306(d))Assess whether each addressable specification is reasonable and appropriate, and document the decision.A decision record per addressable item. If not implemented, document why and implement an equivalent alternative where reasonable.
Business associate contract (45 CFR 164.314(a)(2)(i))Requires Security Rule compliance, flow-down to subcontractors handling ePHI, and incident reporting.A signed agreement with any hosting, backup, email or support provider that can touch ePHI. Confirm subcontractor terms in writing.
Documentation and retention (45 CFR 164.316)Written policies, procedures and records of required actions, kept and maintained.Policies, a survey data retention schedule, and a change log. Confirm retention periods with counsel and applicable state law.

Where patient survey data can live

Under this model, the covered entity or research institution runs LimeSurvey on servers it controls, either in its own data center or in a private cloud account it administers. No outside vendor hosts the responses, so no business associate relationship is created for the hosting itself, though any staff or contractor who administers the system must be covered by the organization's own safeguards. The Security Rule applies to every ePHI copy the organization creates, receives, maintains or transmits, so the organization carries the full administrative, physical and technical burden.

  • Server control: Your team sets the region, network segmentation, patching schedule and backup location.
  • Access roles: Administrator, survey designer and data analyst roles are configured inside the application and enforced through your directory.
  • Encryption: Transport and storage encryption are configured by you, and the decision on each addressable encryption specification must be documented.
  • Contractor access: Any implementation partner that touches the servers needs a written agreement covering ePHI handling.
  • Risk location: Patch lag, misconfigured backups and weak administrator credentials become the organization's own findings.

Check that the hosting location matches your written data residency policy, and that each addressable specification has a documented decision.

Which open-source platform fits patient questionnaires

LimeSurvey is the primary fit for patient outcome and feedback questionnaires that need depth, branching and research exports. Formbricks fits only narrower prompts, so the decision turns on instrument complexity, hosting control and the systems the responses must reach.

LimeSurvey as the primary fit

LimeSurvey is licensed under GPL v2.0, with the option to use any later GPL version, and its Community Edition can be self-hosted so that responses stay on the organization's or its provider's server. For patient questionnaires, this means the instrument, the response store and the backups can all sit inside a HIPAA-safeguarded environment you control. Confirm the license terms and the Community Edition feature set against the release you plan to deploy.

Question depth and multilingual reach

LimeSurvey supports more than 30 question types and multilingual surveys in more than 80 languages. Clinics serving mixed-language patient populations can publish one instrument in several languages rather than maintaining separate forms, but translations of validated outcome measures still need clinical and linguistic review. Ask your research lead which validated instruments require licensed translations and confirm the language set in the release you deploy.

Research export plugins

The ExportR and ExportSTATAxml plugins give research teams direct exports for statistical analysis in R and Stata. Export files carry identifiers and item-level answers, so the export permission should be limited to named analysts and exports should be logged. Test each export against your codebook before data collection starts, since a renamed variable can break a registry or trial dataset.

Database and PHP requirements

LimeSurvey requires PHP 8.1.29 or later with the mbstring and PDO drivers, and runs on MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Your database choice determines backup tooling, encryption-at-rest options and the skills your operations team needs. Confirm the supported stack against the current installation requirements before sizing servers.

Version currency and support windows

The latest stable release is LimeSurvey Community Edition 7.6.0, and the 6.17.19 release reached end of support on August 31, 2026. A patient-facing instrument running an unsupported branch carries unpatched risk, so the upgrade path should be part of the plan from day one. Ask your implementation partner how security fixes are delivered and who applies them, since Community Edition support terms are not the same as a paid subscription.

Formbricks for short prompts

Formbricks suits brief in-app or short feedback prompts, such as a single post-visit rating or a two-question check-in. It is a weaker fit for long validated questionnaires with complex skip logic, scoring and research exports. If you plan to use it for patient-facing prompts, confirm where its data is stored, which features your edition includes and whether its integrations can be disabled so no third party receives health-related responses.

How a patient survey rollout moves from scoping to go-live

This sequence takes a patient survey or health questionnaire from an agreed instrument list to a hardened, documented, self-hosted deployment that the care or research team can run without depending on the implementer. Each phase closes with a named written output so the covered entity can see what was decided and why.

  1. Inventory instruments, data and access needs

    Start by listing every survey and questionnaire, the question-level fields that hold ePHI or could identify a patient when combined, and who needs to see each field (clinicians, quality staff, researchers, vendors of the platform). Confirm which responses are linked to a medical record number and which are anonymized. The written output is a data inventory with an access matrix that names each role and the fields it may read, edit or export. The step is done when the clinical owner and privacy officer both sign the matrix.

  2. Map requirements to the Security Rule

    Take the data inventory and map each finding to the relevant HIPAA Security Rule standards in the administrative, physical and technical safeguard sections, and to the organizational and documentation requirements. Use NIST SP 800-66 Rev. 2 as a working guide for the sample questions for each standard, noting that it is informational rather than binding. For every addressable implementation specification, record whether it is reasonable and appropriate and, if not, the equivalent measure. The output is a requirement register tied to owners. It is complete when each ePHI field and each addressable specification has a recorded decision.

  3. Decide hosting and business associate terms

    Decide where the platform runs: the organization's own data center, a cloud account it controls, or a hosting provider. Confirm which parties will create, receive, maintain or transmit ePHI, including backup and support access, because each one that does may need a business associate contract under 45 CFR 164.314. If a third-party SaaS survey tool is considered, its contract must be checked against the same terms before any patient data is entered. The output is a hosting decision record and a list of signed or pending agreements. Ask counsel to confirm the agreements, since this step does not establish legal sufficiency.

  4. Build and harden the deployment

    Install the chosen platform, such as LimeSurvey, in the agreed environment and configure encryption in transit and at rest, multi-factor authentication for administrators and any remote access, unique user accounts, role-based permissions that match the access matrix, automatic session timeouts, audit logging of access and changes, and scheduled jobs that enforce the retention schedule. Keep configuration in version control so changes are traceable. The output is a hardened build with a configuration record and a summary of each technical safeguard and how it is met. The step closes when a peer review of the configuration matches the requirement register.

  5. Validate with synthetic data

    Test every instrument, branching path, export and role using synthetic patient records that carry no real identifiers. Confirm that users without rights cannot view or export restricted fields, that logs capture the expected events, that retention jobs delete or anonymize as designed, and that backups can be restored into a separate environment. Record defects and retest them. The output is a validation report with test cases, results and a list of accepted residual risks signed by the owner. Testing with real patient data before this sign-off is outside the intended process.

  6. Train staff and write runbooks

    Train the clinical, research and administrative users on their roles, on handling of exports, and on what to do when a respondent asks for a copy or deletion. Write runbooks for account provisioning and removal, incident reporting, restore from backup, patch application, and retention exceptions. Include the path for reporting a suspected security incident to the covered entity's security officer. The output is a training record for each role and an approved runbook set. Completion is confirmed when each user group has been trained and each runbook has an owner.

  7. Go live with monitoring

    Open the survey to patients in a controlled release, starting with the instruments and cohorts agreed in scope. Enable monitoring for failed logins, privilege changes, unusual export volumes, service availability and backup status, and confirm that alerts reach a named responder. Review the first access logs against the access matrix. The output is a go-live record listing the release scope, monitoring coverage and the first review findings. The step is complete when the review finds no access outside the matrix, or each exception has a documented fix.

  8. Hand over operations with written ownership

    Transfer day-to-day operation to the internal team or a support retainer, with written responsibilities for patching, access reviews, backup testing, retention runs and periodic review of the requirement register. Confirm how changes to instruments, roles or hosting are requested and approved, and when the Security Rule proposed revision, which HHS has not finalized, would trigger a reassessment. The output is an operations handover document signed by the covered entity's owner and the implementation team. It closes the engagement only when every recurring task has a named owner.

What auditors and regulators ask for from a survey system

This table maps each evidence item an assessor or HHS investigator is likely to request to the component of the survey system that produces it. Use it to plan what the platform must log, store and export before a review starts. These items are inputs to an assessment; DeployOpen prepares them but does not issue attestations or certifications.

Evidence itemComponent that produces itWhat the reviewer checks
Risk analysis recordDocumented analysis covering every system holding survey responses with ePHI, including the survey platform, database, exports and backupsScope matches the real data flows, threats are identified, and the record is updated after changes
Asset inventoryHosting inventory listing the survey application, database, object storage, mail relays and integrations that touch responsesEvery location where respondent data sits or passes through is accounted for
Signed BAAs and subcontractor flow-downBusiness associate agreements with the hosting provider, backup vendor and any SaaS add-on that receives responsesContracts require Security Rule compliance and incident reporting, and subcontractors carry the same terms
Access role matrix and review recordsSurvey platform roles and permissions, plus dated access reviews against clinical and research need to knowStaff see only the surveys and patient-linked data their role requires, and leavers are removed
MFA and encryption configuration evidenceIdentity provider settings for admin and researcher logins, TLS configuration, and database and backup encryption settingsMulti-factor authentication covers remote and administrative access, and encryption status is documented for data at rest and in transit
Audit log samplesApplication and server logs recording logins, survey edits, response exports and deletions, forwarded to a central storeLogs are complete for the review period, protected from alteration, and reviewed on a defined schedule
Retention and deletion procedure with logsRetention rules configured per survey, scheduled deletion jobs and records of what was deleted and whenDeletion runs as written, and the procedure covers exports and backups as well as the live database
Backup and restore test resultsScheduled backups of the database and file store, plus dated restore tests into a separate environmentRestores succeed within the recovery target the organization set, and test results are signed off
Incident response runbookWritten procedure covering detection, containment, breach assessment and notice to the covered entity under the business associate contractNamed roles, contact paths and decision points are current and were exercised in a tabletop or drill
Training recordsAttendance and completion records for staff who administer the platform or handle patient survey dataTraining covers HIPAA obligations and the platform procedures, and records are kept for each staff member

Which frameworks and enforcement cases apply beyond HIPAA

Which frameworks apply to patient survey data besides HIPAA?

It depends on where you operate and what role you play, so confirm the list with your counsel and compliance lead before you scope the build. In the United States, the HIPAA Security Rule in 45 CFR Part 164 Subpart C is the baseline for covered entities and their business associates. Outside the US, or for EU-based providers and researchers, other regimes may add duties on top, including GDPR, NIS2 and the European Health Data Space Regulation. Each one can change hosting location, access control, breach reporting and retention, so map them to your sites and data flows early.

Is HITRUST certification required for a self-hosted survey system?

No. HITRUST is an optional assurance framework that some health organizations request from their vendors and partners. HITRUST CSF v11.9.0, available from 24 September 2026, is organized into 14 control categories with 49 control objectives and 156 control specifications. Assessments produce e1 and i1 certifications that last one year and r2 certifications that last two years. Independent HITRUST assessors issue these, not DeployOpen, so ask whether your contracts or customers actually require HITRUST before adding it to scope. For planning, the HITRUST CSF release advisory lists the current version.

How can NIST SP 800-66 Rev. 2 help with HIPAA implementation?

NIST SP 800-66 Rev. 2, published in February 2024, is a practical implementation guide for the HIPAA Security Rule. It gives key activities, descriptions and sample questions for every standard. HHS lists it as informational, not legally binding, so it does not replace the regulation. Use it as a checklist when you map each safeguard to a configuration, role or log source in your self-hosted survey environment. Your compliance team should still confirm how each control maps to your own risk analysis.

When will the HIPAA Security Rule revision take effect?

No final rule had been published as of October 2026. HHS proposed a major Security Rule revision on 6 January 2025 (90 FR 898, RIN 0945-AA22), with comments due 7 March 2025. The latest Unified Agenda lists it under Long-Term Actions with final action projected for July 2027. Until then, the current rule applies. Plan your design so that stronger controls, such as multi-factor authentication, encryption and audit logging, can be added without rebuilding the platform, and confirm the status on the Federal Register proposed rule before each design review.

How much can HIPAA civil penalties cost per violation?

For penalties assessed on or after 28 January 2026, the inflation-adjusted range under 45 CFR 102.3 runs from $145 per violation, where there was no knowledge, to $2,190,294 per violation for uncorrected willful neglect. The calendar-year cap is $2,190,294. The amount depends on the culpability tier, how quickly the problem was corrected and the number of violations found. The practical lesson is that documented, timely corrective action changes the outcome, so keep evidence of risk analysis and remediation with the platform.

Do NIS2 and GDPR apply to EU health survey platforms?

They can, depending on your role. NIS2 Annex I lists health as a sector of high criticality, covering healthcare providers, EU reference laboratories, medicinal product research and development, and certain medical device manufacturers. GDPR Articles 32 and 34 require appropriate security and breach notification to data subjects. On 3 September 2026, France's CNIL fined Hopital Prive de la Loire EUR 500,000 for external access to its patient record system without VPN or multi-factor authentication, and for access control that ignored the care team's need to know. Ask your data protection officer which of these apply and how external access is secured.

What does the European Health Data Space Regulation require for research surveys?

Regulation (EU) 2025/327, the European Health Data Space Regulation, sets rules for the use and secondary use of health data in the EU. Researchers and health organizations in scope should confirm how it governs data access, documentation and reuse of questionnaire outcomes. It does not replace GDPR, so both can apply at once. Because its obligations depend on your role and the data purpose, have legal counsel confirm applicability, then design the survey platform so that data location, access logs and export controls can meet those terms.

How research questionnaires differ from patient feedback

Outcome questionnaires for health research carry obligations that patient feedback forms usually do not. Before the first question goes live, the ethics board approval and the protocol define who may see identifiable responses, how long records are kept, and under what conditions data may leave the study team. Research teams typically replace direct identifiers with a study code through pseudonymization, keep the key linking codes to identities in a separate, more tightly controlled store, and document any data sharing agreement with collaborating institutions. Where a questionnaire supports a regulated trial, the team should also confirm whether 21 CFR Part 11 applies to the electronic records and signatures, which affects audit trails, access controls and validation of the survey system itself. Confirm this with the sponsor and your quality function early, because it changes the build more than any feature choice.

The same self-hosted LimeSurvey instance can often serve a patient feedback program and a research study, but the rules around it differ. Feedback responses usually need role-based access for clinical managers and a retention period set by the provider's records policy. Research responses may need separate surveys or projects, restricted roles for coded data, a locked retention schedule that matches the protocol, and deletion or archiving steps agreed with the ethics board. Keep the two in separate survey groups with distinct administrators so that a feedback manager cannot export study data by accident.

Export is where research governance most often breaks. LimeSurvey includes statistical export options such as the ExportR and ExportSTATAxml plugins, which make it easy to move responses into analysis tools. Check each export path against the data governance plan before it is enabled: which fields are included, whether identifiers or free-text answers leave the server, who may run the export, and where the output is stored afterward. Confirm with your implementation partner and your data protection officer which plugins are installed in your environment and whether they are permitted for each study.

What do buyers ask before hiring help for patient surveys?

Is LimeSurvey free to self-host for patient surveys?

Yes, the Community Edition is free to download and self-host, and survey data stays on the server you choose. The license cost is only one line. Infrastructure, database administration, PHP and web server maintenance, backups, patching, and the staff who run the instrument all carry real costs. Because you host it, the HIPAA safeguards (access control, audit logging, encryption, backups and retention) become your obligations, and they need people and time. Ask any partner to separate one-time setup from recurring operations in the quote. If you prefer the hosted route, LimeSurvey Cloud publishes plan limits, including Basic at 1,000 responses per month with 1 admin user and Expert at 10,000 responses per year with 3 admins, but a hosted vendor still needs a business associate agreement before it receives ePHI.

What drives the cost of a self-hosted patient survey project?

The main drivers are the number of instruments, the systems they connect to, and how much validation the clinical and research teams need. Hosting is a recurring cost that depends on whether you run it in your own data center or a cloud account that will sign a business associate agreement. Integrations with an EHR, a patient portal or a research data store add mapping, testing and maintenance. Validation of questionnaires, role design, encryption setup, documented risk analysis and staff training each add effort. Ask for a fixed-scope quote that lists each instrument, each integration, the hosting model and the operations period separately, so you can see what recurs after go-live.

How long does a self-hosted patient survey rollout take?

The duration depends on the scope agreed in writing, and this page does not state a fixed timeline. The biggest variables are the number of questionnaires, whether responses must flow into clinical systems, how many approvals the clinical and privacy teams require, and whether the hosting environment already exists. A pilot with one questionnaire and a single reporting view will move faster than a multi-site program with EHR links. Ask any partner to show the phases, the approval gates and what the client must provide at each stage before agreeing to a date.

What does the client team need to provide for a survey project?

The work needs a current data inventory that lists which questionnaires collect ePHI, which fields are identifiers, and where responses are stored and shared. It also needs clinical and compliance sign-off on question content, consent text and retention periods. IT must provide access to the hosting environment, identity provider, network paths and backup targets. Name one accountable owner for each of these: the clinical instrument owner, the privacy or compliance lead, the IT platform owner and the survey administrator. Without these owners, approvals stall and the risk analysis cannot be finished.

Can our team run a HIPAA-aligned survey platform without a partner?

A team can do it alone if it already has security engineering skills for hosting, identity and encryption, and staff who can administer LimeSurvey and manage its database and updates. The heavier burden is the documentation. HIPAA requires you to assess each addressable implementation specification and record why you adopted it, adapted it or used an alternative measure, which means a documented risk analysis and written policies. NIST SP 800-66 Rev. 2 is a useful informational guide for mapping those activities to the Security Rule. If your team lacks these skills or capacity, a partner can prepare the controls and evidence, though the covered entity remains responsible for its own compliance.

Is there a HIPAA certificate for our survey platform?

No. There is no HIPAA certification. HHS states that no Security Rule standard requires an entity to certify compliance, and that HHS does not endorse or recognize private certifications, which also do not stop HHS from later finding a violation. The Office for Civil Rights enforces the rule through complaints, compliance reviews and audits. Be wary of any vendor or partner that claims a HIPAA certificate. Ask instead for the evidence you can review: the risk analysis, the configuration baseline, access logs, the business associate agreement and the documented retention schedule. Independent assessments against a framework such as HITRUST are separate from HIPAA and are issued by external bodies.

Why does a SaaS survey tool need a business associate agreement?

When a survey collects ePHI for a covered entity, the company hosting or processing those responses is acting as a business associate. Under 45 CFR 164.314, the business associate contract must require the vendor to comply with the Security Rule, pass the same terms to any subcontractor that handles ePHI, and report security incidents, including breaches of unsecured PHI. Without that agreement in place, sending patient responses to a hosted survey service creates a compliance gap, regardless of how secure the service is. Before using any hosted survey service with ePHI, confirm the vendor will sign a business associate agreement, list its subprocessors and state the hosting region. Penalties for Security Rule failures are significant, with the inflation-adjusted civil money penalty for penalties assessed on or after January 28, 2026 reaching $2,190,294 per violation, with a calendar-year cap of the same amount.

Which parts of a patient survey setup do auditors and regulators ask about?

Regulators and reviewers typically ask for evidence that access is limited to the roles that need it, that responses are encrypted in transit and at rest, that audit logs exist and are reviewed, and that retention and deletion follow a written schedule. They also ask how the organization handles emergency access, automatic logoff and incident reporting. Prepare these items as a binder of configuration records, policies and test results before an assessment starts. Note that HHS OCR's 2024 to 2025 audit program reviewed 50 covered entities and business associates on hacking and ransomware-related provisions, so backups and access controls deserve early attention.

How DeployOpen scopes and supports a healthcare survey build

DeployOpen plans, implements, hardens, documents and supports self-hosted survey platforms inside your own infrastructure, so patient responses stay on servers you control. Each engagement starts from a written, fixed scope that reflects how your organization handles ePHI, who needs access and how long responses must be kept.

How we scope

  • Map which questionnaires collect ePHI, outcome data or research data, and which do not.
  • Define hosting location, network paths and who administers the server before any build begins.
  • Agree roles, retention periods and deletion rules in writing, with the fixed scope and deliverables.

How we build

  • Install LimeSurvey or Formbricks on infrastructure you designate, with encryption in transit and at rest configured.
  • Configure unique user accounts, role-based permissions and logging for every administrator and reviewer.
  • Test access controls, backups and survey data exports against the requirements agreed in the scope.

How we hand over

  • Deliver configuration records, access matrix, retention settings and runbooks your security and compliance staff can review.
  • Document the hosting model so your privacy officer and counsel can confirm the business associate position with any third party.
  • Walk your team through administration, backups and incident steps, and confirm which items remain your responsibility.

How we support

  • Ongoing support, upgrades and continuous security testing are available as a retainer after go-live.
  • Plan version upgrades around the vendor's support windows, so the survey platform stays on a supported release.
  • Confirm with your team which controls and evidence need periodic review, since DeployOpen prepares evidence but does not issue audit reports.

Talk to our team.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.

  • 30-minute call: free, with no obligation.
  • NDA on request: we can sign before you share details.
  • Clear next steps: a scope and plan after the call.