Deepthi's Reading

Clinical

008

The Healthcare Quality Dashboards Story

Predictive quality intelligence, not just another health app

Excel · Access · Microsoft Lists · AWS

Edition #008 · 6 chapters · 14 min read

The Healthcare Quality Dashboards Story

Predictive quality intelligence, not just another health app

Compliance data is usually a report nobody reads. This turns it into dashboards that show patterns: P-charts, Pareto analysis, heat maps, and compliance calculations that point to where harm is likely before it happens.

An ebook edition of the Healthcare Quality Dashboards build journey: how it started, what actually happened, the conversations that changed the build, what broke, and what I learned. Written in plain English for readers with no technical background. Tools covered: Excel, Access, Microsoft Lists, AWS, DynamoDB, Netlify.

Start reading Back to the library

Start here

What you'll understand by the end

Not mastery — understanding. By the last page you'll be able to explain these in your own words, even with no technical background.

•what Access really is, and what it cannot do
•what AWS really is, and what it cannot do
•what Excel really is, and what it cannot do
•what Microsoft Lists really is, and what it cannot do
•the difference between what the AI does, what the tool does, and what I do
•why permissions and privacy matter once AI can act on your behalf
•where a real person's judgement is still necessary

The concept ladder — the order I actually learned things

I had an idea worth building

↓

I asked an AI to help me shape it

↓

I learned the AI could explain things but could not act outside the chat by itself

↓

I met the tools that actually do the work

↓

I learned how those tools are connected and permitted

↓

I built something real and watched it break

↓

I learned where my own judgement is still required

Chapter 01

Why Healthcare Quality Dashboards had to exist

Track 1 · My journey

Quality meetings were full of numbers nobody could act on. I wanted charts that end in a decision. Compliance data is usually a report nobody reads. This turns it into dashboards that show patterns: P-charts, Pareto analysis, heat maps, and compliance calculations that point to where harm is likely before it happens. The honest test I set myself was simple: if this existed tomorrow, would anyone actually open it twice? Everything in the rest of this book is downstream of that one question. Healthcare Quality Dashboards is what came out the other side.

Learning checkpoint

Before this chapter

I had a problem I could describe in a corridor conversation, but nothing I could hand to anyone.

After this chapter

I still did not know which tools to use, but I knew exactly who I was building for.

What changed my mind

The problem stopped being a complaint and became a specification.

Can you answer these?

?Can you state the problem in one sentence, without naming a solution?
?Do you know who is holding the screen when your product is used?

Chapter 02

The first conversation

Track 1 · My journey

I did not start with code. I started by describing the thing out loud, in ordinary language, the way I would explain it to a colleague. The build tool answered with a working screen, and that changed the conversation from theory to critique — it is much easier to say what is wrong with something in front of you than to specify it from nothing. These were the exchanges that actually moved the build: Me: "Is this change real or noise?" → Control charts answered it honestly, sometimes uncomfortably. Me: "Which twenty percent causes most of it?" → Pareto turned a long list into three priorities. Me: "Every chart needs an owner." → Dashboards stopped being decoration. Each of those lines looks small. Together they are the design document. I have stopped writing long specifications; the transcript is the specification.

Learning checkpoint

Before this chapter

A blank project and a chat window.

After this chapter

The shape of the product was decided before a single deliberate design decision was made.

What changed my mind

I learned to treat conversation as a design tool, not as preparation for design.

Can you answer these?

?What is the one sentence in your own notes that decided the architecture?
?Are you describing outcomes, or dictating implementation?

Chapter 03

Building it: Excel, Access, Microsoft Lists, AWS, DynamoDB, Netlify

Track 1 · My journey

