Reviews & UGC
AuraScore 81/100

Digital Therapeutics Patient Outcome Review and Evidence Syndication Plan

Deploy a post-purchase patient outcome capture and compliant UGC syndication strategy for digital health products.

Select this template when architecting a post-treatment outcome review loop for digital health apps, medical SaaS, or connected health hardware that must balance clinical evidence with patient privacy.

Template

Role: Lead Digital Health Product Strategist & Patient Experience Architect

Context

  • Digital health therapeutic scope: {{therapy_indication}}
  • Validated patient outcome milestones: {{clinical_endpoint_metrics}}
  • Patient informed consent protocol: {{patient_consent_framework}}
  • E-commerce transaction engine: {{ecom_storefront_platform}}
  • Downstream review syndication channels: {{syndication_destinations}}
  • Privacy and data governance constraints: {{hipaa_safeguard_protocols}}

Task

Design a structured end-to-end plan to capture, de-identify, validate, and syndicate patient outcome reviews and long-term adherence stories for {{therapy_indication}} while enforcing {{hipaa_safeguard_protocols}} across {{syndication_destinations}}.

Method

  1. Define optimal post-purchase review request timing triggered by specific patient progression markers aligned with {{clinical_endpoint_metrics}}.
  2. Design an asynchronous patient review portal integrated with {{ecom_storefront_platform}} that captures qualitative narrative and quantitative health improvement scores.
  3. Embed a multi-tiered consent authorization flow governed by {{patient_consent_framework}} to secure explicit marketing and syndication rights.
  4. Build an automated de-identification engine stripping all Protected Health Information (PHI) to guarantee adherence to {{hipaa_safeguard_protocols}}.
  5. Establish clinical accuracy screening to verify that user self-reported metrics align with realistic parameters of {{therapy_indication}}.
  6. Formulate syndication payloads formatted for {{syndication_destinations}}, separating clinical rating scores from validated qualitative testimonials.
  7. Create a governance cadence for periodic re-consenting, content expiration, and patient right-to-be-forgotten requests.

Constraints

  • MUST strip all 18 HIPAA identifiers from published reviews before pushing to {{syndication_destinations}}.
  • MUST NOT send review solicitations before the patient completes the minimum threshold for {{clinical_endpoint_metrics}}.
  • Every patient submission MUST include an explicit, unbundled opt-in governed by {{patient_consent_framework}}.
  • Reviews containing unsupported absolute medical cure claims MUST be routed to clinical moderation rather than published directly.

Output format

  • Strategic Deployment Blueprint (Phased across Activation, Collection, Redaction, and Syndication)
  • Patient Journey Timing Map (Touchpoint triggers, Day intervals, Success milestones)
  • PHI Scrubbing and De-Identification Protocol (Step-by-step logic)
  • Syndication Architecture Matrix for {{syndication_destinations}}

Self-review

  • Confirms absolute compliance with {{hipaa_safeguard_protocols}} across all ingestion points.
  • Verifies that solicitation triggers strictly correlate with {{clinical_endpoint_metrics}}.
  • Checks that the consent mechanism satisfies {{patient_consent_framework}} provisions.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

ecommerce-retail
ecom-reviews
healthcare-life-sciences
digital-therapeutics
patient-outcomes
ugc-strategy