A fight that began quietly in December has turned into one of the most closely watched privacy disputes in the federal benefits world. The Office of Personnel Management wants far more detailed health claims data on the roughly 8 million people covered by the Federal Employees Health Benefits (FEHB) and Postal Service Health Benefits (PSHB) programs. Lawmakers, unions, and retiree groups say the plan is legally shaky and dangerously broad. OPM says it’s the only way to finally get serious about fraud that has been draining the program for years. Both sides have now put their arguments on the record — and the gap between them is narrower than it was in the spring, but still real.
Takeaways
- What’s changing: OPM finalized a rule (effective June 23, 2026) expanding the health claims data it collects from FEHB and PSHB insurance carriers — including more detailed prescription, provider, and billing codes.
- Why OPM says it needs this: To catch healthcare fraud, waste, and billing abuse in something closer to real time, rather than years after the fact.
- How your identity is supposed to be protected: OPM says direct identifiers (name, SSN, address) are stripped before it receives the data, and your Member ID is scrambled through a hashing process before analysts use it.
- The catch: OPM acknowledges it retains the technical ability to reverse that scrambling and re-identify records for certain “operational” purposes — which is different from data being permanently de-identified.
- Who’s pushing back: NARFE, AFGE, and congressional Democrats say pseudonymized data isn’t the same privacy guarantee as true de-identification under HIPAA, and want firmer, binding commitments from OPM.
- What hasn’t happened: Your individual medical records are not being reviewed one-by-one by OPM staff. The stated goal is pattern-level fraud analysis, not case-by-case review.
- What’s next: The public comment period on the rule closed July 23, 2026. Whether OPM tightens its privacy commitments further, or Congress intervenes, remains unresolved.
Add your first comment to this post