Jeremy Wight

This made me chuckle. And I’m super fortunate that my Dev partners are active participants in the feature design and definition, so in my experience this really applies to the entire team, not just the Dev team. We’ve all underestimated the complexity of features, but this is why a good UX/UI team is so helpful! That research is invaluable! Some things we’ve done to get feedback: - monitor those logs…daily! - watch for drop-offs at unexpected points of the flow - solid research going into the feature - prototyping!! - A/B testing - exit surveys What else do you do to gather feedback? #digital #productmanagement #product #productleadership #UX #UI

20

2 Comments

One of the most underrated aspects of using an #interoperability tool like Metriport is not needing to know where the patient has received care previously 👇 While this may be obvious to providers who have leveraged Health Information Exchanges (HIEs) before, the reality is that so many providers today still need to ask their patient where they’ve received treatment previously (assuming the patient remembers them all), and then needs to call each facility and beg them to send over the records via #fax. This process can take days, if not weeks, and often still results in the provider having an incomplete, partial understanding of their patient's medical history 🤷‍♂️ Through #HIEs, a provider who leverages Metriport simply needs to enter the basic demographic info of their patient (name, DOB, gender, and address) to pull records from all the facilities where their patient has received care previously. Metriport handles this entire process in seconds, without any humans in the loop. This is by far one of the biggest “aha” moments for providers who use Metriport for the first time, after being reliant on manual retrieval methods previously. From initial skepticism, to providers who now can’t live without this, we see these tools as an inevitable part of evolution of modern #healthcare workflows.

25

2 Comments

Somewhat predictably, the headlines of Epic's UGM were mostly focused on AI. In my mind, the ones to focus on got buried as footnotes. Products leveraging Epic's position as the dominant inpatient EHR and selling differentiated products as a wedge into new markets (mostly under Health Grid) should frighten other healthcare vendors more than the AI arms race (which they'll largely win as the default option): - Payer Platform: A Health Grid product for payers. This was decently well covered, but that's because it's a mature product at this point. A lot of outlets covered it as if it was net new, but it was launched in 2019. The most noteworthy piece is Judy's quote saying they’re investigating submitting claims directly through Epic so you don’t need a clearinghouse - this represents a threat to clearinghouses and could represent the expansion from Payer Platform as a beachhead to attack incumbent SaaS, claims processing systems. - Epic Aura (labs): This is a Health Grid product for labs. This was launched previously. I don't see any announcements, but this is a beachhead for Epic to sell to labs that have or built their own LIS, allowing them to eventually replace it over time (or at least have all major labs as customers). This threatens existing LISes even more than Epic's LIS product, Beaker. They also announced a planned Blood Bank module, which increases their appeal as an all-encompassing LIS in this push. - Epic Aura (medical devices): A new sub-category of Aura (and Health Grid) for expanding into medical devices. I was waiting to see if they'd launch a separate category for medical devices or reuse Aura. First devices are cardiac arrhythmia and CGM. This threatens businesses like Redox to some degree. - Per Healthcare IT today, "Judy said they’re working on better surgical device manufacture planning leveraging the Epic schedule." This sounds like further expansion of Aura/Health Grid to surgical supply manufacturers. - I was surprised to not hear any updates about Discovery, Epic's Health Grid program for pharma. I'm curious what shape that will take. - I thought the use of the state of Washington + the Garden Plot model is a smart distribution play. Garden Plot has existed since at least 2022, but using a state for distribution to get to new markets that Epic struggles to sell to (small clinics, behavioral health clinics, correctional medical facilities and tribal facilities) is again another example of their expansionary mode. Health Grid products will be more impactful than the Vendor Services rat races or AI wars. It's worth paying attention to and taking advantage of: https://lnkd.in/gimisDzZ

56

13 Comments

Every time a company faces financial trouble and budget cuts, the first department to experience layoffs is often the QA team or personnel. As a result, basic boundary conditions go untested, leading to a loss of end-user confidence in the product. This is a picture of my car's dashboard at around 7:30 AM. This brand (I'll refrain from naming it) likely did the same thing—let go of QA and dumped all the responsibilities on the already busy developers, telling them, "We need you to design the UI, develop, and test your own product." And here’s the result:

8

1 Comment

