# Managing organizations and your praxis

- Managing organizations and your praxis
  - Managing organizations
  - Managing your praxis
    - Concepts
    - Management

## Managing organizations

GNUmed allows for managing organizations with a granularity of one-level. One can define an organization as such, with name and type to which any number of units (deptartments, branches, sites, locations, offices, ...) can be attached, each with a name, optional type, optional address, and optional communications channels. It is entirely up to the user to decide which level of real world organizations to map into this two-level structure. The choice will depend on what's of most use to the GNUmed installation in question. Examples:

- organization "District General Hospital"
  - unit "Dept. of Pediatrics"
  - unit "Dept. of Surgery"
  - unit "Dept. of Internal Medicine"

- organization "Department of Internal Medicine at DGH"
  - unit "stroke unit"
  - unit "cath lab"
  - unit "rehab"
  - unit "ICU"
  - unit "GE"

- organization "Stanton & Associates GP Offices"
  - unit "Elwood Creek branch"
  - unit "Startford Mall branch"
  - unit "DGH in-house branch"
  - unit "mobile services branch"

## Managing your praxis

### Concepts

Conceptually, your praxis is an organization just like any other. Each site (location, office, ...) of your praxis is a branch therof. And in fact, praxis branches are defined by declaring units of organizations to be a branch of your praxis. There are a few constraints on how you can set up your praxis:

- all branches must be units of one and the same organzation, or, in other words, there can only be one praxis per database
- you can declare only some of the units of an organziation to be praxis branches, in other words, not all units must be branches

This allows for the following scenarios:

A GP has two sites and an office at DGH:

- organization (= praxis) "GPs Assoc"
  - branch "The Mall"
  - branch "Downtown"
  - branch "DGH"

and they all share one database across town (which should be legal everywhere as they serve the same set of patient-doctor relationships).

A physical therapist has branches at The Mall (self-employed), the DGH (employed by hospital), and the Catholic High Internal Hospital (employed be the Lutheran Church owning the hospital). As such the sets of therapist-patient are legally distinct (even if sometimes concerncing the same patient or even continuant in terms of care). Here, one would run three databases, one at each hospital and one at the private practice. It is up to the user to decide whether to make the praxis branches units of the general organization of each hospital inside the appropriate database, eg:

- organization "DGH"
  - unit (= branch) "dept of PT"
  - other units of the hospital which need not be branches of the PT

(this allows for re-using things defined for the organization "DGH" in, say, documents, when working in the branch "dept of DGH PT")

Or else to define an organization alongside the actual DGH:

- organization "PT@DGH"
  - unit (= branch) "my PT"

The latter approach can be (ab)used to still unify all three branches into one remotely-connected database despite that not being encouraged due to likeliness of confidentiality concerns:

- organization "my praxis at DGH/Catholic/The Mall"
  - unit "The Mall"
  - unit "DGH"
  - unit "Catholic"

Whichever way one defines things after startup, there will always be exactly one active praxis branch - this is supposed to be the one you supposedly logged in from.

### Management

At startup GNUmed will:

- if there are no organizations at all: auto-create an organization, unit, and praxis branch for you
- if there are organizations but no praxis branches: let you select (and manage from there) an organizational unit to be your praxis branch
- if there is only one praxis branch: make that branch the currently active one (where you logged in from)
- if there are several praxis branches: ask which one you log in from