01 · SOFTWARE PRODUCT2026 / DEPLOYED SOURCE
ClinicalSOS
A regulatory-intelligence and clinical workflow platform translating compliance signals into scoped cases, tasks, evidence, and plan-of-correction work.
Examine the product workSELECTED WORK / HEALTHCARE TECHNOLOGY & CLINICAL PRODUCT
Technology should work for the people doing the caring.
I'm David E. Kissinger, BSHA, RN. My work connects frontline nursing, healthcare operations, interoperability, technology strategy, and the difficult last mile: getting better workflows into everyday practice.
THE THREAD THROUGH THE WORK
Clinical insight→Product requirements→Implementation→Adoption & learningCare delivery is the test. The interface is only the beginning.
01 / SELECTED WORK
Four different kinds of work. One operating perspective.
02 · EARLY PRODUCT CONCEPT2015 / PROTOTYPE
Dash2Care
A hackathon prototype built around the information gap between a homebound patient, family caregivers, and the clinical team.
Explore the case study03 · INTEROPERABILITY & POLICY2011–2024 / ADVOCACY
HIMSS & health IT
National public policy committee service, Ohio chapter leadership, Statehouse advocacy, and HIMSS Interoperability Showcase engagement.
View the documented record04 · CLINICAL IMPLEMENTATIONCARE OPERATIONS / PRACTICE
From release to adoption
Operational leadership grounded in psychiatric nursing, care delivery, staff training, multi-site workflows, quality oversight, and practical change management.
See the operating approach02 / HOW I APPROACH PRODUCT WORK
Start with the handoff. Finish with the experience.
A workflow can be technically correct and still fail in practice. I evaluate where information changes hands, who must make the next decision, what a clinician needs to trust the system, and how teams will learn whether the change helped.
- ListenUnderstand the care problem and frontline constraints.
- TranslateExpress the problem as product requirements and safe workflow choices.
- ImplementCoordinate dependencies, training, rollout, and change management.
- EvaluateMonitor adoption, exceptions, user feedback, and patient safety.
03 / INDEPENDENT EVIDENCE
Original work and external records, clearly distinguished.
01ClinicalSOS source repositoryPublic GitHub project and technical history↗
02Dash2Care hackathon coveragePublished account of the idea and cross-functional prototype↗
03Ohio Health IT Advocacy Day agendaHIMSS program identifying the 2017 training session presenter↗
Evidence boundaries matter: a concept is not a clinical deployment; a production code release is not verified customer adoption; an operational framework is not a claim of measured product outcomes. Case studies identify their stage and supporting material.
LET'S WORK ON WHAT MATTERS