Docstoc

IHE TF CP

Document Sample
IHE TF CP Powered By Docstoc
					08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc



     IHE Technical Framework Change Proposal

                                                Tracking information:
IHE Technical Framework Domain                              IT Infrastructure
Change Proposal Number (assigned by Domain Technical        TF-ddd-CP-xxx
Committee)
Change Proposal Status:
Date of last update:
Person assigned:



                                 Change Proposal Summary information:
                                              Audit Messages for XDS
Submitter’s Name(s) and e-mail address(es):                 Tjerk Drouen (Tjerk.Drouen@ICT.nl)
Submission Date:                                            16 October 2006
Integration Profile affected:                               ATNA
Version of IHE Technical Framework:                        IHE ITI TF: Vol 2:
                                                           Revision 2.0 – Final Text: August 15, 2005
                                                           --------------------------------------------------------------------------
                                                           IHE ITI TF – Supplement 2006-207
                                                           Registry Stored Query Transaction for XDS Profile [ITI-18]
                                                           Trail Implementation Version
                                                           Publication Data: August 15, 2006
Volume(s) and Section(s) affected:                          Volume 2
                                                            Record Audit Event
                                                            => 3.20.6 Trigger Events and Message semantics
                                                            => 3.20.7.3 IHE Audit Trail
                                                            Register Document Set
                                                            => 3.14.4.1.2.15 Security Requirements
                                                            Query Registry
                                                            => 3.16.4.1.2.3 Security Requirements
Rationale for Change:
The details as specified in the DICOM (Sup 95) are not always directly usable for the XDS actors.
For most audit Trigger Events, the IHE-ITI-TF refers the reader to DICOM (Sup 95).
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc



Proposal
Specify the Audit Messages for XDS Actors in more detail.
Specification can be done in the same format as DICOM Sup 95 or the tables of 3.20.7.3 IHE
Audit Trail.
Certain details as specified by DICOM Sup95 need to be modified.
The following paragraphs describe the Trigger Events that are specific to the XDS Document
Registry and the Document Repository.
These are the IHE actors that I am confronted with during my engineering tasks. This change
proposal does not cover the other Actors in the XDS profile, nor does it cover the more generic
Trigger Events such as start/stop, configuration and node-authentication.
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc



PHI-Import on Register Document Set [ITI-14]
The transaction ‘Register Document Set’ [ITI-14] causes Trigger Event ‘PHI-import’.
The ‘XDS Document Registry’ needs to generate an Audit Message.
The details of DICOM (Sup95) needs to be modified for this Audit Message;
                                   Field Name                   Opt.   Value Constraints
Event                              EventID                      M      EV (110107, DCM, “Import”)
                                   EventActionCode              M      EV “C” (Create)
                                   EventDateTime                M      not specialized
                                   EventOutcomeIndicator        M      not specialized
                                   EventTypeCode                U      not specialized
Importer (1)                       UserID                       M      The identity of the local user or process importing the
                                                                       data. If both are known, then two active participants
The ‘Document Registry’ is                                             shall be included (both the person and the process).
the importer. This is a Web-
                                                                       In order of preference:
Service process.
                                                                       < Hostname | IPAddress >
I believe that the user identity
is irrelevant. Only becomes
relevant if impersonation is
used.
                                   AlternateUserID              U      not specialized
                                                                       Any guidance on this!?
                                   UserName                     U      not specialized
                                   UserIsRequestor              U      EV TRUE on at least one participant
                                                                       EV FALSE on the others
                                                                       EV FALSE
                                                                       The importer is not the requestor nor the initiator
                                                                       for the event.
                                                                       There is only one importer participant!
                                   RoleIDCode                   M      EV (110152, DCM, “Destination”)
                                   NetworkAccessPointTypeCode   U      not specialized
                                   NetworkAccessPointID         U      not specialized
Source (1)                         UserID                       M      See Section A.1.2.3
Source (1..2)                                                          1) Document Repository =>

