Jobs · Florida

Specialist I - Inpatient Clinical Documentation Integrity (ICDI)

Mayo Clinic · Jacksonville, FL · 1 mo ago
$78k–$117k/yrFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro: "Why Mayo Clinic Mayo Clinic is top-ranked..." This is about the organization, maybe "About the role"? Actually "Why Mayo Clinic" is about the organization, not role. Could be "About the role"? But we have no explicit "About the role" heading in source. However we can create a section "About the role" with that content? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says we should use those headings when appropriate. It doesn't say we must include all; only include when posting has real specific content for it. The intro about Mayo Clinic could be considered "About the role"? It's more about the organization. Might be better to put under "About the role" or maybe we skip it because it's not about role specifics. But we need to preserve ALL substantive information; we cannot drop that intro if it's substantive. The intro includes why Mayo Clinic is top-ranked, dedication to employees, benefits, continuing education. That's substantive about the employer. Could be placed under a section like "About Mayo Clinic" but not in allowed headings. However we could put it under "About the role" as a description of the organization and role context. The instruction says "e.g. About the role, Responsibilities...". It's not strict that we must use exactly those headings, but we should use those for section headings. Likely they expect us to use those headings where applicable. So we can create an "About the role" section containing the introductory paragraph about Mayo Clinic and its employee investment. Then Responsibilities: we have a big block starting with "Reviews inpatient and/or outpatient medical records..." etc. That's responsibilities. Qualifications: we have "Associate’s and 2 years of experience as an Inpatient Clinical Documentation Improvement Specialist (CDIS). Certifications (either Are Required) Certified Documentation Improvement Practitioner (CDIP) OR Certified Clinical Documentation Specialist (CCDS) certification". Also maybe "Exemption Status Exempt" and "Compensation Detail" etc. But those are separate sections: Pay, Schedule, Benefits. Skills: maybe we have skills listed in responsibilities (analytical thinking, problem-solving, communication, self-motivated, etc.) Could be placed under Skills. Benefits: we have "Benefits Highlights Medical: Multiple plan options.Dental: Delta Dental or reimbursement account for flexible coverage.Vision: Affordable plan with national network.Pre-Tax Savings: HSA and FSAs for eligible expenses.Retirement: Competitive retirement package to secure your future." Pay: "Compensation Detail $78,270.40 - $117,312.00 / year" Schedule: "Exemption Status Exempt" maybe not schedule. Actually schedule details: "Schedule Full Time Hours/Pay Period 80 Schedule Details Monday - Friday, Business hours. This is a hybrid position and must be located within 100 miles of ANY Mayo Clinic campus for onsite expectations as business needs dictate. Weekend Schedule Not applicable International Assignment No". So schedule info. Also there is "During the selection process you may participate in an OnDemand (pre-recorded) interview..." That's application instructions; we must remove application instructions. So drop that. Also "This vacancy is not eligible for sponsorship/ we will not sponsor or transfer visas for this position. Also, Mayo Clinic DOES NOT participate in the F-1 STEM OPT extension program." That's also maybe not needed? It's about sponsorship; could be considered metadata but not boilerplate? It's about eligibility. Might be considered part of qualifications? But it's not a requirement; it's a note. Could be dropped as it's not substantive to role? Might be considered relevant but it's about visa sponsorship. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Sponsorship note is not exactly those categories, but could be considered legal? Might be okay to keep? However it's not about role duties. I'd consider it as metadata that could be dropped? The instruction says preserve ALL substantive information; does sponsorship count as substantive? It's about eligibility; could be important for applicants. But it's not a requirement like qualifications. Might be considered part of "Qualifications" or "Requirements". However it's not a qualification; it's a restriction. I'd keep it maybe under a short note? But we don't have a heading for that. Could fold into a paragraph under "Qualifications" or "Requirements". But the instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Sponsorship note is minor metadata; we could fold into a short p under Qualifications or maybe under a generic paragraph. But we have no generic section besides headings. Could add a

