search

HospitalRun / hospitalrun

Monorepo that holds all of HospitalRun's v2 projects.
https://hospitalrun.io
MIT License
926 stars 342 forks source link

Medication tracking, Related Person usability improvement #356

Open WaseemAlkurdi opened 4 years ago

WaseemAlkurdi commented 4 years ago

First, the rate at which HospitalRun 2.0 is coming together is very impressive ... so sincere thanks to all developers contributing their time to work on this!

However, it is missing a vital feature from 1.0-beta. As of today, the staging version at https://staging.hospitalrun.io still lacks a very important feature of an EHR system: medication tracking.

Also, it would be great to make Related Persons more intuitive by adding the option to create a "related person" 's file at time of entry of the new patient's information (as opposed to having to save the entry, then adding another entry for the related person, then linking up the two persons via Related Persons in the first patient's record.)

Thanks a lot, and I hope this is taken into consideration!

matteovivona commented 4 years ago

Hi @WaseemAlkurdi, thanks for your feedback. We will definitely consider your request :)

fox1t commented 4 years ago

Hi!Thanks for this important suggestion and feature proposal! Can you please elaborate on how the feature has to work in your opinion? It could be helpful in defining the user story.

jackcmeyer commented 4 years ago

I've made hospitalrun/hospitalrun-frontend#2106 to cover the related person feature request

WaseemAlkurdi commented 4 years ago

@tehKapa @fox1t You're welcome! Let's take the context of a fertility/family planning clinic, where the doctor is creating an entry for an example patient John Doe: image

That John Doe is married to Jane Doe, who should share the same record, as the clinic's context needs that . Currently, we have to create a separate entry for her: image then we would have to search for John Doe's record, open it, select Related Persons from there, Add Related Person, then search Jane Doe and select her as Wife. (The "Patients List" page didn't work at the time of posting this, but I will update with screenshots once it becomes available again).

In addition to being cumbersome and very anti-HospitalRun, this approach simply won't work in a fertility clinic, where a couple, not an individual patient, is the focus of the diagnosis and treatment. Currently, the changes to one person's record would not automatically propagate to the other person's, as the database would consider them as separate patients who just happen to be related. But, as we have seen, this might not be wanted in an obstetrics/gynaecology/fertility/family practice, among others.

A solution would be to move Related Persons to the Add Patient page, where the doctor would be able to enter both John Doe and Jane Doe's details at once, then it would offer the user a checkbox to "join" records (like in the case of a fertility clinic), or leave them detached.

WaseemAlkurdi commented 4 years ago

@jackcmeyer Sorry, didn't notice your comment! I'll copy my comment over there post-haste.

ghost commented 4 years ago

@WaseemAlkurdi hello! would u be able to talk about the other feature 'medication tracking' as well? much appreciated.

WaseemAlkurdi commented 4 years ago

@kumikokashii Sure! In version 1.0.0-beta (https://demo.hospitalrun.io), you can see the following tab in a patient's "record" view: image From there, you can add medications, and even do the billing and inventory control directly from that same page. Conveniently, 1.0.0-alpha (only the online demo) includes the ICD-10-CM medication table as autocomplete values for the "medication name" field, a huge aid for users, which the 2.0 staging version doesn't: image However, in HospitalRun 2.0 (http://staging.hospitalrun.io), as of the time of writing, the functionality from 1.0.0-alpha for both medication tracking and inventory control is totally missing: image So, what would have to be done is ~just "porting"~ porting this from 1.0.0-alpha to this version, ~which should be very easy~ it isn't, after looking at that code and basically facepalming because of how naive my comment sounded in light of that ... the implementation itself was done before though, which might be of some help.

WaseemAlkurdi commented 4 years ago

So .. anything more needed in terms of requirements?