Panelists:

  • Wayne Kubick, Chief Technology Officer, HL7 (moderator)


  • Scott Iverson, Chief Operating Officer, Optum Clinical Solutions
  • Nijay Patel, Senior Vice President of Product, Redox
  • Adam Aaseby, Chief Information Officer and Assistant Director of the Division of Enterprise Technology Services, Washington State Health Care Authority
  • Tim Pletcher, Executive Director, Michigan Health Information Network Shared Services (MiHIN)


  • Joe Miller, Director of IS Strategy and Innovation, The AmeriHealth Caritas Family of Companies (in place of Andrea Gelzer, MD, Senior Vice President & Corporate Chief Medical Officer)


 

To participate in the discussion please post a comment below. Comments will be made anonymously, if you would like to be identified or contacted after the event is over, please include your name. Your registration email address can then be used to contact you after the event.

  • No labels

2 Comments

  1. Anonymous

    The Michigan ACRS provides a good focused use case of sharing basic info (Who, here, when, high level what) to drive "situational awareness" as Tim described it.  That awareness can then be used to drive more detailed queries for data.  We need to focus on prioritized foundation use cases like sharing of basic information and get that information flowing broadly via solutions like PCDH and ACRS and then we will have drivers for more advanced use cases including query and many others.  

    1. Anonymous

      Agree with getting the fundamentals - such as who, what, when, where, why (W5) - in place as foundational to full interoperability.  This is a key emphasis of the following standards:  ISO/HL7 10781 EHR System Functional Model Release 2, Record Infrastructure Section (2014) (http://www.hl7.org/implement/standards/product_brief.cfm?product_id=269), ISO 21089 Trusted End-to-End Information Flows (2017 version approved and in publication) and FHIR STU-3 Record Lifecycle Event Implementation Guide (http://hl7.org/fhir/ehrsrle/ehrsrle.html) including FHIR STU-3 AuditEvent (http://www.hl7.org/FHIR/ehrsrle/ehrsrle-auditevent.html) and FHIR STU-3 Provenance (http://www.hl7.org/FHIR/ehrsrle/ehrsrle-provenance.html) resources.  See also the FHIR STU-3 W5 Report (http://hl7.org/fhir/w5.html) and the FHIR STU-3 Implementer's Safety Checklist, Item #9 (http://hl7.org/fhir/safety.html).