Customizing Settings
With the basic installation of the clinical system i.s.h.med, the majority of settings required by the surgery system will already have been made. The following customizing and system parameter settings, which are specific to the surgery system, still need to be made.
Each operation requires a surgical procedure code for combining all documents for this operation.
You create the number ranges (the range of surgery numbers) in the Implementation Guide
under .
Each anesthesia requires an anesthesia number providing unique identification.
You create the anesthesia number range (the range of anesthesia numbers) in the Implementation Guide
under .
Note
There is a no general rule for allocating the anesthesia number. The anesthesia number is normally created when the premedication or narcosis log is released. You can find a sample solution in the user exit OP_EXIT_DOKA
(Dialog Start) for available premedication log N0_ANAMNE
in the Include RN2N0ANA
.
As standard, the input help for the Anesthetic Course Observations for OR
contains all stored anesthetic course observations. You store anesthesia observations using .
You can define a hierarchical anesthesia observations structure using Complication - Complication Assnmnt
.
You assign the real anesthesia observations 1100, 1200 and 1300 to the pseudo anesthesia observation 1000.
You can further differentiate the input help, for example, from the surgical and anesthesiological perspectives. You enter two pseudo anesthesia observations as complications; the names cannot match any official anesthesia observation keys.
Example for Separating Surgical and Anesthesiological Observations
Create the pseudo anesthesia observations OP
and AN
. Using Complication – Complication Assnmnt
, assign these observations to all desired observations of the upper hierarchy level, e.g. 1000, 2000 and 3000 to OR
and other pseudo observations to AN
.
In order to separate OR observations and AN observations, you must enter the pseudo observations for the area, in our example OR
and AN
, in the institution-dependent, time-independent parameters N2OPKOME
(surgical observations) and N2ANKOME
(anesthesiological observations). N2OPKOME receives the value OP
, N2ANKOME
the value AN
. You define the system parameters in the Implementation Guide
under .
Result:
If you enter observations in the OR Documentation
branch of the surgery monitor, the system will only offer the observations, classified in hierarchy levels, which you indicated as being relevant to the surgical area in this way.
In the AN Documentation
branch the system will only offer observations from the anesthesiological area in the same way.
Note
You can also separate OR observations and AN observations without hierarchical levels, by individually assigning all observations directly to the pseudo observations AN
and OR
.
The assignment type used to assign anesthesia procedures to the anesthesia group service must be entered in the system parameter N2ANZUO. You define the system parameters in the Implementation Guide
under .
For identification of the recovery room, you must assign the OU recovery room to the system parameter N2OEAWR. You define the system parameters in the Implementation Guide
under .
In order to flag the anesthesia department, you must assign the departmental anesthesia OU to system parameter N2FOE_AN
. You find these parameters in the Implementation Guide
under .
You can use this parameter to determine which service facility (OU) represents the anesthesia department.
You then enter the anesthesia services and the material entry for anesthesia services for this anesthesia service facility. This means that the costs for inclusion in cost calculation are collected at this OU (cost center).
Internally, each operation is represented by a so-called anchor service. All OR documents, surgery materials, members of the surgical team, diagnoses and procedures are assigned to these anchor services. The surgery anchor service is a service, which does not appear on the interface of the applications.
To make the surgery system executable, you define this anchor service in your service catalog, The abbreviation should be obvious (e.g. ANKER_OP
) and cannot simultaneously be used for real services.
You enter the abbreviation of your anchor service in the Customizing parameter N2ANKLOP
. You find this parameter in Customizing for i.s.h.med under .
Caution
You should not set any of the service processing indicators (Med. Indicators
tab page), as the anchor service is not actively integrated into service management.
You define the anesthesia anchor service in the same way as the surgery anchor service (also no indicator). Enter the name of the anchor service in Customizing in the institution-related, time-independent system parameter N1ANKLAN
. You name the anesthesia anchor service, for example, ANKER_AN
, as it is possible that other anchor services will be introduced in the future.
Caution
Anesthesia and surgery anchor services must have different names! You should note that the comments made about surgery anchor services are also valid for anesthesia anchor services.