net.ihe.gazelle.assets.SearchCriteria : 53 assertions found for this search Review filtered assertions

Assertion

Applies to

Applied to
Not applied to

Coverage

Covered by
Not covered by
Id scheme
Assertion id
Status
Testable?
#Coverage
#Applies to
Comment
Predicate
Page
Tags
Last changed
Actions
ITI45ITI45-1reviewedTestable 1 1 PIXV3 Query [ITI-45] transaction references the following standard HL7 Version 3 Edition 2008 Patient Administration DSTU, Patient Topic (found at http://www.hl7.org/memonly/downloads/v3edition.cfm#V32008)217Section 3.45.35/29/19 1:47:12 PM by aberge
ITI45ITI45-10reviewedTestable 1 2 The Patient Registry Query by Identifier message and response will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V. 222Section 3.45.4.1.2.45/29/19 1:47:20 PM by aberge
ITI45ITI45-11reviewedTestable 0 2 The following WSDL naming conventions SHALL apply: Query by Identifier -> "PRPA_IN201309UV02_Message" Query Response -> "PRPA_IN201310UV02_Message"222Section 3.45.4.1.2.45/2/19 5:01:46 PM by wbars
ITI45ITI45-12reviewedTestable 0 2 The Patient Identifier Cross-reference Manager shall be capable of accepting attributes as specified in Table 3.45.4.1.2-1223Section 3.45.4.1.35/2/19 5:01:49 PM by wbars
ITI45ITI45-13validatedTestable 0 2 The Patient Identifier Cross-reference Manager shall be capable of accepting multiple concurrent PIX Query requests (Get Corresponding Identifiers messages) and responding correctly using the Return Corresponding Identifiers message.223Section 3.45.4.1.35/2/19 5:01:54 PM by wbars
ITI45ITI45-14reviewedTestable 0 2 The following WSDL naming conventions SHALL apply: wsdl:definitions/@name="PIXManager": "get identifiers" query -> "PRPA_IN201309UV02_Message" "get identifiers" response ->"PRPA_IN201310UV02_Message" portType -> "PIXManager_PortType" get identifiers operation -> "PIXManager_PRPA_IN201309UV02" SOAP 1.2 binding -> "PIXManager_Binding_Soap12" SOAP 1.2 port -> "PIXManager_Port_Soap12"223Section 3.45.4.1.3.15/2/19 5:01:59 PM by wbars
ITI45ITI45-15reviewedTestable 0 2 The Patient Identifier Cross-reference Managers response to the Get Corresponding Identifiers message will trigger the following message:Patient Registry Get Identifiers Query Response (PRPA_TE201310UV02) This query response returns all other identifiers associated with a particular person identifier.224Section 3.45.4.25/2/19 5:02:04 PM by wbars
ITI45ITI45-17reviewedTestable 0 2 The Patient Identifier Cross-reference Manager shall return the attributes within the HL7 Patient Identifiers message (PRPA_MT201304UV02) that are required by the HL7 standard, as shown in Figure 3.45.4.2.2-1.228Section 3.45.4.2.35/2/19 5:02:08 PM by wbars
ITI45ITI45-18reviewedTestable 1 2 The Patient Identifier Cross-reference Manager recognizes the specified Patient ID sent by the Patient Identifier Cross-reference Consumer in PatientIdentifier.value, and corresponding identifiers exist for the specified patient in at least one of the domains requested in DataSource.value (one identifier per domain). (See Case 6 below for the required behavior if there are multiple identifiers recognized within a given Identifier Domain by the Patient Identifier Cross-reference Manager.)AA (application accept) is returned in Acknowledgement.typeCode (transmission wrapper).OK (data found, no errors) is returned in QueryAck.queryResponseCode (control act wrapper).A single RegistrationEvent class is returned, where at least one of the identifiers, which the Patient Identifier Cross-reference Manager did recognize as belonging to a requested domain, is returned in Patient.id. Subsequent such identifiers, if any, are returned in either Patient.id or OtherIDs.id, not including the queried-for patient identifier that is returned in the QueryByParameter parameter list (control act wrapper). 228Section 3.45.4.2.36/6/19 9:09:19 AM by aberge
ITI45ITI45-19reviewedTestable 0 2 The Patient Identifier Cross-reference Manager recognizes the specified Patient ID sent by the Patient Identifier Cross-reference Consumer in PatientIdentifier.value, there are no specific domains requested in the query (no DataSource parameters are present), and corresponding identifiers exist for the specified patient in at least one other domain known to the Patient Identifier Cross-reference Manager (one identifier per domain).AA (application accept) is returned in Acknowledgement.typeCode (transmission wrapper).OK (data found, no errors) is returned in QueryAck.queryResponseCode (control act wrapper).A single RegistrationEvent class is returned, where at least one of the identifiers, which the Patient Identifier Cross-reference Manager did recognize as belonging to a domain different from the domain of the queried-for patient identifier, is returned in Patient.id. Subsequent such identifiers, if any, are returned in either Patient.id or OtherIDs.id, not including the queried-for patient identifier, which is returned in the QueryByParameter parameter list (control act wrapper).228Section 3.45.4.2.35/2/19 5:02:19 PM by wbars
ITI45ITI45-2reviewedTestable 0 3 Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V Web Services for IHE Transactions217Section 3.45.35/2/19 5:00:52 PM by wbars
ITI45ITI45-20reviewedTestable 1 2 The Patient Identifier Cross-reference Manager recognizes the specified Patient ID sent in PatientIdentifier.value, but no identifier exists for that patient in any of the domains sent in DataSource.value. AA (application accept) is returned in Acknowledgement.typeCode (transmission wrapper).NF (no data found, no errors) is returned in QueryAck.queryResponseCode (control act wrapper).No RegistrationEvent is returned.The queried-for patient identifier is returned in the QueryByParameter parameter list (control act wrapper). 228Section 3.45.4.2.36/6/19 9:09:49 AM by aberge
ITI45ITI45-21reviewedTestable 1 2 The Patient Identifier Cross-reference Manager does not recognize the Patient ID sent in the PatientIdentifier.value.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 identifier is returned in the QueryByParameter parameter list (control act wrapper).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 PatientIdentifier parameter228Section 3.45.4.2.36/6/19 9:10:12 AM by aberge
ITI45ITI45-22reviewedTestable 1 2 The Patient Identifier Cross-reference Manager does not recognize one or more of the Patient Identification Domains for which an identifier has been requested.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 DataSource parameter(which includes the repetition number of the parameter)228Section 3.45.4.2.36/6/19 9:10:48 AM by aberge
ITI45ITI45-23reviewedTestable 1 2 The Patient Identifier Cross-reference Manager recognizes the specified Patient ID sent by the Patient Identifier Cross-reference Consumer in PatientIdentifier.value, and corresponding identifiers exist for the specified patient in at least one of the domains requested in DataSource.value, and there are multiple identifiers within at least one of 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)A single RegistrationEvent class is returned, where at least one of the identifiers, which the Patient Identifier Cross-reference Manager did recognize as belonging to a requested domain, is returned in Patient.id. Subsequent such identifiers, if any, are returned in either Patient.id or OtherIDs.id, not including the queried-for patient identifier that is returned in the QueryByParameter parameter list (control act wrapper). If the Patient Identifier Cross-reference Manager chooses to return multiple identifiers associated with the same domain, it shall return these identifiers either grouped in a single instance of the OtherIDs class, or all represented via repetitions of the Patient.id attribute.228Section 3.45.4.2.36/6/19 9:11:16 AM by aberge
ITI45ITI45-24reviewedTestable 0 2 The identifiers found in both Patient.id and OtherIDs.id attributes shall be considered together to form a complete list of patient identifiers from the different Patient Identity domains (either requested or available).230Section 3.45.4.2.45/2/19 5:02:59 PM by wbars
ITI45ITI45-25reviewedTestable 0 2 In the case where the returned list of identifiers contains multiple identifiers for a single domain, the Patient Identifier Cross-reference Consumer shall either use ALL of the multiple identifiers from the given domain or it shall ignore ALL of the multiple identifiers from the given domain.230Section 3.45.4.2.45/2/19 5:03:05 PM by wbars
ITI45ITI45-26reviewedTestable 1 3 When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Query Information event. Audit message produced by the Patient Identifier Cross-reference Consumer actor shall follow the rules defined in section 3.45.5.1.1231Section 3.45.5.18/26/19 5:25:26 PM by aberge
ITI45ITI45-27reviewedTestable 1 3 When grouped with ATNA Secure Node or Secure Application actors, this transaction is to be audited as Query Information event. Audit message produced by the Patient Identifier Cross-reference Manager actor shall follow the rules defined in section 3.45.5.1.2231Section 3.45.5.18/26/19 5:25:26 PM by aberge
ITI45ITI45-3reviewedTestable 1 2 A Patient Identifier Cross-reference Consumers need to get the patient identifier associated with a domain for which it needs patient related information shall trigger the request for corresponding patient identifiers message based on the following HL7 trigger event: Patient Registry Get Identifiers Query (PRPA_TE201309UV02) 218Section 3.45.4.1.15/29/19 1:49:35 PM by aberge