This wiki has undergone a migration to Confluence found Here
Difference between revisions of "RIM based LDAP Registries"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (Created page with "category:RIMBAA Issue ==Summary== When data is exchanged in a large scale environment the need to identify Patients and Providers is an essential requirement. Registries are ...") |
Rene spronk (talk | contribs) |
||
Line 1: | Line 1: | ||
− | [[category:RIMBAA Issue]] | + | [[category:RIMBAA Issue]]Back to [[RIMBAA]]. |
==Summary== | ==Summary== | ||
When data is exchanged in a large scale environment the need to identify Patients and Providers is an essential requirement. Registries are comminly implemented as LDAP registries. This issue seeks to explore the use of LDAP registries based on RIM-mappable static model content. | When data is exchanged in a large scale environment the need to identify Patients and Providers is an essential requirement. Registries are comminly implemented as LDAP registries. This issue seeks to explore the use of LDAP registries based on RIM-mappable static model content. | ||
*See also: the ITI HPD profile, a similar approach by IHE. | *See also: the ITI HPD profile, a similar approach by IHE. |
Revision as of 00:07, 13 January 2011
Back to RIMBAA.
Summary
When data is exchanged in a large scale environment the need to identify Patients and Providers is an essential requirement. Registries are comminly implemented as LDAP registries. This issue seeks to explore the use of LDAP registries based on RIM-mappable static model content.
- See also: the ITI HPD profile, a similar approach by IHE.