MyLigo

At the last Internet Identity Workshop, I announced my talk: “5yrs ago at this conference, Trinsic launched our self-sovereign identity platform. Today, I’m hosting a session called “SSI didn’t work. Trinsic is pivoting.” Since then it’s been a whirlwind helping customers improve their IDV flows through Identity Acceptance—accepting a digital ID (like mobile driver's license) instead of uploaded photos of physical IDs. Only recently, during a couple of 2am - 5am shifts with a newborn baby, did I get around to following up on that IIW talk. ?? Many people asked me to turn that presentation into a blog post, so here it is! The intent of the post is simple. I’m no longer betting on interoperable digital credentials taking off. This post articulates why. Specifically, interoperable, standards-based digital credentials like verifiable credentials (and its variants) face three impossible* problems that block adoption: Interoperability vs innovation catch-22 UX?always?worse initially Scattered heat map I dive into each of these problems in depth in this post. If someone can crack these, they’ll quickly be a millionaire. Obviously, there are hundreds of organizations that ostensibly want interoperable digital credentials. But despite all this spend and attention, have failed to adopt. If these problems are solved, I think adoption can occur and the enablers can succeed wildly. *While I term these "impossible problems", I hope I'm proven wrong. This post is my call for others to pick up the baton and run with it, not from the starting line, but with hard-earned lessons behind them. There are probably only 100 people on earth that care enough about this topic to read the whole post & apply the content. But if you’re one of those, I’d love to hear your feedback & keep the discussion going! Big thanks to Kim Hamilton Duffy Timothy Ruff Gerald Glickman Eve Maler David Grantham James Monaghan and Zachary Jones for giving feedback on a draft of this post ?? https://lnkd.in/g7KkY656

This cartoon is funny. And also a bit sad. Sometimes, confirming patients' birth dates makes sense. But often, we do it for no good reason. It seems trivial, but repeatedly asking these sorts of questions and documenting the answers takes a toll. Watch an admin scheduling an appointment, a front desk staff member checking someone in, a nurse "rooming" a patient, or a resident writing an admission note. Healthcare generates approximately 30% of the world's data. Most of it is useless. Much of it is redundant. EHRs were supposed to make healthcare better. And in many obvious and under-appreciated ways, they have. Yet, by making it so easy to collect data, healthcare workers have been forced to collect, confirm, and enter more and more of it. AI could ease this burden. Or, by making it even easier to collect and generate data, it could paradoxically worsen it. We need more restraint. Just because something seems so easy to do doesn't mean we should repeatedly do it.

If you or your team is just starting out on working with EHR #data, you can benefit from the past knowledge generated by folks who have spent decades and years banging their heads against it.... you *don't* have to hit every pothole yourself. ?? This snippet is from a conference held in 1966 in Denmark that included physicians and researchers from the world's most established hospitals. They point out a common pitfall of pooling data from multiple institutions which is **almost exactly the same today as it was nearly 60 years ago.** ?? Many patients see multiple providers at multiple facilities using different EHRs or different instances of the same #ehr system (Epic, Cerner, etc). You need to resolve these identities to prevent duplication of the same person with >= 2 incomplete records. ?? We'll be talking about this and more in Out-Of-Pocket's EHR Data 101 Course, starting August 13th. We'll have four live sessions in the evenings in Eastern time and learn about using EHR data. I'm distilling many years of experience from me and our guest speakers (7ish for me) in working with EHR data and making sense of its many pitfalls. Check it out! ?? https://lnkd.in/eG4UgaC7 Link to the 1966 conference in the comments.