Healthcare Informatics & Software Engineering

Repository: github.com/srodriguezloya/omop-development-environment Introduction In my previous post, I covered the OHDSI ecosystem explaining what each tool does, when you need it, and how the components work together. That guide focused on understanding the architecture and making informed deployment decisions for production environments. This post tackles a different but equally important challenge: how do you actually learn and experiment with the OHDSI stack without breaking the bank? The OHDSI community provides an excellent quick-start solution called OHDSI-in-a-Box, designed for rapid deployment on AWS. It’s purpose-built for personal learning and training environments—you can have a complete OHDSI stack running in minutes. ...

Introduction If you’re implementing OMOP CDM for your organization, you’ve likely asked: Do we need to deploy the full OHDSI stack, or just transform our data to OMOP CDM? The OMOP Common Data Model is a data standard—a specification for how to structure observational healthcare data. The OHDSI stack (Achilles, Data Quality Dashboard, WebAPI, Atlas, ARES) consists of tools built to work with that standardized data. Understanding what each tool provides helps you decide which ones your use case requires. ...

I recently migrated my personal infrastructure from nginx to Traefik for reverse proxy and SSL management. Here’s what I learned. The Setup Running multiple services on a single VPS: OpenEMR for family health records This blog (Hugo static site) Future services as needed Why Traefik? Coming from nginx, Traefik offers several advantages: Automatic SSL certificate management with Let’s Encrypt Dynamic service discovery through Docker labels No manual config edits for new services The Migration Process Previously, I was using nginx with cronginx - a Docker container combining Cron, Nginx, and Certbot for automated Let’s Encrypt certificate management. It worked reliably for quite some time. ...