Ansicht
Dokumentation

Preregistration, Preregistration List ( RELNISHMED_403_PL01 )

Preregistration, Preregistration List ( RELNISHMED_403_PL01 )

BAL Application Log Documentation   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Preregistration, Preregistration List

Description

The Preregistration

The preregistration enables entry of patients into the system before their admission with a desired treatment and surgery. The desired treatment or surgery is entered as a service that is to be performed on a specific org. unit a hospital. The user can enter one or more services for a preregistration.

A preregistration is always created by an entering org. unit and always makes reference to an org. unit for which the patient is pre-registered. This referenced org. unit can be the same as the entering org. unit, whereas in this case, an org. unit pre-registers a patient by itself.

The preregistration list is made available as an instrument for managing preregistrations and can be called via the menu and from all known IS-H*MED work areas.

The services of a preregistration are usually for the same appointment, although they can also be planned and performed in different appointments (outside of the OR module).

In addition to the preregistration, you can also create a service request that contains preregistered services. This is mainly significant for surgical areas where patients are pre-registered over a longer term. After the admission and examination of the patient, the surgery request must be entered for the planned surgery with the necessary additional information.

Outside of the OR, the preregistered services appear with planned appointments in the work list can be performed there.

The assignment of a preregistration to a case can be executed when the patient is admitted, but also at the time of documentation.

Setting-up preregistrations

If patients are to be preregistered for an org. unit, then the following elements in IS-H*MED should be determined:

  1. Operation of the IS-H*MED preregistration is based around services. The hospital or department can define which services can be included in the preregistration list. Related to surgeries, this can either be the planned surgical procedure, or the universally applicable service OR, which is more precisely specified by verbally formulated text or by the diagnosis entered. In each case, the service range of the org. unit must contain this service. This does not matter whether the service is transferred directly or indirectly into the service range via a higher-level group service.
  2. Each service that should be pre-registered for the patient must be requestable. This results on the one hand from the communication process between an "entering org. unit" and a referenced "referenced org. unit", and alternatively from the possibility of transferring an already pre-registered service into a request or a surgery request.
  3. Principally, every service that meets the criteria specified so far can be transferred into a preregistration. However, in order to offer the user a useful selection list of each service for which the patients on an org. unit can be pre-registered, the preregistration has been implemented based on the already-existing request category. On the request category level, individual selection lists of services similar to the service request can be defined, which the system supplies when a preregistration is entered.

    The request category now has an indicator application to differentiate a request from a preregistration, which you enter in the initial screen when defining a request category. Once you have specified this, this use of a request category can no longer be changed. Defining request categories for preregistrations is simpler than defining request categories for service requests:
  • Since the preregistration has no status, the status-dependent obligatory field definition is no longer needed.

  • There are no additional documents for preregistrations, and correspondingly also no entry of a request category.

  • Preregistrations cannot be created within a request profile, making the reprocessing indicator redundant.

Every org. unit, for which patients are to be preregistered, must supply a request category with the preregistration application. This is also valid if org. units want to individually pre-register patients.
  1. Since preregistrations support an entering org. unit and a referenced org. unit in the communication process, both org. units must be assigned to one another in the master data. You enter this assignment the same as when defining requests via the menu option Hospital -> Basic clinical data -> Request -> Assign org. units requested. An assignment of entering and referenced org. units is not required if both org. units are already assigned to one another (e.g., for entering service requests).
  2. A request category with the preregistration function is available to all entering org. units that are to use it. This takes place the same way as the service request via the menu option for using the request category in the menu Basic clinical data -> Request.

Entering preregistrations

Principally every IS-H*MED work station can enter preregistrations. The corresponding menu option is in the med. unit list, the work list and the waiting list as well as in the OR plan and in the OR schedule in the menu Edit -> Patient -> Create preregistration. The function is also available as a pushbutton.

The user receives a selection list of all org. units for which he can pre-register the patient from the user's org. unit. If this is only one org. unit, the system will automatically offer all services that are defined as the selection list with the related request categories.

