You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is one code in mCSD Organization Affiliation Types. Should there be at least two, one for transparent federation vs opaque federation?
The expectations would be different: with transparent federation, federated identifiers would be
preserved in responses and respected in requests. With opaque federation, identifiers would be
consolidated/overwritten with the identifiers of the "parent" organization.
Probably, but the implications of opaque federation are complex. Some aspects may be consolidated
(e.g. golden patient record) while others are not (separate documents). Perhaps we could limit scope
to whether federated communities (Organizations with an ID of type HCID) are addressable in
requests and responses. Seeking input from reviewers.
The text was updated successfully, but these errors were encountered:
Currently there is one code in mCSD Organization Affiliation Types. Should there be at least two, one for transparent federation vs opaque federation?
The expectations would be different: with transparent federation, federated identifiers would be
preserved in responses and respected in requests. With opaque federation, identifiers would be
consolidated/overwritten with the identifiers of the "parent" organization.
Probably, but the implications of opaque federation are complex. Some aspects may be consolidated
(e.g. golden patient record) while others are not (separate documents). Perhaps we could limit scope
to whether federated communities (Organizations with an ID of type HCID) are addressable in
requests and responses. Seeking input from reviewers.
The text was updated successfully, but these errors were encountered: