Function documentationStructuring

 

On the Structuring tab page you determine the type structure of the parts of which an order type consists. Here you define the template for the order header and the order items.

The composition of an order type depends on whether it is an elemental order type or a profile type.

Note Note

On the Other tab page, the system administration can define appointment dependencies for profile types for the planning of the order items.

If you remove an elemental order type, for which appointment dependencies were already defined in the profile type, from the Structuring tab page, the system also removes all appointment dependencies of this elemental order type from the Other tab page.

End of the note.

To structure the order header or order items of a clinical order using the relevant order type used by the user as a basis when creating a clinical order, you must determine the tab pages for the following areas:

If you have defined the tab pages for the order type, you determine for each tab page which component(s) should be used.

Note Note

You can configure application components (standard and customer-specific) as order type-related, if they are intended for this. The system flags configurable application components on the Structuring tab page using - (-).

If you choose the hotspot on this indicator, you access the component-specific configuration dialog.

As standard the Context application component is currently available as a configurable component.

End of the note.

You can find further information in the Implementation Guide under Start of the navigation path Industry-Specific Component Clinical System Next navigation step Clinical Order Next navigation step Clinical Order Basic Data Next navigation step Set Up Order Types for Clinical Order End of the navigation path.

Example

You wish to define the order type ZAMBULANZ for the clinical order, which consists of the following header and item components:

  • Patient header (header component)

    The system automatically enters the header component in the type structure.

  • Order data (header component)

    The system automatically enters the header component in the type structure.

  • General Medical Data (Header Component)

    When creating a clinical order with this order type the user should be able to enter the general medical data on the Medical Data tab page.

    You must therefore create a tab page with the label Medical Data.

  • Waiting list (header component)

    The user should be make waiting list management entries on the Waiting List tab page.

    You must therefore create a tab page with the label Waiting List.

  • Services (item component)

    The user should be able to enter the services for the order item on the Treatment tab page.

    You must therefore create a tab page with the label Treatment.

  • Transport order (item component)

    The user should be able to enter the transport order on the Transport Patient tab page.

    You must therefore create a tab page with the label Transport Patient.

In this example, the type structure has to contain the following entries in the order specified:

Element

Type

Patient header

SAP header component

Order Data

SAP header component

Medical Data

Tab Page

General Medical Data

SAP header component

Waiting List

Tab Page

Waiting List

SAP header component

Treatment

Tab Page

Services

SAP component

Transport Patient

Tab Page

Transport Order

SAP component