The services selected transfer into the entry dialog for the preregistration, where you can enter more information and, if possible, you can specify the planned treatment/surgery date:

  • Referring physician: The physician is entered with the code or can be sought in the data saved for external physicians.
  • Short anamnesis
  • Diagnosis: The diagnosis is entered here in text form. Comment: In the diagnosis overview of IS-H, you will not find a diagnosis entered in the preregistration, since the diagnosis, as a case-related construction is only available after the admission of the patient in IS-H.
  • Priority: If an appointment is not immediately allocated for the preregistration, then it is inserted into the preregistration list with the priority indicted. Here, the same priority levels are available that IS-H recognizes in its waiting list.
  • Desired appointment: If a treatment/surgery date is not found immediately, the preregistration is sorted under "No date specified" in the preregistration list, whereby the desired date serves the user as a guide for the date search. The desired date for preregistrations can be input with an approximate value for months: e.g. at the beginning of June 1999.
  • Planned treatment or surgery date: Manual input is possible or you can use the date search function from the calendar and determine the past preregistrations of the org. unit. As a function of the organizational form, day or time-specific planning can be run. Further information on this topic you will find in the Release Notes for day-specific planning and the planning board.
  • You can already optionally enter the team for preregistrations whose request category has the characteristic "OR". This function mainly facilitates the surgeon to enter the preregistration far in advance.
  • Admission data: Case type, admission date, org. unit. This information helps organize the planned admitting unit/outpatient clinic: When queried for admission date, the preregistration list shows the unit/outpatient clinic all patients, who (for example) have admissions planned for the next day. Entering the planned admission date does not create an admission or a case. For this reason, patients who were pre-registered for an admission do not appear in the arrivals list of the IS-H Medical unit management.
  • The responsible employee appears/is entered in the preregistration next to the entering org. unit. Entry check and possible entries always take place related to the entering org. unit.

Patient-related, caseless entry

preregistrations are always created with a reference to the patient, but without a reference to the case. Patient-related means that with the preregistration of a new patient, a complete patient data record is created. This adds the advantage that the preregistration as well as all (pre-) examinations requested because of the preregistration are linked to each other and can be presented together.

To effectively set-up the assignment to the patient for the user, IS-H*MED has two processing forms:

  1. For example, a patient currently in treatment should be pre-registered for one surgery. In this case, the patient is already stored and appears on one of the IS-H*MED work stations (unit list, work list or waiting list). The patient is selected. With the preregistration function, you can enter a new preregistration for the patient. Last name and first name of the patient are displayed in the dialog of the preregistration. Its master data and insurance data as well as the risk factors are mostly already available from the current admission. As a check/enhancement, this information can be accessed from the preregistration via push button.
  2. The patient is not available on the current work station. The preregistration is to be entered (e.g., due to a telephone call): The user does not select a patient on his work station and activates the function "Create preregistration". Here it is important that a possible date is found for the desired treatment/surgery, before the particular patient is entered. For this reason the system requires the entry of the patient only then if the preregistration is stored. The processing sequence is as follows:
  • Select desired treatment/operation

  • Search possible date or set on waiting list

  • If date with patient/referring physician clarified: Enter master data of the patient and insurance.

For the entering the patient, the usual procedure in IS-H is selected: The user receives a dialog window for inputting search criteria (last name, first name, etc.) In order to avoid double entries, the user looks for a patient with the criteria entered. If the patient is already recognized in the hospital from an earlier admission, the user selects the patient, whereas the preregistration will be assigned to the patient. If the patient does not appear in the selection list, the user creates a new patient, whereby patient-related information can be entered such as insurance relationship and risk factors among other types of information. The preregistration is stored together with the new patient.

Appointment allocation

The arrangement of the functions was selected in such a way that the search for a date can take place as rapidly as possible, in any case before the complete input of the preregistration and the entry of patient data. If the user does not find a date in the desired period for the patient, he/she can abort the input without canceling.

Procedure: When creating a preregistration, by activating the function "Find appointment" (pushbutton with headlights icon next to the entry field of the appointment), you can branch immediately into the appointment calendar of the referenced org. unit. As a function of the planning mode of the referenced org. unit (day-specific planning/time-specific planning), the system calls the daily planner or the planning board. The user determines a day or time-specific date for the treatment or surgery and returns to the initial screen. The planning mode is adjustable in the OU-related parameter N1VKPLMOD.

You can find a complete description of both planning functions in the Release Notes for day-specific time-specific planning.

Information and representation of preregistrations

