• Title/Summary/Keyword: quick services

Search Result 142, Processing Time 0.017 seconds

Consideration on Shielding Effect Based on Apron Wearing During Low-dose I-131 Administration (저용량 I-131 투여시 Apron 착용여부에 따른 차폐효과에 대한 고찰)

  • Kim, Ilsu;Kim, Hosin;Ryu, Hyeonggi;Kang, Yeongjik;Park, Suyoung;Kim, Seungchan;Lee, Guiwon
    • The Korean Journal of Nuclear Medicine Technology
    • /
    • v.20 no.1
    • /
    • pp.32-36
    • /
    • 2016
  • Purpose In nuclear medicine examination, $^{131}I$ is widely used in nuclear medicine examination such as diagnosis, treatment, and others of thyroid cancer and other diseases. $^{131}I$ conducts examination and treatment through emission of ${\gamma}$ ray and ${\beta}^-$ ray. Since $^{131}I$ (364 keV) contains more energy compared to $^{99m}Tc$ (140 keV) although it displays high integrated rate and enables quick discharge through kidney, the objective of this study lies in comparing the difference in exposure dose of $^{131}I$ before and after wearing apron when handling $^{131}I$ with focus on 3 elements of external exposure protection that are distance, time, and shield in order to reduce the exposure to technicians in comparison with $^{99m}Tc$ during the handling and administration process. When wearing apron (in general, Pb 0.5 mm), $^{99m}Tc$ presents shield of over 90% but shielding effect of $^{131}I$ is relatively low as it is of high energy and there may be even more exposure due to influence of scattered ray (secondary) and bremsstrahlung in case of high dose. However, there is no special report or guideline for low dose (74 MBq) high energy thus quantitative analysis on exposure dose of technicians will be conducted based on apron wearing during the handling of $^{131}I$. Materials and Methods With patients who visited Department of Nuclear Medicine of our hospital for low dose $^{131}I$ administration for thyroid cancer and diagnosis for 7 months from Jun 2014 to Dec 2014 as its subject, total 6 pieces of TLD was attached to interior and exterior of apron placed on thyroid, chest, and testicle from preparation to administration. Then, radiation exposure dose from $^{131}I$ examination to administration was measured. Total procedure time was set as within 5 min per person including 3 min of explanation, 1 min of distribution, and 1 min of administration. In regards to TLD location selection, chest at which exposure dose is generally measured and thyroid and testicle with high sensitivity were selected. For preparation, 74 MBq of $^{131}I$ shall be distributed with the use of $2m{\ell}$ syringe and then it shall be distributed after making it into dose of $2m{\ell}$ though dilution with normal saline. When distributing $^{131}I$ and administering it to the patient, $100m{\ell}$ of water shall be put into a cup, distributed $^{131}I$ shall be diluted, and then oral administration to patients shall be conducted with the distance of 1m from the patient. The process of withdrawing $2m{\ell}$ syringe and cup used for oral administration was conducted while wearing apron and TLD. Apron and TLD were stored at storage room without influence of radiation exposure and the exposure dose was measured with request to Seoul Radiology Services. Results With the result of monthly accumulated exposure dose of TLD worn inside and outside of apron placed on thyroid, chest, and testicle during low dose $^{131}I$ examination during the research period divided by number of people, statistics processing was conducted with Wilcoxon Signed Rank Test using SPSS Version. 12.0K. As a result, it was revealed that there was no significant difference since all of thyroid (p = 0.345), chest (p = 0.686), and testicle (p = 0.715) were presented to be p > 0.05. Also, when converting the change in total exposure dose during research period into percentage, it was revealed to be -23.5%, -8.3%, and 19.0% for thyroid, chest, and testicle respectively. Conclusion As a result of conducting Wilcoxon Signed Rank Test, it was revealed that there is no statistically significant difference (p > 0.05). Also, in case of calculating shielding rate with accumulate exposure dose during 7 months, it was revealed that there is irregular change in exposure dose for inside and outside of apron. Although the degree of change seems to be high when it is expressed in percentage, it cannot be considered a big change since the unit of accumulated exposure dose is in decimal points. Therefore, regardless of wearing apron during high energy low dose $^{131}I$ administration, placing certain distance and terminating the administration as soon as possible would be of great assistance in reducing the exposure dose. Although this study restricted $^{131}I$ administration time to be within 5 min per person and distance for oral administration to be 1m, there was a shortcoming to acquire accurate result as there was insufficient number of N for statistics and it could be processed only through non-parametric method. Also, exposure dose per person during lose dose $^{131}I$ administration was measured with accumulated exposure dose using TLD rather than through direct-reading exposure dose thus more accurate result could be acquired when measurement is conducted using electronic dosimeter and pocket dosimeter.

  • PDF

