Id

12983

Keyword

PDQv3_Multiple_Query

Name

PDQv3_Multiple_Query

Version

EPR Den Haag 2018

Test Author

r.hilary

Last modifier

sthiam

Status

ready

Type

connectathon

Is external tool ?

Is Orchestrable

is Validated ?

Peer Type

Peer To Peer

Test permanent link

https://ehealthsuisse.ihe-europe.net/gazelle/test.seam?id=12983

Short Description

PDQv3 Multiple Query

Last changed

4/4/22 2:53:51 PM

Short Description

Query multiple Patient Demographics from a PDQ Supplier 

Goal

This test verifies the required steps to retrieve Patient Demographics with different Search queries

Test Components

• PDQ Consumers
• PDQ Supplier 

The PDQv3_Multiple_Query test requires PDQ Consumers to send different types of queries to a PDQ Supplier. Some PDQ Consumers may not have user interfaces that support all of the intended queries.

Each query (Using the HL7v3 Patient Registry Find Candidates Query) is made assuming a single domain Assigning Authority that can be specified with an empty value in the DataSource.value attribute. 

The PDQ Consumer SHALL perform the Queries with the following attributes:

Query 1

• LivingSubjectName.value
  

If your application does not query by exact name, you should demonstrate a different query that retrieves this one patient record.

Query 2 

• LivingSubjectName.value
• LivingSubjectBirthTime
  

The following steps are marked "Optional". That doesn't mean you should skip them. We want you to demonstrate the ability to send a query with multiple different query keys:

Query 3

• LivingSubjectName.value
  
• use="SRCH" for a non-exact match

Query 4

• LivingSubjectId
  
• OtherIDsScopingOrganization
  
• You may include another demographic fields.

Query 5

• LivingSubjectBirthTime

Query 6

• LivingSubjectName.value
• LivingSubjectAdministrativeGender.value
  
• use="SRCH" for a non-exact match

Query 7

• LivingSubjectName.value
  
• PatientAddress
  

Evidence

The PDQ Supplier is required to support queries with the attributes listed below. Not all Consumers will support all queries. Evaluate as many query combinations as are supported by the Consumer.

• LivingSubjectId
• LivingSubjectName
• LivingSubjectBirthTime
• LivingSubjectAdministrativeGender
• Patient.Address
• OtherIDsScopingOrganization (ie the Assigning Authority)

The PDQ Supplier is required to support at least all exact matches to the query parameters sent by the Consumer. The Technical Framework does not further specify matching requirements (eg wildcards, upper and lower case, alternate spellings')

Evaluation

Ideally, the Connectathon monitor can observe all queries in real time and evaluate the response.

Additionally, the gazelle proxy offers the opportunity to examine messages in the exchange between Consumer and Supplier.