Skip to main content

Share a Prescription PDF When the Phone Share Button Fails

When a phone's share button fails, first confirm that the correct, current prescription PDF exists. Then use an approved download-and-attach route, verify the intended recipient and record what actually happened. Creating a file, opening a share sheet, handing it to WhatsApp and the patient receiving it are different events. A fallback must preserve document identity and privacy; it should not become an invitation to send screenshots or use any available personal account.

By Bractis · Updated · 9 min read

Indian clinic reception teams and doctors helping patients obtain their prescription PDFs, including shared family phones and mixed desktop/mobile workflows.

Identify which step failed before repeating the whole process

A patient may say 'the prescription did not share' when the file never generated, the browser blocked file sharing, the operating-system chooser closed or the messaging application did not finish sending. Each case needs a different recovery action.

First locate the final document inside the clinic's authorised record workflow. Confirm patient, visit, issue or correction version and page count. If the source is still a draft, a successful download does not make it an issued prescription.

MDN documents that native browser sharing depends on the device and supported targets. Its completion signal is not the same on every platform, and a cancelled share can reject the operation. Therefore, a clinic should not label the patient record 'delivered' solely because the share function returned.

Ask the patient or staff member what they actually saw, without requesting a screenshot containing unrelated conversations. A neutral record such as 'file created; share chooser closed; recipient not selected' is more useful than 'WhatsApp failed'.

Source: MDN: Navigator share method

Preserve the exact file the clinician intended to issue

Open the exported PDF from its actual saved location. Inspect the patient identifier, current visit, clinician details, medicine rows and any second page. A filename can help find a document but is not sufficient evidence that the contents are correct.

Use a filename that is understandable within the approved workflow without unnecessarily advertising a diagnosis in notifications or shared download folders. The clinic must balance reliable matching with the privacy of the device and recipient; an opaque name alone can also invite wrong-file selection.

Keep the original issued document intact. Cropping it into images, combining it with an old prescription or editing it in an unrelated application can remove context and may affect any verifiable signature. If a correction is necessary, use the clinic's authorised correction process.

Do not treat a printed signature image as proof of cryptographic validation. Sharing staff should preserve the issued file and its provenance, not make legal claims about signature validity. The clinic's signature workflow needs its own verification.

Where several versions exist, make the superseded status explicit. A fresh download should not accidentally retrieve yesterday's cached file while the record screen shows today's correction.

Use a controlled manual attachment route

A manual route usually means downloading the verified file and attaching that file through an approved messaging or record-delivery channel. The exact controls vary by phone and application version, so train the sequence around the evidence rather than a two-tap promise.

Before selecting a contact, establish which person is meant to receive this patient's document and through which agreed channel. A saved contact called 'Dad' or a shared family number does not establish permission for every family member's records.

Open or preview the chosen attachment again where the workflow allows it. Confirm that the selection is the current PDF, not an image thumbnail, an invoice or another patient's similarly named file. Minimise simultaneous downloads to reduce selection mistakes.

Do not move the file through a staff member's personal email, cloud drive or chat merely because the clinic channel is inconvenient. If the approved route is unavailable, use the clinic's documented alternative and explain the delay or paper-copy option.

After sending, distinguish the evidence available from the action still needed. The fact that a messaging application accepted an attachment does not establish that the intended person opened the right document or understood a clinical change.

On a narrow screen, scroll the table horizontally to read all columns.

Prescription sharing: events that must not be collapsed into 'sent'
EventWhat it establishesWhat remains unknown
PDF createdAn export existsCorrect patient and current version
File checkedContents inspected for this handoverRecipient and channel
Share openedDevice chooser is availableWhether a destination was selected
App handoffTarget received the file from the deviceMessage completion and recipient receipt
Message evidenceA channel reports a particular statusWhether the intended person can use it
Clinical changeA correction was communicated and checkedAny unresolved earlier copies or questions

Manage the copies left behind on shared devices

A downloaded PDF can remain in a browser download list, a device folder, a messaging application's recent files or a backup workflow. Logging out of the clinic application does not necessarily remove those separate copies.

Agree which clinic-managed locations may hold temporary files and who is responsible for clearing them under the clinic's policy. Do not delete the authoritative medical record as part of tidying a download folder. Retention and temporary-copy handling are separate decisions.

Patients control their own devices and may need the file for continuing care. Explain where the copy went in plain language without promising the clinic can remotely remove every forwarded or backed-up copy.

For support, provide a document reference, export time, device/browser description and failure stage through an approved channel. OWASP's logging guidance cautions against raw health information and secrets in diagnostics; the same minimisation question is useful when preparing a support attachment.

