RCM Analyst

We need to output HTML fragment with sections: Role Overview (maybe as h3?), Essential Duties & Responsibilities (maybe split into subsections? but we need to use h3 for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has "Role Overview", "Essential Duties & Responsibilities", "Qualifications", "Education & Experience", "Knowledge, Skills & Abilities", "Working Conditions", "Benefits", "About Us", "Position Base Pay Range". We need to map to allowed headings: About the role (maybe Role Overview), Responsibilities (Essential Duties & Responsibilities), Requirements (maybe Education & Experience?), Qualifications (maybe Knowledge, Skills & Abilities?), Skills (maybe part of Knowledge, Skills & Abilities?), Benefits, Pay, Schedule. We should not create sections without real content. We have Benefits content, Pay content (Base salary range), Schedule? Not explicit schedule; Working Conditions mentions flexible hours, evenings or weekends if required. That could be considered Schedule? The instruction: include a section ONLY when posting has real, specific content for it. Schedule: we have "Must be able to work flexible hours, including evenings or weekends, if required." That's schedule info. So we can include Schedule section. We must not repeat job title as heading. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the long EEO paragraph, privacy policy, E-Verify, SMS opt-in etc. Also remove "About Us" maybe? It's substantive about company; we could keep as maybe not a required heading but we could include as maybe "About the company"? Not in allowed headings list. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use h3 for section headings (e.g. those). Likely we should stick to those headings only. So we should not include About Us as a separate heading; maybe we can incorporate into About the role? But About the role is for role overview. Could we add a paragraph about company under About the role? Might be okay but not required. Better to omit About Us entirely as it's not required heading; but we must preserve ALL substantive information. If we omit About Us, we lose substantive info about company. However maybe we can treat About Us as part of "About the role"? Not ideal. The instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid adding extra sections beyond the examples, but says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should not create other headings. So we need to fit all substantive info under those headings. We can put company description under About the role (maybe as a paragraph). That seems acceptable. We also have "Working Conditions" which could be part of Schedule? Or maybe we can treat Working Conditions as part of Schedule? But we have Schedule heading for schedule info; Working Conditions includes physical requirements (sit/stand, lift, etc.) and fast-paced environment. That is not schedule but working conditions. There's no heading for Working Conditions in allowed list. Could we incorporate into Schedule? Not really. Could we incorporate into Responsibilities? No. Could we incorporate into Requirements? Not really. Could we create a section "Working Conditions"? Not in allowed list but maybe allowed as it's not prohibited; the instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, but suggests those are typical. Safer to stick to those. We could put Working Conditions under Schedule? Not accurate. Could we put under Responsibilities? No. Could we put under Requirements? Not really. Could we put under Qualifications? Not really. Could we put under Skills? No. Could we put under Benefits? No. Could we put under Pay? No. Could we put under About the role? Could add a paragraph about working conditions there. That might be okay: About the role can include overview and working conditions. Thus we will have sections: About the role (h3), Responsibilities (h3), Requirements (h3), Qualifications (h3), Skills (h3), Benefits (h3), Pay (h3), Schedule (h3). We need to fill each with content from posting. Let's extract content. About the role: Role Overview paragraph(s). Also maybe include Working Conditions? We'll add a paragraph about working conditions after overview. Responsibilities: Essential Duties & Responsibilities broken into subparts: Reporting & Analytics, Payor Relations Support, Credentialing Analytics Support. We'll make a

  with each duty as
  • . Could also break into sublists but okay. Requirements: Education & Experience (Bachelor's degree preferred, 2-4 years experience, demonstrated experience building reports/dashboards in Power BI required, experience writing SQL required, experience with financial/operational/insurance data advantage). We'll put as
    . Qualifications: Knowledge, Skills & Abilities list. We'll put as
    . Skills: Could be overlapping with Qualifications; but we need a Skills section. Perhaps we can extract specific skills: Proficiency in Power BI, DAX, SQL, Excel, relational databases, ETL concepts, healthcare data familiarity, analytical/problem-solving, attention to detail, multitasking, communication, independent/collaborative work, commitment to data integrity. We'll put as
    . Benefits: list of benefits as given. Pay: Base salary range $70,000 - $80,000 USD. Also mention base salary and bonus structure? The posting says "Base salary and bonus structure" under Benefits? Actually after Benefits list: "Paid Time Off Diverse and Inclusive Work Environment Base salary and bonus structure". We'll include base salary range and mention bonus structure. Schedule: from Working Conditions: "Must be able to work flexible hours, including evenings or weekends, if required." Also maybe mention fast-paced environment etc. But schedule specifically about hours. We'll include that. We must not include boilerplate like EEO, privacy, E-Verify, SMS opt-in, etc. Now produce HTML fragment. We need to ensure we don't repeat job title as heading. No markdown. Let's craft. Section About the role:

    About the role

    then

    with role overview paragraphs combined. Then maybe another

    for working conditions? But working conditions could be separate paragraph. We'll combine overview and working conditions in one

    maybe too long but okay. Better: overview

    , then working conditions

    . Responsibilities:

    Responsibilities

    then
    with
    • items. We need to capture all duties: From Reporting & Analytics: - Develop, maintain, and enhance recurring reports, dashboards, scorecards, and ad hoc analyses supporting RCM operations. - Collect, validate, organize, and analyze data from practice management systems, billing platforms, payor portals, credentialing systems, contract databases, and other data sources. - Identify trends, variances, anomalies, and opportunities for improvement within operational and financial data. - Support the development and monitoring of key performance indicators and provide timely reporting to leadership and business stakeholders. - Perform data validation and reconciliation to ensure reporting accuracy, consistency, and integrity. - Assist with automating recurring reports and improving reporting processes to reduce manual effort. - Translate analytical findings into clear summaries, visualizations, and actionable insights for non-technical stakeholders. - Participate in projects involving data integration, reporting improvements, system enhancements, and operational optimization. Payor Relations Support: - Analyze payor performance, reimbursement trends, negotiated rates, underpayments, denials, and reimbursement variances. - Develop and maintain reporting processes to monitor negotiated reimbursement rates and payor compliance. - Support benchmarking of reimbursement across commercial insurance, Medicare Advantage, Medicaid, and other payor arrangements. - Assist with financial analysis related to payor contract negotiations, renewals, rate changes, and proposed contract terms. - Maintain and update contract and reimbursement information within internal databases and reporting tools. - Develop analyses and models to quantify the potential financial impact of reimbursement changes and other payor-related initiatives. - Assist with identifying and escalating trends that may negatively impact reimbursement, collections, or overall revenue cycle performance. - Support analysis of insurance contracts and reimbursement structures for existing and prospective practices. Credentialing Analytics Support: - Develop and maintain reporting related to provider credentialing, enrollment, participation, and related operational activities. - Track and report on credentialing status, enrollment progress, aging, expirations, turnaround times, and outstanding requirements. - Identify trends, bottlenecks, and opportunities to improve credentialing workflows and operational visibility. - Support data reconciliation and validation between credentialing records, provider information, payor data, and other relevant systems. - Maintain accurate and well-documented datasets related to providers, locations, payors, participation status, and credentialing activities. We'll list each as separate
    • . Requirements:

      Requirements

      with: - Bachelor's degree in Data Analytics, Business Analytics, Computer Science, Statistics, Information Systems, or a related technical field preferred. - 2 to 4 years of experience in data analysis, business intelligence, reporting, or related field. - Demonstrated experience building reports and dashboards in Power BI or a comparable business intelligence platform required. - Experience writing SQL queries to extract, transform, and analyze data from relational databases required. - Experience working with financial, operational, or insurance-related data is an advantage but not required. Qualifications:

      Qualifications

      with: - Proficiency in Power BI, including report building, data visualization, and working with data models. - Experience with DAX measures is a strong plus. - Working SQL skills with the ability to write queries independently, including joins, filters, aggregations, and subqueries. - Advanced proficiency in Microsoft Excel, including formulas, pivot tables, lookups, and structured data analysis. - Experience working with relational databases and understanding how data tables, relationships, and keys work. - Familiarity with ETL concepts, data pipelines, or data integration between systems is preferred. - Familiarity with healthcare data, practice management systems, billing platforms, or insurance data is helpful but can be developed on the job. - Strong analytical and problem-solving skills with the ability to identify trends, variances, and meaningful patterns in data. - Strong attention to detail and ability to work accurately with large and complex datasets. - Ability to manage multiple priorities and complete assignments within established deadlines. - Strong written, verbal, and presentation skills, with the ability to communicate analytical findings to both technical and non-technical stakeholders. - Ability to work independently and collaboratively in a cross-functional environment. - Commitment to data integrity, documentation, confidentiality, and continuous improvement. Skills: Could be similar but we need distinct. Maybe we can extract specific technical skills: Power BI, DAX, SQL, Excel, relational databases, ETL, healthcare data familiarity. We'll put as
      : - Power BI (report building, data visualization, data models) - DAX measures - SQL (joins, filters, aggregations, subqueries) - Microsoft Excel (formulas, pivot tables, lookups, structured data analysis) - Relational databases (understanding tables, relationships, keys) - ETL concepts and data pipelines - Healthcare data, practice management systems, billing platforms, insurance data familiarity - Analytical and problem‑solving skills - Attention to detail - Prioritization and deadline management - Communication (written