Click or drag to resize
TOPICA Basic Class OrgUnitType

[This is preliminary documentation and is subject to change.]

The OrgUnitType class models the types of organizational units.

Each OrgUnit is related to exacly one OrgUnitType object.

OrgUnitType properties

Property

Type

Description

Type

String

Key field

Usually an abbreviation of the name - e.g. "hosp" for "Hospital"

Name

String

The name displayed in the user interface - singular form, e.g. "Hospital"

NamePlur

String

The name displayed in the user interface - plural form, e.g. "Hospitals"

DisplayAncestor

String

The type of some other OrgUnitType object, that identifies the ancestor used to construct the full name (property FullName) of the OrgUnit.

When DisplayAncestor is blank, OrgUnit.FullName will have same value as OrgUnit.Name

When DisplayAncestor is NOT blank, the system will locate the ancestor with the given type, and concatenat the name of this ancestor to the front of the OrgUnit in question, and return this concatenaed string as the value of OrgUnit.FullName.

The reationale behind this is, that e.g. hospital departments may may very generic names e.g. "Medical department" or "Surgical department". To display such departments it is usefull, if the hospital name is prepended, e.g. "First hospital, Medical department" and "Second hospital, Medical department".

ClassName

String

Used to group OrgUnitType objects with access permissions.

Users employed by an OrgUnit in a class may not edit assign permissions in any other class to users.

This may be used to define some permissions as usable for central users and other permisison as usable for decantral users. I.e. a user employed centrally may not assign decentral permissions to users - and the other way round.

Hidden

Boolean

Hidden in hierarchy

IsInstitution

Boolean

Institution status.

Setting institution status on a specific level in the organization, enables some extra functionality at that level. Example:

  • Mark the hospital type as institution.

  • No matter how many levels of deparmtnes and sub-departments are created below a hospital, the user interface will contain links to navigate from any department directly to the hospital.

  • With a hospital in context, it is possible to see all functions / spacialties on all departments in that hospital.

  • Institution status is widely used in the accreditation sub-system.