IHE_ITI_Suppl_XPID_Rev1-0_PC_2011-06-03_Forcare_comments

							                                                                    IT Infrastructure (ITI) Technical Framework Supplemen
Use the table below to submit comments on 2011 IT Infrastructure (ITI) Technical Framework and Supplements to the IHE IT
below. Comments on these documents submitted by July 3, 2011 will be considered in refining the Trial Implementation vers
are invited at any time. You may use the form below to submit comments on ITI documents currently published in their trial i
and indicate the title of the relevant document in the Other Document Name column. Enter your comments using the table b

Instructions:
1. Download and review documents. The 2011 ITI Profile Supplements are: (list below)
   a. Cross Community Fetch (XCF)
   b. Cross-Enterprise Document Workflow (XDW)
   c. Document Encryption (DEN)
   d. Support for Metadata-Limited Document Sources
   e. XAD-PID Change Management (XPID)

   These documents are available for download at http://www.ihe.net/Technical_Framework/public_comment.cfm.
  (ITI Trial Implementation supplements and Final Text Technical Frameworks are available at http://www.ihe.net/Technical_
2. Designate Submitter Name, Supplement Name, Volume, Section and Line Number for each comment (or designate as "gen
3. Specify the Issue concisely and provide any new or replacement text in the Proposed Change section.
4. Designate the Priority of each comment as High (H), Medium (M), or Low (L)
    H: Important issue where there is major issue to be resolved. Requires discussion and debate.
    M: Medium issue or clarification. Requires discussion, but should not lead to long debate.
    L: Typo or other minor classification that an editor can manage. Requires no group discussion.
5. After completing form, save it and send as an email attachment to iticomments@googlegroups.com.
6 .Comments on Supplements for Public Comment are due by July 3, 2011.




Submitter   Supplement Name             Other Document   Vol    Section #       Line #
Name        (click cell and select from Name
            list)

Mark Sinke XAD-PID Change                                      1 Introduction
           Management (XPID)

Mark Sinke XAD-PID Change                                      1 Introduction            114
           Management (XPID)

Mark Sinke XAD-PID Change                                      1 X.5                     336
           Management (XPID)

Mark Sinke XAD-PID Change                                      2 3.Y.4.1.2               395
           Management (XPID)
Mark Sinke XAD-PID Change      2 3.Y.4.1.3   425
           Management (XPID)




Mark Sinke XAD-PID Change      2 3.Y.4.1.3   425
           Management (XPID)




Mark Sinke XAD-PID Change      2 3.Y.5.1.1   495
           Management (XPID)
structure (ITI) Technical Framework Supplement Public Comment Form
ure (ITI) Technical Framework and Supplements to the IHE ITI Technical Committee. Documents currently in their specified public comme
1 will be considered in refining the Trial Implementation versions of these supplements to be published in August 2011. Comments on oth
 omments on ITI documents currently published in their trial implementation or final text versions. To do so select "Other" in the Supplem
ument Name column. Enter your comments using the table below and send by email to iticomments@googlegroups.com.


ments are: (list below)




he.net/Technical_Framework/public_comment.cfm.
  Frameworks are available at http://www.ihe.net/Technical_Framework/index.cfm.)
on and Line Number for each comment (or designate as "general").
nt text in the Proposed Change section.
(M), or Low (L)
   Requires discussion and debate.
 ould not lead to long debate.
ge. Requires no group discussion.
nt to iticomments@googlegroups.com.
 ly 3, 2011.




            Issue



            HLv3 is not mentioned. It is discussed later in the Closed
            Issues, but those will not make it into the integrated TF
            version.
            "(this needs to be validated)"


            Link to risk analysis points to work section on FTP site.


            The transaction explicitly states enhanced ACK mode, but
            does not futher specify its use. Enhanced ACK is not
            consistent with the transactions in ITI-30, as far as I can tell.
The supplement only targets moving documents. It is not
possible to move submission sets. However, if the
submission set is not moved, moving a document
underneath it will violate registry constraints. This can be
solved by requiring the submission sets associated with the
moved documents (which should all refer to the same
patient as the submission set) to move as well.

The supplement only targets moving documents. It is not
possible to move folders. Since the folder might be
referencing documents with multiple, different
sourcePatientIds this may not be possible. If that is the case,
a constraint violation of the registry rules occurs. However,
if all documents in the folder are moved, it makes sense to
move the folder as well. The latter is probably the most
common case, since when multiple institutions are
collaborating, the mismatch between the identifiers is likely
found earlier. I would personally opt for specifying behavior
instead of letting it be up to the implementor, at least as
good as we can at this point.

Audit table lists all three patientIDs as having the exact
same structure. A field to distinguish them (at least the"to"
from the "source" patientID would be welcome
ment Public Comment Form
 HE ITI Technical Committee. Documents currently in their specified public comment phase are listed
n versions of these supplements to be published in August 2011. Comments on other ITI documents
 trial implementation or final text versions. To do so select "Other" in the Supplement Name column
able below and send by email to iticomments@googlegroups.com.




nical_Framework/index.cfm.)
 "general").




            Proposed Change                                                         Priority



                                                                                    Low
            Add rationale why HL7v3 was not taken into consideration, from XPID.3
            closed issue
            Just a friendly reminder to do just that before TI                      Low


            Move final risk analysis to a stable URL                                Low


            Change to original ACK mode (i.e., remove the text, as original         Medium
            ACK mode is implied)
Add text to state that submission sets move with their documents.     Medium
This would be in addition to any text about folder handling, and
hence additional to text in the current supplement.




Add text to state that folders move with their documents where        High
appropriate, or fail otherwise. This would replace some text around
line #465 where implementation options are discussed. The current
text leaves too much open and requires "documentation" to solve it.
I would opt for a stricter approach




Suggest to add ParticipantObjectDetail with "to" and "from"           Medium
indication (or MRG-1 and PID-3)
Cross Community Fetch (XCF)
Cross-Enterprise Document Workflow (XDW)
Document Encryption (DEN)
Support for Metadata-Limited Document Sources
XAD-PID Change Management (XPID)
Other
High
Medium
Low