TL;DR
Evaluate acquisition through approved administrative evidence: the offer shown, request receipt, handling, consultation scheduling and attendance where appropriately available. Patient weight changes and treatment details do not establish which marketing work produced an inquiry. Give the vendor a task-to-field specification with explicit exclusions, internal reconciliation and review of the actual report before sharing.
Ask which decision requires the requested outcome data
A vendor might request patient weight changes to demonstrate campaign quality. Ask what acquisition decision those fields would answer. They do not explain whether a campaign link worked, a request reached staff or an appointment state was recorded accurately.
Keep service quality and clinical evaluation in the clinic's qualified process. This article proposes a narrower administrative performance report. It does not judge treatment effectiveness, establish that an inquiry is medically suitable or imply every vendor engagement can be evaluated from the same fields.
For U.S. covered entities, HHS says the Privacy Rule generally requires reasonable steps to limit protected-health-information use, disclosure and requests to the minimum necessary for the purpose, with stated exceptions. HHS minimum-necessary guidance. Have the practice assess applicability, permitted purpose and the actual recipient. That guidance is not universal authorization to share a marketing summary.
Write a minimum-data performance specification
Start with the purchased task and work backward to sufficient evidence. The table is an original reporting proposal. The practice's responsible reviewers must assess the implemented fields, systems and transfer arrangement.
| Decision | Proposed administrative evidence | Information outside this specification |
|---|---|---|
| Did the approved offer appear correctly? | Versioned public page and creative, approval and change record | Patient stories and treatment results |
| Did the request route work? | Coordinated synthetic test and receiving-role confirmation | Live patient submission contents |
| Were requests received? | Approved request totals with period, definition and exclusions | Names, medical history and message text |
| Did administrative handling progress? | Approved category summaries for reached, pending or resolved states | Detailed symptom or medication questions |
| Were consultations scheduled or attended? | Practice-verified summary under a declared cohort and cutoff | Clinical assessment, prescribing and weight outcomes |
| Did the report overcount new relationships? | Internally reconciled new, existing, reentry and unknown summary | Person-level historical program exports |
| What work did the partner deliver? | Accepted URL changes, issue resolutions and documented scope | Unsupported assumptions about later health benefits |
For each proposed field, require purpose ___; internal source owner ___; definition ___; permitted recipient ___; retention arrangement ___; exclusion ___; limitation ___. A field without a useful decision should be challenged rather than retained because the software can export it.
Keep the join inside the practice
If consultation attendance must be reconciled to a defined inquiry cohort, authorized staff should assess whether the connection is reliable and permitted in approved systems. Do not hand the agency a patient export merely to make that work convenient.
A shared contact detail may represent different people, and duplicate records may represent the same request. Keep unresolved links unknown. An aggregate numerator and denominator do not form a valid conversion measure unless they describe compatible events and the same defined population.
Have the reviewer inspect the actual output. Small categories, exact timestamps, free text or combinations of fields may reveal more than their labels suggest. This specification provides no universal safe category size and does not call a report anonymous because names are absent.
Use the data-request guide when the vendor argues that additional fields are necessary. Require a specific unresolved task and a separately assessed request. Agreement to evaluate acquisition does not authorize expanding into clinical analysis or an advertising-platform upload.
Label the evidence gap instead of filling it with patient outcomes
If only request receipt is verified, report received requests. If the clinic can appropriately supply consultation attendance but cannot connect source, report attendance with source unknown. Weight change should not be substituted for a missing acquisition link.
Keep public discovery observations in their own section: tested questions, saved answers and cited pages where collected under an agreed method. The reporting specification explains method disclosure. An AI mention is neither an attended consultation nor a treatment benefit.
When reviewing continuation, compare the partner's accepted work with the original scope and the administrative evidence available. The owner can decide to repair tracking, improve the offer explanation, assign an unresolved queue or stop an unhelpful purchase. None requires manufacturing an efficacy claim.
Accept the report at its real scope
Close the reporting brief with approved fields ___; excluded fields ___; reconciliation owner ___; sharing decision ___; known gaps ___; decision now supported ___. Keep the report version and field definitions together so later revisions do not quietly add sensitive data.
If a material disclosure question remains unresolved, continue public-page and synthetic-route review while the practice resolves that specific request. Do not make all marketing work dependent on receiving clinical outcomes that the agreed task does not require.
Frequently asked questions
Can the clinic use weight outcomes for its own clinical evaluation?
That is a separate qualified clinical and governance decision. This specification concerns marketing acquisition and does not authorize or assess a clinical outcomes program.
Is an aggregated spreadsheet automatically safe to share?
No. Have the responsible reviewer inspect the actual fields, combinations, purpose and recipient. Aggregation is a proposed reporting format, not proof of permission or de-identification.
What if the agency cannot verify attendance without an export?
Keep its claim at the supported request stage or assess a narrower practice-produced summary. Do not convert a reporting limitation into a blanket entitlement to patient records.