Lists
Lists
subjective factors
difficult to model all of healthcare
difficult due to incomplete, imprecise, vague, inconsistent and uncertain information
Humans can adapt to this dynamic and vague information but computers can not
Why Health IT Fails Sometimes?
Inadequate time
Inadequate time
Inadequate expertise and workforce
Inadequate cost and return on investment data
High cost to adopt
Change in workflow
Privacy concerns
Legal issues
Behavioral change
Informatics Use in Healthcare
Patient portals
Electronic prescriptions
Voice-to-text translation
Reporting
Microcomputer
Minicomputer
Personal computer (PC) (Desktop)
Supercomputer: mainframe enterprise level
Laptop
Server: robust in terms of speed and memory
Mobile (smartphone ,tablet)
RESTful Operations
SOAP
WSDL
UDDI
The OSI Model Layers
Application
Presentation
Session
Transport
Network
Data link
Physical
Topic 3
Why do we need EHRs? (benefits, advantages)
Knowledge support
Calculators
Flow charts and graphs
Order sets
Reminders
Differential diagnosis
Lab and Imaging decision support
Public health alerts
eRx Benefits
Alert fatigue
wrong drug or wrong dose
issues at the pharmacist’s end
Still not clear how many adverse drug events are prevented with eRx
EHR Challenges (barriers, difficulties)
Financial
Physician resistance
Loss of productivity
EHR and Meaningful Use Challenges
Workflow changes
Reduced physician-patient interaction
Usability issues
Integration with other systems
Lack of interoperability
Privacy concerns
Legal Inadequate proof of benefit
Patient safety and unintended consequences
Clinicians had to: (according to HITECH ACT)
(1) be eligible
(2) register for reimbursement
(3) use a certified HER
(4) demonstrate and prove Meaningful Use
(5) receive reimbursement
EHR Steps
Develop an office strategy
Do Research
List features
Analyze and re-engineer workflow
Use project management tools
Choose client versus ASP model
Practice management system needs
Survey your hardware and network needs
Develop a vendor strategy
Select a vendor
Develop a paper to EHR conversion strategy
Training
Implementation
Topic 4
** Levels of interoperability
• Level 1 – no interoperability
• Level 2 – machine-transportable (structural)
• Level 3 – machine-organizable (syntactic)
• Level 4 – machine-interpretable (semantic)
Types of Standards
• Identifier standards
o Patient Identifiers
o Other Identifiers (National Provider Identifier (NPI), Employer Identifier Number
(EIN))
• Transaction standards
• Messaging standards
• Imaging standards
• Terminology standards
Patient identifier key attributes
• Unique – only one person has an identifier
• Non-disclosing – discloses no personal information
• Permanent – will never be re-used
• Ubiquitous – everyone has one
• Canonical – each person has only one
• Invariable – will not change over time
Major transactions in 5010 (ASC X12)
• Health claims and equivalent encounter information
• Enrollment and disenrollment in a health plan
• Eligibility for a health plan
• Health care payment and remittance advice
• Health plan premium payments
• Health claim status
Elements of the message (Messaging Standards)
• Entity – things in world
• Role – capability or capacity
• Participation – role in context of an act
• Act – clinical or administrative definitions
• Act relationship – links between acts
Types of resources in FHIR
• Clinical: The content of a clinical record
• Identification: Supporting entities involved in the care process
• Workflow: Manage the healthcare process
• Financial: Resources that support the billing and payment parts of FHIR
• Conformance: Resources use to manage specification, development and testing of FHIR
solutions
• Infrastructure: General functionality, and resources for internal FHIR requirements
** Interoperability Levels
Foundational
Syntactic
Semantic
Shared Healthcare Data
Clinical results
Images
Documents
Clinical summaries
Financial information
Medication data
Performance data
Case management
Public health data
Referral management
HIO Functions
Results delivery
Quality reporting
Connectivity with EHRs Results distribution
Clinical documentation
Electronic health record (EHR) hosting
Alerts to clinicians
Assist data loads into EHRs
Electronic prescribing
EHR interfaces
Health summaries
Drug-drug alerts
Electronic referral processing
Drug-allergy alerts Consultation/referrals
Drug-food allergy alerts Credentialing Billing
HIO Facts
• Can be centralized or decentralized (federated)
• Can be for profit or not-for-profit
• Can be government, private or community based
HIE Barriers