Patient Identification
Full legal name, date of birth, contact details and an identifier such as medical record number to avoid sample mismatches and ensure accurate result delivery.
A well-drafted consent form protects patient autonomy, clarifies the scope of testing and data use, and documents permission required under federal rules such as ESIGN for e-signatures and HIPAA for protected health information. Clear consent reduces legal and clinical uncertainty and supports downstream use for care, research, or third-party disclosure as authorized by the patient.
Primary users and stakeholders include patients, authorized family members, and a range of clinical and laboratory professionals who collect and act on genetic information.
Each party has distinct responsibilities: patients give consent, clinicians facilitate understanding, and laboratories maintain records and follow limitations specified in the consent.
Full legal name, date of birth, contact details and an identifier such as medical record number to avoid sample mismatches and ensure accurate result delivery.
A concise explanation of why the test is performed, including clinical indications or research goals, and whether results could affect treatment decisions.
Specify the genes, panels, or analyses to be performed and whether incidental or secondary findings will be evaluated and reported.
Detail who can access raw data and reports, third-party sharing policies, de-identification steps, and whether data may be used for future research.
Describe potential medical, emotional, or privacy risks, and foreseeable benefits, including limitations in predictive value or clinical utility.
Explain how to withdraw consent, what withdrawal affects (future testing, data use), and any limits after data release or de-identification.
| Form Field | System Configuration Settings | Setting |
|---|---|
| Authentication Method | SMS code, institutional SSO, or identity verification |
| Signature Type | Typed name, drawn signature image, or PKI-backed |
| Conditional Fields | Show optional research consent only if selected |
| Save Destination | EMR record and secure archival repository |
Ensure the chosen platform supports secure signing, audit trails, and integrations with clinical systems before e-submission.
Confirm platforms can provide audit logs, support HIPAA BAAs where required, and export signed records in standard formats for the EMR.
Consent must be documented prior to any genetic sample collection or testing.
Turnaround varies by lab; check lab-specific processing estimates.
Obtain new consent when proposing tests outside original scope.
Clinically significant findings should be communicated promptly per institutional policy.
Review consent policy whenever data-sharing practices change materially.
| Criteria | Clinical Consent | Research Consent |
|---|---|---|
| Scope | direct patient care | study-specific or broad future use |
| IRB Review | not required | required for human subjects research |
| Data Sharing | limited to care team | may include broad research sharing |
| Withdrawal Effect | affects future testing | may not retract already-shared data |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |