Performing PIX and PDQ Queries Against an EMPI

The following diagram is an annotated PIX query message trace.

The test service shown in the diagram is a simple message router. Trace operations is a utility that makes intermediate processing steps visible. The numbers in the diagram match the steps in the procedure below.

1. You provide a Patient Search RequestOpens in a new tab message containing an MRN and assigning authority to the InterSystems PIX Consumer operation.

2. The InterSystems PIX Consumer operation transforms the message into an IHE “PIXv3_QueryRequest” using the transformation specified in the TransformPatientSearchToPIX setting.

3. The InterSystems PIX Consumer operation then forwards the PIX request to the service named in the ServiceName setting. This setting is typically PIXv3.Manager, and it refers to a Service Registry entry pointing to the location of the PIX manager actor endpoint in another system.

4. The PIX manager on the other system returns a PIX response message that contains the name and MPI ID for a single patient if there is a match.

5. The InterSystems PIX Consumer operation transforms the response into a Patient Search ResponseOpens in a new tab message using the transformation specified in TransformPIXToPatientSearch.

6. The InterSystems PIX Consumer returns the Patient Search ResponseOpens in a new tab message, which contains the name and MPI ID of the patient, if found. If no patient is found, the response message indicates a <ResultsCount> of zero. If there is an error, the PIX Consumer returns null.

The method below generates a PIX query:

 ClassMethod PIXQuery()
  {
     /// Create Patient Search Request message 
     Set obj=##class(HS.Message.PatientSearchRequest).%New()

     //Provide the Patient MRN
     Set obj.AssigningAuthority="EXTERNAL" //refers to an Assigning Authority entry in the OID Registry
     Set obj.MRN="1111222"

     // Send to the routing service (or directly to HS.IHE.PIXv3.Consumer.Operations)
     Do ##class(HS.Test.Service).SendSync(obj,.pr)

     quit
  }

The following diagram is an annotated PDQ query message trace.

The test service shown in the diagram is a simple message router. Trace operations is a utility that makes intermediate processing steps visible in the trace. The numbers in the diagram match the steps in the procedure below.

1. You provide a Patient Search RequestOpens in a new tab message containing partial demographics to the InterSystems PDQ Consumer.

2. The InterSystems PDQ Consumer transforms the message into an IHE “PDQv3_QueryRequest” using the transformation specified in the TransformPatientSearchToPDQ setting.

3. The InterSystems PDQ Consumer then forwards the PDQ request to the PDQ supplier endpoint on another system that is named in the ServiceName setting.

4. The PDQ supplier on the other system returns a PDQ response message that contains the complete demographics for all patients that match the supplied partial demographics.

5. The InterSystems PDQ Consumer transforms the response into a Patient Search ResponseOpens in a new tab message using the transformation specified in the TransformPDQToPatientSearch setting.

6. The InterSystems PDQ Consumer returns the Patient Search ResponseOpens in a new tab message, which contains the full demographics and MPI IDs of the matching patients. If no patient is found, the response message indicates a <ResultsCount> of zero. If there is an error, the PDQ Consumer returns null.

The method below generates a PDQ query:

 ClassMethod PDQQuery()
  {
     // Create Patient Search Request message 
     Set obj=##class(HS.Message.PatientSearchRequest).%New()
 
     // Provide patient demographics
     Set obj.FirstName="James"
     Set obj.LastName="Smith"
 
     // Required only for HS.Test.Service to distinguish between PIX/PDQ
     Do obj.AdditionalInfo.SetAt(1,"PDQ")
 
     // Send to the routing service (or directly to HS.IHE.PDQv3.Consumer.Operations)
     Do ##class(HS.Test.Service).SendSync(obj,.sr)
 
     quit
  }