Among the methods of customizing client startup, GNUmed has implemented a construct of "workplaces". Workplaces make it possible, within a single praxis, to perform a variety of jobs (modes of work) in a consistent way.

A workplace is designated to be loaded by use of the name = parameter positioned within the [workplace] group within a config file. A workplace
  • is a named entity which stores, in the backend, a combination – a "set", if you like – of the following:
    • the workplace name
    • which plugins to load, and in what order, in the toolbar
    • as a consequence of the above-specified list, the self-attachment of these plugins' names to various GNUmed menus
    • many of the GNUmed menu configuration settings concerning encounters and episodes
  • may be
    • provided as part of a GNUmed client release
      • effective with release 0.5, these include
        • Front Desk
        • Clinician
        • Local Default (when none was already specified; plugin load list and load order will be determined by what was available at creation)
    • created or modified by users via GNUmed > Master data > Workplace profiles
    • emulated, as a workaround in the case of broken plugin problems, by temporary use of the special name System Fallback

Examples might be "Ultrasound Room", "Exam Room 3", "Front Desk", "Medical Records Clerk" – whatever you want.

To configure the plugins go to the menu item "GNUmed > Master data > Manage lists > Workplace profiles" to see a list of existing workplaces (the active one being pre-selected). Select the workplace of interest and press the "Edit" button, or Add a new workplace. At left will be a list of the available plug-ins. At right will be a list of plug-ins (if any) that have so far been added. The top-down order of the plug-ins on the right will determine their load-order (left to right) in the GNUmed client. Presently it is not possible to re-order them in-place, however you can achieve a re-ordering by removing as many as necessary to then re-add them from the list at left.

Deletion of a workplace offers the choice of whether to delete the name only (as a result of which it will disappear from the list), or whether to delete the entire workplace, complete with associated (saved) configurational settings. As long as the latter has not been deleted, the old workplace with settings can be restored by re-designating the exact original workplace name into a configuration file.

For more on config files, see here. For more on customizing client startup, see here.

From an email of Karsten's re gnumed.conf on Dec 30, 2005

The workplace is determined by the config file. The client can be started with different config files - also concurrently. So I could have a client instance configured for the reception area and another configured for an exam room running side by side on the same machine. It simply depends on which configuration file the client is started with. $home/.gnumed/gnumed.conf is just the default config file which is used in the absence of an explicit command line option. It is also this value which determines some of the options in the backend.

Just set up two links with different config files in which you define the workplace you want and click on the one you want to run.

Say, Tuesday afternoon you are doing ultrasound scans in room A while the rest of the week you ain't doing any scans there but rather do standard physical exam work.

So on the machine in room A you set up two entries in the GNUmed menu under your account. You might name them "GNUmed - Ultrasound" and "GNUmed - PE". The first is called with --conf-file=$home/.gnumed/gm-ultrasound.conf while the second is called with --conf-file=$home/.gnumed/gm-pe.conf.

Now, every Tuesday afternoon you startup a client instance "GNUmed - Ultrasound". You can leave the "GNUmed - PE" clients you started in the morning running alongside w/o problems.
Topic revision: 20 Jan 2013, JamesBusser
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback
Powered by Olark