A health system asked if I could share what SeamlessMD’s secret sauce was for engaging patients… so I’ve decided to open source my response here. They wanted to know what principles and success factors have enabled our customer partners to achieve industry-leading results like: ⬇️ Cost of care by $1,000+ per patient ⬆️ Increased net profit of $1,000+ per patient ⬇️ 1 to 2 days length of stay ⬇️ 89% readmissions reduction by up to 89% ⬇️ 68% ED visit reduction by up to 68% ⬇️ 89% mortality ⬇️ 65% phone calls to providers Here are the main principles and success factors I shared: 1️⃣ It starts with a high touch partnership to ensure success. The People + Process we assign to a health system partnership matter even more than the Technology 2️⃣ Clinical expertise applied to the product matters more than Tech features. Our product’s secret sauce is our world class, pre-built care plan content. 3️⃣ Key elements of our care plan content that drive high patient engagement include: - Brand personalization - Condition-specific patient experiences - Personalization to a patient’s demographics & comorbidities - Condition-specific health status & symptom tracking - Automated self-care guidance for 80%+ of patient issues 4️⃣ Obsession with patient accessibility further optimizes patient engagement. - Gr. 6 reading level - Colour-blind tested - Screenreader friendly - WCAG 2.0 Level AA requirements met and more 5️⃣ Digital care plan implementation is Clinical Change Management. A successful implementation requires a proven playbook and hands-on expertise for: - Achieving care pathway standardization and alignment - while being efficient with clinician time commitment - Embedding digital care journeys into the clinical workflow: What workflows make the most sense for receiving alerts and monitoring dashboards given our limited staff resources? - Having the clinical acumen to going deep into the nitty gritty clinical workflows. E.g. for a pregnancy care journey - how will our solution know if there is an infant loss? How should the care plan change in that case? 6️⃣ Clinicians must be engaged to have a sense of ownership so they promote it to patients We’ve figured ou the optimal time commitment that ensures all clinicians are engaged during implementation (hint: physicians have very limited time!) 7️⃣ Let busy clinicians act as the Editors of Clinical Content. By having a clinical Patient Education team act as proactive Ghost Writers. - The key principles are to (1) earn clinician trust and (2) reduce friction to clinician engagement. 8️⃣ The ideal approach to patient enrollment varies from health system to health system. Sometimes a hybrid approach might even be needed 9️⃣ You must believe that the job’s not done until you achieve business outcomes. We obsess over the data and push our partners to measure ROI. More details in the slides below 👇 *** I’m curious: Which of these resonated most?

40

7 Comments

Stop calling it technical debt. We’re not fixing old code - we’re investing in our platform's future. As product leaders, we often struggle to get buy-in for these critical improvements because we're telling the wrong story. Here's what transformed our customer conversations: Instead of talking about refactoring legacy systems, we shared how we're strengthening our foundation to unlock new possibilities. Rather than discussing system complexity, we focused on how our platform investments directly improve reliability and speed. The magic happened when we stopped apologizing for maintenance and started showcasing the long-term vision. Our customers don't care about our code - they care about growing their business, staying competitive, and reducing risks. The key is simple - translate technical challenges into business opportunities. Customers want to hear about outcomes, not operations. #ProductLeadership #TechnicalStrategy #CustomerSuccess #ProductManagement

9

2024 was a big year for Flexpa. Writing it all down in one place was hard - there was too much to cover! But I tried. The big 4: 1⃣️ 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗘𝘅𝗽𝗮𝗻𝘀𝗶𝗼𝗻: We hit 85%+ CMS lives coverage and rolled out the largest network of payer FHIR endpoints in the industry. We support patient-consented claims data for over 215 million people. 2⃣️ 𝗖𝗼𝗻𝘀𝗲𝗻𝘁 𝗜𝗺𝗽𝗿𝗼𝘃𝗲𝗺𝗲𝗻𝘁𝘀: From the new Multiple Use tier to 24-hour access token expirations—our transparent, user-friendly authorization flows put patients in control. 3⃣️ 𝗥𝗲𝗰𝗼𝗿𝗱 𝗣𝗿𝗼𝗰𝗲𝘀𝘀𝗶𝗻𝗴 𝗮𝘁 𝗦𝗰𝗮𝗹𝗲: We processed over 50 million FHIR Resources with 95% of consented data transfers completed in less than 60 seconds, plus added advanced Resource filtering and data standardization. 4⃣️ 𝗔 𝗟𝗼𝗼𝗸 𝗔𝗵𝗲𝗮𝗱: Payer-to-Payer data exchange, new HL7 working group contributions, and even more secure data-sharing—2025 is going to be big! Read the rest: https://lnkd.in/gwrye5Fm A huge thanks to everyone who contributed to our success this year, from our customers to interoperability partners - and especially everyone on the team: Claudio Carbajal III, Amanda McGivern, Angela Liu, Dylan Klein, Larry Ditton, Kyle Tilman, and of course my co-founders Tom Hamilton and Andrew Arruda.

