Whitepaper on Document Sharing Across Network Topologies expands upon the concepts in the Health Information Exchange White Paper by providing additional guidance on how existing document sharing communities can be interconnected to form a unified federated exchange ecosystem.
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.
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.