[Openid-specs-heart] How do you define a resource set?

[Debbie Bucci]

These profiles will not be like DAF or USLab or QiCore; but will be a layer
added to these. This layer will be agnostic to the underlying data
profiling layer.

Are you referring to something like ...
https://www.hl7.org/fhir/profilelist.html ?


Hence why I recommend HEART simply adopt either the SMART scopes or the
> _confidentiality codes.
>

I was going to include SMART in potential example but did not see a direct
reference to the profile on HL7 - though generally understood I suppose.
Any talk by other groups wanting to implement SMART  seem to focus on the
resources that lead back to DAF  ... and given the examples in the profile
(pasted below)  I assumed that all resources could have separate access
scopes

Scopes can be used to indicate access to different kinds of things in an
API. Common examples include:


   - The kind of resource being protected (medications, appointments).
   - The kind of access to the resource being requested (read, write,
   delete).
   - The specific resource being accessed (user ID, resource URI).




> The _confidentiality codes are in my view closer to a useable set, and are
> not specific to FHIR. But the SMART scopes are being used in demonstration
> systems and are not out-right-wrong. The important part is that the scopes
> we include need to be recognized as a starter-set, that the actual scopes
> we will find in production are likely to be totally different.
>


SMART AND Confidentiality codes seems like good combination to start with-
  http://hl7.org/fhir/v3/Confidentiality/index.html

>
> You can continue to ignore me...
>

Not ignoring - just ignorant.   REALLY trying to put the pieces together.
Can't help the process along if I don't understand.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20160702/bd60ff03/attachment.html>