Pharmacy Application Support Engineer (L2 Support)

We need to capture each as separate bullet maybe. The text: "5+ years Core Imaging Technologies PACS AdministrationDICOM ProtocolsHL7 IntegrationRIS/PACS Workflow ManagementVNA AdministrationModality WorklistManagementImage Lifecycle Management". It's a run-on but we can split. Better to list each item: - PACS Administration - DICOM Protocols - HL7 Integration - RIS/PACS Workflow Management - VNA Administration - Modality Worklist Management - Image Lifecycle Management Similarly for Radiology Applications: "Life Image LILAMEDRADQPathEnterprise PACS SolutionsAdvanced Visualization PlatformsAI Imaging Analysis Tools". Likely list: Life Image, LILA, MEDRAD, QPath, Enterprise PACS Solutions, Advanced Visualization Platforms, AI Imaging Analysis Tools. Imaging Modalities: CT, MRI, Ultrasound, Nuclear Medicine, Digital Radiography, Mammography. Interface & Integration Technologies: DICOM, HL7 (ADT, ORM, ORU), TCP/IP Networking, VPN and Secure Data Exchange, Healthcare Interoperability Standards. We'll create

with each. Preferred Qualifications: Bachelor's Degree in Computer Science, Information Technology, Biomedical Engineering, Healthcare Informatics, or related field. Experience working in hospital, diagnostic imaging, or healthcare provider environments. Exposure to cloud-based imaging platforms and enterprise imaging initiatives is an added advantage. Skills: Could list DICOM, HL7, modality connectivity, radiology infrastructure, imaging workflow management, etc. But we already have many in qualifications. Might still create Skills section with list of specific technical skills: DICOM, HL7 (ADT, ORM, ORU), modality connectivity, PACS administration, VNA administration, advanced visualization platforms, diagnostic viewers, QA tools, image-sharing platforms, root cause analysis, etc. However to avoid duplication, we could skip Skills if content overlaps heavily with Requirements. But instruction: Prefer few substantive sections over many thin ones. We could combine Skills into Requirements or Qualifications. But we need to follow headings list; we can omit Skills if not distinct. However we have many skill details in responsibilities; maybe better to include Skills as a section summarizing key technical skills: DICOM, HL7, modality connectivity, PACS/VNA administration, advanced visualization, diagnostic viewers, workflow optimization, root cause analysis. We'll include. Benefits: list as per text. Pay: include range and incentive. Schedule: include remote/hybrid and in-office attendance. Now produce HTML. Check no boilerplate: remove NTT DATA description, EEO