Skip to content

Commit 9f5e4a7

Browse files
committed
add Document Consumer open-issue
1 parent 465b9dc commit 9f5e4a7

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

README.md

+2-5
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,10 @@
11
## Status
22
This is the source for the IHE ITI Mobile Cross-Enterprise Document Data Element Extraction(mXDE) Implementation Guide.
33

4-
54
Release - https://profiles.ihe.net/ITI/mXDE
65

76
CI Build - http://build.fhir.org/ig/IHE/ITI.mXDE/branches/master/index.html
87

9-
For todo, issues, and changes review the [issues page in the build](http://build.fhir.org/ig/IHE/ITI.mXDE/branches/master/issues.html)
10-
11-
## Question
8+
For significant change list, and open-issues see the [issues page in the build](http://build.fhir.org/ig/IHE/ITI.mXDE/branches/master/issues.html)
129

13-
- Why does mXDE need to add the mXDE actor to ITI-43? Seems it can just integrate the Document Consumer actor. What is wrong with mXDE requiring a grouping with Document Consumer? This would also seem to meet MHD vs XDS vs XCA need. Is the reason that one deployment model wants to decompose the documents upon publication rather than being triggered by a QEDm query?
10+
The [mXDE github Issue tracking](https://github.com/IHE/ITI.mXDE/issues) is used for comments and feature requests

input/pagecontent/issues.md

+3
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,10 @@
1111

1212
## Issues
1313

14+
The details are available on github at the link provided. Comments on these github issues are encouraged.
15+
1416
- [mXDE_001](https://github.com/IHE/ITI.mXDE/issues/1): There is no "Transform Considerations" identified in mXDE, but should there be? Such as preserving original identifiers in the resulting FHIR Resources, even when those identifiers can't be used to retrieve the original data, as they are still useful for de-duplication downstream.
17+
- [mXDE_003](https://github.com/IHE/ITI.mXDE/issues/3) nXDE_003: Use of Document Consumer grouping. The original mXDE chose not to group with Document Consumer, but rather chose to add the mXDE actor to the ITI-43 (Retrieve Document Set) transaction. I recommend we change to grouping with Document Consumer (possibly Content Consumer) to enable broader support such as MHDS and XCA.
1518

1619
### Submit an Issue
1720

0 commit comments

Comments
 (0)