Segmentation Use Cases

The following use cases are generic examples and scenarios, which are intended to answer some questions you might have about how common segments can be applied.

Question: Both Biomed and Facilities are contained in one database. There are five Facilities segments and six Biomed segments. They want to share codes and assets with in Biomed or Facilities, but not with each other.

Answer: They will create a number of common segments, and link those new common segments to specific user segments. That will allow them to share data across different user segments, without Biomed users seeing Facilities data and visa-versa.

Question: An Asset is in common segment 2. Where do the code values come from?

Answer: They will be pulled from common segment 2 and the system segment. If common segment 2 has any parents, these codes will also be included.

Question: A Resource is in user segment 1. User segment 1 is a child of common segments 10 and common segment 10 is a child of common segment 12. Where do the code values come from when creating a Resource in user segment 1?

Answer: They would come from user segment 1, common segments 11 and 12, and system segment.

Question: A database contains five Facilities segments. Two of those segments want to share data, and the other three want to share data. How can we accomplish this?

Answer: A common segment will be created, and linked to Facilities segments 1 and 2. Another common segment will be created, and linked to Facilities segments 3, 4 and 5.

Question: A user segment is currently linked to only 1 common segment. There are a total of 2 common segments in the database. Each common segment contains the Account Code ‘ABC’. What happens when the TMS Administrator attempts to make the 2nd common segment a child of the first?

Answer: The application will prevent this relationship from being put into place. Since codes have to be unique in a user segment, this includes the system segment and all common segments the user segment is mapped to.

Question: A three hospital network might want to share corporate account and location codes throughout TMS, but their Biomed and Facilities departments want their own skill, category, and type codes. Certain assets are also shared between the Biomed departments at the different hospitals.

Answer: An All Common segment is created as a child of the system segment and contains account and location codes. The All Common segment has two children: Biomed Common and Facilities Common. Assets can be created in the Biomed Common segment using account codes from the All Common segment. Each Biomed User Segment has access to the codes in the Biomed Common, the All Common, and the System Segment. Work order default values can be set for all Biomed segments by setting them for the Biomed Common segment.

Question: How would this work for a three hospital network, each with Biomed and Facilities segments. Hospital 3 also uses TMS for IT.

Answer: The system defines information common to all seven segments or common across departments in any single hospital in the “All Common” segment. Skills for each type of segment (Facilities, Biomed, or IT) are defined in common segments for each department type.