Each preregistration entered is placed into the preregistration list. preregistrations, which have a date, are displayed in the work list, in the OR planning list and in the OR schedule, if its date falls into the selection period of these lists. In order to be able to differentiate preregistrations from service requests, preregistrations are always represented with the SAP icon ICON_SHORT_MESSAGE.

You can find a description of the preregistration list in the following chapter of these Release Notes. The display of preregistrations and their possible editing functions in unit lists, work lists and waiting lists as well as in the OR module are described in the Release Notes "Integration of the Planning module into the Basis Functions of IS-H*MED.

Creating a case reference

preregistrations are principally entered without a case. A case is only created if the patient is admitted into the hospital. For the admission, the standard admission functions of IS-H are available, whereby these can also be called optionally from the preregistration list. In order to avoid repeated versions, the user in each case passes through the patient identification function; i.e. the user tries to find the patients in the stored patient master.

When storing the admission the system checks whether there are caseless preregistrations or service requests entered for this patient. If so, the user receives a selection list and can add a case to the preregistration and/or request, which were entered with the assigned date.

Constraint: Often, administrative units enter the admission without proper authorization for making the decision of whether a pre-registered treatment/surgery should be added to the case or not. For this reason, you can control the creation of the case reference by using the OU parameter N1VKCHKFAL. The OU parameter is queried for the admissions point, which is input as org. unit when creating the case. If the user does not input an admissions point with the admission, the parameter setting will use the org. unit*.

preregistration list

The preregistration list acts as a centralized administration tool for preregistrations. You can access this via the menu option Service facility -> preregistration list as well as via the Environment menus for Unit list, Work list and Waiting list and the OR plan and the OR schedule.

The preregistration list is available to the user in the following configurations:

  1. The display by referenced org. units for listing all patients who are pre-registered for a certain service facility.
  • You call the display in the initial screen by pressing the "preregistrations" key. The valid search criteria are those entered in the blocks "Pre-registered for" and "Planned admissions". Org. units can also be co-ordination units and departments, whereas in this case, selection of preregistrations takes place via the hierarchy of the org. unit entered. All criteria entered in the search terms "Patient" are not relevant for display.

  • The list is primarily organized by admitting org. units for which the patient is pre-registered.

  • Within the org. unit, planned and unplanned preregistrations are differentiated from each other. Planned preregistrations always appear before unplanned preregistrations. A preregistration is "planned" if one of its services has an appointment within the selection period that you can add to on the initial screen.

  • The list of unplanned preregistrations can be further organized in categories. Arrangement by categories is optional and facilitates better structuring of the preregistrations for planning purposes: It is important for the long-term appointment allocation, for example, to have preregistrations for major surgeries grouped in a list in order to plan the next 10 entries in this list. preregistrations for minor and moderate operations are not meant to appear in this list. For this, please also see the coming paragraph "Classification of preregistrations".

  • Within the planned and unplanned preregistrations, the list sorts by the criteria that you specified in the menu option Settings.

  1. Display by admitting org. unit for listing all pre-registered patients, who will be admitted (for example) in the next 3 days at a certain unit or outpatient clinic.
  • You can activate the display by admitting org. units in the initial screen via the "Admission" key. The valid search criteria are those entered in the blocks "Pre-registered for" and "Planned admissions". All criteria entered in the search terms "Patient" are not relevant for display.

  • The list is primarily organized by admitting org. units.

  • Within each org. unit, the preregistrations appear by the line and sorting definitions specified in the menu option Settings.

  1. Display by patient. This mode facilitates the search for pre-registered patients independently from org. units, for which the patient was pre-registered for the treatment/surgery or admission. You can activate the patient-related display by entering search criteria for the desired patient and pressing the search key.
  • The system first determines all patients, for whom the search code corresponds. From these patients, the ones with a preregistration are displayed. The patient list common to IS-H and IS-H*MED for patient searches does not appear, since it contains no information regarding preregistrations. Instead, the user immediately receives the list of preregistrations found.

  • The user can freely define line contents and sorting settings via the menu option Settings.

User-defined line definition

The user can freely define the line contents of all 3 displays via the menu option preregistration list -> Settings. Each of the 3 displays supplies its own list making various lines and sorting settings possible for each display. For this reason, the standard setting for the patient-oriented display appear different from the standard setting of the list for by admitting org. units.