33

2 Comments

✨ A lesson in writing clear requirements… with a little Friday humor! ✨ Picture this… You’re on a cross-functional product team—whether as a product manager, designer, software developer, or QA engineer—and it’s your job to communicate exactly what needs to be built. Your colleague depends on your instructions to successfully create the end product. Sounds easy, right? Well, not always. Clear requirements can make or break whether a product solves the intended problem. But what does clear really mean? A recent video gave me a funny reminder of this: A dad challenged his kids to write down instructions on how to make a peanut butter and jelly sandwich, and he followed their instructions EXACTLY—with not so exact results 😂. After a few rounds of trial and error, the kids finally got better at explaining, and voila! A successful sandwich. It’s just like product development. Requirements need to be clear, complete, and delivered in a way that your team can follow without missteps. Along the product development lifecycle, you’ll come across several requirement types, such as: ✨ Business Requirements: Why are we doing this? What value are we creating? ✨ User Requirements: What do users want or need to accomplish? ✨ Functional Requirements: How will we implement these features? ✨ Design Requirements/Specifications: How should it look, feel, and behave? ✨ Technical Requirements: What infrastructure is required (databases, APIs, etc.)? And, as the video hilariously reminds us... ✨ Testing Requirements (a.k.a Test Cases): How do we verify that we built what we set out to build? Each one is crucial. Each one can either launch or derail a product. Throughout my career—whether as a research leader, product leader, or now CTO—I’ve had to write (and refine!) requirements of all kinds. It’s truly an essential skill for any PM to master. So… what do you think? Can you tell me how to make a PB&J? 🍞🥜🍇 #productmanagement #productdevelopment #fridayhumor #innovation #thoughtleadership

14

3 Comments

I'm not sure if 10 years and lots of medical school debt is effective, but the system does create doctors. Are they all good no? What do you call the person who graduates last in their medical school class? Doctor. Graham McMahon champions GenAI's potential as a collaborator. The commenters do, for the most part, as well. I love the call out that docs and other professionals are human. Humans make mistakes. Humans are not perfect. AI should be Augmented Intelligence! How do we use GenAI to be better? Play with it. Use it. Understand how to use it effectively. Hint: not a search engine. #digitalhealth #genai #doctors #medicine

3

🌟Collaboration Alert! 🌟 Great news for everyone in healthcare operations using ModMed's EHR system: Voiceoc has officially joined the ModMed marketplace! 🌟 Explore more here: https://lnkd.in/gJB_4U7h Voiceoc helps medical practices cut down support costs & boost patient experience by automating front desk calls for appointments, refills, queries, support etc. Imagine This: All incoming calls handled by AI 24x7 with no patient wait time and no voicemails. You can dedicate more time to take care of your patients. 💜 By joining forces, we can now offer healthcare providers and their patients an improved experience through effortless integration into your workflows, boosting both efficiency and accessibility. 🤝 Interested in learning how Voiceoc can help you automate calls by integrating with ModMed, DM me now! #HealthcareInnovation #AIinHealthcare #ModMedMarketplace #Voiceoc #Automation #PatientCare #HealthcareEfficiency

13

3 Comments

When I first started in healthcare in the mid-2000s, organizations were still transitioning from paper charts to computerized charts (reluctantly, I might add). Very quickly, templates for progress notes and treatment plans followed, creating cookie-cutter documentation that insurance companies and accreditation bodies disliked. They wanted individualized documentation that was clearly focused on the patient. AI offers the potential to continue cookie-cutter documentation or do something better. AI can understand more nuance about the patient and ensure the documentation is tailored to the specific person being treated, instead of a template that fits them based on their generic presenting problems. It will take a great team working in conjunction with industry experts to create the best results. The quick and easy AI solutions will be no better than the templates being used for the last 20 years. We're focused on creating something better. #SigmundSoftware

29

2 Comments

It's the final week to sign up for the EHR 101 course!!! Phil Ballentine, MSc has really put together a master class on everything you need to understand electronic health records and how to analyze the data that's in them. - What's the deal with data lag? - How do you deal with the lack of standardization in things like medication names? - What're the different formats you can get the data out? - Common pitfalls when analyzing the data, how to address them, and real-world examples of data analysis If you touch EHR data in some capacity, this is going to shorten your learning time from a year of pain to 2 weeks. You can sign up for it here: https://lnkd.in/e8wia3QV

