I ran this past an AI reviewer and it asked: "which spec are you pointing to?"…
Original post on LinkedInI ran this past an AI reviewer and it asked: “which spec are you pointing to?” Of course my implicit but intentional answer is “none, yet.” I guess I should explain.
Vendors, left to themselves, have little reason to build something that unbundles a function they currently control. That’s not an indictment; it’s just how market positions work. No one rushes to commoditize their own gate. And so the demand signal that would normally pull a standard into existence never forms.A functional certification requirement changes that equation. It creates the incentive that the market on its own won’t. Customers get a clear thing to expect, vendors get a clear reason to build it (and build it together, by collaborating on an open spec).
Am I thinking about SMART Permission Tickets? Sure, I hope that will be one possibility. But picking a technology today isn’t the point. The goal here is to define the problem space and get the community exploring solutions together.
Josh Mandel, MD (original on LinkedIn):
Thanks Aneesh Chopra for prompting me to think about the kinds of modularity we want in access permissions across the diverse EHRs, PACS, Document Repositories, Genomics Servers, and many other nooks and crannies where clinical data live… here are my thoughts about what a future round of certification might aspire to.