How does Fix Encounter dates ACL work?

ajperezcrespo wrote on Tuesday, September 03, 2013:

Hi all,
Where would a user (Having the Fix Encounter date ACL set) be able to fix the encounter/hospitalization date?
It doesn’t show up as an option in the encounter summary as editable (or viewable for that matter).

Thanks
Alfonso

fsgl wrote on Tuesday, September 03, 2013:

Are you referring to this:

ajperezcrespo wrote on Tuesday, September 03, 2013:

Yup I is,
Even though the user belongs to the Accounting Group and the Accounting group has this ACL enabled, I cannot find my way to that input screen.

Thanks
Alfonso

epsdky wrote on Tuesday, September 03, 2013:

How about the “Edit” button next to “Patient Encounter by (provider)”?

ajperezcrespo wrote on Tuesday, September 03, 2013:

I tried it on the demo.
https://omp.openmedpractice.com/openemr-4.1.2
Created a user (billing) password (pass). Lookup a patient with an encounter Select the encounter from past encounters and documents
No edit button is avilable.

Reproduced on 4.1.0 also.

ajperezcrespo wrote on Tuesday, September 03, 2013:

FYI: billing belongs only to the Accounting group and has the Fix Encounter Dates ACL.

epsdky wrote on Tuesday, September 03, 2013:

Don’t know if this is of any use but…

Elusive “Edit” button appears under these conditions…

Under Groups and Access Controls…

Accounting-write…

With these active…

[Accounting]
(All)

[Encounters]
Fix encounter dates…
Notes-any encounters…

[Patients]
Demographics…

[Sensitivities]
Normal

fsgl wrote on Tuesday, September 03, 2013:

The problem has to do with fine granular control, which is not possible in Administration/ACL. It is not even possible in Access Control List Administration (Advanced) or phpGACl (see attachment 1), in its present form.

You obviously don’t want the Accountant to have Administrator privileges, therefore Adminstrator Lite would be Superuser. I was hoping that moving Superuser into the Active column, the Accountant would be able to edit encounter dates (see attachment 2), because that is one of the ACL’s of Superuser, but it didn’t work in the Demo.

Adding this ACL means changing the codes.

fsgl wrote on Tuesday, September 03, 2013:

Great explanation of ACO’s, AXO’s and ACL’s in the phpGACL manual, last tab on right, especially for Star Wars fans.