| Literature DB >> 35045583 |
Ioannis Tamposis1, Ioannis Tsougos2, Anastasios Karatzas3, Katerina Vassiou4, Marianna Vlychou5, Vasileios Tzortzis3.
Abstract
BACKGROUND ANDEntities:
Mesh:
Year: 2022 PMID: 35045583 PMCID: PMC8769808 DOI: 10.1055/s-0041-1741481
Source DB: PubMed Journal: Appl Clin Inform ISSN: 1869-0327 Impact factor: 2.342
Fig. 1Diagram of PCaGuard physical architecture. The synthesis of the platform software is based on various components. The framework includes PACS component to store and exchange medical images, Mirth component to retrieving/communicating data from/to subsystems, Oracle database Express Edition to store data, Apache Tomcat as application server, BIRT component to generate reports. Furthermore, PCaGuard provides basic DICOM services and interacts with other systems through the HL7 protocol and web services. APEX, Application Express; BIRT, Business Intelligence Reporting Tool; DICOM, Digital Imaging and Communications in Medicine; HIS, hospital information system; HL7, Health Level Seven; HTTP, HyperText Transfer Protocol; MPPS, modality performed procedure step; MWL, modality work list; ORDS, Oracle REST Data Services; PACS, picture archiving and communication system; REST, representational state transfer; SOAP, simple object access protocol; VM, Virtual Machine; WADO, web access to DICOM object; XE, express edition.
Fig. 2Workflow activity diagram. DRE, digital rectal examination; PSA, prostate-specific antigen; MRI, magnetic resonance imaging; SSN, social security number; US, ultrasound.
Fig. 3PCaGuard's reporting application screen. mpMRI, multiparametric magnetic resonance imaging; TRUS, transrectal ultrasound-guided biopsy.