Skip to content
remoty.work

Description review

EHR Integration Engineer (MuleSoft)

Virtusa · United States · back to the listing

HR standards

39/100

poor

Title ↔ description

85/100

strong

Reads as

Backend Engineer

100% confident

What this role officially is

software developer — ESCO, the EU occupation classification

Software developers implement or program all kinds of software systems based on specifications and designs by using programming languages, tools, and platforms.

Also known as: application developer, application programmer, solutions developer, programmer, software specialist, application software developer

How others title the same work

Large employers

  • Software Engineer - OpenStack Canonical
  • C, Golang Software Engineer working on dqlite, a Raft extension for SQLite Canonical Ltd.
  • Containerization & Virtualisation Engineer Canonical Ltd.
  • Go (Golang) Software Engineer, Developer Tooling and Containers Canonical Ltd.
  • Golang Engineer Canonical Ltd.

Startups

  • Anterior (Sequoia-backed, Series B) | Senior Member of Technical Staff | On-Site (New York, NY) | Full Time | $230,000–$300,000 + equity Anterior (Sequoia-backed, Series B)
  • BitPay | Senior Backend Software Developer | Atlanta, GA | REMOTE (US) | BitPay
  • Distributed Systems Engineer Beam
  • Software Engineer, Platform Beam
  • Blaine, WA | CaseLight Systems Inc. (CSI) | Solo Founder | Remote (US Only) | Founding Systems Engineer | FULL EQUITY (30% Stake) Blaine, WA

What the listing never says

  • No section describes what the person would actually do. Scope clarity
  • No pay range published. Candidates cannot tell whether applying is worth their time. Pay transparency

The listing, marked up

Nothing in the wording of this listing tripped a check. The scores above still judge how complete and coherent it is.

This is a remote position.

For one of our clients from Medical industry we are looking for EHR Integration Engineer (MuleSoft).
Requirements

• Proven experience with MuleSoft (Anypoint Platform) — API design, DataWeave transformations, and connector development/configuration.

• Hands-on experience working with MuleSoft’s EHR connectors, integrating with systems such as Epic, Cerner/Oracle Health, Athena, or Allscripts — direct experience with multiple is preferred.

• Working knowledge of HL7 v2.5 message structure and MLLP transport.

• Working knowledge of FHIR R4 resources and RESTful FHIR APIs.

• Experience with Kafka (producer/consumer patterns).

• Understanding of healthcare data privacy/security requirements (e.g., HIPAA) as they apply to data-intransit and access control.

• Experience designing multi-tenant, configuration-driven integration systems is a strong plus.

Originally posted on Himalayas