Mckelvey Lung Transplantation Center Evaluation Referral Form
Create a custom McKelvey Lung Transplantation Center Evaluation Referral Form 0 that meets your industry’s specifications.
What this transplant referral form does
The Mckelvey Lung Transplantation Center Evaluation Referral Form is a healthcare intake document used to begin evaluation for lung transplantation. It gathers referral information, patient details, clinical history, and supporting information so the transplant center can review whether evaluation should proceed. A coordinator can upload the form to signNow, check or add fillable fields, route it to the required signer, and retain the completed record with its audit trail. Because the form may contain protected health information, the center should apply HIPAA safeguards and its own clinical intake policies.
Features for this referral workflow
signNow connects document preparation, signer routing, electronic completion, and audit evidence to the specific needs of a lung transplant referral intake process.
Field preparation
Upload the Mckelvey referral document, inspect automatically detected fields, and add missing patient, provider, date, or signature fields before routing the form.
Signer routing
Assign the referring provider or other required signer directly to the correct fields, reducing uncertainty about who must complete each referral section.
Electronic signing
Collect electronic signatures through a documented workflow while preserving signer actions, timestamps, and completion evidence for authorized healthcare staff.
Audit evidence
Use audit trails and document history to connect the completed referral with its signing events when the record is reviewed later.
HIPAA workflow
Support protected health information workflows with HIPAA compliance available through signNow when the healthcare organization has the required BAA.
Mobile access
Prepare or review the referral form on desktop or mobile devices, including iOS and Android signNow apps for authorized staff.
Complete the referral form in signNow
Prepare the Mckelvey referral form in signNow by checking every patient, clinical, and signer field before routing it for completion.
Upload form:
Upload the current Mckelvey referral form to signNow. Check fields:
Review detected fields and add missing patient or signer fields. Assign roles:
Assign the transplant coordinator, patient, or required signer. Send securely:
Send the completed referral for secure electronic signing. Store record:
Download the signed form and audit trail for the patient record.
Recommended referral workflow setup
Configure the referral workflow around signer attribution, protected health information, audit evidence, and the center’s documented retention policy.
| Setting | Recommendation |
|---|---|
| Authentication method | Email link with SMS OTP |
| Signature type | Typed or drawn electronic signature |
| Audit trail | Retain completion certificate and action history |
| Document retention | 6 years for HIPAA documentation (45 CFR §164.530(j)) |
| Encryption | TLS 1.2/1.3 in transit and AES-256 at rest |
How the referral audit trail works
The audit trail documents who handled the referral, what happened, and when, creating evidence separate from the visible signature on the form.
Authenticate signer:
Capture timestamp:
Hash document:
Seal record:
Track actions:
Export trail:
Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.
Authenticate referral form signers
PKI certificates:
X.509 certificates:
Two-factor authentication:
SMS OTP:
ID verification:
Signer evidence:
Access requirements for referral signing
Staff can prepare the Mckelvey referral form through supported desktop browsers, including Chrome, Firefox, Safari, and Edge, on Windows or macOS. signNow also provides mobile apps for iOS and Android. Encrypted transmission uses TLS 1.2/1.3, while stored data uses AES-256.
Browsers Chrome, Firefox, Safari, Edge Operating systems Windows, macOS, iOS, Android Secure access TLS 1.2/1.3 and mobile apps
Healthcare organizations should use managed Windows, macOS, iOS, or Android devices when referral records contain protected health information. Administrators should also review account provisioning, authentication, API access, and storage controls before deployment. HIPAA workflows require a Business Associate Agreement and organization-specific safeguards beyond the platform configuration.
Record-keeping practices for referrals
Preserve the completed Mckelvey referral form with the evidence and controls needed for healthcare records, privacy review, and later retrieval.
Confirm the governing retention period
Export the signed record and audit trail
Restrict access to referral information
Archive protected health information securely
Retention schedule for referral records
Retention depends on the record’s legal classification and state policy; the HIPAA documentation period below is distinct from the center’s clinical-record schedule.
Six years for HIPAA documentation
State healthcare rule period
Until litigation hold ends
Policy-defined clinical retention
Longer rule controls
Protect privacy during referral intake
Sending the referral to the wrong recipient can disclose protected health information and require incident review under the center’s privacy procedures. Leaving patient consent or authorization fields incomplete can prevent the transplant center from relying on the submitted evaluation information. Using unrestricted shared links may expose clinical details beyond the intended referral team and weaken access-control evidence. Saving a signed PDF without its audit trail can make later verification of signer identity, timestamps, and document history more difficult.
Legal standing of the referral form
For U.S. business transactions, an electronic referral record can be admissible when the signer intended to sign, consented to electronic records, can be identified, and the record remains reproducible. ESIGN and UETA generally support that treatment, but wills, certain court orders, and specified family-law documents are excluded.
Referral workflow examples
These examples show how transplant coordinators and referring healthcare teams can handle this form while preserving signer and privacy controls.
Transplant coordination
A transplant coordinator needs signed referral information from a referring provider while preserving a clear record of patient-document routing.
- Upload the referral form
- Assign the referring provider
- Retain the audit trail
signNow provides a defined sequence for uploading the Mckelvey referral form, placing or checking fields, sending it to the intended provider, and retaining the completed document with action history. The coordinator must still verify patient identity, authorization, and clinical completeness before accepting the referral.
Healthcare practice
A healthcare practice sends referral information from a mobile device when staff are coordinating evaluation outside a central office.
- Use the signNow mobile app
- Apply signer authentication
- Store the completed record
The signNow mobile apps can support referral preparation and signing on iOS and Android devices. For protected health information, the practice should use managed devices, apply minimum-necessary access, maintain the required agreement, and confirm that the final record and audit trail enter its approved patient-record system.
Resolve referral form workflow questions
Use these answers to address field detection, protected health information, signer identity, plan limits, and record retention for this referral form.
Open the Mckelvey Lung Transplantation Center Evaluation Referral Form in signNow, then use the fillable-field tools to add missing fields manually. Auto-detection may not identify every scanned field, so verify names, dates, medical details, and signature locations before sending.
Business includes legally binding eSignatures, templates, mobile apps, and audit trails at $8 per user monthly when billed annually. It includes 100 signature invites per user per year; additional invitations may incur overage fees, so review usage before selecting the plan.
HIPAA compliance is available when the appropriate Business Associate Agreement is in place. signNow states that HIPAA workflows protect private health information, but the transplant center must still apply minimum-necessary access, authorization, and retention policies under HIPAA.
Use SMS OTP or another available authentication control when the transplant center requires stronger signer attribution. signNow supports two-factor authentication, while the organization remains responsible for choosing controls appropriate to patient identity and referral sensitivity.
The Business Premium plan adds bulk send, but bulk sending should be used only when each recipient receives the correct referral record. For individualized clinical referrals, confirm recipient, patient, and document matching before release.
Completed records can be retained with signNow’s document history and audit trail, but the center must define its governing retention schedule. HIPAA documentation requirements generally use six years under 45 CFR §164.530(j); state rules may require longer.
Key performance indicators that demonstrate SignNow's proven track record.
BE READY TO GET MORE
Get this form now!
If you believe that this page should be taken down, please follow our DMCA take-down process.