P-charts told us whether a change was real variation or just noise, and Pareto analysis told us which few causes carried most of the harm. The stack was whatever was already available — Excel, Access, Microsoft Lists, a DynamoDB store, a Netlify front end. The value was never the tooling. It was refusing to report a number without also reporting what to do about it. Once the dashboards had an owner and an action per chart, the meetings got shorter and the improvements got real. The stack was Excel, Access, Microsoft Lists, AWS, DynamoDB, Netlify. I did not choose it for elegance; I chose it because it let me get a real, usable thing in front of a real person quickly, and because I could change my mind cheaply when the first idea turned out to be wrong. The rhythm mattered more than the tooling. Ship something small, use it honestly, fix the one thing that hurt most, repeat. Most of the good decisions in Healthcare Quality Dashboards came from that loop rather than from planning.

Track 2 · Learn with Deepthi

Excel

EXPLORED — I researched or discussed it

What did I just discover?: That Excel was doing more of the work in this build than I gave it credit for.
What I thought it meant: I assumed it was a technical detail I could pick up later.
What I learned: It shaped what was easy and what was expensive, and therefore what the product became.
What is it, really?: Excel is one of the pieces this build rests on — it is worth understanding what it makes cheap and what it makes hard before you commit to it.
Think of it like this (analogy): A workshop tool: it does not decide what you make, but it strongly influences what you find yourself making.
How does it actually work?: In simple terms: I give Excel an input, it does one well-defined job with it, and it hands back a result the rest of the project can use.
Why does this exist?: Excel exists to solve a specific, repetitive problem so that people building things do not have to solve it again from scratch every time.
Why did it matter to my project?: Because the constraints of your tools quietly become the constraints of your product.
Where I used it: Used throughout Healthcare Quality Dashboards, especially while getting the first working screens in front of people.
Common beginner misunderstanding: A common beginner assumption is that adding Excel automatically makes a project better. A tool only helps when it matches the problem you actually have.
What this tool cannot do: Excel does one job well and nothing outside that job. It cannot decide what your product should be, and it will not protect you from a wrong requirement.
What surprised me: How much of the design pressure came from the tool rather than from the problem.

What happens behind the scenes

What the AI is doing

The AI model reads my instruction, decides how Excel fits, and writes or explains the part that uses it.

What the tool is doing

Excel performs its own specific job — the AI does not do that work itself, it only directs it.

What I am doing

I decide whether Excel is the right choice, approve it, and judge whether the outcome is actually what my readers need.

One thing to remember

Remember this

Choose tools by what they make cheap to change, not by what they make possible.

Try it yourself

Rebuild one screen of your own project with Excel and time it honestly.

Accuracy note: product behaviour checked on 2026-08-15. General concepts are stable; product-specific behaviour can change.

Track 2 · Learn with Deepthi

Access

EXPLORED — I researched or discussed it

What did I just discover?: That Access was doing more of the work in this build than I gave it credit for.
What I thought it meant: I assumed it was a technical detail I could pick up later.
What I learned: It shaped what was easy and what was expensive, and therefore what the product became.
What is it, really?: Access is one of the pieces this build rests on — it is worth understanding what it makes cheap and what it makes hard before you commit to it.
Think of it like this (analogy): A workshop tool: it does not decide what you make, but it strongly influences what you find yourself making.
How does it actually work?: In simple terms: I give Access an input, it does one well-defined job with it, and it hands back a result the rest of the project can use.
Why does this exist?: Access exists to solve a specific, repetitive problem so that people building things do not have to solve it again from scratch every time.
Why did it matter to my project?: Because the constraints of your tools quietly become the constraints of your product.
Where I used it: Used throughout Healthcare Quality Dashboards, especially while getting the first working screens in front of people.
Common beginner misunderstanding: A common beginner assumption is that adding Access automatically makes a project better. A tool only helps when it matches the problem you actually have.
What this tool cannot do: Access does one job well and nothing outside that job. It cannot decide what your product should be, and it will not protect you from a wrong requirement.
What surprised me: How much of the design pressure came from the tool rather than from the problem.

What happens behind the scenes

What the AI is doing

The AI model reads my instruction, decides how Access fits, and writes or explains the part that uses it.

What the tool is doing

Access performs its own specific job — the AI does not do that work itself, it only directs it.

What I am doing

I decide whether Access is the right choice, approve it, and judge whether the outcome is actually what my readers need.

