Sr Epic Bridges & Rhapsody Interface Engineer
for sections present. Must not repeat job title. Must include only sections with real specific content. Must not include boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About the role? The first paragraph: "Optum Insight is improving the flow of health data...". That's description. Could be "About the role" or "Overview". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for the introductory description.
- Responsibilities: The "Primary Responsibilities" section with bullet points. Should be Responsibilities
then - ... each bullet.
- Requirements: The "Required Qualifications" list. Could be
Requirements
or Qualifications
. The instruction includes both Requirements and Qualifications as possible headings. We need to decide. Since they list "Required Qualifications" we could use Qualifications
for required qualifications. Or "Requirements". Probably "Qualifications". But we also have "Preferred Qualifications". Could combine? The instruction says prefer a few substantive sections over many thin ones. Could have one Qualifications section that includes both required and preferred? But they said include a section ONLY when posting has real, specific content for it. We have both required and preferred content. Could split into Required Qualifications and Preferred Qualifications as separate sections? That would be thin but maybe okay. However they said prefer a few substantive sections over many thin ones. Could combine into one "Qualifications" section with subheadings? But we cannot use other headings besides . Could use
to separate required vs preferred within same section. That might be better: one
Qualifications
then paragraphs listing required and preferred.
But we also have "Skills" maybe not needed separately.
We have Pay: The posting includes salary range: "The salary for this role will range from $91,700 to $163,700 annually based on full-time employment." Also mention Pay based on factors. So we should include a Pay section.
We have Benefits: The posting mentions "In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements)." Also earlier: "You'll be rewarded and recognized for your performance..." but that's generic. So we have benefits info. So include Benefits section.
Schedule: The posting mentions remote flexibility: "You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week." That's schedule/location info. So we can include Schedule section.
We also have "Application Deadline" etc which is boilerplate/application instructions; we should drop.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO paragraph, drug test, etc.
We must preserve all substantive information: So we need to keep the description about Optum Insight, role summary, responsibilities list, required qualifications list, preferred qualifications list, pay range, benefits description, schedule/remote info.
We must not invent or summarize away detail. So we need to keep each bullet exactly as in posting? We can keep the substance but not necessarily exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Safer to keep the original phrasing.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
Optum Insight is improving the flow of health data and information to create a more connected system. We remove friction and drive alignment between care providers and payers, and ultimately consumers. Our deep expertise in the industry and innovative technology empower us to help organizations reduce costs while improving risk management, quality and revenue growth. Ready to help us deliver results that improve lives? Join us to start Caring. Connecting. Growing together. The Senior Rhapsody Interface Engineer / Server Administrator plays a critical role in maintaining, evolving, and scaling Optum's healthcare integration platform. This position combines hands-on Rhapsody platform administration with advanced interface engineering and technical leadership responsibilities. In this role, you will own the reliability, performance, and architecture of the Rhapsody environment while designing and supporting complex clinical integrations across Epic, Oracle Health, and third party systems. You will also serve as a technical mentor, helping grow and guide a high performing Integration Engineering team supporting mission critical healthcare workflows. You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week.
Responsibilities
- Serve as a senior technical owner for the Rhapsody integration platform across multiple environments
- Install, configure, maintain, and upgrade Rhapsody, including backups, disaster recovery, and environment hardening
- Administer Red Hat Linux and Windows servers, including access controls, security patching, performance tuning, and system upgrades
- Monitor system health, availability, and performance; troubleshoot and resolve complex production issues
- Design and maintain high availability architectures, including virtual machines, clustering, and load balancing configurations
- Develop and maintain platform architecture diagrams, system design documentation, and operational standards
- Design, develop, and support clinical and business interfaces integrating Epic and/or Oracle Health with third party systems and external EMRs
- Lead conversion and migration efforts from legacy systems to modern integration platforms
- Serve as a technical subject matter expert for healthcare integration standards, including HL7, FHIR, and DICOM
- Provide design oversight, code review, and technical guidance to interface engineers
- Mentor and develop team members, fostering best practices, consistency, and continuous improvement across the integration team
- Ensure all integration solutions meet organizational, security, and regulatory requirements
Qualifications
Required Qualifications:
- Epic Bridges certification (current or prior)
- 7+ years of experience in healthcare interface engineering or integration development
- 5+ years of hands on experience with the Rhapsody Interface Engine in a production environment
- 3+ years of integration experience with a major EMR/EHR platform such as Epic or Oracle Health
- 3+ years of experience administering server operating systems, including Red Hat Linux and Windows, with responsibility for access management, system upgrades, and performance tuning
- 3+ years of experience with healthcare integration standards (HL7, FHIR, DICOM)
- 3+ years of experience supporting high availability, 24x7 healthcare systems
- 1+ years of demonstrated experience mentoring or providing technical leadership to engineering teams
Preferred Qualifications:
- Rhapsody Professional Certification
- Relevant technical certifications (e.g., Azure Administrator, CompTIA Security+)
- Experience hosting or administering interface engines in cloud or hybrid environments (AWS, Azure, or Google Cloud)
- Experience leading or supporting platform upgrades, migrations, or large scale integration initiatives
- Knowledge of database technologies, including SQL and/or NoSQL databases
- Familiarity with additional integration engines or middleware platforms beyond Rhapsody
- Proven solid written and verbal communication skills, with the ability to document technical solutions and collaborate with clinical and IT stakeholders
Benefits
In addition to your salary, we offer benefits such as a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements). You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear direction on what it takes to succeed in your role as well as provide development for other roles you may be interested in.
Pay
The salary for this role will range from $91,700 to $163,700 annually based on full-time employment. Pay is based on several factors including but not limited to local labor markets, education, work experience, certifications, etc. We comply with all minimum wage laws as applicable.
Schedule
You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week.
We need to ensure we didn't include any boilerplate like "Application Deadline", "EEO", etc. We removed those.
Check for duplicated lines: We have not duplicated.
Check that we didn't include "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" - that's a policy line; is that substantive? It's about remote work policy. Could be considered part of schedule/remote. Might be worth including? The instruction: preserve ALL substantive information. That line is substantive about remote work policy. Should we include? It is under Preferred Qualifications? Actually it's in the posting: "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy". That's a requirement for remote workers. Could be included in Schedule or a note. Since we have schedule section about remote flexibility, we could add that line there. But we must not invent or summarize away detail. Better to include it as part of Schedule paragraph.
Thus modify Schedule paragraph to include that sentence.
Also we have "No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives." That's benefits fluff but still substantive? Could be included in Benefits.
We already have benefits paragraph; we could add that sentence.
Also "At UnitedHealth Group, our mission is to help people live healthier lives and make the health system work better for everyone..." that's EEO/mission boilerplate; we should drop as it's generic mission/EEO.
We also have "We believe everyone-of every race, gender, sexuality, age, location and income-deserves the opportunity to live their healthiest life..." that's EEO; drop.
"We are committed to mitigating our impact on the environment and enabling and delivering equitable care that addresses health disparities and improves health outcomes - an enterprise priority reflected in our mission." drop.
"UnitedHealth Group is an Equal Employment Opportunity employer..." drop.
"UnitedHealth Group is a drug-free workplace. Candidates are required to pass a drug test before beginning employment." drop.
Now ensure we didn't miss any substantive info: The initial paragraph about Optum Insight and role summary we kept.
The "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear direction on what it takes to succeed in your role as well as provide development for other roles you may be interested in." we included in Benefits.
The "No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives." we could add to Benefits.
Add that to Benefits paragraph.
Now check for any other substantive: "Application Deadline: This will be posted for a minimum
Responsibilities
then- ... each bullet.
- Requirements: The "Required Qualifications" list. Could be
Requirements
orQualifications
. The instruction includes both Requirements and Qualifications as possible headings. We need to decide. Since they list "Required Qualifications" we could useQualifications
for required qualifications. Or "Requirements". Probably "Qualifications". But we also have "Preferred Qualifications". Could combine? The instruction says prefer a few substantive sections over many thin ones. Could have one Qualifications section that includes both required and preferred? But they said include a section ONLY when posting has real, specific content for it. We have both required and preferred content. Could split into Required Qualifications and Preferred Qualifications as separate sections? That would be thin but maybe okay. However they said prefer a few substantive sections over many thin ones. Could combine into one "Qualifications" section with subheadings? But we cannot use other headings besides. Could use
to separate required vs preferred within same section. That might be better: one
Qualifications
then paragraphs listing required and preferred. But we also have "Skills" maybe not needed separately. We have Pay: The posting includes salary range: "The salary for this role will range from $91,700 to $163,700 annually based on full-time employment." Also mention Pay based on factors. So we should include a Pay section. We have Benefits: The posting mentions "In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements)." Also earlier: "You'll be rewarded and recognized for your performance..." but that's generic. So we have benefits info. So include Benefits section. Schedule: The posting mentions remote flexibility: "You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week." That's schedule/location info. So we can include Schedule section. We also have "Application Deadline" etc which is boilerplate/application instructions; we should drop. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO paragraph, drug test, etc. We must preserve all substantive information: So we need to keep the description about Optum Insight, role summary, responsibilities list, required qualifications list, preferred qualifications list, pay range, benefits description, schedule/remote info. We must not invent or summarize away detail. So we need to keep each bullet exactly as in posting? We can keep the substance but not necessarily exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Safer to keep the original phrasing. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:About the role
Optum Insight is improving the flow of health data and information to create a more connected system. We remove friction and drive alignment between care providers and payers, and ultimately consumers. Our deep expertise in the industry and innovative technology empower us to help organizations reduce costs while improving risk management, quality and revenue growth. Ready to help us deliver results that improve lives? Join us to start Caring. Connecting. Growing together. The Senior Rhapsody Interface Engineer / Server Administrator plays a critical role in maintaining, evolving, and scaling Optum's healthcare integration platform. This position combines hands-on Rhapsody platform administration with advanced interface engineering and technical leadership responsibilities. In this role, you will own the reliability, performance, and architecture of the Rhapsody environment while designing and supporting complex clinical integrations across Epic, Oracle Health, and third party systems. You will also serve as a technical mentor, helping grow and guide a high performing Integration Engineering team supporting mission critical healthcare workflows. You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week.
Responsibilities
- Serve as a senior technical owner for the Rhapsody integration platform across multiple environments
- Install, configure, maintain, and upgrade Rhapsody, including backups, disaster recovery, and environment hardening
- Administer Red Hat Linux and Windows servers, including access controls, security patching, performance tuning, and system upgrades
- Monitor system health, availability, and performance; troubleshoot and resolve complex production issues
- Design and maintain high availability architectures, including virtual machines, clustering, and load balancing configurations
- Develop and maintain platform architecture diagrams, system design documentation, and operational standards
- Design, develop, and support clinical and business interfaces integrating Epic and/or Oracle Health with third party systems and external EMRs
- Lead conversion and migration efforts from legacy systems to modern integration platforms
- Serve as a technical subject matter expert for healthcare integration standards, including HL7, FHIR, and DICOM
- Provide design oversight, code review, and technical guidance to interface engineers
- Mentor and develop team members, fostering best practices, consistency, and continuous improvement across the integration team
- Ensure all integration solutions meet organizational, security, and regulatory requirements
Qualifications
Required Qualifications:
- Epic Bridges certification (current or prior)
- 7+ years of experience in healthcare interface engineering or integration development
- 5+ years of hands on experience with the Rhapsody Interface Engine in a production environment
- 3+ years of integration experience with a major EMR/EHR platform such as Epic or Oracle Health
- 3+ years of experience administering server operating systems, including Red Hat Linux and Windows, with responsibility for access management, system upgrades, and performance tuning
- 3+ years of experience with healthcare integration standards (HL7, FHIR, DICOM)
- 3+ years of experience supporting high availability, 24x7 healthcare systems
- 1+ years of demonstrated experience mentoring or providing technical leadership to engineering teams
Preferred Qualifications:
- Rhapsody Professional Certification
- Relevant technical certifications (e.g., Azure Administrator, CompTIA Security+)
- Experience hosting or administering interface engines in cloud or hybrid environments (AWS, Azure, or Google Cloud)
- Experience leading or supporting platform upgrades, migrations, or large scale integration initiatives
- Knowledge of database technologies, including SQL and/or NoSQL databases
- Familiarity with additional integration engines or middleware platforms beyond Rhapsody
- Proven solid written and verbal communication skills, with the ability to document technical solutions and collaborate with clinical and IT stakeholders
Benefits
In addition to your salary, we offer benefits such as a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements). You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear direction on what it takes to succeed in your role as well as provide development for other roles you may be interested in.
Pay
The salary for this role will range from $91,700 to $163,700 annually based on full-time employment. Pay is based on several factors including but not limited to local labor markets, education, work experience, certifications, etc. We comply with all minimum wage laws as applicable.
Schedule
You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week.
We need to ensure we didn't include any boilerplate like "Application Deadline", "EEO", etc. We removed those. Check for duplicated lines: We have not duplicated. Check that we didn't include "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" - that's a policy line; is that substantive? It's about remote work policy. Could be considered part of schedule/remote. Might be worth including? The instruction: preserve ALL substantive information. That line is substantive about remote work policy. Should we include? It is under Preferred Qualifications? Actually it's in the posting: "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy". That's a requirement for remote workers. Could be included in Schedule or a note. Since we have schedule section about remote flexibility, we could add that line there. But we must not invent or summarize away detail. Better to include it as part of Schedule paragraph. Thus modify Schedule paragraph to include that sentence. Also we have "No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives." That's benefits fluff but still substantive? Could be included in Benefits. We already have benefits paragraph; we could add that sentence. Also "At UnitedHealth Group, our mission is to help people live healthier lives and make the health system work better for everyone..." that's EEO/mission boilerplate; we should drop as it's generic mission/EEO. We also have "We believe everyone-of every race, gender, sexuality, age, location and income-deserves the opportunity to live their healthiest life..." that's EEO; drop. "We are committed to mitigating our impact on the environment and enabling and delivering equitable care that addresses health disparities and improves health outcomes - an enterprise priority reflected in our mission." drop. "UnitedHealth Group is an Equal Employment Opportunity employer..." drop. "UnitedHealth Group is a drug-free workplace. Candidates are required to pass a drug test before beginning employment." drop. Now ensure we didn't miss any substantive info: The initial paragraph about Optum Insight and role summary we kept. The "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear direction on what it takes to succeed in your role as well as provide development for other roles you may be interested in." we included in Benefits. The "No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives." we could add to Benefits. Add that to Benefits paragraph. Now check for any other substantive: "Application Deadline: This will be posted for a minimum