RE: [ihe-hpd-implementors:347] Abridged summary of ihe-hpd-implementors@googlegroups.com - 1 update in 1 topic

[Nagesh Bashyam]

Have you seen sitenv.org ? provider directory test tool ? http://sitenv.org/web/site/provider-directory-test-tool

 

Is your tool going to be different than the above tool ?

 

From: ihe-hpd-im...@googlegroups.com [mailto:ihe-hpd-im...@googlegroups.com]
Sent: Tuesday, January 20, 2015 4:21 AM
To: Abridged recipients
Subject: [ihe-hpd-implementors:347] Abridged summary of ihe-hpd-im...@googlegroups.com - 1 update in 1 topic

 

ihe-hpd-im...@googlegroups.com

Google Groups

Today's topic summary
View all topics

·         Automated test drivers for connectathon tests? - 1 Update

Automated test drivers for connectathon tests?

dcsillag....@gmail.com: Jan 19 07:19AM -0800 I'm looking to write an automated test driver for the connectathon tests, and was wondering if somebody had already done this before I spend a bunch of time. Most of them don't look too ...more

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to ihe-hpd-implemen...@googlegroups.com.

 

[Drew Csillag]

I’ve seen the sitenv tool and used it.  I was looking specifically for tests that matched those that are in Gazelle for the 2015 Connectathon next week, with the datasets it expects, which are different than the PDTT.

--
You received this message because you are subscribed to the Google Groups "ihe-hpd-implementors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ihe-hpd-implemen...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Anne-Gaëlle Bergé]

Gazelle HPD Simulator provided by IHE Europe development team has been initialized with the providers defined for the connectathon.
Sample request/response showing professionals: http://gazelle.ihe.net/HPDSimulator/messages/messageDisplay.seam?id=53
Sample request/response showing organizations: http://gazelle.ihe.net/HPDSimulator/messages/messageDisplay.seam?id=55
The simulator also embeds a validator for checking the conformance of your messages.
Tool is accessible at http://gazelle.ihe.net/HPDSimulator
Documentation: http://gazelle.ihe.net/content/hpd-simulator

Do not hesitate to contact me if you have any questions

Anne-Gaëlle

Anne-Gaëlle BERGÉ
IHE Europe Development
Gazelle team

KEREVAL
4, rue Hélène Boucher
Z.A. Bellevue
35235 Thorigné Fouillard
Tel : +33 (0)2 23 20 36 64
http://www.kereval.com

[Drew Csillag]

Hi Anne-Gaëlle,

 

Not 100% sure if this is your service or mine, but it looks as though there may be something off with the Provider Information Directory Service at http://ovh1.ihe-europe.net:8180/HPDSimulator-ejb/ProviderInformationDirectory_Service/ProviderInformationDirectory_PortType?wsdl.  It looks like addressing isn’t turned on in neither the WSDL nor the service itself.  The WSDL should contain something like this: <wsaw:UsingAddressing required="true" />

 

I tried sent the WS-Addressing headers anyway, and I still get this fault:

com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Cannot uniquely indentify operation: {urn:oasis:names:tc:DSML:2:0:core}batchRequest Please see the server log to find more detail regarding exact cause of the failure.

 

When I’ve got this in the past, it was because the feed and query operations have the same signature (they receive and return the same types), the server is unable to figure out which one the request is for if WS-Addressing isn’t turned on.

 

Thanks,

Drew Csillag

[Drew Csillag]

Also, according to the reference WSDL (referenced by TF Vol2x Appendix W) here:

    ftp://ftp.ihe.net/TF_Implementation_Material/ITI/wsdl/HPD_ProviderInformationDirectory.wsdl

The <port name= part in the WSDL should be ProviderInformationDirectory_Port_Soap not ProviderInformationDirectory_PortType.

 

For what it’s worth, the other implementers I’ve been working with have it as …_Port_Soap also.

 

Vol 2x Appendix V WSP201 seems to imply it should be _Port_Soap12, but I’m not 100% sure that I’m applying the rule properly, though Example 1 under V.3.2.1.3 seems to imply it.

 

Thanks,

Drew Csillag

[Greg Carver]

I haven't checked to make sure the tests are unchanged, but these are the ldap queries I've curated for previous connectathons:

Test Step 100 (hcIdentifier=*O-343434*)

Test Step 105 (o=Mercy Health Center)

Test Step 115 (|(hcRegisteredName~=Saint-André)(hcRegisteredName~=Saint-Andre))

Test Step 125 Part 1 (&(hpdProviderPracticeAddress~=city=Toronto)(hpdProviderPracticeAddress~=state=Ontario))

Test Step 125 Part 2 (&(hpdProviderPracticeAddress~=city=Bordeaux)(hpdProviderPracticeAddress~=country=France))

Test Step 200 (description=Oncology)

Test Step 205 (displayName~=Marston)

Test Step 210 (|(physicalDeliveryOfficeName=Hunting Park Medical Center)(physicalDeliveryOfficeName=Hunting Park Health Center))

Test Step 300 (memberOf=cn=1.3.6.1.4.1.21367.13.95.11,ou=Relationship,O=HPDTEST,DC=HPD,C=US)

Greg

[Drew Csillag]

Greg,

 

That’s exactly what I was looking for!  Thanks!

 

Drew

[Anne-Gaëlle Bergé]

Hi Drew,

Thank you for your feedback. I confirm that the addressing is turned on. I have investigated a little bit and managed to reproduce the error. Actually, I made a typo and so the expected action was not correct.
Concerning the port name, I have also change it to ..._Port_Soap. The sample WSDL uses Port_Soap whereas the ITI appendix uses Port_Soap_12 but let's follow the other implementation and use the sample as reference.
I have just released a new version of the simulator, feel free to use it.

Best regards,

Anne-Gaëlle

Anne-Gaëlle BERGÉ
IHE Europe Development
Gazelle team

KEREVAL
4, rue Hélène Boucher
Z.A. Bellevue
35235 Thorigné Fouillard
Tel : +33 (0)2 23 20 36 64
http://www.kereval.com