MEDICAL CODING SPECIALIST-RISK ADJUSTMENT

We need to output HTML fragment with sections for headings where content exists. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the job posting. Key sections: - Description: includes "MAKE A DIFFERENCE AT OCHIN ..." etc. That's about the organization and role overview. Could be "About the role" or maybe "Overview". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings if present. We have: - Position Overview: description of role responsibilities. Could go under Responsibilities. - Essential Functions: list of duties. Could be Responsibilities. - Requirements: certificate, experience. - Base Pay Overview: talk about pay ranges. - Physical Requirements/Work Environment: maybe Skills? Or maybe Qualifications? Not exactly. Could be Qualifications? But we have separate Requirements and Qualifications. Usually Requirements = certifications, experience. Qualifications = maybe education, skills. But we can decide. - Work Location and Travel Requirements: maybe Schedule? Not exactly. Could be Schedule? Not given. - Work From Home Requirements: maybe Schedule? Not. - Benefits: mention "We offer a comprehensive range of benefits. See our website for details". That's a benefit statement but not detailed. According to rule: never create Benefits section unless posting actually states them. It does state "We offer a comprehensive range of benefits." That's a statement, albeit vague. Should we include Benefits section? It says "We offer a comprehensive range of benefits. See our website for details". That's substantive enough? It's not specific but it's a statement. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "We offer a comprehensive range of benefits" is not placeholder; it's a statement. So we can include Benefits section with that sentence. - Pay: Salary Description "$23.56 -$37.69 per hour". Also Base Pay Overview about broadened pay ranges. So we have pay info. So we include Pay section. - Schedule: Not mentioned. No schedule info. So we should not create Schedule section. - Skills: Not explicitly listed. Could infer from responsibilities but not explicit. Better not to create Skills unless explicit. - Qualifications: Could include education? Not given. Could include certification? Already in Requirements. Might combine. But we can have Qualifications maybe empty; better not to create if no specific content. Thus sections: About the role (maybe from description intro), Responsibilities (Essential Functions + Position Overview), Requirements (certification, experience), Benefits, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Let's extract substantive content. Intro description: "MAKE A DIFFERENCE AT OCHIN OCHIN is a nonprofit leader in health care innovation and a trusted partner to a growing national provider network, delivering the clinical insights and tailored technologies needed to expand patient access, strengthen care teams, and improve the health of rural and medically underserved communities. We are hiring for a number of new positions to meet increasing demand. When you choose to join OCHIN, you have the opportunity to continuously grow your skills and do meaningful work to help fulfill our vision of good health and well-being for everyone. At OCHIN, we value the unique perspectives and experiences of every individual and work hard to maintain a culture rooted in our values. Founded in Oregon in 2000, OCHIN employs a growing virtual workforce of more than 1,200 skilled professionals, working remotely across 49 states. We offer a generous compensation package and are committed to supporting our employees’ entire well-being by fostering a healthy work-life balance and opportunity for professional advancement. We are curious, collaborative learners who strive to live our values every day. OCHIN is excited to support our continued national expansion and the increasing demand for our innovative tools and services by welcoming new talent to our growing team." That's about the organization; could be About the role. Work Authorization: "Candidates must be legally authorized to work in the United States on a permanent basis at the time of application. This position is not eligible for employment visa sponsorship now or in the future. OCHIN does not provide sponsorship for employment-based visas or transfers of existing employment-based visas." This is substantive; could be part of Requirements? It's a requirement. We'll include in Requirements. Position Overview: "The Outpatient Coding Specialist plays a critical role in delivering accurate and high-quality healthcare coding services to OCHIN member clinics and acute care hospital organizations. This position is responsible for identifying potential high-risk coding trends, applying best practices to optimize revenue, and enhancing coding accuracy to support a streamlined and efficient revenue cycle. The Coding Specialist proactively escalates complex or unique coding issues, collaborates with supervisors to resolve challenges, and applies newly acquired knowledge to future scenarios. Additionally, this role contributes to continuous improvement efforts by recommending process enhancements that increase operational efficiency and effectiveness." Essential Functions list: - Accurate and Compliant Coding: Deliver efficient and accurate coding services on behalf of member clients, ensuring full compliance with payer requirements, organizational policies, and all applicable coding guidelines. - Clinical Data Abstraction: Extract and interpret relevant clinical data—including diagnoses and procedures—from patient medical records and electronic health systems to support accurate code assignment. - Code Assignment and Validation: Review and analyze patient encounters to assign appropriate diagnosis and procedure codes, ensuring accuracy and completeness for all relevant clinical information. - Reimbursement Optimization: Support member organizations in achieving appropriate reimbursement by reviewing and recommending accurate code assignments that are critical to third-party payer claims. - Provider Communication and Documentation Follow-Up: Conduct research and obtain additional information from providers or clinical staff via Epic In-Basket messaging, as needed and in accordance with established agreements. Messaging, as needed and in accordance with established agreements. (duplicate line) - Other duties as assigned. Note duplicate line "Messaging, as needed and in accordance with established agreements." appears twice; we should keep only once? The instruction: "Remove duplicated lines". So we need to deduplicate. Requirements: - Certificate of completion from: AAPC (CPC Certificate), AHIMA (CCS Certificate) or ADCA (CDC certificate) is REQUIRED. (Certification must be in hand at the time of your application). - Experience working with Epic EHR highly preferred. - Experience with FQHCs highly desired. Candidates with FQHC experience will be given priority. Base Pay Overview: "OCHIN uses broadened pay ranges to support equitable and market-aligned compensation practices. The final offer will be based on a variety of factors, including relevant skills, certifications, education, experience, training, responsibilities, internal equity, and market data." Physical Requirements/Work Environment: includes many bullet-like sentences but not list format. It says: "Constant interpersonal skills, teamwork, and customer service. Frequent creativity, mentoring, presentations/teaching. Occasional decision making and independent judgment or action.Reading, speaking, writing, and understanding English.While performing the duties of the job, the employee is regularly required to sit for long periods of time; stand and walk; use hands to finger, handle or feel; reach with hands and arms.This position requires a virtual home-office environment, working remotely and will require that employees be on camera for all virtual meetings.The role routinely uses standard office equipment such as computers and mobile devices." We could treat this as Qualifications or Skills? It's more about work environment. Not explicitly requested headings. Could be omitted if not matching headings. But we could put under "Requirements" maybe? But it's not a requirement; it's description of work environment. The instruction says to include a section only when posting has real, specific content for it. We have headings list; we could map this to "Qualifications"? Not exactly. Could be "Skills"? It mentions interpersonal skills, creativity, mentoring, presentations/teaching, decision making, reading, speaking, writing, understanding English, etc. Those are skills. So we could create a Skills section with those items as list. But we need to check if we already have Skills section; we haven't used it yet. So we can create Skills section with those items. Work Location and Travel Requirements: "OCHIN is a 100% remote organization with no physical corporate office location. Employees work remotely from home and many of our positions also support our member organizations on-site for new software installations. Nationwide travel is determined based on OCHIN business needs. Please inquire during the interview process about travel requirements for this position." That's about work location/travel; could be under Schedule? Not exactly. Could be under "Schedule"? Not really. Could be under "Benefits"? No. Could be under "Requirements"? Not. Could be under "Qualifications"? Not. Since we don't have a heading for location/travel, we might omit it if not matching allowed headings. But we could incorporate into "About the role" maybe? But it's substantive. The instruction: "Prefer a few substantive sections over many thin ones." We could add a section "Work Location" but not in allowed headings list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems we should only use those headings. So we must fit content into those headings. If content doesn't fit, maybe we drop it? But we must preserve ALL substantive information. So we need to find a way to fit location/travel into one of those headings. Perhaps "Schedule" could include remote work and travel? Not ideal but maybe we can treat "Schedule" as work arrangement (remote, travel). However schedule usually means hours/shifts. But we have no schedule info. Could we create a Schedule section with remote work and travel info? Might be acceptable as it's about work location/travel which influences schedule. But risk. Alternatively, we could treat location/travel as part of "About the role" (description of work environment). That seems plausible: About the role can include organization description and work arrangement. So we can merge location/travel into About the role. Similarly, Physical Requirements/Work Environment could go under Skills (as they are skills) or Qualifications. Let's decide. We have: - About the role: organization description + work location/travel + remote/home office + camera requirement maybe. - Responsibilities: Position Overview + Essential Functions (deduplicated). - Requirements: Work Authorization + Certification + Experience (Epic EHR, FQHC). - Skills: Interpersonal skills, teamwork, customer service, creativity, mentoring, presentations/teaching, decision making, independent judgment, reading, speaking, writing, understanding English, sitting long periods, stand/walk, use hands, reach, virtual home-office, on camera for meetings, uses standard office equipment. That's a mix of physical requirements and skills. Could be Skills. - Benefits: "We offer a comprehensive range of benefits. See our website for details: https://ochin.org/career" - Pay: Base Pay Overview + Salary Description. We should not create Schedule. Now we need to format. Use

  for each heading. Inside each, use

  for prose,

  • for lists. We need to ensure we don't repeat content. Let's craft About the role paragraph(s). Could be multiple paragraphs but we can combine. About the role:

    MAKE A DIFFERENCE AT OCHIN OCHIN is a nonprofit leader in health care innovation and a trusted partner to a growing national provider network, delivering the clinical insights and tailored technologies needed to expand patient access, strengthen care teams, and improve the health of rural and medically underserved communities. We are hiring for a number of new positions to meet increasing demand.