Chapter 8 Functional Needs Assessment 1 2007 Purpose

  • Slides: 10
Download presentation
Chapter 8 Functional Needs Assessment 1 © 2007

Chapter 8 Functional Needs Assessment 1 © 2007

Purpose • Describes key capabilities or application requirements for achieving the benefits of the

Purpose • Describes key capabilities or application requirements for achieving the benefits of the EHR as the organization has envisioned it • Process assessment – Focuses on specific tasks • Functional assessment – Focuses on overall purposes © 2007

Information Infrastructure • EHR system – Has many interrelationships with applications – Must be

Information Infrastructure • EHR system – Has many interrelationships with applications – Must be integrated with other components of information infrastructure • To achieve the desired output, – The right input must be provided – The right (analytical) processing tools and technology must be used • Internal and external uses and users must be accommodated © 2007

Functional Requirements Sources • Institute of Medicine – Original patient record study (1991, 1997)

Functional Requirements Sources • Institute of Medicine – Original patient record study (1991, 1997) – Key capabilities (2003) • HL 7 EHR System Functional Model (FM) (2007) • CCHIT EHR Certification Criteria (2006–present) © 2007

IOM Key Capabilities • EHR System includes: – Longitudinal collection of health information –

IOM Key Capabilities • EHR System includes: – Longitudinal collection of health information – Immediate access to information by authorized users – Knowledge and decision support for improved patient safety and quality of care – Support efficient healthcare delivery processes • This work was contributed to HL 7 development of EHR System © 2007

Health Level 7 • HL 7 EHR System Functional Model – Draft Standard for

Health Level 7 • HL 7 EHR System Functional Model – Draft Standard for Trial Use (DSTU) 2004 – Standard is visionary and voluntary – Final, ANSI accredited standard 2007 © 2007

CCHIT • Certification Commission on Health Information Technology – 2004: President’s call for HIT

CCHIT • Certification Commission on Health Information Technology – 2004: President’s call for HIT – Created Office of the National Coordinator for Health Information Technology (ONC) – July 2004: Framework of Strategic Action • August 2006: Executive Order establishes Recognized Certification Body (RCB) designation and designates CCHIT as first RCB © 2007

Why Functional Needs Assessment? • Each organization needs to define its own requirements –

Why Functional Needs Assessment? • Each organization needs to define its own requirements – Different vantage point – Different needs – Vendors have different approaches – Other elements of product selection © 2007

Identifying Functional Requirements • • Utilize resources (e. g. , IOM, HL 7, CCHIT)

Identifying Functional Requirements • • Utilize resources (e. g. , IOM, HL 7, CCHIT) Survey users Create use cases Verify user requirements © 2007

Conclusion • Because the EHR is not a single product, but a system of

Conclusion • Because the EHR is not a single product, but a system of applications integrated with appropriate technology that supports analytical tools to create information that contributes to improvement of health care, • Understanding the information infrastructure and thoroughly understanding and specifying functional needs ensures benefits realization © 2007