RE: [ebcore] HITSP letter draft

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

Mary,

 

We are looking to do precisely that formally from our TC.  And establishing a dialogue so as to avoid this in future.

 

It's hard to believe that Brett is on the board there.  What on earth is going on?

 

To your point - that is EXACTLY the problem I'm seeing - people should NOT be trying to predetermine - use this instead of that when this scenario applies.  This is merely imposing their own narrow view and prejudices on others.  How am I to be saying use ebXML instead of foobar?

 

State the strengthes of the technologies - let the implementers run their own AoA scenarios and come up with what makes best sense.  But do not exclude perfectly viable OASIS specifications from their choices in the first instance!!!

 

Thanks, DW

 

 

-------- Original Message --------
Subject: RE: [ebcore] HITSP letter draft
From: "Mary McRae" <mary.mcrae@oasis-open.org>
Date: Tue, February 24, 2009 3:09 pm
To: "'David RR Webber (XML)'" <david@drrw.info>, "'Breininger,Kathryn
R'" <kathryn.r.breininger@boeing.com>
Cc: <ebcore@lists.oasis-open.org>

Hi David,

 

  The goal of HITSP is to create a reliable, recommended and approved end-to-end set of standards to solve each particular use case. The committees are doing that by singling out specific standards to be used for each task/component. OASIS is a member of HITSP, and Brett Trusko represents us on the Board of Directors. My suggestion is that if you feel a particular HITSP use case recommendation should be using ebXML rather than something else that you correspond with the chair of that particular committee, or submit your comments during the public review periods.

 

Mary

 

From: David RR Webber (XML) [mailto:david@drrw.info]
Sent: Tuesday, February 24, 2009 2:31 PM
To: Breininger,Kathryn R
Cc: ebcore@lists.oasis-open.org
Subject: RE: [ebcore] HITSP letter draft

 

Kathryn,

 

This is a strategic question for sure.  From the BOD position - I'm sure they would want HITSP to view OASIS specifications generally as equally of merit and applicable.  I think HITSP have gone to a bad place when they starting trying to differenciate and pick and choose.  This rarely works out well.  Technically it is difficult to assume that only one size fits all.  This is absolutely something HITSP should be leaving to their projects to make the calls on - and the pro's and con's - not prejudging this on arbitary basis.

 

Unfortunately there's not a nice way to say that in the letter - so I guess we kind of help them read between the lines... ; -)

 

Thanks, DW

 

 

-------- Original Message --------
Subject: RE: [ebcore] HITSP letter draft
From: "Breininger, Kathryn R" <kathryn.r.breininger@boeing.com>
Date: Tue, February 24, 2009 1:19 pm
To: "David RR Webber (XML)" <david@drrw.info>,
<ebcore@lists.oasis-open.org>

Thank you David - appreciate you working this!  Should we list the specific OASIS standards we are referring to in the letter?

 

I would like to cover this and the draft "10 reasons" document at our next ebCORE meeting and hopefully reach agreement so we can submit the letter.  Our next ebXML CORE meeting is Friday March 6th at 10:00 am Pacific Time.

 

 

Kathryn Breininger
Manager, Release & Delivery Services
CIMS - Center for Information Management Services

MC 62-LC
425-965-0242 desk
425-512-4281 cell
425-237-4582 fax

 

 

---

From: David RR Webber (XML) [mailto:david@drrw.info]
Sent: Monday, February 23, 2009 6:47 PM
To: ebcore@lists.oasis-open.org
Subject: [ebcore] HITSP letter draft

Team,

 

Here's a draft on this.

 

Below is my original post and link to their site.

 

Goal is to keep this simple and throw ball back into their court.  I do not they can publically justify their position which appears to be the result of some bad advice provided to them (as we saw with the Danish government last year).

 

Thanks, DW

 

======================

On Wednesday, HHS released for comment the health care interoperability standards; see http://edocket.access.gpo.gov/2009/pdf/E9-1068.pdf . There are a lot of references to HL7 and IHE standards, but ebXML Registry was specifically dropped; see page 4 (3602).

 

Also - I believe HL7 has endorsed ebMS V3 - so this should be reflected in HHS too.

 

Can we make official comments back to HHS from ISO and OASIS?

 

 

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php