[ONBOARD] Azure Health Deidentification
@samvaity is already working on this.
Since Oct 30, 2025.
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 624
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 220
Description
Tracking backlog issue
### Health Tools (New Namespace: `health`) ⚠️
> **Note**: The `health` namespace does not exist yet in the current Azure MCP server implementation.
#### Azure.Health.Deidentification
- [ ] `azmcp-health-deidentification-text-process` - De-identify text containing protected health information (PHI) using HIPAA-compliant methods. This tool removes or masks sensitive health data including names, dates, addresses, and medical identifiers while preserving clinical context. Returns de-identified text with redaction summary. Requires service-name and text-content. - Suggested prompt: "De-identify this medical text: "
- [ ] `azmcp-health-deidentification-job-submit` - Submit batch de-identification jobs for processing multiple documents containing health information. This tool handles large-scale PHI removal from document collections with configurable redaction policies and output formats. Returns job ID and submission status. Requires service-name, source-location, and job-configuration. - Suggested prompt: "Submit a batch de-identification job for documents in "
- [ ] `azmcp-health-deidentification-job-status` - Check status and progress of batch de-identification jobs with detailed processing metrics. This tool monitors job execution providing completion percentage, processing times, and error reports for batch operations. Returns job status as JSON. Requires service-name and job-id. - Suggested prompt: "Check the status of de-identification job "
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.