I hope you don’t mind, but I’m cross-posting this to the OpenHIE Implementer’s Network (OHIN) mailing list, too. The issues you’re raising are ones that others have been finding, too. It is not easy, at present, to know “what to do” in order to communicate with the OpenHIE technology solutions.
As a community, we have identified that “implementer’s guides” are needed, with code examples etc., in order to help the dev teams on point-of-service applications (like EMRs) to connect and do message exchanges. The new OHIN community is tasked with helping develop such guides and with other work efforts that will help the whole of our HIE “ecosystem”.
I can also say, Wyclif, that I advocated strongly for the use of mature, existing standards in OpenHIE. One of my reasons for this was so OpenHIE could just “hyperlink” to the underlying standards’ documentation from our wiki site. It is clear to me that this approach comes at an expense. Most developers expect to find all the instructions they need on our OpenHIE wiki pages. It is quite an unpleasant surprise when they find out that they must follow the links and that some of the comprehensive health informatics specs (like for XDS.b for example) are quite lengthy and involved. Clearly, step-by-step implementation guides are needed.
I look forward to following your spike and to helping it in any ways I can. As a start, I’m also cc’ing my colleague from the mHealth and eHealth Development and Innovation Centre (MEDIC), Justin Fyfe. Justin has been a longtime OpenHIE contributor and did a lot of dev work on the OpenSHR software product (which is OpenMRS-based). @Justin – can you point Wyclif to the modules you developed for CDA-based message generation and consumption from OpenMRS?
Thanks and warmest regards,
Derek.
Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.
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: openhie-interop...@googlegroups.com [mailto:openhie-interop...@googlegroups.com] On Behalf Of wyc...@openmrs.org
Sent: Friday, October 7, 2016 12:19 PM
To: Interoperability Layer (OpenHIE)
Cc: wyc...@openmrs.org
Subject: Re: Help needed to communcate with a HIE
Thanks Derek!
The message doesn't have to be a FHIR message, we can probably switch to sending out a CDA document if FHIR isn't supported
Turning on/ff TLS has nothing to do with CDC, as I said this is a spike, meaning I'm trying out things on my machine in a VM to present a demo to the CDC folks, so I'll get rid of the VM after that.
As for the third, I'm fairly new to XDS so I can't really clearly comprehend what you just said, I'll do some reading on that. I thought all I had to do was to make a straight forward old style soap based call to OpenHIM to submit a message. I had also assumed XDS is used by the SHR. I guess I was hoping to get the OpenHIM URL that I'd post to a message and how to get the SWDL.
Wyclif
On Friday, October 7, 2016 at 11:11:25 AM UTC-4, Derek Ritz (ecGroup) wrote:
Hi Wyclif.
May I ask a couple of questions, please?
1. is it a requirement from CDC that the outbound message be a FHIR message?
2. is it OK with CDC that the TLS be turned off?
I'm asking the first question because, if it is a requirement that the message be a FHIR message then I'm hoping there is scope in the spike to adopt a FHIR->CDA component and incorporate this into the OpenHIE interoperability layer. There are a number of products (including open source) that do this. At present, however, only inbound CDA documents can be checked, verified, resolved, and routed to the SHR. The SHR itself is a CDA document store (XDS registry and repository) plus an OpenMRS-based database of discrete data. There is not a FHIR-compatible message handler (in the IL) and there is not, today, a FHIR-compatible SHR (above the IL, in the OpenHIE registry/repository stack).
I'm asking question #2 because failure on the PKI side is, in my experience, one of the most common failure modes for new software that has turned off security during dev. My wholehearted recommendation would be to keep this turned on. It is a design requirement to be able to operate, when the time comes, in the secured environment. Unless CDC expects to operate in an unsecured envrinment -- which is unlikely -- this is likely something worthwhile to keep. :-)
Re: your question #3, the OpenHIE documentation links through to IHE documentation regarding the standards for communicating XDS.b payloads. There is quite a lot of information at the IHE wiki which is helpful in this regard (e.g. http://wiki.ihe.net/index.php/XDS.b_Implementation). There are also lots of mature open source toolkits for doing XDS.b message management (as you can probably already tell, the XDS spec has been around for ages) -- so there is no need to code from scratch.
Warmest regards,
Derek.
PS: the discussions re: support for FHIR in OpenHIE are active and ongoing. Please see the most recent notes, here: https://wiki.ohie.org/display/resources/2016-10-04+SHR+Community+Calls. We would love your inputs, Wyclif, into this important step for the IL and SHR communities. :-D
On Fri, Oct 7, 2016 at 10:16 PM, <wyc...@openmrs.org> wrote:
Hi,
I have a module that I worked on not so long ago with Regenstrief and CDC on case based reporting, the CDC wants us to do a spike on how to integrate the module into the HIE, the idea is that the module gets installed in an OpenMRS instance and will send a case report to the HIE for a given patient in form of a FHIR message when they match a certain criteria, saving it as a document in the SHR should be enough for demonstration purposes. I managed to set up OpenHIM and the console and I'm trying to figure out where to go next, below are some of the questions I have:
1- Can I turn off TLS authentication since this is a demo installation on a dev machine?
2- I understand that the HIE works with CDA documents and not FHIR, do you intend to support FHIR anytime soon? If not, is there a way I can plugin in something that can parse another message format? I also see that there is the concept of a data handler in the SHR, can I add my own FHIR handler to process a FHIR message when it gets to the SHR? Assuming it can go through the transport layer even if the transport layer can't parse it.
3- Where is the documentation on how to make requests to OpenHIM? I read somewhere that communication is SOAP based, if this is true, what is the URL to fetch WSDL?
Thanks in advance
Wyclif
--
You received this message because you are subscribed to the Google Groups "Interoperability Layer (OpenHIE)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-interoperabil...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.
+1 (905) 515-0045
www.ecgroupinc.com
--
You received this message because you are subscribed to the Google Groups "Interoperability Layer (OpenHIE)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-interoperabil...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Oct 7, 2016, at 1:49 PM, wyc...@openmrs.org wrote:Thanks Derek! That was helpful, I was starting to beat up myself for failing to figure out things :), let me keep playing around with things and will get back to you guys in case I run into any issues.
Wyclif
On Friday, October 7, 2016 at 10:16:33 AM UTC-4, wyc...@openmrs.org wrote:Hi,
I have a module that I worked on not so long ago with Regenstrief and CDC on case based reporting, the CDC wants us to do a spike on how to integrate the module into the HIE, the idea is that the module gets installed in an OpenMRS instance and will send a case report to the HIE for a given patient in form of a FHIR message when they match a certain criteria, saving it as a document in the SHR should be enough for demonstration purposes. I managed to set up OpenHIM and the console and I'm trying to figure out where to go next, below are some of the questions I have:
1- Can I turn off TLS authentication since this is a demo installation on a dev machine?
2- I understand that the HIE works with CDA documents and not FHIR, do you intend to support FHIR anytime soon? If not, is there a way I can plugin in something that can parse another message format? I also see that there is the concept of a data handler in the SHR, can I add my own FHIR handler to process a FHIR message when it gets to the SHR? Assuming it can go through the transport layer even if the transport layer can't parse it.
3- Where is the documentation on how to make requests to OpenHIM? I read somewhere that communication is SOAP based, if this is true, what is the URL to fetch WSDL?
Thanks in advance
Wyclif
--
You received this message because you are subscribed to the Google Groups "Interoperability Layer (OpenHIE)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-interoperabil...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I think this would be really helpful Jennifer.
Please do share J
Niamh
--
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
ohie-implement...@googlegroups.com.
To post to this group, send email to
ohie-imp...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ohie-implementers/BA4CEBB6-948C-4F0A-83BB-792398DC7D5E%40gmail.com.
Thanks Jennifer! It turns out Openhim spawns several worker processes each listening on a separate port, it isn't documented what requests should be forwarded to each port, I had to look at the test to realize that I had to direct my calls to port 5001 and not the same port number used by the console app that I had configured OpenHIM to listen on, I think it would be nice to document these details.
The MongoDB documentation doesn't seem to mention that one needs to tell the server which folder to use for storage when starting it, so it kept on failing to start because I wasn't specifying one, It would be nice to add this a side note to the step about installing MongoDB may be it could help others in the future. Otherwise the installation documentation seems pretty good, so good job guys! Keep it up.
Hi,
I have a module that I worked on not so long ago with Regenstrief and CDC on case based reporting, the CDC wants us to do a spike on how to integrate the module into the HIE, the idea is that the module gets installed in an OpenMRS instance and will send a case report to the HIE for a given patient in form of a FHIR message when they match a certain criteria, saving it as a document in the SHR should be enough for demonstration purposes. I managed to set up OpenHIM and the console and I'm trying to figure out where to go next, below are some of the questions I have:
1- Can I turn off TLS authentication since this is a demo installation on a dev machine?
2- I understand that the HIE works with CDA documents and not FHIR, do you intend to support FHIR anytime soon? If not, is there a way I can plugin in something that can parse another message format? I also see that there is the concept of a data handler in the SHR, can I add my own FHIR handler to process a FHIR message when it gets to the SHR? Assuming it can go through the transport layer even if the transport layer can't parse it.
3- Where is the documentation on how to make requests to OpenHIM? I read somewhere that communication is SOAP based, if this is true, what is the URL to fetch WSDL?
Thanks in advance
Wyclif
--
You received this message because you are subscribed to the Google Groups "Interoperability Layer (OpenHIE)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-interoperabil...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Ryan
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-interoperability-layer+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Ryan CrichtonLead Developer, Jembi Health Systems | SOUTH AFRICAMobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ry...@jembi.org
--
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 ohie-implementers+unsubscribe@googlegroups.com.
To post to this group, send email to ohie-implementers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-implementers/CABh-%2BTLzAoEuOaAFiZ9P_5Le0e32TzPeqBV1jdernb445FuFEA%40mail.gmail.com.
Hi Carl,Naively, I would be looking for:- software to download and install- configuration instructions for this software (and the others it is supposed to connect with)- a webpage I can visit that tells me if things are working or which ones are broken.Example:We just conducted a connectathon for a PACS in our hospital and I would be looking for a similar experience for OpenHIEAfter setting up the server on the LAN, the vendor entered the AE title, IP and Port of each node (CT, MRI, ultrasound) and they found each other and started exchanging images...we were up in an hour (most of the time consumed was going around and configuring the machines with the AE title, IP, port)....Is this use case too simple?alvin
Ryan
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-interoperability-layer+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
----Ryan CrichtonLead Developer, Jembi Health Systems | SOUTH AFRICAMobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ry...@jembi.org
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 ohie-implementers+unsubscribe@googlegroups.com.
To post to this group, send email to ohie-implementers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-implementers/CABh-%2BTLzAoEuOaAFiZ9P_5Le0e32TzPeqBV1jdernb445FuFEA%40mail.gmail.com.
--
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 ohie-implementers+unsubscribe@googlegroups.com.
To post to this group, send email to ohie-implementers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-implementers/CAFNRjWjgphQBfE26bbvpU6Q1E%2BTk2uzbvcfM9Wdbor6ngraq5g%40mail.gmail.com.
--Alvin B. Marcelo www.alvinmarcelo.com
WyclifThanks!The IOL is kind of what I expected it to be, it would be nice to have the getting started tutorial Ryan mentioned on the main documentation page. And as I mentioned in one of my earlier posts, OpenHIM spawns several child processes listening on different ports, it's not documented what requests each handles.OpenHIE is actually what I expected it to be, i.e a deployed stack that allows you to consume services.Hi,Thank you all for your responses! @Ryan the getting started page you recommended is really helpful for somebody trying to set up OHIE for the first time.
To respond to Carl's questions:
--Wyclif Luyima
Regenstrief Institute Inc.
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.
--
You received this message because you are subscribed to the Google Groups "Interoperability Layer (OpenHIE)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-interoperability-layer+unsubscribe@googlegroups.com.
Jamie Thomas | Health Information Project Manager/Communications
Center for Biomedical Informatics
1101 West Tenth Street
Indianapolis, IN 46202
Tel 317-274-9218 | Fax 317-274-9305
Email: jt...@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @RegenstriefGHI
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.
This call is October 18th at 10am, correct?
Jamie Thomas | Health Information Project Manager/Communications
Center for Biomedical Informatics
1101 West Tenth Street
Indianapolis, IN 46202
Tel 317-274-9218 | Fax 317-274-9305
Email: jt...@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @RegenstriefGHI
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.