PLEASE READ Re: OpenHIE Provider Registry Community Call: April 17 @ 10:00am EST: Agenda and Conference Bridge

Dear Provider Registry community,

I hope this finds everyone well and looking forward to another good conversation on the OpenHIE Provider Registry initiative. On today’s call, I would like to invite a further discussion of and answer any questions
on Derek Ritz’s request to support the emerging CSD (Care Services Discovery) profile currently being cultivated by the OpenHIE Community and evaluated by IHE (Integrating the Healthcare Enterprise -
http://www.ihe.net/). The CSD profile will be one of our guiding lights as work on the OpenHIE registries evolves and has particular applicability to our provider registry work.

Per their website, Integrating the Healthcare Enterprise (IHE) accelerates the adoption of health technologies by improving the exchange of information among healthcare systems. Its goal is to improve the quality,
efficiency and safety of clinical care by making relevant health information conveniently accessible.

IHE brings together users and developers of healthcare information technology (HIT) in an annually recurring four-step process:

Clinical and technical experts define critical use cases for information sharing.

Technical experts create detailed specifications for communication among systems to address these use cases, selecting and optimizing established standards.

Industry implements these specifications called IHE Profiles in HIT systems.

IHE tests vendors’ systems at carefully planned and supervised events called Connectathons.

IHE is committed to choosing and profiling underlying standards. They do not write standards, per se, but rather define how standards will be configured and used. In our experience so far, there is significant
flexibility in this “implementation guide” profile development approach.

A core guiding principle regarding the IHE profile definition is its implementability (which is a good thing). One of our challenges, however, is that “implementability” is generally defined in terms of “implementable
in the US”. Our active participation on the committee, so far, is helping expand the dialogue. This is also a good thing, and it is being appreciated by the group (if sometimes grudgingly).

Derek invites us as a community to become members of IHE and participate in the CSD process. It is free to become an IHE member. The principles of IHE’s governance, plus a link to the membership forms, are
found at http://www.ihe.net/governance/index.cfm IHE members vote on Profiles during the committee development process. It is one member, one vote; there is no “extra” voting weight given to a large organization
like GE or IBM vs. a small organization.

OpenHIE community partners who join IHE will need to identify a participant on the IT Infrastructure (ITI) committee in order to be active on CSD. That is the committee where our profile’s work is being done.
An IHE committee member is not eligible to vote unless they have attended two consecutive committee meetings (which can include the one where the vote is being called/cast). This incents participation. Voting is not done at every committee meeting; many are
“working” meetings on the various drafts that are under development. A WebEx connection is always made available; even at “face to face” meetings. We’ll help coordinate our community’s participation.

Our CSD Profile will be moving to a next important stage (Part 1 release for public comment) at the beginning of May during the face to face meetings in Chicago. It will move to public comment of both Parts 1
& 2, likely in late June or early July. Public comments will addressed and a final edit released for trial Implementation in mid-August or so. The first trial implementation of CSD will occur at the January 2014 Connectathon in Chicago, as long as we have
enough participants “signing up” to implement the various profile actors.

And that’s where our community comes in… If we can support the approval of the CSD profile, support it with the ‘central level’ Provider Registry described in our community goals, and also implement it into
our individual provider and consumer applications, we can demonstrate this interoperability in Chicago in January, 2014 and be recognized by an important international HIT coordination body that has a great deal of influence on implementers around the world.
This will elevate the Provider Registry and larger OpenHIE work well beyond our usual spheres.

So, next steps –

Visit
www.ihe.net
and learn more about Integrating the Healthcare Enterprise

Support your organization to become a member of IHE (for free) by reviewing the governance principles and filling out the forms at
http://www.ihe.net/governance/index.cfm

Join the IHE ITI committee and attend two consecutive committee meetings to become eligible to vote. We’ll help coordinate community participation.

Review the CSD profile and provide comments to Derek Ritz (derek.ritz@ecgroupinc.com ) either directly in email or more collaboratively through our community,
the IHE ITI technical Google group or the IHE HPD implementers Google group – we’ll provide a link to the Profile later today.

Engage in the public comment process, and start working as a community to move towards trial implementation

Thank you for taking the time to review all of this. Please share comments and questions with the OpenHIE Provider Registry Google group, and I look forward to discussing more in our call in a few hours. Derek,
if you would like to add any additional comments or amendments, please do.

Warmest regards,

···

From: Tiffany Jager
Sent: Tuesday, April 16, 2013 19:58
To: provider-registry@googlegroups.com; Global iHRIS Secretariat
Cc: Nancy Puttkammer (nputt@u.washington.edu); ‘robmcl@uw.edu’; florencesaburi@yahoo.com; Jørn Braa (jornbraa@gmail.com); Malik Jaffer; Miked4@uw.edu; kelly.keisling@nethope.org
Subject: OpenHIE Provider Registry Community Call: April 17 @ 10:00am EST: Agenda and Conference Bridge

Greetings All,

Please find below the agenda and conference bridge details for tomorrow’s
call. The below link will also take you to the google document version** . Upon joining the call, I would appreciate it if you would add your name and organization to the google document so that we are better able to keep
track of participants:**

https://docs.google.com/document/d/1fzyrsn6tHWkPvwpQH2b2tlqVOutPh67vb22UPuwV7T4/edit?usp=sharing

AGENDA:

  1. Review of Community goals

  2. Discussion on choosing profiles and standards

  3. User stories

  4. Next steps

CONFERENCE BRIDGE DETAILS:
OpenHIE Provider Registry Community Call
10:00 – 11:00 am EST/ 4:00-5:00 CAT
Passcode – 34048002#
The numbers to call are:
US: 800-220-9875
Norway: 800-142-85
Ireland: 800-625-002
Canada: 800-221-8656
South Africa 0-800-982-555
International (Not Toll-free) 1-302-709-8332
For additional toll free country numbers ** click
here**
.

Kind regards,

Tiffany

Tiffany Jager| Program Officer, Global Informatics

**IntraHealth International |**Because Health Workers Save Lives.

6340 Quadrangle Drive, Suite 200 | Chapel Hill, NC 27517

t. +1 (919) 313-9144 |
tjager@intrahealth.org

twitter |
facebook

Dear All,

There has been a recent update to the Care Services Discovery (CSD) profile dated April 20th. You can find the CSD profile here:
   ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr11-2013-2014/Technical_Cmte/WorkItems/CareServicesDiscovery/IHE_ITI_TF_Supplement_Care_Services_Discovery_13-04-20.docx
The CSD profile leverages the Healthcare Provider Registry (HPD) profile that we have discussed.

I would urge you to read over this CSD profile and suggest that we have a conversation on our next call to see if we, as a community, want to participate the CSD process.

Please note also that on the OpenHIE community call from Monday, Derek suggested that commenting on the CSD could be one mechanism to address issues related to potential overlaps in data sets between the Facility Registry and the Provider Registry.

Cheers.
-carl

···

On Apr 17, 2013, at 7:20 AM, Dykki Settle <dsettle@intrahealth.org<mailto:dsettle@intrahealth.org>> wrote:

Dear Provider Registry community,

I hope this finds everyone well and looking forward to another good conversation on the OpenHIE Provider Registry initiative. On today’s call, I would like to invite a further discussion of and answer any questions on Derek Ritz’s request to support the emerging CSD (Care Services Discovery) profile currently being cultivated by the OpenHIE Community and evaluated by IHE (Integrating the Healthcare Enterprise - http://www.ihe.net/). The CSD profile will be one of our guiding lights as work on the OpenHIE registries evolves and has particular applicability to our provider registry work.

Per their website, Integrating the Healthcare Enterprise (IHE) accelerates the adoption of health technologies by improving the exchange of information among healthcare systems. Its goal is to improve the quality, efficiency and safety of clinical care by making relevant health information conveniently accessible.

IHE brings together users and developers of healthcare information technology (HIT) in an annually recurring four-step process:
1. Clinical and technical experts define critical use cases for information sharing.
2. Technical experts create detailed specifications for communication among systems to address these use cases, selecting and optimizing established standards.
3. Industry implements these specifications called IHE Profiles in HIT systems.
4. IHE tests vendors’ systems at carefully planned and supervised events called Connectathons.

IHE is committed to choosing and profiling underlying standards. They do not write standards, per se, but rather define how standards will be configured and used. In our experience so far, there is significant flexibility in this “implementation guide” profile development approach.

A core guiding principle regarding the IHE profile definition is its implementability (which is a good thing). One of our challenges, however, is that “implementability” is generally defined in terms of “implementable in the US”. Our active participation on the committee, so far, is helping expand the dialogue. This is also a good thing, and it is being appreciated by the group (if sometimes grudgingly).

Derek invites us as a community to become members of IHE and participate in the CSD process. It is free to become an IHE member. The principles of IHE’s governance, plus a link to the membership forms, are found at http://www.ihe.net/governance/index.cfm IHE members vote on Profiles during the committee development process. It is one member, one vote; there is no “extra” voting weight given to a large organization like GE or IBM vs. a small organization.

OpenHIE community partners who join IHE will need to identify a participant on the IT Infrastructure (ITI) committee in order to be active on CSD. That is the committee where our profile’s work is being done. An IHE committee member is not eligible to vote unless they have attended two consecutive committee meetings (which can include the one where the vote is being called/cast). This incents participation. Voting is not done at every committee meeting; many are “working” meetings on the various drafts that are under development. A WebEx connection is always made available; even at “face to face” meetings. We’ll help coordinate our community’s participation.

Our CSD Profile will be moving to a next important stage (Part 1 release for public comment) at the beginning of May during the face to face meetings in Chicago. It will move to public comment of both Parts 1 & 2, likely in late June or early July. Public comments will addressed and a final edit released for trial Implementation in mid-August or so. The first trial implementation of CSD will occur at the January 2014 Connectathon in Chicago, as long as we have enough participants “signing up” to implement the various profile actors.

And that’s where our community comes in… If we can support the approval of the CSD profile, support it with the ‘central level’ Provider Registry described in our community goals, and also implement it into our individual provider and consumer applications, we can demonstrate this interoperability in Chicago in January, 2014 and be recognized by an important international HIT coordination body that has a great deal of influence on implementers around the world. This will elevate the Provider Registry and larger OpenHIE work well beyond our usual spheres.

So, next steps –
1. Visit www.ihe.net<http://www.ihe.net> and learn more about Integrating the Healthcare Enterprise
2. Support your organization to become a member of IHE (for free) by reviewing the governance principles and filling out the forms at http://www.ihe.net/governance/index.cfm
3. Join the IHE ITI committee and attend two consecutive committee meetings to become eligible to vote. We’ll help coordinate community participation.
4. Review the CSD profile and provide comments to Derek Ritz (derek.ritz@ecgroupinc.com<mailto:derek.ritz@ecgroupinc.com>) either directly in email or more collaboratively through our community, the IHE ITI technical Google group or the IHE HPD implementers Google group – we’ll provide a link to the Profile later today.
5. Engage in the public comment process, and start working as a community to move towards trial implementation

Thank you for taking the time to review all of this. Please share comments and questions with the OpenHIE Provider Registry Google group, and I look forward to discussing more in our call in a few hours. Derek, if you would like to add any additional comments or amendments, please do.

Warmest regards,
-
Dykki
+1.919.360.4011

From: Tiffany Jager
Sent: Tuesday, April 16, 2013 19:58
To: provider-registry@googlegroups.com<mailto:provider-registry@googlegroups.com>; Global iHRIS Secretariat
Cc: Nancy Puttkammer (nputt@u.washington.edu<mailto:nputt@u.washington.edu>); 'robmcl@uw.edu<mailto:robmcl@uw.edu>'; florencesaburi@yahoo.com<mailto:florencesaburi@yahoo.com>; Jørn Braa (jornbraa@gmail.com<mailto:jornbraa@gmail.com>); Malik Jaffer; Miked4@uw.edu<mailto:Miked4@uw.edu>; kelly.keisling@nethope.org<mailto:kelly.keisling@nethope.org>
Subject: OpenHIE Provider Registry Community Call: April 17 @ 10:00am EST: Agenda and Conference Bridge

Greetings All,

Please find below the agenda and conference bridge details for tomorrow’s call. The below link will also take you to the google document version. Upon joining the call, I would appreciate it if you would add your name and organization to the google document so that we are better able to keep track of participants:

https://docs.google.com/document/d/1fzyrsn6tHWkPvwpQH2b2tlqVOutPh67vb22UPuwV7T4/edit?usp=sharing

AGENDA:

1. Review of Community goals
2. Discussion on choosing profiles and standards
3. User stories
4. Next steps

CONFERENCE BRIDGE DETAILS:

OpenHIE Provider Registry Community Call
10:00 – 11:00 am EST/ 4:00-5:00 CAT

Passcode – 34048002#

The numbers to call are:

US: 800-220-9875
Norway: 800-142-85
Ireland: 800-625-002
Canada: 800-221-8656
South Africa 0-800-982-555
International (Not Toll-free) 1-302-709-8332
For additional toll free country numbers click here<https://openhie.atlassian.net/wiki/download/attachments/524314/Intl%20TF%20Numbers%20Oct%202012.pdf?version=1&modificationDate=1354043516340&api=v2>.

Kind regards,

Tiffany

Tiffany Jager | Program Officer, Global Informatics

IntraHealth International<http://www.intrahealth.org> | Because Health Workers Save Lives.
6340 Quadrangle Drive, Suite 200 | Chapel Hill, NC 27517
t. +1 (919) 313-9144 | tjager@intrahealth.org<mailto:%20tjager@intrahealth.org>

twitter<http://twitter.com/IntraHealth> | facebook<http://www.facebook.com/IntraHealth>