LIAM O’NEIL, PHARMD / FOUNDER

The expertise behind LoneRX.

LoneRX Analytics brings pharmacy practice, clinical research, and software development together. Meet founder Liam O’Neil, PharmD.

FROM THE NORTH CAROLINA COAST TO WISCONSIN

The people make
the work matter.

Liam’s background spans biology and neuroscience, psychology research, and a PharmD from UW–Madison. His work connects careful observation with practical decisions in pharmacy and software.

He now practices as a Wisconsin-licensed staff pharmacist. Patient communication, prescription review, and the demands of a busy pharmacy shape his approach to tools that people can use.

Liam founded LoneRX Analytics in January 2026. His clinical training spans infectious diseases, neurology, ambulatory care, health-system administration, and community practice. The company applies that context to software, analysis, and medical communication.

EXPERIENCE / TRANSLATED INTO PRACTICE

Context you can
build on.

Clinical practice, analytical work, and leadership that inform the company’s approach to a project.

2019

NIIMBL / BIOPHARMACEUTICAL INDUSTRY

Good Manufacturing Practices training

NIIMBL workforce development certificate, awarded August 2019, with chemistry laboratory work and Good Manufacturing Practices training.

Training in laboratory practice and manufacturing quality adds context to the company’s approach to reproducibility and documentation.

2016–17

UNC WILMINGTON / PSYCHOLOGY RESEARCH

Supporting human research

Liam supported mindfulness and biofeedback research with older adults through participant orientation, surveys, and research records.

Experience with participants and research data informs clear communication and careful evidence handling.

NOW

COMMUNITY PHARMACY / WISCONSIN

Build from the work you understand.

As a community staff pharmacist, Liam verifies prescriptions, counsels patients, provides immunizations, and works with prescribers to resolve care questions. That experience informs the company’s software requirements.

Practice informs the requirements: useful information, clear decisions, and tools that fit the day.

2024

UNITYPOINT HEALTH / CLINICAL ANALYSIS

When risk models disagree, inspect the decision.

Compared anticoagulation prescribing across ATRIA, GARFIELD-AF, and CHA₂DS₂-VASc risk models, including statistical testing of differences between models.

Brings to the work: model comparison, guideline interpretation, and careful separation of analysis from clinical decisions.

2025

UW HOSPITAL & CLINICS / NEUROLOGY APPE

Understand the workflow on the other side of the screen.

Used Epic chart review during neurology and stroke-care training and contributed therapy and monitoring recommendations within an interdisciplinary team.

Brings to the work: clinical context, structured chart review, and communication across disciplines.

APPE

HEALTH-SYSTEM ADMINISTRATION / MEDICATION SAFETY

Carry the review toward a practical change.

Helped move an emergency-department epinephrine vial-to-kit initiative from review toward implementation, completed code-blue reviews, and updated medication-use resources.

Connects evidence review, medication safety, and the practical details of implementation.

2023–25

PHI LAMBDA SIGMA / UW–MADISON

Bring people and ideas together.

Liam served as chapter Treasurer (2023–2024) and Vice President (2024–2025), managing budgets and professional development. The chapter initiative he developed won the 2024 Annual Leadership Challenge and was selected for implementation support.

Leadership means making an idea clear enough for other people to act on it.

Selected professional and training experience · Updated September 2026

OPERATING PRINCIPLES

Understand. Test. Refine.

Complexity is earned only when a real workflow needs it.

01

Built around operations

Technology starts with the workflow, not the model.

02

Designed for explainability

Managers should understand why a system produced an answer.

03

Measured against outcomes

Useful software should improve something observable.

04

Designed to evolve

Prototypes should have a path toward dependable operational use.

WHERE THIS COMBINATION FITS

A useful first conversation.

For hiring teams

Health informatics, pharmacy technology, clinical software implementation, and roles that connect users with technical teams.

For collaborators

Bring a workflow, a dataset, or a question. We can discuss scope, constraints, a small prototype, and what would count as success.

Work with Us ↗
PharmDUW–Madison, 2026
WisconsinCommunity pharmacy practice
PublishedPharmacy leadership writing
Hands-onPython, JavaScript, analytics