The display by referenced org. units (pushbutton for preregistrations in the initial screen) contains two different line types: For planned preregistrations and for unplanned preregistrations. This makes it possible to display the priority and the desired date for unplanned preregistrations as well as planned treatment/surgery dates for planned preregistrations.
The display by admitting org. unit and by patient each has an available line type.

Sorting the preregistrations can be freely selected within the fields of a line. This is only expanded by the fundamental structure of the list:

  • In the display by referenced org. unit: Sorting takes place according to org. unit, preregistrations with/without appointments and by user-selected definition.
  • In the display by admitting org. unit and user-selected definition
  • In the patient-related display by user-selected sorting criteria

The definition of line contents in the preregistration list is limited to 10 fields, since the R/3 tree structure is used as a structuring tool, which only allows a maximum of 10 fields per line. The selection field at the first position of each line also counts as a field leaving nine positions free for the layout. To do away with this restriction, the preregistration list offers the following possibilities:

  • The field contents comprise available field combinations; e.g., patient data as a combination of last name, first name, sex and birth date of a patient.
  • Each of the field contents also includes a field that can be filled in via the SAP enhancement SAPLN1VK, function exit EXIT_SAPLN1VK_001, into which user-selected fields can be transferred.

The fields "Document exists", "Request exists and "Risk factors" appear as icons following this logic:

  • Document exists. The list searches with the following steps for already saved documents:
  • If the preregistration is not assigned to a case yet, documents will be sought that have a patient reference but no case reference: case-wide documents.

  • If the preregistration is already assigned to a case, the system will additionally search for documents that belong to the case of the preregistration: case-wide documents and documents for the current case.

If these documents are saved, the list will display the icon "Change". If there is a special indicator set for one or more of these documents (e.g., the "Warning" icon), the list will display this special indicator. If more than one indicator are found, that with the highest priority will appear.
  • Request exists: The search for requests is the same as the search for documents:
  • If the preregistration has no case reference, caseless requests will be sought.

  • If the preregistration is assigned to a case, the list will also search for requests for this case.

If no request is found, the list will display the icon "Create". If a request exists, the icon "Change" will appear.
  • Risk factors exist: If no risk factors for the patient exist, the list will display the icon "Create". If the patient has risk factors, the icon "Change" will appear.

The system determines the list variants to be used by employing the following algorithm:

  • Search according to a personal variant for the user. Dependent on the activated display, this is stored in the following user parameters:
  • In the display by referenced org. unit: Parameters VKLOT (lines without appointment) and VKLMT (lines with appointment)

  • In the display by admitting org. unit: Parameter VKLAN

  • In the display by patient: Parameter VKLPT

  • If no variant is specified via the user parameter, the system will search for a variant with the name of the user logged-in.
  • If no variant is found with the name of the user, the system will search for a variant with the name STANDARD.
  • If no variant STANDARD is defined, the system will use the variant supplied SAPSTANDARD.

Classification of unplanned preregistrations

In the representation by referenced org. unit, it is possible to display unplanned treatments/surgeries by major, moderate and minor operations. "Major", "moderate" and "minor" operations in this example are service classes to which the pre-registered services are assigned. A different classification possibility would be defining the treatment/surgery by body region (e.g., heart surgery, hip surgery, etc.)

If a preregistration does not belong to any service category, it will be listed in the standard section "Unplanned" (not planned.)

To determine the classification of the services, follow these steps:

  • Enter the service classes as services
  • Specify an assignment type for the services and enter these assignment types into the institution-related customizing parameter N1LKPZUO.

Assign any services on which you base the preregistrations that you enter, with the new assignment type to the class services. In order to do this, use the transaction "Maintain service group" in the basic data of IS-H*MED.

Functions of the preregistration list

Here you can find a description of each of the functions for the preregistration list, which deviate from the general list standard or are not clear.

