Title
RAD IC: Patient Management via MITRA Simple Interface (MSI)
Formatting HCM Messages for RAD IC - PACS Communication.

Purpose
Filter program for the conversion of HCM - result files (./NTISH.dat)into corresponding MSI event types.
The program RN2_MSI_ADT interprets the HC-M result fileNTISH.dat. This contains all ADT events set for the recipient PACS inHCM customizing.
This displays the IS-H events in the MSI event typesPatient_Updated, Patient_Merged, Patient_Admitted,Patient_Transferred, Patient_Discharged, Visit_Updated, Visit_Cancelled.
For each HCM message, the system will create an MSI file in the targetdirectory.
The file name results from the HCM message number (8 Byte) and thedefined file name extension (standard msi) and is constructedaccording to the logical file (standard ISHMED_RAD_MSI_FILE, seeTA File).
If all HCM messages signal an error-free structure, the system willdelete the NTISH.dat file.
You can test the program and the link to the PACS Broker in the dialog.For testing purposes, you can use the available options in the selectionscreen.

Integration

• You must plan this program as a periodic batch.


• With varying file names, you must plan a variant. The logical file name
and syntax of the MSI output file are specified in the transactionFILE.

• The MSI files written into the target directory are usually transferred
to the MITRA PACS Broker via FTP. The delivered template for this is theMS Windows NT script msiput.cmd (download with program RN2L210). Youmust configure the access for the FTP.

Prerequisites
The files are guided using the user name which was used to start the SAPsystem. This user must be authorized to write and delete files (seedocumentation concerning the OPEN DATASET command). The authorizationobject is called S_DATASET. We recommend the Read (33), Writeand Delete (34) activities.
If several frontend or application servers exist, depending on whichwhich you are writing to, you must set up a logical connection to aphysical output path so that the storage location can be reached fromall servers.
If necessary you can set up the logical file name in use with theFILE transaction.

Features

Selection
Selection parameter,,Standard value
HC-M Source File,,\usr\sap\work\ishcm\pacs\NTISH.dat
Logical Name MSI Target File,,ISH_MED_RAD_MSI_FILE
with Options
Selection parameter,,Standard value
MSI File Name Extension,,msi
Prefix for Patient ID or Case ID,,Space
Delete HC-M File after Action,,X

Output
In batch processing, the system will write the MSI files to the physicalor logical directory on the application server defined by the logicalfile name.
In dialog-oriented test mode, the system will output the program on thelocal PC under \usr\users\PACS\.

Activities
Refer to the Implementation Guide Industry-Specific ComponentClinical System --> i.s.h.med: Radiology --> Component i.s.h.med: RAD IC--> Patient Management --> Patient Management with the MITRA PACS Broker
.


• If necessary, you define a logical file name (transaction FILE)


• You create a program variant for the production system


• You schedule periodic batch-job for converting HCM messages into MSI
event types

• If necessary, transfer MSI files to the MITRA PACS Broker possibly by
using msiput.cmd

• You schedule the deletion of job logs older than one day with standard
jobs for the daily run