GE Healthcare. Meaningful Use 2014 Prep: Menu and Interfaces. Ray Bender, DPh, PMP Product Manager January 16, 2014

Transcription

1 GE Healthcare Meaningful Use 2014 Prep: Menu and Interfaces Ray Bender, DPh, PMP Product Manager January 16, 2014 Revised 20Jan2014

2 2014 General Electric Company All rights reserved. This does not constitute a representation or warranty or documentation regarding the product or service featured. All illustrations are provided as fictional examples only. Your product features and configuration may be different than those shown. Information contained herein is proprietary to GE. No part of this publication may be reproduced for any purpose without written permission of GE. DESCRIPTIONS OF FUTURE FUNCTIONALITY REFLECT CURRENT PRODUCT DIRECTION, ARE FOR INFORMATIONAL PURPOSES ONLY AND DO NOT CONSTITUTE A COMMITMENT TO PROVIDE SPECIFIC FUNCTIONALITY. TIMING AND AVAILABILITY REMAIN AT GE S DISCRETION AND ARE SUBJECT TO CHANGE AND APPLICABLE REGULATORY CLEARANCE. Customer is responsible for understanding and meeting the requirements of achieving meaningful use through use of HHS certified EHR technology and associated standards. Customer is responsible for understanding applicable GE documentation regarding Meaningful Use functionality and reporting specifications, and for using that information to confirm the accuracy of meaningful use attestation. Customer is responsible for ensuring an accurate attestation is made and GE does not guarantee incentive payments. Use of the product does not ensure customer will be eligible to receive payments. * GE, the GE Monogram, Centricity and imagination at work are trademarks of General Electric Company. General Electric Company, by and through its GE Healthcare division. Centricity Practice Solution v12.0 and Centricity EMR v9.8 are certified ONC 2014 Edition compliant complete and modular EHRs. For additional certification and transparency information, visit

3 Agenda Stage 2 Menu measures 1-6 Measure Workflow Application Changes/Configuration Exclusions and References Interfaces Q&A

4 Stage 2 Menu Measures 1-6

5 MENU Measure 1 Syndromic Surveillance (Public Health) Changed in Stage 2: (Measurement changed) Measure Attestation to successful ongoing submission of syndromic Surveillance data to a Public Health agency for the entire reporting period. (Stage 1 only required one successful test). Workflow Information is entered into an Urgent Care form and when the document is signed, data is sent to a configured public health agency. The Urgent Care encounter form will collect the required values/codes. Chief Complaint, Vitals, Triage Notes, Diagnosis, Procedures, Disposition The Public Health Registry subscription was certified with the QIE interface engine; sending HL7 ADT 04 and ADT 03 (Admit/Discharge) messages to the registry. The GE-supported mechanism is QIE. However, other transport mechanisms can be used. Product and Service Used to Meet Criteria: CPS 12/CEMR 9.8, QIE 2.0, Interface configuration

6 MENU Measure 1 Syndromic Surveillance (Public Health) Urgent Care Management encounter form

7 MENU Measure 1 Syndromic Surveillance (Public Health) Configuration Import and enable Subscription in Administration In Administration go to Interoperability > Configuration. The new permission Common Event Model > ACCESS Subscriptions Modification is required to manage subscriptions for MU interfaces. For custom forms, the following OBS terms are used to collect the required data: TEMP(DEG C) - HDID UCUM code is "Cel" - degree Celsius TEMPERATURE - HDID UCUM Code is "[degf]" - degree Fahrenheit O2SAT(OXIM) - HDID 2173 TRIAGESUBJHX HDID TRIAGEOBJCHX DISCHDISP CHIEF CMPLNT HDID 1018 More discussion on Subscriptions later in this presentation

8 MENU Measure 1 Syndromic Surveillance (Public Health) Exclusions 1 The EP is not in a category of providers that collect ambulatory syndromic surveillance information on their patients during the EHR reporting period; 2 The EP operates in a jurisdiction for which no public health agency is capable of receiving electronic syndromic surveillance data in the specific standards required by CEHRT at the start of their EHR reporting period; 3 The EP operates in a jurisdiction where no public health agency provides information timely on capability to receive syndromic surveillance data; or 4 The EP operates in a jurisdiction for which no public health agency that is capable of accepting the specific standards required by CEHRT at the start of their EHR reporting period can enroll additional EPs. References EHR Incentive Program Specification: Guidance/Legislation/EHRIncentivePrograms/downloads/Stage2_EPMenu_1_SyndromicSurveillanceDataSub.pdf