Create preregistration: You can create a new preregistration from the preregistration list, whereas the function is dependent on the selected lines in the following way:

  1. Patient selected, no org. unit selected: You would like to create a preregistration for the patient selected. This system supplies you with all org. units, for which the patient can be pre-registered from the view screen of your org. unit (e.g., the org. unit entering, entry in the initial screen, parameter OEE). If only one org. unit is involved here, you will immediately receive a selection list of the services that can be pre-registered. Select the services desired, then press Enter and you will branch to the data screen for entering the preregistration and finding the appointment.
  2. No patient selected, org. unit selected: You would like to create a new patient and a preregistration for the org. unit selected. The system will present a list of services, which you can pre-register. You then select the desired service(s) and receive the data screen for entering the preregistration. The data of the patient are then entered after saving the preregistration.
  3. Patient and org. unit selected: You would like to pre-register the patient selected for the selected org. unit. Service selection as with point 2, create preregistration same as point 1.

Change preregistration: This function can be called via a menu item, pushbutton or mouse clicking in the diagnosis. A preregistration can be changed, as long

  • As it has not been transferred and
  • None of the pre-registered services were performed or released.

Display preregistration: Callable via a menu item or pushbutton

Cancel preregistration: This function can be called via a menu item or push button. When the preregistration is cancelled, services contained in the preregistration will be cancelled also. Appointments for which the pre-registered services were booked will also be cancelled. Any appointments, for which other additional services not contained in the preregistration are to be performed, will remain unaltered.

Assign a preregistration to a case: You can assign an already saved preregistration to a case as soon as the patient is admitted. This function is available if the case reference is not created when admission takes place. The system presents a list of all cases of the patient. When you select a case, the system will assign the preregistration selected to the selected case via a query.

Plan a day-specific preregistration: Using this function, you can plan a preregistration for a treatment or surgery day. To execute this, select the preregistrations to be planned and then the menu item Edit -> preregistration -> Plan day-specifically, or press the pushbutton with the calendar icon. The program branches to the day-specific planner, where you can determine the treatment or surgery days based on the stored quotas and the other services already booked. You can access a specific description in the Release Notes under "Day-specific planning".
A preregistration can be planned as long as its services have either the status "Unconfirmed" or "Confirmed". No longer plannable preregistrations are filtered out of the selection with the display of a message.
If you would like to plan a preregistration or change the date of the preregistration, alternately to the menu item or pushbutton, you can mouse-click on to the desired date or the planned to call it. Calling the day-specific planner is dependent on the OU related parameter N1VKPLMOD: If an org. unit, for which the patient is pre-registered, plans day-specifically, you will receive the day-specific planner as a planning tool.

Plan a time-specific preregistration: You can obtain the IS-H*MED planning board via the menu item Edit -> preregistration -> Planning board as well as the pushbutton with the schedule icon. No longer plannable preregistrations are filtered out with the display of a message. The planning board supplies a graphical overview of resources and the available timeslots of all org. units for which planning authority exists from the view screen of the planning org. unit. In the planning board, you can book appointments with starting times and duration for the pre-registered services at the resource level.
For individual editing, you can also mouse-click on t he desired or planned date. The planning board is then only called if the parameter N1VKPLMOD is set to time-specific planning.

Patient history: You can access the patient history is via the menu item Goto -> Patient history or by mouse clicking on the name of the patient available.

Create request: Service requests can be entered for a pre-registered patient (menu item Request -> Create or via the pushbutton). A nursing org. unit making a request is always the org. unit that the user should enter in the initial screen and which is defaulted with the user parameter OEE. A departmental org. unit making a request is a department for whose service facility the patient is pre-registered. As in the medical unit, outpatient clinic and service facility support, the system offers a selection list of all org. units, request categories and services that can be requested from the view screen of the nursing org. unit making the request.
If the preregistration still has no case reference, the system will create caseless requests, which will be linked in the work list with the case when the patient is admitted or only when the patient is treated. If the preregistration is already assigned to a case, the requests will be created for the same case.
If no requests are entered yet for a patient or a case, the list in the "Requests" column will show the "Create" icon. Mouse clicking on this icon will cause services to be requested for the patient.

Request overview: The request overview is available via a menu item and a pushbutton. If requests were already entered for the patient or case, the "Requests" column will show the icon "Change". Mouse clicking on this icon will access the Request overview.

Risk factors: Can be displayed and entered via the menu Med. docu -> Risk factors. You can call the entry function by mouse clicking on the "Risk factors" column of the preregistration list.

Diagnoses: You can access the "Diagnosis overview" in the "Med.Docu" menu or via pushbutton. Since diagnoses in IS-H and IS-H*MED are a case-related element, the Diagnosis overview is available only if the preregistration is assigned to a case. With preregistrations and requests entered without a case, the diagnosis is entered as textual information.

