Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » OHF » OHF Bridge MESA test 10503
OHF Bridge MESA test 10503 [message #36229] Tue, 30 October 2007 17:40 Go to next message
Corey Spears is currently offline Corey SpearsFriend
Messages: 18
Registered: July 2009
Junior Member
All,
I am using the OHF bridge.
I am trying to run MESA test 10503. This test calls for sending a PIX query
"ABC10503^^^XXXX"
I assume the PIX query should look something like
MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
QPD|Q23^Get Corresponding IDs|5412693612507688165591841744311|ABC10503^^^XXX
RCP|I

However I am getting
MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
QPD|Q23^Get Corresponding
IDs|5412693612507688165591841744311|ABC10503^^^&1.3.6.1. 4.1.21367.2007.1.2.400&ISO
RCP|I


I have configured a new RHIO in the rhioConfig.xml. The rhio is just a copy
of the XDS.a RHIO, but with a pixId of "LocalPIX"
LocalPIX is configured as
<pix>
<id>LocalPIX</id>
<mllp>
<unsecured>mllp://localhost:3600</unsecured>
</mllp>
<pixServerPropertiesId>Local PIX Server</pixServerPropertiesId>
<pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
<pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
<pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
<pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
</pix>

Local PIX Server is configured as
<pixProperties>
<id>Local PIX Server</id>
<facility>XDSDEMO</facility>
<application>HIMSS2005</application>
<assigningAuthorityNamespaceId>XXXX</assigningAuthorityNamespaceId >
<assigningAuthorityUniversalId></assigningAuthorityUniversalId >
<assigningAuthorityUniversalIdType>ISO</assigningAuthorityUniversalIdType >
</pixProperties>


In the patientIdentifier, I am specifiying the assigningAuthorityNamespaceId
to XXXX and the assigningAuthorityUniversalId is left blank.
Is anyone else having this problem? Am I missing something?

Thank you,
Corey Spears
Re: OHF Bridge MESA test 10503 [message #36263 is a reply to message #36229] Tue, 30 October 2007 19:46 Go to previous messageGo to next message
Matthew DavisFriend
Messages: 269
Registered: July 2009
Senior Member
Hi Corey,

It looks like the default value from your PIX configuration settings are
being copied into the message. From the OHF Bridge
AssigningAuthorityType, there is an option
"useDefaultAssigningAuthority". Make sure this is set to "false".

From the Bridge MESA Test 1503
(org.eclipse.ohf.bridge.ws.tests.mesa.TestMESA1053), we have this:

PatientIdType idType = new PatientIdType("ABC10503");
idType.getAssigningAuthorityType().setNamespaceId("XXXX");

idType.getAssigningAuthorityType().setUseDefaultAssigningAut hority(false);

PatientInfoType infoType = new PatientInfoType();
infoType.setPatientIdentifier(idType);

PatientSearchPreferencesType patientSearchPreferencesType = new
PatientSearchPreferencesType();
patientSearchPreferencesType.setWithoutDemographics(true);


-Matt



Corey Spears wrote:
> All,
> I am using the OHF bridge.
> I am trying to run MESA test 10503. This test calls for sending a PIX query
> "ABC10503^^^XXXX"
> I assume the PIX query should look something like
> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
> QPD|Q23^Get Corresponding IDs|5412693612507688165591841744311|ABC10503^^^XXX
> RCP|I
>
> However I am getting
> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
> QPD|Q23^Get Corresponding
> IDs|5412693612507688165591841744311|ABC10503^^^&1.3.6.1. 4.1.21367.2007.1.2.400&ISO
> RCP|I
>
>
> I have configured a new RHIO in the rhioConfig.xml. The rhio is just a copy
> of the XDS.a RHIO, but with a pixId of "LocalPIX"
> LocalPIX is configured as
> <pix>
> <id>LocalPIX</id>
> <mllp>
> <unsecured>mllp://localhost:3600</unsecured>
> </mllp>
> <pixServerPropertiesId>Local PIX Server</pixServerPropertiesId>
> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
> </pix>
>
> Local PIX Server is configured as
> <pixProperties>
> <id>Local PIX Server</id>
> <facility>XDSDEMO</facility>
> <application>HIMSS2005</application>
> <assigningAuthorityNamespaceId>XXXX</assigningAuthorityNamespaceId >
> <assigningAuthorityUniversalId></assigningAuthorityUniversalId >
> <assigningAuthorityUniversalIdType>ISO</assigningAuthorityUniversalIdType >
> </pixProperties>
>
>
> In the patientIdentifier, I am specifiying the assigningAuthorityNamespaceId
> to XXXX and the assigningAuthorityUniversalId is left blank.
> Is anyone else having this problem? Am I missing something?
>
> Thank you,
> Corey Spears
>
>
Re: OHF Bridge MESA test 10503 [message #36295 is a reply to message #36263] Tue, 30 October 2007 20:30 Go to previous messageGo to next message
Matthew DavisFriend
Messages: 269
Registered: July 2009
Senior Member
Also,
It is possible, from the Bridge logs, to tell what the current
configuration setting is so long as you have it on debug logging mode
(should be the default). If you look at your bridge log file
(\tomcat\bridge.log or tomcat\bridge\<rhio name>\<faciltiy name>\<user
name>.log), you will see this line:

[DEBUG][12:41:03][clipse.ohf.bridge.ws.OHFBridge] Starting
PatientInfoType[] SearchPatient(PatientInfoType (
patientIdentifier=[PatientIdType ( idNumber=[ABC10503]
assigningAuthority=[AssigningAuthority ( namespaceId=[XXXX]
universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]
)] patientName=[PatientNameType ( familyName=[] givenName=[]
otherName=[] suffix=[] prefix=[] )] patientDateOfBirth=[]
patientSex=[] patientAddress=[AddressType ( streetAddress=[]
otherDesignation=[] city=[] stateOrProvince=[]
zipOrPostalCode=[] country=[] countyParishCode=[] )]
patientPhoneHome=[PhoneType ( unformattedTelephoneNumber=[] )]
patientPhoneBusiness=[PhoneType ( unformattedTelephoneNumber=[] )]
genericAdtValues=[] ), PatientSearchPreferencesType (
quantityLimit=[-1] withoutDemographics=[true] ))

Please find this information in your log for the transaction that you
ran regarding 10503. As you can see from the details, it will tell us
whether it's using the default assigning authority or not:

AssigningAuthority ( namespaceId=[XXXX]
universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]


Thanks,
-Matt



Matthew Davis wrote:
> Hi Corey,
>
> It looks like the default value from your PIX configuration settings are
> being copied into the message. From the OHF Bridge
> AssigningAuthorityType, there is an option
> "useDefaultAssigningAuthority". Make sure this is set to "false".
>
> From the Bridge MESA Test 1503
> (org.eclipse.ohf.bridge.ws.tests.mesa.TestMESA1053), we have this:
>
> PatientIdType idType = new PatientIdType("ABC10503");
> idType.getAssigningAuthorityType().setNamespaceId("XXXX");
>
> idType.getAssigningAuthorityType().setUseDefaultAssigningAut hority(false);
>
> PatientInfoType infoType = new PatientInfoType();
> infoType.setPatientIdentifier(idType);
>
> PatientSearchPreferencesType patientSearchPreferencesType = new
> PatientSearchPreferencesType();
> patientSearchPreferencesType.setWithoutDemographics(true);
>
>
> -Matt
>
>
>
> Corey Spears wrote:
>> All,
>> I am using the OHF bridge.
>> I am trying to run MESA test 10503. This test calls for sending a PIX
>> query "ABC10503^^^XXXX"
>> I assume the PIX query should look something like
>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>
>> QPD|Q23^Get Corresponding
>> IDs|5412693612507688165591841744311|ABC10503^^^XXX
>> RCP|I
>>
>> However I am getting
>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>
>> QPD|Q23^Get Corresponding
>> IDs|5412693612507688165591841744311|ABC10503^^^&1.3.6.1. 4.1.21367.2007.1.2.400&ISO
>>
>> RCP|I
>>
>>
>> I have configured a new RHIO in the rhioConfig.xml. The rhio is just a
>> copy of the XDS.a RHIO, but with a pixId of "LocalPIX"
>> LocalPIX is configured as
>> <pix>
>> <id>LocalPIX</id>
>> <mllp>
>> <unsecured>mllp://localhost:3600</unsecured>
>> </mllp>
>> <pixServerPropertiesId>Local PIX Server</pixServerPropertiesId>
>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>> </pix>
>>
>> Local PIX Server is configured as
>> <pixProperties>
>> <id>Local PIX Server</id>
>> <facility>XDSDEMO</facility>
>> <application>HIMSS2005</application>
>> <assigningAuthorityNamespaceId>XXXX</assigningAuthorityNamespaceId >
>> <assigningAuthorityUniversalId></assigningAuthorityUniversalId >
>>
>> <assigningAuthorityUniversalIdType>ISO</assigningAuthorityUniversalIdType >
>>
>> </pixProperties>
>>
>>
>> In the patientIdentifier, I am specifiying the
>> assigningAuthorityNamespaceId to XXXX and the
>> assigningAuthorityUniversalId is left blank.
>> Is anyone else having this problem? Am I missing something?
>>
>> Thank you,
>> Corey Spears
>>
Re: OHF Bridge MESA test 10503 [message #36328 is a reply to message #36295] Tue, 30 October 2007 20:56 Go to previous messageGo to next message
Matthew DavisFriend
Messages: 269
Registered: July 2009
Senior Member
Corey,

After reviewing the log bit:
2007-10-30T10:07:25.497-07:00 Starting PatientInfoType[]
SearchPatient(PatientInfoType ( patientIdentifier=[PatientIdType (
idNumber=[ABC10503] assigningAuthority=[AssigningAuthority (
namespaceId=[XXXX] universalId=[] universalIdType=[ISO]
useDefaultAssigningAuthority=[false] universalIdTypeCode=[] )]
)] patientName=[PatientNameType ( familyName=[Stein]
givenName=[Richard] otherName=[] suffix=[] prefix=[] )]
patientDateOfBirth=[01/01/1983] patientSex=[M]
patientAddress=[AddressType ( streetAddress=[2401 4th Ave]
otherDesignation=[] city=[Seattle] stateOrProvince=[WA]
zipOrPostalCode=[98121] country=[] countyParishCode=[] )]
patientPhoneHome=[PhoneType ( unformattedTelephoneNumber=[] )]
patientPhoneBusiness=[PhoneType ( unformattedTelephoneNumber=[] )]
genericAdtValues=[] ), PatientSearchPreferencesType (
quantityLimit=[0] withoutDemographics=[true] ))

This is actually related to the universalIdType being set to "ISO". In
this case, the PIX Consumer is rejecting the the parameter and setting
its default - in this case that is
^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO instead of ^^^^XXXX. Try setting
the universal id type to "" by setting:

idType.getAssigningAuthorityType().setUniversalIdType("");

And see if it works. We'll find some work around or throw an error if
this case comes out.

Please let me know if this works.

Thanks,
-Matt


Matthew Davis wrote:
> Also,
> It is possible, from the Bridge logs, to tell what the current
> configuration setting is so long as you have it on debug logging mode
> (should be the default). If you look at your bridge log file
> (\tomcat\bridge.log or tomcat\bridge\<rhio name>\<faciltiy name>\<user
> name>.log), you will see this line:
>
> [DEBUG][12:41:03][clipse.ohf.bridge.ws.OHFBridge] Starting
> PatientInfoType[] SearchPatient(PatientInfoType (
> patientIdentifier=[PatientIdType ( idNumber=[ABC10503]
> assigningAuthority=[AssigningAuthority ( namespaceId=[XXXX]
> universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
> useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]
> )] patientName=[PatientNameType ( familyName=[] givenName=[]
> otherName=[] suffix=[] prefix=[] )] patientDateOfBirth=[]
> patientSex=[] patientAddress=[AddressType ( streetAddress=[]
> otherDesignation=[] city=[] stateOrProvince=[]
> zipOrPostalCode=[] country=[] countyParishCode=[] )]
> patientPhoneHome=[PhoneType ( unformattedTelephoneNumber=[] )]
> patientPhoneBusiness=[PhoneType ( unformattedTelephoneNumber=[] )]
> genericAdtValues=[] ), PatientSearchPreferencesType (
> quantityLimit=[-1] withoutDemographics=[true] ))
>
> Please find this information in your log for the transaction that you
> ran regarding 10503. As you can see from the details, it will tell us
> whether it's using the default assigning authority or not:
>
> AssigningAuthority ( namespaceId=[XXXX]
> universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
> useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]
>
>
> Thanks,
> -Matt
>
>
>
> Matthew Davis wrote:
>> Hi Corey,
>>
>> It looks like the default value from your PIX configuration settings
>> are being copied into the message. From the OHF Bridge
>> AssigningAuthorityType, there is an option
>> "useDefaultAssigningAuthority". Make sure this is set to "false".
>>
>> From the Bridge MESA Test 1503
>> (org.eclipse.ohf.bridge.ws.tests.mesa.TestMESA1053), we have this:
>>
>> PatientIdType idType = new PatientIdType("ABC10503");
>> idType.getAssigningAuthorityType().setNamespaceId("XXXX");
>>
>> idType.getAssigningAuthorityType().setUseDefaultAssigningAut hority(false);
>>
>>
>> PatientInfoType infoType = new PatientInfoType();
>> infoType.setPatientIdentifier(idType);
>>
>> PatientSearchPreferencesType patientSearchPreferencesType = new
>> PatientSearchPreferencesType();
>> patientSearchPreferencesType.setWithoutDemographics(true);
>>
>>
>> -Matt
>>
>>
>>
>> Corey Spears wrote:
>>> All,
>>> I am using the OHF bridge.
>>> I am trying to run MESA test 10503. This test calls for sending a
>>> PIX query "ABC10503^^^XXXX"
>>> I assume the PIX query should look something like
>>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>>
>>> QPD|Q23^Get Corresponding
>>> IDs|5412693612507688165591841744311|ABC10503^^^XXX
>>> RCP|I
>>>
>>> However I am getting
>>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>>
>>> QPD|Q23^Get Corresponding
>>> IDs|5412693612507688165591841744311|ABC10503^^^&1.3.6.1. 4.1.21367.2007.1.2.400&ISO
>>>
>>> RCP|I
>>>
>>>
>>> I have configured a new RHIO in the rhioConfig.xml. The rhio is just
>>> a copy of the XDS.a RHIO, but with a pixId of "LocalPIX"
>>> LocalPIX is configured as
>>> <pix>
>>> <id>LocalPIX</id>
>>> <mllp>
>>> <unsecured>mllp://localhost:3600</unsecured>
>>> </mllp>
>>> <pixServerPropertiesId>Local PIX Server</pixServerPropertiesId>
>>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>>> </pix>
>>>
>>> Local PIX Server is configured as
>>> <pixProperties>
>>> <id>Local PIX Server</id>
>>> <facility>XDSDEMO</facility>
>>> <application>HIMSS2005</application>
>>> <assigningAuthorityNamespaceId>XXXX</assigningAuthorityNamespaceId >
>>> <assigningAuthorityUniversalId></assigningAuthorityUniversalId >
>>>
>>> <assigningAuthorityUniversalIdType>ISO</assigningAuthorityUniversalIdType >
>>>
>>> </pixProperties>
>>>
>>>
>>> In the patientIdentifier, I am specifiying the
>>> assigningAuthorityNamespaceId to XXXX and the
>>> assigningAuthorityUniversalId is left blank.
>>> Is anyone else having this problem? Am I missing something?
>>>
>>> Thank you,
>>> Corey Spears
>>>
Re: OHF Bridge MESA test 10503 [message #36362 is a reply to message #36328] Tue, 30 October 2007 21:07 Go to previous messageGo to next message
Corey Spears is currently offline Corey SpearsFriend
Messages: 18
Registered: July 2009
Junior Member
Matt,

It looks like this worked for me.

Is this something that will always have to be done? Is there a rule here
that I am missing? I have been assuming that the universalIdType is always
supposed to be "ISO". Is that not the case?

"Matthew Davis" <mattadav@us.ibm.com> wrote in message
news:fg85qf$f0h$1@build.eclipse.org...
> Corey,
>
> After reviewing the log bit:
> 2007-10-30T10:07:25.497-07:00 Starting PatientInfoType[]
> SearchPatient(PatientInfoType ( patientIdentifier=[PatientIdType (
> idNumber=[ABC10503] assigningAuthority=[AssigningAuthority (
> namespaceId=[XXXX] universalId=[] universalIdType=[ISO]
> useDefaultAssigningAuthority=[false] universalIdTypeCode=[] )] )]
> patientName=[PatientNameType ( familyName=[Stein] givenName=[Richard]
> otherName=[] suffix=[] prefix=[] )]
> patientDateOfBirth=[01/01/1983] patientSex=[M]
> patientAddress=[AddressType ( streetAddress=[2401 4th Ave]
> otherDesignation=[] city=[Seattle] stateOrProvince=[WA]
> zipOrPostalCode=[98121] country=[] countyParishCode=[] )]
> patientPhoneHome=[PhoneType ( unformattedTelephoneNumber=[] )]
> patientPhoneBusiness=[PhoneType ( unformattedTelephoneNumber=[] )]
> genericAdtValues=[] ), PatientSearchPreferencesType (
> quantityLimit=[0] withoutDemographics=[true] ))
>
> This is actually related to the universalIdType being set to "ISO". In
> this case, the PIX Consumer is rejecting the the parameter and setting its
> default - in this case that is ^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO
> instead of ^^^^XXXX. Try setting the universal id type to "" by setting:
>
> idType.getAssigningAuthorityType().setUniversalIdType("");
>
> And see if it works. We'll find some work around or throw an error if
> this case comes out.
>
> Please let me know if this works.
>
> Thanks,
> -Matt
>
>
> Matthew Davis wrote:
>> Also,
>> It is possible, from the Bridge logs, to tell what the current
>> configuration setting is so long as you have it on debug logging mode
>> (should be the default). If you look at your bridge log file
>> (\tomcat\bridge.log or tomcat\bridge\<rhio name>\<faciltiy name>\<user
>> name>.log), you will see this line:
>>
>> [DEBUG][12:41:03][clipse.ohf.bridge.ws.OHFBridge] Starting
>> PatientInfoType[] SearchPatient(PatientInfoType (
>> patientIdentifier=[PatientIdType ( idNumber=[ABC10503]
>> assigningAuthority=[AssigningAuthority ( namespaceId=[XXXX]
>> universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
>> useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )] )]
>> patientName=[PatientNameType ( familyName=[] givenName=[] otherName=[]
>> suffix=[] prefix=[] )] patientDateOfBirth=[] patientSex=[]
>> patientAddress=[AddressType ( streetAddress=[] otherDesignation=[]
>> city=[] stateOrProvince=[] zipOrPostalCode=[] country=[]
>> countyParishCode=[] )] patientPhoneHome=[PhoneType (
>> unformattedTelephoneNumber=[] )] patientPhoneBusiness=[PhoneType (
>> unformattedTelephoneNumber=[] )] genericAdtValues=[] ),
>> PatientSearchPreferencesType ( quantityLimit=[-1]
>> withoutDemographics=[true] ))
>>
>> Please find this information in your log for the transaction that you ran
>> regarding 10503. As you can see from the details, it will tell us
>> whether it's using the default assigning authority or not:
>>
>> AssigningAuthority ( namespaceId=[XXXX]
>> universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
>> useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]
>>
>>
>> Thanks,
>> -Matt
>>
>>
>>
>> Matthew Davis wrote:
>>> Hi Corey,
>>>
>>> It looks like the default value from your PIX configuration settings are
>>> being copied into the message. From the OHF Bridge
>>> AssigningAuthorityType, there is an option
>>> "useDefaultAssigningAuthority". Make sure this is set to "false".
>>>
>>> From the Bridge MESA Test 1503
>>> (org.eclipse.ohf.bridge.ws.tests.mesa.TestMESA1053), we have this:
>>>
>>> PatientIdType idType = new PatientIdType("ABC10503");
>>> idType.getAssigningAuthorityType().setNamespaceId("XXXX");
>>>
>>> idType.getAssigningAuthorityType().setUseDefaultAssigningAut hority(false);
>>>
>>> PatientInfoType infoType = new PatientInfoType();
>>> infoType.setPatientIdentifier(idType);
>>>
>>> PatientSearchPreferencesType patientSearchPreferencesType = new
>>> PatientSearchPreferencesType();
>>> patientSearchPreferencesType.setWithoutDemographics(true);
>>>
>>>
>>> -Matt
>>>
>>>
>>>
>>> Corey Spears wrote:
>>>> All,
>>>> I am using the OHF bridge.
>>>> I am trying to run MESA test 10503. This test calls for sending a PIX
>>>> query "ABC10503^^^XXXX"
>>>> I assume the PIX query should look something like
>>>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>>> QPD|Q23^Get Corresponding
>>>> IDs|5412693612507688165591841744311|ABC10503^^^XXX
>>>> RCP|I
>>>>
>>>> However I am getting
>>>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>>> QPD|Q23^Get Corresponding
>>>> IDs|5412693612507688165591841744311|ABC10503^^^&1.3.6.1. 4.1.21367.2007.1.2.400&ISO
>>>> RCP|I
>>>>
>>>>
>>>> I have configured a new RHIO in the rhioConfig.xml. The rhio is just a
>>>> copy of the XDS.a RHIO, but with a pixId of "LocalPIX"
>>>> LocalPIX is configured as
>>>> <pix>
>>>> <id>LocalPIX</id>
>>>> <mllp>
>>>> <unsecured>mllp://localhost:3600</unsecured>
>>>> </mllp>
>>>> <pixServerPropertiesId>Local PIX Server</pixServerPropertiesId>
>>>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>>>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>>>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>>>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>>>> </pix>
>>>>
>>>> Local PIX Server is configured as
>>>> <pixProperties>
>>>> <id>Local PIX Server</id>
>>>> <facility>XDSDEMO</facility>
>>>> <application>HIMSS2005</application>
>>>> <assigningAuthorityNamespaceId>XXXX</assigningAuthorityNamespaceId >
>>>> <assigningAuthorityUniversalId></assigningAuthorityUniversalId >
>>>>
>>>> <assigningAuthorityUniversalIdType>ISO</assigningAuthorityUniversalIdType >
>>>> </pixProperties>
>>>>
>>>>
>>>> In the patientIdentifier, I am specifiying the
>>>> assigningAuthorityNamespaceId to XXXX and the
>>>> assigningAuthorityUniversalId is left blank.
>>>> Is anyone else having this problem? Am I missing something?
>>>>
>>>> Thank you,
>>>> Corey Spears
>>>>
Re: OHF Bridge MESA test 10503 [message #36391 is a reply to message #36362] Tue, 30 October 2007 22:56 Go to previous message
Sondra Renly is currently offline Sondra RenlyFriend
Messages: 39
Registered: July 2009
Member
Corey,

The following are valid:

a) namespaceId only
b) both universalId and universalIdType
c) all 3


Corey Spears wrote:
> Matt,
>
> It looks like this worked for me.
>
> Is this something that will always have to be done? Is there a rule here
> that I am missing? I have been assuming that the universalIdType is always
> supposed to be "ISO". Is that not the case?
Re: OHF Bridge MESA test 10503 [message #582787 is a reply to message #36229] Tue, 30 October 2007 19:46 Go to previous message
Matthew DavisFriend
Messages: 269
Registered: July 2009
Senior Member
Hi Corey,

It looks like the default value from your PIX configuration settings are
being copied into the message. From the OHF Bridge
AssigningAuthorityType, there is an option
"useDefaultAssigningAuthority". Make sure this is set to "false".

From the Bridge MESA Test 1503
(org.eclipse.ohf.bridge.ws.tests.mesa.TestMESA1053), we have this:

PatientIdType idType = new PatientIdType("ABC10503");
idType.getAssigningAuthorityType().setNamespaceId("XXXX");

idType.getAssigningAuthorityType().setUseDefaultAssigningAut hority(false);

PatientInfoType infoType = new PatientInfoType();
infoType.setPatientIdentifier(idType);

PatientSearchPreferencesType patientSearchPreferencesType = new
PatientSearchPreferencesType();
patientSearchPreferencesType.setWithoutDemographics(true);


-Matt



Corey Spears wrote:
> All,
> I am using the OHF bridge.
> I am trying to run MESA test 10503. This test calls for sending a PIX query
> "ABC10503^^^XXXX"
> I assume the PIX query should look something like
> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
> QPD|Q23^Get Corresponding IDs|5412693612507688165591841744311|ABC10503^^^XXX
> RCP|I
>
> However I am getting
> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
> QPD|Q23^Get Corresponding
> IDs|5412693612507688165591841744311|ABC10503^^^&1.3.6.1. 4.1.21367.2007.1.2.400&ISO
> RCP|I
>
>
> I have configured a new RHIO in the rhioConfig.xml. The rhio is just a copy
> of the XDS.a RHIO, but with a pixId of "LocalPIX"
> LocalPIX is configured as
> <pix>
> <id>LocalPIX</id>
> <mllp>
> <unsecured>mllp://localhost:3600</unsecured>
> </mllp>
> <pixServerPropertiesId>Local PIX Server</pixServerPropertiesId>
> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
> </pix>
>
> Local PIX Server is configured as
> <pixProperties>
> <id>Local PIX Server</id>
> <facility>XDSDEMO</facility>
> <application>HIMSS2005</application>
> <assigningAuthorityNamespaceId>XXXX</assigningAuthorityNamespaceId >
> <assigningAuthorityUniversalId></assigningAuthorityUniversalId >
> <assigningAuthorityUniversalIdType>ISO</assigningAuthorityUniversalIdType >
> </pixProperties>
>
>
> In the patientIdentifier, I am specifiying the assigningAuthorityNamespaceId
> to XXXX and the assigningAuthorityUniversalId is left blank.
> Is anyone else having this problem? Am I missing something?
>
> Thank you,
> Corey Spears
>
>
Re: OHF Bridge MESA test 10503 [message #582800 is a reply to message #36263] Tue, 30 October 2007 20:30 Go to previous message
Matthew DavisFriend
Messages: 269
Registered: July 2009
Senior Member
Also,
It is possible, from the Bridge logs, to tell what the current
configuration setting is so long as you have it on debug logging mode
(should be the default). If you look at your bridge log file
(\tomcat\bridge.log or tomcat\bridge\<rhio name>\<faciltiy name>\<user
name>.log), you will see this line:

[DEBUG][12:41:03][clipse.ohf.bridge.ws.OHFBridge] Starting
PatientInfoType[] SearchPatient(PatientInfoType (
patientIdentifier=[PatientIdType ( idNumber=[ABC10503]
assigningAuthority=[AssigningAuthority ( namespaceId=[XXXX]
universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]
)] patientName=[PatientNameType ( familyName=[] givenName=[]
otherName=[] suffix=[] prefix=[] )] patientDateOfBirth=[]
patientSex=[] patientAddress=[AddressType ( streetAddress=[]
otherDesignation=[] city=[] stateOrProvince=[]
zipOrPostalCode=[] country=[] countyParishCode=[] )]
patientPhoneHome=[PhoneType ( unformattedTelephoneNumber=[] )]
patientPhoneBusiness=[PhoneType ( unformattedTelephoneNumber=[] )]
genericAdtValues=[] ), PatientSearchPreferencesType (
quantityLimit=[-1] withoutDemographics=[true] ))

Please find this information in your log for the transaction that you
ran regarding 10503. As you can see from the details, it will tell us
whether it's using the default assigning authority or not:

AssigningAuthority ( namespaceId=[XXXX]
universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]


Thanks,
-Matt



Matthew Davis wrote:
> Hi Corey,
>
> It looks like the default value from your PIX configuration settings are
> being copied into the message. From the OHF Bridge
> AssigningAuthorityType, there is an option
> "useDefaultAssigningAuthority". Make sure this is set to "false".
>
> From the Bridge MESA Test 1503
> (org.eclipse.ohf.bridge.ws.tests.mesa.TestMESA1053), we have this:
>
> PatientIdType idType = new PatientIdType("ABC10503");
> idType.getAssigningAuthorityType().setNamespaceId("XXXX");
>
> idType.getAssigningAuthorityType().setUseDefaultAssigningAut hority(false);
>
> PatientInfoType infoType = new PatientInfoType();
> infoType.setPatientIdentifier(idType);
>
> PatientSearchPreferencesType patientSearchPreferencesType = new
> PatientSearchPreferencesType();
> patientSearchPreferencesType.setWithoutDemographics(true);
>
>
> -Matt
>
>
>
> Corey Spears wrote:
>> All,
>> I am using the OHF bridge.
>> I am trying to run MESA test 10503. This test calls for sending a PIX
>> query "ABC10503^^^XXXX"
>> I assume the PIX query should look something like
>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>
>> QPD|Q23^Get Corresponding
>> IDs|5412693612507688165591841744311|ABC10503^^^XXX
>> RCP|I
>>
>> However I am getting
>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>
>> QPD|Q23^Get Corresponding
>> IDs|5412693612507688165591841744311|ABC10503^^^&1.3.6.1. 4.1.21367.2007.1.2.400&ISO
>>
>> RCP|I
>>
>>
>> I have configured a new RHIO in the rhioConfig.xml. The rhio is just a
>> copy of the XDS.a RHIO, but with a pixId of "LocalPIX"
>> LocalPIX is configured as
>> <pix>
>> <id>LocalPIX</id>
>> <mllp>
>> <unsecured>mllp://localhost:3600</unsecured>
>> </mllp>
>> <pixServerPropertiesId>Local PIX Server</pixServerPropertiesId>
>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>> </pix>
>>
>> Local PIX Server is configured as
>> <pixProperties>
>> <id>Local PIX Server</id>
>> <facility>XDSDEMO</facility>
>> <application>HIMSS2005</application>
>> <assigningAuthorityNamespaceId>XXXX</assigningAuthorityNamespaceId >
>> <assigningAuthorityUniversalId></assigningAuthorityUniversalId >
>>
>> <assigningAuthorityUniversalIdType>ISO</assigningAuthorityUniversalIdType >
>>
>> </pixProperties>
>>
>>
>> In the patientIdentifier, I am specifiying the
>> assigningAuthorityNamespaceId to XXXX and the
>> assigningAuthorityUniversalId is left blank.
>> Is anyone else having this problem? Am I missing something?
>>
>> Thank you,
>> Corey Spears
>>
Re: OHF Bridge MESA test 10503 [message #582812 is a reply to message #36295] Tue, 30 October 2007 20:56 Go to previous message
Matthew DavisFriend
Messages: 269
Registered: July 2009
Senior Member
Corey,

After reviewing the log bit:
2007-10-30T10:07:25.497-07:00 Starting PatientInfoType[]
SearchPatient(PatientInfoType ( patientIdentifier=[PatientIdType (
idNumber=[ABC10503] assigningAuthority=[AssigningAuthority (
namespaceId=[XXXX] universalId=[] universalIdType=[ISO]
useDefaultAssigningAuthority=[false] universalIdTypeCode=[] )]
)] patientName=[PatientNameType ( familyName=[Stein]
givenName=[Richard] otherName=[] suffix=[] prefix=[] )]
patientDateOfBirth=[01/01/1983] patientSex=[M]
patientAddress=[AddressType ( streetAddress=[2401 4th Ave]
otherDesignation=[] city=[Seattle] stateOrProvince=[WA]
zipOrPostalCode=[98121] country=[] countyParishCode=[] )]
patientPhoneHome=[PhoneType ( unformattedTelephoneNumber=[] )]
patientPhoneBusiness=[PhoneType ( unformattedTelephoneNumber=[] )]
genericAdtValues=[] ), PatientSearchPreferencesType (
quantityLimit=[0] withoutDemographics=[true] ))

This is actually related to the universalIdType being set to "ISO". In
this case, the PIX Consumer is rejecting the the parameter and setting
its default - in this case that is
^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO instead of ^^^^XXXX. Try setting
the universal id type to "" by setting:

idType.getAssigningAuthorityType().setUniversalIdType("");

And see if it works. We'll find some work around or throw an error if
this case comes out.

Please let me know if this works.

Thanks,
-Matt


Matthew Davis wrote:
> Also,
> It is possible, from the Bridge logs, to tell what the current
> configuration setting is so long as you have it on debug logging mode
> (should be the default). If you look at your bridge log file
> (\tomcat\bridge.log or tomcat\bridge\<rhio name>\<faciltiy name>\<user
> name>.log), you will see this line:
>
> [DEBUG][12:41:03][clipse.ohf.bridge.ws.OHFBridge] Starting
> PatientInfoType[] SearchPatient(PatientInfoType (
> patientIdentifier=[PatientIdType ( idNumber=[ABC10503]
> assigningAuthority=[AssigningAuthority ( namespaceId=[XXXX]
> universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
> useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]
> )] patientName=[PatientNameType ( familyName=[] givenName=[]
> otherName=[] suffix=[] prefix=[] )] patientDateOfBirth=[]
> patientSex=[] patientAddress=[AddressType ( streetAddress=[]
> otherDesignation=[] city=[] stateOrProvince=[]
> zipOrPostalCode=[] country=[] countyParishCode=[] )]
> patientPhoneHome=[PhoneType ( unformattedTelephoneNumber=[] )]
> patientPhoneBusiness=[PhoneType ( unformattedTelephoneNumber=[] )]
> genericAdtValues=[] ), PatientSearchPreferencesType (
> quantityLimit=[-1] withoutDemographics=[true] ))
>
> Please find this information in your log for the transaction that you
> ran regarding 10503. As you can see from the details, it will tell us
> whether it's using the default assigning authority or not:
>
> AssigningAuthority ( namespaceId=[XXXX]
> universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
> useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]
>
>
> Thanks,
> -Matt
>
>
>
> Matthew Davis wrote:
>> Hi Corey,
>>
>> It looks like the default value from your PIX configuration settings
>> are being copied into the message. From the OHF Bridge
>> AssigningAuthorityType, there is an option
>> "useDefaultAssigningAuthority". Make sure this is set to "false".
>>
>> From the Bridge MESA Test 1503
>> (org.eclipse.ohf.bridge.ws.tests.mesa.TestMESA1053), we have this:
>>
>> PatientIdType idType = new PatientIdType("ABC10503");
>> idType.getAssigningAuthorityType().setNamespaceId("XXXX");
>>
>> idType.getAssigningAuthorityType().setUseDefaultAssigningAut hority(false);
>>
>>
>> PatientInfoType infoType = new PatientInfoType();
>> infoType.setPatientIdentifier(idType);
>>
>> PatientSearchPreferencesType patientSearchPreferencesType = new
>> PatientSearchPreferencesType();
>> patientSearchPreferencesType.setWithoutDemographics(true);
>>
>>
>> -Matt
>>
>>
>>
>> Corey Spears wrote:
>>> All,
>>> I am using the OHF bridge.
>>> I am trying to run MESA test 10503. This test calls for sending a
>>> PIX query "ABC10503^^^XXXX"
>>> I assume the PIX query should look something like
>>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>>
>>> QPD|Q23^Get Corresponding
>>> IDs|5412693612507688165591841744311|ABC10503^^^XXX
>>> RCP|I
>>>
>>> However I am getting
>>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>>
>>> QPD|Q23^Get Corresponding
>>> IDs|5412693612507688165591841744311|ABC10503^^^&1.3.6.1. 4.1.21367.2007.1.2.400&ISO
>>>
>>> RCP|I
>>>
>>>
>>> I have configured a new RHIO in the rhioConfig.xml. The rhio is just
>>> a copy of the XDS.a RHIO, but with a pixId of "LocalPIX"
>>> LocalPIX is configured as
>>> <pix>
>>> <id>LocalPIX</id>
>>> <mllp>
>>> <unsecured>mllp://localhost:3600</unsecured>
>>> </mllp>
>>> <pixServerPropertiesId>Local PIX Server</pixServerPropertiesId>
>>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>>> </pix>
>>>
>>> Local PIX Server is configured as
>>> <pixProperties>
>>> <id>Local PIX Server</id>
>>> <facility>XDSDEMO</facility>
>>> <application>HIMSS2005</application>
>>> <assigningAuthorityNamespaceId>XXXX</assigningAuthorityNamespaceId >
>>> <assigningAuthorityUniversalId></assigningAuthorityUniversalId >
>>>
>>> <assigningAuthorityUniversalIdType>ISO</assigningAuthorityUniversalIdType >
>>>
>>> </pixProperties>
>>>
>>>
>>> In the patientIdentifier, I am specifiying the
>>> assigningAuthorityNamespaceId to XXXX and the
>>> assigningAuthorityUniversalId is left blank.
>>> Is anyone else having this problem? Am I missing something?
>>>
>>> Thank you,
>>> Corey Spears
>>>
Re: OHF Bridge MESA test 10503 [message #582827 is a reply to message #36328] Tue, 30 October 2007 21:07 Go to previous message
Corey Spears is currently offline Corey SpearsFriend
Messages: 18
Registered: July 2009
Junior Member
Matt,

It looks like this worked for me.

Is this something that will always have to be done? Is there a rule here
that I am missing? I have been assuming that the universalIdType is always
supposed to be "ISO". Is that not the case?

"Matthew Davis" <mattadav@us.ibm.com> wrote in message
news:fg85qf$f0h$1@build.eclipse.org...
> Corey,
>
> After reviewing the log bit:
> 2007-10-30T10:07:25.497-07:00 Starting PatientInfoType[]
> SearchPatient(PatientInfoType ( patientIdentifier=[PatientIdType (
> idNumber=[ABC10503] assigningAuthority=[AssigningAuthority (
> namespaceId=[XXXX] universalId=[] universalIdType=[ISO]
> useDefaultAssigningAuthority=[false] universalIdTypeCode=[] )] )]
> patientName=[PatientNameType ( familyName=[Stein] givenName=[Richard]
> otherName=[] suffix=[] prefix=[] )]
> patientDateOfBirth=[01/01/1983] patientSex=[M]
> patientAddress=[AddressType ( streetAddress=[2401 4th Ave]
> otherDesignation=[] city=[Seattle] stateOrProvince=[WA]
> zipOrPostalCode=[98121] country=[] countyParishCode=[] )]
> patientPhoneHome=[PhoneType ( unformattedTelephoneNumber=[] )]
> patientPhoneBusiness=[PhoneType ( unformattedTelephoneNumber=[] )]
> genericAdtValues=[] ), PatientSearchPreferencesType (
> quantityLimit=[0] withoutDemographics=[true] ))
>
> This is actually related to the universalIdType being set to "ISO". In
> this case, the PIX Consumer is rejecting the the parameter and setting its
> default - in this case that is ^^^&1.3.6.1.4.1.21367.2007.1.2.400&ISO
> instead of ^^^^XXXX. Try setting the universal id type to "" by setting:
>
> idType.getAssigningAuthorityType().setUniversalIdType("");
>
> And see if it works. We'll find some work around or throw an error if
> this case comes out.
>
> Please let me know if this works.
>
> Thanks,
> -Matt
>
>
> Matthew Davis wrote:
>> Also,
>> It is possible, from the Bridge logs, to tell what the current
>> configuration setting is so long as you have it on debug logging mode
>> (should be the default). If you look at your bridge log file
>> (\tomcat\bridge.log or tomcat\bridge\<rhio name>\<faciltiy name>\<user
>> name>.log), you will see this line:
>>
>> [DEBUG][12:41:03][clipse.ohf.bridge.ws.OHFBridge] Starting
>> PatientInfoType[] SearchPatient(PatientInfoType (
>> patientIdentifier=[PatientIdType ( idNumber=[ABC10503]
>> assigningAuthority=[AssigningAuthority ( namespaceId=[XXXX]
>> universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
>> useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )] )]
>> patientName=[PatientNameType ( familyName=[] givenName=[] otherName=[]
>> suffix=[] prefix=[] )] patientDateOfBirth=[] patientSex=[]
>> patientAddress=[AddressType ( streetAddress=[] otherDesignation=[]
>> city=[] stateOrProvince=[] zipOrPostalCode=[] country=[]
>> countyParishCode=[] )] patientPhoneHome=[PhoneType (
>> unformattedTelephoneNumber=[] )] patientPhoneBusiness=[PhoneType (
>> unformattedTelephoneNumber=[] )] genericAdtValues=[] ),
>> PatientSearchPreferencesType ( quantityLimit=[-1]
>> withoutDemographics=[true] ))
>>
>> Please find this information in your log for the transaction that you ran
>> regarding 10503. As you can see from the details, it will tell us
>> whether it's using the default assigning authority or not:
>>
>> AssigningAuthority ( namespaceId=[XXXX]
>> universalId=[1.3.6.1.4.1.21367.2005.1.1] universalIdType=[ISO]
>> useDefaultAssigningAuthority=[true] universalIdTypeCode=[] )]
>>
>>
>> Thanks,
>> -Matt
>>
>>
>>
>> Matthew Davis wrote:
>>> Hi Corey,
>>>
>>> It looks like the default value from your PIX configuration settings are
>>> being copied into the message. From the OHF Bridge
>>> AssigningAuthorityType, there is an option
>>> "useDefaultAssigningAuthority". Make sure this is set to "false".
>>>
>>> From the Bridge MESA Test 1503
>>> (org.eclipse.ohf.bridge.ws.tests.mesa.TestMESA1053), we have this:
>>>
>>> PatientIdType idType = new PatientIdType("ABC10503");
>>> idType.getAssigningAuthorityType().setNamespaceId("XXXX");
>>>
>>> idType.getAssigningAuthorityType().setUseDefaultAssigningAut hority(false);
>>>
>>> PatientInfoType infoType = new PatientInfoType();
>>> infoType.setPatientIdentifier(idType);
>>>
>>> PatientSearchPreferencesType patientSearchPreferencesType = new
>>> PatientSearchPreferencesType();
>>> patientSearchPreferencesType.setWithoutDemographics(true);
>>>
>>>
>>> -Matt
>>>
>>>
>>>
>>> Corey Spears wrote:
>>>> All,
>>>> I am using the OHF bridge.
>>>> I am trying to run MESA test 10503. This test calls for sending a PIX
>>>> query "ABC10503^^^XXXX"
>>>> I assume the PIX query should look something like
>>>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>>> QPD|Q23^Get Corresponding
>>>> IDs|5412693612507688165591841744311|ABC10503^^^XXX
>>>> RCP|I
>>>>
>>>> However I am getting
>>>> MSH|^~\&|OHFSource1|HIMSSSANDIEGO|HIMSS2005|XDSDEMO|2007 1030100729-0700||QBP^Q23^QBP_Q21|7250571275013314812|P|2.5
>>>> QPD|Q23^Get Corresponding
>>>> IDs|5412693612507688165591841744311|ABC10503^^^&1.3.6.1. 4.1.21367.2007.1.2.400&ISO
>>>> RCP|I
>>>>
>>>>
>>>> I have configured a new RHIO in the rhioConfig.xml. The rhio is just a
>>>> copy of the XDS.a RHIO, but with a pixId of "LocalPIX"
>>>> LocalPIX is configured as
>>>> <pix>
>>>> <id>LocalPIX</id>
>>>> <mllp>
>>>> <unsecured>mllp://localhost:3600</unsecured>
>>>> </mllp>
>>>> <pixServerPropertiesId>Local PIX Server</pixServerPropertiesId>
>>>> <pixSourcePropertiesId>IBM PIX Server</pixSourcePropertiesId>
>>>> <pixConsumerPropertiesId>IBMPIXPDQClient</pixConsumerPropertiesId >
>>>> <pdqServerPropertiesId>IBM PIX Server</pdqServerPropertiesId>
>>>> <pdqConsumerPropertiesId>IBMPIXPDQClient</pdqConsumerPropertiesId >
>>>> </pix>
>>>>
>>>> Local PIX Server is configured as
>>>> <pixProperties>
>>>> <id>Local PIX Server</id>
>>>> <facility>XDSDEMO</facility>
>>>> <application>HIMSS2005</application>
>>>> <assigningAuthorityNamespaceId>XXXX</assigningAuthorityNamespaceId >
>>>> <assigningAuthorityUniversalId></assigningAuthorityUniversalId >
>>>>
>>>> <assigningAuthorityUniversalIdType>ISO</assigningAuthorityUniversalIdType >
>>>> </pixProperties>
>>>>
>>>>
>>>> In the patientIdentifier, I am specifiying the
>>>> assigningAuthorityNamespaceId to XXXX and the
>>>> assigningAuthorityUniversalId is left blank.
>>>> Is anyone else having this problem? Am I missing something?
>>>>
>>>> Thank you,
>>>> Corey Spears
>>>>
Re: OHF Bridge MESA test 10503 [message #582839 is a reply to message #36362] Tue, 30 October 2007 22:56 Go to previous message
Sondra Renly is currently offline Sondra RenlyFriend
Messages: 39
Registered: July 2009
Member
Corey,

The following are valid:

a) namespaceId only
b) both universalId and universalIdType
c) all 3


Corey Spears wrote:
> Matt,
>
> It looks like this worked for me.
>
> Is this something that will always have to be done? Is there a rule here
> that I am missing? I have been assuming that the universalIdType is always
> supposed to be "ISO". Is that not the case?
Previous Topic:OHF Bridge MESA test 10503
Next Topic:Incremental OHF bulids for Connectathon
Goto Forum:
  


Current Time: Sun Dec 21 12:07:40 GMT 2014

Powered by FUDForum. Page generated in 0.11358 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software