Hierarchy
IS-H (Software Component) SAP Healthcare⤷
IS-HMED (Application Component) Clinical System⤷
NMED_DS (Package) Departmental Solutions
IMG Activity
| ID | SIMG_ISHMED_CADEVDOT | Description for Maintenance of Technical Settings |
| Transaction Code | S_PRI_97000069 | (empty) |
| Created on | 20061215 | |
| Customizing Attributes | SIMG_ISHMED_CADEVDOT | Description for Maintenance of Technical Settings |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHMED_CADEVDOT |
Use
For each device interface you must first decide whether the system should work only with HCM or whether file actions should be directly called by the application server, optionally supplemented with previous polling by FTP.
Depending on whether HCM is used direclty in the file interface, various technical settings must be made.
In any case, a logical system must be created for each device type to be connected.
- Maintain technical settings for data determination without HCM
- Customizing for the logical system (same as for HCM use)
A logical system is created for each device to be connected
(transaction ONC6 ).
The following is preset as default:
Logical system name (7 characters) (e.g. N2HKATH)
TXCOM name (technical system name, 7 characters like system ) (e.g.N2HKATH)
Code page
System type: External system
possibly Lock indicator
- TXCOM maintenance (TA SM54)
Table TXCOM must contain an entry for the system (7 characters) and 8th character = '2' (e.g. N2HKATH2).
In field TP Name you enter the path for the directory, in which the interface file to be imported is expected.
The log is set to 'F'.
The file name (without an extension) is entered in table TN2DEVICES.
- Customizing for HCM
The interface file must exist as an ASCII file in a directory of an application server of the processing SAP system. - Customizing for the logical system (TA ONC2)
The system is created with transaction ONC2 - with presetting.
The system is created with transaction ONC2 - with presetting.
The following is preset:
Institution (e.g. 1)
Logical system name (e.g. N2HKATH)
TXCOM -Name (technical system name, 7 characters) (e.g. N2HKATH)
Server name (logical unit) (e.g. yyynt16)
Gateway host (e.g. yyynt16)
Gateway service (e.g. sapgw06)
Code page
The system is only configured for data receipt !
Transaction programs on external system:
For GET TAB and GET RESP the complete file name of the command file, in which the system environment for HCM requirements is set, must be specified.
This information is then available in the corresponding TXCOM entry.
In the file formats to be expected the corresponding file structure cannot be defined as a HCM message type.
However, as HCM should not forward the interface file to ISHMED itself, only the functions for reading and logging are used, dummy entries can be made in some places.
Communication standard HL7 or SAP-HCM (e.g. HL7)
Version (e.g. 2.1)
Own ID (e.g. SH)
This transaction creates several customizing entries, which must then be supplemented.
- System attributes (TA ONC6)
System type: External system
Check External System
A lock indicator can be set here.
- Receipt control (TA ONCV)
An entry must exist in receipt control for the system.
Event (e.g. N2HL7)
Message type (e.g. ORU)
Own ID (e.g. SH)
- TXCOM Maintenance (TA SM54)
Table TXCOM must contain to entries for the system.
The entry with the 8th character = '2' contains information for data receipt.
The entry with the 8th character = '3' contains information for confirmation.
The log is set to 'E' in both cases.
The command files entered for TP must be created correspondingly and contain further information on the interface file:
set CPIC_TRACE=0
set INTERF_DEB=0
set INTERF_NTISH=\usr\sap\xxx\work\ishcm\kat
set INTERA_NTISH=1
.......
set INTERF_Z2DEV=\usr\sap\xxx\work\ishcm\kat
\usr\sap\xxx\work\ishcm\prog\gettab.exe %1 %2 %3
File name here is Z2DEV.dat
- Entries for SAPFTP
If you wish to procure the interface files using report RN2DS_COLLECT_ALL_FILES with FTP, you must store some settings for SAPFTP (TA N2DS_SAPFTP_CUST).
Target system Symbolic destination
(TXCOM entry for receipt, 8th character '2')
User and password of FTP connection The entered password is coded
Target machine of connection
Log. RFC destination Entry from transaction SM59 e.g. SAPFTPA
Remote directory and file name extension
Position of file name in directory
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_CADEVDOT | 0 | I010004300 | Clinical System |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20070103 |
| SAP Release Created in | 700 |
