Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-3377

Should be able to define a privilege required to view or edit an encounter

    XMLWordPrintable

    Details

    • Complexity:
      Medium

      Description

      Add two optional properties to EncounterType: viewPrivilege and editPrivilege.
      In the db those would be encounter_type.view_privilege and edit_privilege (varchar references privilege).
      The encounters dashboard tab would need to respect viewPrivilege when deciding what encounters to display. (can we build this into the paged hibernate query we're using, though?).
      Same goes for the visits dashboard tab.
      Same goes for the encounter search widget, and the manage encounters admin page.
      If an encounter type has this property equal to null, everyone sees the encounters.

        Gliffy Diagrams

          Attachments

          1. TRUNK-3377.patch
            17 kB
          2. TRUNK-3377-1.patch
            22 kB
          3. TRUNK-3377-2.patch
            24 kB
          4. TRUNK-3377-3.patch
            13 kB
          5. TRUNK-3377-4.patch
            13 kB
          6. TRUNK-3377-5.patch
            5 kB
          7. TRUNK-3377-6.patch
            22 kB
          8. TRUNK-3377-7.patch
            24 kB

            Issue Links

              Activity

                People

                Assignee:
                mvorobey Mykola Vorobey
                Reporter:
                dkayiwa Daniel Kayiwa
                Votes:
                1 Vote for this issue
                Watchers:
                11 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: