Kontakt

Ansicht
Dokumentation

Outpatient Clinic/Service Facility Work Station - How To Use ( RELNISHMED_463_NWPAMB_10 )

Outpatient Clinic/Service Facility Work Station - How To Use ( RELNISHMED_463_NWPAMB_10 )

ABAP Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Outpatient Clinic/Service Facility Work Station - How To Use

Use

The Outpatient Clinic/Service Facility work station replaces the worklist, waiting list and visit management overview, and provides standardized parameters, functions and layouts in a single environment.

This release note gives you information on how to use the Clinical Work Station interface and the Service Facility/Outpatient Clinic view type in your facility/clinic.

Hinweis: If you do not use IS-H*MED, please refer to the section at the end of this release note.

What Information Does This View Type Display?

The idea behind this new view type is similar to the one behind the care unit work station view type, only that it provides support for users in various forms of outpatient organizations. The new view type meets the information demands of service facilities (electronic requests, planning), outpatient clinics and various hybrid forms of these types of organization.

In order to satisfy these requirements, the Outpatient Clinic/Service Facility work station displays the following information:

  • Patient preregistration details (IS-H*MED)
  • Visit appointments that you booked using Outpatient Clinic Management or that you preregistered or planned
  • Medical services that have been requested, are planned, or have been performed (IS-H*MED)
  • Outpatient visits
  • This information is displayed in tabular form. The view type provides a range of flexible sorting and filter options. In fact, you can sort and filter the table using any of the fields in the field list.

By defining settings in a selection variant you can, for example, specify that only services should appear. For more information about configuring a selection variant, see the section entitled Configuring Selection Variants below.

Scenario for using the work station on a service facility: if a request for a patient is performed and documented, this generates an outpatient visit for the service facility in question. An appointment and a quantity of documentation (such as team data, findings, and discharge summary) can be linked to the outpatient visit and services.

As was the case in the worklist, information on the appointment, services and visit is not displayed separately - only the smallest element (in this case, the service) is displayed. Details of the appointment and visit are represented as dependent attributes of the service - for example, the visit type is always displayed for each service.

Other examples of interdependencies like this include:

  • Appointment/visit

If an appointment is linked to a visit, only the visit is displayed
  • Visit/services (IS-H*MED)

The services are displayed
  • Appointment/services (IS-H*MED)

The services are displayed

If you do not want any services at all to be displayed in a view, your system administrator will have to configure the selection variant accordingly.

Field List and Layout

Each of the elements that can appear in the view type (services, appointments, visits, preregistrations) has its own specific field list. In the transaction for maintaining layout variants, you can define a filter for each element.

A field that provides more details about the service itself (the "service code" field, for example) is of no relevance to visits, so it does not appear with a value. An attribute of a visit or an appointment, on the other hand, will be displayed even for services that are linked to the visit or appointment.

It should also be noted that some fields are used for several elements in the Outpatient Clinic/Service Facility work station. The point of this is to keep the list width to a minimum - especially when services, appointments and visits are all to be denoted as such in a specific view.

Examples:

  • An example of a field that is used for several elements is the Status field. This field is used to show the service status for services, and the visit status for visits. From a technical point of view, the fields are different - but from the point of view of the end user, this field provides the same type of information.
  • Another field like this is the Comment field. This field contains
  • The scheduling type for appointments

  • The service short text for services and preregistrations (IS-H*MED)

  • The medical text or comment text for visits

For more information on this topic, refer to the SAP Library and the F1 Help for the various fields in the view type.

Configuring Selection Variants

You can use a selection variant to make settings for a specific work station.

You can define a selection variant for each view. When you go to define a selection variant, you can make settings on three tab pages:

  • On the General tab page, you specify parameters that are generally applicable - for example,
  • Organizational unit

  • Date

  • Time

  • Elements to be displayed

You also use this tab page to specify whether the system should display appointments, services and movements.
  • On the Visits/Appointments tab page, you specify selection criteria that are relevant mainly to visits - for example,
  • Visit type

  • Visit status

  • On the Services tab page, you make settings that apply to services. This tab page is displayed only if you are using IS-H*MED. For example, you can state that only specific service statuses, or specific types of service and medical documentation should be used (for example, findings pertaining to service are released).

The fact that all document statuses can be displayed represents a major improvement in the Outpatient Clinic/Service Facility work station. Within a single view, you can select services on the basis of the medical documents entered. This means that you can display combinations of information that meet typical user needs - all in a single view. Examples include:

  • Display all examinations performed in the last n days for which no findings have been entered
  • Display all examinations whose findings have not yet been proofread
  • Display all examinations whose findings have not yet been released

In all these cases, the only thing you have to ensure is that the document status can be used to map these processes. Remember, though, that it only makes sense to use document statuses that are supported by the document during the work process.

Outpatient Clinic Support

In a typical outpatient clinic, much revolves around appointments and the patient visits they result in. When an appointment is scheduled and the patient is admitted, the patient is put on the outpatient clinic's waiting list. At this point in time, though, it is not necessarily known what course of treatment the patient will require, or indeed what future course of action will be pursued for the patient.

The main elements of this view are:

  • Provisional appointments
  • Patient admission
  • Patient registration
  • Functions from the outpatient tracking system (treat, transfer)
  • Diagnostic documentation (IS-H*MED)
  • Service documentation (IS-H*MED)
  • Medical documentation (IS-H*MED)
  • Patient organizer (IS-H*MED)
  • Admission of outpatient for inpatient treatment (inpatient admission)
  • Arranging follow-up visits using integrated appointment planning
  • Preregistration of patient far in advance (IS-H*MED)

Service Facility Support (IS-H*MED)

A service facility is a facility that has a clear-cut, well defined range of services. Inpatients who require specific examinations are usually sent to service facilities for these examinations. Normally, the information to be provided by the examination in question has been clearly defined.

That is why it is possible to define requests for the medical services that are required. This information should also appear at the view level. It is recommended that you include the following elements in the view:

  • Appointment planning for services
  • Service documentation
  • Diagnostic documentation
  • Medical documentation
  • Request for further examinations
  • Arranging of follow-up visits

Using the View to Monitor Documentation of Findings (IS-H*MED)

You can use the Service Facility/Outpatient Clinic view type to define views that allow you to monitor the quality of documentation.

You could, for example, define a view for displaying all services that have been performed but for which no findings have yet been entered. In this case, you would need to include the following combination of selection fields:

  • Service status
  • Document category
  • Document status

The system administrator must add the following functions to the function list so that you can generate service documentation and medical documentation on the service:

  • Release of service
  • Medical documentation (diagnoses and medical documents)

The field list should contain fields that meet these requirements. In some cases, you can add fields not already in the standard field list. For more information on how to do this, refer to the release note entitled Extendable Field List inAll View Types.

Installations Without IS-H*MED

If you do not use IS-H*MED, you will only be able to use the appointment management and visit management options in the Outpatient Clinic/Service Facility work station. Any fields that read data from services will not contain any values.

This also means that only IS-H functions will be available in the function list for transfer into the function variant.

The following processes are elements of appointment and visit management:

  • Patients with provisional master data
  • Planning of appointments and provisional appointments
  • Patient admission
  • Visit overviews

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information






rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 12904 Date: 20240520 Time: 153231     sap01-206 ( 193 ms )