Quantcast

Clarity needed on Patient Discovery and Patient Correlation

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Clarity needed on Patient Discovery and Patient Correlation

khk1216
Hi Team,
Currently i am using Connect4.5.
I have a query regarding the Patient Discovery and Patient Correlation.
I have gone thru CONNECTUniversalClientGUI, in which the Patient Discovery and Patient Correlation queries are made with the same Assertion.

My question is:
1. What is significance of using the Assertion?
2. Can i make a Patient Correlation query independently without using the PD assertion. Do i have alternative path.

Help me if i am in wrong assumption.

Thank you

--
Regard's
Hari Krishna Kaja
+91 9000018373
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

Sovann Huynh
Administrator
Hi there, can you please clarify what assertion this is in regards to? The Universal Client allows you to execute a PD query, it's not intended to query patient correlations.
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

khk1216
My problem statement is:  I have to interact the Connect with WS, but could not able to generate the clients for that. And help me how to do the query patient correlations details.?

Getting below error when generating the client for PD:
[ERROR] IOException thrown when processing "http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=datatypes
e.xsd". Exception: java.io.IOException: Premature EOF.


[ERROR] Attribute name "v2000" associated with an element type "xs:enumeration" must be followed by the ' = ' character.
  line 7128 of http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=../coreschemas/voc.xsd

[ERROR] org.xml.sax.SAXParseException; systemId: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=../c
chemas/voc.xsd; lineNumber: 7128; columnNumber: 1; Attribute name "v2000" associated with an element type "xs:enumeration" mus
 followed by the ' = ' character.
  line 1 of http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?wsdl

        Failed to parse the WSDL.


=====================================
=====================================
Error From server:
=====================================
=====================================
[#|2016-01-31T22:18:55.295+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=136;_ThreadName=http-thread-pool-8080(4);|Inbound Message
----------------------------
ID: 19
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?wsdl
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8], accept-encoding=[gzip, deflate, sdc
h], accept-language=[en-US,en;q=0.8], connection=[keep-alive], Content-Type=[null], cookie=[JSESSIONID=885266296e1d175663689283442
6; treeForm_tree-hi=treeForm:tree:applications], host=[localhost:8080], upgrade-insecure-requests=[1], user-agent=[Mozilla/5.0 (Wi
ndows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36]}
--------------------------------------|#]

[#|2016-01-31T22:19:37.229+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=134;_ThreadName=http-thread-pool-8080(2);|Inbound Message
----------------------------
ID: 20
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?wsdl
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:19:37.385+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=135;_ThreadName=http-thread-pool-8080(3);|Inbound Message
----------------------------
ID: 21
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=classpath:schemas/nhinc/hl7/RespondingGateway_PR
PA_IN201305UV02Request.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:19:37.392+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=136;_ThreadName=http-thread-pool-8080(4);|Inbound Message
----------------------------
ID: 22
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=../../HL7V3/NE2008/multicacheschemas/PRPA_IN2013
05UV02.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:19:37.404+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=137;_ThreadName=http-thread-pool-8080(5);|Inbound Message
----------------------------
ID: 23
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=../coreschemas/infrastructureRoot.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:19:37.411+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=137;_ThreadName=http-thread-pool-8080(5);|Inbound Message
----------------------------
ID: 24
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=../coreschemas/voc.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:19:37.928+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=134;_ThreadName=http-thread-pool-8080(2);|Inbound Message
----------------------------
ID: 25
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=datatypes.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:21:07.938+0530|WARNING|glassfish3.1.2|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=137;_ThreadName=http-t
hread-pool-8080(5);|Interceptor for {urn:gov:hhs:fha:nhinc:adaptermpi}AdapterMpiService has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: java.io.IOException: Client is busy or timed out
        at org.apache.cxf.frontend.WSDLGetInterceptor.handleMessage(WSDLGetInterceptor.java:148)
        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
        at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
        at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
        at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:218)
        at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:198)
        at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
        at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:158)
        at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:243)
        at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:168)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
        at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:219)
        at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
        at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
        at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
        at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
        at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
        at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
        at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
        at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
        at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
        at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
        at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
        at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
        at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
        at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
        at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.ctc.wstx.exc.WstxIOException: java.io.IOException: Client is busy or timed out
        at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteEndTag(BaseNsStreamWriter.java:717)
        at com.ctc.wstx.sw.BaseNsStreamWriter.writeEndElement(BaseNsStreamWriter.java:280)
        at org.apache.cxf.staxutils.StaxUtils.writeElement(StaxUtils.java:852)
        at org.apache.cxf.staxutils.StaxUtils.writeElement(StaxUtils.java:745)
        at org.apache.cxf.staxutils.StaxUtils.writeNode(StaxUtils.java:882)
        at org.apache.cxf.staxutils.StaxUtils.writeElement(StaxUtils.java:847)
        at org.apache.cxf.staxutils.StaxUtils.writeElement(StaxUtils.java:745)
        at org.apache.cxf.staxutils.StaxUtils.writeNode(StaxUtils.java:882)
        at org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:723)
        at org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:711)
        at org.apache.cxf.staxutils.StaxUtils.writeNode(StaxUtils.java:901)
        at org.apache.cxf.frontend.WSDLGetInterceptor.handleMessage(WSDLGetInterceptor.java:129)
        ... 35 more
