NHS Trusts today may be very large, multi site enterprises, and even if not will be structured into many different derpartments.
In order to tailor the individual user’s experiance of the system it may be very desirable to limit the data vissible to only that which is relevant to the users’s actual role. An EBME maintenance specialist does not need to know about other types of maintenance tasks. A stores clerk in a large trust may only have responsibilities relating to one stores location.
The Eclipse-fm® user login profile optionally includes constraining to only the data for a particular combination of the following elements:-
- Organisation
- Derived from your own Organisation Codes
- Site
- Derived from your own Site codes
- Equipment such as but not limited to
- EBME
- EME
- IT Equipment
- Standard
- Test Equipment
- Vehicle
- Store
- Derived from your own Store IDs
- Task Type
- Derived from your own Task types
Examples – a member of staff might only have access to
- A particular site or organisation, a combination of both or a group of several organisations and sites.
- Only “EBME” tasks relating to that site, organisation or site/organisation combination.
- Only EBME and EME tasks relating to Sites ABC and organization XYZ
- Only a particular store in a particular site
Many different elements may be used to define a user profile, and any one element may be used multiple times with different values without noticeably affecting performance.
Usage
- Set up “Help Desks” that appear to be for a particular site, or for a particular task type
- Allow higher level management to access to management information from all Sites, Define higher level responsibility, e.g. as authoriser of Purchase Orders at a trust level, generated by staff who only see their own site or store details.
- enable contract staff to access tasks defined to be for them, and no others
- e.g. only EBME and EME tasks within organisation XYZ
