SAP ABAP IMG Activity SIMG_ISHMED_CAPDOCU (General Information on Functionality)
Hierarchy
IS-H (Software Component) SAP Healthcare
   IS-HMED (Application Component) Clinical System
     NMED_DS (Package) Departmental Solutions
IMG Activity
ID SIMG_ISHMED_CAPDOCU General Information on Functionality  
Transaction Code S_PRI_97000054   (empty) 
Created on 20061214    
Customizing Attributes SIMG_ISHMED_CAPDOCU   General Information on Functionality 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_ISHMED_CAPDOCU    

Use

  • Service Reference
    The cardiological sample documents have a service reference. In the document the system will check the following:
    - A movement reference must exist
    - The services are performed or confirmed and assigned to only one movement
    At the beginning of document processing (update mode) the system undoes the connection to canceled services.
    The system checks whether any more services exist for the movement. Such services can then be connected to the document (selection).
    In some documents you can subsequently enter services. This function should not be used to exchange services, as the subsequently added services do not have an order reference and and the order reference in the document may be lost.
    You can implement the CMOD enhancement before document creation, to check whether the services for the document have a movement reference, i.e. service number and movement are filled.
  • Procedure Entry
    In some documents a procedure table exists with the corresponding Enter Procedures function.
    Procedures can be stored for individual medical services in the service catalog, using the assignment type entered in the system parameter N2OPICPZ. These procedures are offered as proposals after you branch to procedure entry. Any possible localization requirement is taken into account. Selected procedures are then saved with a movement reference and transferred into the procedure table of the document.
  • Diagnosis Entry
    Some documents have a table for diagnoses with the corresponding function Enter Diagnoses.
    For each document category, alias name, and field value, several diagnosis keys can be stored as proposals with the usual indicators and a free text.
    Selected diagnoses are then saved with a movement reference and transferred into the diagnosis table of the document.
  • Device
    The room is stored in the comment text of the combo box entry for the device. When a document is created a device which suits the room can then be proposed (user exit: Create).
  • Branch to a File Viewer
    If an external program is used to view a connected file with examination data, from a PMD, you can use the ISH_N2_DS_EXEC_DOCUMENT function module.
    This module can be called in the user exit of a pushbutton.
    A prerequisite is a field on the document which contains the definite file name. The file can be located on the file system of the front end or on an application server.
    Table TN2DOCEXE_CUST must contain an entry for the file path and an external program can be stored, which is called, if no program is registered for this file type on the front end.
  • Transfer of External Examination Data
    The cardiological documents provide the option of transferring examination data from devices.
    For this purpose, a file interface is provided, which must be configured for the definite device type and document category if required.
  • Transfer of Historical Findings
    On the Prefindings tab page you can transfer data from a relevant prefinding, which must be of the same type as the current document, into the current document. Select the relevant row in the document viewer and select Transfer Historical Findings. The ALIAS of the link element for the document viewer must be entered in the document category definition as the grouping (tab page 'User Exit-Interface (Gen-2)'of the element list) of the action button, together with the code for selecting elements to be transferred (e.g. N8CA_LVB;[H]). The code (here e.g. [H]) must then be entered in the grouping of all elements, which should be taken into account during a data transfer. As this is medical data and there is no plausibility check during the transfer, you should use this function with extreme caution.
    During the transfer you can differentiate between overwriting and attaching. Attaching means that, in tables or long texts the corresponding content is suppliemented and that only individual fields without existing content will be overwritten.
  • Data Extraction of Document Data
    If an evaluation of the data entered in the documents is desired, it can be downloaded from the system and, for example, imported into an MS Access® database. The report RN2DS_FB_EXTRACT_PMD is provided for this.

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 899   not to be assigned 
Mandatory / Optional 3   Nonrequired 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_CAPDOCU 0 I010004300 Clinical System 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20070103 
SAP Release Created in 700