> Markdown version of [/jobs/ext/2702706-ehr-data-lead](https://www.wearedevelopers.com/jobs/ext/2702706-ehr-data-lead). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # EHR Data Lead - **Company:** Chamber Cardio - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Clinical Data Repository, Databases, Data Transmissions, Data Security, Data Sharing, Data Warehousing, Health Information Technology, Interoperability, Virtual Private Networks (VPN), Python (Programming Language), Remote Access Technology, EClinicalWorks, SQL Databases, Data Streaming, File Transfer Protocol (FTP), Data Ingestion, EHR Systems, Fast Healthcare Interoperability Resources, Health Level Seven International, Api Management - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/ehr-data-lead-chamber-cardio-8696822 ## About the Role * 5-7+ years of experience in healthcare technology, EHR implementation, or interoperability * A track record getting live data access across multiple ambulatory EHR systems - through APIs, HL7/FHIR, VPN access, portal pulls, or other nonstandard paths * Working knowledge of healthcare interoperability standards (FHIR, HL7v2, C-CDA) - enough to use them fluently, not necessarily to have built interface engines from scratch * Experience navigating vendor and practice-IT relationships to secure access - you can drive a procurement or coordination conversation, not just a technical one * Comfort operating across the spectrum from clean API integrations to scrappy, get-it-working approaches * Fluency with clinical and value-based care concepts: eligibility, claims, attribution, transitions of care, and GDMT * AI-native and genuinely curious about automation. You can automate yourself into being 3x as effective using SQL, Python, or tools like Claude - and you'll pass a basic coding assessment * A pragmatic, ownership-minded approach - you simplify what's overcomplicated, and you ship * Working knowledge of HIPAA and data protection requirements as they apply to clinical data transmission and third-party data sharing., Remote, located in the Eastern or Central time zone. Periodic travel to practice sites or Chamber offices as needed. You must be authorized to work in the U.S. without sponsorship. ## Description Chamber Cardio is building the connective tissue between our value-based cardiology network and the practices we serve. We're hiring an EHR Data Lead to own how clinical data moves in and out of local practice EHRs - making sure the right notifications, care gaps, and transitions-of-care signals reach providers inside the tools they already use. Our practice EHRs are a patchwork - some offer clean APIs, some speak HL7/FHIR, some require a VPN login, a portal pull, or a CSV export. You'll meet each one where it is, coordinate with the vendor or practice IT when needed, and get the data flowing. This is a hands-on, build-it role. You're equally comfortable wrangling an HL7 feed, reasoning about FHIR resources, and finding a pragmatic workaround when a practice's system won't cooperate. You don't need to be a software engineer - but you do need to know EHRs from the inside, move data confidently on your own, and use AI to do the work of three What You'll Do * Get read and write access into a fragmented set of practice EHRs - via FHIR APIs, HL7 feeds, VPN/remote access, portal pulls, SFTP drops, or CSV exports, whatever the practice's system supports - and land that data where our engineering team can clean, normalize, and model it. * Coordinate directly with EHR vendors and practice IT teams to negotiate access, troubleshoot connections, and unblock integrations that don't have an out-of-the-box path - including writing and overseeing Data Transfer Agreements (DTAs) with external providers. * Design and ship clinical notifications to practices - GDMT prompts, care gaps, ADT-triggered discharge alerts, and transitions-of-care signals - so they land inside provider workflows, not a separate portal. * Do the first-pass mapping of raw patient data from disparate EMR formats toward our standardized target data models, handing off translation-ready data for engineering to finish cleaning and modeling. * Apply AI tooling to extract, normalize, and route unstructured clinical data where direct integration isn't possible. * Support partner and payer data integrations - ingesting eligibility files, claims, and attribution data, and producing return files, in step with our analytics stack (dbt, attribution logic). * Partner with internal engineering on downstream cleaning, normalization, and modeling - your job is getting the data in the door, not owning the data model. Troubleshoot data ingestion errors together and work with database developers to keep our data warehousing running smoothly. * Partner across teams - clinical, network, and practice-facing - to translate operational needs into reliable data flows. * Build for durability: the monitoring, error-handling, and documentation that keep these integrations dependable as we scale. * Ensure strict compliance with HIPAA and data protection laws throughout data transmission and handling. What You'll Achieve in Your First 90 Days By Day 30 * Get fluent in how Chamber sources, evaluates, and stands up integrations - and get the new practice cohort wired in and ready to build against. By Day 60 * Define the integration strategy by choosing which point solutions and EHR-wide partnerships to pursue, with a priority on a master integration agreement with eClinicalWorks, which covers roughly 40% of our practices and offers the greatest opportunity to scale. By Day 90 * Establish live read access for transitions of care across 70% of patient coverage, with base integrations built for our larger practices - the foundation everything else will be built on top of. ## Related Videos - [Smart City, Smart Mobility](https://www.wearedevelopers.com/videos/954-smart-city-smart-mobility) - [Bitcoin SV: The Massively Scaled Blockchain to Meet Developer Needs](https://www.wearedevelopers.com/videos/20-bitcoin-sv-the-massively-scaled-blockchain-to-meet-developer-needs) - [Kubernetes and Microservices with Multi-Model Databases](https://www.wearedevelopers.com/videos/382-kubernetes-and-microservices-with-multi-model-databases) - [What if your HR software adapted to you, not the other way around?](https://www.wearedevelopers.com/videos/100259-what-if-your-hr-software-adapted-to-you-not-the-other-way-around) - [Building Accountability in Agentic AI](https://www.wearedevelopers.com/videos/100046-building-accountability-in-agentic-ai) - [ZEISS & Microsoft - Building the Next Generation Medical Ecosystem in the Cloud](https://www.wearedevelopers.com/videos/424-zeiss-microsoft-building-the-next-generation-medical-ecosystem-in-the-cloud) ## Related Articles - [The Most Popular IT Jobs on the Market](https://www.wearedevelopers.com/magazine/376-the-most-popular-it-jobs-on-the-market) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs) - [What’s the Difference between a Junior, Mid, and Senior Developer?](https://www.wearedevelopers.com/magazine/238-what-s-the-difference-between-a-junior-mid-and-senior-developer) - [Top-Paying Tech Jobs (with Salaries)](https://www.wearedevelopers.com/magazine/372-top-paying-tech-jobs-with-salaries) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [7 Most Popular Web Developer Jobs in Europe](https://www.wearedevelopers.com/magazine/163-7-most-popular-web-developer-jobs-in-europe)