HL7 Advanced Web Services Profiles

HL7 Advanced Web Services Profiles

  • Comments 9

HL7 is an ANSI-accredited Standards Organization that develops interface requirements for health care organizations.   Last September the following profiles were submitted by Microsoft to HL7:

If you work in Healthcare you are probably already aware of these profiles.  If you don't work in Healthcare you should still take a look - these profile serve as excellent guidelines for using some of the advanced Web Services specifications.

Conngratulations to Roberto Ruggeri, Chris Kaler, Felipe Cabrera and Mauro Regio!

Leave a Comment
  • Please add 6 and 7 and type the answer here:
  • Post
  • other HL7-related stories (a la ebXML) at http://healthcare.xml.org/news/ and http://www.ebxmlforum.org/articles/ebfor_eHealthcare.html
  • (via Loosely Coupled Thinking) HL7 is an ANSI-accredited Standards Organization that develops interface requirements for health care organizations.   Last September the following profiles were submitted by Microsoft to HL7: Security Profile as DSTU: based on WS-Security (pdf), WS-SecureConversation, WS-Trust and WS-Policy Addressing...
  • ebXml is dead my friend
  • looks like i need to slow down a bit. john, would you care to discuss ebXML and Microsoft's approach to it? if i have misrepresented you it would make sense to clear up any misunderstandings on my part. i have heard both IBM and MS folks says ebXML is dead many times...

    I had also been meaning to ask about your compliance metadata strategy.
  • Any ties to between ERDA Famework and web services Profiles
  • KP,

    If you mean EDRA (Enterprise Development Reference Architecture), then the answer is no. EDRA was designed to standardize the internal architecture of a distributed application. HL7 is a well-known industry standard with several existing messaging patterns and messages. The profiles for HL7 could potentially be used within an EDRA-like framework. The HL7 profiles focus specifically on WS-Security, WS-Addressing and WS-ReliableMessaging. EDRA has a much broader scope, providing architectural guidance for enterprises looking to standardize the separation of business logic from the underlying infrastructure.
  • BTW - you can learn more about EDRA here: http://www.gotdotnet.com/team/rojacobs/shadowfax/shadowfaxfaq.aspx
  • James,

    While I used to work with ebXML in 1999/2000 (well before I joined Microsoft), most of the work I do these days is related to SOA and WS-I compliant web services (SOAP, WSDL, etc.). We're also developing recommendations for various vertical industries to assist them in the adoption of some of the advanced web services specifications (like WS-Security et. al.).

    Regarding Compliance metadata, Mike Burner gave a webcast a few weeks ago discussing some of the framework ideas we're working on (see http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032265153&EventCategory=5&culture=en-us&CountryCode=US). (Ignore the embarassing text crediting me with the webcast - this is Mike's baby.)

    Hope this helps!

    John
  • A long while ago I was excited to hear that someone from Microsoft was working on compliance architecture. This seemed like really good news, because RedMonk strongly believes in taking a systematic, integrated approach to the related problems
Page 1 of 1 (9 items)