Clarification of relationships between an individual and an organization
35 views
Skip to first unread message
Dick Donker
Jan 28, 2016, 7:23:24 AM1/28/16
to ihe-hpd-implementors
When reading the text in ITI-58 transaction Provider Information Query it seems to me there are 3 ways to create a link (relationship) between classes of HPD individual providers and HPD organizational providers:
1. To use a DN-attribute directly. For instance, the HPD individual provider has an attribute HcPracticeLocation which can be multivalued with DN’s of HPD organizational providers.
2. Using the ‘MemberOf’ Provider relationship. The HPD individual provider has an attribute MemberOf which can be multivalued with DN’s of HPDProviderMembership classes. Within the HPDProviderMembership class an HPD individual provider can be 1:1 linked with and HPD organizational provider.
3. Using the Relationships as described in paragraph 3.58.4.1.2.2.4. Such a relationship uses the groupOfNames object and has a name, an owner and multiple members.
I suppose the third option is the preferred one, but we do not understand why the other 2 exist.
1. To use a DN-attribute directly. For instance, the HPD individual provider has an attribute HcPracticeLocation which can be multivalued with DN’s of HPD organizational providers.
2. Using the ‘MemberOf’ Provider relationship. The HPD individual provider has an attribute MemberOf which can be multivalued with DN’s of HPDProviderMembership classes. Within the HPDProviderMembership class an HPD individual provider can be 1:1 linked with and HPD organizational provider.
3. Using the Relationships as described in paragraph 3.58.4.1.2.2.4. Such a relationship uses the groupOfNames object and has a name, an owner and multiple members.
I suppose the third option is the preferred one, but we do not understand why the other 2 exist.
Having three ways to relate a person to an organization will have a burden for a correct querying mechanism.
clau...@gmail.com
Jan 29, 2016, 9:57:09 AM1/29/16
to ihe-hpd-implementors
The way I see it:
- An individual provider can be member of multiple organizations, this can be achieved using groupOfNames.
- The HcPracticeLocation indicates where the individual practices i.e. works.
- The memberOf on the individual provider is what normally should be calculated by the LDAP server i.e. the reverse relationship of the groupOfNames. See e.g. OpenLDAP memberof overlay [1].
[1] http://www.openldap.org/doc/admin24/overlays.html
- An individual provider can be member of multiple organizations, this can be achieved using groupOfNames.
- The HcPracticeLocation indicates where the individual practices i.e. works.
- The memberOf on the individual provider is what normally should be calculated by the LDAP server i.e. the reverse relationship of the groupOfNames. See e.g. OpenLDAP memberof overlay [1].
[1] http://www.openldap.org/doc/admin24/overlays.html
Greg Carver
Jan 29, 2016, 10:07:55 AM1/29/16
to clau...@gmail.com, ihe-hpd-implementors
I wonder to what extent the memberOf overlay is a required feature in hpd. It's nice that OpenLDAP does it, and I'm sure many other ldap systems will implement it for you. But is that actually a required behavior of ldap? Maybe it's the job of the hpd-feed to set both the memberOf and groupOfNames (although, isn't it "member" in OU=Relationships?)
--
You received this message because you are subscribed to the Google Groups "ihe-hpd-implementors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ihe-hpd-implemen...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages