Hi there!
Yep, you were right - infoman had auto upgraded, and the existing data had been wiped out. I was unfortunately ignoring this transaction log because it wasn’t showing as failed on the IOL.
On the other hand, once I get this to work, the patient query on openempi seems to fail.
The PIX message looks like this:
MSH>^~&|openhim|openhim-mediator-ohie-xds|pix|pix|20151011194313-0400||QBP^Q23^QBP_Q21|c062c2ec-597f-401f-bd3e-bd456305c8e5|P|2.5
QPD>IHE PIX Query|b45d875d-e0c6-49c5-bd81-6ed1de6f4d08|5555^^^&2.16.840.1.113883.3.72.5.9.1&ISO^PI|^^^CR_CID&0.0.0.0.0&ISO^PI
RCP>I
But the response i’m getting is:
MSH>^~&|CR-TEST|Fake Jurisdiction|openhim|openhim-mediator-ohie-xds|201510112343||RSP^K23^RSP_K23|6d60d5fe-fbfa-4068-aeb6-1ec301c0214c|P|2.5
MSA>AE>c062c2ec-597f-401f-bd3e-bd456305c8e5
ERR>>QPD^1^3^1^1|204^HL7204|E||||DTPE006 : Could not locate specified patient identifier
QAK>b45d875d-e0c6-49c5-bd81-6ed1de6f4d08|AE
QPD>IHE PIX Query|b45d875d-e0c6-49c5-bd81-6ed1de6f4d08|5555^^^&2.16.840.1.113883.3.72.5.9.1&ISO|^^^CR_CID&0.0.0.0.0&ISO
According to OpenEMPI (direct search), I do have a patient with Id 5555 and identifier domain 2.16.840.1.113883.3.72.5.9.1
The XDS message that i’m posting is : http://pastebin.com/cSKVg2n1
I’m wondering if i’m doing anything stupid again? 
···
On Thu, Oct 8, 2015 at 2:28 AM, Hannes Venter hannes@jembi.org wrote:
Hey Suranga
Apologies, I’m afraid the details of that issue slipped my memory, but looking at the logs you sent through, it seems there’s an issue reading the response from the CSD server:
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
at org.openhim.mediator.denormalization.CSDRequestActor.processHTTPResponse(CSDRequestActor.java:167)
at org.openhim.mediator.denormalization.CSDRequestActor.onReceive(CSDRequestActor.java:200)
So the mediator’s receiving an unparseable message. I’m not sure what it could be - perhaps there is an issue with the instance and it’s returning an empty response for some reason?
Kind Regards
Hannes
Thanks and best regards,
Suranga Kasthurirathne
Regional Community manager (Asia-Pacific)
On 7 October 2015 at 20:26, Suranga Kasthurirathne surangak@openmrs.org wrote:
Hi Ryan,
To send these messages, i’m using the code that we wrote in https://github.com/surangak/ohie-integration-tests (look at XdsMessageUtil.java).
This code was based/copied from Justin’s own testing module - we used it for the OHIE integration, and it worked just fine.
I also tried decoding the message content that we’re sending in base 64 encoded format… and it looks just fine
I distinctly remember that this was something that we encountered before, and fixed in one of the components. I wonder if Hannes can remember exactly what we did, and would care to weigh in 
–
You received this message because you are subscribed to the Google Groups “Shared Health Record (OpenHIE)” group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-shr+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Hannes Venter
Senior Software Developer
Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org
This e-mail contains proprietary and confidential information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then deleting same. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail. Jembi Health Systems NPO, its subsidiaries and associated companies is not liable for the security of information sent by e-mail and accepts no liability of whatsoever nature for any loss, damage or expense resulting, directly or indirectly, from the access of this e-mail or any attachments hereto.
Thanks and best regards,
Suranga Kasthurirathne
Regional Community manager (Asia-Pacific)
On Fri, Oct 2, 2015 at 3:38 AM, Ryan Crichton ryan@jembi.org wrote:
Hey Suranga,
I can’t see anything really wrong with those messages. It seems whatever xml that the mediator is receiving it cannot parse it. How are you sending these messages in?
Cheers,
Ryan
On Thu, Oct 1, 2015 at 7:51 PM Suranga Kasthurirathne surangak@openmrs.org wrote:
Hi all,
I’m playing around with iol.test.ohie.org, which is the OpenHIE instance that we used for integration testing, and discovered a problem.
You may remember that during integration testing, we had a problem where saving clinical documents failed with a ‘’ Premature end of file." error. This was because the base-64 decoding added non-xml content to the document, and so, xds-b repo failed.
Now, I do remember that we (more specifically Hannes I think…) fixed this on the mediator, and got things working.
However, it seems that the error is back.
As per Ryan Y, we haven’t changed anything, and we’re still using mediator-xds-1.0.2 on this instance.
The transaction in question is: http://iol.test.ohie.org/#/transactions/560d50437791b81e3d4c0e5b
In case you cant access it, the message body reads: http://pastebin.com/rdLbpewb
Log from the OpenXDS mediator: http://pastebin.com/pM2Gsnzy
Any idea why this has returned to haunt us?
Thanks and best regards,
Suranga Kasthurirathne
Regional Community manager (Asia-Pacific)
–
You received this message because you are subscribed to the Google Groups “Shared Health Record (OpenHIE)” group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-shr+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Ryan Crichton
Lead Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org