12

1 Comment

I consistently hear from my contacts in the medical field that they *hate* the EMR/EHR systems they are forced to use. "I wish it did this..." or "why doesn't it do that..." or "why is it so hard to do this..." and so on and so on. Especially when it comes to charting. Nurses, doctors, etc spend a tremendous amount of time charting on patients... not just because they *should* or because accurate notes and observations are critical to patient care, but because the sad reality is they need to cover their butts for legal reasons, state audits, etc. However, I've witnessed first-hand the chaotic high-stress nature of what nursing staff have to deal with on the daily and *time* is often a problem. I've seen these people spend *hours* at the end of their shift charting or even charting after hours, off-the-clock, etc just to try and catch up. After all, their licenses are on the line. A lot of these systems are so monolithic, complex, and cumbersome... it's amazing anyone gets anything done at all. As an engineer, my gut reaction was: I can build something better. My wife practically begged me: "PLEASE build something better. I can help. I can tell you everything that sucks about all these systems." But then I was smacked with reality: Most of these companies and institutions spend a ton of time and money on the systems they have in place and are typically reluctant to pry themselves away from these systems. It's too hard. Too expensive. Too time consuming. Luckily, there are new add-on systems to simplify these kinds of things, but I still feel like building a more modular, simpler system with stellar integration support and data import/export facilities, and a cleaner easier UI and voice dictation support would be ideal. But I'm also one man with limited time and resources. I often wonder how much innovation has been stifled under these same circumstances. I'm certain the list is long. And that is a shame.

11

1 Comment

🌟 Being Unrealistic is the Key to Unlocking Innovation 🌟 Yes, you heard me right. After leading commercial, product, and partnership innovation, strategy, and GTM for virtual care, navigation, wellness, and DtX solutions in the complex U.S. healthcare landscape, I have often heard the mantra: “Be realistic.” This advice is usually rooted in concerns about feasibility—whether due to technical, regulatory, compliance, resource, or budgetary constraints. On the surface, it seems like sound guidance, offering a safe and logical path. Right? 🚫 I say no. Let’s challenge the notion of being “realistic.” Stay with me now… What if being “realistic” is the very thing that holds us back? True innovation demands pushing boundaries, challenging the status quo, and sometimes, outright ignoring the constraints that bind us. 📉 Consider Blockbuster, a company that played it safe by sticking to its traditional brick-and-mortar rental model while ignoring the digital revolution. Their reluctance to innovate and adapt to changing technology led to their downfall, proving that playing it safe is not always the logical choice. On the other hand, consider the story of CirrusMD • 🗨️ We launched a chat-based virtual care solution before chat was even a thing, much less in healthcare. • 🛠️ We faced numerous technical and regulatory hurdles, but we didn’t settle for what was deemed “realistic.” Instead, we adopted a mindset of relentless problem-solving, refusing to let constraints dictate our vision. • 🌐 Today, CirrusMD serves over 10 million members, boasts a patient satisfaction rate of 96% and delivers a remarkable ROI of 3:1. But wait. We haven’t stopped innovating. Recently, we launched the Physicians-First Care & Guidance program, which uniquely combines the expertise of physicians with personalized care pathways to guide patients through their healthcare journeys. This model improves access and speed to care for patients, reduces time and information barriers for physicians, brings patient data into the care encounter, and promotes cost and quality transparency at the point of referral. 💹 Oh, and offers up to 6:1 ROI for our customers. If we’d been realistic, we’d have missed out on groundbreaking opportunities. By forcing ourselves to find solutions to constraints rather than being confined by them, we continue to open the door to true innovation. Let’s embrace the challenges and dare to dream beyond what’s “realistic.” 💬 What are your thoughts? How do you balance feasibility with the need to push boundaries in your own projects? #healthcareinnovation #virtualcare #primarycare #carenavigation #patientexperience

9