Caused by: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Client is busy or timed out
        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:430)
        at com.sun.grizzly.util.buf.ByteChunk.flushBuffer(ByteChunk.java:458)
        at com.sun.grizzly.util.buf.ByteChunk.append(ByteChunk.java:380)
        at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:455)
        at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:442)
        at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:160)
        at org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:51)
        at com.ctc.wstx.io.UTF8Writer.write(UTF8Writer.java:143)
        at com.ctc.wstx.sw.BufferingXmlWriter.flushBuffer(BufferingXmlWriter.java:1366)
        at com.ctc.wstx.sw.BufferingXmlWriter.fastWriteRaw(BufferingXmlWriter.java:1412)
        at com.ctc.wstx.sw.BufferingXmlWriter.writeEndTag(BufferingXmlWriter.java:830)
        at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteEndTag(BaseNsStreamWriter.java:715)
        ... 46 more
Caused by: java.io.IOException: Client is busy or timed out
        at com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:129)
        at com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:76)
        at com.sun.grizzly.http.SocketChannelOutputBuffer.flushChannel(SocketChannelOutputBuffer.java:426)
        at com.sun.grizzly.http.SocketChannelOutputBuffer.flushBuffer(SocketChannelOutputBuffer.java:498)
        at com.sun.grizzly.http.SocketChannelOutputBuffer.realWriteBytes0(SocketChannelOutputBuffer.java:382)
        at com.sun.grizzly.http.SocketChannelOutputBuffer.realWriteBytes(SocketChannelOutputBuffer.java:364)
        at com.sun.grizzly.tcp.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:894)
        at com.sun.grizzly.tcp.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:167)
        at com.sun.grizzly.tcp.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:661)
        at com.sun.grizzly.tcp.Response.doWrite(Response.java:685)
        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:425)
        ... 57 more
|#]

[#|2016-01-31T22:21:07.955+0530|INFO|glassfish3.1.2|org.apache.cxf.binding.soap.interceptor.Soap12FaultOutInterceptor|_ThreadID=13
7;_ThreadName=http-thread-pool-8080(5);|class org.apache.cxf.binding.soap.interceptor.Soap12FaultOutInterceptor$Soap12FaultOutInte
rceptorInternalapplication/soap+xml|#]

[#|2016-01-31T22:21:07.988+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=135;_ThreadName=http-thread-pool-8080(3);|Inbound Message
----------------------------
ID: 26
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=datatypes-base.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:21:08.120+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=136;_ThreadName=http-thread-pool-8080(4);|Inbound Message
----------------------------
ID: 27
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=SDTC.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:22:37.960+0530|WARNING|glassfish3.1.2|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=137;_ThreadName=http-t
hread-pool-8080(5);|Interceptor for {urn:gov:hhs:fha:nhinc:adaptermpi}AdapterMpiService has thrown exception, unwinding now
org.apache.cxf.binding.soap.SoapFault: Error writing to XMLStreamWriter.
        at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor.handleMessage(SoapOutInterceptor.ja
va:289)
        at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor.handleMessage(SoapOutInterceptor.ja
va:271)
        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
        at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:114)
        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:331)
        at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
        at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
        at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:218)
        at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:198)
        at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
        at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:158)
        at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:243)
        at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:168)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
        at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:219)
        at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
        at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
        at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
        at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
        at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
        at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
        at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
        at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
        at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
        at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
        at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
        at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
        at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
        at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
        at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.ctc.wstx.exc.WstxIOException: java.io.IOException: Client is busy or timed out
        at com.ctc.wstx.sw.BaseStreamWriter._finishDocument(BaseStreamWriter.java:1406)
        at com.ctc.wstx.sw.BaseStreamWriter.writeEndDocument(BaseStreamWriter.java:536)
        at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor.handleMessage(SoapOutInterceptor.ja
va:283)
        ... 38 more
