Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Federated Directory Grouping #192

Open
JohnMoehrke opened this issue Dec 19, 2022 · 6 comments
Open

Federated Directory Grouping #192

JohnMoehrke opened this issue Dec 19, 2022 · 6 comments
Assignees

Comments

@JohnMoehrke
Copy link
Contributor

No description provided.

@JohnMoehrke
Copy link
Contributor Author

  1. Proposed Work Item: Federation Directory Grouping
    Proposal Editor: Joe Lamy
    Work item Editor: TBD
    Date: November 15, 2022
    Version: 1
    Domain: ITI
  2. The Problem
    Given the work in mCSD and the Topologies white paper to define document sharing topologies such as federation in more detail, there is a need to define how implementers may group these directory representations with addressing and routing behaviors of IHE document sharing profiles.
  3. Key Use Case
    Enable an mCSD Care Services Selective Supplier to describe not only its document sharing topology in a directory, but details about how requests and data will be routed, specific to grouped IHE profiles that support federation. Add normative routing requirements to be added to the existing document sharing transactions.
    Enable an mCSD Care Services Selective Consumer to deterministically discover these details, answering questions such as:
    • Which federated Organizations’ data will be included in aggregate responses?
    • Which federated Organizations or related Practitioners may I target when using a transaction’s routing capability?
  4. Standards & Systems
    FHIR
  5. Discussion
    Proposed scope:
    • XCDR: targetable communities (Organization)
    • XDR: targetable intendedRecipients (Organization, Practitioner)
    • MHD ITI-65: targetable intendedRecipients (Organization, Practitioner)
    • XCPD: explicitly aggregated communities (Organization) (i.e. information identifiable as from those communities)
    • XCPD: implicitly aggregated communities (Organization) (i.e. information consolidated; not identifiable as from those communities)
    • XCPD: targetable communities (Organization)*
    • XCA: explicitly aggregated communities (Organization)
    • XCA: implicitly aggregated communities (Organization)
    • XCA: targetable communities (Organization)*
    • MHD ITI-66, ITI-67: explicitly aggregated communities (Organization)
    • MHD ITI-66, ITI-67: implicitly aggregated communities (Organization)
    • MHD ITI-66, ITI-67: targetable communities (Organization)
    Scope would include potential additions/modifications to the mCSD Organization Affiliation Types code system to support specific needs of these groupings. See issue Open Issue 30: organization affiliation types ITI.Topologies#5
    *This work item would not include in its scope the actual transaction federation capabilities (e.g. targeted XCPD), only the grouping of these capabilities with the directory.

@JohnMoehrke
Copy link
Contributor Author

Seems this should be put on hold until the whitepaper gets closer to a defined set of needs. I think it is too soon to start work on solving a problem that is not yet clear.

@JohnMoehrke
Copy link
Contributor Author

Please itemize the specific changes this is asking for. Minimally defining the use-case need, or defining the specific items.

@lukeaduncan
Copy link
Contributor

@jlamy Now that the whitepaper is done, should we review this again at the next face to face?

@jlamy
Copy link
Contributor

jlamy commented Aug 16, 2024

Related CP-ITI-1301, which is defining XCA: targetable communities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Under assessment by planning
Development

No branches or pull requests

3 participants