The patient dashboard has become much too cluttered with 20 sections!
It combines information that does not go together, i.e clinical info (used mostly by medical provider) and demographic/billing info (used mostly by office staff) .
What do people think about breaking these two apart, into 2 tabs: “Clinical” and “Demographic”.
Current tabs:
Dashboard, History, Report, Documents, Transactions, Issues, Ledger, External Data
Proposed Tabs (remove Dashboard and replace with Clinical & Demographic):
Clinical, Demographic, History, Report, Documents, Transactions, Issues, Ledger, External Data
Clinical would contain:
Vitals
Allergies
Medical Problems
Medications
Prescriptions
Labs
Care Team
Clinical Reminders
Messages
Patient Reminders
Clinical Reminders
Immunizations
Demographic would contain:
Demographics
Billing
Insurance
Appointments
Recall
Patient Portal / API Access
Disclosures
Amendments
Any feedback and further suggestions to improve these sections would be appreciated. I will try to start working on this soon (unless there are objections) !
My first take is a good idea. Instead of a new tab to wrapper existing I’d approach from the POV of section by context and was something @robert.down and I talked about few years back.
This would mean a context manager and part of setup to allow user to decide what is Clinical or Demo…
So user would assign context to sections and enable or disable. Something like this I could get behind but at any rate, I appreciated you taking on new improvements as I know how committed you are the the project. thanks
It probably should be in both the demographic and clinical tab.
Plus, there should be a tab for messages since it opens a new webpage when you click on “Click here to view them all”. That way someone can get to messages without going through the dashboard.
I am also thinking maybe the “Demographic” tab should be named “Billing” instead. Thoughts?
My ai is trained to understand our card system and I’d bet could come up with a solution that would only require a little integration knowledge.
You want?
Read the comment.md for explanation of scripts. I think Claude over did it as always but the code is viable from my quick glance and give precise examples. I believe everything you’d need is there.
I’ll try to be on call tomorrow if you want to discuss @psoas @snailwell The Billing widget is meant and designed to be in users face.
We have a ledger that explains Account better where Billing is just that basically an invoice.
For legacy I’d think it be an issue and my guess, it’d be tough to get by @stephenwaite
On this I’ll go with the flow.