Caused by: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Client is busy or timed out
        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:430)
        at com.sun.grizzly.util.buf.ByteChunk.flushBuffer(ByteChunk.java:458)
        at com.sun.grizzly.util.buf.ByteChunk.append(ByteChunk.java:380)
        at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:455)
        at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:442)
        at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:160)
        at org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:51)
        at org.apache.cxf.io.CacheAndWriteOutputStream.write(CacheAndWriteOutputStream.java:71)
        at org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:51)
        at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:100)
        at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:225)
        at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:198)
        at com.ctc.wstx.sw.BaseStreamWriter._finishDocument(BaseStreamWriter.java:1404)
        ... 40 more
Caused by: java.io.IOException: Client is busy or timed out
        at com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:129)
        at com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:76)
        at com.sun.grizzly.http.SocketChannelOutputBuffer.flushChannel(SocketChannelOutputBuffer.java:426)
        at com.sun.grizzly.http.SocketChannelOutputBuffer.flushBuffer(SocketChannelOutputBuffer.java:498)
        at com.sun.grizzly.http.SocketChannelOutputBuffer.realWriteBytes0(SocketChannelOutputBuffer.java:382)
        at com.sun.grizzly.http.SocketChannelOutputBuffer.realWriteBytes(SocketChannelOutputBuffer.java:364)
        at com.sun.grizzly.tcp.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:894)
        at com.sun.grizzly.tcp.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:165)
        at com.sun.grizzly.tcp.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:661)
        at com.sun.grizzly.tcp.Response.doWrite(Response.java:685)
        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:425)
        ... 52 more
|#]

[#|2016-01-31T22:22:38.142+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=133;_ThreadName=http-thread-pool-8080(1);|Inbound Message
----------------------------
ID: 28
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=../multicacheschemas/POCD_MT000040.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:22:38.222+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=134;_ThreadName=http-thread-pool-8080(2);|Inbound Message
----------------------------
ID: 29
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=../coreschemas/datatypes.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:22:38.330+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=135;_ThreadName=http-thread-pool-8080(3);|Inbound Message
----------------------------
ID: 30
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=../coreschemas/NarrativeBlock.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:22:38.517+0530|INFO|glassfish3.1.2|org.apache.cxf.services.AdapterMpiService.AdapterMpiPort.AdapterMpiPortType|_T
hreadID=136;_ThreadName=http-thread-pool-8080(4);|Inbound Message
----------------------------
ID: 31
Address: http://localhost:8080/Adapter/PatientDiscovery/A_0/AdapterMpiService?xsd=voc.xsd
Http-Method: GET
Content-Type:
Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], connection=[keep-alive], Content-Type=[null], host=[local
host:8080], user-agent=[Java/1.7.0_60]}
--------------------------------------|#]

