arcane aspects of ehr - ehcca.com › presentations › ehrsummit1 › simkus_ms5.pdf · 10...
TRANSCRIPT
Arcane aspects of EHR
Raymond Simkus MD, CM, Brookswood Family Practice
Who am I?
• Raymond Simkus, MD, CM
• Practicing GP in Langley, BC, just outside of Vancouver• Pilot site for primary care reform for 10 years
• Part of a group that created an EMR in 1979
• Became involved with medical informatics in 1983
• Involved with AMIA, HL7, SNOMED, IHTSDO, Wonca International Classification Committee, Canada Health
Infoway and Canadian Institute for Health Information (CIHI)
October 6, 2010 EHR Summit San Francisco
Larry Weed ‐
the father of the Problem Oriented Medical Record
“If we accept the limits of discipline and form as we keep data in the medical record the physician’s
task will be better defined…and the art of medicine will gain freedom at the level of interpretation and be released from the
constraints that disorder and confusion always impose.”
Weed,1968
The Function of the Medical Record
• to communicate with yourself
• to communicate with others
• quality assurance• research• for the patient• legal document
Themes of this presentation
• Will focus on the user interface and the infrastructure that helps to facilitate efficient
and accurate data input.
• Will mention how different parts of the EMR could interact.
• User frustrations that users have with the products they have to use.
Merck Manual 100th
Anniversary
Office Records
Exam Room
Starting Computerization
Knocking on Doors
EMR Requirements are Not New
• Clem McDonald. The barriers to electronic medical record systems and how to overcome
them. 1997 JAMIA May‐Jun;4(3):213‐21• To solve their record movement problems• To improve the quality and coherence of the
care process• To automate guidelines and care pathways to
assist clinical research, outcomes management, and process improvement.
Octo Barnett 10 Commandments
• There is no such thing as ‘free text’• ‘‘I’m just a country doctor.’’
• Work started in 1964
Octo Barnett 10 Commandments in Clinical Data Management
1)
“Thou shall know what you want to do.”2)
“Thou shall construct modular systems.”3)
“Thou shall build a system that can evolve in a graceful fashion.”4)
“Thou shall build a system that allows easy and rapid programming
development and
programming modification.”
5)
“Thou shall build a system that has a consistently rapid time response and is easy for the non‐
computernik to use.”
6)
“Thou shall have duplicate hardware systems.”7)
“Thou shall build and implement your system as a joint effort with
real users in a real situation
with real problems.”
8)
“Thou shall be concerned with realities of the cost and projected
benefit of the computer
system.”
9)
“Innovation in computer technology is not enough; there must be an
equal commitment to the
potentials of radical change in other aspects of health care delivery, particularly those having to
do with organization and manpower utilization. “
10)
“Be optimistic about the future, supportive of good work that is being done, passionate in your
commitment, but always be guided by a fundamental skepticism.”
10 Commandments of CDS
• 1.
Speed is everything
• 2.
Anticipate needs and deliver in real‐time
• 3.
Fit into the User’s workflow
• 4.
Little things make a big difference –test for usability
• 5.
Recognize that physicians will strongly resist stopping
• 6.
Changing direction is easier than stopping
• 7.
Simple interventions work best
• 8.
Ask for additional information only when you really need it
• 9.
Monitor impact, get feedback and respond
• 10. Manage and maintain your knowledge‐based systems
David Bates 2003
Electronic medical records not seen as a cure‐all
• "Health IT can be beneficial, but many current systems are clunky, counterintuitive and in some
cases dangerous," said Ross Koppel
• Faulty software that miscalculated intracranial pressures and mixed up kilograms and pounds.
• A computer system that systematically gave adult doses of medications to children.
• Washington Post Article Oct. 25, 2009
Think Speed
• Repeated interruptions and pauses are very disruptive to the train of thought
• When you are in the process of dealing with a patient at 60 miles per hour having to pause for
3‐4 seconds is very disturbing• For physicians that use the system in an
interactive manner it is very disruptive• For physicians that use the EHR as a static tool
this is not much of a problem (still in the paper paradigm)
Listening device
How users feel about using current EMRs
Physician ResistanceThis is the main reason given for slow adoption of computers into medical practice
What Physicians Want
Vendors View of the Issues
What Physicians Need
US Pioneers in Medical Informatics
Tipping Point
• The technology adoption curve is moving
from incremental to exponential change
• There is growing pressure from the public– Concerns regarding safety– The public is using computers ‐
why are their
medical records on paper?
• Don Berwick – patience has run out
Blois “Information and Medicine”
• Marsden Blois 1984
• Provides a description of the structure of medical
information
“An Essential Technology for Health Care”
Provides a roadmap to the
getting healthcare
computerized
1st
edition: 1987‐1991
2nd
edition: 1997
Principles of Health Interoperability HL7 and SNOMED
• Tim Benson
• GP from the UK
• Provides a general background on
interoperability
Standards for the Foundation of the EHR
• ISO 10781 Electronic health record system functional model
• ISO 13606 Electronic health record communication
• ISO 18308 Requirements for an EHR architecture
• HL7, SNOMED, LOINC, ICD
User or EMR Responsibility ?
Sometimes multiple steps
may be required before
approaching completion of
the task and forward in the
task to another person.
Often there is no needed
action before the task is
completed and the Complete
button can be clicked.
The cognitive state is that the
task has been completed but
while the Save button should
have been clicked the
Complete button is clicked.
Then task is marked as
completed and no follow up
is done.
This has happened
multiple times with
multiple users in multiple
offices.
Who is liable if a report
on a cancer is simply filed
away?
D I Y
• The do it yourself approach is very common
• Quote from an EMR programmer “I am too busy
programming to read journals”
– Even when understanding of the issues is lacking• Quote from several EMR vendors “We have lots of input from
our users”
– Advice that is often contradictory– Developers listen to the wrong users
Back Button
• Other doctors spoke of cluttered screens, unresponsive vendors and illogical displays. "It's a
huge safety issue," said Christine Sinsky, an internist in Dubuque, Iowa, whose practice implemented
electronic records six years ago. "I can't tell from the medical display whether a patient is receiving 4mg or 8mg of a certain drug. It took us two years to get a
back‐button on our browser."
Twelve Attributes of the Computer‐ based Patient Record
• The CPR supports data collection & storage with a defined vocabulary
• The CPR helps manage quality & cost of care
• The CPR is flexible & expandable to meet needs over time
Detmer & Simborg
CPR Computerized Patient Record
Twelve Attributes of the Computer‐ based Patient Record
• The CPR has a problem list with status of each problem
• The CPR encourages health status & functional level measurement to promote
outcomes assessment
• The CPR documents clinical rationale
Twelve Attributes of the Computer‐ based Patient Record
• The CPR can link to other clinical records over time
• The CPR system protects confidentiality comprehensively
• The CPR is accessible on a timely basis to authorized individuals
Twelve Attributes of the Computer‐ based Patient Record
• The CPR system allows selective retrieval and formatting
• The CPR system links to local & remote knowledge, literature, data‐bases, & systems
to aid decision making
• The CPR assists & guides clinical problem solving
Clinical Document Architecture ‐
Levels
“…
the concept of "levels" applied to CDA
means the degree to which a receiver can
expect to drive automated processes. A Level
One CDA sets no expectations beyond the
standard header metadata and human‐
readability for the body. A Level Two CDA
means that the body is in XML and that the
sections and sub‐sections are coded. A Level
Three CDA contains the same expectations as
Levels One and Two, plus it contains some
coded information within the sections.”
Source: http://www.hl7.org/documentcenter/public/faq/cda.cfm#_Toc104090430
Header
Metadata
Body
Narrative
Clinical
Statements
Level 1Level 2
Level 3
CCD Template Model for Problems Section
•
Templates
• Templates are use‐case, region‐, provider‐
or enterprise‐ specific.
• They almost always comprise multiple archetypes. • The beauty of templates is that they are flexible
‐
it is a
key feature. • Combine the stable archetypes in ways that achieve
various purposes. Constrain the stable archetypes down to make them more practical and usable for the local
clinicians, including making optional data points mandatory and binding data points to terminology
subsets appropriate for that given clinical setting.
Ordersets
• To be linked to clinical practice guidelines– ISO 18308, CEN 13940
• To be linked to reference sources– InfoButton
• InfoButton Access™• InfoButton Manager
• Orderset Schemas– Partners Healthcare– HL7 Ordersets– Structuring Order Sets for Interoperable Distribution
• Web‐based order entry– Trillium Ordersets
in Ontario Open Source Order Sets OSOS
Order Sets and Evidence Based Medicine Vanderbilt
• Order sets have been used to make evidence‐based guidelines actionable
at the point of care with evidence of improved outcomes. In order to
understand the impact evidence‐based order sets might have on patients
and providers at Vanderbilt, it is important to understand current and
past use of order sets. This study examined ordering patterns over a 6‐
year period and results are reported.
• AMIA Annu Symp Proc. 2006 ; :1108
• Vanderbilt University, Eskind Biomedical Library, Room 432, Nashville, TN
37232‐8340, USA.
• John Starmer, Lemuel R Waitman
CPOE & Ordersets
• HL7 Ordersets• HL7 Templates
• openEHR archetypes• Link reference information to Orderset
• User interface issues• Link to local practice patterns• Display of previous results
Population Health
• System use of data– CIHI Primary Health Care
Indicators• Population Based Funding• Chronic Disease Management
• GPHIN
International multilingual
surveillance of newspapers and radio• Vaccinations
• Broadcast messages to target populations
• Feedback to Providers– Local bacterial resistance
patterns– Success in achieving
treatment targets– Frequency of orders &
referrals
User Interface
• The interface capabilities depend on the underlying database
• Appropriate defaults and value sets to speed data entry• Summarization of Records• Graphs of data• Make it easy to do the right thing
– And hard to do the wrong thing• Linkages between different parts of the application
– This has been neglected in EMR related standards but is
vital to a high performance EMR• CUI Common User Interface in UK
Retention of Records
• This is a data preservation issue for:– Patients changing to a different provider– Doctors changing clinics– Clinics changing EMR vendors
• Original records may need to be kept up to 25 years after
the last visit– Does anyone have a computer that can read 8 inch floppy discs?
• Are the records transferred from one EMR to a different
one considered to be the legal record?– The courts usually want to see the records in the original form.– With an interactive record how do you recreate what was seen
five years earlier?
Content vs. Structure
Adapted from ©Mayo Clinic College of
Medicine 200744
Family History of Breast CancerFamily History of Heart DiseaseFamily History of Stroke
Terminological Model
Information Model
Equivalent Content
[adapted from Rossi‐Mori]
Breast CancerHeart DiseaseStroke
Family HistoryFamily History
What is the “fundus”?
• To an obstetrician –
• To an ophthalmologist –
• To a gastrointestinal endoscopist –
• To a surgeon doing a lap. cholecystectomy –Kent Spackman, Chief Terminologist IHTSDO
William Cole
On the surface this is a naming problem. A great deal of what goes on in the field of medical informatics is addressed to developing tools for dealing with various naming problems. Coding systems are tools for dealing with naming problems.Naming problems are often problems of communication between two concept systems. Before I know how to designate a concept I have to have some notion of what your conceptual space is.Hybrid expressive/selective interface
47
Donkey cart
48Some things never change
Provider’s View of Healthcare
Administrator’s View of Healthcare
Data Summarization
• Information Density• CLEF & Lifeline• Telemetry• Visual data analysis• CareComposition
– Problem list– Episode of care
• Different providers in different situations will want a different summary
Lifeline
The End Goal of Coding
3D Avatar for EMR
• 3D visualization linked to SNOMED
terminology
Terminologies
SNOMED
GP Term Lists
Reporting
Terminology
Reference
Terminology
Clinical
Interface
terminology
Natural
Language
ICPCICD
Acute onset of SOB last night, bloody sputum, admit to hospital
DRG
Words and groups
SOB
SNOMED
GP Term Lists
Reporting
Terminology
Reference
Terminology
Clinical
Interface
terminology
Natural
Language
ICPCICD
Acute onset of SOB last night, bloody sputum, admit to hospital
DRG
Breathlessness Hemoptysis
Dyspnea
Respiratory Signs
& Symptoms
Respiratory
Symptom
Bloody
Sputum
Pulmonary Edema
Problem List
“The ‘problem list’
then is not static in its composition, but is a dynamic ‘table of contents’
of the patient’s chart, which can be
updated at any time.”
Weed 1968
Problem List Issues
• master problem list vs. working problem list
• inactive, resolved or temporary problems
• exhaustive vs. selective• “lumpers”
vs “splitters”
• procedures included or not• To be called Problem, Issue, Concern ?
EMR designed to Corrupt the Database
Physician Resistance
• Systems need to be reliable
• The system must not distract the physician from their prime function
• Collected data should not be lost when you switch to a different system
Reliability of the System
• Mission Critical
• Needs to work every day all day• Scheduler is most critical for office to
function
Expectation of Finding what you want
• Frustration of going through a series of menus to find that there is no data there
– “I just wasted another 20 seconds!”• Going around in circles looking for what you
want
Problem of distractions and interruptions
• Need to keep the user oriented– Clear indication of who the patient is on the
screen
– Clear indication of when actions are completed
Prescriptions
Where is Waldo for Prescriptions
Medication errors are 3 times higher with computers than paper
eGFR Table
eGFR Drop
1
eGFR Drop
2
Dramatic Decline or Not?
Lab & Med Graph
Hemoglobin
Lab display Comparison
User Interface
• Critical to manage workflow• Should be a step ahead of the user• Should minimize cognitive load• Should bring in data from other parts of the
EMR without the user having to ask for it• CUI UK & Microsoft
– http://www.cui.nhs.uk/Pages/NHSCommonUserIn terface.aspx
Requires Silverlight
– http://www.mscui.net/
Requires Silverlight
Prescribing by Indication
Search for med by part of name
CUI Prescribing
• Place to see the indication• Brilliant use of “Group by”
and “Level of
detail”
• Would question the wide separation of the start and end dates
CUI Graphs
CUI Graphing Controls
1 Allow the user to
change the size of the
vertical axis
2 Horizontal Slider for
Period (time window)
3 Have side panel to
show visit note or
reports as the date
cursor goes by.
1
23
CUI Graphs Video
• Multiple user selectable options
• Use of ‘sliders’• Could be improved by
having resizable sliders• Filters to select
multiple patients• Select an event and
center on the event for the time scale
Graphing
• <
and >
effect how EMRs handle lab results– The result instead of being read as a number is
treated as text. The result might not be graphed.– TSH <0.01 Platelets <1 INR >10– EMR vendors do not feel that they can alter a
reported result – Could drop the < and >, do that and lower or raise
the resulting number– Could change or label the display as being altered
SNOMED Working Group
SNOMED Primary Care WG
Canada Health Infoway iEHR Team
Wonca International Classification Committee
Small group
AMIA
Non Computer Related Healthcare Problems
• Hundreds of deaths due to connecting wrong tubes
– feeding tubes mixed up with IV tubes, …
• 10% of temperatures recorded in hospital are wrong
• Chemotherapy meant for IV injected into epidural
• Wrong side surgery
How Would Natural Language Processing deal with these entries found in a paper chart.
• Patient has chest pain if she lies on her left side for over a year
• The skin was moist and dry
• Patient was alert and unresponsive• Patient refused autopsy• Patient has 2 teenage children, but no other
abnormalities
Need for Executive support
• Need executive leadership, commitment and protection of
human resources
• A Medical Association exec said that working on standards is
of lesser interest than working on hospital bylaws.
• It is not so much ‘physicians’
resistance’
but rather fear of
changing legacy systems
– On the verge of rolling out a province wide ePrescribing application the government decided to put it off for
another 3 years.
Foundation of the EHR
• Terminology ‐‐‐
SNOMED
• User Interface ‐‐‐
CUI, direct user manipulation
• Lab results ‐‐‐
delivered electronically using LOINC which is being harmonized with SNOMED
• Drug reference using SNOMED for clinical concepts
• Templates for data entry and display
• Data tables rather than free text
Suggestions for Accelerating EMR/EHR Development
• Have collaborative and cooperative meetings with the
membership of the group sustained over time• Include providers
– Need to have naïve users as well as power users– Naïve users may be less tolerant of poorly designed applications– Power users understand the nuances and requirements for high
performance applications
• Include developers– Developers need to understand the requirements– Developers need to know what is idiosyncratic and what is good
practice
• Include payers
End
• You cross the river by feeling the rocks
• Thank you for the platform to share my views of where we have been and where we are
going