Skip to main content

Smile CDR Integration Developer

Posted yesterday

talent software servicesPittsburgh (PA)

SENIORITY

Senior

Apply (opens in a new tab)

About the role

Job Description
Position Summary: We are seeking a Smile CDR Integration Developer to design, develop, and support enterprise interoperability solutions that enable healthcare data exchange across payer, provider, and regulatory platforms. This role will focus on building scalable integrations utilizing Smile CDR, Apache Camel, FHIR APIs, PySpark, JavaScript, and modern integration technologies. The candidate will play a critical role in delivering CMS Interoperability, Prior Authorization, Provider Access, Payer-to-Payer, and BCBSA interoperability solutions.
Key Responsibiities: Design and develop Smile CDR integrations and FHIR-based solutions. Develop Apache Camel routes and integration services. Build and support API integrations with internal and external systems. Develop ETL and data ingestion pipelines using PySpark and Python. Create scalable healthcare interoperability solutions utilizing HL7 FHIR standards. Consume and publish REST APIs across enterprise platforms. Develop and maintain JavaScript-based Smile CDR modules and automation components. Collaborate with architects and business stakeholders to translate requirements into technical solutions. Support testing, deployment, monitoring, and production support activities. Participate in architecture reviews, code reviews, and technical design sessions. Create technical documentation, data mappings, and integration specifications.
Required Qualifications: 5 years of software development experience. Strong experience with: Python / PySparkJavaJavaScriptApache CamelREST APIsJSON/XMLSQLExperience with healthcare interoperability standards. Experience consuming and developing APIs. Strong understanding of distributed integration architectures. Experience with ETL and data engineering practices.
Preferred Qualifications:
  • Smile CDR development experience.
  • HL7 FHIR R4 expertise.
  • CMS Interoperability experience.
  • Prior Authorization, Payer-to-Payer, or Provider Access experience.
  • Databricks experience.
  • Hadoop ecosystem experience.
  • GitLab CI/CD experience.
  • Healthcare payer domain experience.
  • SkillsSmile CDR Development
  • Apache CamelPySparkPythonJavaJavaScriptREST API DevelopmentFHIRHL7Data Engineering
  • Healthcare InteroperabilityETL/ELTIntegration Architecture
DevOps

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this