The ‘Document Source’ is the                                           In order of preference:
                                                                       < Hostname | IPAddress >
ultimate source. However the
‘Document Repository’ acts                                             2) Document Source =>
as intermediate agent.                                                 Only the following information is known at the
The ‘Document Repository’                                              Document Registry.
can be identified through the                                          < XDSSubmissionSet.sourceId >
HTTP request details and the                                           Note:
‘Document Source’ can be                                               XDSSubmissionSet.sourceId is a codedValue!
identified by the                                                      Should the code-scheme be recorded?
‘XDSSubmissionSet.sourceId’
I suggest to record both as
sources.


                                   AlternateUserID              U      See Section A.1.2.4
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc


                                  UserName                         U    not specialized
Should the repository be          UserIsRequestor                  U    EV FALSE
considered a requestor                                                  1) Document Repository =>
initiator? Actually it is an                                            EV TRUE
intermediate agent that relays
the submission.                                                         The source is the requestor and the initiator for the
                                                                        event.
                                                                        2) Document Source =>
                                                                        EV TRUE
                                                                        The source is the requestor and the initiator for the
                                                                        event.
OPEN ISSUE:                       RoleIDCode                       M    EV (110155, DCM, “Source Media”)
How to distinguish                                                      1) Document Repository =>
afterwards which of the two                                             EV (110153, DCM, “Source”)
participants was the Source
and which was the                                                       2) Document Source =>
Repository?                                                             EV (110153, DCM, “Source”)
Should RoleIDCode be set to
an XDS value instead of a
DCM value?
                                  NetworkAccessPointTypeCode       U    not specialized
                                  NetworkAccessPointID             MC   Shall be present if Net Access Point Type Code is
                                                                        present. Shall
                                                                        use fields as specified in RFC nnnn.
Studies (0..N)                    ParticipantObjectTypeCode        M    EV 2 (system)
XDSSubmissionSet (1)
The transaction ‘Register
Document Set’ [ITI-14]
always contains only one
XDSSubmissionSet.
The XDSSubmissionSet is
identified by its uniqueId.
I suggest to record the
uniqueId.
I suggest NOT to include the
folder, documents and
associations. That would
create too large audit records.
                                  ParticipantObjectTypeCodeRole    M    EV 3 (report)
                                                                        5 Master file
                                                                        The XDSSubmissionSet is actually a master file in
                                                                        the context of XDS. It contains the meta-
                                                                        information about the documents.
                                  ParticipantObjectDataLifeCycle   U    not specialized
                                                                        I suggest to use the following codes;
                                                                        1 Origination / Creation
                                                                        3 Amendment
                                  ParticipantObjectIDTypeCode      M    EV (110180, DCM, “Study Instance UID”)
                                                                        No proper ParticipantObjectIDTypeCode is defined
                                                                        for XDS indentifiers. I Suggest to use;
                                                                        Either
                                                                        EV (xxxxx, xxxxx, “XDSSubmissionSet.uniqueId”)
                                                                        -or-
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc


                                                                   EV (xxxxx, xxxxx, “XDSSubmissionSet.UUID”)
                             ParticipantObjectSensitivity     U    not specialized
                             ParticipantObjectID              M    The Study Instance UID
                                                                   I suggest to use;
                                                                   Either
                                                                   XDSSubmissionSet.uniqueId
                                                                   -or-
                                                                   XDSSubmissionSet.UUID
                             ParticipantObjectName            U    not specialized
                                                                   Any guidance?
                                                                   I suggest to use
                                                                   XDSSubmissionSet.contentTypeCode.DisplayName
                             ParticipantObjectQuery           U    not specialized
                             ParticipantObjectDetail          U    Not further specialized
                             ParticipantObjectDescription     U    not further specialized
