EMR Applications Analyst

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key info: - Position is REMOTE. Candidate must be able to work eastern standard time hours. - Salary Range: $125-140K (DOE) - About PRISM Vision Group: description. - Role description: connective tissue between clinical and business operations and systems. - FY27 priorities etc. - What You'll Do: list of duties (multiple bullet-like paragraphs). We need to put these in

• . - Required: "What You'll Bring" list of requirements. - Preferred: list. - What Success Looks Like: description of success metrics. We need sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have remote and EST hours -> could be Schedule? Actually schedule: remote, must work EST hours. That's schedule info. Could put under Schedule section. Pay: Salary Range $125-140K (DOE). So Pay section. Benefits: Not mentioned explicitly. No benefits details. So we should NOT create Benefits section because no specific content. Qualifications: Could be education (Bachelor's degree or equivalent). Could be part of Requirements. But we have separate Requirements and Qualifications sections. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = maybe preferred? But we have Preferred separate. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content. We have: - About the role: description of PRISM and role purpose (first paragraphs). Could be About the role. - Responsibilities: the "What You'll Do" bullet points. - Requirements: the "Required What You'll Bring" list (mandatory). - Qualifications: maybe the education (Bachelor's degree) and maybe "Proven, hands-on experience supporting a complex..."? Actually those are requirements. But we can split: Requirements = mandatory experience and skills; Qualifications = education? However we also have Preferred section separate. The instructions didn't list Preferred as a heading option, but we could include it under Qualifications or Skills? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit Preferred somewhere, maybe under Qualifications or Skills. But we should not invent headings not listed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive list. But they say "include a section ONLY when the posting has real, specific content for it". So we can add a Preferred section if we want, but better to map to existing headings. Could treat Preferred as part of Qualifications or Skills. Let's think. Qualifications could include education and maybe certifications. Skills could include technical skills like HL7, APIs, reporting/BI, etc. The Preferred list includes: Direct experience with Athena, Nextech, or SIS; Experience in ophthalmology, retina, ASC, or another specialty ambulatory care environment; Experience supporting technology onboarding for practice affiliations, de novo openings, or M&A integrations; Familiarity with integration and interoperability tools (HL7, APIs) and basic reporting/BI concepts. Those could be considered Skills or Qualifications. Since they are "Preferred", we could still put them under Skills (maybe as a subsection). But we need to avoid filler. We also have "What Success Looks Like" which could be a section maybe not in list but we could include as a separate section like "Success Metrics" but not in the given headings. However we could incorporate into Responsibilities or maybe a separate section like "Expectations". But instructions: "Prefer a few substantive sections over many thin ones." We could add a section for Success Looks Like as its own heading (maybe "Success Metrics") but not in the given list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. We could incorporate success metrics into Responsibilities or maybe a separate "Expectations" but that might be thin. Could add a section "Performance Expectations" but not listed. I'd rather include it under Responsibilities as part of what success looks like? But it's more about outcomes. Could create a section "Goals" but not listed. I'd rather add a section "Success Metrics" as a heading; it's still a heading and uses

  . The instruction didn't forbid other headings; it just gave examples. So it's okay. But to be safe, we could add a section "What Success Looks Like" as a heading. It's specific content. Now schedule: remote, must work EST hours. So Schedule section. Pay: Salary Range $125-140K (DOE). So Pay section. Benefits: none. Now we need to output only HTML fragment, no /, no markdown. We'll produce something like:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • Bachelor’s degree or equivalent practical experience.

  Skills

  • ...
  ...

  Pay

  Salary Range: $125-140K (DOE)

  Schedule

  Remote position; must be able to work Eastern Standard Time hours.

  What Success Looks Like

  ...

  We need to ensure we preserve all substantive info. Let's extract details. About the role: The first paragraph after "This position is REMOTE..." includes description of PRISM Vision Group and role purpose. Let's capture: "At PRISM Vision Group, we are passionate about transforming community ophthalmology and retina practices into centers of excellence, helping physicians deliver world-class, comprehensive eye care to patients. Our commitment to cultivating an unrivaled practice environment for affiliated ophthalmologists, retina specialists, and optometrists is unwavering. With a rapidly growing network of over 200 affiliated physicians, 90+ clinics, 8 state-of-the-art ambulatory surgery centers, and robust research and teaching programs, we are redefining the standard of care every day. This role is the connective tissue between clinical and business operations and the systems that run them — translating how practices actually work into system configuration, integration, and support, and making sure PRISM gets the full value of its EMR investments rather than just keeping the lights on. As PRISM works through FY27 priorities — platform stability across Athena, SIS, and Nextech and a growing pipeline of AI-enabled clinical workflows — this role will be one of the primary hands executing that work and one of the primary voices shaping what comes next." That's the about. Now Responsibilities: The "What You'll Do" section includes multiple paragraphs each starting with a bold heading? Actually they have headings like "Be the Operational Partner", "Serve as the primary technology partner...", etc. We need to capture each bullet as a list item. Let's parse: - Be the Operational Partner Serve as the primary technology partner to clinical and business operations leaders on all things EMR — understanding how practices work and translating that into system requirements, configuration, and workflow design. Build trusted, ongoing relationships with practice administrators, clinical leadership, and end users so that EMR decisions are grounded in how care gets delivered, not just how the system is built. - Own the Vendor Relationship Act as the primary point of accountability for assigned EMR vendor relationship(s) — managing escalations, tracking issue resolution, and holding vendors to committed timelines and SLAs. Stay current on vendor roadmaps and releases and represent PRISM’s needs and priorities directly with the vendor, including advocating for fixes and enhancements that matter to PRISM’s practices. - Drive Value Proactively Look beyond ticket queues to actively find opportunities to get more value from the EMR — underused features, workflow redesign, or new modules that reduce manual work or improve the patient/provider experience. Bring ideas forward rather than waiting to be asked; treat the EMR as a platform to be optimized, not just a system to be maintained. Participate proactively in testing new EMR releases, patches, and updates before they go live — partnering with the vendor and internal teams to catch issues before they reach end users. Pull reports and extract data from the EMR to support billing, clinical decision-making, and other operational reporting needs as they come up. - Solve for the Gaps When the EMR doesn’t have an out-of-the-box answer, find one — through configuration, integration, workaround, or partnering with engineering and business systems analyst resources to build a custom solution. Balance creativity with discipline: solutions need to be supportable long-term, not just clever in the moment. - Understand The Whole System Map and document upstream and downstream impacts before changes go live — across practice management, billing, scheduling, communicator/AI scribe tools, data & analytics, and other integrated systems. Partner with Clinical Informatics, Compliance, Site Reliability, and the broader Applications team on go-lives, upgrades, de novo site openings, and M&A technology integrations. - Own the Day-to-Day Provide hands-on day-to-day EMR support — triaging and resolving tickets, troubleshooting production issues, and escalating appropriately when a fix requires vendor or engineering involvement. Maintain data integrity, security, and HIPAA compliance within the EMR — including reviewing user access appropriately, safeguarding PHI, and escalating any potential security or privacy concerns in line with PRISM policy and regulatory requirements. Maintain clear, current documentation: configuration records, SOPs, and training materials that keep support sustainable as the team and practice footprint grow. Participate in on-call or after-hours escalation coverage as needed for critical EMR issues affecting patient care. We need to preserve all substantive info. We'll create list items each maybe containing multiple sentences. Could combine each bullet's subpoints into one li with line breaks? But HTML li can contain

  or
  . Simpler: each responsibility as a li containing the sentences separated by spaces. We'll keep them as is. Now Requirements: "Required What You'll Bring" list: - Proven, hands-on experience supporting a complex, specialty-specific or enterprise EMR — for example NextGen, Epic, Oracle/Cerner, or a comparable specialty platform — in a healthcare or ambulatory care setting. - A demonstrated ability to translate clinical and business operations needs into system requirements, configuration, and workflow design. - Experience owning a vendor relationship — comfortable managing escalations and holding vendors accountable for outcomes, not just logging tickets. - Working knowledge of HIPAA and healthcare data security/privacy requirements, and experience applying them to day-to-day EMR administration and support. - An analytical, systems-level mindset: able to map dependencies and anticipate the downstream effects of a change before it happens. - Strong communication skills and the judgment to work directly and credibly with clinical and operational leaders. - Bachelor’s degree or equivalent practical experience. We'll put each as li. Now Preferred: we could put under Skills or Qualifications. Let's decide to put under Skills (