[#|2016-01-31T22:24:29.528+0530|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=55;_Th
readName=Thread-24;|[31/22:24:29:528] DEBUG  DeferredQueueTimer              Now read properties....


 |#]

[#|2016-01-31T22:24:29.530+0530|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=55;_Th
readName=Thread-24;|[31/22:24:29:530] DEBUG  DeferredQueueTimerTask          DeferredQueueTimerTask is disabled by the DeferredQue
ueRefreshActive property.


 |#]

[#|2016-01-31T22:24:29.531+0530|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=55;_Th
readName=Thread-24;|[31/22:24:29:531] DEBUG  DeferredQueueTimer              Before reading properties wait status....
 
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

christophermay07
Hi,

Your client should be connecting to the Entity endpoint, not the Reference Adapter endpoint, e.g.: http://localhost:8080/Gateway/PatientDiscovery/1_0/EntityPatientDiscovery

Regards,

Chris May
CONNECT Product Team
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

Alamelu Chidambaram
As a follow up with chris's post  want to understand the requirements.

1.  Are you looking for a PatientDiscovery Query ? If you do a PatientDiscovery then there is a PatientCorrelation adapter and the functionality of the adapter is to add patient correlation and the endpoint for this webservice can be replaced with your PatientCorrelation implemented endpoint in internalConnectionInfo files. If you are working on DocumentQuery workflow then PatientCorrelation service will be looked up for Patient Correlations and based on correlations send out Document Query requests to the community in standard mode.

2. But if you are looking for Adapter MPI webservice, the own mpi adapters can be implemented and those endpoints can be placed in internalConnectionInfo files replacing the reference adapter endpoints. The PatientDiscovery request should be targeted to Entity endpoints as mentioned by Chris and in the workflow the Adapter mpi service will be used to do a Patient look up.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

khk1216
Hi,
As suggested I am using the below URL for PD from my client:
 http://localhost:8080/Gateway/PatientDiscovery/1_0/EntityPatientDiscovery

My stub is making the call to this end point, but end up with errors, as first part of it the error is:
14:44:19,483 WARN  [org.apache.cxf.ws.addressing.ContextUtils] (http--127.0.0.1-8080-2) WS-Addressing - failed to retrieve Message Addressing Properties from context
14:44:19,506 INFO  [org.springframework.context.support.FileSystemXmlApplicationContext] (http--127.0.0.1-8080-2) Refreshing org.springframework.context.support.FileSystemXmlApplicationContext@235c2724: startup date [Fri Feb 05 14:44:19 IST 2016]; root of context hierarchy
14:44:19,509 INFO  [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (http--127.0.0.1-8080-2) Loading XML bean definitions from URL [file:/E:/Project/jboss-as-7.1.1.Final/modules/org/connectopensource/configuration/main//TransactionLoggingProxyConfig.xml]
14:44:19,528 INFO  [org.springframework.beans.factory.support.DefaultListableBeanFactory] (http--127.0.0.1-8080-2) Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1efb0530: defining beans [transactionstorenoop,transactionstoredatabase,transactionstoreinmemory]; root of factory hierarchy
14:44:19,533 INFO  [gov.hhs.fha.nhinc.logging.transaction.dao.TransactionDAO] (http--127.0.0.1-8080-2) TransactionDAO initialized
14:44:19,535 INFO  [gov.hhs.fha.nhinc.logging.transaction.dao.TransactionDAO] (http--127.0.0.1-8080-2) -- MessageId Parameter is required for Transaction Query --
14:44:19,541 INFO  [gov.hhs.fha.nhinc.logging.transaction.dao.TransactionDAO] (http--127.0.0.1-8080-2) -- MessageId Parameter is required for Transaction Query --
14:44:19,637 INFO  [gov.hhs.fha.nhinc.event.Log4jEventLogger] (http--127.0.0.1-8080-2) BEGIN_OUTBOUND_MESSAGE has triggered. It has messageID null, transactionID null and description {"responding_hcids":["urn:oid:1.1"],"service_type":"Patient Discovery","action":"1.0"}
14:44:19,650 INFO  [gov.hhs.fha.nhinc.logging.transaction.dao.TransactionDAO] (http--127.0.0.1-8080-2) -- MessageId Parameter is required for Transaction Query --
14:44:19,651 INFO  [gov.hhs.fha.nhinc.logging.transaction.dao.TransactionDAO] (http--127.0.0.1-8080-2) -- MessageId Parameter is required for Transaction Query --
14:44:19,659 INFO  [gov.hhs.fha.nhinc.event.Log4jEventLogger] (http--127.0.0.1-8080-2) BEGIN_OUTBOUND_PROCESSING has triggered. It has messageID null, transactionID null and description {"responding_hcids":["urn:oid:1.1"],"service_type":"Patient Discovery","action":"1.0"}
14:44:19,663 INFO  [gov.hhs.fha.nhinc.transform.audit.PatientDiscoveryTransforms] (http--127.0.0.1-8080-2) ***************************************************************
14:44:19,665 INFO  [gov.hhs.fha.nhinc.transform.audit.PatientDiscoveryTransforms] (http--127.0.0.1-8080-2) Entering transformEntityPRPAIN201305RequestToAuditMsg() method.
14:44:19,666 INFO  [gov.hhs.fha.nhinc.transform.audit.PatientDiscoveryTransforms] (http--127.0.0.1-8080-2) ***************************************************************
14:44:27,142 INFO  [gov.hhs.fha.nhinc.transform.audit.PatientDiscoveryTransforms] (http--127.0.0.1-8080-2) **************************************************************
14:44:27,143 INFO  [gov.hhs.fha.nhinc.transform.audit.PatientDiscoveryTransforms] (http--127.0.0.1-8080-2) Exiting transformEntityPRPAIN201305RequestToAuditMsg() method.
14:44:27,144 INFO  [gov.hhs.fha.nhinc.transform.audit.PatientDiscoveryTransforms] (http--127.0.0.1-8080-2) **************************************************************
14:44:27,238 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (http--127.0.0.1-8080-2) Creating Service {urn:gov:hhs:fha:nhinc:nhinccomponentauditrepository}AuditRepositoryManagerSecuredPortTypeService from class gov.hhs.fha.nhinc.nhinccomponentauditrepository.AuditRepositoryManagerSecuredPortType
14:44:33,813 ERROR [gov.hhs.fha.nhinc.saml.extraction.SamlTokenCreator] (http--127.0.0.1-8080-2) Error: samlSendOperation input assertion Home Community is null
14:44:33,814 ERROR [gov.hhs.fha.nhinc.saml.extraction.SamlTokenCreator] (http--127.0.0.1-8080-2) Error: samlSendOperation input assertion AuthnStatement is null
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

christophermay07
Hi,

    It looks like elements are missing from the SAML assertion in your request.  You can find more information in section 3.2.2 of the NHIN Authorization Framework:  http://sequoiaproject.org/wp-content/uploads/2014/11/nhin-authorization-framework-production-specification-v3.0.pdf

Regards,

Chris May
CONNECT Product Team
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

khk1216
Hi Chris,
Thanks for the inputs, the issue got resolved.


But now im not able to validate the PD response, because if i hit the end point using soap action, it returns valid response, where as if I use EntityPatientDiscoveryProxy method to invoke my end point, then my response is different which looks wrong.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

christophermay07
Hi,

    Do you have an example of the incorrect response, or perhaps an error in the logs that might help troubleshoot the current issue?

Regards,

Chris May
CONNECT Product Team
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

khk1216
Hi there,
For successful response: I did compare the success response with the response which is included in the SOAP Validate suite and I have the attached the auditrepository table with completing the PD cycle logs.

For unsuccessful /failure response:
I could not see error in the log, but found discrepancy in the audit table entries,
auditrepository.txt
server.log
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

khk1216
Hi Chris,
Finally able to connect two gateways and execute the PD, DQ,DR.

But I want to do the PD with "Demographic Query only mode". Could some one provide me the sample request format of this?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Clarity needed on Patient Discovery and Patient Correlation

Sovann Huynh
Administrator
Hi there,

It appears the term "demographic query only mode" implies that a patient identifier is simply missing from the request. If you do not pass one in to CONNECT, CONNECT will not append one. See the following for reference:

https://exchange-specifications.wikispaces.com/share/view/61321662
http://healthcaresecprivacy.blogspot.com/2012/03/nwhin-exchange-use-of-xcpd-for-patient.html
Sovann
CONNECT Product Team Member
Loading...