NOT applicable               SOPClass                         MC   not further specialized
NOT applicable               Accession                        U    not further specialized
NOT applicable               NumberOfInstances                U    not further specialized
NOT applicable               Instances                        U    not further specialized
NOT applicable               Encrypted                        U    not further specialized
NOT applicable               Anonymized                       U    not further specialized
Patient (1..N)               ParticipantObjectTypeCode        M    EV 1 (person)
Patient (1)
The transaction ‘Register
Document Set’ [ITI-14] is
always related to only one
patient.
                             ParticipantObjectTypeCodeRole    M    EV 1 (patient)
                             ParticipantObjectDataLifeCycle   U    not specialized
                             ParticipantObjectIDTypeCode      M    EV 2 (patient ID)
                             ParticipantObjectSensitivity     U    not specialized
                             ParticipantObjectID              M    The patient ID
                                                                   I suggest to use;
                                                                   XDSSubmissionSet.patientId
                             ParticipantObjectName            U    The patient name
                                                                   Note: XDS is actually patient ID based.
                                                                   Do not expect patient names!
                                                                   OPEN ISSUE:
                                                                   Due to privacy constraints, the audit message
                                                                   should NOT contain human-readable patient data.
                                                                   Patient names should be avoided.
                             ParticipantObjectQuery           U    not specialized
                             ParticipantObjectDetail          U    not specialized
                             ParticipantObjectDescription     U    not further specialized
NOT applicable               SOPClass                         NA
NOT applicable               Accession                        NA
NOT applicable               NumberOfInstances                NA
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc


NOT applicable            Instances        NA
NOT applicable            Encrypted        U    not further specialized
NOT applicable            Anonymized       U    not further specialized
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc



PHI-Export on
      Registry Stored Query [ITI-18] and
      Query Registry [ITI-16]
The transactions
‘Registry Stored Query’ [ITI-18] and
‘Query Registry’ [ITI-16]
cause Trigger Event ‘PHI-export’.
The ‘XDS Document Registry’ needs to generate an Audit Message.
The details of DICOM (Sup95) needs to be modified for this Audit Message;
                          Field Name                   Opt.   Value Constraints
Event                     EventID                      M      EV (110106, DCM, “Export”)
                          EventActionCode              M      EV “R” (Read)
                          EventDateTime                M      not specialized
                          EventOutcomeIndicator        M      not specialized
                          EventTypeCode                U      not specialized
Exporter (1..2)           UserID                       M      The identity of the local user or process exporting the
                                                              data. If both are known, then two active participants
Exporter (1)
                                                              shall be included (both the person and the process).
The ‘Document                                                 In order of preference:
Registry’ is the                                              < Hostname | IPAddress >
exporter. This is a
Web-Service process.
I believe no the user
identity is irrelevant.
Only becomes
relevant if
impersonation is
used.
                          AlternateUserID              U      not specialized
                                                              Any guidance on this!?
                          UserName                     U      not specialized
                          UserIsRequestor              U      EV TRUE on at least one participant
                                                              EV FALSE
                                                              The exporter is not the requestor nor the initiator
                                                              for the event.
                          RoleIDCode                   M      EV (110153, DCM, “Source”)
                          NetworkAccessPointTypeCode   U      not specialized
                          NetworkAccessPointID         U      not specialized
Destination (1)           UserID                       M      See Section A.1.2.3
The ‘Document
Consumer’ is the
destination.
                          AlternateUserID              U      See Section A.1.2.4
                          UserName                     U      not specialized
                          UserIsRequestor              U      EV FALSE
                                                              EV TRUE
                                                              The destination is the requestor and the initiator
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc

                                                              for the event.
                        RoleIDCode                       M    EV (110154, DCM, “Destination Media”)
                                                              EV (110152, DCM, “Destination”)
                        NetworkAccessPointTypeCode       MC   Shall be present if being exported to other than
                                                              physical media, e.g. to a network destination rather
                                                              than to film, paper or CD. May be present otherwise.
                                                              This field shall be present with values selected from
                                                              those specified in RFC nnnn where applicable.
                                                              Either
                                                              EV 1 (Machine Name, including DNS name)
                                                              -or-
                                                              EV 2 (IP Address)
                        NetworkAccessPointID             MC   Shall be present if Net Access Point Type Code is
                                                              present. Shall use fields as specified in RFC nnnn.
                                                              Either
                                                              Machine Name
                                                              -or-
                                                              IP Address
