1. Data Intake (The Provider Interface)

• Action: The mental health professional visits S.A.F.E. Triage for privacy1.co. They input the patient’s triage data (Safety, Location, Denial Reason, Financial Status) along with the patient’s contact and verification details.

• Security Context: The data is encrypted in transit as it travels directly from your site into your secure, HIPAA-compliant Google Workspace.

2. The Automation Hub (Google Apps Script)

The moment the provider hits “Submit,” Google Sheets triggers our core background logic engine. It processes the submission through two strict rule pathways:

• Rule A (Crisis Route): If an active crisis is flagged, the script completely bypasses the resource matching table. It instantly drafts and fires a standardized text/email containing 988 and Crisis Text Line instructions directly to the patient’s contact.

• Rule B (Standard Matching Route): If the patient is safe, the script evaluates the matching criteria (State, Reason, and Financial Status) against your Resource_Directory tab.

3. Secure Link Creation & Ledger Logging

• Token Generation: If a match is found during the Step 2 check, the system creates a highly secure, randomized cryptographic token (UUID).

• Ledger Recording: The token is tied to the patient’s specific Last Name, Date of Birth, and the text of their Matched Resource. This is logged inside a private, backend database tab named Active_Links with a mandatory 48-hour expiration timestamp.

• Patient Delivery: The system emails the patient. To maintain strict PHI privacy compliance, no medical or facility details are written in the email itself. The email only contains a generic notification and their unique access URL string (.../exec?id=UNIQUE_TOKEN).

4. The Patient Gate (Web App Portal)

• Server-Side Capture: When the patient clicks the link, Google’s server strips the tracking token from the URL and securely injects it into a hidden element on a clean Web App interface (Index.html).

• Identity Challenge: The webpage forces the patient to enter their Last Name and Date of Birth.

• The Unmasking: The page sends those entries back to the spreadsheet ledger. If they perfectly match the token’s logged credentials and the link hasn’t expired, the secure portal unmasks and prints the matching facility’s contact details on the screen.