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

New Imaging Request - required visit not enforced #2556

Open
blestab opened this issue Jan 27, 2021 · 7 comments · May be fixed by #2572
Open

New Imaging Request - required visit not enforced #2556

blestab opened this issue Jan 27, 2021 · 7 comments · May be fixed by #2572
Assignees
Labels
🐛bug issue/pull request that documents/fixes a bug imaging in progress indicates that issue/pull request is currently being worked on
Milestone

Comments

@blestab
Copy link
Contributor

blestab commented Jan 27, 2021

When requesting a new imaging, visit is required but a user can still save without choosing a visit. See #2552 (review)

🐛 Bug Report

When creating a new imaging request, a user should not be able to save without specifying a visit.

To Reproduce

Go to staging https://staging.hospitalrun.io/
Create a new patient and create one visit for this patient
Create a new imaging request leaving the visit field empty
Notice you are allowed to save even though the visit is marked as required

Expected behavior

User should not be able to save a New Imaging request without selecting a visit.

Reference

See how the Patient or Type field are handled and do the same

Your Environment

  • node version: 6,8,10
  • fastify version: >=1.0.0
  • os: Mac, Windows, Linux
  • any other relevant information
@blestab blestab added 🐛bug issue/pull request that documents/fixes a bug help wanted indicates that an issue is open for contributions imaging labels Jan 27, 2021
@blestab blestab added this to the v2.0 milestone Jan 27, 2021
@SamuelQZQ
Copy link
Contributor

@blestab Can I be assigned to this task?

@blestab
Copy link
Contributor Author

blestab commented Jan 27, 2021

@blestab Can I be assigned to this task?

Thank you @SamuelQZQ, Let's get #2557 out first then will assign this to you once done.

@alexma01
Copy link

Hi,
Sorry I'm getting in the way :)

"See how the Patient or Type field are handled and do the same"

In this case I don't think it's okay to manage them in the same way, with which search criteria would you do it?
I don't think it would be good to even see them all.
It would be necessary to decide with which criteria to show the visits.

@blestab
Copy link
Contributor Author

blestab commented Jan 28, 2021

Hi,
Sorry I'm getting in the way :)

"See how the Patient or Type field are handled and do the same"

In this case I don't think it's okay to manage them in the same way, with which search criteria would you do it?
I don't think it would be good to even see them all.
It would be necessary to decide with which criteria to show the visits.

Thanks @alexma01, you're not in the way at all, all ideas are welcome; Why don't you hop onto our slack and tell us more about your thoughts about this

@bernoraj
Copy link

bernoraj commented Feb 6, 2021

Hi @blestab , Is there anything that I can help in this issue?

@matteovivona
Copy link
Contributor

@bernoraj currently I'm afraid it's stuck. if you want to take it over, you're welcome to it

@bernoraj
Copy link

Sure @tehkapa , I would like to take it up.

@matteovivona matteovivona 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 Feb 11, 2021
@bernoraj bernoraj linked a pull request Feb 16, 2021 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐛bug issue/pull request that documents/fixes a bug imaging in progress indicates that issue/pull request is currently being worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants