SAP ABAP IMG Activity SIMG_ISHMED_VKGTYP (Set Up Preregistration Types -> Remove When Doc. Added to CORD)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       NORD (Package) R/3MED: Services processing EDV-G
IMG Activity
ID SIMG_ISHMED_VKGTYP Set Up Preregistration Types -> Remove When Doc. Added to CORD  
Transaction Code S_KK4_96000420   (empty) 
Created on 20010719    
Customizing Attributes SIMG_ISHMED_VKGTYP   Set Up Preregistration Types 
Customizing Activity SIMG_ISHMED_VKGTYP   Set Up Order Types for Preregistration 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_ISHMED_VKGTYP    

In this IMG activity, you set up preregistration types. You need preregistration types is you wish to preregister patients in your system.

Use

The preregistration type defines the attributes of a preregistration. Using preregistration types, you define the various possibilities for preregistering patients and the layout of the preregistration screen.

The preregistration type controls:

  • Which organizational units (OUs) you can address with the preregistration. In other terms, in which OUs you can preregister a patient for admission, surgery or treatment.
  • A selection list containing services for which you can preregister the patient in the operating or treatment OU.
  • Which OUs can initiate the preregistration of a patient.
  • The information that is required for a preregistration.
  • The default values for various fields in the preregistration.

Requirements

For you to be able to enter preregistration types, the following preparations must be completed:

  • To be able to enter preregistrations for an institution, you require authorization for the transaction N1VE and the relevant institution (authorization object: N_EINR_TCO).
  • The OUs for which you wish to preregister patients, and the initiating OUs must be defined and released in the organizational structure of your institution.

The preregistration type also provides a number of optional settings for which preparation is also required:

  • If you wish to preregister patients for a surgery or treatment, you have to first maintain the service ranges for the organizational units in which the patient is to be preregistered for the surgery/treatment.
  • If you wish to define a service hit list for the preregistration type, you have to define a service catalog as the in-house service catalog. Store the identification key of the in-house service catalog in the system parameter GTARIF for your institution.
  • You can stipulate default values for a number of fields (Waiting List, Preregistration Status) in the preregistration type that the system applies when new preregistrations are entered. Make the necessary Customizing settings for this first.
  • If you wish to book visit appointments in addition to the admission appointment in the preregistration, you can do this once you have stored treatment contexts for the preregistration type. First define the possible treatment contexts, and then include the treatment contexts you require in the preregistration type.

Standard settings

Since preregistration types are highly dependent on the organizational structure of your institution and on their intended use, the standard SAP Patient Management shipment does not contain any preregistration types.

Activities

The initial screen of this IMG activity comprises an input help for the institution and an overview of all of the preregistration types defined for the institution.

Clicking on the Create Preregistration Type pushbutton takes you to the detail screen for creating a new preregistration type. To access the detail screen for changing a preregistration type, double-click on the relevant preregistration type, or choose Change Preregistration Type.

  • In the Preregistration Type field, specify a key to identify the preregistration type. This key is used to identify the preregistration type within the system, and once saved, cannot be modified.
  • The user sees the identifier and name of the preregistration type. You can use an identifier and name of your choosing. You can modify these attributes at any time.
  • On the Possible Treatment Organizational Units tab page, you specify the OUs in which the patient can be preregistered. These can be departments for the admission appointment or service facilities for the surgery/treatment appointment.
    • If the Limited indicator is set, the preregistration type only allows you to preregister patients in the OUs that have an explicit entry in the Treatment OUs table. If the Limited indicator is not set, the preregistration type can be used in all departments or service facilities in the institution. In such cases, the Treatment OUs table simply functions as a selection list containing the most frequently used OUs.
    • The characteristic determines whether the specified service facility is an operating facility. Select the OP characteristic if you wish to record the preregistration on the OR-oriented OR plan and document it as a surgery in IS-H*MED. If you wish to preregister the patients in an outpatient clinic or a service facility, select the General characteristic.
    • Select Only Services from Hit List if only those services you defined in the table Service Hit List are to be made available to the user entering preregistrations. In such cases, that services in the service range that are not included in the hit list will not be available in the preregistration.
    • To define a service hit list for a service facility, select the service facility in the Treatment OUs table, and choose the Service Hit List pushbutton. In the adjacent Service Hit List table, enter the services the user is to see in the hit list for the organizational unit currently selected.
  • On the Initiating Organizational Units tab page, enter the OUs that can be included as initiating OUs in the preregistration. The initiating OU in the preregistration function is the OU on whose orders a patient is preregistered for an admission or surgery/treatment. When entering a preregistration, an initiating OU can only use the preregistration type(s) for which it has been specified on the Initiating Organizational Units tab page.
    • The For External Bus. Partners flag indicates that the preregistration type can be used if an external business partner is entered as the initiator in the preregistration. External business partners can be general practitioners, external hospitals, health insurers.
    • If you wish to enable external physicians to preregister patients on the Internet, the Available in Internet flag indicates that the preregistration type can be used for this purpose.
  • The Dialog Control tab page determines how the dialog for entering, changing or displaying a preregistration should behave.
    • Enter a case type, a waiting list and a preregistration in the Default Values group box. The system automatically applies these values when you enter a preregistration.
    • In the Tab Pages group box, you can activate or deactivate specific predefined tab pages in the preregistration.
    • If other visit appointments are to be scheduled in addition to the admission appointment and the surgery/treatment appointment in the preregistration, you can define other tab pages in the Treatment Contexts table. Any number of visit appointments can be included on each of these tab pages.

  • You can set the Deletion Indicator for preregistration types you no longer need.

Example

You wish to preregister patients for surgery in the General Surgery department. The preregistrations are initiated by the Outpatient Surgery clinic, but can also be directly ordered by referring physicians. The referring physicians phone in to the General Surgery department secretaries' office.

To accommodate this scenario, you set up a preregistration type with the following attributes:

  • Identifier: GENSRG, Name:    Operations General Surgery
  • Since the preregistration type should enable patients to be preregistered in the operating facility GENSRG, you specify the service facility GENSRG on the Possible Treatment Organizational Units tab page, and select the OP characteristic.
  • For the services for which patients are most frequently preregistered, you create a service hit list based on the service range of the service facility GENSRG.
  • You enter the Outpatient Surgery Clinic as the initiating OU on the Initiating Organizational Units tab page. So that the secretary can enter referring physicians as the initiator in the preregistration, you select For External Bus. Partners. The Outpatient Surgery Clinic and secretary can new enter preregistrations with this definition.

New preregistrations should be assigned the status "entered" by default, and put on a waiting list.

  • To accommodate this scenario, you define the preregistration status Entered and the waiting list Surgical Interventions and enter these as default values in the preregistration type.

The routine examinations prior to the operation should be handled as outpatient appointments. Once the surgery appointment has been fixed, these examinations should be scheduled from the preregistration.

  • For this purpose, you define the treatment context Clarification on the Dialog Control tab page. This enables the user to enter and schedule service requests addressed to the lab or ECG from the preregistration.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_ISHMED_VKGTYP 0 I041002042 Preregistration 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
N1VE T - Individual transaction object N1COT  
History
Last changed by/on SAP  20031126 
SAP Release Created in 463