EHR staffing
Epic and Cerner staffing
Certified Epic and Cerner analysts, build and optimisation consultants, and at-the-elbow go-live support. We staff by module and by certification rather than by job title, because an Ambulatory analyst and a Willow analyst are not interchangeable.
Staffed by module, not by job title
The most common failure in EHR staffing is treating certification as generic. A requisition for an Epic analyst tells a recruiter almost nothing. An Ambulatory analyst, a Willow pharmacy analyst and a Beaker lab analyst hold different certifications, work with different clinical stakeholders and are not substitutable, and the market rate for each moves independently.
We screen against the specific module, the certification version, and whether the person has done build, optimisation or support, because those are three different jobs done by three different kinds of people.
Epic
Clinical modules
Ambulatory, ClinDoc and Inpatient, ASAP for emergency, OpTime and Anesthesia for perioperative, Stork for obstetrics, Willow and Willow Inpatient for pharmacy, Beaker for laboratory, Radiant for radiology, Cupid for cardiology, and Phoenix and related transplant modules.
Revenue cycle and access
Resolute Hospital Billing and Professional Billing, Prelude, Cadence, Grand Central, HIM and Identity, and Tapestry for managed care.
Reporting and technical
Clarity and Caboodle, Cogito, Reporting Workbench, Bridges interfaces, and Hyperspace and Citrix side technical roles.
Roles
Application analysts at all levels, principal trainers, credentialled trainers, application coordinators, integration and interface analysts, report writers, and Epic project managers.
Cerner
Millennium across PowerChart, FirstNet, SurgiNet, PathNet, RadNet, PharmNet, and CareAware device integration. Revenue cycle including Registration Management and Patient Accounting. HealtheIntent and population health. Discern reporting, CCL developers, and Cerner Command Language work.
Roles run from application analysts and solution architects through to build consultants, testing analysts and clinical adoption specialists.
Go-live and activation support
Activation is a specific staffing problem: a large number of people for a short, immovable window, all of whom need to be credentialled and badged before day one.
- At-the-elbow support at scale, sized to your go-live plan by department and shift, covering nights and weekends as well as days
- Super user backfill, because pulling your own clinical staff to support go-live creates a staffing hole on the units at exactly the wrong moment. This is where our clinical desk and our technology desk work together.
- Command centre staffing and triage
- Post-live stabilisation for the weeks after the vendor team leaves, which is when most of the real optimisation requests arrive
If you are backfilling clinical super users, tell us early. Credentialling a nurse to work your floors takes longer than onboarding a consultant to work your build, and go-live dates do not move.
Optimisation and legacy support
Most EHR work is not implementation. It is the years afterwards: upgrade readiness and testing, workflow optimisation after clinicians have found what does not work, decision support tuning, and reducing the click count that drives documentation burden.
We also staff legacy system support during and after a transition, including AR wind-down, legacy data access and archive projects, which is unglamorous work that consistently gets underestimated.
Contract, contract to hire, direct hire
EHR work suits contract engagement because it is genuinely project shaped. Build and activation are finite. Optimisation is continuous but variable. Many organisations run a small permanent core team and flex around it, and we staff both parts.
For related roles see IT and tech recruitment, and for clinical trial roles that are frequently confused with informatics see clinical research staffing.
Questions
Common questions
Do you only place certified Epic analysts?
For most build roles yes, because Epic certification is controlled and clients require it. Certification is generally obtained through employment at an Epic customer or partner, which is why the certified pool is finite and rates reflect that. For at-the-elbow and support roles we also place experienced non-certified staff with strong module familiarity, where the client accepts it.
Why does the module matter so much?
Because certifications are module specific and the work is not transferable. A Willow pharmacy analyst and a Beaker laboratory analyst have different certifications, different clinical stakeholders and different build logic. Hiring the wrong one costs you the requisition and the ramp time.
Can you staff a full go-live?
Yes. Tell us the go-live date, the departments, the shift pattern and the support ratio you are planning, and we will size and credential the team against it. Start early, because badging and access provisioning for a large activation team takes longer than most plans allow.
Can you backfill our clinical super users?
Yes, and this is one of the reasons we run clinical and technology desks together. Pulling experienced nurses onto go-live support leaves units short during the highest risk period of a transition. We cover the floor with contract clinicians while your own staff support the activation.
Do you staff Cerner as well as Epic?
Yes, across Millennium including PowerChart, FirstNet, SurgiNet, PathNet, RadNet and PharmNet, plus Discern reporting and CCL development, revenue cycle and HealtheIntent.
Are these roles remote?
Build, optimisation and reporting work is frequently remote or hybrid. Go-live and at-the-elbow support is onsite by definition. We will tell you which model a given candidate pool expects, because pricing a remote-market role as onsite is a common reason requisitions sit unfilled.