alfadocs-patient-deep-link

Generate AlfaDocs patient deep links from practice and patient IDs.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alfadocs/ai-harness-instructions --skill alfadocs-patient-deep-link
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alfadocs-patient-deep-link
Source: https://github.com/alfadocs/ai-harness-instructions/tree/main/lovable/skills/alfadocs-patient-deep-link
Command: npx skills add https://github.com/alfadocs/ai-harness-instructions --skill alfadocs-patient-deep-link

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you send users from your app directly into the right AlfaDocs patient record without manual searching, token exposure, or confusing handoffs.

Core Features & Use Cases

  • Patient Record Navigation: Generate AlfaDocs browser links that open a specific patient's show page in the correct practice.
  • Practice-Aware Redirects: Use the practice ID to land users in the right AlfaDocs session with the default archive selected automatically.
  • Common Use Cases: Add an "Open in AlfaDocs" button, link a patient row back to the external chart, or send a user to a specific patient tab such as appointments.
  • Safety Guidance: Build the URL with proper encoding, keep authentication in the backend, and open the link in a new tab so your app stays available.

Quick Start

Create a safe AlfaDocs patient link from the practice ID and patient ID, then render it as an external button that opens in a new tab.

Frequently Asked Questions about alfadocs-patient-deep-link

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deep-link directly to a patient record in AlfaDocs from my app?

To deep-link to an AlfaDocs patient record, you build a browser URL using the specific practice ID and patient ID. This generates a direct redirect into app.alfadocs.com, opening the correct patient show page without manual searching.

Does building AlfaDocs redirect URLs require an Authorization header or archive ID?

Building AlfaDocs redirect URLs does not require an archive ID or Authorization header in the browser link. Authentication must remain in the backend to ensure safe patient chart handoffs without exposing tokens to the client.

How do I add an Open in AlfaDocs button for patient row-level navigation?

To add an Open in AlfaDocs button for row-level navigation, construct the URL-encoded redirect path from the practice and patient identifiers, then render it as an external link that opens in a new tab.

Can I use AlfaDocs patient deep links in a Lovable app for practice-specific redirects?

AlfaDocs patient deep links are specifically designed for Lovable apps requiring practice-specific redirects. They use the practice ID to land users in the correct AlfaDocs session with the default archive selected automatically.

Why does my AlfaDocs patient deep link not open the correct practice session?

If your AlfaDocs patient deep link fails to open the correct practice session, it is likely due to incorrect practice or patient IDs, or improper URL encoding. Ensure the redirect path is properly URL-encoded and both identifiers are accurate.

What is the safest way to handle AlfaDocs browser navigation for patient handoffs?

The safest way to handle AlfaDocs browser navigation for patient handoffs is to open the generated link in a new tab. This keeps your application available while directing the user to the specific AlfaDocs patient show page.