The Promise and Peril of Software Designed for

The Promise and Peril of
Software Designed for
Forensic Odontology
JOHN MELVILLE, MS, MD
SITE DIRECTOR, CHILD ADVOCACY CENTER AT AKRON CHILDREN’S HOSPITAL,
MAHONING VALLEY.
SOFTWARE ARCHITECT, BUSINESS CASUAL SOFTWARE
Disclosures
X
I am a Software Architect for Business Casual Software.
X
We created PhotoDocumentor.
X
I want to sell it to every one of you.
X
I have worked as a paid expert witness in child abuse
cases.
Agenda
X
Describe the development of PhotoDocumentor, an electronic
medical record designed for medical forensics.
X
Avoid the urge to give a 30 minute infomercial for my software.
X
Determine a software product’s metaphor.
X
Discuss and demonstrate checklists as a clinical quality tool.
X
Evaluate opportunities to integrate complicated mathematics
into forensic odontology.
X
Evaluate and criticize the incorporation of “negative” features in
forensic software.
How to solve a problem with a
computer.
X
Get lucky – Find exactly the software you were looking for.
(www.google.com)
X
Create custom templates, files, and practices in existing software.
(Word, WordPress)
X
Create macros or plug-ins for existing software. (Access, Sharepoint,
Drupal)
X
Write you own software
X
Use a general purpose language. (C#)
X
Beware of products that advertise programming without programming.
My Approach: PhotoDoc
X
X
X
Custom Software Application
X
C#, WPF, Xaml, C++, HLSL
X
42,830 lines of computer code.
X
1,260 pages as a trade
paperback.
It’s a lot of work
X
I started in 2006.
X
I work on PhotoDoc most
evenings and weekends.
People look at me funny when
I say you relax by
programming computers.
Software’s Metaphor
X
X
What does the software think that it does
X
Correlate antemortem and postmortem dental findings.
X
Enhance and modify pictures.
X
Organize, analyze, and present digital forensic evidence.
Signs that your software has the wrong metaphor.
X
There are settings or features you have to never use.
X
Every time you start out you have to change a lot of things.
X
Common or fundamental operations just seem hard.
X
Simple mistakes have serious consequences.
Checklists in Medicine (or
Dentistry)
X
X
1
Medicine is hard
X
People are stupid.
X
Checklists make you smarter
A surgical checklist1
X
Reduced 30 day morality 46%
X
Reduced complications 36%
Haynes AB, Wieser TG, Berry WR, et al. “A surgical safety
checklist to reduce mortality and morbidity in a global
population.” NEJM 2009; 360: 491-499
Computerized Documentation
Promise
X
Faster to write.
X
Faster to read.
X
Consistency
X
Coders get you lots of $$$$!
X
Can guide practitioner into
best practices.
Peril
X
Can be more difficult to
read.
X
Makes imprecise, or worse
incorrect documentation
the easy path.
X
Sometimes the form is going
to be incorrect.
Negative Features
X
Sometimes, what a program will not do can be a
feature.
X
After a note is signed it cannot be changed.
X
The program will not let you delete evidence pictures.
X
Money in a bank account can only get spent once.
X
The problem is that the negative features you put in
V1 and up being your biggest requests for V2.
X
It turns out that the world is messier than we would
like it to be.
X
Back in the paper and pen world, we could break
the rules when we needed to.
Features come in groups
X
Programmers refer to the CRUD operations
X
Create
X
Read
X
Update
X
Delete (And Undelete.)
X
If your software has a negative feature, make sure
you have a way to make it look like you did the
forbidden thing.
X
Alternatively, consider a compensatory operation.
In Conclusion
X
Custom software is an expensive but flexible method to
control your work.
X
X
Expensive for me may become very inexpensive for you.
All software has a metaphor.
X
Using software against its metaphor is a recipe for ongoing
frustration.
X
Custom software can guide professionals into best
practices.
X
Custom software provides space for genuinely innovative
mathematics.
X
Negative features may be helpful, But look that gift horse
in the mouth.