What the work actually involves
You will be reading AI-generated responses about front-end revenue cycle scenarios and judging them the way you would judge a new registrar's work. A prompt might involve a self-pay patient presenting for an outpatient MRI, a Medicare Secondary Payer questionnaire, a coordination-of-benefits conflict, or a scheduling intake that would predictably produce a front-end denial. Your job is to decide whether the model's answer is operationally correct, catch the specific error, and write feedback that a model trainer who has never worked in a hospital can act on.
Typical tasks include scoring paired responses, annotating factual and procedural errors, rewriting model output into a correct gold-standard answer, and occasionally authoring original scenarios drawn from workflows you've actually managed. Volume and task type shift as the lab's priorities move; some weeks lean toward evaluation, others toward writing reference material.
What the screen looks for
- Verifiable operational depth. Expect follow-ups on eligibility verification mechanics, authorization vs. referral distinctions, POS collection scripting, and how registration errors surface as downstream denials. Generic revenue cycle vocabulary does not survive a second question.
- Leadership scope. The listing asks for 5+ years in patient access with at least 2 at manager or director level. Be ready to name team size, facility type, and the KPIs you personally owned.
- System fluency. Epic, Cerner, or Meditech registration and scheduling modules — specific workqueues and build experience carry weight. CHAM or CHAA is preferred, not required.
- Written precision. Feedback quality is the deliverable. The screen samples your writing directly.
Logistics
Fully remote and asynchronous, with no set shifts. Contributors commonly report 10–20 hours per week, though availability requirements vary by project batch and can change on short notice. Pay is observed at $80/hr for this listing; Mercor sets rates per engagement and terms are not guaranteed. Engagements are contract-based and typically run in defined cycles rather than open-ended.