1 / 10

Advanced Project Management for Behavioral Health Electronic Health Records (EHRs)

This module provides an in-depth review of system requirements for Behavioral Health EHRs. It covers infrastructure, practice management, clinical data, meaningful use, and assessing EHR capacities.

gleslie
Download Presentation

Advanced Project Management for Behavioral Health Electronic Health Records (EHRs)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Series 2: Project ManagementAdvanced Project Management for Behavioral Health Electronic Health Records (EHRs) From the CIHS Video Series “Ten Minutes at a Time” 9/2013

  2. Module 9: Identifying EHR System Requirements Overview • In depth review of “Systems Requirements Definition” and “Requirements Traceability Matrix” • 4 functional categories for identifying and assessing requirements • Tracking groups of requirements against the Requirements Matrix • Realistically and accurately evaluating EHR capacity to meet requirements

  3. Understanding “System Requirements” • Patient population • Drivers for business processes • Requirements for grants and contracts • State, Federal and certification requirements • Licensing requirements • Tools for managing daily tasks • Assessment, evaluation, treatment planning, progress notes • Managing standard patient documents (Living Wills) • Maintain current licensing and credentialing information • Ease of use • Support for managing workflows • Clear improvement in processes

  4. Four Functional Categories for Identifying EHR System Requirements • Infrastructure – see Module 6 on Information Technology Architecture; consider “transparent functionality” • Practice Management – includes scheduling functionality • Clinical Data – EHR should support evidence-based practices; billing for services • Meaningful Use – “Certified” does not mean “robust” in Meaningful Use functionality.

  5. Systems Analysis – System Requirements Definition • Examples available online • California Request for Information to behavioral health EHR businesses – can be used as a template http://www.dmh.ca.gov/Prop_63/MHSA/Technology/docs/EHR_Project/CA_BH-EHR_RFI_v10_091708.pdf (note- does NOT include Meaningful Use System Requirements) • Meaningful Use Electronic Standards and Specifications Stage 1: http://www.gpo.gov/fdsys/pkg/FR-2010-07-28/pdf/2010-17210.pdf Stage 2: http://regulations.vlex.com/vid/implementation-certification-396307770 • Requirements specific to Behavioral Health https://www.cchit.org/documents/18/158304/CCHIT+Certified+2011+Behavioral+Health+Criteria.pdf

  6. Assessing EHR Capacities- Describing Functionality • “Demonstrated existing functionality” • “Not demonstrated, will be available in the next version” (obtain date of release) • “Not demonstrated, can be added with minor modification (usually a configuration or the addition of a script or Web-based service)” • “Not demonstrated, customization possible” (obtain Level of Effort Estimate – how long, how much?) • “Not demonstrated, no possibility of customization”

  7. Systems Analysis –Requirements Traceability Matrix • Example and information available online • From NYS Office of Mental Health http://www.omh.ny.gov/omhweb/rfp/2011/emr/updates/20120305qa.pdf • From SlideShare • http://www.slideshare.net/sks2009/requirementstraceabilitymatrixsimple

  8. About Developing Use Case Scenarios • Developed in Business Process Analysis (look for Series 3 modules on this, coming January 2014) • Refines requirements identification to the workflow level • Taps into the expertise of the individuals meeting the requirements - they understand the nuances of the requirements • Results in Business Process Narrative - Collection of “Use Case Scenarios,” the individual business processes that staff engage in on a daily basis • Captures “As Is” state, used to develop “To Be” vision • Can be used to validate the final system configuration • http://www.himss.org/files/HIMSSorg/content/files/Code%20119%20-%20EHR%20Usability_Evaluation%20and%20Use%20Case%20Framework_AHRQ.pdf

  9. Summary • Identifying system requirements in advance is helpful to selecting an EHR and defending any choices that need to be made • Start with the existing requirements defined by various system drivers (funding sources, 3rd party payers, state and federal regulations, etc.) • Assign a numeric value to the requirement and track it to its source • Understand that no EHR will be able to meet all requirements • Therefore, it is essential to select an EHR based on its capacity to meet non-negotiable requirements • Confirm the status of the EHRs capacity to meet necessary requirements with EHR business principles before signing a contract • Track any assurances made about future functionality and obtain promises about future capability in writing in the final contract (Module 12)

  10. We Have Solutions for Integrating Primary and Behavioral Healthcare Contact CIHS for all types of primary and behavioral health care integration technical assistance and training needs 1701 K Street NW, Ste 400 Washington DC 20006 Web: www.integration.samhsa.gov Email: integration@thenationalcouncil.org Phone: 202-684-7457 Prepared and presented by Colleen O’Donnell, MSW, PMP, CHTS-IM for the Center for Integrated Health Solutions

More Related