AWS sms-voice documentation change
Summary
Refined healthcare registration guidance: clarified denial reasons, paper form requirements, and multi-location registration scenarios.
Security assessment
Changes improve compliance documentation but don't address security vulnerabilities. Privacy policy mentions are compliance-focused, not security feature additions.
Diff
diff --git a/sms-voice/latest/userguide/registration-help-vertical-healthcare.md b/sms-voice/latest/userguide/registration-help-vertical-healthcare.md index c94d917a1..650d68e54 100644 --- a//sms-voice/latest/userguide/registration-help-vertical-healthcare.md +++ b//sms-voice/latest/userguide/registration-help-vertical-healthcare.md @@ -67 +67 @@ Denial title reference Denial title | What it means for healthcare providers -**Campaign unclear** | Your description doesn't clearly explain what messages patients will receive. "Healthcare communications" is too vague – specify: "Appointment reminders, prescription refill notifications, and billing alerts for established patients of Smith Family Medicine." +**Campaign unclear** | Your description doesn't clearly explain what messages patients will receive. "Healthcare communications" is too vague. Specify something like: "Appointment reminders, prescription refill notifications, and billing alerts for established patients of Smith Family Medicine." @@ -79 +79 @@ Denial title reference Denial title | What it means for healthcare providers -**Opt-in workflow mismatch** | The practice name on your opt-in form doesn't match your registered brand. If your form says "Downtown Medical Associates" but you registered as "DMA Health LLC," this triggers a mismatch. +**Opt-in workflow mismatch** | The practice name on your opt-in form doesn't match your registered brand. For example, your form might say "Downtown Medical Associates" but you registered as "DMA Health LLC." This difference triggers a mismatch. @@ -85 +85 @@ Denial title reference Denial title | What it means for healthcare providers -**Opt-in workflow non compliant privacy policy** | Your opt-in flow doesn't link to a privacy policy or doesn't state that mobile opt-in data won't be shared with third parties. Critical for healthcare – patients expect strict data handling. +**Opt-in workflow non compliant privacy policy** | Your opt-in flow doesn't link to a privacy policy. Or it doesn't state that mobile opt-in data won't be shared with third parties. This is critical for healthcare – patients expect strict data handling. @@ -147 +147 @@ Many healthcare practices collect SMS consent on paper intake forms. This is val -**For registration:** Photograph or scan the relevant section of your paper form and host it at a publicly accessible URL, or upload a screenshot showing the SMS consent portion. +**For registration:** Photograph or scan the relevant section of your paper form. Then host it at a publicly accessible URL, or upload a screenshot showing the SMS consent portion. @@ -164 +164 @@ If patients opt in through your patient portal: -If your practice has multiple locations under one brand, you can use a single campaign registration. If locations operate under different brand names (e.g., "Smith Cardiology" vs. "Smith Orthopedics"), register each as a separate campaign. +If your practice has multiple locations under one brand, you can use a single campaign registration. Locations might operate under different brand names (for example, "Smith Cardiology" vs. "Smith Orthopedics"). In that case, register each as a separate campaign.