Practice Operations Analyst
OSF HealthCare · Pontiac, IL · 1 mo ago
Management$25.1–$29.54/hrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
Let's parse the posting.
Content:
- "Total Rewards OSF HealthCare is dedicated to provide Mission Partners with a comprehensive and market-competitive total rewards package that includes benefits, compensation, recognition and well-being offerings that focus on the whole person and engage with their current stage of life and career. Click here to learn more about benefits and the total rewards at OSF." This is about benefits/total rewards. Could be Benefits section.
- "Expected pay for this position is $25.10 - $29.54/hour. Actual pay will be determined by experience, skills and internal equity. This is a Salaried position." This is Pay.
- "Overview Please note. This position is not eligible for H1B Sponsorship**" This is maybe a note but not a section.
- "Position Summary: The Practice Operations Analyst serves as a subject matter expert on operational and quality key metrics. The Analyst designs and analyzes reports for operational effectiveness, translates data into actionable information that assists leadership with decision making which helps OSF improve its healthcare delivery system. Uses analytical tools and problem solving, relationship building, and will at times present to various leadership groups. This position requires travel to all sites within the region as needed." This is responsibilities/overview.
- "Qualifications REQUIRED QUALIFICATIONS: Education: Associate’s Degree OR High School Diploma/ GED and 3 years’ experience in healthcare related field. Experience: Work experience retrieving and deciphering data. Other Skills/ Knowledge: Excellent interpersonal and communication skills.Solid computer skills, including proficiency with Microsoft software.Strong analytical and problem-solving skills, with the ability to be detail oriented."
- "Experience: PREFERRED QUALIFICATIONS: Proficient in Electronic Medical Records Advanced Excel skills."
- "OSF HealthCare is an Equal Opportunity Employer." That's boilerplate to remove.
Also there is "Click here to learn more about benefits and the total rewards at OSF." That's a link but we can keep as prose? It's part of benefits description.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO line.
We need to include sections only when posting has real specific content.
Potential sections:
- About the role (maybe Position Summary). Could be "About the role" heading.
- Responsibilities (maybe from Position Summary includes duties). Could be responsibilities.
- Requirements (maybe required qualifications). Could be Requirements.
- Qualifications (maybe preferred qualifications). Could be Qualifications.
- Skills (maybe other skills/knowledge). Could be Skills.
- Benefits (total rewards description). Could be Benefits.
- Pay (expected pay). Could be Pay.
- Schedule: Not mentioned. No schedule info. So omit.
We must not repeat job title as heading. Not needed.
We must not put Job ID/requisition numbers as headings.
We need to use for section headings.
Use
for section headings.
Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide what to list as lists.
We have duties: "designs and analyzes reports for operational effectiveness, translates data into actionable information that assists leadership with decision making which helps OSF improve its healthcare delivery system. Uses analytical tools and problem solving, relationship building, and will at times present to various leadership groups. This position requires travel to all sites within the region as needed."
We could make a list of duties: maybe bullet points: design and analyze reports; translate data into actionable information; use analytical tools and problem solving; relationship building; present to leadership groups; travel to sites as needed.
But we need to preserve all substantive information; we can convert to list but must not lose info. It's okay to rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we can't lose detail, but we can rephrase as long as we keep the meaning. Safer to keep as prose? But rule: Use
- for any list of duties/requirements/benefits. If we have duties, we should make a list. However we must not lose detail. We can break into items that capture each duty.
Let's extract duties:
- Serves as a subject matter expert on operational and quality key metrics.
- Designs and analyzes reports for operational effectiveness.
- Translates data into actionable information that assists leadership with decision making.
- Helps OSF improve its healthcare delivery system.
- Uses analytical tools and problem solving.
- Relationship building.
- Presents to various leadership groups (at times).
- Travels to all sites within the region as needed.
That seems to capture.
Now qualifications: Required qualifications: Education: Associate’s Degree OR High School Diploma/ GED and 3 years’ experience in healthcare related field. Experience: Work experience retrieving and deciphering data. Other Skills/ Knowledge: Excellent interpersonal and communication skills. Solid computer skills, including proficiency with Microsoft software. Strong analytical and problem-solving skills, with the ability to be detail oriented.
We could list required qualifications as bullet points.
Preferred qualifications: Proficient in Electronic Medical Records. Advanced Excel skills.
Skills: maybe combine other skills? But we already have skills in required qualifications. Could have a Skills section for "Excellent interpersonal and communication skills; Solid computer skills, including proficiency with Microsoft software; Strong analytical and problem-solving skills, with the ability to be detail oriented." But that duplicates. Better to have Requirements (education/experience) and Skills (other skills). However the instruction: Use headings for sections like Requirements, Qualifications, Skills. We can decide.
We have "Qualifications REQUIRED QUALIFICATIONS:" and then "Experience: PREFERRED QUALIFICATIONS:" So we could have a Qualifications section with required and preferred subpoints? But we need to follow headings: Requirements, Qualifications, Skills. Might be overlapping.
Simplify: Use:
- About the role (Position Summary) as prose.
- Responsibilities (duties) as list.
- Requirements (required qualifications) as list.
- Skills (other skills/knowledge) as list.
- Benefits (total rewards) as prose.
- Pay (expected pay) as prose.
We could also have a Qualifications section for preferred qualifications, but maybe we can incorporate preferred into Skills or Requirements? The instruction: "Prefer a few substantive sections over many thin ones." So we might combine required and preferred into Qualifications section? But we have separate headings: Requirements, Qualifications, Skills. Could treat Requirements as education/experience, Qualifications as preferred qualifications, Skills as other skills.
Let's do that.
Now Benefits: The total rewards paragraph: "Total Rewards OSF HealthCare is dedicated to provide Mission Partners with a comprehensive and market-competitive total rewards package that includes benefits, compensation, recognition and well-being offerings that focus on the whole person and engage with their current stage of life and career. Click here to learn more about benefits and the total rewards at OSF."
We need to keep that as prose. Remove the "Click here to learn more..." maybe it's okay as part of prose.
Pay: "Expected pay for this position is $25.10 - $29.54/hour. Actual pay will be determined by experience, skills and internal equity. This is a Salaried position."
We keep as prose.
Now we need to output only HTML fragment, no html/body tags, no markdown fences.
Let's construct.
About the role
The Practice Operations Analyst serves as a subject matter expert on operational and quality key metrics. The Analyst designs and analyzes reports for operational effectiveness, translates data into actionable information that assists leadership with decision making which helps OSF improve its healthcare delivery system. Uses analytical tools and problem solving, relationship building, and will at times present to various leadership groups. This position requires travel to all sites within the region as needed.
But we decided to make responsibilities list. Actually we could keep About the role as prose summary, and Responsibilities as list.
Let's do:
About the role
The Practice Operations Analyst serves as a subject matter expert on operational and quality key metrics.
Then Responsibilities list.
But we need to preserve all substantive information; splitting may lose some nuance but we keep all details across sections.
Let's extract About the role: maybe just first sentence? But we could keep the whole position summary as About the role.
Better: About the role = Position Summary (full). Then Responsibilities could be a more detailed list of duties derived from that summary. However that would duplicate info. The instruction says preserve all substantive information; duplication is okay? It didn't forbid duplication but we should avoid unnecessary duplication. Better to not duplicate. So we could have either About the role (prose) or Responsibilities (list) but not both with same content.
We could treat About the role as brief overview, and Responsibilities as detailed list. That adds detail not present elsewhere. Let's craft About the role as a short overview: "The Practice Operations Analyst serves as a subject matter expert on operational and quality key metrics, designing and analyzing reports to support leadership decision-making and healthcare delivery improvements." That's a summary but may lose some detail like relationship building, presenting, travel. Those we can put in Responsibilities list.
Thus we keep all info across sections.
Now Responsibilities list items:
- Designs and analyzes reports for operational effectiveness.
- Translates data into actionable information that assists leadership with decision making.
- Helps OSF improve its healthcare delivery system.
- Uses analytical tools and problem solving.
- Builds relationships.
- Presents to various leadership groups as needed.
- Travels to all sites within the region as required.
Now Requirements (required qualifications) list:
- Education: Associate’s Degree OR High School Diploma/GED and 3 years’ experience in a healthcare-related field.
- Experience: Work experience retrieving and deciphering data.
Now Skills list (other skills/knowledge):
- Excellent interpersonal and communication skills.
- Solid computer skills, including proficiency with Microsoft software.
- Strong analytical and problem-solving skills, with the ability to be detail oriented.
Now Qualifications (preferred qualifications) list:
- Proficient in Electronic Medical Records.
- Advanced Excel skills.
Now Benefits paragraph:
Total Rewards OSF HealthCare is dedicated to provide Mission Partners with a comprehensive and market-competitive total rewards package that includes benefits, compensation, recognition and well-being offerings that focus on the whole person and engage with their current stage of life and career. Click here to learn more about benefits and the total rewards at OSF.
Now Pay paragraph:
Expected pay for this position is $25.10 - $29.54/hour. Actual pay will be determined by experience, skills and internal equity. This is a Salaried position.
We should not include Schedule section.
Now ensure we removed boilerplate: EEO line removed. Also removed "Overview Please note. This position is not eligible for H1B Sponsorship**" maybe that's not boilerplate but it's a note about sponsorship. It's substantive? It says not eligible for H1B Sponsorship. That's relevant info. Should we keep? It's not a standard heading but could be included in About the role or a note. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is about H1B sponsorship, not exactly boilerplate but could be considered legal? It's a specific condition. I'd keep it maybe as a note in About the role or as a separate paragraph. Since we have no section for "Work Authorization" etc. Could add a short paragraph under About the role or after. But we must not create a heading unless there is real specific content. We could add a paragraph after About the role: "This position is not eligible for H1B Sponsorship.
" That preserves info.
Let's incorporate that.
Now check for any duplicated lines: we have not duplicated.
Now output HTML fragment.
Make sure to use proper heading tags.
Let's craft final HTML:
About
for prose. We need to decide what to list as lists. We have duties: "designs and analyzes reports for operational effectiveness, translates data into actionable information that assists leadership with decision making which helps OSF improve its healthcare delivery system. Uses analytical tools and problem solving, relationship building, and will at times present to various leadership groups. This position requires travel to all sites within the region as needed." We could make a list of duties: maybe bullet points: design and analyze reports; translate data into actionable information; use analytical tools and problem solving; relationship building; present to leadership groups; travel to sites as needed. But we need to preserve all substantive information; we can convert to list but must not lose info. It's okay to rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we can't lose detail, but we can rephrase as long as we keep the meaning. Safer to keep as prose? But rule: Use
- for any list of duties/requirements/benefits. If we have duties, we should make a list. However we must not lose detail. We can break into items that capture each duty.
Let's extract duties:
- Serves as a subject matter expert on operational and quality key metrics.
- Designs and analyzes reports for operational effectiveness.
- Translates data into actionable information that assists leadership with decision making.
- Helps OSF improve its healthcare delivery system.
- Uses analytical tools and problem solving.
- Relationship building.
- Presents to various leadership groups (at times).
- Travels to all sites within the region as needed.
That seems to capture.
Now qualifications: Required qualifications: Education: Associate’s Degree OR High School Diploma/ GED and 3 years’ experience in healthcare related field. Experience: Work experience retrieving and deciphering data. Other Skills/ Knowledge: Excellent interpersonal and communication skills. Solid computer skills, including proficiency with Microsoft software. Strong analytical and problem-solving skills, with the ability to be detail oriented.
We could list required qualifications as bullet points.
Preferred qualifications: Proficient in Electronic Medical Records. Advanced Excel skills.
Skills: maybe combine other skills? But we already have skills in required qualifications. Could have a Skills section for "Excellent interpersonal and communication skills; Solid computer skills, including proficiency with Microsoft software; Strong analytical and problem-solving skills, with the ability to be detail oriented." But that duplicates. Better to have Requirements (education/experience) and Skills (other skills). However the instruction: Use headings for sections like Requirements, Qualifications, Skills. We can decide.
We have "Qualifications REQUIRED QUALIFICATIONS:" and then "Experience: PREFERRED QUALIFICATIONS:" So we could have a Qualifications section with required and preferred subpoints? But we need to follow headings: Requirements, Qualifications, Skills. Might be overlapping.
Simplify: Use:
- About the role (Position Summary) as prose.
- Responsibilities (duties) as list.
- Requirements (required qualifications) as list.
- Skills (other skills/knowledge) as list.
- Benefits (total rewards) as prose.
- Pay (expected pay) as prose.
We could also have a Qualifications section for preferred qualifications, but maybe we can incorporate preferred into Skills or Requirements? The instruction: "Prefer a few substantive sections over many thin ones." So we might combine required and preferred into Qualifications section? But we have separate headings: Requirements, Qualifications, Skills. Could treat Requirements as education/experience, Qualifications as preferred qualifications, Skills as other skills.
Let's do that.
Now Benefits: The total rewards paragraph: "Total Rewards OSF HealthCare is dedicated to provide Mission Partners with a comprehensive and market-competitive total rewards package that includes benefits, compensation, recognition and well-being offerings that focus on the whole person and engage with their current stage of life and career. Click here to learn more about benefits and the total rewards at OSF."
We need to keep that as prose. Remove the "Click here to learn more..." maybe it's okay as part of prose.
Pay: "Expected pay for this position is $25.10 - $29.54/hour. Actual pay will be determined by experience, skills and internal equity. This is a Salaried position."
We keep as prose.
Now we need to output only HTML fragment, no html/body tags, no markdown fences.
Let's construct.
About the role
The Practice Operations Analyst serves as a subject matter expert on operational and quality key metrics. The Analyst designs and analyzes reports for operational effectiveness, translates data into actionable information that assists leadership with decision making which helps OSF improve its healthcare delivery system. Uses analytical tools and problem solving, relationship building, and will at times present to various leadership groups. This position requires travel to all sites within the region as needed.
But we decided to make responsibilities list. Actually we could keep About the role as prose summary, and Responsibilities as list. Let's do:About the role
The Practice Operations Analyst serves as a subject matter expert on operational and quality key metrics.
Then Responsibilities list. But we need to preserve all substantive information; splitting may lose some nuance but we keep all details across sections. Let's extract About the role: maybe just first sentence? But we could keep the whole position summary as About the role. Better: About the role = Position Summary (full). Then Responsibilities could be a more detailed list of duties derived from that summary. However that would duplicate info. The instruction says preserve all substantive information; duplication is okay? It didn't forbid duplication but we should avoid unnecessary duplication. Better to not duplicate. So we could have either About the role (prose) or Responsibilities (list) but not both with same content. We could treat About the role as brief overview, and Responsibilities as detailed list. That adds detail not present elsewhere. Let's craft About the role as a short overview: "The Practice Operations Analyst serves as a subject matter expert on operational and quality key metrics, designing and analyzing reports to support leadership decision-making and healthcare delivery improvements." That's a summary but may lose some detail like relationship building, presenting, travel. Those we can put in Responsibilities list. Thus we keep all info across sections. Now Responsibilities list items: - Designs and analyzes reports for operational effectiveness. - Translates data into actionable information that assists leadership with decision making. - Helps OSF improve its healthcare delivery system. - Uses analytical tools and problem solving. - Builds relationships. - Presents to various leadership groups as needed. - Travels to all sites within the region as required. Now Requirements (required qualifications) list: - Education: Associate’s Degree OR High School Diploma/GED and 3 years’ experience in a healthcare-related field. - Experience: Work experience retrieving and deciphering data. Now Skills list (other skills/knowledge): - Excellent interpersonal and communication skills. - Solid computer skills, including proficiency with Microsoft software. - Strong analytical and problem-solving skills, with the ability to be detail oriented. Now Qualifications (preferred qualifications) list: - Proficient in Electronic Medical Records. - Advanced Excel skills. Now Benefits paragraph:Total Rewards OSF HealthCare is dedicated to provide Mission Partners with a comprehensive and market-competitive total rewards package that includes benefits, compensation, recognition and well-being offerings that focus on the whole person and engage with their current stage of life and career. Click here to learn more about benefits and the total rewards at OSF.
Now Pay paragraph:Expected pay for this position is $25.10 - $29.54/hour. Actual pay will be determined by experience, skills and internal equity. This is a Salaried position.
We should not include Schedule section. Now ensure we removed boilerplate: EEO line removed. Also removed "Overview Please note. This position is not eligible for H1B Sponsorship**" maybe that's not boilerplate but it's a note about sponsorship. It's substantive? It says not eligible for H1B Sponsorship. That's relevant info. Should we keep? It's not a standard heading but could be included in About the role or a note. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is about H1B sponsorship, not exactly boilerplate but could be considered legal? It's a specific condition. I'd keep it maybe as a note in About the role or as a separate paragraph. Since we have no section for "Work Authorization" etc. Could add a short paragraph under About the role or after. But we must not create a heading unless there is real specific content. We could add a paragraph after About the role: "This position is not eligible for H1B Sponsorship.
" That preserves info. Let's incorporate that. Now check for any duplicated lines: we have not duplicated. Now output HTML fragment. Make sure to use proper heading tags. Let's craft final HTML:About