Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Track Physio events #28

Closed
tangollama opened this issue Dec 18, 2014 · 12 comments
Closed

Track Physio events #28

tangollama opened this issue Dec 18, 2014 · 12 comments
Assignees
Labels
🚀enhancement an issue/pull request that adds a feature to the application v2.x
Projects

Comments

@tangollama
Copy link
Member

Doctor's assign physio. We need to queue it and track the notes from it. Note that physio could be "prescribed." i.e. daily while in the hospital.

@tangollama tangollama added the 🚀enhancement an issue/pull request that adds a feature to the application label Dec 18, 2014
@tangollama tangollama added the help wanted indicates that an issue is open for contributions label Sep 25, 2015
@tangollama
Copy link
Member Author

I need to get feedback from Eric Gokcen on this. It may be the notes feature is sufficient to support this function.

@tangollama tangollama added the needs requirements indicates that an issue needs more requirements in order to be worked on label Oct 14, 2015
@tangollama
Copy link
Member Author

Physical therapy events are another set of actions attached to either inpatient or outpatient visits, just like labs, pharmacy, etc.

So a patient could have an appointment for a visit and during that visit, they need to receive physical therapy. The point of the physio events is to capture the results / feedback from the physical therapist in the medical record.

At minimum, an event has a person who conducted the session, notes, and a date. Each event must be associated to a visit (and thus a patient). Physio events should become another tab in a patient's record, and will find it's way into both the Notes feature (which I'm working on #32) as well as the patient history (which I'm also working on).

What makes Physio a needed feature is a bit of a business issue.

  1. patients (or insurance) may be charged for each session, and thus we need to track them.
  2. Physical Therapists need the ability to add/edit Physio events but should not necessarily have rights to do much else. Thus they are a new rule in the system. More specifics will be needed here, but the developer who works on this feature can see @tangollama for assistance as needed.

@tangollama
Copy link
Member Author

See requirements here

@tangollama tangollama removed the needs requirements indicates that an issue needs more requirements in order to be worked on label Feb 2, 2016
@nfung
Copy link

nfung commented Apr 15, 2017

@tangollama I'd like to work on this.

@tangollama
Copy link
Member Author

tangollama commented Apr 15, 2017 via email

@tangollama tangollama added in progress indicates that issue/pull request is currently being worked on and removed help wanted indicates that an issue is open for contributions labels Apr 20, 2017
@nfung
Copy link

nfung commented Apr 27, 2017

Need clarification on the requirements... it states that visits should be read-only to physical therapists, but that physio events should be a list under visits. I took this to mean that one needs to view a visit in order to see a list of physio events, but with the read-only permission, this wouldn't be possible for physical therapists.

@tangollama
Copy link
Member Author

tangollama commented Apr 27, 2017 via email

@tangollama
Copy link
Member Author

@nfung are you still interested in this issue? If not, I'll move it back to Help Wanted.

@nfung
Copy link

nfung commented Aug 5, 2017

@tangollama sorry it's taking me so long to finish this. i've got most of this done... i'll try to wrap this up soon

@tangollama
Copy link
Member Author

@nfung absolutely no need to say sorry. We're all volunteering. Thanks for responding so promptly.

@stale
Copy link

stale bot commented Aug 7, 2019

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.

@stale stale bot added the wontfix indicates an issue/pull request will not be worked on label Aug 7, 2019
@fox1t fox1t self-assigned this Aug 7, 2019
@stale stale bot removed the wontfix indicates an issue/pull request will not be worked on label Aug 7, 2019
@fox1t fox1t added v2.x and removed in progress indicates that issue/pull request is currently being worked on ready labels Aug 7, 2019
@stale

This comment has been minimized.

@stale stale bot added the wontfix indicates an issue/pull request will not be worked on label Oct 6, 2019
@matteovivona matteovivona added this to To do in Version 2.0 via automation Oct 6, 2019
@matteovivona matteovivona removed the wontfix indicates an issue/pull request will not be worked on label Oct 6, 2019
@fox1t fox1t closed this as completed Jan 14, 2020
Version 2.0 automation moved this from To do to Done Jan 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🚀enhancement an issue/pull request that adds a feature to the application v2.x
Projects
Version 2.0
  
Done
Development

No branches or pull requests

4 participants