[Openid-specs-heart] Draft HEART Meeting Notes 2017-04-03

[Eve Maler]

Hi Danny-- You can find all the profiles at this link:

https://openid.bitbucket.io/HEART/

The first three profiles are the "mechanical" (basic security/interop) ones:

Health Relationship Trust Profile for OAuth 2.0:
http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?modeAsFormat=html/ascii&url=https://bitbucket.org/openid/heart/raw/master/openid-heart-oauth2.xml

Health Relationship Trust Profile for OpenID Connect 1.0:
http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?modeAsFormat=html/ascii&url=https://bitbucket.org/openid/heart/raw/master/openid-heart-openid-connect.xml

Health Relationship Trust Profile for User-Managed Access 1.0:
http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?modeAsFormat=html/ascii&url=https://bitbucket.org/openid/heart/raw/master/openid-heart-uma.xml


*Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

On Sat, Apr 8, 2017 at 5:49 PM, Danny van Leeuwen <danny at health-hats.com>
wrote:

> Can someone please point me to the mechanical profiles. Is this the nine
> use cases here <https://bitbucket.org/openid/heart/wiki/Home>?
>
> Danny van Leeuwen, Opa, RN, MPH, CPHQ
> Health Hats
> 617-304-4681 <(617)%20304-4681> (c)
> www.health-hats.com (blog)
> @healthhats (Twitter)
> LinkedIn <https://www.linkedin.com/in/healthhatsdannyvl/>
>
> On Mon, Apr 3, 2017 at 4:24 PM, Sarah Squire <sarah at engageidentity.com>
> wrote:
>
>> Attending:
>>
>> Debbie Bucci
>>
>> Celestin Bitjonck
>>
>> David Batchelor
>>
>> Edmund Jay
>>
>> Jin Wen
>>
>> Justin Richer
>>
>> Nancy Lush
>>
>> Sarah Squire
>>
>> Thompson Boyd
>>
>> Debbie:
>>
>> Last week we reviewed Justin’s changes to the spec, and there was a
>> general consensus that the text that’s there is good enough and touches on
>> the right points. I think it’s time to wrap these profiles up and do
>> another round of implementer's drafts, this time for all five drafts so we
>> can open for comments at IIW.
>>
>> Justin:
>>
>> The specs themselves haven’t changed in the last few weeks. We need deep
>> reads and reviews from the group, not just the technical content, but the
>> editorial content as well.
>>
>> Debbie:
>>
>> So at that point we would scale meetings back to once or twice a month.
>> The hope is that the evolving work in the Moving Health Data Forward group
>> could dovetail with our work so that they could come talk to us as they
>> implement.
>>
>> Justin:
>>
>> Let’s dedicate next week’s call to a deep read of the mechanical profiles.
>>
>> Nancy:
>>
>> I like that we’re talking about sensitivity codes as an example, rather
>> than having it be normative.
>>
>> Justin:
>>
>> Well, even if it’s an example, we should point to some external list plus
>> a process to extend and define new ones. Do we want to use URIs? Or point
>> to an IANA registry? Or…?
>>
>> Nancy:
>>
>> Well, they are currently changing.
>>
>> Debbie:
>>
>> Nancy, didn’t you point to a couple of lists?
>>
>> Nancy:
>> Yes, but I don’t know if those are the right codes.
>>
>> Sarah Squire
>> Engage Identity
>> http://engageidentity.com
>>
>> _______________________________________________
>> Openid-specs-heart mailing list
>> Openid-specs-heart at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-heart
>>
>>
>
> _______________________________________________
> Openid-specs-heart mailing list
> Openid-specs-heart at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-heart
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20170408/6d9e6df1/attachment.html>