Studies (1..N)          ParticipantObjectTypeCode        M    EV 2 (system)
Query Responses
(1...N) of IHE-ITI-
TF Transactions;
- Query Registry
[ITI-16]
- Registry Stored
Query Transaction
for XDS Profile [ITI-
18]
These responses
contain
XDSSubmissionSet,
XDSDocumentEntry,
and XDSFolder
objects and
Associations that are
identified by
entryUUID or
uniqueId.
                        ParticipantObjectTypeCodeRole    M    EV 3 (report)
                        ParticipantObjectDataLifeCycle   U    not specialized
                        ParticipantObjectIDTypeCode      M    EV (110180, DCM, “Study Instance UID”)
                                                              No proper ParticipantObjectIDTypeCode is defined
                                                              for XDS indentifiers. I Suggest to use;
                                                              EV (xxxxx, xxxxx, “XDSDocument.UUID”)
                                                              EV (xxxxx, xxxxx, “XDSDocument.uniqueId”)
                                                              EV (xxxxx, xxxxx, “XDSFolder.UUID”)
                                                              EV (xxxxx, xxxxx, “XDSFolder.uniqueId”)
                                                              EV (xxxxx, xxxxx, “XDSSubmissionSet.UUID”)
                                                              EV (xxxxx, xxxxx, “XDSSubmissionSet.uniqueId”)
                                                              What should one do with ebXML Associations?
                        ParticipantObjectSensitivity     U    not specialized
                        ParticipantObjectID              M    The Study Instance UID
                                                              One of the following;
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc


                                                          XDSDocument.UUID
                                                          XDSDocument.uniqueId
                                                          XDSFolder.UUID
                                                          XDSFolder.uniqueId
                                                          XDSSubmissionSet.UUID
                                                          XDSSubmissionSet.uniqueId
                                                          What should one do with ebXML Associations?
                    ParticipantObjectName            U    not specialized
                                                          Any guidance?
                                                          I suggest to use
                                                          XDSDocumentEntry.title or
                                                          XDSDocumentEntry.classCode.DisplayName
                                                          XDSFolder.codeDisplayNameList
                                                          XDSSubmissionSet.contentTypeCode.DisplayName
                                                          OPEN ISSUE:
                                                          One needs to be careful that these do not contain
                                                          data that can compromise the patient’s privacy.
                    ParticipantObjectQuery           U    not specialized
                                                          This is already captured by the Event Trigger
                                                          ‘Query Information’ that is preceding this ‘PHI-
                                                          Export’. This information does not need to be
                                                          recorded twice.
                                                          I suggest to specify that this should be empty.
                    ParticipantObjectDetail          U    Not further specialized
                    ParticipantObjectDescription     U    not further specialized
NOT applicable      SOPClass                         MC   not further specialized
NOT applicable      Accession                        U    not further specialized
NOT applicable      NumberOfInstances                U    not further specialized
NOT applicable      Instances                        U    not further specialized
NOT applicable      Encrypted                        U    not further specialized
NOT applicable      Anonymized                       U    not further specialized
Patients (1..N)     ParticipantObjectTypeCode        M    EV 1 (person)
Patient (1)
XDS is patientId
based
                    ParticipantObjectTypeCodeRole    M    EV 1 (patient)
                    ParticipantObjectDataLifeCycle   U    not specialized
                    ParticipantObjectIDTypeCode      M    EV 2 (patient ID)
                    ParticipantObjectSensitivity     U    not specialized
                    ParticipantObjectID              M    The patient ID
                    ParticipantObjectName            U    The patient name
                                                          Note: XDS is actually patient ID based.
                                                          Do not expect patient names!
                                                          OPEN ISSUE:
                                                          Due to privacy constraints, the audit message
                                                          should NOT contain human-readable patient data.
                                                          Patient names should be avoided.
                    ParticipantObjectQuery           U    not specialized
                    ParticipantObjectDetail          U    not specialized
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc


                           ParticipantObjectDescription     U           not specialized
