OASIS ebXML Messaging Services TC

 View Only
Back to discussions
Expand all | Collapse all

FYI: [ebxml-msg] FW: Multimedia content management with HL7 V3 messages

  • 1.  FYI: [ebxml-msg] FW: Multimedia content management with HL7 V3 messages

    Posted 03-23-2007 09:54 
    




    Hello,
    

     
    

    For your information, a follow-up on this 
topic.
    

     
    

    Interestingly, HL7 is already updating its ebXML 
profile to support ebMS3:
    


     
    

    This is the 
first industry adoption of ebMS3 I am aware of (and ebMS3 is not even an 
OASIS Standard). 
    

     
    

    Regards,
    

     
    

    Pim 
    

     
    

    

    
From: Pim van der Eijk 
[mailto:lists@sonnenglanz.net]
    Sent: 23 March 2007 
10:46
    To: 'Miroslav Koncar (ZG/ETK)'; 
'transports@lists.hl7.org'
    Cc: 'Bojan Blazona 
(ZG/ETK)'
    Subject: RE: [ebxml-msg] FW: Multimedia content management 
with HL7 V3 messages

    

    

    Hello Miroslav,
    

     
    

    In ebMS3, it is possible to put the business document 
(an HL7v3 XML document in your case) in the SOAP body, as all ebXML information 
is now in the SOAP header. It still is possible to have the XML payload in the 
attachment, so the second MIME part (the first being used for the SOAP 
header).  Any additional payloads, such as multimedia data, can be stored 
in other MIME parts (referenced using "cid" content-id references, http://www.ietf.org/rfc/rfc2392.txt), 
or referenced as URLs as for example the streaming video server suggested 
example.
    

     
    

    Whether HL7v3 XML supports hyperlinks with the 
"content-id" is a question for HL7, and for the HL7 binding to ebXML 
Messaging, other people may know more about that.  The binding 
document at http://www.hl7.org/v3ballot/html/infrastructure/transport/transport-ebxml.htm (despite the 
phrase "ebXML, Release 2" in its title) is for ebMS3, and it 
says: 
    

     
    

    "While the ebMS specification allows xml User 
Messages, application messages, messages to be contained in either the SOAP Body 
element or a MIME part, this specification restricts the placement of User 
Messages for HL7 Messages to being placed in a MIME part, and for SOA style xml 
documents to be placed in the Body element." 
    

     
    

    There are some comments on multimedia attachments in 
section B.2.2 2.1.4 Payload Container of that draft.
    

     
    

    Pim

    

    

    
From: Miroslav Koncar (ZG/ETK) 
[mailto:miroslav.koncar@ericsson.com]
    Sent: 22 March 2007 
16:46
    To: Pim van der Eijk; transports@lists.hl7.org
    Cc: 
Bojan Blazona (ZG/ETK)
    Subject: RE: [ebxml-msg] FW: Multimedia content 
management with HL7 V3 messages

    

    

    Hi 
all,
    

     
    

    two questions related to the discussion below:
    

      
  
    1. is it 
  possible to reference a binary attachment contained in one MIME part 
  from the HL7v3 XML formatted message contained in another, where none of 
  them are residing in the SOAP envelope (Figure 7 in the ebMS v3.0 Part 1 
  document - first MIME Part in the MIME envelope)? 
  
    2. the 
  same question as above, but this time HL7v3 message is residing the SOAP body 
  of the first MIME part of the MIME envelope
    

     
    

    Note 
that HL7 and ebXML specification can be found at: http://www.hl7.org/v3ballot/html/infrastructure/transport/transport-ebxml.htm
    

     
    

    Thanks, all the best,
    

    Miroslav
    

     

    

    
  
    
  
    
  From: owner-transports@lists.hl7.org 
  [mailto:owner-transports@lists.hl7.org] On Behalf Of Pim van der 
  Eijk
    Sent: Thursday, March 22, 2007 4:30 PM
    To: 
  transports@lists.hl7.org
    Subject: FW: [ebxml-msg] FW: Multimedia 
  content management with HL7 V3 messages

    
  
    
  
    From: David RR Webber 
  (XML) [mailto:david@drrw.info]
    Sent: 22 March 2007 
  14:39
    To: Pim van der Eijk
    Cc: 
  ebxml-msg@lists.oasis-open.org
    Subject: RE: [ebxml-msg] FW: 
  Multimedia content management with HL7 V3 messages

    
  
    
  
    Pim,
    
  
     
    
  
    Could you also point them at the implementation NIH has please - 
    
  
     
    
  
  
     
    
  
    This supports "staged delivery" where really large payloads can be setup 
  for pulling - so you can optimize bandwidth usage - and do queued 
  delivery.
    
  
     
    
  
    Also - CDC PHIN has implemented their own mechanism to allow splitting 
  and then re-assembling of large payloads using ebXML messaging  (aka - 
  this is similar to the bittorrent approach - except of course you have secure 
  transmission - with reliable delivery - rather than sending fragments over a 
  public network - that rely on peers being online).
    
  
     
    
  
    At NIH we have successfully sent 150Mb attachments using Hermes and 
  ebMS.  The typical payload is 3MB to 5MB.  Next we intend to test 
  OrionSMG and NEXUSe2e in these environments to see how they handle this 
  transaction mix too.
    
  
     
    
  
    Thanks, DW

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


Related Content