<p dir="ltr">I have a hybrid opinion on this. I strongly believe the core profiles should remain under the auspices of the Openid foundation and hopefully inform other work but the FHIR based profiles probably do belong elsewhere for long term maintenance. Other API specific profiles may emerge over time </p>
<p dir="ltr">Given we are developing profiles and not Standards, IHE seems appropriate place to me.</p>
<p dir="ltr">Deb</p>
<div class="gmail_extra"><br><div class="gmail_quote">On Oct 4, 2016 9:55 PM, "Adrian Gropper" <<a href="mailto:agropper@healthurl.com">agropper@healthurl.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>With all due respect to John, and having worked with IHE extensively in the past, IHE is the main reason we're in the interoperability and data blocking predicament we're in today. The E in IHE stands for Enterprise and the focus of IHE is not the individual patient or even the physician, it's the business. I have lots of experience with other standards groups, including DICOM, that have been enablers of innovation. I have no experience with HL7. <br><br></div>From a patient perspective, HEART is broader than healthcare enterprises alone. Our perspective includes financial, social, research, and environmental services well beyond the "integrated delivery network" providers and vendors that dominate IHE. Identity and authorization management are not enterprise issues. They are people issues and we must keep HEART independent of the Integrated Healthcare Enterprise and under a broad, and consumer-oriented standards organization. <br><br></div>Adrian<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 4, 2016 at 10:47 AM, John Moehrke <span dir="ltr"><<a href="mailto:johnmoehrke@gmail.com" target="_blank">johnmoehrke@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">For all the various reasons you site; Specifically that the specifications HEART is developing are applicable beyond HL7, including DICOM and other. I would rather see this work happen in IHE. There is no need to create new standards, this is an effort of constraining and guiding the use of existing standards. IHE already fulfills this role. IHE has a very basic profile of OAuth 2.0; looking much like the HEART one. I would far prefer that profiling happen in IHE, than in HL7.<div><br></div><div>That said, I don't see any reason why the move needs to be urgently started. HL7, IHE, and DICOM are already pointing at HEART as the workgroup that is developing these guidance. This was done in recognition of the compiled expertise and focus of HEART. </div><div><br></div><div>The unknown right now is what Argonaut's plans for SMART are. SMART contains yet-another profile of OAuth. I understood that Argonaut would soon be proposing that specification be brought to HL7 FHIR. </div><div><br></div><div>As one of the HL7 Security WG co-chairs; I want a solution, but I want it maintained in a place that can best create and maintain it. I really don't think HL7 is the right organization.</div><div><br></div><div>What is the benefit of moving away from HEART? I originally expected that the specifications that HEART created could be transferred to IHE (or HL7) for long-term maintenance. No a creation effort, but a maintenance effort. But I was told that HEART is not intending on moving their specifications. I understood that HEART was going to exist forever.</div><div><br></div><div>I suspect the question is: How can we get HEART specifications tested and part of regular-testing under the organizationship of HL7 FHIR Connectathon (and IHE Connectathon)? If this is the question, then I think we have a different set of work. We don't need to move specifications, we need to create a bright-line from HL7 and IHE to HEART (today the line might not be as bright as it could be); and we then need to create test plans, test tools, test bench, and test procedures. These all can be re-used at IHE and HL7; so there is no need to specialize them.</div><div><br></div><div>John</div></div><div class="gmail_extra"><br clear="all"><div><div class="m_4251453630925545596m_-5628168173993733308gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">John Moehrke<br>Principal Engineering Architect: Standards - Interoperability, Privacy, and Security<br>CyberPrivacy – Enabling authorized communications while respecting Privacy<br>M <a href="tel:%2B1%20920-564-2067" value="+19205642067" target="_blank">+1 920-564-2067</a><br><a href="mailto:JohnMoehrke@gmail.com" target="_blank">JohnMoehrke@gmail.com</a><br><a href="https://www.linkedin.com/in/johnmoehrke" target="_blank">https://www.linkedin.com/in/jo<wbr>hnmoehrke</a><br><a href="https://healthcaresecprivacy.blogspot.com" target="_blank">https://healthcaresecprivacy.b<wbr>logspot.com</a><br>"Quis custodiet ipsos custodes?" ("Who watches the watchers?")</div></div></div>
<br><div class="gmail_quote"><div><div class="m_4251453630925545596h5">On Mon, Oct 3, 2016 at 11:26 AM, Glen Marshall [SRS] <span dir="ltr"><<a href="mailto:gfm@securityrs.com" target="_blank">gfm@securityrs.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_4251453630925545596h5">
<div link="blue" vlink="purple" lang="EN-US">
<div class="m_4251453630925545596m_-5628168173993733308m_-6827281199517455651WordSection1">
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif">Debbi,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif">I strongly urge that the HEART group plan and execute an entry into HL7 so it can influence the ongoing FHIR security and privacy work. We need a successful health IT beachhead. And we need
to establish incremental objectives, not a singular idealized goal. Gaining a testing thread in the HL7 FHIR Connectathon in January is a stretch benchmark objective.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif">There are some administrative hurdles in HL7, e.g., establishing an official project within the Security workgroup. To do that we need to write and present a business proposal. The HL7
Security workgroup can help us understand the tasks for it. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif">While HEART has uses in other standards-based health data communication, FHIR has the collective ear of many people. A successful effort in HL7 will then help lead to
<a href="http://www.x12.org/x12org/subcommittees/asc-x12-rosters.cfm?strSC=N" target="_blank">X12N</a> (insurance claims),
<a href="http://dicom.nema.org/" target="_blank">DICOM</a> (medical imaging), <a href="http://www.ncpdp.org/" target="_blank">
NCPDP</a> (pharmacy), <a href="https://www.cdisc.org/about/mission" target="_blank">CDISC</a> (clinical research),
<a href="http://www.iso.org/iso/iso_technical_committee?commid=54960" target="_blank">ISO/TC 215</a> (general health IT, including security),
<a href="http://www.pcori.org/" target="_blank">PCORi</a> (patient-centered outcomes), etc. <u></u>
<u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif">Your thoughts?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif">Glen<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Helvetica",sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Glen F. Marshall<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Consultant<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Security Risk Solutions, Inc.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">698 Fishermans Bend<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Mount Pleasant, SC 29464<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Tel: <a href="tel:%28610%29%20644-2452" value="+16106442452" target="_blank">(610) 644-2452</a>
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Mobile: <a href="tel:%28610%29%20613-3084" value="+16106133084" target="_blank">(610) 613-3084</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif"><a href="mailto:gfm@securityrs.com" target="_blank">gfm@securityrs.com</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif"><a href="http://www.securityrisksolutions.com/" target="_blank"><span style="color:#0563c1">www.SecurityRiskSolutions.com</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Openid-specs-heart [mailto:<a href="mailto:openid-specs-heart-bounces@lists.openid.net" target="_blank">openid-specs-heart-bou<wbr>nces@lists.openid.net</a>]
<b>On Behalf Of </b>Debbie Bucci<br>
<b>Sent:</b> Monday, October 3, 2016 06:56<br>
<b>To:</b> <a href="mailto:openid-specs-heart@lists.openid.net" target="_blank">openid-specs-heart@lists.openi<wbr>d.net</a><br>
<b>Subject:</b> [Openid-specs-heart] HEART Agenda 2016-10-3<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><strong><span style="font-family:"Times",serif">When: Monday 1 PM PST/4 PM EST</span></strong><u></u><u></u></p>
</div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Times",serif">Where: Gotomeeting – </span></b><span style="font-size:10.0pt;font-family:"Times",serif"><a href="https://global.gotomeeting.com/join/785234357" target="_blank">https://global.gotomeeting.c<wbr>om/join/785234357</a></span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Times",serif">US phone number</span></b><span style="font-size:10.0pt;font-family:"Times",serif">: <a href="tel:%2B1%20%28619%29%20550-0003" target="_blank"><span style="color:#0066cc">+1
(619) 550-0003</span></a>. Access Code 785-234-357</span><span style="font-size:10.0pt"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt"> </span></b><span style="font-size:10.0pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">Agenda :</span></b><span style="font-size:10.0pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Symbol">·</span> Recap decisions and/or clarifications made three weeks ago
<u></u><u></u></p>
<p class="MsoNormal"><span style="font-family:Symbol">·</span> UMA semantic profile
<br>
AOB<u></u><u></u></p>
</div>
</div>
</div>
<br></div></div>______________________________<wbr>_________________<br>
Openid-specs-heart mailing list<br>
<a href="mailto:Openid-specs-heart@lists.openid.net" target="_blank">Openid-specs-heart@lists.openi<wbr>d.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" rel="noreferrer" target="_blank">http://lists.openid.net/mailma<wbr>n/listinfo/openid-specs-heart</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
Openid-specs-heart mailing list<br>
<a href="mailto:Openid-specs-heart@lists.openid.net" target="_blank">Openid-specs-heart@lists.openi<wbr>d.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" rel="noreferrer" target="_blank">http://lists.openid.net/mailma<wbr>n/listinfo/openid-specs-heart</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="m_4251453630925545596gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br><div dir="ltr">Adrian Gropper MD<span style="font-size:11pt"></span><br><br><span style="font-family:"Arial",sans-serif;color:#1f497d">PROTECT YOUR FUTURE - RESTORE Health Privacy!</span><span style="font-family:"Arial",sans-serif;color:#1f497d"><br>HELP us fight for the right to control personal health data.</span><span style="font-family:"Arial",sans-serif;color:#1f497d"></span><span style="font-family:"Arial",sans-serif;color:#1f497d"><br>DONATE:
<a href="http://patientprivacyrights.org/donate-2/" target="_blank"><span style="color:#0563c1">http://patientprivacyrights.<wbr>org/donate-2/</span></a></span><span style="color:#1f497d"></span>
</div></div></div></div></div></div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
Openid-specs-heart mailing list<br>
<a href="mailto:Openid-specs-heart@lists.openid.net">Openid-specs-heart@lists.<wbr>openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" rel="noreferrer" target="_blank">http://lists.openid.net/<wbr>mailman/listinfo/openid-specs-<wbr>heart</a><br>
<br></blockquote></div></div>