NOT applicable             SOPClass                         NA          not further specialized
NOT applicable             Accession                        NA          not further specialized
NOT applicable             NumberOfInstances                NA          not further specialized
NOT applicable             Instances                        NA          EV 1 (person)
NOT applicable             Encrypted                        U           EV 1 (patient)
NOT applicable             Anonymized                       U           not specialized




PHI-Export on
      Retrieve Document [ITI-17]
The transaction [ITI-17] causes Trigger Event ‘PHI-export’.
The ‘XDS Document Repository’ needs to generate an Audit Message.
The details of DICOM (Sup95) needs to be modified for this Audit Message;
                               Field Name                        Opt.       Value Constraints
Event                          EventID                           M          EV (110106, DCM, “Export”)
                               EventActionCode                   M          EV “R” (Read)
                               EventDateTime                     M          not specialized
                               EventOutcomeIndicator             M          not specialized
                               EventTypeCode                     U          not specialized
Exporter (1..2)                UserID                            M          The identity of the local user or process exporting
                                                                            the data. If both are known, then two active
Exporter (1)                                                                participants shall be included (both the person
The ‘Document                                                               and the process).
Repository’ is the                                                          In order of preference:
exporter. This is a Web-                                                    < Hostname | IPAddress >
Service process.
I believe no the user
identity is irrelevant.
Only becomes relevant if
impersonation is used.
                               AlternateUserID                   U          not specialized
                                                                            Any guidance on this!?
                               UserName                          U          not specialized
                               UserIsRequestor                   U          EV TRUE on at least one participant
                                                                            EV FALSE
                                                                            The exporter is not the requestor nor the
                                                                            initiator for the event.
                               RoleIDCode                        M          EV (110153, DCM, “Source”)
                               NetworkAccessPointTypeCode        U          not specialized
                               NetworkAccessPointID              U          not specialized
Destination (1)                UserID                            M          See Section A.1.2.3
The ‘Document
Consumer’ is the
destination.
                               AlternateUserID                   U          See Section A.1.2.4
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc


                              UserName                         U    not specialized
                              UserIsRequestor                  U    EV FALSE
                                                                    EV TRUE
                                                                    The destination is the requestor and the
                                                                    initiator for the event.
                              RoleIDCode                       M    EV (110154, DCM, “Destination Media”)
                                                                    EV (110152, DCM, “Destination”)
                              NetworkAccessPointTypeCode       MC   Shall be present if being exported to other than
                                                                    physical media, e.g. to a network destination
                                                                    rather than to film, paper or CD. May be present
                                                                    otherwise. This field shall be present with values
                                                                    selected from those specified in RFC nnnn where
                                                                    applicable.
                                                                    Either
                                                                    EV 1 (Machine Name, including DNS name)
                                                                    -or-
                                                                    EV 2 (IP Address)
                              NetworkAccessPointID             MC   Shall be present if Net Access Point Type Code is
                                                                    present. Shall use fields as specified in RFC
                                                                    nnnn.
                                                                    Either
                                                                    Machine Name
                                                                    -or-
                                                                    IP Address
