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

Display allergies on the patient summary header #235

Closed
1 of 4 tasks
tangollama opened this issue Dec 12, 2015 · 5 comments
Closed
1 of 4 tasks

Display allergies on the patient summary header #235

tangollama opened this issue Dec 12, 2015 · 5 comments
Labels
in progress indicates that issue/pull request is currently being worked on

Comments

@tangollama
Copy link
Member

tangollama commented Dec 12, 2015

Once we have #234, display allergies in the patient summary component (app/components/patient-summary.js).

TODO

  • Ability to specify allergies for a patient�
    • Modify the model to add allergies hasMany
    • Change Visits edit route to allow editing allergies
    • Display on Patient Summary
@jkleinsc
Copy link
Member

Since part of this issue is to Change Visits edit route to allow editing allergies, I suggest what happens is that there is a way to edit the allergies directly in the patient summary header when on the visit screen versus having separate fields on the visit form to collect allergies.

@donaldwasserman
Copy link
Contributor

I'm taking a stab at this as well, but would it be better to do this on the patient information view or the visit view?

(I only say that because I just added it on the patient information screen, but it can be an easy copy and paste over)

@jkleinsc
Copy link
Member

@donaldwasserman it should be added to the patient summary component:
https://github.com/HospitalRun/hospitalrun-frontend/blob/master/app/templates/components/patient-summary.hbs

This component displays on both the patient screen as well as the visit screen.

The allergies need to be editable from the visit screen, but making it editable on the patient screen is probably a good idea too.

@donaldwasserman
Copy link
Contributor

I have the stuff setup as a component to jam in wherever.

@jkleinsc I'll have some stuff I want you to look at this week. (Day care-related illnesses cut back on some of my available time/willingness this weekend). It's not going to be finished, but want to get some feedback to make sure I haven't gotten too far afield.

What's the best way to share some of that code with you?

@jkleinsc
Copy link
Member

Thanks @donaldwasserman... sorry about the illnesses... sick kids are no fun!

As far as sharing the code, just create a pull request but specifically state that it is in progress (I'll add a label as well), so that it doesn't accidentally get merged in. Github PR's now have a nice review process so we can use that as well if you put in in a PR.

@jkleinsc jkleinsc 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 Nov 8, 2016
matteovivona pushed a commit that referenced this issue Jan 15, 2021
…hinput-test-improvements

Improve PatientSearchInput.test.tsx
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
in progress indicates that issue/pull request is currently being worked on
Projects
None yet
Development

No branches or pull requests

4 participants