ebBP 10/5/2005: Collaborative Business Process Support Using ebBP

[Monica J Martin <Monica.Martin@Sun.COM>]

As indicated at this week's call, here is the positive response we 
received from Dr. Asuman Dogac on the use of ebBP for health care 
automation. I had queried Dr. Dogac after her publication of a paper 
showing the use of registry and collaborative business processes for 
healthcare [1]. At that time (late August), I encouraged Dr. Dogac and 
the extended project teams to consider the v2.0.1 CD packages under 
Public Review. This update is a positive one and directly in line with 
our goal to serve our user communities. We'll continue to work on this 
association. Thanks.


[1] 
http://www.oasis-open.org/apps/org/workgroup/ihc/download.php/14104/DogacBicerOkcan-IHE-XDS-BussProcess.pdf 

public reference: 
http://lists.oasis-open.org/archives/ihc/200508/msg00001.html

> 3 October 2005 - Dr. Dogac: Dear Monica,
> My comments about ebBP specification draft are as follows:
>
> 1. I think the new Business Transaction (BT) patterns
> is a valuable improvement over the previous
> monolithic business process definition.
>
> These BT patterns are generic. It is possible to
> define "domain specific" standard patterns by specializing these
> abstract patterns which can then be stored in the ebXML registry
> together with their semantics. For example, one may want to use
> RosettaNet PIPs such as "PIP3A4: Manage Purchase Order". Such a PIP 
> can be
> defined by inheriting from the BT patterns and by specializing them
> to PIP3A4 and registering this particular PIP and its related
> semantics to the ebXML registry so that they can be discovered
> and re-used.
>
> 2. I think a lot of synergy  can be created between the new ebBP standard
> and the eHealth domain. In my opinion, eHealth domain
> is in need of standards to specify semantically enriched
> and flexible healthcare specific business processes. For example,
> IHE Scheduled workflow is monolithic; any change in it
> would reduce its interoperability which should not be the case.
>
> We plan to update our IHE XDS business process work to be based on the 
> new ebBP
> standard. I will send you a draft as soon as we produce it.
> We can then work on it collaboratively, as you have proposed.
>
> 3. I also think that a graphical ebBP editor together with a CPP
> editor to help to produce ebBP and CPP definitions in XML automatically
> may really help for industry take up.
>
> Finally, since our work will be done within the scope
> of the Artemis project, I am copying this email to our sponsors
> from the European Commission, namely, Dr. Iakovidis and Dr. Purcarea.
>
> Best regards,
> Asuman