One thing to remember

Remember this

Choose tools by what they make cheap to change, not by what they make possible.

Try it yourself

Rebuild one screen of your own project with Access and time it honestly.

Accuracy note: product behaviour checked on 2026-08-15. General concepts are stable; product-specific behaviour can change.

Track 2 · Learn with Deepthi

Microsoft Lists

EXPLORED — I researched or discussed it

What did I just discover?: That Microsoft Lists was doing more of the work in this build than I gave it credit for.
What I thought it meant: I assumed it was a technical detail I could pick up later.
What I learned: It shaped what was easy and what was expensive, and therefore what the product became.
What is it, really?: Microsoft Lists is one of the pieces this build rests on — it is worth understanding what it makes cheap and what it makes hard before you commit to it.
Think of it like this (analogy): A workshop tool: it does not decide what you make, but it strongly influences what you find yourself making.
How does it actually work?: In simple terms: I give Microsoft Lists an input, it does one well-defined job with it, and it hands back a result the rest of the project can use.
Why does this exist?: Microsoft Lists exists to solve a specific, repetitive problem so that people building things do not have to solve it again from scratch every time.
Why did it matter to my project?: Because the constraints of your tools quietly become the constraints of your product.
Where I used it: Used throughout Healthcare Quality Dashboards, especially while getting the first working screens in front of people.
Common beginner misunderstanding: A common beginner assumption is that adding Microsoft Lists automatically makes a project better. A tool only helps when it matches the problem you actually have.
What this tool cannot do: Microsoft Lists does one job well and nothing outside that job. It cannot decide what your product should be, and it will not protect you from a wrong requirement.
What surprised me: How much of the design pressure came from the tool rather than from the problem.

What happens behind the scenes

What the AI is doing

The AI model reads my instruction, decides how Microsoft Lists fits, and writes or explains the part that uses it.

What the tool is doing

Microsoft Lists performs its own specific job — the AI does not do that work itself, it only directs it.

What I am doing

I decide whether Microsoft Lists is the right choice, approve it, and judge whether the outcome is actually what my readers need.

One thing to remember

Remember this

Choose tools by what they make cheap to change, not by what they make possible.

Try it yourself

Rebuild one screen of your own project with Microsoft Lists and time it honestly.

Accuracy note: product behaviour checked on 2026-08-15. General concepts are stable; product-specific behaviour can change.

Track 2 · Learn with Deepthi

AWS

EXPLORED — I researched or discussed it

What did I just discover?: That AWS was doing more of the work in this build than I gave it credit for.
What I thought it meant: I assumed it was a technical detail I could pick up later.
What I learned: It shaped what was easy and what was expensive, and therefore what the product became.
What is it, really?: AWS is one of the pieces this build rests on — it is worth understanding what it makes cheap and what it makes hard before you commit to it.
Think of it like this (analogy): A workshop tool: it does not decide what you make, but it strongly influences what you find yourself making.
How does it actually work?: In simple terms: I give AWS an input, it does one well-defined job with it, and it hands back a result the rest of the project can use.
Why does this exist?: AWS exists to solve a specific, repetitive problem so that people building things do not have to solve it again from scratch every time.
Why did it matter to my project?: Because the constraints of your tools quietly become the constraints of your product.
Where I used it: Used throughout Healthcare Quality Dashboards, especially while getting the first working screens in front of people.
Common beginner misunderstanding: A common beginner assumption is that adding AWS automatically makes a project better. A tool only helps when it matches the problem you actually have.
What this tool cannot do: AWS does one job well and nothing outside that job. It cannot decide what your product should be, and it will not protect you from a wrong requirement.
What surprised me: How much of the design pressure came from the tool rather than from the problem.

What happens behind the scenes

What the AI is doing

The AI model reads my instruction, decides how AWS fits, and writes or explains the part that uses it.

What the tool is doing

AWS performs its own specific job — the AI does not do that work itself, it only directs it.

What I am doing

I decide whether AWS is the right choice, approve it, and judge whether the outcome is actually what my readers need.

