CONNECT 5.1 unable to invoke Adapter PD service

classic Classic list List threaded Threaded
37 messages Options
12
Reply | Threaded
Open this post in threaded view
|

CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti
Hi,

When we have configured our Adapter level PD responding service CONNECT 5.1 is not able to invoke it. For plugging our Adapter we have changed the AdapterMpiConfig.xml but still we are getting the following error. This is emergency, we are reaching deadline and we are stuck here. Please Help !




2018-04-26 23:42:17,322 WARN  [org.apache.cxf.phase.PhaseInterceptorChain] (default task-1) Interceptor for {urn:gov:hhs:fha:nhinc:adaptermpi}AdapterMpiPortTypeService#{urn:gov:hhs:fha:nhinc:adaptermpi}FindCandidates has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message.
        at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
        at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277)
        at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
        at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
        at com.sun.proxy.$Proxy286.findCandidates(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at gov.hhs.fha.nhinc.webserviceproxy.WebServiceProxyHelper.invokeTheMethod(WebServiceProxyHelper.java:279)
        at gov.hhs.fha.nhinc.webserviceproxy.WebServiceProxyHelper.invokePort(WebServiceProxyHelper.java:359)
        at gov.hhs.fha.nhinc.webserviceproxy.WebServiceProxyHelper.invokePortWithRetry(WebServiceProxyHelper.java:407)
        at gov.hhs.fha.nhinc.webserviceproxy.WebServiceProxyHelper.invokePort(WebServiceProxyHelper.java:333)
        at gov.hhs.fha.nhinc.messaging.client.CONNECTBaseClient.invokePort(CONNECTBaseClient.java:54)
        at gov.hhs.fha.nhinc.mpi.adapter.proxy.AdapterMpiProxyWebServiceUnsecuredImpl.findCandidatesMpiUnsecured(AdapterMpiProxyWebServiceUnsecuredImpl.java:120)
        at gov.hhs.fha.nhinc.mpi.adapter.proxy.AdapterMpiProxyWebServiceUnsecuredImpl.findCandidates(AdapterMpiProxyWebServiceUnsecuredImpl.java:82)
        at gov.hhs.fha.nhinc.mpi.adapter.proxy.AdapterMpiProxyWebServiceUnsecuredImpl$$FastClassBySpringCGLIB$$ff5b20d7.invoke(<generated>)
        at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
        at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:718)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
        at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:52)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168)
        at org.springframework.aop.framework.adapter.AfterReturningAdviceInterceptor.invoke(AfterReturningAdviceInterceptor.java:52)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168)
        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653)
        at gov.hhs.fha.nhinc.mpi.adapter.proxy.AdapterMpiProxyWebServiceUnsecuredImpl$$EnhancerBySpringCGLIB$$c7e1d5c4.findCandidates(<generated>)
        at gov.hhs.fha.nhinc.patientdiscovery.PatientDiscovery201305Processor.queryMpiForPatients(PatientDiscovery201305Processor.java:272)
        at gov.hhs.fha.nhinc.patientdiscovery.PatientDiscovery201305Processor.queryMpi(PatientDiscovery201305Processor.java:260)
        at gov.hhs.fha.nhinc.patientdiscovery.PatientDiscovery201305Processor.process201305(PatientDiscovery201305Processor.java:83)
        at gov.hhs.fha.nhinc.patientdiscovery.inbound.StandardInboundPatientDiscovery.process(StandardInboundPatientDiscovery.java:85)
        at gov.hhs.fha.nhinc.patientdiscovery.inbound.StandardInboundPatientDiscovery.respondingGatewayPRPAIN201305UV02(StandardInboundPatientDiscovery.java:74)
        at gov.hhs.fha.nhinc.patientdiscovery.inbound.StandardInboundPatientDiscovery$$FastClassBySpringCGLIB$$ae5e0583.invoke(<generated>)
Reply | Threaded
Open this post in threaded view
|

Re: CONNECT 5.1 unable to invoke Adapter PD service

Tabassum
Administrator
Sai,
Can you post server logs, internalExchangeInfo and proxy config file.
Thanks
Tabassum
(CONNECT Product Team Member)
Reply | Threaded
Open this post in threaded view
|

Re: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti
Reply | Threaded
Open this post in threaded view
|

Re: CONNECT 5.1 unable to invoke Adapter PD service

Tabassum
Administrator
Sai,
I found this error in your server logs,
org.apache.cxf.transport.http.HTTPException: HTTP response '400: Bad Request'
when communicating with
http://10.252.0.68/Adapter/PatientDiscovery/A_0/AdapterComponentMpi.svc        at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1600)

