01
Access control
Identity, roles, and least-privilege boundaries decide who can reach patient information — enforced in the backend, not only hidden in the interface.
SERVICES / HEALTHCARE SOFTWARE
HIPAA-compliant software,
engineered with security by design.
I build healthcare software as both a podiatric medical student and a cybersecurity engineer — treating patient-data protection as part of the architecture rather than a checklist added at the end.
01 / SAFEGUARDS IN THE ARCHITECTURE
Protect the data, then build the product.
HIPAA’s security safeguards describe outcomes — control access, protect information, and stay accountable for it. These are the engineering practices I use to support those outcomes in real software.
02
Data protection
Health information is encrypted in transit and at rest, with data minimization so a system only stores what it genuinely needs to do its job.
03
Audit trails
Meaningful logging of access and changes, so a practice can answer who saw what, when, and why — without logging the sensitive values themselves.
04
Review and hardening
Threat modeling, input validation, dependency review, and testing how the system might fail before it is trusted with real patient data.
02 / HEALTHCARE WORK
Built for clinicians and the people they treat.
FootCheckAI & FOOT HEALTH
FootCheck
Bringing technology closer to foot health. A platform focused on early awareness, self-monitoring, and education.
BodyOSPERSONAL HEALTH
BodyOS
An AI-assisted fitness platform connecting training, progress tracking, and a personal coaching experience.
Smillin Healthcare TechFOUNDER · HEALTHCARE TECHNOLOGY
Smillin Healthcare Tech
My healthcare technology studio, connecting product design and engineering to the needs of clinicians and patients.
GoogolgonHEALTHCARE PORTFOLIO
Googolgon
A healthcare portfolio platform with a cohesive brand system, marketing site, and structured content.
03 / HOW THE WORK RUNS
A clear path from idea to protected system.
Each stage keeps engineering decisions and data-protection decisions in the same conversation.
Map the data
Identify what health information the system touches, where it travels, and who genuinely needs it.
Design boundaries
Define identity, roles, storage, encryption, and the trust boundaries between services.
Build carefully
Implement the product with validation, authorization, and audit logging as part of the feature, not an afterthought.
Review honestly
Test how the system could fail, review dependencies and access paths, and document what remains for your compliance team.
Engineering practices support compliance; they do not replace a formal HIPAA risk assessment, legal review, or a business associate agreement. I work alongside those.
GOOD WORK STARTS WITH A CONVERSATION