• DATE_CREATED
• DATE_MODIFIED
• DESCRIPTION
• DISCOUNT
• ECOMMERCE
• EXPIRATION_DATE
• FINAL_PRICE

• IDENTIFIER
• KNODE_ID
• NAME
• OBJECTIVES
• PKG_ID
• STATUS
• XACCESS

The date when the PKG record was created in Knowledge Link.

Example: 10/24/2006

Values:
List of values not available

The date when the PKG record was last updated in Knowledge Link.

Example: 11/13/2007

Values:
List of values not available

Text (in mixed case) that explains what the package includes. See also IDENTIFIER, NAME, and PKG_ID.

A package is a set of courses that may be taken in any order, and that can be assigned to a business unit using one assignment specification. A business unit--also known as a BU, role, Knowledge Node, or K Node--is a set of one or more Knowledge Link users. Packages are assigned to business units that correspond to bureaucratic groups reflecting various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (members whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation).

For example, say that trainees are usually required to take both course A and course B. Package P includes courses A and B. If business unit X is required to take both courses, it is more convenient to specify that P is assigned to X than to specify each course separately. See also the KNODE_CRS_JOIN table.

A package usually (but not always) includes at least one course. A given course may belong to more than one package. You can identify a package by its PKG_ID or IDENTIFIER. See also the PKG_CRS_JOIN table.

Example: Unit Specific Competencies for Med Surg. 4 South Only.

Values:
List of values not available

This data element currently is not used.

This data element currently is not used.

If the package is inactive (STATUS=0), this is the date when it became inactive. See also STATUS.

In most cases, if the package is active, EXPIRATION_DATE is null. However, it is possible for a package to have its status change from active, to inactive, and back to active. In such a case, EXPIRATION_DATE might still store the date when the package became inactive, even though the package is active again.

Example: 12/6/2007

Values:
List of values not available.

This data element currently is not used.

A string that uniquely identifies the package to Knowledge Link users. The IDENTIFIER may include numerals and/or letters and/or other characters. If the IDENTIFIER includes letters, they may be in upper case, lower case, or mixed case. See also DESCRIPTION, NAME, and PKG_ID.

A package is a set of courses that may be taken in any order, and that can be assigned to a business unit using one assignment specification. A business unit--also known as a BU, role, Knowledge Node, or K Node--is a set of one or more Knowledge Link users. Packages are assigned to business units that correspond to bureaucratic groups reflecting various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (members whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation).

For example, say that trainees are usually required to take both course A and course B. Package P includes courses A and B. If business unit X is required to take both courses, it is more convenient to specify that P is assigned to X than to specify each course separately. See also the KNODE_CRS_JOIN table.

A package usually (but not always) includes at least one course. A given course may belong to more than one package. You can identify a package by its PKG_ID or IDENTIFIER. See also the PKG_CRS_JOIN table.

Examples: MS100; EHRS / Radiation Safety; 10366

Values:
Refer to the PKG table for values.

The number used within the Knowledge Link system as the unique identifier for the business unit that is the owner of the package and all of the courses in the package. The owner's name and identification code are stored in the KNODE table (in NAME and IDENTIFIER, respectively), where PKG.KNODE_ID = KNODE.KNODE_ID.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. The business units to which Knowledge Link users are assigned are known as KPs, or Knowledge Positions. (See the KNODE_USER_JOIN table.) Some KPs denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system.

Business units are organized into a hierarchy. In the business unit hierarchy, the parent of a KP can be a Knowledge Community (KC) or a Knowledge Microcommunity (KMC). KCs and KMCs are the types of business units that are package owners. The KCs that own packages correspond to University orgs. or to University of Pennsylvania Health System (UPHS) entities (process levels) or departments (cost centers or accounting units). A KMC identifies a group of trainees from unrelated UPHS departments.

A package of course versions can be created by a Knowledge Link user if: (1) that user is assigned to a KP denoting a group that has administrator or junior administrator privileges, and (2) the parent of that KP is the same as the owner of the course versions, or falls above the course versions' owner in the business unit hierarchy. A package has the same owner that its course versions have.

The owner of the package is one of the criteria used to determine what packages (if any) are included on the list of packages that a given user can assign. Two of the other criteria are the package's access level (XACCESS) and the user’s privileges (determined by the privileged KP(s) to which the user is assigned). Packages can be assigned by Knowledge Link users with administrator, junior administrator, or instructor privileges.

• If the user has administrator privileges, the user can assign any package to any business unit, regardless of the package’s owner and XACCESS.
  
• If the user is assigned to a KP for a group whose privileges include the ability to assign packages, and that KP’s parent is a KMC, the package’s XACCESS is irrelevant. The list of packages that the user can assign will include a given package only if that KMC is the package’s owner.
  
