Definition

Base items can contain system objects, system functions, and presettings for objects such as diagnoses, documents, and procedures.

Functions include, for example, the display of objects such as document printouts or the display of an URL, but also the integration of external applications.

Base items are used in components such as treatment pathways and the documentation work station.

In the base item type you determine which object a base item refers to.

Use

You usually connect base items with objects of the used components in the definition application. The base item is then available for execution. Depending on the component, some other steps may be necessary. You can find further information in the documentation of the relevant components.

You can find information on how to create a base item under Processing Base Items .

Structure

The user identifies a base item using its name. This must be unique and is checked by the system. Base items on customer systems must begin with A – Z, a – z, 0 – 9 or _ . You can describe a base item in more detail using its description.

A base item refers to an institution. Components can only use base items which are in their institution.

The base item type characterizes the base item. One possible specification is, for example the document. Each base item must be assigned to exactly one base item type.

The initial action determines which of the functions defined in the base item type is called the first time the base item is executed. It is executed once only for each object.

The repeat action determines which of the functions defined in the base item type is called when the base item is repeatedly executed. It can only be called once the initial action has successfully been executed. The number of calls is not restricted.

You can use the filter values Before Execution and After Execution to call an implementation of the BAdI belonging to the base item type before and after the action defined in the base item is executed. This function is not available for all base item types.

The status identifies the changeability of the base item and its completion (release). A base item, which is still in processing and in testing, has the status Inactive . As soon as the base item can be used, you should set the status Active . Only base items in Active status can be productively used on a client. On all other client roles, such as for example, test or customizing, inactive base items can also be assigned and executed.

When a base item is deleted it receives a deletion indicator . The deletion indicator is a prerequisite for the physical deletion.

You can assign base items to a group . Grouping simplifies the search for base items in the catalog of available base items.

Integration

Base items are connected to the transport and correction system. When a base item is edited, the changes are listed in a transport request, depending on the client settings. Changes are not possible on a productive client.

Create base items on your test or customizing client. Test them, activate them and transport the activated base items to your productive client.

Example

You have created a base item which you wish to use in a task of the Outpatient Clinic documentation work station.