9 MENU Measure 2 Electronic Notes New in Stage 2 Measure >30% of all unique patients with an office visit during the reporting period, have a note created, edited, and signed by the EP. The text of the electronic note must be text searchable. Workflow The application meets this new Stage 2 requirement (no changes other than reporting). All signed chart notes for a patient seen by the provider in the office, at least once during the reporting period, are counted. Configuration - N/A References EHR Incentive Program Specification: Guidance/Legislation/EHRIncentivePrograms/downloads/Stage2_EPMenu_2_ElectronicNotes.pdf Product and Service Used to Meet Criteria: CPS 12/CEMR 9.8

10 MENU Measure 3 Imaging Results New in Stage 2 Measure >10% of all scans and tests whose result is an image, ordered by the EP for patients seen during the reporting period, are incorporated into or accessible through CEHRT. Workflow The application currently has the ability to store and link to images; in this release support has been added for MU reporting. For reporting, the application checks for an Image Report document type, and increments the numerator if it has either an attachment or a link to an image on an external site. Product and Service Used to Meet Criteria: CPS 12/CEMR 9.8, Interface configuration in some cases

11 MENU Measure 3 Imaging Results Here the image is attached Image Report document type is counted if an attachment or external link is included

12 MENU Measure 3 Imaging Results Configuration Varies Exclusion Any EP who orders less than 100 tests whose result is an image during the EHR reporting period; or any EP who has no access to electronic imaging results at the start of the EHR reporting period. References EHR Incentive Program Specification: Guidance/Legislation/EHRIncentivePrograms/downloads/Stage2_EPMenu_3_ImagingResults.pdf

13 MENU Measure 4 Family History New in Stage 2 Measure >20% of all unique patients seen by the EP during the reporting period have family history recorded in SNOMED for at least one first-degree relative. Workflow The FH-SH-CCC form contains a patient's family and social history. When saved, data entered appears on the Family Hx Summary Alternate options are included for No Known Family History, No Known Relative, and Reviewed - No Changes Required Product and Service Used to Meet Criteria: CPS 12/CEMR 9.8

14 MENU Measure 4 Family History

15 MENU Measure 4 Family History Configuration Install the CCC-Basic package to use the FH-SH-CCC form Alternatively, custom content can be developed using new FHX MEL symbols (MEL_RELATIVES_FHX, MEL_LIST_FHX, MEL_LIST_FHX_AFTER, MEL_LIST_FHX_NEW, MEL_ADD_FHX, MEL_UPDATE_FHX, and MEL_REMOVE_FHX) Exclusion Any EP who has no office visits during the EHR reporting period. References EHR Incentive Program Specification: Guidance/Legislation/EHRIncentivePrograms/downloads/Stage2_EPMenu_4_FamilyHealthHistory.pdf

16 MENU Measure 5 Cancer Registry New in Stage 2 Measure Attestation to successful ongoing reporting of cancer cases to a public health central cancer registry, for the entire reporting period Workflow Not supported at this time Configuration N/A Product and Service Used to Meet Criteria: N/A

17 MENU Measure 5 Cancer Registry New in Stage 2 Exclusion The EP does not diagnose or directly treat cancer; The EP operates in a jurisdiction for which no public health agency is capable of receiving electronic cancer case information in the specific standards required for CEHRT at the beginning of their EHR reporting period; The EP operates in a jurisdiction where no PHA provides information timely on capability to receive electronic cancer case information; or The EP operates in a jurisdiction for which no public health agency that is capable of receiving electronic cancer case information in the specific standards required for CEHRT at the beginning of their EHR reporting period can enroll additional EPs. References EHR Incentive Program Specification: Guidance/Legislation/EHRIncentivePrograms/downloads/Stage2_EPMenu_5_ReportCancerCases.pdf