Create document: You can execute this with the menu item or the pushbutton allocated for this task. If the patient is not admitted yet, i.e., the preregistration still has no case reference, then a patient-based document will be created. If the preregistration is already linked to a case, the document created will obtain the same case reference as that of the preregistration. If no document exists yet for a patient or a case, the "Document" column will show the icon "Create". Mouse clicking on this document will also activate the function "Create document".

Document list: The document list can be accessed via a menu item and a pushbutton. If documents have been created for a patient or case, the "Document" column will show the icon "Change". By mouse clicking on this icon, you can also access the document list.

Create/change/display outpatient/inpatient admission: These functions are in Menu "Environment". For quick processing, two pushbuttons are available: "Outpatient admission" and "Inpatient admission", which create a new admission or are used to change an existing admission depending on the existing case or case type of the selected patient. If no patient is selected, the admission of a new patient is initiated.

Selection variants

In the programs "Medical Unit List", "Work List", "Waiting List", "OR plan" and "OR schedule" offer the preregistration list. In the menu "Environment" you can add selection variants to the call that are to be implemented via the SAP enhancement SAPLN1VK, function exit EXIT_SAPLN1VK_002. Implementation can be executed independently from the calling program, since other preregistration lists are significant for a medical unit as well as for an outpatient clinic. A variant includes all selection criteria that can also be entered in the initial screen of the preregistration list.

It is possible to store a variant for which the user obtains its initial screen and can individually enter the selection criteria or change the criteria offered. You can access more detailed information for defining variants in the documentation for the SAP enhancement SAPLN1VK as well as in the documentation for the function module ISHMED_CALL_VKG_LIST.

One of the variants implemented can be stored as a standard variant. Calling the standard variant is done via Environment -> preregistration list -> Standard variant or via the pushbutton preregistration list, if no other variants have already been stored.

When selecting the menu item Environment -> preregistration list -> Select variant, the user obtains a selection list of all variants that are available from his current work environment.

The menu option Environment -> preregistration list -> Call without variant circumvents possibly stored selection variants and callsthe preregistration list for a certain org. unit with unplanned and planned preregistrations as well as with the complete selection period. The org. unit for which the call is made can be store in the OU parameter N1VKLOE. The parameter N1VKLOE will always be requested for any org. unit for which the user called the workstation (med. unit list, work list, waiting list, OR plan, OR schedule). This org. unit also represents a standard value if the parameter N1VKLOE is not maintained.
Example: In standard operation, the preregistration list for the service facility OR general surgery should be callable from the waiting list for the surgical outpatient clinic. The parameter N1VKLOE for the surgical outpatient clinic should for this reason be set to OR general surgery. If the parameter is not maintained, the preregistration list for the surgical outpatient clinic will be called.

Independently from the menu item "Environment", the preregistration list can be called for the patients selected in the medical unit list, work list, and other lists in all of the programs mentioned (med. unit list, work list, etc.) via the menu item Edit -> Patient -> preregistration list.

The pushbutton "preregistration list" has various functions depending on the selection that is set:

  • If patients are selected, the preregistration list is called for these patients (same function as menu item Edit -> Patient -> preregistration list)
  • If no patients are selected, the function "preregistration list" is called for the referenced org. unit (same function as menu item Environment -> preregistration list -> Variant selection as well as Call without variant, if no variant is defined).

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Authorizations

With the implementation of the preregistration, two new authorization objects were also implemented:

  • N_VKG_FCT - Authorization for the preregistration with the fields
  • Institution

  • Entering Org. Unit

  • Referenced Org. Unit

  • Function (Create, Change, Display, Cancel)

  • N_VKGLI_EB - Authorization for the initial screen of the preregistration list with the fields:
  • Institution

  • Referenced org. unit

  • Admitting org. unit

Universal authorizations (N_VMKG_ALL, N_VKGLI_ALL) are supplied for both objects in the profiles N_ISHMED_ALL and N_ISHMED_NEW. Please add the necessary authorizations to the authorization profiles of each user group that works with preregistrations.

Classifying services

