Noty – I’m going to cc this thread to the OpenHIE Implementer’s Network.
The challenges that you’re having came up on this morning’s OpenHIE Dev Ops call and the recommendation was to leverage the technical support listserv that is dedicated to implementers. I’m sorry if this is duplicative (I am not sure if you’re already leveraging the OpenHIE community in this way)… but in the interests of giving this support channel an opportunity to work as it is intended to work, let’s move this to the community support network and see how we fare.
OpenHIE Implementer’s Network (OHIN)… we look forward to assistance re: this thread. At summary – we have a tech team in Cambodia who is looking to connect to OpenEMPI through the OpenHIM. Presently, there are configuration challenges (and these may be related to the versions, or to the configuration of the tech stacks, etc.).
Warmest regards,
Derek.
Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.
+1 (905) 515-0045
This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality.
···
From: noty chea [mailto:noty.setec@gmail.com] Sent: Monday, December 5, 2016 2:15 AM To: Hannes Venter Cc: Derek Ritz (ecGroup); Ryan Crichton; hroith.pbh@gmail.com Subject: Re: Feather advice (Implementation openHIM with openEMPI)
Already try.
On Fri, Dec 2, 2016 at 8:45 PM Hannes Venter hannes@jembi.org wrote:
Hi Sovannoty,
I’m also just including my colleague Ryan who might be more responsive than me (I’m out of country at the moment). Ryan is the lead developer of the OpenHIM and a health information exchange expert.
@Ryan Sovannoty is a developer who is trying to setup the HIM with OpenEMPI.
So I remember OpenEMPI was sometimes inconsistent with the mime types, and sometimes uses text/xml, and sometimes application/xml for certain endpoints.
Maybe try sending it with a header of text/xml instead?
Thanks you very much for advice
If I don’t misunderstand what you suggested
not to use old openhim-openempi-patient-adapter.
pass-through channel.
HL7.
Since my question from the beginning is
How can I create post or get with body in curl or any form for request with body to openhim?
since openhim need that body to pass to openempi even though I used passthrough channel.
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.
I believe you may be running into a malformed request error from OpenEMPI. The OpenHIM shouldn’t care what form the request was in. Are you trying to communicate with OpenEMPI using their rest API or via HL7 v2 or via HL7 v3. I think that would be the first step that we need to determine to try help you further.
Then would you be able to provide us with more details about the request that you are making and the error message that you get back, then perhaps we can figure out how to best help you. Also, it would be useful to know your overall usecase to help guide you to the best solution. If you could provide those details then we can take it from there.
Noty – I’m going to cc this thread to the OpenHIE Implementer’s Network.
The challenges that you’re having came up on this morning’s OpenHIE Dev Ops call and the recommendation was to leverage the technical support listserv that is dedicated to implementers. I’m sorry if this is duplicative (I am not sure if you’re already leveraging the OpenHIE community in this way)… but in the interests of giving this support channel an opportunity to work as it is intended to work, let’s move this to the community support network and see how we fare.
OpenHIE Implementer’s Network (OHIN)… we look forward to assistance re: this thread. At summary – we have a tech team in Cambodia who is looking to connect to OpenEMPI through the OpenHIM. Presently, there are configuration challenges (and these may be related to the versions, or to the configuration of the tech stacks, etc.).
Warmest regards,
Derek.
Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.
+1 (905) 515-0045
This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality.
From: noty chea [mailto:noty.setec@gmail.com] Sent: Monday, December 5, 2016 2:15 AM To: Hannes Venter Cc: Derek Ritz (ecGroup); Ryan Crichton; hroith.pbh@gmail.com Subject: Re: Feather advice (Implementation openHIM with openEMPI)
Already try.
On Fri, Dec 2, 2016 at 8:45 PM Hannes Venter hannes@jembi.org wrote:
Hi Sovannoty,
I’m also just including my colleague Ryan who might be more responsive than me (I’m out of country at the moment). Ryan is the lead developer of the OpenHIM and a health information exchange expert.
@Ryan Sovannoty is a developer who is trying to setup the HIM with OpenEMPI.
So I remember OpenEMPI was sometimes inconsistent with the mime types, and sometimes uses text/xml, and sometimes application/xml for certain endpoints.
Maybe try sending it with a header of text/xml instead?
Thanks you very much for advice
If I don’t misunderstand what you suggested
not to use old openhim-openempi-patient-adapter.
pass-through channel.
HL7.
Since my question from the beginning is
How can I create post or get with body in curl or any form for request with body to openhim?
since openhim need that body to pass to openempi even though I used passthrough channel.
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.
–
You received this message because you are subscribed to the Google Groups “OpenHIE Implementers Network (OHIN)” group.
I am also requesting to add (Ms) Perl Gasmen to this list – she is working with Mohawk on the MPI Myanmar project…
She will benefit from the experts in this thread –
Hi Noty! Hope to meet you when AeHIN goes to Phnom Penh…
alvin
···
On Tue, Dec 6, 2016 at 12:28 PM, Ryan Crichton ryan@jembi.org wrote:
Hi Sovannoty,
I believe you may be running into a malformed request error from OpenEMPI. The OpenHIM shouldn’t care what form the request was in. Are you trying to communicate with OpenEMPI using their rest API or via HL7 v2 or via HL7 v3. I think that would be the first step that we need to determine to try help you further.
Then would you be able to provide us with more details about the request that you are making and the error message that you get back, then perhaps we can figure out how to best help you. Also, it would be useful to know your overall usecase to help guide you to the best solution. If you could provide those details then we can take it from there.
Noty – I’m going to cc this thread to the OpenHIE Implementer’s Network.
The challenges that you’re having came up on this morning’s OpenHIE Dev Ops call and the recommendation was to leverage the technical support listserv that is dedicated to implementers. I’m sorry if this is duplicative (I am not sure if you’re already leveraging the OpenHIE community in this way)… but in the interests of giving this support channel an opportunity to work as it is intended to work, let’s move this to the community support network and see how we fare.
OpenHIE Implementer’s Network (OHIN)… we look forward to assistance re: this thread. At summary – we have a tech team in Cambodia who is looking to connect to OpenEMPI through the OpenHIM. Presently, there are configuration challenges (and these may be related to the versions, or to the configuration of the tech stacks, etc.).
Warmest regards,
Derek.
Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.
+1 (905) 515-0045
This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality.
From: noty chea [mailto:noty.setec@gmail.com] Sent: Monday, December 5, 2016 2:15 AM To: Hannes Venter Cc: Derek Ritz (ecGroup); Ryan Crichton; hroith.pbh@gmail.com Subject: Re: Feather advice (Implementation openHIM with openEMPI)
Already try.
On Fri, Dec 2, 2016 at 8:45 PM Hannes Venter hannes@jembi.org wrote:
Hi Sovannoty,
I’m also just including my colleague Ryan who might be more responsive than me (I’m out of country at the moment). Ryan is the lead developer of the OpenHIM and a health information exchange expert.
@Ryan Sovannoty is a developer who is trying to setup the HIM with OpenEMPI.
So I remember OpenEMPI was sometimes inconsistent with the mime types, and sometimes uses text/xml, and sometimes application/xml for certain endpoints.
Maybe try sending it with a header of text/xml instead?
Thanks you very much for advice
If I don’t misunderstand what you suggested
not to use old openhim-openempi-patient-adapter.
pass-through channel.
HL7.
Since my question from the beginning is
How can I create post or get with body in curl or any form for request with body to openhim?
since openhim need that body to pass to openempi even though I used passthrough channel.
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.
–
You received this message because you are subscribed to the Google Groups “OpenHIE Implementers Network (OHIN)” group.
If you or anyone on your team would like to join the OpenHIE Implementers Network (OHIN) mailing list please subscribe here: ohie-implementers+subscribe@googlegroups.com .
This forum is for countries and implementers to bring their questions, problems and ideas so we can work on solutions together.
**Jamie Thomas **|****Health Information Project Manager/Communications
Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged
information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and
State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical
or other information is not sufficient for this purpose.
If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention,
disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited.
···
On Tue, Dec 6, 2016 at 12:28 PM, Ryan Crichton ryan@jembi.org wrote:
Hi Sovannoty,
I believe you may be running into a malformed request error from OpenEMPI. The OpenHIM shouldn’t care what form the request was in. Are you trying to communicate with OpenEMPI using their rest API or via HL7 v2 or via HL7 v3. I think
that would be the first step that we need to determine to try help you further.
Then would you be able to provide us with more details about the request that you are making and the error message that you get back, then perhaps we can figure out how to best help you. Also, it would be useful to know your overall
usecase to help guide you to the best solution. If you could provide those details then we can take it from there.
Noty – I’m going to cc this thread to the OpenHIE Implementer’s Network.
The challenges that you’re having came up on this morning’s OpenHIE Dev Ops
call and the recommendation was to leverage the technical support listserv that is dedicated to implementers. I’m sorry if this is duplicative (I am not sure if you’re already leveraging the OpenHIE community in this way)… but in the interests of giving this
support channel an opportunity to work as it is intended to work, let’s move this to the community support network and see how we fare.
** OpenHIE Implementer’s Network (OHIN)…
we look forward to assistance re: this thread.** At summary – we have a tech team in Cambodia who is looking to connect
to OpenEMPI through the OpenHIM. Presently, there are configuration challenges (and these may be related to the versions, or to the configuration of the tech stacks, etc.).
Warmest regards,
Derek.
**Derek Ritz,**P.Eng., CPHIMS-CA
ecGroup Inc.
+1
(905) 515-0045
This communication is intended only for the party to whom it is addressed, and
may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality.
From:
noty chea [mailto:noty.setec@gmail.com] Sent: Monday, December 5, 2016 2:15 AM To: Hannes Venter Cc: Derek Ritz (ecGroup); Ryan Crichton; hroith.pbh@gmail.com Subject: Re: Feather advice (Implementation openHIM with openEMPI)
Already try.
On Fri, Dec 2, 2016 at 8:45 PM Hannes Venter hannes@jembi.org wrote:
Hi Sovannoty,
I’m also just including my colleague Ryan who might be more responsive than me (I’m out of country at the moment). Ryan is the lead developer of the OpenHIM and a health information exchange expert.
@Ryan Sovannoty is a developer who is trying to setup the HIM with OpenEMPI.
So I remember OpenEMPI was sometimes inconsistent with the mime types, and sometimes uses text/xml, and sometimes application/xml for certain endpoints.
Maybe try sending it with a header of text/xml instead?
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.*
–
You received this message because you are subscribed to the Google Groups “OpenHIE Implementers Network (OHIN)” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
![F447BFA7-64CF-416E-9382-5383D9F359EA[15].png](https://discourse.ohie.org/uploads/default/original/1X/921ca8b7deaf8e796929e5a31a55a752f0687197.png){kind=small}