Dear All,
I have been asking for more than 2 years for HL7 to become simplified and
free- to-use, so that it could proliferate globally. So this is good
news.....however I still await details. Like - (1) what is free, (2) how
long is it free, (3) what does 'free' really mean, (4) how soon will it
become free(time lines) and (5) what are the rules for commercial use and
localisation .
It is V2.x that especially needs to be made free as this is the version that
is the real work horse.
There is also a related issue. How will this effect HL7 membership fees -
for members and franchisees.
With warm regards,
Dr D Lavanian
MBBS,MD
CEO and MD
HCIT Consultant
www.hcitconsultant.com
www.telemedconsultant.com
Certified HL7 Specialist
Joint Secretary - Indian Association for Medical Informatics
Co-Chair, Memberships - HL7 India
Senior Consultant and Domain Expert - Healthcare Informatics and TeleHealth
Former Vice President - Healthcare Products, Bilcare Ltd
Former Vice President - Software Division, AxSys Healthtech Ltd
Former Co-convener Sub committee on Standards , Government of India, Task
force for Telemedicine
Former Vice President - Telemedicine (Technical), Apollo Hospitals Group
For useful updates in Healthcare IT, visit us at
www.facebook.com/HCitConsultant and 'friend' us.
HL7, DICOM, ICD 10, HIPAA 5010 - strategy, training, implementation
The Right Solution, at the Right Time, at the Right Place and at the Right
Price
Call us Right Now!
----- Original Message -----
From: "Bert Verhees" <[email protected]>
To: "For openEHR technical discussions"
<openehr-technical at lists.openehr.org>
Sent: Wednesday, September 05, 2012 3:14 AM
Subject: Re: HL7 opens up
On 04-09-12 20:06, Diego Bosc? wrote:
> The big question is, how does it affect us?
HL7 is primary a way of messaging. In the Netherlands HL7 is very
important, as message format. All (I mean ALL) the underlying systems
which create the messages have legacy datamodel-storage.
There is no such thing as an HL7v3 storage system on the dutch market.
Also an OpenEHR system can create HL7 messages, especially those
message-definitions which are created for the Netherlands, which are
created with focus on interoperability, to get all the legacy-systems
possible to join.
So, I see no big change for the Dutch market. Anyway, costs were never
an issue.
HL7 is also a storage concept, and I have been to some HL7-meetings,
where they discuss these kind of things.
Without any hesitation, I saw people admiring HL7 systems which needed
50 to 100 tables to store their thing, and which auto-created
SQL-statements from 250!!! lines to query the thing.
That is not my way to go, especially if the purpose is interoperability
by creating the specially defined RMIM-messages, which are written with
focus on legacy to incorporate in the messaging-EPD.
As I know the market in the Netherlands, I know it well, my expectation
is that legacy will dominate the progression next ten years, or even longer.
We even have systems which are just five years ago ported to 32 bits
Windows (from 16 bits), and still use an old fashioned API-based
database. This is one of the richest healthcare-environments in the world.
That is what is going on.
So HL7 for free, nice, we can conform to the message-definitions for
free, and if system-builders succeed in free themselves from their
academic way of software-constructing and legacy and can use HL7
constructs to store their data quick, they have an easy way for creating
the messages.
(Hey HL7 folks, the secret for you is XPath, oops, now I gave away the
secret.)
Fine. Let a thousand flowers bloom.
When we are confident in our own software, there is nothing to fear from
HL7.
That is my opinion.
kind regards
Bert Verhees
>
> 2012/9/4 Timothy Cook <timothywayne.cook at gmail.com>:
>> Finally:
>> http://www.hl7.org/about/faqs/FreeIP.cfm
>>
>>
>>
>> --
>> ============================================
>> Timothy Cook, MSc +55 21 94711995
>> MLHIM http://www.mlhim.org
>> 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 lists.openehr.org
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
_______________________________________________
openEHR-technical mailing list
openEHR-technical at lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
