UV (You-vee)
Systems Architect • Building High-Scale Pharmaceutical Infrastructure
I'm a systems-focused engineer and technology leader building large-scale healthcare and logistics platforms.
My work sits at the intersection of healthcare infrastructure, APIs, compliance, and distributed systems. I design and build systems that process millions of dollars in medication inventory, claims transactions, and international shipments every month.
I prefer clean architecture, simple interfaces, and systems that can run reliably for years without constant babysitting.
CTO / Lead Engineer — Parkway Pharmacy
I lead the architecture and development of internal and external platforms supporting:
- Cross-border pharmacy logistics
- Prescription claims processing
- Insurance eligibility and billing
- Cold-chain medication shipping
- Employer healthcare programs
- Regulatory compliance automation
The systems we run power operations shipping medication across the United States and Canada.
A modern REST API for NCPDP D.0 pharmacy claims.
- JSON in / JSON out, the first ever
- Supports B1, B2, E1 transactions
- No pharmacy NPI required
- Designed for developers, not clearinghouses
Goal: bring modern developer tooling to legacy pharmacy claims infrastructure.
A full pharmacy operations platform.
Features include:
- Order intake and processing
- Pharmacist workflow management
- Conveyor and fulfillment integration
- Employer healthcare program management
- Automated compliance checks
- Claims processing and eligibility verification
Designed to replace fragmented pharmacy software stacks with a unified platform.
Custom logistics automation for medication fulfillment.
Integrations include:
- Canada Post
- FedEx
- DHL
- Tariff calculation systems
- Cross-border compliance validation
- Cold-chain monitoring
Focus: reliability, automation, and regulatory compliance.
One of the areas I'm actively exploring is the development of domain-specific language models for pharmacy operations and regulatory compliance.
Healthcare infrastructure relies heavily on complex regulatory frameworks, including:
- NCPDP D.0 claims standards
- FDA personal importation guidance
- DEA controlled substance regulations
- HIPAA / PHIA / PIPEDA privacy compliance
- Insurance billing rules
- Cross-border pharmaceutical shipping regulations
Most of this knowledge currently lives in PDF documents, government guidance pages, and institutional expertise, making it difficult for developers and operators to use programmatically.
Build language models that can assist with:
- interpreting healthcare regulations
- validating pharmacy workflows
- auditing compliance procedures
- explaining insurance claim responses
- identifying regulatory risk in software systems
Example structured and unstructured datasets include:
- NCPDP telecommunications standards
- FDA regulatory guidance
- DEA controlled substance regulations
- Health Canada drug regulations
- insurance claim specifications
- pharmacy operations SOPs
- shipping compliance documentation
- anonymized claim response data
- Compliance copilots for pharmacy operators
- Automated audit assistants
- Developer tools for healthcare APIs
- Real-time claim interpretation
- Regulatory change monitoring
Healthcare compliance models must prioritize:
- factual correctness
- traceable citations
- regulatory jurisdiction awareness
- privacy preservation
- deterministic outputs where required
Unlike general LLM applications, incorrect answers in healthcare systems can have regulatory or legal consequences, so system design must incorporate verification and structured validation layers.
The long-term goal is to build AI systems that understand healthcare regulations deeply enough to assist in designing compliant software systems and operational workflows.
These systems should function less like chatbots and more like compliance engines that help healthcare infrastructure operate safely and legally at scale.
- Node.js / Bun
- TypeScript
- Python
- Ruby
- PostgreSQL
- MySQL
- PlanetScale
- DigitalOcean
- Cloudflare
- MinIO (S3 compatible storage)
- Tailscale
- Linux systemd services
- Next.js
- React
- API-first architecture
- NCPDP D.0
- EDI systems
- Insurance networks
- Shipping carriers
- Payment processors
I believe good systems should be:
- Simple
- Observable
- Auditable
- Deterministic
- Built to last
Healthcare systems in particular must prioritize reliability and compliance over hype.
The best infrastructure is infrastructure nobody has to think about.
Beyond healthcare infrastructure I explore:
- Distributed file systems
- Autonomous trading systems
- Game development
- Developer tooling
- Secure infrastructure design
Outside of engineering I enjoy:
- Ancient history (especially Greece)
- Systems design
- Game development
- Finance and markets
- Cybertruck engineering
Development inquiries:
development@parkwaypharmacy.ca
"Build systems that still work ten years later."