{'fraction_non_alphanumeric': 0.01860920666013712, 'fraction_numerical': 0.0, 'mean_word_length': 5.083333333333333, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Radiology information system control of a DICOM-based PACS

PACS implementations require IS data for efficient operation and coherent information management. The images contributing to a radiology report in a practical multi-vendor PACS implementation may be derived from more than one DICOM study, and it is the Radiology Information System (RIS) that is responsible for the report. Flows of existing RIS-based information were studied and the required set of messages between the PACS archive and the RIS was defined. An archive providing the required functionality using standard and extended DICOM protocols was specified and acquired. The DICOM interface for the RIS was developed in-house using the M(MUMPS) programming language native to the RIS. We found that close integration of a RIS and PACS can be provided using DICOM protocols employing extensions compatible with the standard. The DICOM interfaces for textural data can be implemented in a MUMPS-based RIS without the need for an external interface 'box'.