Revenue Cycle Analyst

We need to output HTML fragment with sections: About the role (maybe Position Summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for headings. Use

• for lists. Use

  for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. We need to parse the posting. Key sections: Position Summary: first paragraph: "Position Summary At Stony Brook Medicine the Revenue Cycle Analyst will provide operational support and analytical and reporting services throughout the hospital’s Business Office. This position will work closely with subject matter experts in their assigned area to support day to day business functions, performance improvement initiatives, reconciliation, benchmarking and reporting. Candidates will possess a high degree of both technical and analytical aptitude with a history or background which demonstrates an ability to: 1) summarize, analyze and report business data; 2) adopt and master software tools/platforms; 3) effectively communicate (written & verbal) business process, objectives and trends." Then Duties: "Duties of the Revenue Cycle Analyst may include the following, but are not limited to: Analyze claims and remittance data and present findings to departmental leadership.Complete variance and trend analyses via spreadsheets, databases and dashboards. Create audit and reconciliation plans related to: charges, adjustments, expected reimbursement and denials; accelerated and unposted cash.Document and validate business processes and business systems configuration, including: Patient Billing, Claims Scrubber, Contract Management and Work Listing Software.Interpret billing, coding and payment regulations, third party contracts." Qualifications: Required Qualifications list: Bachelor of Science in Accounting or Finance, Health Information Management, Health Administration, Computer Science or related field. Proficiency in MS Office Suite including; Excel, Word, Access, Visio, PowerPoint. Excellent written and verbal communication skills. Preferred Qualifications: Masters Degree or Professional Licensure. Experience in an Acute Care Hospital/Health System Revenue Cycle, Accounting, Finance, Information Technology or Decision Support role. Experience with inpatient and outpatient billing requirements (UB-04) and CMS Medicare and New York Medicaid reimbursement methodologies. Knowledge of third party payer reimbursement methodologies and contracts. Knowledge of CPT, HCPCs and ICD-10 coding principles. Knowledge of Invision Patient Accounting, RPM, Contract Management and/or Claims Scrubber Software. Knowledge of SQL or Database Queries. Experience reporting from healthcare decision support, patient accounting, contract management and/or claims scrubber systems. Proficiency with SAP Business Objects, Crystal Reports. Proficiency with visualization software (Tableau, MS Power BI, etc.). Please Note: Verification of degree (e.g., diploma or official transcript) is required for this role. Upload of documentation must be included with your application for consideration. Special Notes: Resume/CV should be included with the online application. Posting Overview: details about posting duration, review dates, etc. This is metadata; we can maybe put in a short paragraph under a heading like "Posting Details" but instructions say only include sections when posting has real, specific content for it. The posting overview is substantive but not exactly a standard heading. Could be placed under a generic "About the role" or maybe "Additional Information". However we have limited headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About the role = Position Summary. Responsibilities = Duties. Requirements = maybe Required Qualifications? Or we could separate Requirements (maybe required qualifications) and Qualifications (preferred). But they said use headings for those categories. We'll include both Required and Preferred under Qualifications? Could split: Requirements = Required Qualifications, Qualifications = Preferred Qualifications. Skills could be extracted from both required and preferred (proficiency in MS Office, SQL, visualization software, etc). Benefits: there is a paragraph about benefits: "At Stony Brook University Hospital, your compensation extends beyond your paycheck. We offer comprehensive benefits including generous leave, health insurance, and participation in the state pension system that contribute significantly to your overall total rewards package." Also mention location pay, shift differentials? That's under Anticipated Pay Range section. Pay: Salary range $68,563 - $83,578 / year. Also mention location pay, shift differentials. Schedule: Full-time. We need to avoid boilerplate like EEO, diversity statement, etc. Also remove "Please Note: Verification of degree..." maybe that's part of qualifications but it's about application requirement; could be included under Qualifications as a note. We must not include application instructions like "Upload of documentation must be included with your application". That's application instruction; we should remove. Also "Special Notes: Resume/CV should be included with the online application." That's application instruction; remove. Also "Posting Overview: This position will remain posted until filled or for a maximum of 90 days..." That's metadata about posting; maybe we can keep as a short paragraph under About the role? But it's not about role. Could be omitted as it's not substantive about job? It's about posting timeline; maybe we can keep as a short note under a generic heading like "Posting Information" but not in allowed headings. Safer to omit because it's not about role responsibilities etc. However instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." The posting overview is substantive info about the job posting timeline. Should we keep? It's not about the role but it's still info. The allowed headings list does not include a heading for posting timeline, but we could embed it in a

  under About the role? Might be okay. But better to include a short paragraph under About the role? Might be odd. Alternatively we could create a section "Additional Information" but not allowed. The instruction says: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map all info into those sections. Thus: - About the role: Position Summary paragraph. - Responsibilities: Duties list (bullet points). - Requirements: Required Qualifications (maybe also include verification note? but that's more about application). We'll put required qualifications. - Qualifications: Preferred Qualifications list. - Skills: Could combine technical skills: MS Office Suite, SQL, visualization software, etc. But we already have those in qualifications. Might be redundant. Perhaps we can put skills separate: proficiency in MS Office, SQL, SAP Business Objects, Crystal Reports, Tableau/Power BI, etc. But we already listed them. Might be okay to have Skills section summarizing technical skills. - Benefits: paragraph about comprehensive benefits, generous leave, health insurance, state pension system, location pay, shift differentials. - Pay: Salary range $68,563 - $83,578 / year. Also mention location pay, shift differentials (but those already in benefits). Could mention that final offer based on experience. - Schedule: Full-time. We must not include boilerplate like EEO, diversity statement, etc. Also remove "Please Note: Verification of degree..." maybe that's part of qualifications but it's about application requirement; could be included under Requirements as a note. We must not include application instructions like "Upload of documentation must be included with your application". So we will omit that. We must not include "Special Notes: Resume/CV should be included with the online application." Omit. We must not include "Posting Overview" details; maybe we can incorporate into About the role as a sentence? But it's not about role. Safer to omit? But that would be losing substantive info. However the instruction says preserve ALL substantive information. The posting overview is substantive info about the posting. But we have no heading for it. Could we treat it as part of About the role? It's not about role but could be considered additional info. Might be acceptable to include a short paragraph under About the role after the summary. Let's do that: after the position summary, add a paragraph about posting timeline. Now ensure we don't repeat job title as heading. The job title is "Revenue Cycle Analyst". Not used as heading. Now produce HTML fragment. Structure:

  About the role

  Position Summary ...

  Posting Overview: This position will remain posted until filled or for a maximum of 90 days. An initial review of all applicants will occur two weeks from the posting date. Candidates are advised that for full consideration, applications must be received before the initial review date (which is within two weeks of the posting date). If within the initial review no candidate was selected to fill the position posted, additional applications will be considered for the posted position; however, the posting will close once a finalist is identified, and at minimal, two weeks after the initial posting date. Please note, that if no candidate were identified and hired within 90 days from initial posting, the posting would close for review, and possibly reposted at a later date.

  But note: The posting overview includes some filler like "Please note, that if no candidate were identified..." It's substantive. Now Responsibilities:

  Responsibilities

  • Analyze claims and remittance data and present findings to departmental leadership.
  • Complete variance and trend analyses via spreadsheets, databases and dashboards.
  • Create audit and reconciliation plans related to: charges, adjustments, expected reimbursement and denials; accelerated and unposted cash.
  • Document and validate business processes and business systems configuration, including: Patient Billing, Claims Scrubber, Contract Management and Work Listing Software.
  • Interpret billing, coding and payment regulations, third party contracts.
  Now Requirements (Required Qualifications):

  Requirements

  • Bachelor of Science in Accounting or Finance, Health Information Management, Health Administration, Computer Science or related field.
  • Proficiency in MS Office Suite including Excel, Word, Access, Visio, PowerPoint.
  • Excellent written and verbal communication skills.
  • Verification of degree (e.g., diploma or official transcript) is required for this role.
  Now Qualifications (Preferred Qualifications):

  Qualifications

  • Masters Degree or Professional Licensure.
  • Experience in an Acute Care Hospital/Health System Revenue Cycle, Accounting, Finance, Information Technology or Decision Support role.
  • Experience with inpatient and outpatient billing requirements (UB-04) and CMS Medicare and New York Medicaid reimbursement methodologies.
  • Knowledge of third party payer reimbursement methodologies and contracts.
  • Knowledge of CPT, HCPCs and ICD-10 coding principles.
  • Knowledge of Invision Patient Accounting, RPM, Contract Management and/or Claims Scrubber Software.
  • Knowledge of SQL or Database Queries.
  • Experience reporting from healthcare decision support, patient accounting, contract management and/or claims scrubber systems.
  • Proficiency with SAP Business Objects, Crystal Reports.
  • Proficiency with visualization software (Tableau, MS Power BI, etc.).
  Now Skills: Could list technical skills maybe summarizing: MS Office, SQL, SAP Business Objects, Crystal Reports, Tableau/Power BI, etc. But we already have those in Qualifications. To avoid duplication, maybe we can put Skills as a short list of key competencies: data analysis, process documentation, regulatory interpretation, etc. But we already have those in Responsibilities. Might be okay to have Skills section with a concise list: Data analysis, spreadsheet/database/dashboards, audit/reconciliation planning, process validation, regulatory interpretation, communication. However that duplicates responsibilities. Might be better to omit Skills section if no distinct