1) My understanding thus far is that to participate in the NA Connectathon in 2014, we should register for both the ITI-41 SEDI Document Source Actor and SEDI Document Recipient Actor tests, as users of our software could be both SEDI Sources and SEDI Recipients – is this correct?
Comment from Andrew: Yes, our intention was to share information and interchange metadata. Our SEDI use case is between dental provider’s systems. We expect the ability to both receive and send this information.
2) Are we required to develop our own web service for transmission/receipt of SEDI Documents, or is there some kind of public/standard web service that is utilized for the Connectathon? I have loaded the XDSToolkit 2.159 referenced in your presentation (pdf from Chicago 2013) in house, but am at a loss as to how to configure the thing to work correctly for XDR tests.
Comment from Andrew: In my presentation I made an important point to use the IHE community and specifically the Google groups. There is currently over 1,346 threads in the IHE XDS Implementers group, so every problem you have or will face, there’s a great chance that it has been addressed and solved already by your peers. The community part of the Connectathon is one of the best experiences in participating! I recommend that you review the threads and you’ll find some great insight.
In particular, once you have the XDStoolkit installed, first you’ll want to configure the environment. The XDStoolkit2 is now up to version 161, the version that was successfully used in the IHE Europe Connectathon. It should be the EURO2013 for version 161. Other versions such as 159, would have the NA2013 environment. Once you have the simulator environment installed, then you’ll want to configure the actors, first privately within your own test environment then publically to the ihexdsnist.gov gateway.
3) Will there be an update to the XDS Toolkit soon that will include specific test examples for SEDI? We’d really like to have a solid start on this by the end of June, so we can determine whether or not we are prepared to register for the 2014 NA Connectathon.
Comment from Andrew: You should really have a solid start by using the existing XDStoolkit2. It will be your best guide this spring.
Toni Magni
tops Software
2621 Sandy Plains Road, Suite 101
Marietta, GA 30066-4276
cell: +39(331)924-8580
office: (770) 627-2527
ama...@topsOrtho.com
topsOrtho | topsCephMate | topsEcho
www.topsOrtho.com
I received an email from a vendor with some Connectathon prep questions, and I thought it would be appropriate if I included the thread with my comments out to the group.Hope this helps, Andrew1) My understanding thus far is that to participate in the NA Connectathon in 2014, we should register for both the ITI-41 SEDI Document Source Actor and SEDI Document Recipient Actor tests, as users of our software could be both SEDI Sources and SEDI Recipients – is this correct?
Comment from Andrew: Yes, our intention was to share information and interchange metadata. Our SEDI use case is between dental provider’s systems. We expect the ability to both receive and send this information.
2) Are we required to develop our own web service for transmission/receipt of SEDI Documents, or is there some kind of public/standard web service that is utilized for the Connectathon? I have loaded the XDSToolkit 2.159 referenced in your presentation (pdf from Chicago 2013) in house, but am at a loss as to how to configure the thing to work correctly for XDR tests.
Comment from Andrew: In my presentation I made an important point to use the IHE community and specifically the Google groups. There is currently over 1,346 threads in the IHE XDS Implementers group, so every problem you have or will face, there’s a great chance that it has been addressed and solved already by your peers. The community part of the Connectathon is one of the best experiences in participating! I recommend that you review the threads and you’ll find some great insight.
In particular, once you have the XDStoolkit installed, first you’ll want to configure the environment. The XDStoolkit2 is now up to version 161, the version that was successfully used in the IHE Europe Connectathon. It should be the EURO2013 for version 161. Other versions such as 159, would have the NA2013 environment. Once you have the simulator environment installed, then you’ll want to configure the actors, first privately within your own test environment then publically to the ihexdsnist.gov gateway.
3) Will there be an update to the XDS Toolkit soon that will include specific test examples for SEDI? We’d really like to have a solid start on this by the end of June, so we can determine whether or not we are prepared to register for the 2014 NA Connectathon.
Comment from Andrew: You should really have a solid start by using the existing XDStoolkit2. It will be your best guide this spring.
Hi Toni,
Thanks for your feedback. Yes, you are required to develop your own web service for transmission/receipt of SEDI Documents. To find more information on what SEDI is based on, please see the following standards and guidelines:
Ø ebRIM - OASIS/ebXML Registry Information Model v3.0
Ø ebRS- OASIS/ebXML Registry Services Specifications v3.0
Ø ITI TF-2x: Appendix V Web Services for IHE Transactions. Contains references to all Web Services standards and requirements of use
Ø MTOM - SOAP Message Transmission Optimization Mechanism http://www.w3.org/TR/soap12-mtom/
Ø XOP - XML-binary Optimized Packaging http://www.w3.org/TR/2005/REC-xop10-20050125/
In particular, Appendix V Web Services for IHE Transactions includes IHE web services requirement to help provide consistency and clarity on addressing and namespaces.
Thanks Andrew: Same place but a little earlier date than this year then… Not a problem to be there on that date… Just let me know how I can help? Will information go out to - and through - the Dental Trades Alliance? Best wishes, Allan