Reference Configs for Privileges and Workflows for the Frontend

Implementing
,
1

Hi All,

Implementers , Developers,

There’s always a problem for Implementations getting started setting up User privileges and various workflows for a particular Distro in the frontends specifically.

Is it possible or a good idea to include basic / Reference workflows and Privileges controlled by default User privileges for the Refapp

It could be configs that Ship with the content packages, but activated by the Implementer based on some flags.

Is this something that’s necessary? given there’s some docs already explaining some bits

cc @ibacher / @veronica / @nethmi / @burke / @michaelbontyes / @grace / @dkayiwa

2

Is this something you are ready to get started on?

3

I feel like giving it some time.

4

@slubwama do you think this would be a good thing to have ? In the Refapp ?

5

Hi @tendomart,

Do you have an example? And which configs would be part of it? (Iniz files, frontend json, etc.?)

Thanks

6

Hey @michaelbontyes

  1. Patient registration (Clerks, Nurses and others) Isolated from consultation (Can do Triage and add patient to queues app, appointments, can’t access labs and other irrelevant apps)
  2. Provider / physician consultation Isolated (Physician should see Patient Queues and appointment app and may be beds management apps but not Labs app)
  3. Lab Technician can only see labs app (cannot see Patient chart, Queues app, appointments, e.t.c that’s not relevant)
  4. e.t.c

do these make sense ?

7

Hi @tendomart, it certainly make sense.

I would be happy to review any text file explaining in details the different personas, roles, privileges, demo users, and other requirements, you’re thinking about to be part of such reference configs, and how it would be translated in config files.

Thanks

1 Like
8

@michaelbontyes I have uploaded this doc featuring an overview of the users, roles and privileges, can be made better OPENMRS-REFERENCE-CONFIGS.docx (7.8 KB)