One thing to remember

Remember this

Choose tools by what they make cheap to change, not by what they make possible.

Try it yourself

Rebuild one screen of your own project with AWS and time it honestly.

Accuracy note: product behaviour checked on 2026-08-15. General concepts are stable; product-specific behaviour can change.

Learning checkpoint

Before this chapter

I had screens in my head and a stack I had not yet justified.

After this chapter

A working product, and a much shorter list of things I believed without evidence.

What changed my mind

The stack became a means, not an identity.

Can you answer these?

?Could you rebuild your first screen in an afternoon if you had to?
?Which tool are you using out of habit rather than fit?

Chapter 04

What broke

Track 1 · My journey

The first dashboard was beautiful and useless — lots of charts, no decisions. I deleted half of it. Breakage is the most useful part of the process because it is unambiguous. A feature nobody uses is a feature that failed, no matter how well it is built. So I cut, simplified, and made the default path shorter until the product stopped resisting the person using it. I keep this chapter in every book deliberately. The polished version of a build story is not useful to anyone; the failure is where the transferable lesson lives.

Learning checkpoint

Before this chapter

Something that worked in the demo and failed in real life.

After this chapter

A smaller, blunter, considerably more useful product.

What changed my mind

I stopped defending the first version and started measuring it.

Can you answer these?

?What in your build is complete but unused?
?What would you cut if you had to halve the time it takes to use?

Chapter 05

What actually changed

Track 1 · My journey

The point of Healthcare Quality Dashboards was never the software. It was the change in behaviour around it: fewer things forgotten, less guessing, a clearer handover between the people involved. Predictive quality intelligence, not just another health app What I watch for now is whether the thing gets opened a second time, without being asked. Second use is the only honest metric I have found at this scale. Everything else is a story I tell myself. The status of this build: in_progress. That is stated plainly on purpose — unfinished work teaches as much as shipped work, and pretending otherwise makes these books useless.

Learning checkpoint

Before this chapter

A product that worked, and no clear evidence that it mattered.

After this chapter

A clear-eyed view of what the product does and does not fix.

What changed my mind

Success stopped meaning "it is built" and started meaning "it is used".

Can you answer these?

?What behaviour changed because your product exists?
?Would anyone notice if it disappeared tomorrow?

Chapter 06

What I would tell you before you start

Track 1 · My journey

A metric without an owner and an action is decoration. Predict, then act, then measure again. Three things I would repeat on the next build: 1. Describe the problem before naming a tool. The tool is the last decision, not the first. 2. Get something usable in front of a real person within a day. Opinions about a screenshot are worth more than opinions about a plan. 3. Keep a record of the conversation. The transcript is the design history, the documentation and — as this book proves — the product. If you take one thing from Healthcare Quality Dashboards: the difference between an idea and a product is a short loop, run honestly, many times.

Learning checkpoint

Before this chapter

You have read what happened. Here is what to take with you.

After this chapter

A method you can reuse on a completely different problem.

What changed my mind

The build became repeatable rather than lucky.

Can you answer these?

?What is your version of the short loop?
?What will you ship this week, even if it is embarrassing?

Appendix

Deepthi's Dictionary

Short loop: Describe, build, use, correct — repeated in hours rather than weeks. The core working method behind this build.
Second use: Whether someone opens the product a second time without being asked. The simplest honest measure of whether it works.
Conversation beat: A single line in a build conversation that changed a decision. Collected, these form the real design document.
Worst day design: Designing for the tired, rushed, distracted user rather than the ideal one in a demo.
Excel: Excel — part of the stack used to build Healthcare Quality Dashboards.
Access: Access — part of the stack used to build Healthcare Quality Dashboards.
Microsoft Lists: Microsoft Lists — part of the stack used to build Healthcare Quality Dashboards.
AWS: AWS — part of the stack used to build Healthcare Quality Dashboards.
DynamoDB: DynamoDB — part of the stack used to build Healthcare Quality Dashboards.
Netlify: Netlify — part of the stack used to build Healthcare Quality Dashboards.