Clinical Application Administrator

We're Scan.com . We're building America's national imaging network: the infrastructure that connects patients, providers, and payers to faster, better-value diagnostic imaging. Thousands of patients move through our platform every day, and each is a real person waiting for an answer to a healthcare concern. We exist to get them that answer faster. We manage the medical imaging pathway end-to-end. Providers order through a single point of entry, and from there, we run the entire medical diagnostic pathway. Managing the full pathway, rather than brokering pieces of it, is what lets us deliver imaging faster, at higher quality, and at a lower cost than the fragmented status quo. We're looking for a Clinical Application Administrator at an exciting time. We've raised over $200m in funding to date, reached profitability, and are growing 100% year on year. Millions of people wait too long for a diagnosis. Come help us fix that.

What You Will Be Getting Involved in

Scan.com 's interoperability layer is what makes our network run. Every scan order that arrives from a referring physician, every radiology report delivered back to a provider, and every image routed through our PACS infrastructure depends on reliable integrations in production, every day. When they don't, patients wait longer, and providers lose trust. As Clinical Application Administrator , you will be on the front line of keeping that infrastructure healthy. You will monitor HL7 interfaces, triage and resolve failures, manage the support queue, and work alongside engineering, operations, and clinical teams to close issues and prevent recurrence. You will also play a hands-on role in onboarding new imaging center clients, configuring and validating DICOM and HL7 gateway connections from deployment through live production. This is a technically demanding operations role that rewards a deep curiosity about how clinical systems communicate with each other. You do not need to be a software engineer, but you need to be comfortable reading an HL7 message, diagnosing why it failed, and knowing what to do about it. As a scale-up business, you can expect your role to develop over time. Here are some of the types of things you could be getting involved in:

• Monitor and maintain active HL7 interfaces across ORM and ORU message types, ensuring orders and results are transmitted accurately and on time between Scan.com and partner systems
• Analyze HL7 message segments, including PID, PV1, OBR, and OBX, to diagnose data transmission failures and validate downstream delivery
• Reprocess failed messages and confirm successful resolution, maintaining detailed records of the issue, root cause, and corrective action
• Perform daily production support tasks, including report reprocessing, data corrections, and study transfers, to keep workflows running without interruption
• Manage the support ticket queue across Slack, Linear, and HubSpot, ensuring every issue has clear ownership, timely follow-up, and complete documentation
• Support PACS gateway operations alongside the Team Lead, including writing and maintaining scripts, pushing studies, troubleshooting connectivity issues, and validating image transfers
• Lead the technical deployment and configuration of DICOM and HL7 gateway software for new client onboarding, validating end-to-end image routing before go-live
• Collaborate with engineering, operations, clinical, and client support teams to investigate and resolve integration issues, and to implement longer-term fixes where recurring patterns emerge
• Document processes, issue resolutions, and configuration changes to build a reliable knowledge base for the team
• Identify opportunities for automation and workflow improvement within the integration support function
• Manage smaller-scale projects end-to-end, providing coordination and communication across stakeholders from initiation through delivery

The Top

5

Things We Want You to Achieve in Your First Year

• Production fluency. Within 60 days, you independently triage and resolve the majority of incoming support tickets, demonstrating a clear understanding of our interface landscape, escalation paths, and documentation standards.
• Interface reliability. You have measurably reduced the average time to resolution for HL7 failures and reprocessing requests, and you have helped eliminate at least one category of recurring failures through improved monitoring or process changes.
• Successful client onboardings. You have led the technical deployment and validation for new imaging center connections, completing them on schedule and with clean post-go-live performance.
• Documentation depth. The team's knowledge base is materially better because of your time here. Process documentation, gateway configuration records, and issue resolution logs are complete, up to date, and actively used.
• Continuous improvement contribution. You have identified and implemented at least one automation or workflow improvement that reduces manual effort in the support or onboarding process.

What You Might Bring to the Table

You don't need to tick all the boxes to apply for this role. Whether it's your first role or your fifth, we believe everyone can add value, learn, and grow. However, these might be some of the ways you are currently adding value:

• Working knowledge of HL7 v2 message structure, including common message types (ORM, ORU) and segment-level analysis (PID, PV1, OBR, OBX). You don't need to have built an interface engine from scratch, but you should be able to read a message and identify what's wrong with it
• Experience with an integration engine such as Rhapsody, Mirth Connect, or equivalent. Depth matters less than genuine familiarity and a clear appetite to develop further
• Familiarity with PACS, RIS, or EHR systems and the radiology workflow they support: from order to acquisition to interpretation to results delivery. Understanding this lifecycle is essential context for diagnosing where things break
• Familiarity with DICOM concepts and basic imaging terminology, including experience pushing, reprocessing, or validating imaging studies for troubleshooting purposes
• Strong organizational instincts. This role manages multiple concurrent issues across multiple platforms, and the person who thrives here keeps clear notes, closes loops, and doesn't let tickets go stale
• Clear written and verbal communication. You will work across technical and non-technical stakeholders and need to translate between them accurately and without jargon where it isn't warranted
• Experience in healthcare IT or clinical systems support is strongly preferred. Familiarity with the regulatory and operational context of healthcare makes a meaningful difference in this role

AI Requirements

At Scan.com , AI isn't a side project; it's how we work. We expect everyone to use AI to think faster, remove drudgery, and multiply their output. What we care about is judgment: knowing when AI makes you sharper, when it doesn't, and how to use it responsibly around patient data. We'll assess this in the way that matters for this role, using the tier below. You don't need to be an engineer. You need to be someone who reaches for the best tool and gets more done as a result.

• Tier 2 — For this role, the expectation is that you are AI-Amplified. AI is part of your daily workflow for drafting, analysis, and research, and you know how to check its output and use it responsibly with sensitive data. (most commercial, marketing, finance, people, and G&A roles)
• AI is part of your daily default. You use it to draft, analyse, research, and pressure-test your own thinking.
• You can show concrete examples where AI made your work meaningfully faster or better.
• You know its failure modes: you check its work, and you don't paste sensitive data into public tools.
• Assessment: We'll ask you to walk through how you'd use AI to tackle a real task from the role. A VIEW