Studies (1..N)                ParticipantObjectTypeCode        M    EV 2 (system)
Document (1)
The transaction Retrieve
Document [ITI-17]
results in the retrieval of
one document via an
document URI.
                              ParticipantObjectTypeCodeRole    M    EV 3 (report)
                                                                    EV 17 (Data repository)
                                                                    I suggest to audit the URI of the retrieve
                                                                    request.
                                                                    The retrieve response contains the report for
                                                                    that URI.
                                                                    The URI has the role of „Data Repository‟;
                                                                    17 Data RepositoryWhile the report has the
                                                                    role of „Report‟;
                                                                    3 Report
                              ParticipantObjectDataLifeCycle   U    not specialized
                                                                    I suggest to use;
                                                                    6 Access / Use
                              ParticipantObjectIDTypeCode      M    EV (110180, DCM, “Study Instance UID”)
                                                                    12 URI
                              ParticipantObjectSensitivity     U    not specialized
                              ParticipantObjectID              M    The Study Instance UID
                                                                    URI
                                                                    Auditing this may be considered a security
                                                                    breach. URIs should only be provided to
                                                                    trusted consumers. Should one consider the
                                                                    „Audit Record Repository‟ as trusted party?
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc


                           ParticipantObjectName            U    not specialized
                                                                 Any guidance?
                           ParticipantObjectQuery           U    not specialized
                                                                 This URI is not directly related to any query.
                                                                 I suggest to specify that this should be empty.
                           ParticipantObjectDetail          U    Not further specialized
                           ParticipantObjectDescription     U    not further specialized
NOT applicable             SOPClass                         MC   not further specialized
NOT applicable             Accession                        U    not further specialized
NOT applicable             NumberOfInstances                U    not further specialized
NOT applicable             Instances                        U    not further specialized
NOT applicable             Encrypted                        U    not further specialized
NOT applicable             Anonymized                       U    not further specialized
Patients (1..N)            ParticipantObjectTypeCode        M    EV 1 (person)
Patient (0..1)
The transaction Retrieve
document [ITI-17] is
agnostic to the patient.
However the Document
Repository could
determine the patientId
of the corresponding
document.
I would recommend to
AVOID this!
                           ParticipantObjectTypeCodeRole    M    EV 1 (patient)
                           ParticipantObjectDataLifeCycle   U    not specialized
                           ParticipantObjectIDTypeCode      M    EV 2 (patient ID)
                           ParticipantObjectSensitivity     U    not specialized
                           ParticipantObjectID              M    The patient ID
                           ParticipantObjectName            U    The patient name
                                                                 Note: XDS is actually patient ID based.
                                                                 Do not expect patient names!
                                                                 OPEN ISSUE:
                                                                 Due to privacy constraints, the audit message
                                                                 should NOT contain human-readable patient
                                                                 data. Patient names should be avoided.
                           ParticipantObjectQuery           U    not specialized
                           ParticipantObjectDetail          U    not specialized
                           ParticipantObjectDescription     U    not specialized
NOT applicable             SOPClass                         NA   not further specialized
NOT applicable             Accession                        NA   not further specialized
NOT applicable             NumberOfInstances                NA   not further specialized
NOT applicable             Instances                        NA   EV 1 (person)
NOT applicable             Encrypted                        U    EV 1 (patient)
NOT applicable             Anonymized                       U    not specialized
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc



„Query Information‟ on
             Registry Stored Query [ITI-18]
IHE IT Infrastructure Technical Framework 10 Supplement 2006-2007
Registry Stored Query Transaction for XDS Profile
[ITI-18]


The transaction
‘Registry Stored Query’
causes Trigger Event ‘Query Information’.
The ‘XDS Document Registry’ needs to generate an Audit Message.
The details of DICOM (Sup95) needs to be modified for this Audit Message;
                           Field Name                   Opt.   Value Constraints
Event                      EventID                      M      EV (110112, DCM, “Query”)
                           EventActionCode              M      EV “E” (Execute)
                           EventDateTime                M      not specialized
                           EventOutcomeIndicator        M      not specialized
                           EventTypeCode                U      not specialized
Source (1)                 UserID                       M      The identity of the process issuing the query.
The ‘Document                                                  In order of preference:
Consumer’ is the source.                                       < Remote User | Remote Machine Name |
                                                               Remote IPAddress >
                           AlternateUserID              U      not specialized
                           UserName                     U      not specialized
                           UserIsRequestor              U      not specialized
                                                               EV TRUE
                                                               The source is the requestor and the initiator
                                                               for the event.
                           RoleIDCode                   M      EV (110153, DCM, “Source”)
                           NetworkAccessPointTypeCode   U      not specialized
                                                               Either
                                                               EV 1 (Machine Name, including DNS name)
                                                               -or-
                                                               EV 2 (IP Address)
                           NetworkAccessPointID         U      not specialized
                                                               Either
                                                               Machine Name
                                                               -or-
                                                               IP Address
