Application Analyst
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Keep substantive info.
Let's parse the posting:
- Opening: "Exciting Career Opportunity with Avance Care! Join our rapidly expanding network of 30+ practice locations in the Triangle Area (Raleigh-Durham-Chapel Hill), the Charlotte Region, and Wilmington, NC. Avance Care is dedicated to elevating the standard of healthcare. As one of North Carolina's largest networks of independent primary care practices, we offer comprehensive services to support the physical, mental, and emotional health of our patients."
That's about the organization; could be "About the role"? Actually "About the role" maybe includes description of role. The posting then says: "As our Application Analyst, you’ll be responsible for configuring, modifying, testing, and maintaining software applications. In addition to coordinating all issues that arise during the project for the application area. You’ll build collaborative relationships with project leadership, business owners, clinical department users, and other corporate departments to facilitate usage and acceptance of the system."
That's role description.
Then "Selected Responsibilities" list bullet points (though not bullet but sentences). We'll need to extract responsibilities as list items.
Then "Required On-Call after hours and on weekends at management’s discretion" and "Performs other duties as assigned" maybe part of responsibilities.
Then "Qualifications" heading: "The ideal candidate will possess an associate or bachelor’s degree in information technology (or a related field) and at least two years of EMR experience. Epic certification or accreditation is required in a primary application—such as EpicCare Ambulatory, Cadence, Prelude, Welcome, MyChart, or HealthPlanet/Compass Rose —with additional certifications highly preferred."
Then "If you are excited to join a growing organization focused on changing the way healthcare is delivered to patients in North Carolina, please submit your resume." That's application instruction; we should remove.
Then EEO boilerplate; remove.
No explicit Benefits, Pay, Schedule sections. There's mention of on-call after hours and weekends; that could be schedule info? It's about required on-call after hours and weekends at management's discretion. That's schedule detail. Could be placed under Schedule section? The instruction: include a section ONLY when posting has real, specific content for it. The on-call requirement is specific content about schedule. So we could create a Schedule section with that detail.
Benefits: none mentioned. Pay: none.
Skills: maybe we could infer from qualifications? But we should not invent. There's no explicit Skills section. Could we treat qualifications as Skills? The instruction: Use headings for sections like Skills if posting has real specific content. The posting includes qualifications (education, experience, certifications). That's more like Qualifications. So we will have Qualifications section.
We also have About the role? Could combine role description and responsibilities? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have:
- About the role: could include the introductory paragraph about the company and role description? The posting includes "Exciting Career Opportunity..." and description of Avance Care, plus role description. That could be About the role.
- Responsibilities: list of duties.
- Qualifications: education, experience, certification.
- Schedule: on-call after hours and weekends.
We might also have Requirements? The qualifications could be considered Requirements. But we have both Requirements and Qualifications headings as options. The posting has "Qualifications" heading. So we should use Qualifications. Not Requirements.
We should not create Skills unless there is explicit skills list. Not present.
Thus output sections: About the role, Responsibilities, Qualifications, Schedule.
We need to preserve all substantive information; do not invent or summarize away detail. Use - for any list of duties/requirements/benefits. For prose use
.
We need to extract responsibilities as list items. Let's list them:
From "Selected Responsibilities" paragraph (looks like a list but not bullet). Let's break each sentence:
- Act as the primary support contact for the Ambulatory application’s end-users
- Recognize issues that arise in their application area as well as issues that impact other application teams, and work to resolve them
- Guiding workflow design, building and testing the system, and analyzing other technical issues associated with EPIC software
- Identifying and implementing request changes to the system
- Serving as a liaison between end users’ workflow needs and EPIC implementation staff
- Maintaining regular communication with your EPIC representatives including participating in weekly project team meetings
- Working with Epic representatives, the organization’s business community, and end users to ensure the system meets the organization’s business needs regarding the project deliverables and timeline
- Develop an understanding of operational needs to set the direction for the organization’s workflows by attending site visit and other integrated sessions
- Participate in training and working with end users
- Holding weekly communications with team members to discuss the status of deliverables, shared issues, end-user concerns, budget, and upcoming milestones
- Adhering to service level agreements in incident and task management
- Attending and participating in workgroup and steering meetings
- Preparing agendas and performing system demonstrations for stakeholders
- Review and complete Epic NoVA notes and upgrades within the project timelines
- Maintain all applicable certification(s) and ensure CEE’s are up to date
- Translating operational requests into Epic build tasks
- Required On-Call after hours and on weekends at management’s discretion
- Performs other duties as assigned
We need to keep all. Some are gerund phrases; we can keep as is.
Now About the role: combine the introductory paragraph and role description.
Intro: "Exciting Career Opportunity with Avance Care! Join our rapidly expanding network of 30+ practice locations in the Triangle Area (Raleigh-Durham-Chapel Hill), the Charlotte Region, and Wilmington, NC. Avance Care is dedicated to elevating the standard of healthcare. As one of North Carolina's largest networks of independent primary care practices, we offer comprehensive services to support the physical, mental, and emotional health of our patients."
Then role description: "As our Application Analyst, you’ll be responsible for configuring, modifying, testing, and maintaining software applications. In addition to coordinating all issues that arise during the project for the application area. You’ll build collaborative relationships with project leadership, business owners, clinical department users, and other corporate departments to facilitate usage and acceptance of the system."
We'll put that in
maybe multiple paragraphs.
Qualifications: "The ideal candidate will possess an associate or bachelor’s degree in information technology (or a related field) and at least two years of EMR experience. Epic certification or accreditation is required in a primary application—such as EpicCare Ambulatory, Cadence, Prelude, Welcome, MyChart, or HealthPlanet/Compass Rose —with additional certifications highly preferred."
Schedule: "Required On-Call after hours and on weekends at management’s discretion." Actually that line appears also in responsibilities list; but we can still include as schedule detail. However we should not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we include it in Responsibilities list, we still need to keep it somewhere. It's okay to have it appear both in Responsibilities and Schedule? Might be duplication but we could keep it only in Schedule and remove from Responsibilities to avoid duplication. However the responsibilities list includes that line as a bullet; if we remove it, we lose that detail from responsibilities. But we could keep it in responsibilities and also have schedule section referencing it? That would duplicate. Better to keep it only in responsibilities and not create schedule section unless we have other schedule info. But we have schedule info only that line. If we put it in responsibilities, we still have the info. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having the same info appear in multiple sections, but we should avoid unnecessary duplication. However we need to decide: Should we create Schedule section? The posting mentions on-call after hours and weekends at management's discretion. That's schedule-related. Could be considered schedule. If we create Schedule section, we should move that line there and maybe remove from responsibilities to avoid duplication. But the responsibilities list includes many items; removing one might be okay as we still preserve the info elsewhere. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Moving it is fine as long as we keep it somewhere. So we can put it in Schedule section and remove from responsibilities list.
Thus responsibilities list will exclude the on-call line.
Now we need to ensure we don't include boilerplate like EEO, application instructions, etc.
Now produce HTML fragment:
About the role
Exciting Career Opportunity with Avance Care! Join our rapidly expanding network of 30+ practice locations in the Triangle Area (Raleigh-Durham-Chapel Hill), the Charlotte Region, and Wilmington, NC. Avance Care is dedicated to elevating the standard of healthcare. As one of North Carolina's largest networks of independent primary care practices, we offer comprehensive services to support the physical, mental, and emotional health of our patients.
As our Application Analyst, you’ll be responsible for configuring, modifying, testing, and maintaining software applications. In addition to coordinating all issues that arise during the project for the application area. You’ll build collaborative relationships with project leadership, business owners, clinical department users, and other corporate departments to facilitate usage and acceptance of the system.
Responsibilities
- Act as the primary support contact for the Ambulatory application’s end-users
- Recognize issues that arise in their application area as well as issues that impact other application teams, and work to resolve them
- Guiding workflow design, building and testing the system, and analyzing other technical issues associated with EPIC software
- Identifying and implementing request changes to the system
- Serving as a liaison between end users’ workflow needs and EPIC implementation staff
- Maintaining regular communication with your EPIC representatives including participating in weekly project team meetings
- Working with Epic representatives, the organization’s business community, and end users to ensure the system meets the organization’s business needs regarding the project deliverables and timeline
- Develop an understanding of operational needs to set the direction for the organization’s workflows by attending site visit and other integrated sessions
- Participate in training and working with end users
- Holding weekly communications with team members to discuss the status of deliverables, shared issues, end-user concerns, budget, and upcoming milestones
- Adhering to service level agreements in incident and task management
- Attending and participating in workgroup and steering meetings
- Preparing agendas and performing system demonstrations for stakeholders
- Review and complete Epic NoVA notes and upgrades within the project timelines
- Maintain all applicable certification(s) and ensure CEE’s are up to date
- Translating operational requests into Epic build tasks
- Performs other duties as assigned
Qualifications
The ideal candidate will possess an associate or bachelor’s degree in information technology (or a related field) and at least two years of EMR experience. Epic certification or accreditation is required in a primary application—such as EpicCare Ambulatory, Cadence, Prelude, Welcome, MyChart, or HealthPlanet/Compass Rose —with additional certifications highly preferred.
Schedule
Required On-Call after hours and on weekends at management’s discretion.
Check for any leftover boilerplate: none.
Make sure no
- for any list of duties/requirements/benefits. For prose use
. We need to extract responsibilities as list items. Let's list them: From "Selected Responsibilities" paragraph (looks like a list but not bullet). Let's break each sentence: - Act as the primary support contact for the Ambulatory application’s end-users - Recognize issues that arise in their application area as well as issues that impact other application teams, and work to resolve them - Guiding workflow design, building and testing the system, and analyzing other technical issues associated with EPIC software - Identifying and implementing request changes to the system - Serving as a liaison between end users’ workflow needs and EPIC implementation staff - Maintaining regular communication with your EPIC representatives including participating in weekly project team meetings - Working with Epic representatives, the organization’s business community, and end users to ensure the system meets the organization’s business needs regarding the project deliverables and timeline - Develop an understanding of operational needs to set the direction for the organization’s workflows by attending site visit and other integrated sessions - Participate in training and working with end users - Holding weekly communications with team members to discuss the status of deliverables, shared issues, end-user concerns, budget, and upcoming milestones - Adhering to service level agreements in incident and task management - Attending and participating in workgroup and steering meetings - Preparing agendas and performing system demonstrations for stakeholders - Review and complete Epic NoVA notes and upgrades within the project timelines - Maintain all applicable certification(s) and ensure CEE’s are up to date - Translating operational requests into Epic build tasks - Required On-Call after hours and on weekends at management’s discretion - Performs other duties as assigned We need to keep all. Some are gerund phrases; we can keep as is. Now About the role: combine the introductory paragraph and role description. Intro: "Exciting Career Opportunity with Avance Care! Join our rapidly expanding network of 30+ practice locations in the Triangle Area (Raleigh-Durham-Chapel Hill), the Charlotte Region, and Wilmington, NC. Avance Care is dedicated to elevating the standard of healthcare. As one of North Carolina's largest networks of independent primary care practices, we offer comprehensive services to support the physical, mental, and emotional health of our patients." Then role description: "As our Application Analyst, you’ll be responsible for configuring, modifying, testing, and maintaining software applications. In addition to coordinating all issues that arise during the project for the application area. You’ll build collaborative relationships with project leadership, business owners, clinical department users, and other corporate departments to facilitate usage and acceptance of the system." We'll put that in
maybe multiple paragraphs. Qualifications: "The ideal candidate will possess an associate or bachelor’s degree in information technology (or a related field) and at least two years of EMR experience. Epic certification or accreditation is required in a primary application—such as EpicCare Ambulatory, Cadence, Prelude, Welcome, MyChart, or HealthPlanet/Compass Rose —with additional certifications highly preferred." Schedule: "Required On-Call after hours and on weekends at management’s discretion." Actually that line appears also in responsibilities list; but we can still include as schedule detail. However we should not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we include it in Responsibilities list, we still need to keep it somewhere. It's okay to have it appear both in Responsibilities and Schedule? Might be duplication but we could keep it only in Schedule and remove from Responsibilities to avoid duplication. However the responsibilities list includes that line as a bullet; if we remove it, we lose that detail from responsibilities. But we could keep it in responsibilities and also have schedule section referencing it? That would duplicate. Better to keep it only in responsibilities and not create schedule section unless we have other schedule info. But we have schedule info only that line. If we put it in responsibilities, we still have the info. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having the same info appear in multiple sections, but we should avoid unnecessary duplication. However we need to decide: Should we create Schedule section? The posting mentions on-call after hours and weekends at management's discretion. That's schedule-related. Could be considered schedule. If we create Schedule section, we should move that line there and maybe remove from responsibilities to avoid duplication. But the responsibilities list includes many items; removing one might be okay as we still preserve the info elsewhere. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Moving it is fine as long as we keep it somewhere. So we can put it in Schedule section and remove from responsibilities list. Thus responsibilities list will exclude the on-call line. Now we need to ensure we don't include boilerplate like EEO, application instructions, etc. Now produce HTML fragment:
About the role
Exciting Career Opportunity with Avance Care! Join our rapidly expanding network of 30+ practice locations in the Triangle Area (Raleigh-Durham-Chapel Hill), the Charlotte Region, and Wilmington, NC. Avance Care is dedicated to elevating the standard of healthcare. As one of North Carolina's largest networks of independent primary care practices, we offer comprehensive services to support the physical, mental, and emotional health of our patients.
As our Application Analyst, you’ll be responsible for configuring, modifying, testing, and maintaining software applications. In addition to coordinating all issues that arise during the project for the application area. You’ll build collaborative relationships with project leadership, business owners, clinical department users, and other corporate departments to facilitate usage and acceptance of the system.
Responsibilities
- Act as the primary support contact for the Ambulatory application’s end-users
- Recognize issues that arise in their application area as well as issues that impact other application teams, and work to resolve them
- Guiding workflow design, building and testing the system, and analyzing other technical issues associated with EPIC software
- Identifying and implementing request changes to the system
- Serving as a liaison between end users’ workflow needs and EPIC implementation staff
- Maintaining regular communication with your EPIC representatives including participating in weekly project team meetings
- Working with Epic representatives, the organization’s business community, and end users to ensure the system meets the organization’s business needs regarding the project deliverables and timeline
- Develop an understanding of operational needs to set the direction for the organization’s workflows by attending site visit and other integrated sessions
- Participate in training and working with end users
- Holding weekly communications with team members to discuss the status of deliverables, shared issues, end-user concerns, budget, and upcoming milestones
- Adhering to service level agreements in incident and task management
- Attending and participating in workgroup and steering meetings
- Preparing agendas and performing system demonstrations for stakeholders
- Review and complete Epic NoVA notes and upgrades within the project timelines
- Maintain all applicable certification(s) and ensure CEE’s are up to date
- Translating operational requests into Epic build tasks
- Performs other duties as assigned
Qualifications
The ideal candidate will possess an associate or bachelor’s degree in information technology (or a related field) and at least two years of EMR experience. Epic certification or accreditation is required in a primary application—such as EpicCare Ambulatory, Cadence, Prelude, Welcome, MyChart, or HealthPlanet/Compass Rose —with additional certifications highly preferred.
Schedule
Required On-Call after hours and on weekends at management’s discretion.
Check for any leftover boilerplate: none. Make sure no