Sr Application Analyst (Epic Willow Certified))
Wellstar Health System · Atlanta, GA · 3 wk ago
Information TechnologyFull-time
We need to extract substantive content: job summary, responsibilities, requirements, etc. Remove boilerplate like mission statements? The user says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement may be considered boilerplate? It's part of the posting but maybe not essential? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The mission statement is substantive? It's about company mission; maybe keep? However they say "Prefer a few substantive sections over many thin ones." We can include sections: About the role (maybe job summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real specific content.
Let's parse the posting:
- Intro: "How would you like to work in a place where your contributions and ideas are valued? A place where you can serve with compassion, pursue excellence and honor every voice? At Wellstar, our mission is simple, yet powerful: to enhance the health and well-being of every person we serve. We are proud to have become a shining example of what's possible when the brightest professionals dedicate themselves to making a difference in the healthcare industry, and in people's lives." This is generic fluff; maybe we can keep as "About the role" or "About Wellstar"? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. The intro could be considered about the organization; we could put under
About the role
orAbout Wellstar
. However they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role for intro. - "Work Shift Day (United States of America)" maybe metadata; we can drop or put in short p. - "Job Summary Functions under the direction of the IT Manager. Senior Application Analyst provides advanced system-level support of multi-user clinical or financial applications, operating systems, hardware, software, and reporting tools, including installation, configuration, training, maintenance, and end user support of complex systems. Requires advanced knowledge of systems analysis. In-depth knowledge of project management concepts and methodology. Able to lead and participate in project planning sessions. Ability to establish project goals, milestones, and procedures. Able to manage multiple projects with varying levels of complexity. The Senior Application Analyst works closely with project leaders on all aspects of project planning to meet project deadlines. Promotes excellent customer service and strong communication skills to ensure the success of all software applications. Works with outside departments to promote, educate and train on current applications. Works with other members of the Information Systems staff, clinical and operational departments and other WHS personnel to accomplish the goals established for the project." That is job summary; we can put under About the role or Responsibilities? Probably About the role. Then there is a long list of competencies: Initiative, Decision Making/Judgment, Results Focus, Adaptability/Flexibility, Creativity/Innovation, Project Management, Mission, Vision, and Credo, Self Development. These are essentially responsibilities/qualities. Could be grouped under Responsibilities or Requirements. We need to decide sections: maybe About the role (summary), Responsibilities (list of duties), Requirements (knowledge/skills), Qualifications (maybe education/experience not explicit), Skills (maybe list), Benefits/Pay/Schedule not present (no specifics). So we should not create those sections. Thus we will output:About the role
... job summary ...
Responsibilities
- ... each bullet from the competencies ...
- but that would lose the heading structure. Better to have each competency as a subsection? But only allowed headings are the predefined list; we cannot create arbitrary headings like Initiative etc. However we could embed them as within
- ? But we need to preserve ALL substantive information; we could put the competency heading as a inside a
- or as a
preceding the list. 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 a
Responsibilities
then inside we can havefor the prose paragraphs and
- for bullet points. However we have multiple competency sections each with prose and bullets. We could either combine all prose into
- or as a