Destination (1)            UserID                       M      The identity of the process that will respond to the
                                                               query.
The ‘Document
Registry’ is the                                               In order of preference:
                                                               < Local Hostname | Local IPAddress >
destination. This is a
Web-Service process.
I believe no the user
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc

identity is irrelevant.
Only becomes relevant if
impersonation is used.
                            AlternateUserID                  U   not specialized
                                                                 Any guidance on this!?
                            UserName                         U   not specialized
                            UserIsRequestor                  U   not specialized
                                                                 EV FALSE
                                                                 The destination is not the requestor nor the
                                                                 initiator for the event.
                            RoleIDCode                       M   EV (110152, DCM, “Destination”)
                            NetworkAccessPointTypeCode       U   not specialized
                            NetworkAccessPointID             U   not specialized
Other Participants (0..N)   UserID                           M   The identity of any other participants that might be
                                                                 involved and
Not applicable!
                                                                 known, especially third parties that are the
                                                                 requestor
                            AlternateUserID                  U   not specialized
                            UserName                         U   not specialized
                            UserIsRequestor                  U   not specialized
                            RoleIDCode                       U   not specialized
                            NetworkAccessPointTypeCode       U   not specialized
                            NetworkAccessPointID             U   not specialized
Query Request               ParticipantObjectTypeCode        M   EV 2 (system)
                            ParticipantObjectTypeCodeRole    M   EV 3 (report)
                                                                 I suggest to use;
                                                                 24 Query
                            ParticipantObjectDataLifeCycle   U   not specialized
                            ParticipantObjectIDTypeCode      M   DT (110181, DCM, “SOP Class UID”)
                                                                 I suggest to use a coded value for the specific
                                                                 query.
                                                                 EV (xxxxx, xxxxx, “RegistryStoredQueryId”)
                            ParticipantObjectSensitivity     U   not specialized
                            ParticipantObjectID              M   If the ParticipantObjectIDTypeCode is (110181,
                                                                 DCM, “SOP Class UID”), then this field shall hold
                                                                 the UID of the SOP Class being queried
                                                                 Stored Query ID
                                                                 See 3.18.4.1.2.4 Stored Query IDs
                                                                 IHE_ITI_TF_Supplement_
                                                                 XDS_Stored_Query_TI_2006_08_15.pdf
                            ParticipantObjectName            U   not specialized
                                                                 Stored Query Name
                                                                 See 3.18.4.1.2.4 Stored Query IDs
                                                                 IHE_ITI_TF_Supplement_
                                                                 XDS_Stored_Query_TI_2006_08_15.pdf
                            ParticipantObjectQuery           M   If the ParticipantObjectIDTypeCode is (110181,
                                                                 DCM, “SOP Class UID”), then this field shall hold
                                                                 the Dataset of the DICOM query, base64
                                                                 encoded.
                                                                 HELP! Should the list of parameters be
                                                                 encoded in base64? This requires detailing!
08f20088-6ed8-42d0-b4b4-ec09d05a16d5.doc


                      ParticipantObjectDetail        MC   An element with the Attribute “type” equal to
                                                          "TransferSyntax” shall be present with the
                                                          Transfer Syntax UID as the value, indicating the
                                                          transfer syntax of the query Dataset prior to
                                                          base64 encoding. Required if the
                                                          ParticipantObjectIDTypeCode is (110181, DCM,
                                                          “SOP Class UID”)
                      ParticipantObjectDescription   U    not further specialized
NOT applicable        SOPClass                       NA
NOT applicable        Accession                      NA
NOT applicable        NumberOfInstances              NA
NOT applicable        Instances                      NA
NOT applicable        Encrypted                      U    not further specialized
NOT applicable        Anonymized                     U    not further specialized

				
DOCUMENT INFO