after Qualifications before Benefits? But that would be outside headings; still okay as long as we follow heading usage for sections. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose." So we can have paragraphs outside headings as prose. So we can include a short paragraph for sponsorship note. But we also have "Equal Opportunity..." etc which is boilerplate; must remove. Also "Recruiter Lynnette Fleshman" maybe minor metadata; could be dropped or folded into a short p. Probably drop as it's not substantive. Now we need to decide which sections to include. We have content for: - About the role (intro about Mayo Clinic) - Responsibilities (list) - Qualifications (education/experience, certifications) - Skills (maybe derived from responsibilities: analytical thinking, problem-solving, communication, self-motivated, teamwork, etc.) - Benefits (list) - Pay (salary range) - Schedule (full-time, hybrid, location, etc.) We might not need a separate "Requirements" section if qualifications cover it. But we could have both Requirements and Qualifications; but we should avoid thin sections. The posting has qualifications; we could treat that as Qualifications. Requirements maybe not separate. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual specifics. Now format:

    About the role

    Why Mayo Clinic is top-ranked in more specialties than any other care provider according to U.S. News & World Report. As we work together to put the needs of the patient first, we are also dedicated to our employees, investing in competitive compensation and comprehensive benefit plans – to take care of you and your family, now and in the future. And with continuing education and advancement opportunities at every turn, you can build a long, successful career with Mayo Clinic.

    Then Responsibilities: we need to convert the block into
    • items. The block includes many sentences; we can split each sentence as a list item. Let's extract responsibilities sentences: - Reviews inpatient and/or outpatient medical records to ensure accurate representation of severity of illness. - Validates that clinical documentation supports medical necessity of services and accurate coding. - Ensures documentation reflects patient’s clinical status, risk of mortality, and care complexity. - Applies advanced knowledge of disease processes, pathophysiology, medications, and critical thinking to identify and remedy documentation gaps. - Identifies opportunities for improvement in concurrent and retrospective documentation. - Ensures compliance with regulatory standards related to documentation, coding, and billing. - Collaborates with physicians, coders, case managers, nurses, and other staff to improve documentation quality. - Acts as an educator and resource to clinical staff, promoting best practices in documentation. - Acts as a change agent for improved documentation and enhanced documentation practices. - May perform ICDI DRG Secondary Reviews as well as support audit related activities. - Maintains compliance with ethical, legal, and coding standards. - Demonstrates strong analytical thinking and problem-solving skills. - Communicates effectively, both verbally and in writing, with physicians, leadership, and interdisciplinary teams. - Self-motivated with the ability to work independently and without close supervision. - Works collaboratively in a dynamic, team-oriented environment. - Must be able to work flexible hours, including evenings and weekends, as needed to meet business demands. Note: The last about flexible hours could also go under Schedule, but it's a responsibility. We'll keep it there. Now Qualifications: we have: - Associate’s degree and 2 years of experience as an Inpatient Clinical Documentation Improvement Specialist (CDIS). - Certification: Either Certified Documentation Improvement Practitioner (CDIP) OR Certified Clinical Documentation Specialist (CCDS) required. Also maybe "Exemption Status Exempt" is not a qualification; it's about FLSA status. Could be placed under Schedule or separate? Probably not needed. We could also include "Must be located within 100 miles of ANY Mayo Clinic campus for onsite expectations as business needs dictate." That's location requirement; could be under Schedule or Requirements. We'll put under Schedule. Now Skills: we can extract from responsibilities: analytical thinking, problem-solving, communication (verbal/written), self-motivated, ability to work independently, collaborative, team-oriented, educator, change agent, critical thinking, etc. But we might just list a few. Better to create a Skills section with bullet list: - Advanced knowledge of disease processes, pathophysiology, medications - Critical thinking - Analytical thinking and problem-solving - Effective verbal and written communication - Self-motivated, able to work independently - Collaborative and team-oriented - Educator and resource for clinical staff - Change agent for documentation improvement Now Benefits: we have bullet list: - Medical: Multiple plan options. - Dental: Delta Dental or reimbursement account for flexible coverage. - Vision: Affordable plan with national network. - Pre-Tax Savings: HSA and FSAs for eligible expenses. - Retirement: Competitive retirement package to secure your future. We could also mention continuing education and advancement opportunities but that's in intro. Now Pay: we have salary range: $78,270.40 - $117,312.00 per year. Now Schedule: we have: - Full-time (80 hours per pay period) - Monday - Friday, Business hours - Hybrid position; must be located within 100 miles of any Mayo Clinic campus for onsite expectations as business needs dictate. - Weekend schedule: Not applicable - International Assignment: No - Exemption Status: Exempt (maybe include) We could also note flexible hours including evenings and weekends as needed (but that's in responsibilities). We'll keep schedule as above. Now we need to ensure we don't include any boilerplate like EEO, E-Verify, etc. Also we need to drop the OnDemand interview instructions and sponsorship note. The sponsorship note maybe we could keep as a short p under Qualifications? But it's not a qualification. Might be considered metadata; we could drop it as it's not essential to role? The instruction says preserve ALL substantive information; sponsorship eligibility is substantive for some applicants. However it's not about the role itself; it's about employment eligibility. Could be considered minor metadata and we could fold into a short p. But we have no generic section; we could add a

      after Qualifications before Benefits. That would be okay as prose. But the instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." Sponsorship note is minor metadata; we can fold into a short p. Thus after Qualifications we can add a

      with sponsorship note: "This position is not eligible for sponsorship; Mayo

Similar jobs