Clinical Patient Navigator
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also we must not include Pay/Schedule/Benefits unless posting actually states them. The posting includes "The hourly rate for this position generally ranges between $19.02-$23.34 Per Hour". That's pay info, so we can include Pay section. Benefits? Not mentioned. Schedule? Not mentioned. So we should not include Benefits or Schedule sections. Also we need sections: About the role (maybe description of company and role), Responsibilities (essential functions), Requirements (education, experience, credentials), Qualifications (maybe knowledge, skills, abilities?), Skills (maybe required knowledge, skills and abilities). The instructions: Use headings for those categories. We need to decide what content goes where. The posting includes sections: "Think you are a great fit? Learn more about this role here:" then description of Healogics, then role description. Then "Essential Functions/Responsibilities" with Administrative Functions and Clinical Functions. Then "Required Education, Experience And Credentials". Then "Required Knowledge, Skills And Abilities". Then "Physical Demands". Then "Work Environment". Then pay info. Then internal application instruction (which we should remove). Also there is mention of "All Healogics employees must perform their job responsibilities according to all Healogics policies..." that's generic; we can keep as part of responsibilities maybe.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections, but we can format as lists or paragraphs.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the line about internal candidate applying via Workday.
Also remove duplicated lines? Not seeing duplicates.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
Healogics is the largest provider of advanced wound care services in the United States, treating more than 300,000 chronic wound patients annually across over 600 sites. With an aging society, obesity and diabetes on the rise, and an uptick in surgical procedures, the number of patients with non-healing wounds that would benefit from expert care is dramatically increasing. As a result, the company is working to provide our differentiated, quality outcomes to as many patients that would benefit through our out-patient clinic partnerships. The Clinical Patient Navigator manages a variety of front office functions and is key to smooth operation of a dynamic outpatient wound care center as well as performs general office duties to assist the staff of the WCC. This individual serves in a dual administrative/clinical role to streamline workflow in providing effective and exceptional patient care. All Healogics employees must perform their job responsibilities according to all Healogics policies, Hospital policies, as well as to accrediting organizations, federal and state regulation, and to the Centers for Medicare and Medicaid Services (CMS) guidelines, as applicable.
Responsibilities
- Coordinates with Center leadership to maximize daily patient census.
- Actively participates in staff meetings to support key functions within the Center.
- Greets patients and other visitors, answers and routes calls to appropriate staff.
- Maintains all patient communication needs including scheduling, rescheduling, and appointment reminders.
- Works and schedules for provider, according to the care continuum model.
- Obtains and verifies patient insurance information, to include pre-certifications and pre-authorizations for services and enters data in appropriate databases.
- Collects and enters patient charges in databases.
- Verifies and reconciles charges as directed, prepares monthly patient survey data and appropriate documentation, then transmits to providers.
- Assembles new patient charts, maintains and files existing patient charts, and spot checks charts for data completeness and signatures.
- Coordinates/schedules ancillary testing with other hospital departments.
- Arranges for patient transportation, as needed.
- Maintains office equipment and supplies as needed, and medical supplies as directed.
- Under the direction of the RN/Provider, provides wound-related patient care as approved by hospital protocols, Policies & Procedures and scope of practice and with documented competencies where necessary.
- May assist with intake and discharge within scope of practice and according to hospital bylaws and completion of appropriate skills competencies.
- May perform hyperbaric oxygen therapy related duties, as needed, after completing the required Healogics hyperbaric training and completion of required skills competency.
- May assist in Vein Clinic within scope of practice after Healogics Vein Clinic training completed (if applicable).
- Gathers patient information.
- Gathers necessary equipment and supplies for the RN or provider.
- Reports quality of care issues to Clinical Nurse Manager.
- Communicates as needed with all team members regarding therapeutic interventions to ensure quality of care.
- May function as a Documentation Assistant (scribe) in accordance with Healogics policy.
- Performs other duties as required.
Requirements
- High School Diploma or General Education Development (GED); Associate’s degree preferred.
- Graduate from a Certified Medical Assistant (CMA), Emergency Medical Technician (EMT) or Certified Nursing Assistant (CNA) program approved by the Commission on Accreditation of Allied Health Program (CAAHEP) or by the Accrediting Bureau of Health Education Schools (ABHES).
- Current CMA, CNA or EMT Certification licensed in the state of employment – to be maintained throughout the duration of employment in the position.
- Minimum of Two (2) or more years office administration experience is required; Preferably in a medical setting, acute hospital, rehabilitation hospital, or skilled nursing unit.
- Prior medical coding experience preferred.
Qualifications
Maybe we can combine Knowledge, Skills and Abilities into Qualifications? But we also have Skills heading. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need both Qualifications and Skills sections if content exists. The posting has "Required Knowledge, Skills And Abilities". That could be split into Qualifications (maybe education/credentials) and Skills (knowledge, skills, abilities). But we already used Requirements for education/experience/credentials. So Qualifications could be something like "Demonstrated competency in BLS (Basic Life Support)" etc. But we need to decide what goes where. The posting includes "Required Knowledge, Skills And Abilities" list: Demonstrated competency in BLS, Proficient in Microsoft Office, Good customer, interpersonal and communication skills, both orally and in writing, Organization and time-management skills, Basic math skills, Attention to details, Ability to maintain confidentiality, Ability to work in fast paced environment and to work on multiple projects at the same time, Ability to work with others and in a team environment. Those are skills/abilities. So we could put those under Skills heading. Then Qualifications could be maybe something else? The posting didn't have a separate qualifications beyond education/experience. But we could treat "Required Education, Experience And Credentials" as Requirements, and "Required Knowledge, Skills And Abilities" as Skills. Then Qualifications could be omitted if no specific content. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine Qualifications and Skills if needed, but we must use headings only when posting has real specific content. If we don't have distinct qualifications beyond requirements, we could omit Qualifications heading. But we need to decide. The list of possible headings includes Qualifications; we can include it if there is content. The posting does not have a separate "Qualifications" section besides the education/experience. However sometimes "Qualifications" could encompass both education/experience and knowledge/skills. But we already used Requirements for education/experience. So maybe we put knowledge/skills under Qualifications, and Skills under something else? But the heading list includes both Qualifications and Skills; we need to decide which to use. Better to follow typical job posting structure: Requirements (education/experience), Qualifications (knowledge/skills/abilities), Skills (maybe technical skills). But the posting's "Required Knowledge, Skills And Abilities" seems to cover both knowledge and skills. So we could put that under Qualifications. Then we could have Skills heading for maybe technical skills like Microsoft Office? But that's already in the list. Could split: Qualifications: BLS competency, etc. Skills: Microsoft Office proficiency, communication skills, etc. But that seems arbitrary. Given instruction to prefer few substantive sections, we could combine knowledge, skills, abilities into a single section, maybe under Skills heading (since it's more about skills). Then we could omit Qualifications heading. However the instruction says to use headings for those sections if posting has real specific content. It does not require us to use all headings. So we can omit Qualifications if no distinct content. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Pay. We must not include Benefits or Schedule. Now we need to include Pay section with the hourly rate info. Pay section:
Pay
The hourly rate for this position generally ranges between $19.02-$23.34 Per Hour. This range is an estimate, based on potential employee qualifications: education, experience, geography as well as operational needs and other considerations permitted by law.
We should not include the internal application instruction. Now we need to ensure we didn't include any boilerplate like "All Healogics employees must perform their job responsibilities according to all Healogics policies..." we kept that in About the role. That's okay. Check for duplicated lines: none. Now output HTML fragment. Make sure to use- for lists. For prose use
. We need to ensure we didn't miss any substantive info: Physical Demands and Work Environment sections are present in posting. Should we include them? They are substantive. The instruction: include a section ONLY when the posting has real, specific content for it. Physical Demands and Work Environment are specific content. Should we create sections for them? The allowed headings list does not include Physical Demands or Work Environment. But we could still include them as
? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not an exhaustive list? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. It doesn't explicitly forbid other headings, but the examples indicate those are the expected sections. Safer to stick to those headings only. However we have substantive info about Physical Demands and Work Environment that doesn't fit those headings. Where could we put them? Could be part of Responsibilities or Requirements? Not really. Could be part of About the role? Not ideal. But we could include them under Responsibilities as additional bullet points? They are not responsibilities but job demands. Could we create a section "Physical Demands" using
even though not in list? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for