<div dir="auto">We standards geeks have tried to enable this. The best example is in FHIR with a universal​ tag element available for this. Making that element available for patients to adjust is a operational responsibility.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mar 25, 2017 2:12 PM, "Aaron Seib" <<a href="mailto:aaron.seib@nate-trust.org" target="_blank">aaron.seib@nate-trust.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div class="m_6680531488399435593WordSection1"><p class="MsoNormal">Thanks John – and to build on your statement about the service getting “…sensitive topics from a Healthcare organization, or might get them from the Patient; possibly both.”<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">I would add that experience has shown that adoption by Provider Organizations without an Authoritative list of what is sensitive in relation to a specific regulatory set of conditions (think of a HIPAA transaction for Treatment Purposes) has been hard to engender.  My perception is that the law has given no agency the authority to constrain liability (protect the Provider Organization that subscribes to a list of codes representing sensitive topics when that list is defective either sharing too much or sharing too little) for the Provider Organizations that use sanctioned LOVs and basically anything that has been published to date is “use at your own risk”.<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">That said – if we can figure out how to properly capture and persist the sensitivity tags of the consumer my perception is that the discloser who does so is not liable.  Of course this relies on the consumer being able to tag things themselves and have the literacy to do so without inadvertent consequences (their failing to recognize that a Prescription they didn’t mark as sensitive essentially tells literate users that they have a specific condition that the consumer didn’t want to disclose).  <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I am not advocating that LOVs that help people set their preferences don’t have value.  I am asserting that such lists alone are insufficient and for their intended purpose.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Aaron  <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Aaron Seib, CEO<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">@CaptBlueButton <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> (o) <a href="tel:(301)%20540-2311" value="+13015402311" target="_blank">301-540-2311</a><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">(m) <a href="tel:(301)%20326-6843" value="+13013266843" target="_blank">301-326-6843</a><u></u><u></u></span></p><p class="MsoNormal"><a href="http://nate-trust.org" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d;text-decoration:none"><img border="0" width="205" height="48" id="m_6680531488399435593Picture_x0020_1" src="cid:image001.jpg@01D2A57A.30D033F0"></span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> John Moehrke [mailto:<a href="mailto:johnmoehrke@gmail.com" target="_blank">johnmoehrke@gmail.com</a>] <br><b>Sent:</b> Saturday, March 25, 2017 2:31 PM<br><b>To:</b> Aaron Seib<br><b>Cc:</b> Nancy Lush; HEART List<br><b>Subject:</b> Re: [Openid-specs-heart] HEART profiling for sensitive data<u></u><u></u></span></p><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">I agree with Aaron. However the problem is far bigger. The 'vectors' that are necessary to segment data for various purpose-of-use, and various roles; are many. That is to say sensitivity is not the only vector that is necessary. See <a href="https://healthcaresecprivacy.blogspot.com/2016/08/vectors-through-consent-to-control-big.html" target="_blank">https://<wbr>healthcaresecprivacy.blogspot.<wbr>com/2016/08/vectors-through-<wbr>consent-to-control-big.html</a> <u></u><u></u></p><div><div><p class="MsoNormal" style="line-height:13.85pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><u></u> <u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Data Identity - unique identifier of the data<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Folder Identity this data sits within<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">When was the data created<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">When was the data last updated<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Who authored the data<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Who verified the data<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Where was the data authored<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Availability, has the data been replaced or refuted<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">What kind of treating facility authored the data<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">What kind of care practice setting authored the data<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Predecessor data that was used in the authoring of this data (e.g. Order)<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Successor data that was created based on this data (e.g. Discharge Summary)<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Relationships to other data (e.g. folder identifier)<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Type of data object<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Type of clinical content implied by the data (e.g. Pregnant, Cancer, Addict)<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:3.0pt;margin-left:0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">etc<u></u><u></u></span></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I will note that the struggle to automatically determine what data might be sensitive from what data might be normal healthdata is the topic of a 'service' in a specification from HL7. That is to note that regardless of the technical details, one really needs a service to carry out that labeling task in an automated way. That service might get the list of sensitive topics from a Healthcare organization, or might get them from the Patient; possibly both. This isolates the labeling from the Access Control decision and enforcement. -- Look for HL7 Security Labeling Service<u></u><u></u></p></div></div></div><div><p class="MsoNormal"><br clear="all"><u></u><u></u></p><div><div><div><p class="MsoNormal">John Moehrke<br>Principal Engineering Architect: Standards - Interoperability, Privacy, and Security<br>CyberPrivacy – Enabling authorized communications while respecting Privacy<br>M <a href="tel:(920)%20564-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/<wbr>johnmoehrke</a><br><a href="https://healthcaresecprivacy.blogspot.com" target="_blank">https://healthcaresecprivacy.<wbr>blogspot.com</a><br>"Quis custodiet ipsos custodes?" ("Who watches the watchers?")<u></u><u></u></p></div></div></div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">On Sat, Mar 25, 2017 at 10:33 AM, Aaron Seib <<a href="mailto:aaron.seib@nate-trust.org" target="_blank">aaron.seib@nate-trust.org</a>> wrote:<u></u><u></u></p><div><div><p class="MsoNormal"><span style="color:#1f497d">Nancy</span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">At the end of the day I am of the opinion that relying on a coding scheme to identify what falls into a sensitive “category” and what doesn’t ends up being arbitrary and often dangerously imprecise.  </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">There is no way to apriori tag what any one consumer considers sensitive and what is considered sensitive by one consumer is not to another.  </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">In short – I am worried that if there isn’t a way for the consumer to mark what they are comfortable being shared any mechanism to make it “easy” for a data-holder to share with a third party while “respecting” the preferences of the consumer is insufficient and represents a legacy perspective.  </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">When we enable the consumer to tag their own data and constrain what is shared by the 3^rd parties that disclose data “on their behalf” we don’t fall into the trap of trying to create one size fits all LOVs that are inaccurate and only reflect the requirements of a regulatory requirement established decades in the past.</span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">We have to figure out how to enable the consumer to define what they want segmented if we are attempting to be respectful of the consumer’s preference.  We all know that these preferences change over time and the consumer should be able to update them.  </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">I believe data segmenation without the consumer’s ‘corrections’ leaves too many inaccuracies that inevitably result in disclosures not consistent with the individuals preferences.  </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">We can certainly create categories as an aid to building a consumer specific segmentation rules set but relying on pre-defined code sets to indicate what is sensitive (driven by legacy policies) will miss the mark.</span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">Aaron</span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><div><p class="MsoNormal"><span style="color:#1f497d">Aaron Seib, CEO</span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">@CaptBlueButton </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> (o) <a href="tel:(301)%20540-2311" target="_blank">301-540-2311</a></span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d">(m) <a href="tel:(301)%20326-6843" target="_blank">301-326-6843</a></span><u></u><u></u></p><p class="MsoNormal"><a href="http://nate-trust.org" target="_blank"><span style="color:#1f497d;text-decoration:none"><img border="0" width="205" height="48" id="m_6680531488399435593m_1865437489803582208_x005f_x0000_i1026" src="cid:image002.jpg@01D2A57A.30D033F0"></span></a><u></u><u></u></p></div><p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Openid-specs-heart [mailto:<a href="mailto:openid-specs-heart-bounces@lists.openid.net" target="_blank">openid-specs-heart-<wbr>bounces@lists.openid.net</a>] <b>On Behalf Of </b>Nancy Lush<br><b>Sent:</b> Friday, March 24, 2017 5:05 PM<br><b>To:</b> <a href="mailto:openid-specs-heart@lists.openid.net" target="_blank">openid-specs-heart@lists.<wbr>openid.net</a><br><b>Subject:</b> [Openid-specs-heart] HEART profiling for sensitive data</span><u></u><u></u></p></div></div><div><div><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal"><span style="color:#1f3864">Hello all,</span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f3864"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f3864">Attached is a document which includes background and suggestions for profiling sensitive data.  Comments welcome. </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f3864"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f3864">Thanks, and have a great weekend.</span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f3864"> </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f3864">-Nancy</span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f3864"> </span><u></u><u></u></p><table class="m_6680531488399435593MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse"><tr style="height:1.0pt"><td width="428" colspan="2" valign="top" style="width:256.7pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt"><div style="border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in"><p class="MsoNormal" style="line-height:115%"><span style="font-size:8.0pt;line-height:115%;color:#1f3864"> </span><u></u><u></u></p></div><p class="MsoNormal"><span style="font-size:8.0pt;color:#1f3864"> </span><u></u><u></u></p></td></tr><tr style="height:1.0pt"><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt;height:1.0pt"><p class="MsoNormal"><b><span style="font-size:10.0pt;color:#222a35">Nancy Lush          </span></b><u></u><u></u></p></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt"><p class="MsoNormal"><span style="font-size:10.0pt;color:#1f3864"><a href="mailto:nancy.lush@lgisoftware.com" target="_blank">nancy.lush@lgisoftware.com</a></span><u></u><u></u></p></td></tr><tr style="height:1.0pt"><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt;height:1.0pt"><p class="MsoNormal"><b><span style="font-size:10.0pt;color:#222a35">Lush Group, Inc</span></b><u></u><u></u></p></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt"><p class="MsoNormal"><span style="font-size:10.0pt;color:#1f3864">Office: <a href="tel:(401)%20423-9111" target="_blank">(401) 423-9111</a></span><u></u><u></u></p></td></tr><tr style="height:1.0pt"><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt;height:1.0pt"><p class="MsoNormal" style="line-height:115%"><span style="font-size:10.0pt;line-height:115%;color:#1f3864">28 Narragansett Ave</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10.0pt;color:#1f3864">PO Box 651</span><u></u><u></u></p></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt"><p class="MsoNormal" style="line-height:115%"><span style="font-size:10.0pt;line-height:115%;color:#1f3864"><a href="http://www.lgisoftware.com" target="_blank">www.lgisoftware.com</a> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10.0pt;color:#1f3864">Cell:<a href="tel:(401)%20965-9347" target="_blank">(401) 965-9347</a></span><u></u><u></u></p></td></tr><tr style="height:1.0pt"><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt;height:1.0pt"><p class="MsoNormal"><span style="font-size:10.0pt;color:#1f3864">Jamestown, RI 02835</span><u></u><u></u></p></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt;height:1.0pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"><p class="MsoNormal" style="line-height:115%"><span style="font-size:10.0pt;line-height:115%;color:#1f3864"> </span><u></u><u></u></p></td></tr><tr><td width="428" colspan="2" valign="top" style="width:256.7pt;padding:0in 5.75pt 0in 5.75pt"><p class="MsoNormal" style="line-height:115%"><span style="font-size:10.0pt;line-height:115%;color:#1f3864"><img border="0" width="153" height="50" id="m_6680531488399435593m_1865437489803582208Picture_x0020_1" src="cid:image003.gif@01D2A57A.30D033F0" alt="LGI_logo_small"></span><u></u><u></u></p></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="174" valign="top" style="width:1.45in;padding:0in 5.75pt 0in 5.75pt"></td><td width="254" valign="top" style="width:152.3pt;padding:0in 5.75pt 0in 5.75pt"></td></tr><tr><td width="428" colspan="2" valign="bottom" style="width:256.7pt;padding:0in 5.75pt 0in 5.75pt"></td></tr></table><p class="MsoNormal"><span style="color:#1f3864"> </span><u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p></div></div></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>______________________________<wbr>_________________<br>Openid-specs-heart mailing list<br><a href="mailto:Openid-specs-heart@lists.openid.net" target="_blank">Openid-specs-heart@lists.<wbr>openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" target="_blank">http://lists.openid.net/<wbr>mailman/listinfo/openid-specs-<wbr>heart</a><u></u><u></u></p></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></blockquote></div></div>