Hypertext: Object Class - Class to which a document belongs.
Document Name
SIMG_ISHMED_CADEVDOC
Use
Various parameterized documents are available for the creation of findings and logging of cardiological examinations. Some of the data entered is stored on the device during the examination. Such data must then be transferred by machine into the processed document at the time of logging or findings creation. For this a file interface is configured which enables the evaluation of ASCII files with any structure (e.g. XML, HL7, etc.) and the transfer of examination results. The files with the examination data are collected in one directory and transferred individually to the interface using a report. For this purpose you can use the report RN2DS_COLLECT_ALL_FILES which is supplied. During execution, data is initially formatted and saved in the SAP database. During the processing of a document you can use a pushbutton to transfer corresponding examination results from the database.
It is possible to import the file contents via direct file transfer, previous FTP transfer, or using HCM technology.
Requirements
For each device type to be connected, an (Incoming) directory must be created on an application server of the R/3 system. If the data is procured with the report RN2DS_COLLECT_ALL_FILES, the directory must be structured as follows: The directory must contain a file called 'inbound_readme.txt', the interface will check the existence of this. Below this directory there must be directories called \work as the work directory \save as the save directory for transferred files (test phase) . If you wish to use RN2DS_COLLECT_ALL_FILES with FTP you must save some settings for SAPFTP. The files must be ASCII files and may only contain characters, the code of which is known in the system character record of the R/3 system. This should be taken into account particularly when selecting separators. The number range object ISH_NCI0 is used for logging.
Standard settings
Formatting files and saving measured data in the database ( without HCM )
Technical settings (same as for HCM use) A logical system is created for each device to be connected (transaction ONC6 ) and a TXCOM entry must be maintained for receipt. You should refer to the Details of the technical settings.
Customizing for interface information / formats An entry must exist in table TN2DEVICES for the symbolic destination for data receipt (TXCOM). The fields Name of Transfer File Separator in File Path ( / or \ ) Description of Ext. Date Format (e.g. DD.MM.YY) Description of Ext. Time Format (e.g. HH:MM:SS) Sex - Female Sex - Male must be filled.
Process in the interface For report RN2DS_COLLECT_ALL_FILES a variant using the name of the logical systemis created. The report is scheduled as a periodic job and monitors the Incoming directory (TXCOM-TP_NAME). Each transferred file with measured data is first moved to the work directory and then individually placed in the Incoming directory with the fixed file name (from TN2DEVICES). This file is further processed using the function module ISH_N2_DS_PROCESS_FILE. The successfully processed file is deleted and the job log receives the message concerning the number of processed messages (number of examinations) of the file. The corresponding original file is stored in the /save directory, if necessary (according to parameterSave Files) and deleted in /work. In case of a logical error, the interface file remains in the directory and the corresponding original file is retained in /work. In this case the next file is processed. If one of the files is incorrect, the job is canceled and the error messages are contained in the job log. The transferred data is then logged for each file as a message in table NCI0. The logs can therefore be processed with the HCM tools. However, detailed display of the fields is not possible using HCM, as the data structure is not available in the system. If you select 'Long Log' the entire content of the file is logged row by row. Otherwise only the first 1024 characters of the file are displayed from the rows.
Get files with HCM and save measured data in the database
Customizing for HCM A prerequisite is that the interface file must exist as an ASCII file on a directory of an application server of the processing SAP system. A logical system is created using transaction ONC2 - with presetting - for each device to be connected. The resulting entries for the system attributes, TXCOM and the receipt control must then be maintained further. You should refer to the Details of the technical settings.
Customizing for interface information / formats A entry must exist in table TN2DEVICES for the symbolic destination for data receipt (TXCOM). The fields Name of transfer file Description of Ext. Date Format (e.g. DD.MM.YY) Description of Ext. Time Format (e.g. HH:MM:SS) Sex - Female Sex - Male must be filled.
Process in the interface The file with the measured data is sent, with the agreed fixed file name, into the specified directory (name/path see command file). For report RN2DS_COLLECT_ALL_FILES a variant under the name of the logical systemis created. The report is scheduled as a periodic job (parameter Type of Data Transfer : via HCM) and transfers the adjacent file for further processing using function module ISH_N2_DS_PROCESS_FILE. The individual records (message segments, rows) must end with carr.returnlinefeed and should not be longer the 4096 bytes (see description of HCM in transaction SPRO). Only the HCM functions for reading (ISHCM_RECEIVE_TABLE) and confirming (ISHCM_RESPOND_TABLE ) are used. The data is actually processed in separate programs. Using HCM the file is locked and renamed ... .tmp. If processing is successful, the processed file is deleted and the job log contains the message concerning the number of processed messages (umber of examinations) of the file. In case of a logical error, HCM resaves the file under the name .. .dat. If a new file has already been sent, the content of the incorrect file is attached to the new file. In this case, processing is canceled and the corresponding error message is inserted in the job log. Following uncontrolled aborts the ... .tmp Datei is retained in the directory, which is deleted or must be provided as an interface file, depending on the situation.
The transferred data is logged as a message in table NCI0. The logs can therefore be processed using the HCM tools. However, the fields cannot be displayed in detail using HCM, as the data structure is not available in the system. If you select 'Long Log' the entire content of the file is logged row by row. Otherwise only the first 1024 characters of the file are displayed from the rows.
BAdI for formatting data to be saved As the files in the interfaces can exist in various proprietary formats, the definite formatting is transferred from a BAdI. The PARSE_DATA method of the ISHMED_DS_PMDDEVICES BAdI must be implemented for the symbolic destination in use (TXCOM entry for data receipt). Data exists in tabular form from strings and must be converted into a table of the N2DSDEVICE_DATA row structure. In particular, characteristics required for later assignment Institution Symbolic Destination Examination Date IS-H Patient Number R/3 gender indicator Patient Last Name Patient First Name Birthdate are placed in separate fields. In addition to these primary selection fields, the content of Examination Type Case Order Number Service Number ..Examination Type are separated and can later optionally be used during data assignment.
Any errors determined must be returned to a message table, in order for them to appear on the job log. The data formatted by the BAdI are saved in the database by standard processing.
Import measured data from the database into a document
Customizing for data retrieval
Interface - document assignment dep. on OK code In table TN2DEVDOC_ACT the symbolic destination of the device is determined for the document category, version and OK code in use, from which the data is imported. If data are received form the interface from various examination types, the expected examination type can be entered here.
Maintain field mapping per document category Mapping information is required for data import into a document.
Hierarchy 
IS-H (Software Component) SAP Healthcare
IS-HMED (Application Component) Clinical System
NMED_DS (Package) Departmental Solutions
IMG Activity 
Document 
History 
