Purpose
1.2. Ensure regulatory compliance (HIPAA), reduce human error, and streamline onboarding.
1.3. Enable fast, secure document handling to reduce manual data entry and accelerate patient admission.
Trigger Conditions
2.2. Referral or scheduling request is received.
2.3. Initiation from staff via EHR/EMR entry.
2.4. Patient is sent a document upload request via SMS, email, or app notification.
Platform Variants
3.1. DocuSign
• Feature/Setting: eSignature workflow with ‘Identification Verification’ module enabled for intake packages.
• Configure API: POST /envelopes with recipient authentication = "ID Check".
3.2. Twilio
• Feature/Setting: SMS with document upload link.
• Configure API: POST /Messages with mediaUrl.
3.3. SendGrid
• Feature/Setting: Email with secure upload request.
• Configure API: POST /mail/send; include secure upload CTA.
3.4. Dropbox API
• Feature/Setting: Automated folder creation and file upload endpoint for each patient.
• Configure API: /files/upload with path parameter.
3.5. OneDrive
• Feature/Setting: Intake area folder provisioning; file validation webhook.
• Configure API: /drive/root:/intake/{patient_id}:/children.
3.6. AWS Rekognition
• Feature/Setting: Automated ID document authenticity check.
• Configure API: CompareFaces & DetectText endpoints.
3.7. Google Drive
• Feature/Setting: Secure shared drive with access controls per intake session.
• Configure API: /files.create, set permissions via /permissions.create.
3.8. Adobe Sign
• Feature/Setting: Verification workflow with ‘Government ID Verification’ add-on.
• Configure API: POST /agreements, use verification parameter.
3.9. Plaid Identity
• Feature/Setting: Validate IDs through government database checks.
• Configure API: /identity/get endpoint.
3.10. IDology
• Feature/Setting: Automated KYC/AML checks on ID upload.
• Configure API: Submit Verification request.
3.11. Jotform
• Feature/Setting: Intake forms with file upload and e-sign.
• Configure: Enable File Upload and Signature widget.
3.12. Typeform
• Feature/Setting: Customizable onboarding with logic jumps to upload/ID step.
• Configure: Add File Upload field and webhook triggers.
3.13. KYC-Chain
• Feature/Setting: Automated ID matching and record-keeping.
• Configure API: /kyc/individual.
3.14. Slack
• Feature/Setting: Trigger notifications for staff on new uploads.
• Configure API: chat.postMessage with uploaded files link.
3.15. Zapier
• Feature/Setting: Integration to sync uploads with EHR/CRM.
• Configure Zap: New File Trigger → EHR API Action.
3.16. Formstack
• Feature/Setting: Secure intake forms with document validation logic.
• Configure: Add File Upload field, set validation rules in Workflow builder.
3.17. Cognito Forms
• Feature/Setting: Conditional ID upload step.
• Configure: Build logic-driven workflow, enable file storage.
3.18. Salesforce Health Cloud
• Feature/Setting: Patient record attachment via API during onboarding.
• Configure API: /services/data/vXX.X/sobjects/ContentDocument.
3.19. Workato
• Feature/Setting: Automate upload flow across tools (form, storage, EHR).
• Configure Integration Recipe: New Form Submission → Upload Validation → Patient Record Update.
3.20. Onfido
• Feature/Setting: Automated ID document and selfie verification.
• Configure API: /v3/checks with report_name = “document”.
Benefits
4.2. Ensures speedy, compliant, and verified patient intake.
4.3. Enables seamless integration with EHR, audit trails, and onboarding analytics.
4.4. Minimizes fraud and identity risks with instant KYC/verification checks.
4.5. Improves patient experience with faster, guided onboarding flow.