2 years ago, I signed my biggest client in healthcare software development. I quickly learned that the 'Minimum Viable Product' (MVP) approach can be a dangerous myth in this field. Here's why: Patient Safety Isn't Negotiable → Healthcare software must be reliable from day one. → An MVP that 'just works' isn't enough. → Bugs and glitches can lead to realworld harm. Regulatory Hurdles → Healthcare is heavily regulated. → An MVP that doesn't meet compliance standards can cost you more than just money. → It can delay product launch by months or even years. Trust and Credibility → Healthcare providers need to trust your software. → Releasing a barebones MVP can destroy that trust. → It’s hard to rebuild once shattered. Integration Complexity → Healthcare systems are complex and multifaceted. → An MVP that doesn’t integrate well can cause more problems than it solves. Longterm Vision → An MVP is often a shortterm solution. → Healthcare software requires a longterm vision. → Planning for scalability and sustainability from the start is crucial. So, what’s the alternative? → A Minimum Lovable Product (MLP) Focus on creating a product that not only meets but exceeds expectations. → Ensure it’s safe, compliant, and reliable. → Invest in thorough testing and user feedback. Healthcare is not just another industry. → It’s about improving lives and saving them. Don’t risk it with shortcuts. What are your thoughts? Have you experienced the downsides of the MVP approach in healthcare? Share your stories and let's discuss!

17

3 Comments

When it comes to design debt in HealthTech, it's tempting to push it aside. You’ve already got complexity, compliance and deadlines to contend with. But you’ve probably seen these symptoms: • Inconsistent UI elements and design. • Confusing, poorly structured navigation. • Cluttered, overcrowded interfaces. • Redundant features causing confusion. • Vague, unhelpful error messages. • Inconsistent user flows and experiences. • Outdated visuals misaligned with branding. • Hidden, hard-to-find features. • Inconsistent accessibility and mobile support. • Unclear AI explanations causing mistrust. Ignoring design debt isn't just risky, it's a ticking time bomb. Like a small leak in your roof—it’ll only get worse (and more expensive to fix). The best way to manage it? Treat every decision as if a life depends on it—because sometimes with medical software and healthcare apps, it does. #DesignDebt #HealthTech #UXDesign #UserExperience #DesignChallenges #HealthcareDesign #UIUX #DesignThinking #DesignStrategy

19

3 Comments

A leading EHR provider came to us with a UX challenge: ↳ Providers were struggling with real-time documentation during patient interactions ↳ Inconsistent medical records were affecting both patient care and operational efficiency ↳ Their existing AI scribe feature wasn’t generating the traction that they’d hoped They wanted to review the way users interacted with AI features to enhance adoption. 𝗧𝗵𝗲𝗶𝗿 𝗴𝗼𝗮𝗹𝘀 𝘄𝗲𝗿𝗲 𝗰𝗹𝗲𝗮𝗿: > Improve real-time documentation while ensuring patient care wasn’t compromised > Build trust in AI-generated notes while maintaining full control for providers > Seamlessly integrate AI into existing workflows to enhance efficiency without disruption 𝗛𝗲𝗿𝗲’𝘀 𝗵𝗼𝘄 𝘄𝗲 𝗺𝗮𝗱𝗲 𝗶𝘁 𝗵𝗮𝗽𝗽𝗲𝗻: - We designed a UX that emphasized trust and transparency, ensuring providers could rely on the AI: - Clear indicators showed when AI generated notes, along with confidence scores for verification - A jump-to-conversation feature allowed providers to easily cross-check AI summaries with patient interactions - An intuitive editing process enabled quick toggling between AI-generated notes, raw transcriptions, and patient records - Contextual referencing tools were integrated, providing access to relevant past notes without interrupting workflow - Fail-safes ensured manual note-taking was always available if the AI was unavailable 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁? ✓ Significant improvement in documentation accuracy ✓ Increased provider confidence in AI-generated content and higher adoption rates ✓ A hybrid workflow that streamlined efficiency while maintaining high-quality care Interested in learning how we can help you design AI-powered solutions your team can trust?

34

4 Comments

Healthcare interoperability has a long way to go

4

Product is fun, complex, messy, and there are no shortcuts. Once you accept that—and embrace it—amazing things happen to your career. Cat Hicks, PhD puts this better than anyone: "Doing research with developer teams, something that really strikes me is how much people look for ways to make complex problems easy rather than make it easy to work on complex problems What I mean is, sometimes it's really useful to admit we just are trying to accomplish tough things. Asking how we can support our teams who NEED the time and space to work through that, it's often a much more tractable lever than trying to change the inherent nature of the work I think it behooves me to say as a psychologist here that I think people are actually really excellent at working on complex problems! It's one of the reasons research with developers is so great. Overall devs love to learn, love to be curious, love to innovate. It is core stuff. What would it look like if we could ask, "how do I make this the absolute best environment for complex problem-solving" instead of "how do I take away all these annoying hard problems." The stuff we want to accomplish in the world is hard. But can be joyful to accomplish."

250

14 Comments