<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>For on Philterd — Zero-Trust PII Redaction for Cloud and AI</title><link>https://www.philterd.ai/for/</link><description>Recent content in For on Philterd — Zero-Trust PII Redaction for Cloud and AI</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.philterd.ai/for/index.xml" rel="self" type="application/rss+xml"/><item><title>Philter for Integrators &amp; System Builders</title><link>https://www.philterd.ai/for/integrators/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.philterd.ai/for/integrators/</guid><description>&lt;h2 id="common-shapes-of-an-integrator-engagement"&gt;Common shapes of an integrator engagement&lt;/h2&gt;
&lt;p&gt;The bundles we see most often, in roughly the order they show up in proposals:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. Healthcare data-modernization projects.&lt;/strong&gt; A client is moving clinical data into an analytics warehouse, a data lake, or a new application. Somewhere in the spec is &amp;ldquo;PII must be de-identified before it lands in the warehouse.&amp;rdquo; Philter is the de-identification step. The integrator owns the pipeline; Philterd&amp;rsquo;s open source policy library covers the HIPAA Safe Harbor table-stakes; the integrator&amp;rsquo;s clinical-informatics partner validates against a gold-standard sample.&lt;/p&gt;</description></item></channel></rss>