Guide
Patient Feedback and HIPAA: Questions to Review
Review what you collect, where it goes, who can access it and which agreements your workflow needs.
Patient feedback can contain sensitive information in answers, attachments, URLs and metadata. Before selecting a survey tool, map the data you intend to collect and the places it will go. Work with your organization's privacy and security team to determine the requirements for the specific workflow.
Identify the information involved
HHS explains that PHI includes identifiable information about health, care or payment held or transmitted by a covered entity or business associate. A feedback form can capture that information even when its main question concerns service quality. Review open text and contextual fields alongside the visible questions. HHS guidance
An “anonymous” label, removal of a name or replacement with a visit ID does not by itself establish de-identification. HHS describes Safe Harbor and Expert Determination methods. Have qualified reviewers assess your collection and metadata design rather than assuming an opaque identifier removes the risk.
Establish the provider relationship
HHS describes the written assurances used when a covered entity discloses PHI to a business associate. Determine which providers receive the data, including notification, analytics, storage and integration services, and resolve the applicable agreements before use. A signed agreement does not replace review of the actual workflow and safeguards. HHS business associate guidance
Ask concrete implementation questions
- What information appears in answers, attachments, URLs, logs and notification emails?
- Which people and connected apps can read or export responses?
- What retention, deletion and incident-response arrangements apply?
- What hosting and encryption requirements does your organization have, and can the provider document them?
- Can you test the workflow with synthetic data before launch?
These questions help you evaluate a deployment; they are not a certification or a complete legal assessment.
Evaluate Pollenate's supported workflow
Pollenate has role-based access, organization-enforced two-factor authentication, and private forms that can be shared with chosen members. Review how those settings interact with emails, exports and automations. A private form is an access control, not a guarantee that every external destination is suitable for regulated information.
Contact Pollenate before submitting PHI to confirm whether the intended use is supported and agree any required contractual and technical arrangements. Do not assume a BAA, data residency, field-level customer-data encryption or compliance status from a plan name or marketing description.
Start with a sample feedback form and synthetic responses. Once your requirements are resolved, document the approved configuration and the people responsible for reviewing changes.
Official guidance reviewed November 13, 2026. Your organization's privacy and legal teams should decide how the guidance applies to your use.