Project

General

Profile

Actions

Task #306

open

Epic #13: Patient Portal

Feature #300: Patient Consent Management & Signature Workflow

Panda Doc API Integration for Patient Consent

Added by Redmine Admin about 1 month ago. Updated 5 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Start date:
01/05/2026
Due date:
% Done:

0%

Estimated time:

Description

Description:

Integrate DocuSign to allow patients to electronically sign consent forms securely.

Requirements:

  • Send consent forms to patients via DocuSign.
  • Allow patients to complete electronic signatures as part of the application flow.
  • Receive signing status and signed documents from DocuSign.
  • Handle incomplete, cancelled, or failed signing scenarios.

Acceptance Criteria:

  • Consent forms are successfully sent for signature.
  • Signed documents are received and processed correctly.
  • Consent status updates automatically after signing.
Actions #1

Updated by Redmine Admin 28 days ago

  • Subject changed from DocuSign API Integration for Patient Consent to Panda Doc API Integration for Patient Consent
Actions #2

Updated by Redmine Admin 28 days ago

  • Assignee changed from Abhishek Thakur to Vikash Kumar
Actions #3

Updated by Vikash Kumar 26 days ago

  • Assignee changed from Vikash Kumar to Deeksha Singh
Actions #4

Updated by Vikash Kumar 23 days ago

  • Status changed from New to Ready to QA

Integrated PandaDoc for secure electronic signing of patient consent forms, enabling forms to be sent to patients within the application flow, capturing signing status and signed documents, and automatically updating consent status.

Actions #5

Updated by Deeksha Singh 5 days ago

QA test cases:

  • Verify consent form is automatically created when a user confirms email or is added by admin.
  • Verify newly created user is correctly assigned to the generated consent form.
  • Verify system sends an in-app notification informing the user about the consent form availability.
  • Verify system sends an email notification informing the user about the consent form availability.
  • Verify notifications are sent only once per consent form creation.
  • Verify “Consent Form” tab appears in the Profile section after user login.
  • Verify user can view the consent document from the Consent Form tab.
  • Verify user can electronically sign the consent form via PandaDoc.
  • Verify signed consent document is received back from PandaDoc and stored correctly.
  • Verify user can download the signed consent form after completion.
  • Verify consent status automatically updates to Completed after successful signing.
  • Verify consent status remains Pending if signing is incomplete or cancelled.
  • Verify system handles failed PandaDoc signing scenarios gracefully without marking consent as completed.
  • Verify when booking an appointment and clicking Join Meeting with no consent form, a new consent form is created and signing popup is displayed.
  • Verify when consent form exists but is not completed, user is prompted to sign before joining the meeting.
  • Verify when consent form exists and is completed, user can join the meeting without any popup.
  • Verify consent form signing is enforced before allowing access to Join Meeting.
Actions #6

Updated by Deeksha Singh 5 days ago

  • Status changed from Ready to QA to Ready To PROD
Actions #7

Updated by Deeksha Singh 5 days ago

  • Status changed from Ready To PROD to In Progress
  • Assignee changed from Deeksha Singh to Vikash Kumar
Actions

Also available in: Atom PDF