Hierarchy
IS-H (Software Component) SAP Healthcare⤷
IS-HMED (Application Component) Clinical System⤷
NMED_DS (Package) Departmental Solutions
IMG Activity
| ID | SIMG_ISHMED_CAGDTCUS | Settings for Software Calls on Work Station via GDT |
| Transaction Code | S_PRI_97000062 | (empty) |
| Created on | 20061215 | |
| Customizing Attributes | SIMG_ISHMED_CAGDTCUS | Settings for Software Calls on Work Station via GDT |
| Customizing Activity | IMG_ISHMED_CAGDTCUS | Settings for Software Calls on Work Station via GDT |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHMED_CAGDTCUS |
Use
Here you can store settings for the processing of examination data with external software (e.g. start of ECG entry or finding) using GDT files.
Requirements
Standard settings
Activities
If devices should be connected using GDT, you must make an entry in table TN2DS_GDT_CUST for each terminal and user.
The following entries are required:
GDT ID from the description of the connection of medical devices via GDT e.g. EKG01
GDT record type e.g. 6301
Terminal ID e.g. Windows name of front end server
SAP user ID SAP user for which the interface is intended
Recipient abbreviation from the device-specific interface e.g. EKG1
Sender abbreviation from the e.g. ISH1
GDT version e.g. 2.00
Physical file name fully qualified path, where the GDT file is expected
ending with '/' or '\'
Program name fully qualified path and name of the program to be started
Program parameter chain of characters for parameter transfer (e.g. user ID)
It is possible to enter the terminal ID and SAP user strings in the fields, or use * entries. When searching for strings * entries are not taken into account and only found during the last search step. This means that, e.g. on a work station on which external software has been installed, all users can work or the start of the program can be restricted. In a terminal server environment it is possible to enter a string for the terminal ID and qualified SAP user names to restrict the start of the software to some users.
The search sequence is as follows:
- unique entry for user and terminal
- unique for user and string for terminal
- unique for terminal and string for user
- unique for terminal and * for user
- string for terminal and string for user
- string for terminal and * for user
Example
Example data records:
Inst ID Record Term. User Rec. Send GDT-v. Path Program Parameter
0001 EKG01 6311 nt6* USER EKG1 ISH1 2.00 H:\...\ ...\ekg.exe /U:eigener User,pw
0001 EKG01 6311 nt60 * EKG1 ISH1 2.00 H:\...\ ...\ekg.exe /U:General. User,pw
In the first row the user 'USER' can start the software 'ekg.exe' on all servers which begin with 'nt6' (e.g. terminal server environment), by transferring his user ID as a parameter.
In the second row all users are allowed to start the software on server nt60, however, a collective user must be used for logging on.
Asterisk entries for the terminal do not make sense (external software for the GDT start is not usually installed throughout the clinic). The points in the example paths are inserted to save space.
Example
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| 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_CAGDTCUS | 0 | I010004300 | Clinical System |
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 |
| TN2DS_GDT_CUST | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20070315 |
| SAP Release Created in | 700 |
