1. NextGen Interoperability – Leading the Charge Presenter – David Venier DISCLAIMER: The views and opinions expressed in this presentation are those of the author and do not necessarily represent official policy or position of HIMSS.

2. Housekeeping Items  Answering your questions  Please hold all questions until the end of the presentation.  Cell phones  Please silence all electronic devices for the presentation.

3. Agenda  Key terminology and IHE profile support.  The current status of NextGen Interoperability  Supported features and technologies  What industry initiatives is NextGen participating in  What NextGen is doing to differentiate itself from its competition  Reduced total cost of ownership for clients  Hub based models for Meaningful Use interfaces.  Rapid deployment, install and update methodologies.  Q & A

4. Key Terms NextGen Supported IHE Profiles:  HPD+ Health Provider Directory  PIX/PDQ Patient demographic and cross reference queries  XDS Cross enterprise document sharing, NwHIN Exchange pull mechanism  XDR Cross enterprise document sharing for reliable exchange, NwHIN Direct push mechanism Other terms:  HIE Health Information Exchange  CCDA Consolidated Clinical Document Architecture  NwHIN Direct National standards where HIE infrastructure is not available. Uses SMTP (email) or XDR (web services)  HISP Health Information Service Provider, use for XDR /NwHIN Direct - 3 rd party (Not NG), acts as translator for SMTP to XDR (and vice versa)  SMTP Simple Mail Transfer Protocol – a.k.a. sending secure email  MDN Message Disposition Notification

5. Where are we today?

6. Interoperability Capabilities Functional capabilities for C-CDA Export:  Save a C-CDA to a local file Functional capabilities for C-CDA Exchange with an External Vendor:  Export a C-CDA to another a 3 rd party (HL7)  Receive a C-CDA from a 3 rd party (HL7) Functional capabilities for C-CDA Exchange with an HIE:  Query and retrieve a C-CDA from an HIE (XDS.b)  Provide and register a C-CDA with an HIE (XDS.b)  External system query and retrieve C-CDA from NextGen. (XDS.b) Functional capabilities for Direct Secure Messaging: (Referrals)  NextGen Share  NextGen’s free messaging service using our own HISP.  HISP is powered by Mirth Mail.  Direct message exchange with a 3 rd party HISP.  Online provider directory lookup (HPD+)  Message delivery confirmation (MDN)

7. Interoperability Capabilities - 2 Functional capabilities for other clinical information exchange:  Immunizations  Cancer Registry Reporting  Syndromic Surveillance  Orders and Results  EHR generated documentation.  NextGen open API’s for third party consumption.

8. What are we working on?

9. Interoperability Plans within the Industry New technologies, standards and workgroups:  Adoption of FHIR standards  Adoption of SMART technologies  Argonaut Project  Open API standards  Data Provenance  esMD - Electronic provider submission.  S&I Frameworks.  Blue Button Plus NextGen - ConfidentialNextGen EHR Connect

10. Interoperability Plans Outside of the Industry Reducing the total cost of ownership to clients:  Less client time spent on installation, updating and troubleshooting our current interoperability offerings.  Meaningful use interfaces a priority  Payer based initiatives (C-CDA exchange with payers)  RIS based initiatives (Radiology system integration) Implementation of a central interface routing solution:  Public Health Registries building on NextGen Share Technology  Immunizations  Syndromic Surveillance  Cancer Registry Reporting  Reference labs (future phase)

11. Centralized Public Health Routing Providers

12. Centralized Routing Benefits Centralized administration:  Reduced costs to NextGen and their clients  Automated deployment  Automated installation  Automated updates Centralized routing:  Manage a single point of connectivity to each registry  Onboard clients more rapidly  Ease of administration for development

13. Q&A