Business Intelligence Developer

Integrated Pain Management Medical Group, Inc.•Portland, OR

2d•$100,000 - $130,000•Onsite

About The Position

BHC’s Revenue Cycle Management (RCM) and financial operations generate a dense stream of performance data — AR aging, cash velocity, denial categories, payer reimbursement, collection ratios — that leadership currently navigates through a mix of ad hoc reports and disconnected exports. The Business Intelligence Developer (RCM & Finance) designs, builds, and maintains the Power BI reporting layer that makes that data navigable, actionable, and trusted. This role owns the analytics surface for RCM leadership, AR management, billing operations, and the CFO — building dashboards against BHC’s Snowflake and dbt data layer and maintaining the metric definitions that ensure every number means the same thing to every stakeholder.

Requirements

5+ years in healthcare RCM analytics, financial reporting, or business analysis — with demonstrated expertise in revenue cycle metrics, AR management, and payer performance reporting.
Strong Power BI proficiency— semantic model development, DAX, Power Query, and Gateway administration. Able to build and optimize production-grade models, not just connect data to pre-built templates.
SQL proficiency sufficient to validate and reconcile reporting data: joins, aggregations, tracing totals, spotting anomalies. Engineering-level SQL is not required; validation-level SQL is non-negotiable.
Workers’ Compensation billing experience, including familiarity with ERA/835 and 837 transaction formats, CARC/RARC denial codes, and EOB interpretation.
Experience supporting multi-platform RCM environments — EMR, clearinghouses, vendor billing platforms — and the data reconciliation challenges that come with them.
Ability to design dashboards for fundamentally different audiences: C-suite executive reporting is not the same design problem as frontline AR operations. You know the difference and build accordingly.
Experience tracing discrepancies across systems — EMR, clearinghouse, vendor reports — and identifying root cause independently before escalating.
HIPAA-compliant reporting experience — PHI masking, role-based access, and audit-ready dashboard design in a healthcare environment.

Responsibilities

RCM & financial reporting estate — Design, build, and maintain dashboards covering charges, payments, adjustments, net collections, AR aging, DSO, cash speed, denial categories, and payer reimbursement trends. Own the full Power BI stack for this domain: semantic model, DAX measures, report design, and Gateway configuration.
Metric definitions & KPI governance — Define, document, and govern RCM performance indicators: charge lag, collection rates, AR aging buckets, denial rates by category, reimbursement trends. Ensure definitions are consistent and defensible across all dashboards serving this domain — resolving conflicts between stakeholder interpretations when they arise.
Vendor & service line segmentation — Build and maintain dashboards that differentiate internal RCM performance from external vendor performance, and Workers’ Compensation billing from other service lines. Stakeholders need to compare performance at the right grain without interpreting raw data themselves.
Data integrity & reconciliation — Own reporting data integrity through tie-outs across the EMR, clearinghouse/remits, and vendor reports. When discrepancies surface, triage root cause, quantify impact, and partner with the Data Engineer to remediate at the source rather than mask in the report layer.
Executive & operational reporting — Deliver accurate, timely reports to RCM leadership, the CFO, and billing operations. Translate complex financial and operational data into insights that drive action — revenue leakage, underpayment trends, reimbursement risk signals, collection velocity. The CFO’s weekly report and the AR coordinator’s denial queue are both your outputs; they should not look like the same dashboard.
Dashboard triage & issue resolution — Triage dashboard and metric issues — filter logic, refresh failures, definition drift, source variances — with enough specificity to resolve within the BI layer or route to Data Engineering with actionable reproduction steps and validation criteria.
Assumes other responsibilities as appropriate to the position and organizational needs