The pMD Blog

Welcome to the
pMD Blog...

where we cover interesting and relevant news, insights, events, and more related to the health care industry and pMD. Most importantly, this blog is a fun, engaging way to learn about developments in an ever-changing field that is heavily influenced by technology.

How to talk to a developer (Part I)
In a small company, developers can’t work in isolation and neither can non-developers. I often find myself discussing a project with a non-developer colleague and am pleasantly surprised when they recognize some software terms I inadvertently used. This made me wonder if sharing a list of common terms developers use may help communication even more. So without further ado, here is part one of a list of terms that might help when conversing with your favorite coder.

Spaghetti Code - Structureless code; like an incoherent essay without proper grammar or flow; a developer’s worst nightmare.

Object Oriented Programming - Code written in terms of objects (ex. User and Document) and their relationships with each other (a User has many Documents); helps avoid spaghetti code.

Null Pointer Exception - The system expected a value to be there, but none was found; usually originates from an unhandled scenario and sometimes leads to a crash.

Refactor - Rewriting code to be cleaner, more robust, and/or better performing; a very gratifying exercise that programmers usually enjoy.

Technical Debt - Compromises made to deliver features in a timely manner at the expense of best practices; the analogy is an accrual of debt that needs to be paid back at some point in the future. Payment can be in the form of horrific catastrophes, or better yet, the time it takes to refactor.

Timing Issue - Technically this refers to unwanted behavior in software arising out of the temporal variance of events, difficult to reproduce and debug; I also use the phrase freely whenever I have no idea what’s going on.

Regression - When a change to the code leads to a previous feature to stop working; the identification of this type of bug is usually preceded a few seconds earlier by the claim that “I haven’t touched that code in months!”
ACA Account Management ACI Advancing Care Information AHCA AHRQ AI Alternative Payment Model Android API Apple Artificial Intelligence Audit BCRA Best Place to Work Big Data bootcamp BPCI BPTW Bundled Payments Care Communities care coordination Care Navigation CDC Charge Capture Charge Capture App Charge Capture Software Charge Capture Solution Charge Capture Statistics Charge Lag CHIP CIO Clinical Communication Clinical Data Registry Clinically integrated network CMS Company Culture Conferences Connected Health Record culture custom reports Customer Interaction customer success customer support Customers cybersecurity Developer DHHS EHR Electronic Charge Capture Encryption epidemic FDA FHIR Flu fundamentals Goals Health Care Health Care Technology Health Care Web Health Information Exchange Health Record Healthcare HIE HIPAA HIPAA-Compliant Hospital Census Hospital Communication IA ICD-10 ICD-11 Improvement Activities interoperability iOS iOS 8 iOS7 iPad iPhone iPhone 6 Lead Generation MACRA Medical Billing Medical Software Medicare Mentorship Messaging Messaging with Patients MGMA MIPS MIPS Registry mobile Mobile App Mobile Charge Capture Mobile EHR Mobile Health Mobile Messaging Mobile security Mobile Technology Modern Healthcare Native App news NIH OCM Oncology Care Model Patient Patient App Patient Care Patient Generated Health Data Patient Handoff Software Patient Information Patient Visits Patient-Centric pmd pMD Team population health Population Health Management PQRS Product Development Productivity QCDR Quality Scoring Recruiting Recruitment Reimbursement Remote Work reports Residents Responsibility Sales Secure Data Secure Messaging Secure Messaging Video Secure Text Messaging Security Audit SF Biz Times SOC 2 success support TCM Teamwork technology telehealth Text Messaging texting Travel Upgrades VA Value-based care Wearable Device wearing many hats Web App Work From Home