Hi Sam,
 
You might have been thinking about this:
 
www.healthcareitnews.com/news/hl7-makes-ip-freely-available-ehrs
 
and
 
https://www.hl7.org/store/index.cfm?item=DAMFP
 

Klaus
 
 
_________________________________________________

Klaus D Veil

Adj. Assoc. Professor - University of Western Sydney
Vice-President - Australasian College of Health Informatics
CoChair - Standards Australia IT014-06 & IT014-06-03
Past Chair - HL7 Australia
Certified V2.4, V2.5 & V2.6 Specialist - HL7 Intl. (USA)
Principal - HL7 Systems & Services, Sydney, Australia

Phone: +61 412 746 457               Skype: KlausDVeil
Fax: +61 2 9475 0303        e-Mail: Klaus at Veil.net.au

Profile: www.Veil.net.au <http://www.veil.net.au/> 






-----Original Message-----
From: openehr-technical-boun...@lists.openehr.org
[mailto:openehr-technical-bounces at lists.openehr.org] On Behalf Of Sam Heard
Sent: Monday, 19 March 2012 09:34
To: 'For openEHR technical discussions'
Subject: RE: openEHR-technical Digest, Vol 67, Issue 34

Hi Tim
HL7 Twittered about making things more openly available the other
day....does anyone have the link?
Cheers, Sam

> -----Original Message-----
> From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
> bounces at openehr.org] On Behalf Of Timothy Cook
> Sent: Thursday, 23 February 2012 4:44 AM
> To: For openEHR technical discussions
> Subject: Re: openEHR-technical Digest, Vol 67, Issue 34
>
> How can anyone say that HL7 is open in any fashion?  You are not free
> to distribute it outside of your organization except in small parts so
> that the specifications cannot reproduced.
>
> See the paragraph immediately preceding the one previously quoted here:
>
> "HL7 CORPORATE/ORGANIZATIONAL MEMBERS are authorized to:
>
>     reproduce and distribute Material on an internal basis solely for
> use within their organization;
>     reproduce and distribute excerpts of Material (not entire domains
> or chapters) to any customers of a product or service implementing
> those Material, provided that the HL7 Access database may not be
> included, either in whole or in part, in any product intended for
> direct or indirect commercial resale;
>     use excerpts of Material to create customized implementation
> guides; and
>     use Material in the development of software applications and
> messaging systems for direct use or distribution without additional
> licensing fees."
>
> There is NOTHING open about this, fee paid or not.
>
> --Tim
>
> On Mon, Feb 20, 2012 at 17:55, Thomas Beale
> <thomas.beale at oceaninformatics.com> wrote:
> > On 20/02/2012 22:34, William Goossen wrote:
> >
> > Hi Heath, Thomas,
> >
> > My experience is that HL7 v3 is an open standard and OpenEHR is
> > proprietary (as owned by the OpenEHR foundation holding the
> > copyrights, albeit I understand that work is underway to sort that
> out).
> >
> >
> >
> > Correction: HL7 is open, although requires a small fee for use;
> > openEHR is an open and free specification. Neither are proprietary;
> > proprietary essentially means 'not openly published and usable'.
> > That does not apply to either HL7 or openEHR.
> >
> > - thomas
> >
> > _______________________________________________
> > openEHR-technical mailing list
> > openEHR-technical at openehr.org
> > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
> >
>
>
>
> --
> ============================================
> Timothy Cook, MSc
> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
> Skype ID == timothy.cook
> Academic.Edu Profile: http://uff.academia.edu/TimothyCook
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical


_______________________________________________
openEHR-technical mailing list
openEHR-technical at lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.or
g 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120319/af4dbdcc/attachment-0001.html>

Reply via email to