[FWD: Feedback to JCC on ISO TC215 e-Business study; Questionaire]

["David RR Webber \(XML\)" <david@drrw.info>]

Team,

 

I just realized this is very appropo to ebSOA. 

 

This is work that CEFACT and TC215 are looking to coordinate.

 

Having templates for ebXML use patterns that can then be readily adapted.

 

Providing the means to support and represent that - definately something we can potentially accomplish by subsetting the FERA contributed work - and providing the architecture level diagrams and components definition as a minimum.

 

This would be without having to deep dive into the specifics of the implementation layer details at all - since the individual ebXML spec's each provide those from implementers.

 

Just looking for some easily achievable goals for us in 2007!?!?

 

DW

"The way to be is to do" - Confucius (551-472 B.C.)

-------- Original Message --------

 

-------- Notes --------

 

What I see here is that HL7 in the US has adopted ebXML but use is lagging; the HL7 RIM relates to CCTS; and the joint DHS/HHS CDC/PHIN project is using ebMS/CPA for emergency alerting; eRA NIH is using ebMS/CPA for adminstrative exchanges; and the EHR work in IHE/XDS work is using ebXML Registry.  NIST also have an ebxml registry supporting HL7 RIM vocabularies.  Then in Europe we have the UK NHS Spine supporting ebMS, and the Norway NIA using ebMS/CPA.

 

What is missing is some profiles of these submitted to TC215 to act as templates and guidelines for adopters.  This would be more enabling - including not just ebMS/CPA, but BPSS, registry and CCTS patterns.  This would enable the value proposition to be more clearly seen.  For example the value proposition of using BPEL, ebMS/CPA and Oracle - as shown in this use case -

http://webservices.sys-con.com/read/318418.htm  - this could be readily adapted to medical supplies and hospitals - same needs

 

Then another whole use case is Registry, CPA, MoU, vocabulary - as in this Navy Medical proposal:

http://www/ebxmlforum.net/research/Registry-Managed-MOU-CPA-PoC-May-2005.ppt

- this would be highly re-usable to create standard contracts for health service providers, medical suppliers, etc.

 

And then of course - medical insurance reimbursement - the Norway NIA whitepaper:

http://www.oasis-open.org/casestudies/Trygdeetaten-A4.pdf

 

So what I think here is the need to focus - if we propose giving TC215 templates for ebXML patterns for healthcare - then this would be a) easy to do, b) very enabling for adopters, c) show clear value propositions leading to more adoption and buy-in.

 

B2B clearly has a huge future in enabling better healthcare delivery at a lower adminstrative cost and enabling things like BAM and KM.

Questions:

1. Which sector and/or group do you represent? (Healthcare, Business, ICT, Standardisation, ........)

>>     Healthcare IT

2. What do you think can be the benefit of using ebXML for TC215 and or HL7?

>>  Clear proven reliable use patterns that can be easily replicated for exploiting ebXML technology

3. Which parts of ebXML are of most interest for TC215

>>  Clearly there are at least these six use cases:

    - ebXML messaging with CPA - provides secure lightweight reliable messaging using web service infrastructure

    - Registry - provides records management + workflow tracking and  then semantic domain repository (two different roles)

    - CCTS - provide consistent way to represent business semantics

    - BPSS - allows modelling of complex public business interactions and workflows between care providers / accounting

    - CPA / MoU / Registry - collaboration control - ability to manage extended B2B network of participants

    - Enabling KM and BAM across a health provider network by exploiting power of B2B and formal XML content exchanges

 

4. Which areas of the healthcare domain can use ebXML as it is (Patient records, reimbursement, .........)

>> complete B2B related care management and accounting.  Also research areas and semantics / collaboration + registry

5.  Is there a need for TC215 to support the ebXML development process in common (not only Healthcare)?

>> Avoid ocean boiling - let's do healthcare first - obviously ebXML is a horizontal set of standards that's domain neutral

6. Organisational viewpoint: How can we work together in the future with ISO, OASIS, UN/cefact and others for e-Business (New liasons, participation in other groups, a new WG or task Force within TC215, ......)?

>> Deriving use cases and standard patterns that are documented and replicatable easily.

7. If a new TC215 WG is proposed, what should be the main target of this group.

>> Developing templates and use patterns.

 

Please take a short time to fill in the questions of this email and return them to me before 1 March 2007.