Route patients and users directly to appointments, workouts, and health content.
• Patient receives appointment reminder
• Opens app to home screen
• Navigates through multiple menus
• Forgets why they opened the app
• Misses check-in or follow-up
• Patient receives appointment reminder
• Taps link, opens directly to check-in
• Opens pre-visit forms in the app
• Confirms the appointment in the app
• Fewer steps between the reminder and the visit
Link reminders directly to check-in, rescheduling, or telehealth sessions. One tap from the message to the right screen.
Deep link to specific workout plans, challenges, or progress tracking.
Keep health data out of link paths and parameters. Authenticate and authorize users in your app before showing private content.
Link SMS and email reminders directly to appointment details or check-in flows.
Route refill notifications to one-tap ordering within your pharmacy app.
Notify patients that something new is ready and link to the results inbox behind sign-in.
Let users share specific workouts or achievements with friends via deep links.
Share challenge links that carry the inviter's ID to your app. Your app tracks the referral.
Link directly to virtual visit waiting rooms from appointment notifications.
Health is where the convenience of a link and the privacy of a patient pull hardest against each other. Every setup below follows one rule: a link names a screen, and nothing about the person opening it.
https://care.example.com/nextappointmentUse the same link for every patient. After sign-in, the app looks up that person's next appointment and opens check-in. The URL contains no appointment ID, date, clinic specialty, or name, so it says nothing about the appointment if the message is forwarded or seen on a lock screen.
https://care.example.com/latestresultsSay that something new is ready, and name no test in the message or the link. The app requires sign-in or biometrics, then shows the newest result. The web fallback should be your patient portal login page, never a page with content on it.
https://fit.example.com/hillsprints20?ref=coach_amyA shared workout is not a medical record, so each workout can have its own link, and with query passthrough on, the coach can be appended to it. A social preview shows the workout title in the chat, and on paid plans deferred deep linking can keep the workout through a first install. The same goes for a QR code on a gym poster or a clinic front desk that names only a location.
Names, dates of birth, record numbers, conditions, and medications. Watch for indirect details too: a slug like /oncologyfollowup tells a reader something. Links pass through SMS carriers, mail gateways, and browser history. Ulinkly's click records store the IP address, user agent, approximate location, and referrer, and can include the link URL and values appended to it.
Mail security systems often open links automatically. If opening a link confirms or cancels an appointment, a scanner can do it for the patient. Open a screen with a confirm button instead, and record the decision only when the patient presses it.
On iOS, a click is matched to a first app open using network and device signals, so a family member installing at home can be matched to someone else's link. Use deferred deep linking only to choose a screen that sits behind sign-in, and never to reveal anything.
For someone already signed in to your app, a push notification from your own backend can carry the destination in its payload, so no URL travels through SMS or email at all. Save links for moments when you cannot be sure the app is installed.
Read next: Routing to private content, Understanding short links, URI schemes vs Universal Links security
Send people to the right screen without putting health data in the link.
Get Started Free