Passport sharing
A passport is shared for a specific Provider and a specific current version. Sending it once does not make it available to every Provider.
When a passport matters
You can have a patient profile before completing passport information. Some basic or general inquiries can proceed without a completed passport. Patient-specific medical or official appointment actions may require identity or passport information under the applicable flow.
The first send to a particular Provider
When a request requires a passport and that Provider has not received the current version, you are asked to approve its first delivery to that Provider. Check the named recipient before deciding. Declining prevents that Provider-specific request from being sent; other approved Hospital requests can still proceed.
If that Provider already has the current version
If the same current passport version was already delivered successfully to that Provider, ShifaTH recognizes it as already held. You are not asked to select, approve or send that same version again for the later request. Medical reports remain separately selected when needed.
After you replace the passport
A replacement becomes a new current version. Sending the older version does not count as sending the replacement. If the new version is required, its first delivery to a Provider requires a new approval where that Provider has not received it.
A different Provider is a separate decision
Successful delivery to one Provider does not make the passport available to another. When you select several Hospitals, the passport requirement and first-send decision are evaluated separately for each.
Keep profile storage and delivery distinct
Adding a passport to the patient’s profile is separate from delivering it to a Provider. The patient-profile and document pages explain those steps; the external-copy page explains the limits of later platform deletion.