Response Requested - OHIE Client Registry Community

Hello all. OHIE Client Registry Community would like to thank you for your interest and involvement over the past year. As we begin a new year we want to take some time to reflect on our previous accomplishments and plan for our future. On a recent OHIE
CR Community call, May 15, the participant completed an After-Action Review. The notes and a recording of this meeting can be found using this

link
. We understand that not all community members can join our calls and want to ensure we provide an opportunity for wide-spread feedback. Below you will find the notes to from the After-Action Review. We would ask each of you to take 5-10 minutes to
review and provide additional content in each area. We will then use this to develop our Road Map for the next 12-18 months.

What is an After-Action Review (AAR)? An AAR allows a group of people to reflect on what they accomplished in a time period, identify if the accomplishments met expectations, and identify future tasks.

How can you participate? Please review the notes below, hit ‘reply’ on this email, add your input to each of the sections below, and send.

**OHIE Client Registry After-Action Review: **

What did you think would happen:

  • we would have two fully tested CR tools ready for OHIE
    release V1

  • continuous broad organizational input on CR process within
    OHIE

  • substantial amount of perf testing with OEMPI

  • clear performance test (interoperality standpoint)

  • clear specifications as to what is a CR with OHIE

  • greater involvement from Sysnet and OP, continued engagement

  • end Y1 with two tested tools

  • community would grow/evolve as a community

  • learn more about MEDIC CR

What actually happened:

  • the community group > membership/involvement has decreased

  • added scope with PDQm

  • able to get involvement with MEDIC CR

  • successfully run CR workflows (integration) on two tools

  • MEDIC CR passed IHE testing

  • save patient/query patient (patient level data )
    workflows

  • moving V3 forward of OpenEMPI

  • CR implementation guide V1 released

  • bug fixes within OpenEMPI

  • MCPHD has implemented OpenEMPI

  • deployed MEDIC CR in Tanzania

  • OpenHIE CR Release 1.0 is complete

  • Rwanda implementation has continued

  • CR Community provided guidance in Philippines

  • learned
    a little about MEDIC-CR

What can we do next:

  • update impletmentation guide (post-testing)

  • focus on increasing community involvement (right people
    at the table)

  • greater understanding
    of MEDIC CR (understanding perf & functional
    capabilities, etc.)

  • look into PIXm
    profile, start to profile that.

  • Integrate PDQm
    with the IO layer, formal work

  • understanding of pros/cons of various profiles (inform
    our approaches to standards) Justin has done this
    for PDQ (http://ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_PDQm.pdf
    , Appendix M)

  • performance/functional testing of OpenEMPI V3

  • IHE testing for OpenEMPI V3

Jennifer L Williams, MPH, PMP

Health Information Project Manager

Regenstrief Institute, Inc., Center for Biomedical Informatics

410 West 10th Street, Suite 2000

Indianapolis, IN 46202

Phone: 317.274.9239

Skype: jenniferlwilliams1

Email: craigjen@regenstrief.org

Confidentiality Notice: The contents of this message and any files transmitted with it
may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal
and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general
authorization for the release of medical or other information is not sufficient for this purpose. If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution
or use of this information by anyone other than the intended recipient is strictly prohibited.

Hello all. OHIE Client Registry Community would like to thank you for your interest and involvement over the past year. As we begin a new year we want to take some time to reflect on our previous accomplishments and plan for our future. On a recent OHIE CR Community call, May 15, the participant completed an After-Action Review. The notes and a recording of this meeting can be found using this link<https://wiki.ohie.org/display/resources/2015-05-15+Client+Registry+Community+Call>. We understand that not all community members can join our calls and want to ensure we provide an opportunity for wide-spread feedback. Below you will find the notes to from the After-Action Review. We would ask each of you to take 5-10 minutes to review and provide additional content in each area. We will then use this to develop our Road Map for the next 12-18 months.

What is an After-Action Review (AAR)? An AAR allows a group of people to reflect on what they accomplished in a time period, identify if the accomplishments met expectations, and identify future tasks.

How can you participate? Please review the notes below, hit ‘reply’ on this email, add your input to each of the sections below, and send.

OHIE Client Registry After-Action Review:
What did you think would happen:
§ we would have two fully tested CR tools ready for OHIE release V1
§ continuous broad organizational input on CR process within OHIE
§ substantial amount of perf testing with OEMPI
§ clear performance test (interoperality standpoint)
§ clear specifications as to what is a CR with OHIE
§ greater involvement from Sysnet and OP, continued engagement
§ end Y1 with two tested tools
§ community would grow/evolve as a community
§ learn more about MEDIC CR

§ Receive assistance and guidance during our OEMPI implementation

§ Have the opportunity to share our experiences from our OEMPI implementation
What actually happened:
§ the community group > membership/involvement has decreased
§ added scope with PDQm
§ able to get involvement with MEDIC CR
§ successfully run CR workflows (integration) on two tools
§ MEDIC CR passed IHE testing
§ save patient/query patient (patient level data) workflows
§ moving V3 forward of OpenEMPI
§ CR implementation guide V1 released
§ bug fixes within OpenEMPI
§ MCPHD has implemented OpenEMPI
§ deployed MEDIC CR in Tanzania
§ OpenHIE CR Release 1.0 is complete
§ Rwanda implementation has continued
§ CR Community provided guidance in Philippines
§ learned a little about MEDIC-CR

§ We received very helpful guidance during our OEMPI implementation
What can we do next:
§ update impletmentation guide (post-testing)
§ focus on increasing community involvement (right people at the table)
§ greater understanding of MEDIC CR (understanding perf & functional capabilities, etc.)
§ look into PIXm profile, start to profile that.
§ Integrate PDQm with the IO layer, formal work
§ understanding of pros/cons of various profiles (inform our approaches to standards) Justin has done this for PDQ (http://ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_PDQm.pdf , Appendix M)
§ performance/functional testing of OpenEMPI V3
§ IHE testing for OpenEMPI V3

§ Share some of our experiences implementing OEMPI in a County Health Department

§ Better understand the advantages/disadvantages of upgrading our OEMPI system

§ Understand the PIX/PDQ system better

§ Hear from others about their experiences implementing PIX/PDQ

Jennifer L Williams, MPH, PMP
Health Information Project Manager
Regenstrief Institute, Inc., Center for Biomedical Informatics
410 West 10th Street, Suite 2000
Indianapolis, IN 46202
Phone: 317.274.9239
Skype: jenniferlwilliams1
Email: craigjen@regenstrief.org<https://www.exchange.iu.edu/owa/UrlBlockedError.aspx>
Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose. If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited.

···

From: client-registry@googlegroups.com [mailto:client-registry@googlegroups.com] On Behalf Of Williams, Jennifer
Sent: Friday, June 05, 2015 2:16 PM
To: client-registry@googlegroups.com
Subject: Response Requested - OHIE Client Registry Community

--
You received this message because you are subscribed to the Google Groups "Client Registry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to client-registry+unsubscribe@googlegroups.com<mailto:client-registry+unsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
________________________________
This E-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the E-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this E-mail is strictly prohibited. If you have received this E-mail transmission in error, please reply to the sender so arrangements can be made for proper delivery, and then delete the message from your system.