Minimum authorities for Reception role
I am trying to set up a role for the reception function. As I see it, this needs the Basic Role plus:
- Appointment Create/Remove/Save
- Task Create/Remove/Save
- Customer Charge & Charge Item Create/Remove/Save
- Customer Payments Create/Remove/Save
- Patient Create/Remove/Save
- act.patientWeight create/save [I created a new authority]
- Patient Document Create/Save
Note that Remove is probably not required in the above - but I figure it allows you to delete something that you just created - once the item is established and linked to others, then you functionally can't delete it anyway.
With the above set, I can create the appointment or worklist task, but if I check in an appointment, then it gets through the 'choose worklist' step and then says "Access is denied". [It would be nice if it told you what it could not get access to - then I could understand what authorities to add.]
What do I need to get a reception function? ie make appointments, check them in, check them out, invoice them and take their money.
Regards, Tim G
Re: Minimum authorities for Reception role
Tim, first I will draw your attention to the post here:
http://www.openvpms.org/forum/users-and-roles-confusion-and-wierd-behaviour
I have come to the conclusion that user roles at the moment dont really work, due to complex interactions between archetypes on every transaction.
ie Previewing an invoice requires Document.Remove
But a new project was setup to cover this.
http://www.openvpms.org/project/enhance-openvpms-user-authorities
It needs further discussing to get it specced.
Ben