-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GSOC-23: Roles and User Modules #43
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chaitak-gorai left some reviews
Update: Added Laratrus Seeder for Roles@muarachmann, I have updated the changes you suggested in the earlier commit. In
Can you please REVIEW these access and suggest to me the changes we need to make?? |
I will review the roles/module in details later this week |
Update:@muarachmann, I have updated some changes here I m listing for your review.
Screenshot of update Roles.vue UI Can you please REVIEW these changes and suggest to me the changes we need to make?? |
Update:@muarachmann, I have updated your suggested reviews. Also, I have created the I ll then implement the functions |
We should stick with separate fields.
… But I find it an interesting thought experiment to consider the
implications of one name field as better internationally. Search is fast
and easy these days, so finding patients would not be an issue.
Sharing data externally would; in the USA, as healthcare businesses are all
stuck in old models.
Tony
On Fri, Jul 7, 2023 at 5:56 PM Chaitak Gorai ***@***.***> wrote:
Update:
@muarachmann <https://github.com/muarachmann>, I have updated your
suggested reviews. Also, I have created the Add Users UI form page with
the fields;
I have added all necessary form fields. I have a doubt whether the name
can be in a single Full Name field or in parts.
Please review it and suggest changes if required.
I ll then implement the functions
[image: image]
<https://user-images.githubusercontent.com/77141674/251884447-4283a838-75db-4878-aa4c-63fd8d108006.png>
—
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACFZC324C54XWM3WP4KX4LXPCV2BANCNFSM6AAAAAAZA67IAQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
https://thinkstorm.net
503-330-2239
|
The users name as a single field would work , if we ONLY used it for user
identification purpose, however we use the provider’s user account on
external forms that require separate fields, including title.
On Sat, Jul 8, 2023 at 9:05 AM Tony McCormick ***@***.***>
wrote:
We should stick with separate fields.
… But I find it an interesting thought experiment to consider the
implications of one name field as better internationally. Search is fast
and easy these days, so finding patients would not be an issue.
Sharing data externally would; in the USA, as healthcare businesses are
all stuck in old models.
Tony
On Fri, Jul 7, 2023 at 5:56 PM Chaitak Gorai ***@***.***>
wrote:
> Update:
>
> @muarachmann <https://github.com/muarachmann>, I have updated your
> suggested reviews. Also, I have created the Add Users UI form page with
> the fields;
> I have added all necessary form fields. I have a doubt whether the name
> can be in a single Full Name field or in parts.
> Please review it and suggest changes if required.
>
> I ll then implement the functions
>
> [image: image]
> <https://user-images.githubusercontent.com/77141674/251884447-4283a838-75db-4878-aa4c-63fd8d108006.png>
>
> —
> Reply to this email directly, view it on GitHub
> <#43 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AACFZC324C54XWM3WP4KX4LXPCV2BANCNFSM6AAAAAAZA67IAQ>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
--
https://thinkstorm.net
503-330-2239
--
https://thinkstorm.net
503-330-2239
|
so as of now can we move forward with a single user name field? I think it will be an efficient way to store the name. |
No, The provider data is used on claim forms that require separate fields.
Wish it was otherwise. Mua, what do you think?
Tony
On Sat, Jul 8, 2023 at 9:16 AM Chaitak Gorai ***@***.***>
wrote:
The users name as a single field would work , if we ONLY used it for user
identification purpose, however we use the provider’s user account on
external forms that require separate fields, including title. On Sat, Jul
8, 2023 at 9:05 AM Tony McCormick *@*.
*> wrote: We should stick with separate fields. … But I find it an
interesting thought experiment to consider the implications of one name
field as better internationally. Search is fast and easy these days, so
finding patients would not be an issue. Sharing data externally would; in
the USA, as healthcare businesses are all stuck in old models. Tony On Fri,
Jul 7, 2023 at 5:56 PM Chaitak Gorai @.*> wrote: > Update: > >
@muarachmann <https://github.com/muarachmann>
https://github.com/muarachmann, I have updated your > suggested reviews.
Also, I have created the Add Users UI form page with > the fields; > I have
added all necessary form fields. I have a doubt whether the name > can be
in a single Full Name field or in parts. > Please review it and suggest
changes if required. > > I ll then implement the functions > > [image:
image] >
https://user-images.githubusercontent.com/77141674/251884447-4283a838-75db-4878-aa4c-63fd8d108006.png
> > — > Reply to this email directly, view it on GitHub > <#43 (comment)
<#43 (comment)>>,
> or unsubscribe >
https://github.com/notifications/unsubscribe-auth/AACFZC324C54XWM3WP4KX4LXPCV2BANCNFSM6AAAAAAZA67IAQ
> . > You are receiving this because you are subscribed to this
thread.Message > ID: *@*.***> > -- https://thinkstorm.net 503-330-2239 --
https://thinkstorm.net 503-330-2239
so as of now can we move forward with a single user name field? I think it
will be an efficient way to store the name.
—
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACFZCYVHONB3LULTEXV7ZLXPGBTRANCNFSM6AAAAAAZA67IAQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
https://thinkstorm.net
503-330-2239
|
Thank you for the reviews. I will update them ASAP. |
Update:
@muarachmann these are the bunch of changes I have updated based on your reviews. Please give it a review and suggest how to proceed further. |
@muarachmann i have added a multiselect input type in |
Hi @chaitak-gorai please use this - MultiSelect component in the project |
I looked for the component in the project but couldn't able to find it. Can you please tell me where it is located. Do you mean by the |
@chaitak-gorai do not forget to list the users in the datatable as well. |
Update@muarachmann i have added these changes
I haven't hide the menu link in frontend. It will be better if we show them a |
Hi @chaitak-gorai will be reviewing this this weekend for a merge. Anything you have to polish? |
Hey @muarachmann, thank you for the update. I'll look into it and do the necessary polishing by the weekend. There are some validations left i guess. I'll update the changes if any. |
Hey @muarachmann, i have added the validation for the |
Hey @muarachmann hope you are doing fine. |
Hi @chaitak-gorai I have been really busy lately. Will review this during the weekend and merge |
Hey @muarachmann its ok if you are busy. Just a reminder that if you are available this weekend can we discuss on this. |
Description
This PR is for the Google Summer of Code Project : Migrate EHR to Laravel: Users and Roles Module .
Workflow
*All the commits will be added to this for the final merge to the codebase