PACS Administrator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay And Benefits section with pay range and benefits list. Also includes Workplace Type (hybrid) and Onsite Requirements (one day a month). Also includes Job Type & Location (Permanent based out of Dallas, TX). Also includes Application Deadline (but that's application instruction? Might be considered metadata; we should drop application instructions. The instruction says remove application instructions. Application Deadline is likely an instruction to apply by date; we should drop it. Also "About TEKsystems" etc is boilerplate about company; we should drop that as it's not specific to role? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About TEKsystems" is company description; might be considered boilerplate? It's not EEO but it's generic. Probably should remove as it's not substantive role info. Also "San Francisco Fair Chance Ordinance" etc is legal boilerplate; remove. Also "Use of Artificial Intelligence (AI)" is also boilerplate; remove. We need to keep: Description Summary (maybe as About the role?), Responsibilities (long list), Required Skills (maybe as Requirements or Qualifications), Onsite Requirements, Job Type & Location, Pay And Benefits, Workplace Type (maybe Schedule? Actually schedule not given; we have hybrid and onsite one day a month; that could be Schedule? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have sections: About the role (from Description Summary), Responsibilities, Requirements (maybe combine Required Skills and Bachelor's degree etc), Qualifications (maybe Certifications?), Skills (maybe same as Requirements?), Benefits, Pay, Schedule (maybe Onsite Requirements and Workplace Type). We need to avoid thin sections; prefer few substantive sections. We could combine: About the role (Description Summary). Responsibilities (the big block). Requirements (includes Required Skills, Bachelor's degree, etc). Benefits and Pay (maybe combine into Benefits & Pay). Schedule (Onsite Requirements + Workplace Type). Let's see. We must not invent or summarize away detail; preserve all substantive information. So we need to include all details from those sections. Let's extract: Description Summary: "The PACS Administrator is responsible for the administration, support, optimization and life cycle management of enterprise imaging applications and infrastructure, including Picture Archiving and Communication Systems (PACS), Vendor Neutral Archive (VNA), DICOM and HL7 integrations, image exchange platforms and advanced post-processing applications. The resource will serves as the technical expert for enterprise imaging workflows, ensuring the availability, performance, security and interoperability of imaging systems across the organization." Note grammar: "will serves" but we keep as is. Responsibilities: huge block; we need to keep all bullet-like sentences. It's currently paragraphs; we need to convert to

• for any list of duties/requirements/benefits. The responsibilities are a series of sentences; we can treat each sentence as a list item. Must preserve all info. We need to parse responsibilities into items. Let's copy the responsibilities section text: "Implementation: Evaluate project requests associated with the field of expertise and supported systems supported, conduct current state assessments, gather and define requirements, provide future state designs and perform application build activities. Manage implementation teams in the planning, design, development, testing (unit, application and integrated) and deployment of projects, as well as contributing to the development of associated training curriculum/program, post-implementation documentation and production support services. Ensure the system designs support corporate policies and federal legislation where applicable. Work with client departments to ensure solutions to complex business issues are an appropriate fit organizationwide. Project Management: Prepare detailed project plans. Manage the application team on adhering to project schedules and timelines and completing projects within the schedule and budget requirements. Identify and escalate issues to the appropriate sponsor group, steering committee or other governing body to ensure successful implementations (on time, on budget and within scope). Facilitate change request processes in relation to assigned projects. Prepare supporting documentation and present initial project requests and change requests to the appropriate change advisory subgroups. Provide weekly status updates on assigned projects. Work with management to coordinate necessary support with the Project Management Office (PMO) as needed. Maintenance/Support/Troubleshooting: Monitor, acknowledge and resolve ServiceNow tickets as assigned. Coordinate software and hardware patches, service packs and version upgrades with client departments and System Administrators. Create and maintain documentation for system procedures. Administrative: Log hours for project related work in the project portfolio management system (ServiceNow) on a weekly basis. Utilize ALM Quality Center system for developing test cases and scripts, monitoring test execution and creating documentation as required for production change control approval. Attend General Information Services (GIS) meetings, weekly Business Application Services team meetings, application team meetings when appropriate and other meetings as needed. Production Support/Maintenance: Provide on-call support (calendar defined by the specific group or application suite). Ensure the integrity, integration and stability of the production system. Formulate the system scope and objectives to develop or modify complex system designs. Follow the daily checklist for servers, services, log files, backups, scheduled SQL jobs, scheduled tasks, CPU usage, monitor space, transaction logs, etc. Provide interface maintenance and support. Ensure the coordination and documentation of hardware and software support and upgrades (SQL, Citrix servers, VMware, desktops, network, telecommunications, SAN storage, Internet applications, remote end users). Work closely with information technology (IT) resources during upgrades and issue resolution. Provide troubleshooting on application, process and technical issues. Identify required resources and coordinate all efforts until issues are resolved. Create documentation as needed. Coordinate and complete tasks during unplanned downtimes, including system maintenance. Support the training of Information Systems (IS) staff members and end users as needed. Manage and coordinate communication, including notifications on both scheduled and unscheduled downtimes to application teams and departmental super users and key stakeholders, vendor communication and staff communication. Provide daily communication to key business process owners and departmental system support staff members. Explain technical and software concepts to non-IS staff members. Stay current with new application functionality and enhancements. Consult vendor support sites, discussion forums and other sources to identify leading practices for issue resolution. Utilize vendor support sites to log issues for resolution assistance; coordinate with the Group Manager, System Administrators and client departments to implement recommended solutions. Perform other duties as assigned. Project Assignments: Design, develop and manage an implementation approach through the use of standard project management tools, such as work plans, change management tools and issue tracking. Analyze end user issues and determine and recommend optimum resolution based on system capabilities and end users' needs. Consult vendor support sites, discussion forums, and other sources to identify leading practices for system implementations. Consult with the department on enhancements to ensure integration with the existing environment. Participate in design, build, test, troubleshooting and conversion activities. Assume Project Lead responsibilities. Plan, direct, develop and coordinate the detailed process flow, design, implementation, performance management and documentation of software and hardware implementations. Coordinate and consult with end user departments to determine activities and business functions of the respective departments. Determine requirements for system software, hardware, interfaces and application integrations. Develop project plans with system specifications based on the defined requirements. Formulate and/or define project scopes and system objectives through the research of internal, external and independent sources. Serve as a Technical Lead to plan, coordinate and develop a comprehensive implementation plan for the specific aspects and components of project integrations. Develop project plans, including the definition and assignment of project tasks to team members. Establish timelines and project milestones. Monitor progress to ensure compliance with project requirements. Report project status and updates to management and/or the PMO. Serve as a Lead for technical, programming, support, vendor and end user staff members to determine system and resource requirements, utilization, installations, implementations and communication plans. Implement complex software, hardware, interfaces and upgrades within a multiple user, networked and integrated computer environment. Coordinate and manage system monitoring and performance enhancement activities to ensure optimal system performance and standards. Establish service level agreement metrics for the supported systems based on identified objectives in order to satisfy quality standards. Provide application expertise during planning and design. Develop and maintain test plans and scripts in ALM Quality Center. Work closely with management to coordinate vendor resources. Coordinate departmental testing efforts and regularly communicate with clients. Mentor and assist other System Analysts with more complex and difficult tasks. Identify and document current and future state analysis. Coordinate and document hardware and software implementations. Perform other duties as assigned." That is huge; we need to break into list items. Could split by sentences. But we need to preserve all info; we can just wrap the whole block in
  • each sentence. However that would be many items; but acceptable. Better: we can keep as paragraphs? The rule: Use
    • for any list of duties/requirements/benefits. So we must convert responsibilities to list. We'll split by periods that end sentences. Might be messy but doable. Similarly Required Skills: "7+ years of PACS/DICOM/VNA experience (preferably Sectra). Certified Imaging Informatics Professional (CIIP) from the American Board of Imaging Informatics (ABII). Project management experience. Bachelor's degree or equivalent experience." That's a list; we can make
      • each. Onsite Requirements: "The PACS Administrator will primarily work remotely but will be required to be onsite one day a month." Job Type & Location: "This is a Permanent position based out of Dallas, TX." Workplace Type: "This is a hybrid position in Dallas,TX." (Note duplicate location; but we keep.) Pay And Benefits: includes pay range and benefits list. We need Benefits section: list of benefits. Pay section: pay range. Schedule: maybe combine Onsite Requirements and Workplace Type as schedule? Could be "Schedule" heading with details: primarily remote, one day onsite per month, hybrid position in Dallas, TX. We must not create sections with filler. All have real content. We must not include duplicated lines; we see location repeated; we can keep once. We must not include boilerplate like "About TEKsystems", legal, etc. Now produce HTML fragment:

        About the role

        The PACS Administrator is responsible for the administration, support, optimization and life cycle management of enterprise imaging applications and infrastructure, including Picture Archiving and Communication Systems (PACS), Vendor Neutral Archive (VNA), DICOM and HL7 integrations, image exchange platforms and advanced post-processing applications. The resource will serves as the technical expert for enterprise imaging workflows, ensuring the availability, performance, security and interoperability of imaging systems across the organization.

        Responsibilities

        • Implementation: Evaluate project requests associated with the field of expertise and supported systems supported, conduct current state assessments, gather and define requirements, provide future state designs and perform application build activities.
        • Manage implementation teams in the planning, design, development, testing (unit, application and integrated) and deployment of projects, as well as contributing to the development of associated training curriculum/program, post-implementation documentation and production support services.
        • Ensure the system designs support corporate policies and federal legislation where applicable.
        • Work with client departments to ensure solutions to complex business issues are an appropriate fit organizationwide.
        • Project Management: Prepare detailed project plans.
        • Manage the application team on adhering to project schedules and timelines and completing projects within the schedule and budget requirements.
        • Identify and escalate issues to the appropriate