ITI XCDR Endpoint Addressing: Difference between revisions
Jump to navigation
Jump to search
Created page with "__NOTOC__ ''This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you d..." |
No edit summary |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
==1. Proposed Workitem: Enable XCDR transactions to address a specific endpoint beyond the gateway== | |||
* Proposal Editor: Vassil Peytchev | |||
* Editor: Vassil Peytchev | |||
* Proposal Editor: | |||
* Editor: | |||
* Date: N/A (Wiki keeps history) | * Date: N/A (Wiki keeps history) | ||
* Version: N/A (Wiki keeps history) | * Version: N/A (Wiki keeps history) | ||
* Domain: | * Domain: IT Infrastructure | ||
==2. The Problem== | ==2. The Problem== | ||
Currently, the XCDR specification describes a use case of XDR/XCDR working together to cross community boundaries. There is, however, no discussion or guidance on how the endpoint addressing should work. | |||
This proposal will enhance the description of the XDR/XCDR use case with more details about the author and intended recipient metadata elements, and will add actor requirements to facilitate directed delivery. | |||
==3. Key Use Case== | ==3. Key Use Case== | ||
The key use case is to add XCDR as an transport option to the PCC 360X profile, and add the US implementation details on how 360X will work on TEFCA. | |||
==4. Standards and Systems== | ==4. Standards and Systems== | ||
* XDR | |||
* XCDR | |||
==5. Discussion== | ==5. Discussion== | ||
| Line 50: | Line 36: | ||
[[Category:ITI]] | |||
Revision as of 14:05, 20 February 2025
1. Proposed Workitem: Enable XCDR transactions to address a specific endpoint beyond the gateway
- Proposal Editor: Vassil Peytchev
- Editor: Vassil Peytchev
- Date: N/A (Wiki keeps history)
- Version: N/A (Wiki keeps history)
- Domain: IT Infrastructure
2. The Problem
Currently, the XCDR specification describes a use case of XDR/XCDR working together to cross community boundaries. There is, however, no discussion or guidance on how the endpoint addressing should work.
This proposal will enhance the description of the XDR/XCDR use case with more details about the author and intended recipient metadata elements, and will add actor requirements to facilitate directed delivery.
3. Key Use Case
The key use case is to add XCDR as an transport option to the PCC 360X profile, and add the US implementation details on how 360X will work on TEFCA.
4. Standards and Systems
- XDR
- XCDR
5. Discussion
<Include additional discussion or consider a few details which might be useful for the detailed proposal>
- <Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>
- <What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>
- <What are some of the risks or open issues to be addressed?>
<This is the brief proposal. Try to keep it to 1 or at most 2 pages>