David Kerr

🧬 We talk about “health data” as if it’s one thing, but it’s really hundreds of incompatible languages trying (and failing) to talk to each other. Every layer speaks a different dialect: • EHRs: HL7 v2, CDA, FHIR • Claims: X12 837, UB-04, CMS-1500 • Labs: LOINC, SNOMED CT • Devices: DICOM, IEEE 11073 • Genomics: VCF, FASTQ, BAM Each was built for a single purpose, not interoperability. The result? 🚑 A patient’s data is scattered across 40+ systems, each with its own schema, timestamps, and access controls. But things are shifting. Newer models are moving beyond formats to: • Graph-based data structures • Semantic layers • Federated architectures These approaches preserve context, not just content, across systems. FHIR paved the road. But the next frontier is semantic interoperability. That’s not just data exchange; it’s data understanding. 🧠 The future of healthcare intelligence isn’t in collecting more data, it’s in connecting meaning. #HealthTech #DataInteroperability #FHIR #HealthcareAI #KnowledgeGraphs #SemanticWeb

146

15 Comments

The most important software in healthcare isn’t Epic, it’s Excel. As impressive as AI is, it’s equally impressive to see billion dollar companies run on XLSX files. A few highlights: 👉 Modeling contract carve-outs, multiple-procedure discounts, outlier payments in Excel - deeply impressive formulas 👉 Excel for forensic accounting: 3-way-match of contract rates, allowed amounts, paid amounts 👉 And of course using Excel to project manage an EHR migration So when we built PayerPrice, we did so recognizing that Excel is both everyone’s favorite data tool, and that “Excel hell” exists. Very few of our customers want to learn a new tool, all of them want to answer questions as quickly as possible. Usually that happens in our application, very often it happens in Excel, and maybe soon it’ll always happen in our forthcoming AI agent ;)  And what are your thoughts on the excel language?

21

3 Comments

Colorado just introduced a bill to require operating systems to provide age verification to apps.  Bill Summary: SB26-051 introduces new requirements for OS providers and application developers regarding the collection and handling of user age data on computing devices. This could reduce the number of random sites that need to collect highly-personal information like your driver’s license or passport just to verify your age. Question will be whether it is robust enough to prevent manipulation. Requirements for Operating System Providers: Age Verification Interface: Must provide an interface during account setup that requires the account holder to input the user's birth date or age. This data is used to generate an "age signal" (indicating the user's age bracket) for apps downloaded from a covered application store. API for Developers: Must provide a real-time Application Programming Interface (API) that allows app developers to request and receive this age signal. Data Privacy: Must only send the minimum amount of information necessary to comply with the bill and are prohibited from sharing the age signal with third parties for any unrelated purposes. Requirements for Application Developers: Mandatory Age Request: Must request a user's age signal from the OS provider or app store when their application is downloaded and launched. Assumption of Knowledge: Once an age signal is received, the developer is legally deemed to know the user's age range across all platforms of that application. (However, if the developer has "clear and convincing" information indicating a different age, they must use that information instead). Data Privacy: Cannot request more information than strictly necessary and are prohibited from sharing the age signal with third parties for unrequired purposes. Penalties for Violations: Enforcement is handled by the attorney general through civil actions. Violators face civil penalties of up to: $2,500 for each minor affected by a negligent violation. $7,500 for each minor affected by an intentional violation. #privacy #colorado #appdevs #developers #software #Windows #MacOS

2

8 Comments

The Cost of Compliance Failure in Healthcare & Other Regulated Industries Compliance isn’t paperwork. It’s risk management at executive level. When it fails, the impact is never small. Under HIPAA and General Data Protection Regulation, fines can reach millions. But the real damage is operational shutdowns, ransomware exposure, lost patient trust, and board-level scrutiny. In regulated industries, “the IT team handles it” is no longer acceptable. If your architecture doesn’t include: • Clear data ownership • Role-based access controls • Encryption & monitoring • Documented audit trails You don’t have compliance. You have liability. After 22+ years in healthcare and regulated environments, I’ve learned this: • Digital transformation without governance is reckless. • AI without data control is dangerous. The modern CIO/CTO isn’t just driving innovation. They are designing resilience. Compliance done right doesn’t slow growth. It protects it. #CIO #CTO #HealthcareIT #CyberSecurity #DataGovernance #HIPAA #GDPR

5

If there was ever a record scratch moment: “…if enacted, [the bill] would ban states from enforcing laws regulating artificial intelligence for 10 years.” This is troubling - we are one step closer to facing a decade of unchecked AI the state and federal levels while threats to individual privacy, identity, security, and ethics continue to grow. That means big tech can develop with reckless abandon, companies (and the government) can use AI and data however they choose, and individuals will have fewer options to protect themselves in an environment that is already inadequate. This will be challenged in the Senate, and if it passes, I expect states to respond legally. None of this means companies can’t lead their own initiatives to govern the use of data and AI. Responsible AI practices should become a cornerstone of business and technology strategies. Maybe you’re just getting started and don’t know where to begin. Or you might be interested in optimizing or right-sizing your existing program. Now is the time to review your strategy around governance to make sure you’re developing, acquiring, and using AI responsibly and ethically. #responsibleai #aiethics #aigovernance #datagovernance

10

1 Comment

22.65M people notified in the Aflac breach—this isn’t just “oops, a spreadsheet leaked.” It’s the full identity puzzle box: SSNs, driver’s licenses, passports/state IDs, DOBs, addresses… plus medical + health insurance data. That combo is basically fraud on hard mode—*for victims*, not criminals. What to be concerned about: - **Longevity of risk:** SSNs and ID numbers don’t “reset” like passwords. - **Medical identity theft:** claims, prescriptions, and benefits abuse can trail you for years. - **Industry-wide targeting:** filings suggest a **known cybercriminal group** aiming at insurers broadly—think repeatable playbooks, not one-off luck. - **Notification lag = attacker head start:** when scale is this large, “time-to-notify” matters. Worth a read: https://lnkd.in/gBDP-weX #cybersecurity #databreach #infosec #privacy #identitytheft #healthcaresecurity #insurance #riskmanagement #cybercrime Security is a streak you can’t afford to break.

8

2 Comments