The classification of unplanned services is optional and can be implemented by following these steps:

  • Create a service for each service class in the hospital catalog, for example major surgeries.
  • Define a new grouping category for services in customizing, for example, CLP classification for preregistration. Enter this grouping category into the institution-specific parameter N1LKPZUO.
  • Assign any services for which the patient can be pre-registered to the service classes with the newly defined assignment types.

Effects on Customizing

Create/change preregistration

The functions "Create/change preregistration" call various planning modules for finding appointments depending on the planning mode of each org. unit, for which the patient is pre-registered:

  • If the org. unit plans day-specifically, the day-specific planner for determining a treatment day will be called.
  • If the org. unit plans time-specifically, the planning for determining a treatment time will be called.

The planning mode is set in the OU-related parameter N1VKPLMOD for the referenced org. unit.

preregistration list

The initial screen of the preregistration list can be completely pre-selected by using user parameters:

  • Institution: Parameter EIN
  • Referenced org. unit: Parameter VKLOE
  • Select the indicator for unplanned preregistrations: Parameter VKLTU
  • Indicator for unplanned preregistrations with appointment: Parameter VKLTG
  • Selection period for the planned appointment: Parameters VKLTV and VKLTB. The values of both parameters are interpreted as a number of days, taken from the system date or calculated with the system date, in order to obtain the selection interval.
    Example: System date = 4.7.1999, VKLTV = 2, VKLTB = 2. For the selection period, the time appears: June 2, 1999 to June 6, 1999.
  • Org. unit for the admission: Parameter VKLAO
  • Selection interval for the admission date: Parameters VKLAV and VKLAB. The calculation of the selection interval takes place like that of the selection period for the planned appointment.
  • List variant for displaying by referenced org. unit: Parameter VKLOT for preregistrations without appointment and VKLMT for preregistrations with appointment
  • List variant for displaying by admitting org. unit: Parameter VKLAN
  • List variant for displaying by patient: Parameter VKLPT
  • Entering Org. unit for new preregistrations: Parameter OEE.

Display of preregistration list

For the classification of unplanned services, the assignment type used is to be entered in the institution-related, time-dependent parameter N1LKPZUO.

Calling the planning

The parameter N1VKPLMOD is interpreted by a mouse-click on the desired and planned date of a preregistration. Depending on its value, either the day-specific planner or the planning board will be called.

Calling the outpatient and inpatient admission

The OU parameters N1VKLANAM and N1VKLANST determine the admission mode (normal/quick/emergency) for the entering org. unit. The standard setting is normal admission.

Calling the preregistration list from other programs

With the OU parameter N1VKLOE, the preregistration list of the medical unit list, work list waiting list OR plan or OR schedule can be called for an org. unit instead of the current station, outpatient clinic or service facility.

Create case reference

With the OU parameter N1VKCHKFAL you can control which transactions the selection list "Case reference" offers the user when saving the admission. The parameter is queried for the admission point. If the admission point is not entered, the system will draw the parameter value for the org. unit*. Possible entry values are all IS-H admission transactions available with the functions "Create" and "Change":

  • NV01, NV02 for inpatient admission
  • NV41, NV42 for outpatient admission
  • As well as the corresponding transactions for quick and emergency admission.

Effect on batch input

Changes to the Interface

You can access the functions "Create preregistration" and "preregistration list" in the following programs:

  • Medical unit list
  • Waiting list
  • Work list
  • OR planning list
  • OR schedule

These programs each contain a menu item:

  • Edit -> Patient -> Create preregistration, to enter a preregistration for one selected patient or a new patient
  • Edit -> Patient -> preregistration list, to call the preregistration list for one or more selected patients
  • Environment -> preregistration list, to call the preregistration list via the initial screen or with the variant selection

Preregistrations without an appointment only appear in the preregistration list.

Preregistrations that have a treatment/surgery appointment are displayed in the work list and the OR planning list, should the treatment/surgery appointment fall in the selected period of the work or planning list.

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Preregistrations are displayed on IS-H*MED workstations including medical unit list, work list, waiting list, OR Plan and OR schedule and linked to the available processing functions. For a related description of this, please refer to the Release-Note Integration of the planning module in the basis functions of IS-H*MED.

Planning

Further notes






Fill RESBD Structure from EBP Component Structure   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 45557 Date: 20240602 Time: 172002     sap01-206 ( 667 ms )