Open Source Update. OSEHRA Conference October 18, 2012 Office of Health Information/Health Systems-Christine Rhodes

Size: px

Start display at page:

Download "Open Source Update. OSEHRA Conference October 18, 2012 Office of Health Information/Health Systems-Christine Rhodes"

Vivien James
8 years ago
Views:

1 Open Source Update OSEHRA Conference October 18, 2012 Office of Health Information/Health Systems-Christine Rhodes September 12, 2012

2 Agenda Open Source and how it works Standardization Gold Disk Activities Impact of Standardization on Medical Centers Waiver Process Applications for Increment 1 VHA POC and Communication for Increment 1 2

3 How Does Open Source Work? Enterprise Enterprise Community Enterprise Community Enterprise Enterprise VA National Enterprise Development Enterprise VA Local Enterprise Development VistA Open Source Community Certification OSEHRA Certified Repository VA s Gold Disk Enterprise Enterprise Innovations Standardization Contribution Voluntary Pull Push VA Medical Center 9

Standardization Depends On Type National Protected * Accounts Receivable Bar Code Medication Administration Blood Bank Computerized Patient Record System (CPRS) Order Entry Modules Fee Basis Health

4 Standardization Depends On Type National Protected * Accounts Receivable Bar Code Medication Administration Blood Bank Computerized Patient Record System (CPRS) Order Entry Modules Fee Basis Health Level Seven (HL7) Integrated Funds Distribution, Control Point Activity, Accounting and Procurement Package (IFCAP) Integrated Billing Kernel Personnel and Accounting Integrated Data (PAID) Time and Attendance Remote Procedure Call (RPC) Broker VA FileMan VistA Data Extraction Framework (VDEF) VistA Imaging VistALink *VHA Directives and National Protected National Non- Protected Local All other Nationally developed and/or supported applications 4

5 Impact of Standardization on Medical Centers National Protected A Local B A. Local that modifies any National Protected WILL NOT BE ALLOWED! B. Local that does not modify any National WILL BE ALLOWED! National Non- Protected C. Local that modifies any National Non-Protected WILL REQUIRE A WAIVER! 5

6 Waiver Process Local IT will assess routines SMEs will be engaged to determine continued need for functional enhancement If functionality must be retained Local IT and SMEs will submit waiver request Waiver Committee will review and approve as appropriate Permanent Waivers Temporary Waivers Disapproval where alternatives exist Local site will be allowed to reinstall functional enhancement when waiver is approved Site may be asked to submit product to OSEHRA for certification and possible VA adoption as part of the National Waivers will not expire simply because there are not enough funds for VA to adopt as part of the National **DO NO HARM 6

7 Waiver Committee OIT Product Development Maureen Hoye OIT Product Support Vanessa Davis OIT Service Delivery & Engineering Eric Raffin VHA Program Office Christine Rhodes Doug Rosendale Marcia Insley Regional Application Service Line Managers Michael Fournier VHA Field Jason Atkins Brad Watts Waiver Committee OIT Architecture Strategy & Design Paul Tibbits 7

8 Gold Disk Standardization Increment 1 Modules/Applications Technical RPC Broker Electronic Signature Help Processer Web Services Client VistA Link Customer Facing Wounded Injured and Ill Warrior MRSA Initiative Report Care Management Generic Code Sheet Unwinder SAGG Project Capacity Management - RUM Capacity Management Tools 8

9 VHA National POCs for Increment 1 Customer Facing Apps Customer Facing VHA Program VHA POC Wounded Injured and Ill Warrior CBO Lynne Harbin MRSA Initiative Report PCS Rajiv Jain Gary Roselle Care Management OIA ONS Gail Graham Murielle Beene Pam Pickett Cathy Rick Christine Engstrom Generic Code Sheet CBO John Derderian *Inform VHA POCs and Local SMEs 9

10 Questions? 10

Department of Veterans Affairs VA DIRECTIVE 6402

Department of Veterans Affairs VA DIRECTIVE 6402 Washington, DC 20420 Transmittal Sheet August 28, 2013 MODIFICATIONS TO STANDARDIZED NATIONAL SOFTWARE 1. REASON FOR ISSUE. To set forth policies and responsibilities