Application Analyst II - Beacon/Clinical Research

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. Position Summary - this is prose, so

2. Key Responsibilities - list of duties, so

• 3. Application Analyst Team Overviews - this seems like a section about the team and applications, could be prose or list 4. Minimum Requirements - list of requirements 5. For Individuals Clinically Trained - additional requirements for clinically trained individuals 6. Preferred Requirements - list 7. Pay Range - specific pay range given 8. Other Information - hybrid role details, schedule 9. About ECU Health - company description 10. General Statement - EEO/legal boilerplate (should be removed per rules) Rules: - Use

  for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

  • for lists - Use

    for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Let me map the content to appropriate sections: 1. "Position Summary" -> could be "About the role" heading with prose 2. "Key Responsibilities Include, But Not Limited To" -> "Responsibilities" heading with list 3. "Application Analyst Team Overviews" -> this describes the team and applications, could be part of "About the role" or separate "Team Overview" but the rules suggest standard headings. Might fit under "About the role" or "Requirements"? Actually it describes the applications they support and on-call rotation. Could be a "Team Overview" section but not a standard heading. The rules list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use those. "Team Overviews" might be part of "About the role" or "Requirements". I'll include it as a subsection under "About the role" or separate? The rules say use

    for section headings like those examples. I can use "Team Overview" as a heading? But the examples are specific. I think I should stick to the suggested headings but can add others if needed? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But they say "Prefer a few substantive sections over many thin ones." So I should group logically. Let me structure: - About the role: includes Position Summary and Team Overviews (since both describe the role) - Responsibilities: Key Responsibilities list - Requirements: Minimum Requirements list - Qualifications: For Individuals Clinically Trained (since it's additional qualifications) and Preferred Requirements - Pay: Pay Range given - Schedule: Other Information includes schedule details (hybrid, in-office expectation, Monday-Friday, day shift) - Benefits: "Great Benefits ECU Health" but no details? Actually "Great Benefits ECU Health" is just a phrase, then "About ECU Health" describes the organization. No specific benefits listed. The rules say never create Benefits section unless posting actually states them. The posting says "Great Benefits ECU Health" but doesn't list any. So I should not create a Benefits section. However, "Other Information" includes hybrid role and schedule. That could be Schedule section. Also "About ECU Health" is company description, could be part of "About the role" or separate? The rules say remove boilerplate, but company description might be considered substantive? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." "About ECU Health" is not boilerplate, it's company info. But the page already shows the job title, maybe company info is also shown elsewhere? The user didn't say to remove company description. However, the rules say "Preserve ALL substantive information". I think I should include it, maybe under "About the role" or a separate "Company Overview" but not a standard heading. I'll include it as a paragraph under "About the role" or after. General Statement is EEO/legal boilerplate, should be removed. Now, let's write HTML. I'll start with

    About the role

    then

    for Position Summary, then maybe a subheading for Team Overview? But only

    for section headings. I could include team overview as part of the prose or as a list. The team overview includes a list of applications. That could be a list. I'll do:

    About the role

    Position Summary text...

    This position is required to rotate on-call responsibilities. All Application Analysts are required to provide all core job duties for, but not limited to, the following applications to provide comprehensive tools for end users.

    • Epic Electronic Medical Record, specifically EpicCare Ambulatory, SmartForms, Haiku/Canto, Phoenix, Stork, Hospital Outpatient Departments (HOD), Beacon, Kaleidoscope and associated Epic tools such as Reporting Workbench and SlicerDicer.
    • Integrated content from IMO, Surescripts, and Krames Staywell.
    But the team overview says "Ambulatory Team Epic Electronic Medical Record, specifically EpicCare Ambulatory, SmartForms, Haiku/Canto, Phoenix, Stork, Hospital Outpatient Departments (HOD), Beacon, Kaleidoscope and associated Epic tools such as Reporting Workbench and SlicerDicer. Integrated content from IMO, Surescripts, and Krames Staywell." That's two bullet points. Now Responsibilities:

    Responsibilities

    • Takes initiative to meet with end users for ongoing review of workflows associated with upcoming enhancements or system changes.
    • Performs the evaluation, testing, and implementation of defect patches, system upgrades and releases according to the Information Services support model and change control procedures.
    • Evaluates and recommends business process and technology driven enhancement opportunities based on application system upgrades, releases and patches.
    • Ability to effectively analyze and resolve simple to moderate issues.
    • Provides well-written and effective professional and technical documentation.
    • Independently manage individual work effort, including developing, executing, and monitoring of a work plan in addition to assisting work efforts of others.
    • Stays informed on current market trends and emerging technology developments that impact their application.
    • Determines solutions with minimal assistance and makes effective decisions within scope of authority.
    • Adheres to change management standards and established Service Level Agreements (SLA) for incidents and requests.
    • Demonstrates effective verbal and written communication.
    • Promotes cooperation and commitment within the team by assisting and working collaboratively with others.
    • Holds self personally accountable to meet or exceed team expectations.
    Requirements:

    Requirements

    • Bachelor's degree in computer science, Information Systems or Healthcare related field or relevant work experience required.
    • 2+ years of progressive experience in IT dealing with vendor application implementations and support or equivalent combination of education, training and experience.
    • Experience in testing software application.
    • Ability to effectively support applications.
    • Works independently with quantifiable and qualitative results.
    • Ability to conduct analysis, document findings, draft plans, execute, monitor and follow up.
    • Independently motivated to seek knowledge through self-education, mentoring, etc. in areas pertaining to their current position.
    • Recognized as a source of knowledge on primary applications both functional and technical operations.
    • Obtains and maintains current certification/accreditation from the vendor and continued education/learning to understand the functionality of applications(s) supported as applicable to the job role.
    Qualifications: For clinically trained individuals and preferred requirements.

    Qualifications

    For individuals clinically trained:

    • Demonstrates knowledge of clinical scope of practice and workflows for roles within clinical setting.
    • Applies clinical knowledge to develop solutions.
    • Ability to communicate clinical concepts to technical team and system design concepts to end users.
    • Understands application and clinical workflow.

    Application Analyst I & II are required to complete and maintain one primary Epic Certification/Accreditation as determined by manager. Epic Certification is obtained through onsite training in Madison, WI, and Accreditation is achieved through remote training. The class content is the same for both certification and accreditation. Team members must achieve minimal required score on their application project and test. See alternative requirements below.

    Preferred requirements:

    • Experience in system analysis with special emphasis on system methodologies, project management and business process reengineering related to information systems preferred.
    • Experience in health care setting preferred.
    Pay:

    Pay

    $75,857.60 - $110,567.60/year

    Schedule:

    Schedule

    Hybrid role (based out of Greenville, NC): In-office expectation between 0 - 4 times/year. Monday - Friday, full-time, day shift: 9:00 a.m. - 5:00 p.m.

    About ECU Health: I'll include as a paragraph under About the role or separate? Since it's company description, maybe add after Schedule? But the rules say prefer few substantive sections. I could add a "Company Overview" heading but not in the example list. I'll include it as a paragraph under "About the role" or at the end. However, the instruction says "Output ONLY the HTML fragment". I think I'll add a final

    About ECU Health

    but that's not in the example headings. The example headings are "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About ECU Health" is not there. But the rules say "use

    for section headings (e.g. ...)" meaning those are examples. I can add a heading for company info. However, the posting includes "About ECU Health" as a section. I'll include it as a heading. But the rules also say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The "General Statement" is EEO boilerplate, remove. "About ECU Health" is not boilerplate, it's company description. I'll keep it. I'll add:

    About ECU Health

    ECU Health is a mission-driven, 1,708-bed academic health care system serving more than 1.4 million people in 29 eastern North Carolina counties. The not-for-profit system is comprised of 13,000 team members, nine hospitals and a physician group that encompasses over 1,100 academic and community providers practicing in over 180 primary and specialty clinics located in more than 130 locations. The flagship ECU Health Medical Center, a Level I Trauma Center