Curriculum Vitae

I've spent years working at the intersection of behavioral health, clinical workflows, and EHR software, using my background in psychology and psychiatric ethics to understand what a feature actually needs to do, not just what the requirements say it should do.

That means asking questions upstream of where most reviews start: What assumption are we making about how this gets used? How does this hold up in the real clinical environment? What happens in the edge case nobody described? Is this actually solving the problem the clinician or patient has?

That approach has taken different forms. I raised a concern with the design of a Bluetooth beacon before manufacturing, rooted in how the device would actually be used by a patient, contributing to a smaller, tamper-resistant redesign. While working on behavioral health Sleep Log functionality, I traced subtle date-rollover and daylight-saving-time issues back to a mismatch between how the workflow was designed and how it would actually be used in practice. And in STAT News, I wrote about the ethical implications of how the PHQ-9 is used in behavioral healthcare, bringing that same academic training in psychology and ethics to a broader question about clinical tooling design.

The common thread is making sure what gets built actually matches what's needed, understanding the clinical workflow well enough to see where a design assumption and a real clinical reality have drifted apart, early enough to still do something about it.

That's the perspective I want to keep bringing to behavioral health technology: understand the clinical need, shape the design around it, and make sure what ships actually delivers on it.

Advisory Board Member — Remote

• —Serves as an Advisory Board member for ProsperityEHR, a behavioral health EHR platform, contributing ongoing product input as an outside advisor.
• —Participates in monthly advisory board sessions, providing guidance and recommendations on product direction and feature decisions.
• —Responds to ad hoc surveys and follow-up inquiries on product design decisions.

Enrollment Quality Assurance Analyst — Remote

• —Built a SQL-based data quality monitoring solution and Power BI dashboard from scratch, identifying and correcting 2,000+ member records with invalid address punctuation.
• —Developed a SQL-driven Excel tool that displays member records side by side across Epic and QNXT, streamlining duplicate record investigations and supporting merge decisions.
• —Validated high-risk potential duplicate member records during Epic implementation, preventing hundreds of incorrect merges ahead of system migration.
• —Created and published an internal SharePoint-based data dictionary and schema for member record databases, giving analysts and SQL users direct access to table structures and definitions.
• —Automated daily CMS reconciliation queries by embedding them into an Excel template, cutting processing time from 20 minutes to under 30 seconds and eliminating manual reporting errors.
• —Analyzes recurring error patterns to identify root causes upstream in the process, developing corrective action plans in partnership with leadership.

Quality Manager & Regulatory Compliance Analyst — Verona, WI

• —Participated in design reviews, feature planning, and sprint standups, contributing analysis that directly influenced developer design decisions.
• —Co-authored a STAT News op-ed on PHQ-9 suicide screening practices, grounded in outpatient behavioral health screening workflows.
• —Tested and helped shape outpatient behavioral health features including group therapy notes, care plans, and clinical scales/questionnaires, working closely with clinical stakeholders.
• —Designed and ran an empirical study on Bluetooth signal reliability across bracelet models, using Python to inform a hardware selection decision.
• —Raised patient-safety concerns during design review of an inpatient Bluetooth beacon prototype before manufacturing, resulting in a smaller, tamper-resistant redesign.
• —Traced how an inpatient psychiatric Sleep Log feature behaved across date rollovers, late-logged entries, and DST transitions, surfacing workflow breaks before real use.
• —Designed and executed test plans for clinical software workflows, with findings significant enough to delay release until issues were resolved.
• —Tested REST APIs and web services, including FHIR endpoints for behavioral health diagnoses and screening results.
• —Validated front-end data entry against downstream reporting dashboards, confirming data integrity across clinical workflows.
• —Collaborated with clinical subject matter experts across inpatient and outpatient settings to understand real operational and documentation workflows.
• —Integrated AI tools into test plan development and documentation workflows to improve speed and consistency.
• —Identified recurring process inefficiencies and developed a documentation template adopted team-wide.
• —Reviewed software design documentation and traceability records against clinical governance standards, evaluating whether procedures were followed in practice.
• —Identified an accessibility compliance gap and worked with the team to correct the underlying process.