Current Framework for Dicom Annotations and Viewer - Case Study Example

ANALYSIS DIMCOM al Affiliation) Key words: Analysis, Dicom Table of Contents Table of Contents 2 Introduction 3 CHAPTER4: DICOM ANALYSIS 3 4.1 Current System for Dicom Viewer and Annotations 3 4.2 Requirements 6 4.2.1 Functional Requirement 6 4.2.2 Non-Functional Requirements for proposed system 9 4.3 SWOT Analysis Table 9 4.4 MoSCoW Analysis table 10 4.5 Risk and mitigation Table 10 4.6 Summary 11 Reference 12 Introduction The section analyses the current framework for Dicom Annotations and Viewer which have been discussed in chapter 2. The paper further discusses problems in the systems; database, user interface, security reasons, storage of Annotations and Dicoms in the viewing and account of the user. Consequently, it highlights the rich picture of the current annotations and Dicom program. The section also talks on the current system like the functional and non-functional necessities for the current system. The functional of the current system include the user register, user login, opening Dicom images, adding annotations, saving the Dicom to user folder, and creating new projects with the names for annotations and Dicom. Other functional of the current system include viewing the available annotations and dicots and creating screen shots for the uploaded files and their annotations. Conversely, some of the non-functional requirements include the security, performance, reliability, adaptability, compatibility, and navigation. CHAPTER 4: DICOM ANALYSIS 4.1 Current System for Dicom Viewer and Annotations The DICOM standard was developed by National Electrical Manufacturers Association (NEMA). NEMA developed DICOM so that the workflow efficiency and compatibility between medical services, imaging systems, and other systems in the hospital can be improved. Their creation has been the crucial guideline for communication the medical images and is used by almost every equipment manufacturer. Image files conforming to the standards of DICOM are known as the DICOM format images. Honoring the DICOM standards the vendors of imaging equipment has assisted in communications of cross machines and has enabled possible integration for the imaging tools from various manufacturers. Although the standard is widely accepted for the networking and storage of medical images, the images are encoded in format that cannot be easily viewed on any personal computer. When the images are viewed outside the network of radiology, the printing of images on the hardcopy films will still be required. Due to reduction in the prices of peripheral devices and hardware, machines having higher hardware specification can be found at affordable prices. The DICOM images can only be viewed when the DICOM browsers are available. The software is very expensive and cannot be easily accessible by an average radiologist. The software is called PROPAXX where by it is used in archiving, processing, and viewing thereby offering a flexible and functional support for diagnosing the acquired x-ray images. The software has a wide spectrum of possibly in optimizing and analyzing image data. The software also incorporate a selection of assisting functions and administrative tools like the integrated interface for issuing finding reports to synchronize the images from a synchronic viewing. The software has various features like region windowing, and zoom visualization. The software is DICOM compatible and compliant with the CONAXX image, DICOM complaint consoles, CD packages provided by WIROMA, and CD systems provided by WIROMA. The above systems have embraced problems in their validation, user interface, security framework, and storage of the Annotation in the viewing and account of users. 4.1.1 Rich Picture of Current Dicom and Annotations Program DICOM PROPAXX vet 4.2 Requirements The requirement definition defines the functional and non-functional requirement of the crucial enhancements on the current system. The enhancements are defined for the previous iteration of the project that contains the DICOM operations. The requirements documented here are meant to improve the usability of the application; the imaging fraternity has shared list features, requested text searching and an improved user interface, and DICOM usage to integrate better with other tools. 4.2.1 Functional Requirement Functional Requirement Description and Justification User Register Enables the user to create an account, registering using a person’s name and password User login Here the client uses the name and password he used during registration Open Dicom images The user is given a provision of opening the already uploaded or stored images. In addition he is given options for uploading and other annotation software’s after clicking Dicom upload Add annotation, draw, text, arrow, color select After opening of the file, the image will be made available for viewing, from here the user can either add, Save files to User folder The features found on the annotations menu like the draw, text, and arrow can be added and the loaded annotations can be saved to files through uploading from the computer Save annotation to database The annotations can be saved on the annotations and before doing this, a project need to be created before entering the annotations name Create new projects with names for annotations and DICOM Before saving to the database, the annotation name will be created. The success or failure message will be displayed on the screen View Available annotations and DICOMS After the annotations have been loaded, the saved annotations will be seen and one can easily click on the DICOM and annotation for viewing. Annotations and DICOM sharing with other users Once the DICOM and annotations have been opened, and downloaded, a person can either share or delete it. This is achieved by clicking the ‘share’ button Creating Screen Shots The screen shots will be created from the available DICOM and annotations. Table 2 Functional Requirement for the Customer Functional Requirement Description User Register Enables the user to create an account, registering using a person’s name and password User login Here the client uses the name and password he used during registration Open Dicom images The user is given a provision of opening the already uploaded or stored images. In addition he is given options for uploading and other annotation software’s after clicking Dicom upload Add annotation, draw, text, arrow, color select After opening of the file, the image will be made available for viewing, from here the user can either add, Table 3 Functional Requirement for the Administrator Functional Requirement Description Create new projects with names for annotations and DICOM Before saving to the database, the annotation name will be created. The success or failure message will be displayed on the screen View Available annotations and DICOMS After the annotations have been loaded, the saved annotations will be seen and one can easily click on the DICOM and annotation for viewing. Annotations and DICOM sharing with other users Once the DICOM and annotations have been opened, and downloaded, a person can either share or delete it. This is achieved by clicking the ‘share’ button Creating Screen Shots The screen shots will be created from the available DICOM and annotations. 4.2.2 Non-Functional Requirements for proposed system Functional requirement Description and Justification Security The medical practitioners use the software for storage of medical reports and other fundamental details of the patient in a manner that is secure Performance DICOM is taken to be a well performing application. It has developed a proper system for communication between the users and the server together with keeping the records updated. Navigation The DICOM annotation and their image processing can be navigated easily to perform their tasks in a simple, error-free and in an independent manner. Reliability From the studies, DICOM have been offering greater help and reliability to medical practitioners in keeping patients records together with their effective communication. Compatibility When preparing and creating the annotations and image processing for DICOM, some of the compatible websites are Csharp, SQL, Cascading Style Sheets, Hypertext Mark-up Language, and MVC 4. Usability The software is user friendly and offers the users with appropriate facility for communication. Adaptability The application can be can be adapted for utilizing data storage in an effective manner like the JavaScript. HTML can be used as a hypertext for www and as an editorial phenomenon to develop the complex instruments. 4.3 SWOT Analysis Table Strength SDO-Cross Coordination DICOM, imaging the domain expertise, incubators for the integration of imaging concepts Weakness Depending on other WGs in participating in liaison efforts Opportunity Aligning the Web service of DICOM with FHIR Threat Imaging the integration standards that are handled in various DICOM applications and crumbling under a squeezed interest 4.4 MoSCoW Analysis table Must Have The solutions must abide with the DICOM. It must have a valid DICOM object for any given application The solution needs to support multiple DICOM applications The solution must be error free when the DICOM application is used Should Have The proposed coding system should inclined with the DICOM object application like the HL7 having a radiology report in HL7 system Could Have The solution could produce a query DICOM object at any time Won’t Have None 4.5 Risk and mitigation Table Risk Mitigation Images being down-right personal Use the masking techniques to blur the entire face through human guidance. Using any visible pathology for identification A software need to be written in fixing the problem Images rendered unused through extensive editing Application of anonymization approach on the image pixels Encrypting a DICOM image with its entirety One needs to embed the encrypted object into one that is regular and be conducted via the conventional protocol traffic just like the DICOM standard. 4.6 Summary Without overstating anything, none of the risk is a reason to disenchanter someone from building a project that is very secure for a clinical practice. On top of the application specific for the DICOM, there are various tools spectrum like the policies, digital signatures, access logs, and VPN which are available in designing an almost near perfect DICOM annotations and image processing. Securing the workflow will remain to be the best technique to secure DICOM. For a successful project one needs to work with potential providers and IT for security options. One needs to have a proper application that will support it. In this project one to be cautious with the identification of DICOM when the DICOM leaves the secured database especially when sharing it. The most fundamental DICOM anonymization will mitigate the problems and will safeguard the application (Oosterwijk & Gihring, 2000). Reference Oosterwijk, H., & Gihring, P. 2000. DICOM basics. Aubrey, TX: OTech Inc., Cap Gemini Ernst & Young. Read More