Clinical workflow platform built from daily EMR experience.
Featured Project / Clinical Documentation Foundation
SKChart
Healthcare workflow platform developed from daily clinical practice, long-term EMR use, and fragmented clinic documentation workflows.
Disconnected charting, photos, documents, payments, and visit notes.
Patient-centered documentation foundation for real clinic workflow.
Communication became the next informatics bottleneck.
Overview
SKChart began as a practical Clinical Informatics response to workflow issues observed through outpatient practice, clinic ownership, and daily EMR use.
Clinical Problem
Daily clinic operations exposed fragmented records, photos, consent documents, payment details, visit notes, and operational records.
Solution
I designed a local-first charting system centered around the patient record, real visit sequence, and EMR-informed workflow needs.
My Role
Physician operator, workflow analyst, product owner, system architect, and hands-on builder.
Key Features
- Patient profiles, visits, treatment notes, and visit history
- Clinical photos grouped by visit
- Consent/document handling, payments, roles, and reporting
- Local-first handling for privacy-sensitive clinic files
Clinical Workflow Impact
- Documentation: visit context and treatment notes stay connected.
- Workflow: photos, documents, and operational records are less fragmented.
- Communication: charting work exposed follow-up and reminder gaps.
- Operations: roles, reporting, and payments support clinic review.
Development Log
Structured patient records, visit-based notes, and photo annotation were added to support cleaner clinical review over time.
View development logScreenshots
Sanitized portfolio screenshots only. No patient data, credentials, or private clinic information.
Technology Stack
Python, Flask, SQLite, HTML, CSS, JavaScript, Git, GitHub.
Future Roadmap
Continue integrating documentation, communication, and staff operations into a connected healthcare workflow platform.