• Otherwise, a given package is included on the list of those that the user can assign if the user is assigned to a KP denoting a group whose privileges include the ability to assign packages, the parent of that KP is a KC (not a KMC), and one of the following is true:
  • XACCESS is 167 (Local), and the KC is the same as the package’s owner.
  • XACCESS is 166 (Inheritable), and the KC is the same as the package’s owner, or falls above the package’s owner in the business unit hierarchy.
  • XACCESS is 167 (Global). The package’s owner is irrelevant if the package's access level is Global.

Example: 56164

Values:
List of values not available

The name of the package, stored in mixed case. It is possible for more than one package to have the same value for NAME. See also DESCRIPTION, IDENTIFIER, and PKG_ID.

A package is a set of courses that may be taken in any order, and that can be assigned to a business unit using one assignment specification. A business unit--also known as a BU, role, Knowledge Node, or K Node--is a set of one or more Knowledge Link users. Packages are assigned to business units that correspond to bureaucratic groups reflecting various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (members whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation).

For example, say that trainees are usually required to take both course A and course B. Package P includes courses A and B. If business unit X is required to take both courses, it is more convenient to specify that P is assigned to X than to specify each course separately. See also the KNODE_CRS_JOIN table.

A package usually (but not always) includes at least one course. A given course may belong to more than one package. You can identify a package by its PKG_ID or IDENTIFIER. See also the PKG_CRS_JOIN table.

Example: Medical Surgical Core Competencies - PPMC

Values:
List of values not available

This data element currently is not used.

A numeric value used to uniquely identify the PKG record within the Knowledge Link system. The PKG table has one record per package. See also DESCRIPTION, IDENTIFIER, and NAME.

A package is a set of courses that may be taken in any order, and that can be assigned to a business unit using one assignment specification. A business unit--also known as a BU, role, Knowledge Node, or K Node--is a set of one or more Knowledge Link users. Packages are assigned to business units that correspond to bureaucratic groups reflecting various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (members whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation).

For example, say that trainees are usually required to take both course A and course B. Package P includes courses A and B. If business unit X is required to take both courses, it is more convenient to specify that P is assigned to X than to specify each course separately. See also the KNODE_CRS_JOIN table.

A package usually (but not always) includes at least one course. A given course may belong to more than one package. You can identify a package by its PKG_ID or IDENTIFIER. See also the PKG_CRS_JOIN table.

Example: 10848

Values:
Refer to the PKG table for values.

A numeral indicating whether the package is active (1) or inactive (0). See also EXPIRATION_DATE.

A record can be created to assign a package to a business unit only if the package is active. See also the KNODE_CRS_JOIN table.

Values:
0 (the package is inactive)
1 (the package is active)

A numeric code indicating the package's access level, which is one of the criteria used to determine whether a given Knowledge Link user can assign the package to a business unit.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. The business units to which Knowledge Link users are assigned are known as KPs, or Knowledge Positions. (See the KNODE_USER_JOIN table.) Some KPs denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system.

Business units are organized into a hierarchy. In the business unit hierarchy, the parent of a KP can be a Knowledge Community (KC) or a Knowledge Microcommunity (KMC). KCs and KMCs are the types of business units that are course version owners. The KCs that own packages correspond to University orgs. or to University of Pennsylvania Health System (UPHS) entities (process levels) or departments (cost centers or accounting units). A KMC identifies a group of trainees from unrelated UPHS departments.

The package’s XACCESS, the package’s owner (KNODE_ID), and the user’s privileges are among the criteria that determine whether the course version is included in the list of course versions that the user can assign. Note:

• If the user has administrator privileges, the user can assign any package to any business unit, regardless of the package’s owner and XACCESS.
  
• If the user is assigned to a KP for a group whose privileges include the ability to assign packages, and that KP’s parent is a KMC, the package’s XACCESS is irrelevant. The list of packages that the user can assign will include a given package only if that KMC is the package’s owner.

There are three kinds of XACCESS:

• Global—the package is included on the list of those that the user can assign if: (1) the user is assigned to a KP denoting a group whose privileges include the ability to assign packages, and (2) the parent of that KP is a KC (not a KMC). The package’s owner is irrelevant if XACCESS is 165 (Global).
  
• Inheritable—the package is included on the list of those that the user can assign if: (1) the user is assigned to a KP denoting a group whose privileges include the ability to assign packages, (2) the parent of that KP is a KC (not a KMC), and (3) that KC is the same as the package’s owner, or falls above the package’s owner in the business unit hierarchy. 166 (Inheritable) is the default value for XACCESS.
  
• Local—the package is included on the list of those that the user can assign if: (1) the user is assigned to a KP denoting a group whose privileges include the ability to assign packages, (2) the parent of that KP is a KC (not a KMC), and (3) that KC is the same as the package’s owner.

The description for XACCESS is LMS_DEFINITION.NAME where PKG.XACCESS = LMS_DEFINITION.DEF_ID.

Values:
165 (Global)
166 (Inheritable)
167 (Local)