| ITI47 | ITI47-1 | to be reviewed | Testable |
0
|
0
| | Implementers of the Patient Demographics Query HL7 V3 [ITI-47] transaction shall comply with the requirements described in HL7 Version 3 Edition 2008, Patient Administration DSTU, Patient Topic (found at http://www.hl7.org/memonly/downloads/v3edition.cfm#V32008) | 248 | Section 3.47.3 | 1/29/19 2:23:58 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-10 | to be reviewed | Testable |
0
|
0
| | The messages exchanged in the context of the Patient Demographics Query HL7 V3 [ITI-47] transaction will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. | 256 | Section 3.47.4.1.2.4 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-11 | to be reviewed | Testable |
0
|
0
| | The following WSDL naming conventions SHALL apply:
query message -> "PRPA_IN201305UV02_Message" | 256 | Section 3.47.4.1.2.4 | 1/29/19 2:23:58 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-12 | to be reviewed | Testable |
0
|
0
| | The Patient Demographics Supplier shall be capable of accepting, searching on, and responding with attributes in the Query Person by Demographics message | 257 | Section 3.47.4.1.3.2 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-13 | to be reviewed | Testable |
0
|
0
| | The Supplier shall return at least all exact matches to the query parameters sent by the Consumer; | 257 | Section 3.47.4.1.3.2 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-14 | to be reviewed | Testable |
0
|
0
| | The Patient Demographics Supplier shall be capable of accepting, searching on, and responding with attributes in the Query Person by Demographics message. | 257 | Section 3.47.4.1.3.2 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-14b | to be reviewed | Testable |
0
|
0
| | If a number of records is specified in the initialQuantity of the original quantity, and the Patient Demographics Supplier supports the Continuation Option, the Patient Demographics Supplier Actor shall return an incremental response of that number of records when the number of matching records it finds exceeds the number of records specified | 271 | Section 3.47.4.3.3 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-15 | to be reviewed | Testable |
0
|
0
| | The Patient Demographics Supplier, which supports the Continuation Option, shall respond in immediate mode. | 257 | Section 3.47.4.1.3.3 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-16 | to be reviewed | Testable |
0
|
0
| | The Patient Demographics Supplier, which supports the Continuation Option, shall be able to interpret QueryByParameter.initialQuantity to return successive responses of partial lists of records | 257 | Section 3.47.4.1.3.3 | 1/29/19 2:23:58 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-17 | to be reviewed | Testable |
0
|
0
| | When processing incremental responses, the Patient Demographics Consumer shall request additional responses using the Query Control Act Request Continue/Cancel message (QUQI_MT000001UV01), as described in ITI TF-2b: 3.47.4.3 | 257 | Section 3.47.4.1.3.3 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-18 | to be reviewed | Testable |
0
|
0
| | The Patient Demographics Suppliers response to the Find Candidates Query message is triggered by the following trigger:
Find Candidates Response (PRPA_TE201306UV02) | 257 | Section 3.47.4.2.1 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-19 | to be reviewed | Testable |
0
|
0
| | An application returns a Patient Registry Find Candidates Response message populated with information it holds for each person whose record matches the demographic information sent as parameters in a query-by-parameter message | 257 | Section 3.47.4.2.1 | 3/20/15 11:59:23 AM by Abderrazek Boufahja |
|
| ITI47 | ITI47-2 | to be reviewed | Testable |
0
|
0
| | Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions | 248 | Section 3.47.3 | 1/29/19 2:23:58 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-21 | to be reviewed | Testable |
0
|
0
| | The components of the Patient Registry Find Candidates Response message (PRPA_MT201310UV02) with cardinality greater than 0 (as shown in Figure 3.47.4.2.2-1) are required | 258 | Section 3.47.4.2.2 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-22 | to be reviewed | Testable |
0
|
0
| | The Patient Demographics Supplier finds (in the patient information source associated with Receiver.Device in the query transmission wrapper) at least one patient record matching the criteria sent in the query parameters. There were no OtherIDsScopingOrganization parameters in the query.
AA (application accept) is returned in Acknowledgement.typeCode (transmission wrapper).
OK (data found, no errors) is returned in QueryAck.queryResponseCode (control act wrapper)
One RegistrationEvent (and the associated Patient role, subject of that event) is returned from the patient information source for each patient record found. If the Patient Demographics Supplier returns data for multiple patients, it shall return these data in successive occurrences of the RegistrationEvent class within the transmission wrapper.
For each patient, one or more identifiers from the Patient ID Domain associated with the target patient information source identified by Receiver.Device are represented as Patient.id attributes.
If an incremental number of records are specified in QueryByParamter.initialQuantity (i.e., the Consumer supports the Continuation Option), and the number of records to be sent exceeds that incremental number, the Supplier shall return only up to the incremental number of records. If the Supplier supports the Continuation Option, it shall correctly populate the resultTotalQuantity, resultCurrentQuantity, and resultRemainingQuantity attributes of the QueryAck class in the control act wrapper. If the Supplier does not support the Continuation Option, in addition to returning only up to the incremental number of records requested, it shall return AE (application error in the Acknowledgement.typeCode (transmission wrapper) and AE (application error) is returned in QueryAck.queryResponseCode (control act wrapper).
The Consumer may then send a query continuation message as a subsequent query request for the next increment of responses. | 265 | Section 3.47.4.2.3 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-23 | to be reviewed | Testable |
0
|
0
| | The Patient Demographics Supplier finds (in the patient information source associated with Receiver.Device in the query transmission wrapper) at least one patient record matching the criteria sent in the query parameters. One or more OtherIDsScopingOrganization parameters are present in the query; the Supplier recognizes all the requested domains.
AA (application accept) is returned in Acknowledgement.typeCode (transmission wrapper).
OK (data found, no errors) is returned in QueryAck.queryResponseCode (control act wrapper)
One RegistrationEvent (and the associated Patient role, subject of that event) is returned from the patient information source for each patient record found. If the Patient Demographics Supplier returns data for multiple patients, it shall return these data in successive occurrences of the RegistrationEvent class within the transmission wrapper.
For each patient, the identifiers from all the Patient ID Domains requested via the OtherIDsScopingOrganization parameter are returned either as values of the Patient.id attribute, or as values of the OtherIDs.idattribute. The same patient identifier value shall not appear in both the Patient.id and OtherIDs.id attributes. The Patient Demographics consumer shall consider the identifiers from both places as equivalently valid. If the Patient Demographics supplier cannot provide a patient ID for some of the requested Patient ID Domains, then an OtherIDs.id attribute shall have an appropriate null value, and the ScopingOrganization class shall identify the corresponding domain.
If an incremental number of records are specified in QueryByParamter.initialQuantity, and the number of records to be sent exceeds that incremental number, and the Patient Demographics Supplier supports the Continuation Option, the Supplier returns only the incremental number of records, correctly populating the resultTotalQuantity, resultCurrentQuantity, and resultRemainingQuantity attributes of the QueryAck class in the control act wrapper. The consumer will sent a query continuation message as a subsequent query request for the next increment of responses. If the Supplier does not support the Continuation Option, then AE (application error) is returned in the Acknowledgement.typeCode (transmission wrapper) and AE (application error) is returned in QueryAck.queryResponseCode (control act wrapper). | 265 | Section 3.47.4.2.3 | 1/29/19 2:23:58 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-24 | to be reviewed | Testable |
0
|
0
| | The Patient Demographics Supplier does not recognize one or more OtherIDsScopingOrganization parameters as representing valid Patient Identity Domains.
AE (application error) is returned in Acknowledgement.typeCode (transmission wrapper) and in QueryAck.queryResponseCode (control act wrapper).
No RegistrationEvent is returned.
The queried-for patient identification domains are returned in the QueryByParameter parameter list (control act wrapper).
For each domain that was not recognized, an AcknowledgmentDetail class is returned in which the attributes typeCode, code, and location are valued as follows:
- typeCode: E
- code: 204
- Location: XPath expression for the value element of the OtherIDsScopingOrganization parameter
(which includes the repetition number of the parameter) | 257 | Section 3.47.4.1.3.3 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-25 | to be reviewed | Testable |
0
|
0
| | The following WSDL naming conventions SHALL apply:
wsdl:definitions/@name="PDSupplier":
patient demographics query -> "PRPA_IN201305UV02_Message"
patient demographics response ->"PRPA_IN201306UV02_Message"
continuation query ->"QUQI_IN000003UV01_Message"
accept acknowledgement -> "MCCI_IN000002UV01_Message"
portType -> "PDSupplier_PortType"
get candidates operation -> "PDSupplier_PRPA_IN201305UV02"
continuation operation -> "PDSupplier_PRPA_IN201305UV02_Continue"
cancel operation -> "PDSupplier_PRPA_IN201305UV02_Cancel"
SOAP 1.2 binding -> "PDSupplier_Binding_Soap12"
SOAP 1.2 port -> "PDSupplier_Port_Soap12" | 267 | Section 3.47.4.2.3.1 | 1/29/19 2:23:58 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-26 | to be reviewed | Testable |
0
|
0
| | A Patient Demographics Consumers need to get another set of matching records to a previously sent Patient Demographics query will trigger the Patient Demographics Query Continuation based on the following HL7 trigger event:
Query General Activate Query Continuation (QUQI_TE000003UV01) | 268 | Section 3.47.4.3.1 | 1/29/19 2:23:47 PM by Abderrazek Boufahja |
|
| ITI47 | ITI47-27 | to be reviewed | Testable |
0
|
0
| | The Query continuation is supported by the Query Control Act Request Continue / Cancel (QUQI_MT000001UV01) message. The Patient Demographics Consumer shall generate the continuation message whenever it needs to receive another set of matching records based on the results of a previously sent query. | 269 | Section 3.47.4.3.2 | 1/29/19 2:23:58 PM by Abderrazek Boufahja |
|