search

IHE / ITI.Topologies

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.
https://profiles.ihe.net/ITI/papers/Topologies/index.html
Creative Commons Attribution 4.0 International
4 stars 1 forks source link

Do we need both mCSD Endpoint and mCSD Endpoint for Document Sharing? #6

Open slagesse-epic opened 2 years ago

slagesse-epic commented 2 years ago

Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2)

Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem.

Currently, there are two profiles for Endpoint - mCSD Endpoint and mCSD Endpoint for Document Sharing.

Since ihe-endpointspecifictype is 0..*, do we need both of these, or should we consolidate them?

Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.

Create one Endpoint profile that satisfies both needs.

Priority:

jlamy commented 2 years ago

Well, the mCSD Endpoint for Document Sharing adds the preferred binding to the doc sharing connection type value set.