OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-poc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: Tech Spec 0.55 - HL7 Scenario Details

  In reading the HL7 Track over, it's clear that this business process is substantially more complex than the Buyer/Seller Automotive stuff we've been doing so far. In the past, it was enough to show an XML document going in, and another one coming out. It's a cheap trick though - everyone has seen a purchase order or an invoice in XML before.

  In the conference call, I hear a lot of people volunteering MSH software, but I'm guessing that very few are interested in designing application-level code or guis to demonstrate how an HL7 user-agent would interact. Even if they did - as was the case with London and Tokyo, the end result is a bit lacking. A few mockup screens are designed to emulate a real application at work. Each vendor makes their own screens and the whole demo looks a little piecemeal.

  I'm wondering what HL7's current messaging infrastructure looks like in terms of software. I also wonder if it can be used by our group to demonstrate how we're supporting their business process. Even if that software consisted of a bunch of HTML forms to use as a layout, at least we could find some common ground and save ourselves some application-design or gui-design work.

  Liora can you comment on this? The use cases and sequence diagrams are only one part of the integration process. I'd like more information on how you create the XML content. Schemas would also be helpful.

// Michael Joya
// XML Global Research and Development
// 1818 Cornwall Ave. Suite 9
// Vancouver, Canada
// 604-717-1100x230

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC