-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
follow a case #149
Comments
While this seems like a pretty substantial project to tackle as my first one, perhaps I can give this a shot? |
@TerryBeyak It looks like you are working on this one. Is that right? Just wanted to make sure two people aren't working on the same issue unknowingly. |
@TerryBeyak Hi Terry, how is this one going for you? |
@jscottchapman @mdarmani I unfortunately think I bit off more than I can chew on this one, so if someone else wants to take it on, they should feel free. 😞 |
@tangollama This is cool idea! I would like to take this work on. |
Have at it!
|
@tangollama I am currently looking at the different roles and trying to decide which roles can follow/unfollow entities. In your vision are there specific roles that can follow/unfollow, or should all roles have the ability to follow/unfollow. |
Anyone who has the ability to see details of a patient record should be able to follow. However, it probably makes sense to provide a special capability in the security settings for following a case.
I'd be happy to discuss further on Slack tomorrow or later this week.
Typed or dictated imperfectly on my iPhone (717.385.9970)
… On May 14, 2017, at 12:21 AM, Michael Bruns ***@***.***> wrote:
@tangollama I am currently looking at the different roles and trying to decide which roles can follow/unfollow entities. In your vision are there specific roles that can follow/unfollow, or should all roles have the ability to follow/unfollow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This comment has been minimized.
This comment has been minimized.
Convert SearchPatients.test.tsx to RTL.
Any entity in HospitalRun should be either automatically or explicitly able to be "followed" by a user within the system. The home screen of HospitalRun would contain a breakdown of all the entities that someone is following, including a current status or latest update.
Some entities, like Lab, Imaging, Medication, and Inventory requests should be automatically followed. For automatic request follows, the notion of "acknowledging" a completed request should cause the user to unfollow that item, though the relationship the user has with the entity should remain recorded, thus putting the "unfollow" into basically an "unsubscribe from this entity" state on the relationship.
The same would be true for physicians who are assigned as the primary care attendant for a Patient Visit, but it would also be good to allow authorized users to explicitly and selectively follow a case to get updates on progress.
Finally, a daily/hourly/twice daily digest email of activity should be emailed to any user set to follow, providing appropriate updates. This gets a little trickier when we talk about what data is and isn't appropriate to share in an email, but I'd like us to try to figure this out.
In other words, think a Twitter feed for an entity in HospitalRun.
The text was updated successfully, but these errors were encountered: