Function documentationOrder Type for Service Ordering: Structuring Tab Page

 

On the Structuring tab page you determine the components from which a service ordering order of a specific order type is compiled.

In service ordering the application components are available as User Interface Building Blocks (UIBBs).

Note Note

Service ordering uses an intersection of application components, which are also available for the clinical order. The division into header and item components is not relevant for service ordering, as a service ordering order only ever consists of one item.

End of the note.

Features

You use the Patient Header application component to determine that the Patient Header is used for the order type within Smart UI. The patient header is mandatory and the system automatically assigns it to every order type.

In service ordering you can use the following application components:

  • Patient Header

    This application component is assigned to every order type by default. This ensures that the patient header, with the patient-related information, is contained in all order types.

    You can find information on this in smart UI under Patient Header.

  • Item Data

    This application component is assigned to every order type by default. You use this application component to define information on the order item, for example, the treatment organizational unit, the desired date, the case and the item status.

  • Order Data

    This application component contains the fields for entering the order-related information, for example, the initiator, the priority and the status.

  • Comment

    This application component provides a text field in which you can enter a comment on the service ordering order.

  • Questions

    This application component provides a text field in which you can enter a question for each order item.

  • General Medical Data

    This application component contains the fields for entering general medical information on the patient, for example, short anamnesis and risk factors.

  • Radiology

    This application component contains the fields for the contraindications necessary for the radiology examinations, and for the radiological patient data. This includes, for example, height and weight as well as metal implants and pacemaker.

  • Services

    This application component provides the fields for the service which you wish to order.

  • Surgical Procedure indicator

    This application component provides the fields for entering the surgery indicators, for example, whether an anesthetist is required.

  • Surgical Team

    This application component provides the fields for entering the surgical team, for example, the operating surgeon, surgery assistant, anesthetist.

  • Transport Order

    This application component provides the fields for entering a transport order.

    For the Transport Service OU field the system checks whether the OU parameter N1OEFD is set for the entered OU. In this case the system presets the field with the transport service OU of the initiating OU.

  • Transport Type

    This application component provides the field for entering the transport type. This field is particularly relevant if you do not i.s.h.med transport service.

  • Outbound Connectivity

    This application component activates the sending of information from an order to the existing external systems whenever you change, save or delete this order.

The following application components are provided to enter services for the cardiology department:

  • Cardiology

    This application component contains the cardiovascular risk factors in addition to the general patient data like weight and height.

  • ECG/Pacemaker

    This application component provides the fields with details about the relevant medication and aggregates.

  • Cardiac Catheter

    This application component contains fields with the following information for performing the services:

  • Patient Consent

  • Surgical Intervention and Time of Surgical Intervention

  • Relevant Examination Results

You also define the following on the Structuring tab page:

  • Design Elements

    A design element compiles application components. In the clinical order each design element represents one tab page.

    Service ordering does not take design elements into account. However, in order to be able to also use an order type in the clinical order, you must also define design elements for service ordering order types.

  • Layout

    You use the Configure Layout function to determine the layout of an order type.

    You use the Personalize function to divide the order type into areas and can determine a layout for each area.

  • Standard Order Type

    You can flag an order type as a standard order type. You can determine standard order types for the surgery, services and radiology areas. If you select a service which is not explicitly assigned to an order type, the system uses the standard order type.

You can find further information on the Structuring tab page and on the integration of the application components into the order types in Customizing under Start of the navigation path SAP Healthcare - 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.

You can find introductory information on the customizing of service ordering under Start of the navigation path Industry-Specific Component Clinical System Next navigation step Smart UI Next navigation step Applications Next navigation step Service Ordering Next navigation step General Information on Service Ordering End of the navigation path.