Check if your sevice url is correct and you have a service up and running on this url.
Thanks
Tabassum
(CONNECT Product Team Member)
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

It is working fine

 

 

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Tabassum [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 01 May 2018 18:14
To: SaiVennelakanti
Subject: Re: CONNECT 5.1 unable to invoke Adapter PD service

 

Sai,
I found this error in your server logs,
org.apache.cxf.transport.http.HTTPException: HTTP response '400: Bad Request'
when communicating with
http://10.252.0.68/Adapter/PatientDiscovery/A_0/AdapterComponentMpi.svc        at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1600)

Check if your sevice url is correct and you have a service up and running on this url.

Thanks
Tabassum
(CONNECT Product Team Member)

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7580969.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML


AdapterComponentMpiSVC.png (77K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
Sai, were you able to establish a connection to your adapter endpoint or is it still returning 400:

org.apache.cxf.transport.http.HTTPException: HTTP response '400: Bad Request'
when communicating with
http://10.252.0.68/Adapter/PatientDiscovery/A_0/AdapterComponentMpi.svc 
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

It is still returning 404 – Bad error

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 04 May 2018 19:11
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

Sai, were you able to establish a connection to your adapter endpoint or is it still returning 400:

org.apache.cxf.transport.http.HTTPException: HTTP response '400: Bad Request'
when communicating with
http://10.252.0.68/Adapter/PatientDiscovery/A_0/AdapterComponentMpi.svc 

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7580978.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti
In reply to this post by Tabassum

I think when the AdapterMpi configuration is loaded in Spring and the service is being invoked, there is some problem. Please note that this is a .NET service that is being loaded.

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Saikrishna Vennelakanti [mailto:[hidden email]]
Sent: 01 May 2018 19:07
To: 'Tabassum [via CONNECT Community Forum]'
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

It is working fine

 

 

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Tabassum [via CONNECT Community Forum] [[hidden email]]
Sent: 01 May 2018 18:14
To: SaiVennelakanti
Subject: Re: CONNECT 5.1 unable to invoke Adapter PD service

 

Sai,
I found this error in your server logs,
org.apache.cxf.transport.http.HTTPException: HTTP response '400: Bad Request'
when communicating with
http://10.252.0.68/Adapter/PatientDiscovery/A_0/AdapterComponentMpi.svc        at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1600)

Check if your sevice url is correct and you have a service up and running on this url.

Thanks
Tabassum
(CONNECT Product Team Member)

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7580969.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti
In reply to this post by Sovann Huynh

Any fix available for the 5.1 that we need to apply for fixing this issue?

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Saikrishna Vennelakanti [mailto:[hidden email]]
Sent: 04 May 2018 20:58
To: 'Sovann Huynh [via CONNECT Community Forum]'
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

It is still returning 404 – Bad error

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [[hidden email]]
Sent: 04 May 2018 19:11
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

Sai, were you able to establish a connection to your adapter endpoint or is it still returning 400:

org.apache.cxf.transport.http.HTTPException: HTTP response '400: Bad Request'
when communicating with
http://10.252.0.68/Adapter/PatientDiscovery/A_0/AdapterComponentMpi.svc 

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7580978.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
Sai, what fix are you asking for. What does your adapter not like about the request message?
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

Not sure. When we test our Adapter service with SOAPUI it is working perfectly. Infact this service was working successfully with Aurion as part of FL start HIE. So I think there is some problem in the way the invoke is happening in C5.1

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 07 May 2018 19:53
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

Sai, what fix are you asking for. What does your adapter not like about the request message?

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7580987.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
Please attach the entire server log from a successful transaction using SoapUI. Without in-depth knowledge of your adapter, it will be difficult to determine why it's returning a 400. We've already assisted in the implementation of CONNECT 5.1.1 without encountering patient discovery adapter issues. Also, please download and use CONNECT 5.1.1 as we are not supporting CONNECT 5.1 (you just need to deploy the updated ear file) - see https://connectopensource.atlassian.net/wiki/spaces/CONNECTWIKI/pages/117610137/CONNECT+Binaries+by+Release
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

The following is the request that was processed successfully by our adapter. The test data is based on DIL. The Adapter service is an Unsecured one as this will be within our network. Please let me know what else information you need to help us out on this issue.

 

<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:urn="urn:hl7-org:v3" xmlns:urn1="urn:gov:hhs:fha:nhinc:common:nhinccommon" xmlns:add="http://schemas.xmlsoap.org/ws/2004/08/addressing"><s:Header xmlns:add="http://www.w3.org/2005/08/addressing"><add:Action>FindCandidates</add:Action></s:Header><s:Body><RespondingGateway_PRPA_IN201305UV02RequestType ITSVersion="XML_1.0" xmlns="urn:hl7-org:v3" xmlns:ns2="urn:gov:hhs:fha:nhinc:common:nhinccommon" xmlns:ns3="http://www.w3.org/2005/08/addressing" xmlns:ns4="urn:gov:hhs:fha:nhinc:common:patientcorrelationfacade" xmlns:ns5="http://www.hhs.gov/healthit/nhin" xmlns:ns6="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:ns7="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:ns8="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"><PRPA_IN201305UV02><id extension="-5a3e95b1:11d1fa33d45:-7f9b" root="2.16.840.1.113883.3.1259.10.1003" /><creationTime value="20120618155123" /><interactionId extension="PRPA_IN201305UV02" root="2.16.840.1.113883.1.6" /><processingCode code="T" /><processingModeCode code="T" /><acceptAckCode code="AL" /><receiver typeCode="RCV"><device classCode="DEV" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.6810.23" /><asAgent classCode="AGNT"><representedOrganization classCode="ORG" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.6810.23" /></representedOrganization></asAgent></device></receiver><sender typeCode="SND"><device classCode="DEV" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.1259.10.1003" /><asAgent classCode="AGNT"><representedOrganization classCode="ORG" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.1259.10.1003" /></representedOrganization></asAgent></device></sender><controlActProcess classCode="CACT" moodCode="EVN"><code code="PRPA_TE201305UV02" codeSystem="2.16.840.1.113883.1.6" /><authorOrPerformer contextControlCode="AP" typeCode="AUT"><assignedDevice classCode="ASSIGNED"><id root="2.16.840.1.113883.3.1259.10.1003" /></assignedDevice></authorOrPerformer><queryByParameter><queryId extension="-abd3453dcd24wkkks545" root="2.16.840.1.113883.3.1259.10.1003" /><statusCode code="new" /><responseModalityCode code="R" /><responsePriorityCode code="I" /><parameterList><livingSubjectAdministrativeGender><value code="F" /><semanticsText>LivingSubject.administrativeGender</semanticsText></livingSubjectAdministrativeGender><livingSubjectBirthTime><value operator="I" value="19831017" /><semanticsText>LivingSubject.birthTime</semanticsText></livingSubjectBirthTime><livingSubjectId><value extension="666660010" root="2.16.840.1.113883.4.1" /><semanticsText>LivingSubject.id</semanticsText></livingSubjectId><livingSubjectId><value extension="RI0004.000000010" root="2.16.840.1.113883.3.1259.10.1003" /><semanticsText>LivingSubject.id</semanticsText></livingSubjectId><livingSubjectName><value><family partType="FAM">Davidson</family><given partType="GIV">Amy</given><given partType="GIV">C</given></value><semanticsText>LivingSubject.name</semanticsText></livingSubjectName><patientAddress><value><postBox partType="POB" /><city partType="CTY">Springfield</city><state partType="STA">MO</state><postalCode partType="ZIP">65801</postalCode><country partType="CNT">USA</country><streetAddressLine partType="SAL">809 First Ave</streetAddressLine></value><semanticsText>Patient.addr</semanticsText></patientAddress></parameterList></queryByParameter></controlActProcess></PRPA_IN201305UV02></RespondingGateway_PRPA_IN201305UV02RequestType></s:Body></s:Envelope>

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 08 May 2018 01:20
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

Please attach the entire server log from a successful transaction using SoapUI. Without in-depth knowledge of your adapter, it will be difficult to determine why it's returning a 400. We've already assisted in the implementation of CONNECT 5.1.1 without encountering patient discovery adapter issues. Also, please download and use CONNECT 5.1.1 as we are not supporting CONNECT 5.1 (you just need to deploy the updated ear file) - see https://connectopensource.atlassian.net/wiki/spaces/CONNECTWIKI/pages/117610137/CONNECT+Binaries+by+Release

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7580990.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
The request to the adapter has not changed in CONNECT. Have you compared the adapter request from CONNECT to the adapter request generated by your SoapUI project?
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

Here is the CONNECT request. The differences are : soap:Header, Assertion. The other difference is our service was expecting RespondingGateway_PRPA_IN201305UV02RequestType whereas CONNECT was sending RespondingGateway_PRPA_IN201305UV02Request.

 

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body><RespondingGateway_PRPA_IN201305UV02Request xmlns="urn:hl7-org:v3" xmlns:ns2="urn:hl7-org:sdtc" xmlns:ns3="urn:gov:hhs:fha:nhinc:common:nhinccommon" xmlns:ns4="http://www.w3.org/2005/08/addressing" xmlns:ns5="urn:gov:hhs:fha:nhinc:common:patientcorrelationfacade"><PRPA_IN201305UV02 ITSVersion="XML_1.0"><id root="2.16.840.1.113883.3.1259.10.1003" extension="-5a3e95b1:11d1fa33d45:-7f9b"/><creationTime value="20120618155123"/><interactionId root="2.16.840.1.113883.1.6" extension="PRPA_IN201305UV02"/><processingCode code="T"/><processingModeCode code="T"/><acceptAckCode code="AL"/><receiver typeCode="RCV"><device classCode="DEV" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.6810.23"/><asAgent classCode="AGNT"><representedOrganization classCode="ORG" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.6810.23"/></representedOrganization></asAgent></device></receiver><sender typeCode="SND"><device classCode="DEV" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.1259.10.1003"/><asAgent classCode="AGNT"><representedOrganization classCode="ORG" determinerCode="INSTANCE"><id root="2.16.840.1.113883.3.1259.10.1003"/></representedOrganization></asAgent></device></sender><controlActProcess classCode="CACT" moodCode="EVN"><code code="PRPA_TE201305UV02" codeSystem="2.16.840.1.113883.1.6"/><authorOrPerformer typeCode="AUT" contextControlCode="AP"><assignedDevice classCode="ASSIGNED"><id root="2.16.840.1.113883.3.1259.10.1003"/></assignedDevice></authorOrPerformer><queryByParameter><queryId root="2.16.840.1.113883.3.1259.10.1003" extension="-abd3453dcd24wkkks545"/><statusCode code="new"/><responseModalityCode code="R"/><responsePriorityCode code="I"/><parameterList><livingSubjectAdministrativeGender><value code="F"/><semanticsText>LivingSubject.administrativeGender</semanticsText></livingSubjectAdministrativeGender><livingSubjectBirthTime><value value="19831017" operator="I"/><semanticsText>LivingSubject.birthTime</semanticsText></livingSubjectBirthTime><livingSubjectId><value root="2.16.840.1.113883.4.1" extension="666660010"/><semanticsText>LivingSubject.id</semanticsText></livingSubjectId><livingSubjectId><value root="2.16.840.1.113883.3.1259.10.1003" extension="RI0004.000000010"/><semanticsText>LivingSubject.id</semanticsText></livingSubjectId><livingSubjectName><value><family partType="FAM">Davidson</family><given partType="GIV">Amy</given><given partType="GIV">C</given></value><semanticsText>LivingSubject.name</semanticsText></livingSubjectName><patientAddress><value><postBox partType="POB"></postBox><city partType="CTY">Springfield</city><state partType="STA">MO</state><postalCode partType="ZIP">65801</postalCode><country partType="CNT">USA</country><streetAddressLine partType="SAL">809 First Ave</streetAddressLine>                                                                         </value><semanticsText>Patient.addr</semanticsText></patientAddress></parameterList></queryByParameter></controlActProcess></PRPA_IN201305UV02><assertion><ns3:homeCommunity><ns3:homeCommunityId>urn:oid:2.16.840.1.113883.3.1259.10.1003</ns3:homeCommunityId></ns3:homeCommunity><ns3:uniquePatientId>RI0004.000000010^^^&amp;2.16.840.1.113883.3.1259.10.1003&amp;ISO</ns3:uniquePatientId><ns3:userInfo><ns3:personName><ns3:familyName>Testcase</ns3:familyName><ns3:givenName>Lab</ns3:givenName><ns3:secondNameOrInitials>IT</ns3:secondNameOrInitials><ns3:fullName>Lab IT Testcase</ns3:fullName></ns3:personName><ns3:userName>UID=TS: PRL-R-0000.0-2011 TC: PD-R-0000.0-2011</ns3:userName><ns3:org><ns3:homeCommunityId>urn:oid:2.16.840.1.113883.3.1259.10.1003</ns3:homeCommunityId><ns3:name>2.16.840.1.113883.3.1259.10.1003</ns3:name></ns3:org><ns3:roleCoded><ns3:code>46255001</ns3:code><ns3:codeSystem>2.16.840.1.113883.6.96</ns3:codeSystem><ns3:codeSystemName>SNOMED_CT</ns3:codeSystemName><ns3:displayName>Pharmacist</ns3:displayName></ns3:roleCoded></ns3:userInfo><ns3:authorized>false</ns3:authorized><ns3:purposeOfDisclosureCoded><ns3:code>TREATMENT</ns3:code><ns3:codeSystem>2.16.840.1.113883.3.18.7.1</ns3:codeSystem><ns3:codeSystemName>nhin-purpose</ns3:codeSystemName><ns3:displayName>Treatment</ns3:displayName></ns3:purposeOfDisclosureCoded><ns3:samlAuthnStatement><ns3:authInstant>2018-04-27T03:43:00.512Z</ns3:authInstant><ns3:authContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:X509</ns3:authContextClassRef></ns3:samlAuthnStatement><ns3:samlSignature><ns3:keyInfo><ns3:rsaKeyValueModulus></ns3:rsaKeyValueModulus><ns3:rsaKeyValueExponent></ns3:rsaKeyValueExponent></ns3:keyInfo><ns3:signatureValue></ns3:signatureValue></ns3:samlSignature><ns3:samlIssuer><ns3:issuer>C=US,O=AEGISnetInc,CN=dilhn003.dil.aegis.net</ns3:issuer><ns3:issuerFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName</ns3:issuerFormat></ns3:samlIssuer><ns3:samlSubjectConfirmations><ns3:method>urn:oasis:names:tc:SAML:2.0:cm:holder-of-key</ns3:method><ns3:subjectCondition/></ns3:samlSubjectConfirmations><ns3:messageId>urn:uuid:095c3944-ec95-4123-ba72-721f86ac4d15</ns3:messageId><ns3:relatesToList xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/></assertion></RespondingGateway_PRPA_IN201305UV02Request></soap:Body></soap:Envelope>

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 08 May 2018 19:42
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

The request to the adapter has not changed in CONNECT. Have you compared the adapter request from CONNECT to the adapter request generated by your SoapUI project?

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7580993.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
CONNECT is sending a valid adapter request and it has not been changed. You will need to update your adapter to accept the request.
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

When we run the soap message that CONNECT was sending to our adapter using SOAPUI response is coming. But when we try to invoke the adapter from CONNECT it is still giving 400-bad request error.

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 09 May 2018 17:48
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

CONNECT is sending a valid adapter request and it has not been changed. You will need to update your adapter to accept the request.

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7580997.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
Troubleshooting will need to be performed on your adapter end. Per the logs, a connection is made to your adapter and the valid request message is received. Unfortunately, we are unable to assist in determining why your adapter is rejecting the request.
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

SaiVennelakanti

There is no call happening to my adapter. If there is a call then a log will be generated from my adapter and this is not happening. Please find attached the CONNECT server log. The adapter is http://10.252.0.68/GuardianMPIWebServiceUnSecured/AdapterComponentMpi.svc. May be there is problem in loading unsecured adapter. Please look into it.

 

We have installed the CONNECT by compiling the 5.1 code base from GITHUB. If there are tools to help in debugging let us know.

 

Regards,

Saikrishna

 

The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying

 

From: Sovann Huynh [via CONNECT Community Forum] [mailto:[hidden email]]
Sent: 09 May 2018 22:44
To: SaiVennelakanti
Subject: RE: CONNECT 5.1 unable to invoke Adapter PD service

 

Troubleshooting will need to be performed on your adapter end. Per the logs, a connection is made to your adapter and the valid request message is received. Unfortunately, we are unable to assist in determining why your adapter is rejecting the request.

Sovann
CONNECT Product Team Member

 


If you reply to this email, your message will be added to the discussion below:

http://forums.connectopensource.org/CONNECT-5-1-unable-to-invoke-Adapter-PD-service-tp7580966p7580999.html

To unsubscribe from CONNECT 5.1 unable to invoke Adapter PD service, click here.
NAML


server.log (136K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: CONNECT 5.1 unable to invoke Adapter PD service

Sovann Huynh
Administrator
CONNECT 5.1.1 out-of-the-box has been thoroughly tested, including Patient Discovery which includes connections to our reference adapters and no issues were found. Without knowledge of why your adapter is rejecting the request, we are unable to assist you in troubleshooting further. If you can figure out why your adapter is rejecting the request, please let us know and we can try to investigate further.
Sovann
CONNECT Product Team Member
12