[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ohf-dev] XDS and ebXML versions: ebXML3.0 or ebXML2.1

Hello J. Andres,

Regarding your OHF questions -
The XDS consumer supports 3 transactions:
- Registry Query (ebXML 2.1, ITI-16)
- Registry Stored Query (ebXML 3.0, ITI-18)
- Retrieve Document (http, ITI-17)

These transactions are implemented as defined by the IHE organization. So the consumer will send ebXML 2.1 messages if you invoke the "query()" methods as defined. The XDS Consumer will send ebXML 3.0 if you invoke the "invokeStoredQuery()" method. XDS Registries, as stated by IHE, are required to handle Stored Queries (ITI-18) and it is optional for them to additionally support the Registry Query (ITI-16). If you are just beginning your implementation and have an ebXML 2.1 registry, the OHF XDS Consumer should work right out of the box using the "query()" method. The OHF XDS Document Source sends ebXML 2.1 messages, so you should be all set.


A HEADS UP as well: This year peer transactions using ebXML 3.0 are coming out in a new supplement in IHE. This supplement is still under development and will be made available for public comment in the coming weeks. After this point in time XDS will have a set of "original" transactions and a new set of "web service" transactions.

Orgininal (using ebXML 2.1):
- Registry Query (ITI-16)
- Provide and Register Document Set (ITI - 15)
- Retrieve Document (ITI-17)
- Register Document Set (ITI-14)

Web service (using ebXML 3.0)
- Registry Stored Query (ITI-18, updated again this cycle)
- Provide and Register Document Set-b (ITI-15.b)
- Retrieve Document Set (ITI-XX - new transaction)
- Register Document Set-b (ITI-14.b)

These transactions will have an effect on OHF and XDS Registry implementors. Requirements for Connectathon and compliance will be affected as well.

For more details on the current status of these new transactions, please see the in-progress document  (.doc) at:
ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr5-2007-2008/Technical_Cmte/Profile_Work/XDSWS

It is my intent to try and implement the XDS Source and XDS Consumer side of these new transactions for the 2008 North American Connectathon, but I will be doing so after the trial implementation text is available from IHE ... which should be sometime in late summer.

Hope this helps,
Sarah Knoop

IBM Almaden Research Center
650 Harry Rd.
San Jose, CA 95120-6099
email: seknoop@xxxxxxxxxx
phone: (408) 927-2622  (tie 457-2622)


jguerrero@xxxxxxxxxxxx
Sent by: ohf-dev-bounces@xxxxxxxxxxx

06/07/2007 01:37 AM

Please respond to
Open Healthcare Framework Mailing list <ohf-dev@xxxxxxxxxxx>
To
ohf-dev@xxxxxxxxxxx
cc
ccercos@xxxxxxxxxxxx, jvillagrasa@xxxxxxxxxxxx, isabelle_mauny@xxxxxxxxxx
Subject
[ohf-dev] XDS and ebXML versions: ebXML3.0 or ebXML2.1






Hi all,

I have questions regarding versions of ebXML used by consumer and source
XDS actor.  I read this in ohf-dev list:

*********
* From: Sarah E Knoop <seknoop@xxxxxxxxxx>
* Date: Thu, 18 May 2006 09:28:12 -0700
* Delivered-to: ohf-dev@xxxxxxxxxxx

This is probably what IHE should have done in the first place, because it
allows vendors who implement a Registry to be more flexible in their SQL
implementation.
ebXML 3.0 was not rattified in time for IHE to commit to this last year.
ebXML 2.1 does not have this capability.
The old way of doing queries is implemented and in the process of being
tested.
Timing is really the issue here, along with the fact that now the consumer
uses ebXML3.0 but the XDS Source uses ebXML 2.1.
Not sure what IHE plans to do about this.
Don't think it is a good idea to leave it as such. If IHE makes this move,
I'm inclined to push that everything go to ebXML3.0.
This would potentially have implications on XDS Source and XDS Metadata.
We'll see at the meeting next week.
This functionality is possible to add onto our Consumer, it just won't be
present at the first drop. I'm inclined to wait until the final text has
gone through public comment before adding this functionality



**********

Any news about that?

I know that, by now, the XDS Consumer plugin source code uses ebXML3 and
XDS Source plugin uses ebXML2.1.
So if we are working with an ebXML2.1 registry implementation (like
ebXMLrr) with XDS Registry Initialization metadata, Is posible to make this
registry work together with the OHF client?

Another questions are:

* Is there available any XDS Registry Initialization metadata for ebXML3
registry?
* Is posible to get a ebXML 2.1 version of the OHF XDS Consumer or is not
necessary?


Thanks in advance


..................................................................

J. Andrés Guerrero

COSTAISA SA
Pau Alcover, 33
Dpto. de Estudios
Extensión 743

_______________________________________________
ohf-dev mailing list
ohf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ohf-dev