18 MENU Measure 6 Specialized Registry New in Stage 2 Measure Attestation to successful ongoing reporting of specific cases to a specialized registry, for the entire reporting period Workflow Varies Configuration N/A Product and Service Used to Meet Criteria: N/A

19 MENU Measure 6 Specialized Registry Exclusion The EP does not diagnose or directly treat any disease associated with a specialized registry sponsored by a national specialty society for which the EP is eligible, or the public health agencies in their jurisdiction; The EP operates in a jurisdiction for which no specialized registry sponsored by a public health agency or by a national specialty society for which the EP is eligible is capable of receiving electronic specific case information in the specific standards required by CEHRT at the beginning of their EHR reporting period; The EP operates in a jurisdiction where no public health agency or national specialty society for which the EP is eligible provides information timely on capability to receive information into their specialized registries; or The EP operates in a jurisdiction for which no specialized registry sponsored by a public health agency or by a national specialty society for which the EP is eligible that is capable of receiving electronic specific case information in the specific standards required by CEHRT at the beginning of their EHR reporting period can enroll additional EPs. References EHR Incentive Program Specification: Guidance/Legislation/EHRIncentivePrograms/downloads/Stage2_EPMenu_5_ReportCancerCases.pdf

20 Stage 2 Interfaces

21 Common Event Model (CEM) The events happening in the system (CPS/CEMR) will result in some database update or insert operations. These events are captured as event objects and queued in database table for processing. The Event Processor running picks up these event objects and disperses them into appropriate internal queues of Job Processors (Immediate or Scheduled) for further processing. The Job Processor picks up the event objects from its internal queue and calls the appropriate Payload Generator to create the appropriate message. The message created is sent to the configured external system, such as an interface engine, which in turn sends it to the final destination (for eg., Immunizations Registry). A second way of exporting messages is from Inquires module. A patient search query processing works in a similar way except that the export of messages does not happen based on the events happening in the system. Rather a patient search query determines the list of patients based on which the messages needs to be exported and sends to specific subscription 21 MU 2014 Prep: Menu & Interfaces January 16, 2014

22 CEM Subscription model Any implemented event in the system can be subscribed. Subscription allows you to extract data associated with the event. Available Subscriptions 1. Immunization - VXU 2. Syndromic ADT03 and ADT04 3. Data Portability - CCDA 4. Centricity Quality Reporting (CQR) CCDA 5. Centricity Quality Reporting (CQR) JSON Note: Inbound Laboratory interfaces do not use the subscription model LinkLogic will continue, without change, for HL messages The Qvera Interface Engine has been certified to convert HL messages to HL for receipt by LinkLogic; if HL is required Laboratory service providers are not required by MU to use HL , but may convert on their own Practices will need to use the version supported by their Lab Provider 22 MU 2014 Prep: Menu & Interfaces January 16, 2014

23 Enabling Subscription Available subscriptions can be imported into system using factory supplied configuration files. Individual subscription can be enabled separately. 23 MU 2014 Prep: Menu & Interfaces January 16, 2014

24 Common Event Model Diagram DB Events (persistent) Event Processor Internal Queue 1 (persistent) Job Processor 1 Immediate Outbound Queue 1 (persistent) IE Pulls Payload Generator 1 Internal Queue 2 (persistent) Job Processor 2 Scheduled Outbound Queue 2 (persistent) Interface Engine Payload Generator 2?? Subscription Services (persistent) CEM based on Java, JBoss, Camel Data Services

25 Centricity LIVE May 4 7, 2014 Denver, CO Visit gehealthcare.com/centricitylive for all the details and register now! Centricity* LIVE 2014 is GE Healthcare s IT User Meeting held in Denver, CO from May 4 th to the 7 th. It is an annual gathering of GE Healthcare customers, Centricity users, administrators and hospital executives coming together to share, learn and network. We look forward to seeing you in the Mile High City and working with you to take healthcare IT to new heights! *Trademark of General Electric Company. 25 GE Title or job number 1/22/2014

26 Thank you for joining us. Questions NOTE: We will send you an after this session with a link to the services portal, where you can download the slides and watch the recording.

27