Design and Implementation of MongoDB-based Unstructured Log Processing System over Cloud Computing Environment (클라우드 환경에서 MongoDB 기반의 비정형 로그 처리 시스템 설계 및 구현)

  • Kim, Myoungjin;Han, Seungho;Cui, Yun;Lee, Hanku
    • Journal of Internet Computing and Services
    • /
    • v.14 no.6
    • /
    • pp.71-84
    • /
    • 2013
  • Log data, which record the multitude of information created when operating computer systems, are utilized in many processes, from carrying out computer system inspection and process optimization to providing customized user optimization. In this paper, we propose a MongoDB-based unstructured log processing system in a cloud environment for processing the massive amount of log data of banks. Most of the log data generated during banking operations come from handling a client's business. Therefore, in order to gather, store, categorize, and analyze the log data generated while processing the client's business, a separate log data processing system needs to be established. However, the realization of flexible storage expansion functions for processing a massive amount of unstructured log data and executing a considerable number of functions to categorize and analyze the stored unstructured log data is difficult in existing computer environments. Thus, in this study, we use cloud computing technology to realize a cloud-based log data processing system for processing unstructured log data that are difficult to process using the existing computing infrastructure's analysis tools and management system. The proposed system uses the IaaS (Infrastructure as a Service) cloud environment to provide a flexible expansion of computing resources and includes the ability to flexibly expand resources such as storage space and memory under conditions such as extended storage or rapid increase in log data. Moreover, to overcome the processing limits of the existing analysis tool when a real-time analysis of the aggregated unstructured log data is required, the proposed system includes a Hadoop-based analysis module for quick and reliable parallel-distributed processing of the massive amount of log data. Furthermore, because the HDFS (Hadoop Distributed File System) stores data by generating copies of the block units of the aggregated log data, the proposed system offers automatic restore functions for the system to continually operate after it recovers from a malfunction. Finally, by establishing a distributed database using the NoSQL-based Mongo DB, the proposed system provides methods of effectively processing unstructured log data. Relational databases such as the MySQL databases have complex schemas that are inappropriate for processing unstructured log data. Further, strict schemas like those of relational databases cannot expand nodes in the case wherein the stored data are distributed to various nodes when the amount of data rapidly increases. NoSQL does not provide the complex computations that relational databases may provide but can easily expand the database through node dispersion when the amount of data increases rapidly; it is a non-relational database with an appropriate structure for processing unstructured data. The data models of the NoSQL are usually classified as Key-Value, column-oriented, and document-oriented types. Of these, the representative document-oriented data model, MongoDB, which has a free schema structure, is used in the proposed system. MongoDB is introduced to the proposed system because it makes it easy to process unstructured log data through a flexible schema structure, facilitates flexible node expansion when the amount of data is rapidly increasing, and provides an Auto-Sharding function that automatically expands storage. The proposed system is composed of a log collector module, a log graph generator module, a MongoDB module, a Hadoop-based analysis module, and a MySQL module. When the log data generated over the entire client business process of each bank are sent to the cloud server, the log collector module collects and classifies data according to the type of log data and distributes it to the MongoDB module and the MySQL module. The log graph generator module generates the results of the log analysis of the MongoDB module, Hadoop-based analysis module, and the MySQL module per analysis time and type of the aggregated log data, and provides them to the user through a web interface. Log data that require a real-time log data analysis are stored in the MySQL module and provided real-time by the log graph generator module. The aggregated log data per unit time are stored in the MongoDB module and plotted in a graph according to the user's various analysis conditions. The aggregated log data in the MongoDB module are parallel-distributed and processed by the Hadoop-based analysis module. A comparative evaluation is carried out against a log data processing system that uses only MySQL for inserting log data and estimating query performance; this evaluation proves the proposed system's superiority. Moreover, an optimal chunk size is confirmed through the log data insert performance evaluation of MongoDB for various chunk sizes.