Hello Messorians,
I just published a new video breaking down what's actually changed for healthcare data analyst hiring in 2026, and what I would personally do differently if I were starting from zero today. First, I want to go deeper on the single most important idea from it, the one that will do more for your career than the rest of the video combined if you actually apply it.
The one paragraph that beats a whole dashboard.
Here's the situation. Any candidate applying for a healthcare analyst role in 2026 can generate a SQL query, a pivot table, and a fully designed dashboard in about ten minutes using AI. Hiring managers know this. Which means a polished portfolio project no longer proves what it used to prove. Everyone has one. Everyone's looks pretty. Everyone's "works."
What separates the candidate who gets the offer from the candidate who gets the polite decline is no longer the artifact. It's the thinking next to the artifact.
I mentioned this in the video and called it a decision log. It's exactly what it sounds like: a short, human-written record of the judgment calls you made while building the project, and why. It doesn't need to be fancy. Three to five bullet points under each project is enough. But when a hiring manager sees one on your portfolio, everything changes about how they read you.
A decision log signals three things at once that a pretty dashboard cannot. First, that you noticed something the raw data didn't hand you. Second, that you made a choice about it rather than running whatever the AI suggested. Third, that you can explain the choice out loud, which is 80% of what an interview actually is.
Here's the structure worth using every time.
The five-part decision log entry.
For every meaningful choice you made in a project, write five short lines.
What I noticed. The anomaly, the surprise, the thing that didn't look right at first glance.
What I checked. The follow-up investigation you did to confirm or disprove it.
What I decided. The call you made. The rows you excluded, the metric you redefined, the KPI you dropped.
Why it mattered. The business or clinical implication if the decision had gone the other way.
What I'd do next. One line of self-critique or the next iteration you'd build.
That's it. Five lines. Put three to five of these underneath each project on your GitHub README or portfolio site and you now have documentation hiring managers actually read.
Three worked examples, one for each of the projects from the video.
If you're building the three projects I recommend (readmissions dashboard, claims cost and utilization, quality and safety trends), here's what a real decision log entry looks like for each one.
Readmissions dashboard.
Noticed: About 12% of what appeared to be 30-day readmissions were actually same-day transfers between units of the same facility. Checked: Cross-referenced admission source codes against discharge disposition on the initial encounter. Decided: Excluded same-day transfers from the readmission numerator. Why it mattered: Without the exclusion, the reported readmission rate was 18%. With it, it was 14%, which matched the CMS methodology and avoided sending leadership a false alarm. Next: Add a toggle so users can see both the strict CMS definition and an all-encounter view.
Claims cost and utilization.
Noticed: The top 5% of members accounted for 62% of total spend. Checked: Segmented by primary diagnosis category and comorbidity count. Nearly all were multi-chronic patients with low medication adherence. Decided: Flagged this subpopulation as the priority cohort for any downstream care management dashboard. Why it mattered: If a plan wanted a quick-win intervention, this is the group where the same dollar of investment recovers the most. Next: Layer in Rx adherence data to sharpen the targeting.
Quality and safety trends.
Noticed: Inpatient fall rates spiked in Q3 and then dropped back to baseline in Q4. Checked: Whether the change correlated with staffing ratios, admissions volume, or protocol changes. Found it aligned with a temporary rollout of a new fall-risk assessment tool that was later rolled back. Decided: Flagged the spike as workflow-driven, not a real safety change. Why it mattered: Without that context, someone would have escalated to the patient safety committee based on an artifact of a pilot program. Next: Build a small annotation layer that lets analysts tag anomalies with known workflow changes.
How to use it in the interview.
When the interviewer asks you to walk through the project, do not lead with the dashboard. Lead with one of these decision log entries. "The most interesting thing I found in this project was that 12% of what looked like readmissions were actually same-day transfers." Then walk them through what you did.
The interviewer will remember that story. They will not remember the color palette on your bar chart.
Why this is the real 2026 differentiator.
Every candidate in 2026 has AI. That means the technical output is no longer the signal. What is still scarce, and getting more scarce, is documented judgment. A candidate who shows they can spot a problem, investigate it, make a call, and explain why now stands out in a way that no amount of AI can replicate. The decision log is the artifact of that thinking. It is the thing that makes a hiring manager stop scrolling.
If you're actively working toward a healthcare data analyst role, watch the new video end to end and pair it with the decision log framework above. That combination will move you further in the next 30 days than another month of tutorial grinding will.
Sharif
Founder, Informessor