A test using fictional records can reveal a shared-device problem without exposing a real prescription. Include an old file with a similar name, a cancelled chooser and a second staff user to see what remains visible.

Source: OWASP: Logging Cheat Sheet

Recover a failed share without creating a confusing second version

Suppose a fictional clinic generates version 2 at 18:10, but the device chooser is cancelled. At 18:12, staff attach the previously downloaded version 1 by mistake. The problem is now wrong-version disclosure, not simply a failed send. Escalate the mismatch and reconcile the patient communication.

If the first send is uncertain, inspect the relevant channel evidence before sending repeatedly. Repeating a message may be appropriate under the approved process, but the record should identify that it is another delivery attempt for the same document, not a new prescription.

Consider eight fictional share attempts: five have appropriate confirmation for the intended recipient, one chooser was cancelled, one device rejected the file and one message status remains uncertain. Five of eight are confirmed on the stated evidence, or 62.5%. That is not a messaging platform's delivery-rate benchmark.

Account for the three unresolved attempts individually. A cancellation may need a new user action; unsupported file sharing may need manual attachment; uncertain delivery may need recipient follow-up. A global 'retry all' button hides those distinctions.

Test the fallback before the waiting room depends on it

Use the same types of device and channel that the clinic expects to support. Test successful export, cancelled native sharing, no compatible target, manual attachment and return to the patient record. A single demonstration on the vendor's phone is not a complete clinic acceptance check.

Include a two-page prescription and a corrected version. Verify whether the final PDF preserves both pages and whether the manual route clearly selects the current file. Confirm what the software records as a sharing attempt versus delivery.

Ask how a patient without the proposed application can receive the document. An accessible record workflow should have an appropriate alternative; installing a consumer app should not be treated as proof that the patient has received their medical information.

For Bractis, request this fictional failure sequence and inspect the actual supported export and fallback paths. The purpose is to learn their limits and train staff around them, not to assume that every mobile operating system exposes identical controls.

The share chooser closed, but the prescription was intact

A fictional clinic prepares a two-page prescription PDF for a patient who wants it sent to an agreed family contact. The phone's native chooser closes before a destination is selected. Staff retain the verified issued file, use the approved manual attachment route and recheck the recipient and page count. The record identifies a cancelled native attempt followed by the separate handover evidence. It does not record two prescriptions or infer delivery from the first tap.

Prescription PDF handover record

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Current document
Which patient, visit, version and page count identify the file that should be handed over?
Failure stage
What is the last event confirmed by evidence, and what is still unknown?
Recipient and route
Who is authorised to receive it, and which approved fallback is available on this device?
Reconciliation
How will uncertain delivery, an earlier version and temporary clinic copies be handled?

Questions doctors ask

Does opening WhatsApp from the share button prove delivery?

No. Device handoff, message completion and receipt by the intended person are different events. Record the evidence available rather than assigning a delivered status from the share action alone.

Can staff send a screenshot instead of the PDF?

A screenshot can omit pages, context or document properties. Prefer the verified issued file through the approved route; any alternative needs an appropriate clinic decision and a check that essential information is preserved.

Can a prescription go to the family's usual phone number?

Confirm the intended recipient and the patient's agreed sharing arrangement for this document. A number used for bookings or another family member's records is not sufficient by itself.

Should staff use their personal account when clinic sharing fails?

Do not improvise a personal-account route. Use the clinic's approved alternative, with an understandable explanation and appropriate record of the handover.

How should a repeated send be recorded?

Identify it as another attempt for the same current document unless a clinical correction created a new version. Check prior delivery evidence and reconcile any obsolete copy rather than silently generating multiple apparently current prescriptions.

Sources and scope

Updated on . This is an original document-handover workflow, not a promise of WhatsApp availability, delivery, signature validity or automatic removal of recipient copies. No independent clinical or legal review is claimed.

  • MDN: Navigator share method

    Primary browser documentation accessed 25 October 2026. Used for device-dependent file sharing and the distinction between operating-system handoff and recipient delivery. No fixed WhatsApp interface or file-size limit is asserted.

  • OWASP: Logging Cheat Sheet

    Relevant data-exclusion and access-control guidance accessed 25 October 2026. Supports avoiding raw credentials and health information in support logs; no complete security audit was performed.

Try the workflow
with Bractis.

Ask Bractis to demonstrate a cancelled share followed by an approved manual PDF attachment using fictional records, with current-version and recipient checks.

Request a clinic demo