HL7 v3 and SAML

[Peter Heggie]

Our local RHIO / IHE is saying that HL7v3 has different protocols than HL7 v2.x. I’m sure I’m not understanding what they are saying. Protocols are for communication, and HL7v2 or v3 specifies data content and format, right?

They are saying that when sending CCDs or other documents to them, they will require WSI Basic Profile v1.2 which includes SAML. Doesn’t SAML use a real-time third party certificate authentication? Will we need to have this capability in Cloverleaf in the coming years?

Peter

Peter Heggie
PeterHeggie@crouse.org

Topic

[Jim Kosloskey]

Peter,

Sounds like they want to exchange using Web Services and they want 1.2 using SAML as the security model. There are a number of ways SAML can be deployed so you will need to find out which way they are doing it and it does involve certificates as I recall but the consumer does not alwayd need to provide the certificate depending on the method deployed. Again that is my recollection of the reading I have done not practical experience.

I don’t think IB (Cloverleaf’s add-on for Web Services) supports 1.2 just 1.0 but you can chack on that.

Otherwise you will probably need to write some Tcl or potentially Java. If you are 5.8.5 Cloverleaf added a java Protocol which might give some exposure but I do not know much about it.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Peter Heggie]

ok, so they are making a disctinction between document exchange and ADT/Results. And while I’ve seen a lot of discussion here about handling various types of documents and exchanges, this is not ‘out of line’, its just a little different, actually adhering to a more rigorous technical standard (WSI 1.2) which is part of New York States requirements for RHIOs, which is based on a national standard (HITSP). So this is our first encounter with an interface based on these newer standards.

But this only applies when going outside our organizational walls, right? Our ancillary local and vpn systems will still connect using traditional protocols.

I’m curious about Cloverleaf’s capabilities – probably Cloverleaf’s Intelligent Health Broker is / will be the toolset that meets these kinds of requirements (unless as you point out, one could employ Java components to perform this work).

Peter Heggie
PeterHeggie@crouse.org

[Jim Kosloskey]

Peter,

Regarding your local ancillary systems, if they can accept what you need to send (CCD, ADT, Etc.) via TCP/IP for example then that is the exchange you will use.

Version 3.0 HL/7 can still be exchanged via mlp as far as I know.

I suspect it still will be quite a while befor many vendors support HL/7 V3.0 outside of CCD.

By the way you can get the CCD Schema from the HL/7 group and download it then compile it on Cloverleaf. I did that and built a ‘dummy’ basic CCD just to fool around with.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Peter Heggie]

Thanks Jim

Peter Heggie
PeterHeggie@crouse.org

[James Cobane]

The HITSP-C32 xsd (schema) file is provided on Cloverleaf (at least under 5.8 ) and can be found under the $HCIROOT/formats/xml; see below ls -al output:

hci@rhaxie3p:(/qvdx/cis5.8/integrator/formats/xml) #ls -al

total 1192

drwxrwxr-x

[Author]

Replies