# Care Communication & Consent Map AI Agent Connect

> Care Communication & Consent Map MCP acts as a decision engine for managing sensitive healthcare data disclosures. It uses least-disclosure logic to determine exactly what information can be shared with specific recipients, ensuring your communications stay within legal and ethical boundaries. You can connect it to your AI client to handle complex permission mapping and compliance monitoring.

## Overview
- **Category:** healthcare
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_5mo56kUEhn0QJ2c8JrdOnLuwmKrRYOSEOroXjWn8/ai-agent-connect
- **Tags:** consent, data-privacy, healthcare-tech, compliance-engine, permission-management

## Description

Navigating the overlap between patient privacy and the need for relational transparency is difficult. This MCP handles that complexity by applying strict consent precedence and least-disclosure rules. Instead of guessing who can see what, you let your agent check the specific permissions tied to a patient or subject. 

You can use it to map out exactly which communication methods are allowed for specific people or to pull approved messaging templates that follow role-based guidelines. It also keeps you on track by identifying privacy barriers and calculating when you need to perform your next compliance review. It essentially acts as a guardrail for your AI client, making sure that every piece of information sent or received respects the established consent framework.

## Tools

### calculate_review_schedule
This tool determines the date for the next required compliance review.

### check_restriction_flags
This tool checks if a specific communication is blocked based on the subject and the recipient.

### get_update_templates
This tool provides approved text templates for sending specific information to different roles.

### query_communication_matrix
This tool identifies exactly what information can be shared with a person and which methods are permitted.

## Prompt Examples

**Prompt:** 
```
Who is allowed to receive medical information for patient ID 123?
```

**Response:** 
```
Based on current consents, the following individuals are allowed to receive medical information: Legal Guardian (ID: 456) and Primary Caregiver (ID: 789).
```

**Prompt:** 
```
Generate a message for the Primary Caregiver about the patient's recent checkup.
```

**Response:** 
```
Dear Primary Caregiver, this is an update regarding the patient's recent checkup. The results indicate that all vitals are within normal ranges.
```

**Prompt:** 
```
Is the neighbor allowed to receive emergency contact details?
```

**Response:** 
```
No, the neighbor (ID: 001) does not have permission to receive emergency contact details under the current consent configuration.
```

## Capabilities

### Permission Mapping
Your agent uses this to find out who can receive specific data and how.

### Restriction Checking
The AI checks for privacy barriers before suggesting any communication.

### Template Generation
Your agent pulls pre-approved text to ensure messaging stays within role-based guidelines.

### Compliance Scheduling
The tool calculates when the next review is due to maintain regulatory standards.

## Use Cases

### Verifying Recipient Permissions
Check if a specific family member or contact has the legal right to see a patient's medical updates.

### Standardizing Care Updates
Use approved templates to send consistent, role-appropriate messages to primary caregivers.

### Compliance Auditing
Monitor the review schedule to ensure all consent permissions are up to date.

### Preventing Data Leaks
Identify restriction flags to stop unauthorized information from being shared with non-authorized parties.

## Benefits

- Enforces least-disclosure rules to prevent unauthorized data sharing.
- Uses role-based templates to keep messaging consistent and compliant.
- Automates the calculation of required compliance review dates.
- Identifies privacy restrictions before any communication is sent.

## How It Works

Connecting this MCP to your AI client gives your agent immediate access to your consent and communication rules.

1. Connect the MCP to your preferred client like Claude or Cursor via Vinkius.
2. Ask your agent to check permissions for a specific patient or recipient.
3. The agent queries the communication matrix to find allowed data and methods.
4. The agent uses restriction flags to confirm no privacy rules are being broken.
5. The agent generates or sends the approved communication using the provided templates.

## Frequently Asked Questions

**What does this MCP do?**
It acts as a decision engine for managing healthcare privacy and communication permissions. It helps determine what information can be shared with specific people based on consent rules.

**How does it handle privacy?**
The MCP uses least-disclosure rules and explicit consent precedence. It checks restriction flags to ensure no unauthorized data is shared.

**Which AI clients can use this?**
You can use this with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

**Can it help with messaging?**
Yes, it provides approved text templates for communicating specific information to different roles.

**Does it manage compliance?**
It helps with compliance by calculating required review schedules to ensure permissions remain valid.

**How does the system handle conflicting permissions?**
The system follows the Explicit Consent Precedence rule: if a person has explicitly denied permission for a specific category, that denial overrides any general permission.

**What is the 'Least-Disclosure Rule'?**
In the absence of explicit permission, the system defaults to the most restrictive state. Information is only shared if there is a clear, valid permission associated with the recipient.

**Can I check if a specific person is blocked from receiving data?**
Yes, you can use the `check_restriction_flags` tool to identify privacy barriers or 'No-Go' zones for a specific subject and recipient.