Governance and the operating question
The operating question is one sentence and the clinical ultrasound director is named and funded.
The program needs one sentence describing what it is for, and a body with the authority to enforce that sentence.
Governance formed after purchase is not governance. It is a ratification body, and everyone in the room knows it. Enterprise imaging governance should be established across the clinical, technology, information, and financial domains before technology selection begins, which is the sequence the HIMSS, SIIM, and AIUM collaborative recommends and the sequence most organizations reverse.
The operating question
Before structure, purpose. A POCUS program can be built to serve any of four distinct objectives, and they are not variations on a theme.
| Operating question | Primary setting | What the program optimizes for | Where the value shows up |
|---|---|---|---|
| Diagnostic acceleration in acute care | ED, ICU, inpatient | Time to decision, avoided advanced imaging | Length of stay, throughput, radiation avoidance |
| Sonographer and echo lab capacity relief | Cardiology, radiology, vascular | Offloading routine acquisition from specialized staff | Backlog reduction, staff retention, complex study capacity |
| Access expansion | Ambulatory, rural, post-acute, home | Reaching patients who currently do not get imaged | Diagnosis rate in underserved populations, referral avoidance |
| Procedural safety and guidance | Anywhere procedures happen | Complication reduction, first-attempt success | Safety events, procedure time |
These four require different device distributions, different operator populations, different documentation, different payment logic, and different measures of success. An access expansion program built in ambulatory sites runs headlong into prior authorization, which the acute care program never encounters. A capacity relief program depends on expanded operators, which the procedural safety program does not need at all.
Choosing all four is the most common way to build none of them. Pick one as the operating question and let the others be secondary benefits you do not have to defend. Write it in a single sentence and put that sentence at the top of the charter.
Structure
Governance body. Representation from clinical departments in scope, imaging informatics, enterprise IT, radiology, nursing leadership, quality, medical staff services, biomedical engineering, and the three financial and access functions described below. The chair should be clinical. The body needs decision rights over device standards, workflow design, privileging criteria, and expansion sequencing, and it needs those rights in writing.
Finance, revenue cycle, and patient access. These belong in the room from the first meeting, not consulted at the business case stage and not brought in when denials start appearing. They are three distinct functions and each one holds something the program cannot build around.
Finance owns the model. If finance does not build the business case, someone else builds it and finance later declines to defend it. The model assumptions, particularly the distinction between charges and collections covered in Phase 5, have to be theirs.
Revenue cycle owns whether documentation becomes payment. They know which payers deny which ultrasound codes in your market, which modifiers are required, how your charge master is structured, and what your current denial and downcode pattern looks like. Documentation template design is a revenue cycle collaboration, not a clinical informatics exercise reviewed by revenue cycle afterward.
Patient access and registration is the function nobody invites and the one encounter-based workflow depends on most directly. In encounter-based imaging, the modality worklist is generated from registration and admission events rather than from an order. Registration accuracy, timing, and the handling of unregistered or pending-registration patients determine whether studies attach to the right encounter at all. In ambulatory settings, access management also owns prior authorization, eligibility verification, and scheduling, which are the operational choke points on outpatient POCUS.
Bringing these three in late is the most common structural error after skipping infrastructure, and it produces the same result. The program works clinically and cannot demonstrate that it worked.
System-wide clinical ultrasound director. The director owns program goals, privileging processes, quality assurance, device standards, and the relationship with senior management. Adequate planning for this position is described in the implementation literature as vital to program health, with published resourcing guidance placing the role in the range of 0.1 to 0.3 FTE and recommending that the budget also cover support staff and office space.
That last part is where programs cut. The FTE gets funded and the support structure does not, which converts a program leadership role into an administrative one performed by a clinician between shifts. Fund the role and the scaffolding around it, or scope the program to what the role as funded can actually carry.
Champions. Respected clinical champions with authority and formal backing from every leadership tier are identified in the implementation literature as the key factor in program success. At URMC, integrating fellowship-trained POCUS physicians into individual departments and developing physician champions is reported to have significantly improved both utilization and compliance. Champions are not volunteers. They are a staffing decision.
The approval map
The pre-deployment work requires sign-off from departments that most program charters never mention. Map each one, name the person who holds the gate, and get a written statement of what they will require.
| Function | What they hold | Typical requirement |
|---|---|---|
| Imaging informatics | Archive integration, DICOM conformance | Modality worklist design, storage architecture approval |
| Enterprise IT | Network, interfaces, identity | Interface build and testing, bandwidth capacity |
| Cybersecurity | Device network admission | Encryption, segmentation, authentication, patching commitments |
| Supply chain | Procurement pathway | RFI and RFP process, contract terms |
| Clinical engineering | Device connection and maintenance | Inventory, network connection, replacement and failure processes |
| Infection prevention | Reprocessing | Disinfection protocol per device type and per application |
| Legal and compliance | Record scope, retention | What constitutes part of the medical record, retention period |
| Billing and coding | Charge capture | Documentation requirements, charge trigger design |
| Revenue cycle | Claim adjudication | Payer-specific documentation, modifier logic, denial monitoring |
| Patient access and registration | Encounter identity | Registration timing and accuracy, worklist source data, prior authorization workflow |
| Finance | Business case ownership | Model assumptions, charges versus collections discipline |
| Medical staff services | Privileging | Pathway approval, competency documentation standards |
Wi-Fi capacity is worth naming explicitly. Handheld and cloud-connected devices depend on secure wireless connectivity, and enterprise deployment frequently requires bandwidth upgrades that belong to a different budget and a different timeline than the program itself.
Scale and sequencing
Decide now whether initial deployment covers all clinical groups or a targeted subset, and design the informatics, finance, and governance infrastructure against the envisioned final scale rather than the initial one. Achieving clean success in one or two clinical groups is a better foundation than partial success in eight. Sequence departments on patient volume, clinical urgency, and demonstrated readiness, in that order, and be willing to defer a department that wants in but is not ready.
Educational scanning deserves a decision at this stage rather than later. Training exams fall into two categories, those performed without a clinical indication purely for learning and those clinically indicated and performed under supervision. Whether they are stored, where, and for how long has to align with institutional policy on the scope of the medical record and applicable retention requirements. It is tempting to defer this when resources are tight. The need for POCUS education is universal enough that the infrastructure for training exams should be included in initial deployment rather than retrofitted.
What to require from your vendor
Named implementation ownership rather than an account team, with the individual identified and their other commitments disclosed. Reference deployments at comparable scale and complexity, with permission to speak to the informatics lead rather than the clinical champion. A written statement of what they do not do, which is the single most informative document you can request and the one least often provided. Confirmation of which integration work is included and which is billable professional services, in writing, before the capital conversation begins.
If your organization is running both a device selection and a workflow solution selection, expect two separate procurement processes with different vendors, and recognize that the two are tightly interdependent. Every device selected must be compatible with the workflow solution chosen. Managing those processes as though they are independent is how organizations end up with devices that cannot participate in the workflow they just bought.
Failure mode
Governance is chartered after the capital purchase is approved. The body's first meeting is briefed on decisions already made. Clinical members conclude the program is an IT rollout with a clinical veneer, participation becomes nominal, and the governance function degrades into a monthly status report.
Gate criteria
This workstream is done when the charter is approved by executive leadership, the operating question is written in one sentence, the clinical ultrasound director is named and funded at a level that matches the scope, the approval map is complete with named owners, and the initial deployment scope is defined against a stated final-state scale. Governance and pathway mapping can and should proceed in parallel.