Home » Archived » OHF » OHF Bridge Mesa test 10501
| |
| Re: OHF Bridge Mesa test 10501 [message #34371 is a reply to message #34204] |
Mon, 08 October 2007 19:27   |
 Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi Sondra,
Ah, I didn't really know what that parameter was for. I assumed it meant
whether I wanted the results returned with or without demographics
information- so I set it to false to indicate I wanted demographics
information :-) Now I understand its use.
So I set it to true and tested and got an error in the bridge:
[DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixPdqMessage:
changeDefaultRecievingFacility
[DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixMsgADT: setField
QPD-3-5 :
QPD-3
[ERROR][12:14:44][clipse.ohf.bridge.ws.OHFBridge] failed at SearchPatient
java.lang.NullPointerException
at
org.eclipse.ohf.ihe.common.hl7v2.message.PixPdqMessage.setFi eld(PixPd
qMessage.java:385)
at
org.eclipse.ohf.bridge.ihe.pixpdq.IhePatientConsumerBridge.c reatePixC
onsumerQuery(IhePatientConsumerBridge.java:184)
I saw a similar problem regarding setting "QPD-3-5" when reading over the
more recent posts on this newsgroup last week. I just reread and see that
you and Graham fixed it. The last time I tried pulling the source trunk,
I couldn't get it to compile. I ended up pulling the branch/tag
"OHF_IHE_POST_2007EUCTHON" which was a lot easier to get running. So, the
fix you guys made, is it in the trunk or is there a branch you're working
on?
thanks,
Jesse
Sondra Renly wrote:
> Hi Jesse,
> One note I want to add is that the bridge has mesa test junits you can
> reference under project org.eclipse.ohf.bridge.ws. This can provide some
> guidance.
> The distinction to do pix vs pdq is based on a flag in the bridge,
> method "setWithoutDemographics". If this flag is set to true, it will
> perform a pix query. If this flag is set to false, it will perform a pdq
> query. The default is false and I suspect this is your problem.
> Sondra
> Jesse Pangburn wrote:
>> Hi,
>> I'm trying to do the first MESA PIX test "10501" using the bridge, but
>> I'm getting an error. It appears to be trying to do a PDQ query instead
>> of a PIX query, though I'm pretty new to IHE so that may be a
>> misunderstanding on my part.
>>
>> I'm sending the following XML to the bridge:
>> <SOAP-ENV:Envelope
>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:tns1="http://ws.bridge.ohf.eclipse.org"
>> xmlns:tns2="http://type.bridge.ohf.eclipse.org"
>> xmlns:impl="http://localhost/bridge/services/ohf-bridge-wrapped">
>> <SOAP-ENV:Body>
>> <tns1:SearchPatient>
>> <tns1:sessionContext>
>> <tns2:returnLogLevel>WARN</tns2:returnLogLevel>
>> <tns2:rhioName>mesa</tns2:rhioName>
>> <tns2:sessionID>1111</tns2:sessionID>
>>
>>
<tns2:useSecuredConnectionWhenAvaliable>true</tns2:useSecuredConnectionWhenAvaliable >
>>
>> <tns2:user>patientsearcher</tns2:user>
>> <tns2:userApplicationName/>
>> <tns2:userFacilityName/>
>> </tns1:sessionContext>
>> <tns1:patientInfo>
>> <tns2:genericAdtValues>
>> <impl:item>
>> <tns2:data/>
>> <tns2:path/>
>> </impl:item>
>> </tns2:genericAdtValues>
>> <tns2:patientAddress>
>> <tns2:city/>
>> <tns2:country/>
>> <tns2:countyParishCode/>
>> <tns2:otherDesignation/>
>> <tns2:stateOrProvince/>
>> <tns2:streetAddress/>
>> <tns2:zipOrPostalCode/>
>> </tns2:patientAddress>
>> <tns2:patientDateOfBirth/>
>> <tns2:patientIdentifier>
>> <tns2:assigningAuthorityType>
>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>
>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>
>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>
>>
<tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>>
>> </tns2:assigningAuthorityType>
>> <tns2:idNumber>PIX10501</tns2:idNumber>
>> </tns2:patientIdentifier>
>> <tns2:patientName>
>> <tns2:familyName/>
>> <tns2:givenName/>
>> <tns2:otherName/>
>> <tns2:prefix/>
>> <tns2:suffix/>
>> </tns2:patientName>
>> <tns2:patientPhoneBusiness>
>> <tns2:unformattedTelephoneNumber/>
>> </tns2:patientPhoneBusiness>
>> <tns2:patientPhoneHome>
>> <tns2:unformattedTelephoneNumber/>
>> </tns2:patientPhoneHome>
>> <tns2:patientSex/>
>> </tns1:patientInfo>
>> <tns1:queryPreferences>
>> <tns2:domainsReturned>
>> <impl:item>
>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>
>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>
>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>
>>
<tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>>
>> </impl:item>
>> </tns2:domainsReturned>
>> <tns2:quantityLimit>1</tns2:quantityLimit>
>> <tns2:withoutDemographics>false</tns2:withoutDemographics>
>> </tns1:queryPreferences>
>> </tns1:SearchPatient>
>> </SOAP-ENV:Body>
>> </SOAP-ENV:Envelope>
>>
>> I get back:
>> <soapenv:Envelope
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>> <soapenv:Body>
>> <SearchPatientResponse xmlns="http://ws.bridge.ohf.eclipse.org">
>> <SearchPatientReturn>
>> <ns1:failMessage
>> xmlns:ns1="http://type.bridge.ohf.eclipse.org"> Error location:
>> QPD^1^3^1^4^ Error code: 204 Error severity: Warning</ns1:failMessage>
>> <ns2:log xmlns:ns2="http://type.bridge.ohf.eclipse.org"/>
>> <ns3:sessionID
>> xmlns:ns3="http://type.bridge.ohf.eclipse.org">1111</ns3:sessionID>
>> <ns4:success
>> xmlns:ns4="http://type.bridge.ohf.eclipse.org">false</ns4:success>
>> <ns5:successMessage
>> xmlns:ns5="http://type.bridge.ohf.eclipse.org"/>
>> <ns6:patients xsi:nil="true"
>> xmlns:ns6="http://type.bridge.ohf.eclipse.org"/>
>> </SearchPatientReturn>
>> </SearchPatientResponse>
>> </soapenv:Body>
>> </soapenv:Envelope>
>>
>> Tracing the network shows that the bridge sends the following HL7:
>>
MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|20071005 133800-0700||QBP^Q22^QBP_Q21|0886784820993939999|P|2.5
>>
>> QPD|QRY_PDQ_1001^Query By
>>
Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO
>>
>> RCP|I|1^RD
>>
>> The mesa PIX server replies:
>>
MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|||RSP^K2 3|MESA4706a0c4|P|2.5||||||||
>>
>> MSA|AE|0886784820993939999||||
>> ERR||QPD^1^3^1^4|204|W||
>> QAK|1903342086890395431720417949101|AE
>> QPD|QRY_PDQ_1001^Query By
>> Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||
>>
>> My rhio config has the same entry for the pix as I used to successfully
>> test against the IBM PIX Manager except the url is to a local machine
>> (the one running the mesa server):
>> <pix>
>> <id>mesa</id>
>> <mllp>
>> <unsecured>mllp://192.168.1.127:3600</unsecured>
>> </mllp>
>> <pixServerPropertiesId>IBM PIX Server</pixServerPropertiesId>
>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>> <defaultMessageQueryNameId>IHEDEMO</defaultMessageQueryNameId >
>> </pix>
>>
>> Any ideas? Is the bridge even supposed to do PIX queries or just PDQ?
>>
>> thanks,
>> Jesse
>>
|
|
|
| Re: OHF Bridge Mesa test 10501 [message #34405 is a reply to message #34371] |
Mon, 08 October 2007 19:40 |
Sondra Renly
Messages: 39
Registered: July 2009 |
Member |
|
|
The update was made in trunk -
Update Segment.java from current which is the real fix is in Grahame's
HL7v2 code. The posted change in PixConsumerQuery is a temp workaround.
Sondra
Jesse Pangburn wrote:
> Hi Sondra,
> Ah, I didn't really know what that parameter was for. I assumed it
> meant whether I wanted the results returned with or without demographics
> information- so I set it to false to indicate I wanted demographics
> information :-) Now I understand its use.
>
> So I set it to true and tested and got an error in the bridge:
> [DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixPdqMessage:
> changeDefaultRecievingFacility
> [DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixMsgADT: setField
> QPD-3-5 :
> QPD-3
> [ERROR][12:14:44][clipse.ohf.bridge.ws.OHFBridge] failed at SearchPatient
> java.lang.NullPointerException
> at
> org.eclipse.ohf.ihe.common.hl7v2.message.PixPdqMessage.setFi eld(PixPd
> qMessage.java:385)
> at
> org.eclipse.ohf.bridge.ihe.pixpdq.IhePatientConsumerBridge.c reatePixC
> onsumerQuery(IhePatientConsumerBridge.java:184)
>
> I saw a similar problem regarding setting "QPD-3-5" when reading over
> the more recent posts on this newsgroup last week. I just reread and
> see that you and Graham fixed it. The last time I tried pulling the
> source trunk, I couldn't get it to compile. I ended up pulling the
> branch/tag "OHF_IHE_POST_2007EUCTHON" which was a lot easier to get
> running. So, the fix you guys made, is it in the trunk or is there a
> branch you're working on?
>
> thanks,
> Jesse
>
>
> Sondra Renly wrote:
>
>> Hi Jesse,
>
>> One note I want to add is that the bridge has mesa test junits you can
>> reference under project org.eclipse.ohf.bridge.ws. This can provide
>> some guidance.
>
>> The distinction to do pix vs pdq is based on a flag in the bridge,
>> method "setWithoutDemographics". If this flag is set to true, it will
>> perform a pix query. If this flag is set to false, it will perform a
>> pdq query. The default is false and I suspect this is your problem.
>
>
>> Sondra
>
>
>> Jesse Pangburn wrote:
>>> Hi,
>>> I'm trying to do the first MESA PIX test "10501" using the bridge,
>>> but I'm getting an error. It appears to be trying to do a PDQ query
>>> instead of a PIX query, though I'm pretty new to IHE so that may be a
>>> misunderstanding on my part.
>>>
>>> I'm sending the following XML to the bridge:
>>> <SOAP-ENV:Envelope
>>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:tns1="http://ws.bridge.ohf.eclipse.org"
>>> xmlns:tns2="http://type.bridge.ohf.eclipse.org"
>>> xmlns:impl="http://localhost/bridge/services/ohf-bridge-wrapped">
>>> <SOAP-ENV:Body>
>>> <tns1:SearchPatient>
>>> <tns1:sessionContext>
>>> <tns2:returnLogLevel>WARN</tns2:returnLogLevel>
>>> <tns2:rhioName>mesa</tns2:rhioName>
>>> <tns2:sessionID>1111</tns2:sessionID>
>>>
> <tns2:useSecuredConnectionWhenAvaliable>true</tns2:useSecuredConnectionWhenAvaliable >
>
>>>
>>> <tns2:user>patientsearcher</tns2:user>
>>> <tns2:userApplicationName/>
>>> <tns2:userFacilityName/>
>>> </tns1:sessionContext>
>>> <tns1:patientInfo>
>>> <tns2:genericAdtValues>
>>> <impl:item>
>>> <tns2:data/>
>>> <tns2:path/>
>>> </impl:item>
>>> </tns2:genericAdtValues>
>>> <tns2:patientAddress>
>>> <tns2:city/>
>>> <tns2:country/>
>>> <tns2:countyParishCode/>
>>> <tns2:otherDesignation/>
>>> <tns2:stateOrProvince/>
>>> <tns2:streetAddress/>
>>> <tns2:zipOrPostalCode/>
>>> </tns2:patientAddress>
>>> <tns2:patientDateOfBirth/>
>>> <tns2:patientIdentifier>
>>> <tns2:assigningAuthorityType>
>>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>>
>>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>>
>>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>>
> <tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>
>>>
>>> </tns2:assigningAuthorityType>
>>> <tns2:idNumber>PIX10501</tns2:idNumber>
>>> </tns2:patientIdentifier>
>>> <tns2:patientName>
>>> <tns2:familyName/>
>>> <tns2:givenName/>
>>> <tns2:otherName/>
>>> <tns2:prefix/>
>>> <tns2:suffix/>
>>> </tns2:patientName>
>>> <tns2:patientPhoneBusiness>
>>> <tns2:unformattedTelephoneNumber/>
>>> </tns2:patientPhoneBusiness>
>>> <tns2:patientPhoneHome>
>>> <tns2:unformattedTelephoneNumber/>
>>> </tns2:patientPhoneHome>
>>> <tns2:patientSex/>
>>> </tns1:patientInfo>
>>> <tns1:queryPreferences>
>>> <tns2:domainsReturned>
>>> <impl:item>
>>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>>
>>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>>
>>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>>
> <tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>
>>>
>>> </impl:item>
>>> </tns2:domainsReturned>
>>> <tns2:quantityLimit>1</tns2:quantityLimit>
>>>
>>> <tns2:withoutDemographics>false</tns2:withoutDemographics>
>>> </tns1:queryPreferences>
>>> </tns1:SearchPatient>
>>> </SOAP-ENV:Body>
>>> </SOAP-ENV:Envelope>
>>>
>>> I get back:
>>> <soapenv:Envelope
>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>>> <soapenv:Body>
>>> <SearchPatientResponse xmlns="http://ws.bridge.ohf.eclipse.org">
>>> <SearchPatientReturn>
>>> <ns1:failMessage
>>> xmlns:ns1="http://type.bridge.ohf.eclipse.org"> Error location:
>>> QPD^1^3^1^4^ Error code: 204 Error severity: Warning</ns1:failMessage>
>>> <ns2:log
>>> xmlns:ns2="http://type.bridge.ohf.eclipse.org"/>
>>> <ns3:sessionID
>>> xmlns:ns3="http://type.bridge.ohf.eclipse.org">1111</ns3:sessionID>
>>> <ns4:success
>>> xmlns:ns4="http://type.bridge.ohf.eclipse.org">false</ns4:success>
>>> <ns5:successMessage
>>> xmlns:ns5="http://type.bridge.ohf.eclipse.org"/>
>>> <ns6:patients xsi:nil="true"
>>> xmlns:ns6="http://type.bridge.ohf.eclipse.org"/>
>>> </SearchPatientReturn>
>>> </SearchPatientResponse>
>>> </soapenv:Body>
>>> </soapenv:Envelope>
>>>
>>> Tracing the network shows that the bridge sends the following HL7:
>>>
> MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|20071005 133800-0700||QBP^Q22^QBP_Q21|0886784820993939999|P|2.5
>
>>>
>>> QPD|QRY_PDQ_1001^Query By
> Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO
>
>>>
>>> RCP|I|1^RD
>>>
>>> The mesa PIX server replies:
>>>
> MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|||RSP^K2 3|MESA4706a0c4|P|2.5||||||||
>
>>>
>>> MSA|AE|0886784820993939999||||
>>> ERR||QPD^1^3^1^4|204|W||
>>> QAK|1903342086890395431720417949101|AE
>>> QPD|QRY_PDQ_1001^Query By
>>> Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||
>>>
>>> My rhio config has the same entry for the pix as I used to
>>> successfully test against the IBM PIX Manager except the url is to a
>>> local machine (the one running the mesa server):
>>> <pix>
>>> <id>mesa</id>
>>> <mllp>
>>> <unsecured>mllp://192.168.1.127:3600</unsecured>
>>> </mllp>
>>> <pixServerPropertiesId>IBM PIX Server</pixServerPropertiesId>
>>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>>>
>>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>>>
>>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>>> <defaultMessageQueryNameId>IHEDEMO</defaultMessageQueryNameId >
>>> </pix>
>>>
>>> Any ideas? Is the bridge even supposed to do PIX queries or just PDQ?
>>>
>>> thanks,
>>> Jesse
>>>
>
>
|
|
|
| Re: OHF Bridge Mesa test 10501 [message #34439 is a reply to message #34405] |
Mon, 08 October 2007 20:59 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi Sondra,
Great, I updated that file, recompiled and now test 10501 is working for
me. Thanks a lot!
BTW, is there a way to tell in buzilla which files were changed? I looked
at the bug referenced and did not see any reference to the files- I've
never really used bugzilla so maybe I'm missing something obvious. I
guessed that file was probably it when I was checking around in CVS, but
wasn't sure until I saw your post since there was no comment in CVS and
the change was slightly different than Graham's buzilla comment.
thanks again,
Jesse
Sondra Renly wrote:
> The update was made in trunk -
> Update Segment.java from current which is the real fix is in Grahame's
> HL7v2 code. The posted change in PixConsumerQuery is a temp workaround.
> Sondra
> Jesse Pangburn wrote:
>> Hi Sondra,
>> Ah, I didn't really know what that parameter was for. I assumed it
>> meant whether I wanted the results returned with or without demographics
>> information- so I set it to false to indicate I wanted demographics
>> information :-) Now I understand its use.
>>
>> So I set it to true and tested and got an error in the bridge:
>> [DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixPdqMessage:
>> changeDefaultRecievingFacility
>> [DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixMsgADT: setField
>> QPD-3-5 :
>> QPD-3
>> [ERROR][12:14:44][clipse.ohf.bridge.ws.OHFBridge] failed at SearchPatient
>> java.lang.NullPointerException
>> at
>> org.eclipse.ohf.ihe.common.hl7v2.message.PixPdqMessage.setFi eld(PixPd
>> qMessage.java:385)
>> at
>> org.eclipse.ohf.bridge.ihe.pixpdq.IhePatientConsumerBridge.c reatePixC
>> onsumerQuery(IhePatientConsumerBridge.java:184)
>>
>> I saw a similar problem regarding setting "QPD-3-5" when reading over
>> the more recent posts on this newsgroup last week. I just reread and
>> see that you and Graham fixed it. The last time I tried pulling the
>> source trunk, I couldn't get it to compile. I ended up pulling the
>> branch/tag "OHF_IHE_POST_2007EUCTHON" which was a lot easier to get
>> running. So, the fix you guys made, is it in the trunk or is there a
>> branch you're working on?
>>
>> thanks,
>> Jesse
>>
>>
>> Sondra Renly wrote:
>>
>>> Hi Jesse,
>>
>>> One note I want to add is that the bridge has mesa test junits you can
>>> reference under project org.eclipse.ohf.bridge.ws. This can provide
>>> some guidance.
>>
>>> The distinction to do pix vs pdq is based on a flag in the bridge,
>>> method "setWithoutDemographics". If this flag is set to true, it will
>>> perform a pix query. If this flag is set to false, it will perform a
>>> pdq query. The default is false and I suspect this is your problem.
>>
>>
>>> Sondra
>>
>>
>>> Jesse Pangburn wrote:
>>>> Hi,
>>>> I'm trying to do the first MESA PIX test "10501" using the bridge,
>>>> but I'm getting an error. It appears to be trying to do a PDQ query
>>>> instead of a PIX query, though I'm pretty new to IHE so that may be a
>>>> misunderstanding on my part.
>>>>
>>>> I'm sending the following XML to the bridge:
>>>> <SOAP-ENV:Envelope
>>>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>>>> xmlns:tns1="http://ws.bridge.ohf.eclipse.org"
>>>> xmlns:tns2="http://type.bridge.ohf.eclipse.org"
>>>> xmlns:impl="http://localhost/bridge/services/ohf-bridge-wrapped">
>>>> <SOAP-ENV:Body>
>>>> <tns1:SearchPatient>
>>>> <tns1:sessionContext>
>>>> <tns2:returnLogLevel>WARN</tns2:returnLogLevel>
>>>> <tns2:rhioName>mesa</tns2:rhioName>
>>>> <tns2:sessionID>1111</tns2:sessionID>
>>>>
>>
<tns2:useSecuredConnectionWhenAvaliable>true</tns2:useSecuredConnectionWhenAvaliable >
>>
>>>>
>>>> <tns2:user>patientsearcher</tns2:user>
>>>> <tns2:userApplicationName/>
>>>> <tns2:userFacilityName/>
>>>> </tns1:sessionContext>
>>>> <tns1:patientInfo>
>>>> <tns2:genericAdtValues>
>>>> <impl:item>
>>>> <tns2:data/>
>>>> <tns2:path/>
>>>> </impl:item>
>>>> </tns2:genericAdtValues>
>>>> <tns2:patientAddress>
>>>> <tns2:city/>
>>>> <tns2:country/>
>>>> <tns2:countyParishCode/>
>>>> <tns2:otherDesignation/>
>>>> <tns2:stateOrProvince/>
>>>> <tns2:streetAddress/>
>>>> <tns2:zipOrPostalCode/>
>>>> </tns2:patientAddress>
>>>> <tns2:patientDateOfBirth/>
>>>> <tns2:patientIdentifier>
>>>> <tns2:assigningAuthorityType>
>>>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>>>
>>>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>>>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>>>
>>>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>>>
>>
<tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>>
>>>>
>>>> </tns2:assigningAuthorityType>
>>>> <tns2:idNumber>PIX10501</tns2:idNumber>
>>>> </tns2:patientIdentifier>
>>>> <tns2:patientName>
>>>> <tns2:familyName/>
>>>> <tns2:givenName/>
>>>> <tns2:otherName/>
>>>> <tns2:prefix/>
>>>> <tns2:suffix/>
>>>> </tns2:patientName>
>>>> <tns2:patientPhoneBusiness>
>>>> <tns2:unformattedTelephoneNumber/>
>>>> </tns2:patientPhoneBusiness>
>>>> <tns2:patientPhoneHome>
>>>> <tns2:unformattedTelephoneNumber/>
>>>> </tns2:patientPhoneHome>
>>>> <tns2:patientSex/>
>>>> </tns1:patientInfo>
>>>> <tns1:queryPreferences>
>>>> <tns2:domainsReturned>
>>>> <impl:item>
>>>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>>>
>>>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>>>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>>>
>>>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>>>
>>
<tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>>
>>>>
>>>> </impl:item>
>>>> </tns2:domainsReturned>
>>>> <tns2:quantityLimit>1</tns2:quantityLimit>
>>>>
>>>> <tns2:withoutDemographics>false</tns2:withoutDemographics>
>>>> </tns1:queryPreferences>
>>>> </tns1:SearchPatient>
>>>> </SOAP-ENV:Body>
>>>> </SOAP-ENV:Envelope>
>>>>
>>>> I get back:
>>>> <soapenv:Envelope
>>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>>>> <soapenv:Body>
>>>> <SearchPatientResponse xmlns="http://ws.bridge.ohf.eclipse.org">
>>>> <SearchPatientReturn>
>>>> <ns1:failMessage
>>>> xmlns:ns1="http://type.bridge.ohf.eclipse.org"> Error location:
>>>> QPD^1^3^1^4^ Error code: 204 Error severity: Warning</ns1:failMessage>
>>>> <ns2:log
>>>> xmlns:ns2="http://type.bridge.ohf.eclipse.org"/>
>>>> <ns3:sessionID
>>>> xmlns:ns3="http://type.bridge.ohf.eclipse.org">1111</ns3:sessionID>
>>>> <ns4:success
>>>> xmlns:ns4="http://type.bridge.ohf.eclipse.org">false</ns4:success>
>>>> <ns5:successMessage
>>>> xmlns:ns5="http://type.bridge.ohf.eclipse.org"/>
>>>> <ns6:patients xsi:nil="true"
>>>> xmlns:ns6="http://type.bridge.ohf.eclipse.org"/>
>>>> </SearchPatientReturn>
>>>> </SearchPatientResponse>
>>>> </soapenv:Body>
>>>> </soapenv:Envelope>
>>>>
>>>> Tracing the network shows that the bridge sends the following HL7:
>>>>
>>
MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|20071005 133800-0700||QBP^Q22^QBP_Q21|0886784820993939999|P|2.5
>>
>>>>
>>>> QPD|QRY_PDQ_1001^Query By
>>
Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO
>>
>>>>
>>>> RCP|I|1^RD
>>>>
>>>> The mesa PIX server replies:
>>>>
>>
MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|||RSP^K2 3|MESA4706a0c4|P|2.5||||||||
>>
>>>>
>>>> MSA|AE|0886784820993939999||||
>>>> ERR||QPD^1^3^1^4|204|W||
>>>> QAK|1903342086890395431720417949101|AE
>>>> QPD|QRY_PDQ_1001^Query By
>>>> Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||
>>>>
>>>> My rhio config has the same entry for the pix as I used to
>>>> successfully test against the IBM PIX Manager except the url is to a
>>>> local machine (the one running the mesa server):
>>>> <pix>
>>>> <id>mesa</id>
>>>> <mllp>
>>>> <unsecured>mllp://192.168.1.127:3600</unsecured>
>>>> </mllp>
>>>> <pixServerPropertiesId>IBM PIX Server</pixServerPropertiesId>
>>>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>>>>
>>>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>>>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>>>>
>>>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>>>> <defaultMessageQueryNameId>IHEDEMO</defaultMessageQueryNameId >
>>>> </pix>
>>>>
>>>> Any ideas? Is the bridge even supposed to do PIX queries or just PDQ?
>>>>
>>>> thanks,
>>>> Jesse
>>>>
>>
>>
|
|
| |
| Re: OHF Bridge Mesa test 10501 [message #581749 is a reply to message #34204] |
Mon, 08 October 2007 19:27 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi Sondra,
Ah, I didn't really know what that parameter was for. I assumed it meant
whether I wanted the results returned with or without demographics
information- so I set it to false to indicate I wanted demographics
information :-) Now I understand its use.
So I set it to true and tested and got an error in the bridge:
[DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixPdqMessage:
changeDefaultRecievingFacility
[DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixMsgADT: setField
QPD-3-5 :
QPD-3
[ERROR][12:14:44][clipse.ohf.bridge.ws.OHFBridge] failed at SearchPatient
java.lang.NullPointerException
at
org.eclipse.ohf.ihe.common.hl7v2.message.PixPdqMessage.setFi eld(PixPd
qMessage.java:385)
at
org.eclipse.ohf.bridge.ihe.pixpdq.IhePatientConsumerBridge.c reatePixC
onsumerQuery(IhePatientConsumerBridge.java:184)
I saw a similar problem regarding setting "QPD-3-5" when reading over the
more recent posts on this newsgroup last week. I just reread and see that
you and Graham fixed it. The last time I tried pulling the source trunk,
I couldn't get it to compile. I ended up pulling the branch/tag
"OHF_IHE_POST_2007EUCTHON" which was a lot easier to get running. So, the
fix you guys made, is it in the trunk or is there a branch you're working
on?
thanks,
Jesse
Sondra Renly wrote:
> Hi Jesse,
> One note I want to add is that the bridge has mesa test junits you can
> reference under project org.eclipse.ohf.bridge.ws. This can provide some
> guidance.
> The distinction to do pix vs pdq is based on a flag in the bridge,
> method "setWithoutDemographics". If this flag is set to true, it will
> perform a pix query. If this flag is set to false, it will perform a pdq
> query. The default is false and I suspect this is your problem.
> Sondra
> Jesse Pangburn wrote:
>> Hi,
>> I'm trying to do the first MESA PIX test "10501" using the bridge, but
>> I'm getting an error. It appears to be trying to do a PDQ query instead
>> of a PIX query, though I'm pretty new to IHE so that may be a
>> misunderstanding on my part.
>>
>> I'm sending the following XML to the bridge:
>> <SOAP-ENV:Envelope
>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:tns1="http://ws.bridge.ohf.eclipse.org"
>> xmlns:tns2="http://type.bridge.ohf.eclipse.org"
>> xmlns:impl="http://localhost/bridge/services/ohf-bridge-wrapped">
>> <SOAP-ENV:Body>
>> <tns1:SearchPatient>
>> <tns1:sessionContext>
>> <tns2:returnLogLevel>WARN</tns2:returnLogLevel>
>> <tns2:rhioName>mesa</tns2:rhioName>
>> <tns2:sessionID>1111</tns2:sessionID>
>>
>>
<tns2:useSecuredConnectionWhenAvaliable>true</tns2:useSecuredConnectionWhenAvaliable >
>>
>> <tns2:user>patientsearcher</tns2:user>
>> <tns2:userApplicationName/>
>> <tns2:userFacilityName/>
>> </tns1:sessionContext>
>> <tns1:patientInfo>
>> <tns2:genericAdtValues>
>> <impl:item>
>> <tns2:data/>
>> <tns2:path/>
>> </impl:item>
>> </tns2:genericAdtValues>
>> <tns2:patientAddress>
>> <tns2:city/>
>> <tns2:country/>
>> <tns2:countyParishCode/>
>> <tns2:otherDesignation/>
>> <tns2:stateOrProvince/>
>> <tns2:streetAddress/>
>> <tns2:zipOrPostalCode/>
>> </tns2:patientAddress>
>> <tns2:patientDateOfBirth/>
>> <tns2:patientIdentifier>
>> <tns2:assigningAuthorityType>
>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>
>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>
>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>
>>
<tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>>
>> </tns2:assigningAuthorityType>
>> <tns2:idNumber>PIX10501</tns2:idNumber>
>> </tns2:patientIdentifier>
>> <tns2:patientName>
>> <tns2:familyName/>
>> <tns2:givenName/>
>> <tns2:otherName/>
>> <tns2:prefix/>
>> <tns2:suffix/>
>> </tns2:patientName>
>> <tns2:patientPhoneBusiness>
>> <tns2:unformattedTelephoneNumber/>
>> </tns2:patientPhoneBusiness>
>> <tns2:patientPhoneHome>
>> <tns2:unformattedTelephoneNumber/>
>> </tns2:patientPhoneHome>
>> <tns2:patientSex/>
>> </tns1:patientInfo>
>> <tns1:queryPreferences>
>> <tns2:domainsReturned>
>> <impl:item>
>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>
>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>
>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>
>>
<tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>>
>> </impl:item>
>> </tns2:domainsReturned>
>> <tns2:quantityLimit>1</tns2:quantityLimit>
>> <tns2:withoutDemographics>false</tns2:withoutDemographics>
>> </tns1:queryPreferences>
>> </tns1:SearchPatient>
>> </SOAP-ENV:Body>
>> </SOAP-ENV:Envelope>
>>
>> I get back:
>> <soapenv:Envelope
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>> <soapenv:Body>
>> <SearchPatientResponse xmlns="http://ws.bridge.ohf.eclipse.org">
>> <SearchPatientReturn>
>> <ns1:failMessage
>> xmlns:ns1="http://type.bridge.ohf.eclipse.org"> Error location:
>> QPD^1^3^1^4^ Error code: 204 Error severity: Warning</ns1:failMessage>
>> <ns2:log xmlns:ns2="http://type.bridge.ohf.eclipse.org"/>
>> <ns3:sessionID
>> xmlns:ns3="http://type.bridge.ohf.eclipse.org">1111</ns3:sessionID>
>> <ns4:success
>> xmlns:ns4="http://type.bridge.ohf.eclipse.org">false</ns4:success>
>> <ns5:successMessage
>> xmlns:ns5="http://type.bridge.ohf.eclipse.org"/>
>> <ns6:patients xsi:nil="true"
>> xmlns:ns6="http://type.bridge.ohf.eclipse.org"/>
>> </SearchPatientReturn>
>> </SearchPatientResponse>
>> </soapenv:Body>
>> </soapenv:Envelope>
>>
>> Tracing the network shows that the bridge sends the following HL7:
>>
MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|20071005 133800-0700||QBP^Q22^QBP_Q21|0886784820993939999|P|2.5
>>
>> QPD|QRY_PDQ_1001^Query By
>>
Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO
>>
>> RCP|I|1^RD
>>
>> The mesa PIX server replies:
>>
MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|||RSP^K2 3|MESA4706a0c4|P|2.5||||||||
>>
>> MSA|AE|0886784820993939999||||
>> ERR||QPD^1^3^1^4|204|W||
>> QAK|1903342086890395431720417949101|AE
>> QPD|QRY_PDQ_1001^Query By
>> Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||
>>
>> My rhio config has the same entry for the pix as I used to successfully
>> test against the IBM PIX Manager except the url is to a local machine
>> (the one running the mesa server):
>> <pix>
>> <id>mesa</id>
>> <mllp>
>> <unsecured>mllp://192.168.1.127:3600</unsecured>
>> </mllp>
>> <pixServerPropertiesId>IBM PIX Server</pixServerPropertiesId>
>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>> <defaultMessageQueryNameId>IHEDEMO</defaultMessageQueryNameId >
>> </pix>
>>
>> Any ideas? Is the bridge even supposed to do PIX queries or just PDQ?
>>
>> thanks,
>> Jesse
>>
|
|
|
| Re: OHF Bridge Mesa test 10501 [message #581759 is a reply to message #34371] |
Mon, 08 October 2007 19:40 |
Sondra Renly
Messages: 39
Registered: July 2009 |
Member |
|
|
The update was made in trunk -
Update Segment.java from current which is the real fix is in Grahame's
HL7v2 code. The posted change in PixConsumerQuery is a temp workaround.
Sondra
Jesse Pangburn wrote:
> Hi Sondra,
> Ah, I didn't really know what that parameter was for. I assumed it
> meant whether I wanted the results returned with or without demographics
> information- so I set it to false to indicate I wanted demographics
> information :-) Now I understand its use.
>
> So I set it to true and tested and got an error in the bridge:
> [DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixPdqMessage:
> changeDefaultRecievingFacility
> [DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixMsgADT: setField
> QPD-3-5 :
> QPD-3
> [ERROR][12:14:44][clipse.ohf.bridge.ws.OHFBridge] failed at SearchPatient
> java.lang.NullPointerException
> at
> org.eclipse.ohf.ihe.common.hl7v2.message.PixPdqMessage.setFi eld(PixPd
> qMessage.java:385)
> at
> org.eclipse.ohf.bridge.ihe.pixpdq.IhePatientConsumerBridge.c reatePixC
> onsumerQuery(IhePatientConsumerBridge.java:184)
>
> I saw a similar problem regarding setting "QPD-3-5" when reading over
> the more recent posts on this newsgroup last week. I just reread and
> see that you and Graham fixed it. The last time I tried pulling the
> source trunk, I couldn't get it to compile. I ended up pulling the
> branch/tag "OHF_IHE_POST_2007EUCTHON" which was a lot easier to get
> running. So, the fix you guys made, is it in the trunk or is there a
> branch you're working on?
>
> thanks,
> Jesse
>
>
> Sondra Renly wrote:
>
>> Hi Jesse,
>
>> One note I want to add is that the bridge has mesa test junits you can
>> reference under project org.eclipse.ohf.bridge.ws. This can provide
>> some guidance.
>
>> The distinction to do pix vs pdq is based on a flag in the bridge,
>> method "setWithoutDemographics". If this flag is set to true, it will
>> perform a pix query. If this flag is set to false, it will perform a
>> pdq query. The default is false and I suspect this is your problem.
>
>
>> Sondra
>
>
>> Jesse Pangburn wrote:
>>> Hi,
>>> I'm trying to do the first MESA PIX test "10501" using the bridge,
>>> but I'm getting an error. It appears to be trying to do a PDQ query
>>> instead of a PIX query, though I'm pretty new to IHE so that may be a
>>> misunderstanding on my part.
>>>
>>> I'm sending the following XML to the bridge:
>>> <SOAP-ENV:Envelope
>>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:tns1="http://ws.bridge.ohf.eclipse.org"
>>> xmlns:tns2="http://type.bridge.ohf.eclipse.org"
>>> xmlns:impl="http://localhost/bridge/services/ohf-bridge-wrapped">
>>> <SOAP-ENV:Body>
>>> <tns1:SearchPatient>
>>> <tns1:sessionContext>
>>> <tns2:returnLogLevel>WARN</tns2:returnLogLevel>
>>> <tns2:rhioName>mesa</tns2:rhioName>
>>> <tns2:sessionID>1111</tns2:sessionID>
>>>
> <tns2:useSecuredConnectionWhenAvaliable>true</tns2:useSecuredConnectionWhenAvaliable >
>
>>>
>>> <tns2:user>patientsearcher</tns2:user>
>>> <tns2:userApplicationName/>
>>> <tns2:userFacilityName/>
>>> </tns1:sessionContext>
>>> <tns1:patientInfo>
>>> <tns2:genericAdtValues>
>>> <impl:item>
>>> <tns2:data/>
>>> <tns2:path/>
>>> </impl:item>
>>> </tns2:genericAdtValues>
>>> <tns2:patientAddress>
>>> <tns2:city/>
>>> <tns2:country/>
>>> <tns2:countyParishCode/>
>>> <tns2:otherDesignation/>
>>> <tns2:stateOrProvince/>
>>> <tns2:streetAddress/>
>>> <tns2:zipOrPostalCode/>
>>> </tns2:patientAddress>
>>> <tns2:patientDateOfBirth/>
>>> <tns2:patientIdentifier>
>>> <tns2:assigningAuthorityType>
>>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>>
>>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>>
>>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>>
> <tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>
>>>
>>> </tns2:assigningAuthorityType>
>>> <tns2:idNumber>PIX10501</tns2:idNumber>
>>> </tns2:patientIdentifier>
>>> <tns2:patientName>
>>> <tns2:familyName/>
>>> <tns2:givenName/>
>>> <tns2:otherName/>
>>> <tns2:prefix/>
>>> <tns2:suffix/>
>>> </tns2:patientName>
>>> <tns2:patientPhoneBusiness>
>>> <tns2:unformattedTelephoneNumber/>
>>> </tns2:patientPhoneBusiness>
>>> <tns2:patientPhoneHome>
>>> <tns2:unformattedTelephoneNumber/>
>>> </tns2:patientPhoneHome>
>>> <tns2:patientSex/>
>>> </tns1:patientInfo>
>>> <tns1:queryPreferences>
>>> <tns2:domainsReturned>
>>> <impl:item>
>>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>>
>>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>>
>>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>>
> <tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>
>>>
>>> </impl:item>
>>> </tns2:domainsReturned>
>>> <tns2:quantityLimit>1</tns2:quantityLimit>
>>>
>>> <tns2:withoutDemographics>false</tns2:withoutDemographics>
>>> </tns1:queryPreferences>
>>> </tns1:SearchPatient>
>>> </SOAP-ENV:Body>
>>> </SOAP-ENV:Envelope>
>>>
>>> I get back:
>>> <soapenv:Envelope
>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>>> <soapenv:Body>
>>> <SearchPatientResponse xmlns="http://ws.bridge.ohf.eclipse.org">
>>> <SearchPatientReturn>
>>> <ns1:failMessage
>>> xmlns:ns1="http://type.bridge.ohf.eclipse.org"> Error location:
>>> QPD^1^3^1^4^ Error code: 204 Error severity: Warning</ns1:failMessage>
>>> <ns2:log
>>> xmlns:ns2="http://type.bridge.ohf.eclipse.org"/>
>>> <ns3:sessionID
>>> xmlns:ns3="http://type.bridge.ohf.eclipse.org">1111</ns3:sessionID>
>>> <ns4:success
>>> xmlns:ns4="http://type.bridge.ohf.eclipse.org">false</ns4:success>
>>> <ns5:successMessage
>>> xmlns:ns5="http://type.bridge.ohf.eclipse.org"/>
>>> <ns6:patients xsi:nil="true"
>>> xmlns:ns6="http://type.bridge.ohf.eclipse.org"/>
>>> </SearchPatientReturn>
>>> </SearchPatientResponse>
>>> </soapenv:Body>
>>> </soapenv:Envelope>
>>>
>>> Tracing the network shows that the bridge sends the following HL7:
>>>
> MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|20071005 133800-0700||QBP^Q22^QBP_Q21|0886784820993939999|P|2.5
>
>>>
>>> QPD|QRY_PDQ_1001^Query By
> Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO
>
>>>
>>> RCP|I|1^RD
>>>
>>> The mesa PIX server replies:
>>>
> MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|||RSP^K2 3|MESA4706a0c4|P|2.5||||||||
>
>>>
>>> MSA|AE|0886784820993939999||||
>>> ERR||QPD^1^3^1^4|204|W||
>>> QAK|1903342086890395431720417949101|AE
>>> QPD|QRY_PDQ_1001^Query By
>>> Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||
>>>
>>> My rhio config has the same entry for the pix as I used to
>>> successfully test against the IBM PIX Manager except the url is to a
>>> local machine (the one running the mesa server):
>>> <pix>
>>> <id>mesa</id>
>>> <mllp>
>>> <unsecured>mllp://192.168.1.127:3600</unsecured>
>>> </mllp>
>>> <pixServerPropertiesId>IBM PIX Server</pixServerPropertiesId>
>>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>>>
>>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>>>
>>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>>> <defaultMessageQueryNameId>IHEDEMO</defaultMessageQueryNameId >
>>> </pix>
>>>
>>> Any ideas? Is the bridge even supposed to do PIX queries or just PDQ?
>>>
>>> thanks,
>>> Jesse
>>>
>
>
|
|
|
| Re: OHF Bridge Mesa test 10501 [message #581774 is a reply to message #34405] |
Mon, 08 October 2007 20:59 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi Sondra,
Great, I updated that file, recompiled and now test 10501 is working for
me. Thanks a lot!
BTW, is there a way to tell in buzilla which files were changed? I looked
at the bug referenced and did not see any reference to the files- I've
never really used bugzilla so maybe I'm missing something obvious. I
guessed that file was probably it when I was checking around in CVS, but
wasn't sure until I saw your post since there was no comment in CVS and
the change was slightly different than Graham's buzilla comment.
thanks again,
Jesse
Sondra Renly wrote:
> The update was made in trunk -
> Update Segment.java from current which is the real fix is in Grahame's
> HL7v2 code. The posted change in PixConsumerQuery is a temp workaround.
> Sondra
> Jesse Pangburn wrote:
>> Hi Sondra,
>> Ah, I didn't really know what that parameter was for. I assumed it
>> meant whether I wanted the results returned with or without demographics
>> information- so I set it to false to indicate I wanted demographics
>> information :-) Now I understand its use.
>>
>> So I set it to true and tested and got an error in the bridge:
>> [DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixPdqMessage:
>> changeDefaultRecievingFacility
>> [DEBUG][12:14:44][on.hl7v2.message.PixPdqMessage] PixMsgADT: setField
>> QPD-3-5 :
>> QPD-3
>> [ERROR][12:14:44][clipse.ohf.bridge.ws.OHFBridge] failed at SearchPatient
>> java.lang.NullPointerException
>> at
>> org.eclipse.ohf.ihe.common.hl7v2.message.PixPdqMessage.setFi eld(PixPd
>> qMessage.java:385)
>> at
>> org.eclipse.ohf.bridge.ihe.pixpdq.IhePatientConsumerBridge.c reatePixC
>> onsumerQuery(IhePatientConsumerBridge.java:184)
>>
>> I saw a similar problem regarding setting "QPD-3-5" when reading over
>> the more recent posts on this newsgroup last week. I just reread and
>> see that you and Graham fixed it. The last time I tried pulling the
>> source trunk, I couldn't get it to compile. I ended up pulling the
>> branch/tag "OHF_IHE_POST_2007EUCTHON" which was a lot easier to get
>> running. So, the fix you guys made, is it in the trunk or is there a
>> branch you're working on?
>>
>> thanks,
>> Jesse
>>
>>
>> Sondra Renly wrote:
>>
>>> Hi Jesse,
>>
>>> One note I want to add is that the bridge has mesa test junits you can
>>> reference under project org.eclipse.ohf.bridge.ws. This can provide
>>> some guidance.
>>
>>> The distinction to do pix vs pdq is based on a flag in the bridge,
>>> method "setWithoutDemographics". If this flag is set to true, it will
>>> perform a pix query. If this flag is set to false, it will perform a
>>> pdq query. The default is false and I suspect this is your problem.
>>
>>
>>> Sondra
>>
>>
>>> Jesse Pangburn wrote:
>>>> Hi,
>>>> I'm trying to do the first MESA PIX test "10501" using the bridge,
>>>> but I'm getting an error. It appears to be trying to do a PDQ query
>>>> instead of a PIX query, though I'm pretty new to IHE so that may be a
>>>> misunderstanding on my part.
>>>>
>>>> I'm sending the following XML to the bridge:
>>>> <SOAP-ENV:Envelope
>>>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>>>> xmlns:tns1="http://ws.bridge.ohf.eclipse.org"
>>>> xmlns:tns2="http://type.bridge.ohf.eclipse.org"
>>>> xmlns:impl="http://localhost/bridge/services/ohf-bridge-wrapped">
>>>> <SOAP-ENV:Body>
>>>> <tns1:SearchPatient>
>>>> <tns1:sessionContext>
>>>> <tns2:returnLogLevel>WARN</tns2:returnLogLevel>
>>>> <tns2:rhioName>mesa</tns2:rhioName>
>>>> <tns2:sessionID>1111</tns2:sessionID>
>>>>
>>
<tns2:useSecuredConnectionWhenAvaliable>true</tns2:useSecuredConnectionWhenAvaliable >
>>
>>>>
>>>> <tns2:user>patientsearcher</tns2:user>
>>>> <tns2:userApplicationName/>
>>>> <tns2:userFacilityName/>
>>>> </tns1:sessionContext>
>>>> <tns1:patientInfo>
>>>> <tns2:genericAdtValues>
>>>> <impl:item>
>>>> <tns2:data/>
>>>> <tns2:path/>
>>>> </impl:item>
>>>> </tns2:genericAdtValues>
>>>> <tns2:patientAddress>
>>>> <tns2:city/>
>>>> <tns2:country/>
>>>> <tns2:countyParishCode/>
>>>> <tns2:otherDesignation/>
>>>> <tns2:stateOrProvince/>
>>>> <tns2:streetAddress/>
>>>> <tns2:zipOrPostalCode/>
>>>> </tns2:patientAddress>
>>>> <tns2:patientDateOfBirth/>
>>>> <tns2:patientIdentifier>
>>>> <tns2:assigningAuthorityType>
>>>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>>>
>>>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>>>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>>>
>>>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>>>
>>
<tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>>
>>>>
>>>> </tns2:assigningAuthorityType>
>>>> <tns2:idNumber>PIX10501</tns2:idNumber>
>>>> </tns2:patientIdentifier>
>>>> <tns2:patientName>
>>>> <tns2:familyName/>
>>>> <tns2:givenName/>
>>>> <tns2:otherName/>
>>>> <tns2:prefix/>
>>>> <tns2:suffix/>
>>>> </tns2:patientName>
>>>> <tns2:patientPhoneBusiness>
>>>> <tns2:unformattedTelephoneNumber/>
>>>> </tns2:patientPhoneBusiness>
>>>> <tns2:patientPhoneHome>
>>>> <tns2:unformattedTelephoneNumber/>
>>>> </tns2:patientPhoneHome>
>>>> <tns2:patientSex/>
>>>> </tns1:patientInfo>
>>>> <tns1:queryPreferences>
>>>> <tns2:domainsReturned>
>>>> <impl:item>
>>>> <tns2:namespaceId>HIMSS2005</tns2:namespaceId>
>>>>
>>>> <tns2:universalId>1.3.6.1.4.1.21367.2005.1.1</tns2:universalId >
>>>> <tns2:universalIdType>ISO</tns2:universalIdType>
>>>>
>>>> <tns2:universalIdTypeCode>PI</tns2:universalIdTypeCode>
>>>>
>>
<tns2:useDefaultAssigningAuthority>false</tns2:useDefaultAssigningAuthority >
>>
>>>>
>>>> </impl:item>
>>>> </tns2:domainsReturned>
>>>> <tns2:quantityLimit>1</tns2:quantityLimit>
>>>>
>>>> <tns2:withoutDemographics>false</tns2:withoutDemographics>
>>>> </tns1:queryPreferences>
>>>> </tns1:SearchPatient>
>>>> </SOAP-ENV:Body>
>>>> </SOAP-ENV:Envelope>
>>>>
>>>> I get back:
>>>> <soapenv:Envelope
>>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>>>> <soapenv:Body>
>>>> <SearchPatientResponse xmlns="http://ws.bridge.ohf.eclipse.org">
>>>> <SearchPatientReturn>
>>>> <ns1:failMessage
>>>> xmlns:ns1="http://type.bridge.ohf.eclipse.org"> Error location:
>>>> QPD^1^3^1^4^ Error code: 204 Error severity: Warning</ns1:failMessage>
>>>> <ns2:log
>>>> xmlns:ns2="http://type.bridge.ohf.eclipse.org"/>
>>>> <ns3:sessionID
>>>> xmlns:ns3="http://type.bridge.ohf.eclipse.org">1111</ns3:sessionID>
>>>> <ns4:success
>>>> xmlns:ns4="http://type.bridge.ohf.eclipse.org">false</ns4:success>
>>>> <ns5:successMessage
>>>> xmlns:ns5="http://type.bridge.ohf.eclipse.org"/>
>>>> <ns6:patients xsi:nil="true"
>>>> xmlns:ns6="http://type.bridge.ohf.eclipse.org"/>
>>>> </SearchPatientReturn>
>>>> </SearchPatientResponse>
>>>> </soapenv:Body>
>>>> </soapenv:Envelope>
>>>>
>>>> Tracing the network shows that the bridge sends the following HL7:
>>>>
>>
MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|20071005 133800-0700||QBP^Q22^QBP_Q21|0886784820993939999|P|2.5
>>
>>>>
>>>> QPD|QRY_PDQ_1001^Query By
>>
Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO
>>
>>>>
>>>> RCP|I|1^RD
>>>>
>>>> The mesa PIX server replies:
>>>>
>>
MSH|^~&|XDSDEMO_ADT|XDSDEMO|XDSDEMO_ADT|XDSDEMO|||RSP^K2 3|MESA4706a0c4|P|2.5||||||||
>>
>>>>
>>>> MSA|AE|0886784820993939999||||
>>>> ERR||QPD^1^3^1^4|204|W||
>>>> QAK|1903342086890395431720417949101|AE
>>>> QPD|QRY_PDQ_1001^Query By
>>>> Name^IHEDEMO|1903342086890395431720417949101|@PID.3.1^PIX105 01|||||
>>>>
>>>> My rhio config has the same entry for the pix as I used to
>>>> successfully test against the IBM PIX Manager except the url is to a
>>>> local machine (the one running the mesa server):
>>>> <pix>
>>>> <id>mesa</id>
>>>> <mllp>
>>>> <unsecured>mllp://192.168.1.127:3600</unsecured>
>>>> </mllp>
>>>> <pixServerPropertiesId>IBM PIX Server</pixServerPropertiesId>
>>>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>>>>
>>>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>>>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>>>>
>>>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>>>> <defaultMessageQueryNameId>IHEDEMO</defaultMessageQueryNameId >
>>>> </pix>
>>>>
>>>> Any ideas? Is the bridge even supposed to do PIX queries or just PDQ?
>>>>
>>>> thanks,
>>>> Jesse
>>>>
>>
>>
|
|
|
Goto Forum:
Current Time: Fri Dec 27 11:49:03 GMT 2024
Powered by FUDForum. Page generated in 0.04640 seconds |
] 
Search
Help
Register
Login
Home
