Вы находитесь на странице: 1из 3

Base Item Definition Base items can contain system objects, system functions, and presettings for obj

ects such as diagnoses, documents, and procedures. Functions include, for example, the display of objects such as document printout s 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 documentati on 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 defini tion application. The base item is then available for execution. Depending on th e 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 Ite ms. Structure The user identifies a base item using its name. This must be unique and is check ed by the system. Base items on customer systems must begin with A Z, a z, 0 r _ . 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 a re in their institution. The base item type characterizes the base item. One possible specification is, f or example the document. Each base item must be assigned to exactly one base ite m type. The initial action determines which of the functions defined in the base item ty pe 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 typ e is called when the base item is repeatedly executed. It can only be called onc e 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 im plementation of the BAdI belonging to the base item type before and after the ac tion defined in the base item is executed. This function is not available for al l base item types. The status identifies the changeability of the base item and its completion (rel ease). 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 item s can also be assigned and executed. When a base item is deleted it receives a deletion indicator. The deletion indic ator is a prerequisite for the physical deletion. You can assign base items to a group. Grouping simplifies the search for base it ems in the catalog of available base items. Integration Base items are connected to the transport and correction system. When a base ite m is edited, the changes are listed in a transport request, depending on the cli ent settings. Changes are not possible on a productive client. Create base items on your test or customizing client. Test them, activate them a nd transport the activated base items to your productive client. Execution Base items are executed in several steps. Depending on whether a base item for a n object has already been executed, different functions are triggered. 1. BAdIs belonging to the base item type are called with the filter value Bef ore Execution. This step is ignored if the BAdI has no default implementation. 2. Execution of the initial or repeat action determined in the base item. The action executed depends on whether the base item has already been executed.

9 o

3. Save the result of the base item execution. 4. BAdIs belonging to the base item type are called with the filter value Aft er Execution. This step is ignored if the BAdI has no default implementation. Some base item types have a different procedure. You can find further informatio n under the corresponding base item type. Example You have created a base item which you wish to use in a task of the Outpatient C linic documentation work station. 1. In template management (transaction N2WLD) create a task template and assi gn the created base item to this. 2. Activate and save the task template. 3. Branch to the Outpatient Clinic documentation work station. 4. Call a patient with a situation and add a task from the new task template to the situation. 5. Choose the new task from the task list. The base item is executed. Base Item Type System object which provides object-dependent data and functions for base items. Each base item is based on a base item type. The system calls the functions according to the actions which you determined in the base item. A base item type provides different functions for processing base items. Base item types form the basis for the creation of base items, which are used in , for example, treatment pathways or the documentation work station. Structure The work area determines the availability of a base item for a used component. E ach component corresponds to exactly one work area. You must release the work ar ea for each base item type in order to be able to use it. The possible actions of the initial action and the repeat action are determined as well as the presetting of the fields during the creation of a new base item. In the base item type you determine which BAdI should be called before or after the execution of the action. This function is not available for all base item ty pes. You can find more information in the documentation for the respective base item type. The following base item types are available: Administrative Services Base Item Type Request Base Item Type Medication Order Base Item Type Drug Administration Base Item Type BAdI Base Item Type Treatment Pathway Base Item Type Surgical Documentation Base Item Type Diagnoses Base Item Type Document Base Item Type Form Printing Base Item Type Clinical Order Base Item Type Complications Base Item Type Material Entry Base Item Type Medical Services Base Item Type Surgery Times Base Item Type Nursing Plan Base Item Type Nursing Service Base Item Type Problems Base Item Type Procedures Base Item Type Assign Situation Base Item Type Team Entry Base Item Type Textual Order Base Item Type

Transaction Base Item Type URL Base Item Type Progress Entry Base Item Type Vital Sign Entry Base Item Type Vital Sign Planning Base Item Type Integration You can derive any number of base items from a base item type. Depending on the system object of a base item type, further components may be ne cessary. You can find more information in the documentation for the respective b ase item type.