AWS connecthealth documentation change
Summary
Added 'Consent and patient notification' section with compliance requirements and mandatory disclosure language for PHI handling
Security assessment
Documents new security controls for PHI processing including legal consent requirements and standardized patient notifications. While important for compliance, there's no evidence this addresses a specific existing vulnerability.
Diff
diff --git a/connecthealth/latest/userguide/patient-verification-agent.md b/connecthealth/latest/userguide/patient-verification-agent.md index 64aba470b..51e7a7a4f 100644 --- a//connecthealth/latest/userguide/patient-verification-agent.md +++ b//connecthealth/latest/userguide/patient-verification-agent.md @@ -5 +5 @@ -CapabilitiesCustomization options +CapabilitiesCustomization optionsConsent and patient notification @@ -18,0 +19,2 @@ The Patient verification agent eliminates time-consuming manual EHR lookups by a + * Consent and patient notification + @@ -50,0 +53,8 @@ After you configure the settings, choose **Publish** to apply the changes. +## Consent and patient notification + +Amazon Connect Health patient engagement uses AI to capture and transcribe conversations in real time. Because this feature records spoken communications that may contain protected health information (PHI), customers and their downstream integrators are responsible for complying with all applicable consent, recording, and privacy laws. This includes obtaining all legally required consents before enabling ambient documentation for any patient encounter. + +AWS’s patient engagement agent provides the following language at the outset of each interaction: + +"Hi, I’m your AI assistant. This call may be monitored and recorded by your health care provider and its service providers to improve their services." +