A complete application in a minute — tailored resume and cover letter, ready to send.
MLK Community Healthcare seeks a Lead PACS Administrator / Imaging Informaticist to serve as the senior technical authority for the enterprise imaging environment. You will design architecture, arbitrate complex decisions, and own the end-to-end plan for Visage PACS and VNA migration while coordinating with the contracted radiology group and internal teams.
This working leadership role emphasizes hands-on architecture, problem-solving, and lifting the technical bar across the imaging informatics
The Lead PACS Administrator / Imaging Informaticist / Enterprise Imaging Architect (the "Lead") is the senior technical authority for the health system's enterprise imaging environment and the technical leader of the imaging informatics staff. Beyond the design and hands-on scope of a senior architect, the Lead sets architecture standards, arbitrates the hardest technical decisions, owns the end-to-end technical plan for the Visage PACS and VNA migration, and serves as the standing technical liaison to the contracted radiology group and to the network, desktop/endpoint, and application teams. The Lead provides technical direction and mentorship to architects, analysts, and PACS administrators, and is the deepest technical escalation point below the Director. This is a working leadership role: most of the Lead's time is hands-on architecture and problem-solving, with the added responsibility of raising the whole team's technical bar and making cross-entity coordination actually function.
Biweekly
Salary Range (Depending on Experience)
$116,241.26 - $170,173.95
The Lead PACS Administrator / Imaging Informaticist / Enterprise Imaging Architect (the "Lead") is the senior technical authority for the health system's enterprise imaging environment and the technical leader of the imaging informatics staff. Beyond the design and hands-on scope of a senior architect, the Lead sets architecture standards, arbitrates the hardest technical decisions, owns the end-to-end technical plan for the Visage PACS and VNA migration, and serves as the standing technical liaison to the contracted radiology group and to the network, desktop/endpoint, and application teams. The Lead provides technical direction and mentorship to architects, analysts, and PACS administrators, and is the deepest technical escalation point below the Director. This is a working leadership role: most of the Lead's time is hands-on architecture and problem-solving, with the added responsibility of raising the whole team's technical bar and making cross-entity coordination actually function.
EHR: Oracle Health (Cerner) Millennium. Radiology: migrating from the incumbent PACS to Visage 7 for PACS, enterprise viewing, and VNA. Cardiology: Fujifilm Synapse for cardiovascular PACS and VNA. Service lines supported include inpatient and outpatient radiology, cardiology, interventional radiology (IR), and a cardiac cath lab, across the hospital and the medical office building (MOB). Study volume is high, driven by a busy emergency department and the imaging needs of underserved communities, so imaging systems are effectively always in use and downtime tolerance is low. Reading workflow adds real complexity. Diagnostic radiology is provided by a contracted radiology group from another health system. That partner operates its own network segment, its own reading workstations, and its own instance of the reading and worklist tools (Visage and Medicalis) inside our facilities. Study routing, worklist orchestration, and report return therefore cross an organizational boundary this role does not fully control. When the partner changes its desktop image, its Visage instance, or its Medicalis configuration, the effect can surface as a problem on our side, and resolution requires coordinated troubleshooting across two organizations and across our own network, desktop, and application teams. Supporting the Visage radiology migration through cutover and stabilization is a near-term priority.
Because the imaging environment spans two organizations and several internal teams, the Lead is accountable for making cross-entity, cross-team coordination work in practice. The Lead owns the documented demarcation between our systems and the partner's, runs structured incident command when imaging is affected, and is the person other teams and the partner call first. The Lead sets the standards, runbooks, and change-review practices that keep a change on one side from silently breaking the other and builds the durable relationships across the contracted radiology group and the network, desktop, and applications teams that let fixes happen fast when no single team owns the whole problem. This leadership of collaboration, more than any single technology, is the defining feature of the role and is weighted heavily in selection.