Clinical Workflow & DiagnosticsPurpose
1.2. Automating removal of paper-based bottlenecks to accelerate clinical workflows and diagnostics.
1.3. Ensure compliance and streamline consent management by auto-routing forms to relevant personnel and systems.
1.4. Automate the tracking of consent form status, digital signatures, and notify stakeholders automatically.
1.5. Support digital archival, audit logging, and consent retrieval for regulatory and patient safety purposes.
Trigger Conditions
2.2. Triggered by clinician request for a diagnostic or treatment requiring explicit consent.
2.3. Automatedly triggered when an inpatient workflow mandates updated consent.
2.4. Automation upon integration events—e.g., HL7/FHIR messaging from EHR systems.
Platform Variants
• Feature/Setting: API for envelope creation and recipient routing; configure webhook for completed forms.
3.2. Adobe Sign
• Feature/Setting: REST API for automated document upload, signature request, and status check.
3.3. Dropbox Sign
• Feature/Setting: Automated workflow builder to digitize forms and collect patient eSignatures.
3.4. Microsoft Power Automate
• Feature/Setting: Flow to route files from hospital forms system to EHR inbox; use "When a file is created" trigger.
3.5. Google Workspace (Drive & Forms)
• Feature/Setting: Google Apps Script for automating form generation, submission collection, and Drive-based archival.
3.6. JotForm
• Feature/Setting: Webhook automation to send new form entries to secure endpoints and trigger consent routing.
3.7. Formstack
• Feature/Setting: Smart Routing and Formstack Sign APIs for automating eConsent workflows.
3.8. PandaDoc
• Feature/Setting: Document automation API for consent forms, with automated recipient assignment and tracking.
3.9. Salesforce Health Cloud
• Feature/Setting: Process Builder or Flows for automating consent form creation and routing to patient records.
3.10. ServiceNow
• Feature/Setting: Workflow designer to automate consent capture and incident management linkage.
3.11. Twilio SMS
• Feature/Setting: Messaging API to automate consent notifications to patients and personnel.
3.12. Slack
• Feature/Setting: Incoming Webhooks to automate alerts of required eConsents in care teams’ channels.
3.13. SendGrid
• Feature/Setting: Automated email API by trigger to send consent forms and confirmation notifications.
3.14. Zapier
• Feature/Setting: Multistep Zap for routing, archiving, and notification of digitized consent forms.
3.15. Box
• Feature/Setting: Automated workflows for storing, sharing, and restricting access to digitized consents.
3.16. AWS Lambda
• Feature/Setting: Automated serverless function to process consent uploads and trigger downstream systems.
3.17. Google Cloud Functions
• Feature/Setting: HTTP-triggered automator to process digitized consent and audit log the event.
3.18. IBM Watson Health
• Feature/Setting: Integration with Watson APIs to automate consent extraction and flag incomplete items.
3.19. HubSpot
• Feature/Setting: Workflows and contact timeline automation for eConsent status.
3.20. Airtable
• Feature/Setting: Automated base scripts for tracking, routing, and updating real-time consent status.
3.21. SharePoint
• Feature/Setting: Automated document libraries for compliance archiving and consent routing processes.
3.22. Smartsheet
• Feature/Setting: Auto-update and route consent statuses across sheets; use automated reminders.
3.23. OnBase by Hyland
• Feature/Setting: Automated document management workflows for consent form lifecycle and secure routing.
Benefits
4.2. Automatedly increases speed, reliability, and auditability of consent capture and routing.
4.3. Automation improves patient experience and reduces registration bottlenecks.
4.4. Enables end-to-end visibility of consent processes for clinical dashboards.
4.5. Minimizes lost or incomplete consent forms through automated digital storage.