difference and relationship between openEHR and EN13606

Ian McNicoll ian at freshehr.com
Wed Aug 26 11:06:19 EDT 2015


Hi Gerard,

Agreed - I was using messaging loosely - 'interfacing between systems' is
better.

Ian

Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: ian at freshehr.com
twitter: @ianmcnicoll

Co-Chair, openEHR Foundation ian.mcnicoll at openehr.org
Director, freshEHR Clinical Informatics Ltd.
Director, HANDIHealth CIC
Hon. Senior Research Associate, CHIME, UCL

On 26 August 2015 at 15:04, "Gerard Freriks (privé)" <gfrer at luna.nl> wrote:

> Hi,
>
> I must repeat the scope of 13606 verbatim once more.
> It is NOT only for messaging but also for *Interfaces*
>
>
>
> Gerard Freriks
> +31 620347088
> gfrer at luna.nl
>
>
>
>
>    1. *Scope*
>
> *This standard is for the communication of part or all of the electronic
> health record (EHR) of a single identified subject of care between EHR
> systems, or between EHR systems and a centralised EHR data repository. *
>
> *It may also be used for EHR communication between an EHR system or
> repository and clinical applications or middleware components (such as
> decision support components) that need to access or provide EHR data. *
>
> *This standard will predominantly be used to support the direct care given
> to identifiable individuals, or to support population monitoring systems
> such as disease registries and public health surveillance. Uses of health
> records for other purposes such as teaching, clinical audit, administration
> and reporting, service management, research and epidemiology, which often
> require anonymisation or aggregation of individual records, are not the
> focus of this standard but such secondary uses might also find the standard
> useful. *
>
> *This Part 1 of the multipart standard is an Information Viewpoint
> specification as defined by the Open Distributed Processing – Reference
> model (ISO/IEC 10746). This standard is not intended to specify the
> internal architecture or database design of EHR systems. *
>
>
>
>
>
> On 26 aug. 2015, at 14:57, Sebastian Garde <
> sebastian.garde at oceaninformatics.com> wrote:
>
> I'd agree with Ian here.
> While both could possibly support AQL, the difference I see is in intent,
> scope and actual implementation.
> As Gerard says, 13606's main aim is to communicate between IT-systems and
> for this, AQL may not be quite as fundamental as it is to openEHR.
>
> Sebastian
>
>
> On 26.08.2015 14:44, Ian McNicoll wrote:
>
> Hi Bert,
>
> "I would leave it with: AQL is an archetype bound query language, and
> every system which is build on archetypes is able to implement AQL."
>
> That is fair enough but we were asked to characterise the differences
> between 13606 and openEHR and I am comfortable that the actual and formal
> adoption of AQL is one of those  differences.
>
> AQL is on the openEHR specifications roadmap but AFAIK this is not the
> case for 13606. Of course that does not stop 13606 vendors implementing AQL
> but in terms of actual differences between the 2 communities the adoption,
> or intention to adopt AQL seems (from the outside) somewhat different both
> at a practical and formal level.
>
> Although AQL adoption in the openEHR community is far from universal, most
> of the vendors/developers that I have spoken to see it as something they
> want to implement, particularly as GDL is somewhat dependent on AQL.
>
> I am just trying to ascertain if there is similar enthusiasm/intention
> amongst 13606 vendors, or if AQL forms part of the current 13606 refresh
> discussions.
>
> Ian
>
>
>
>
> Dr Ian McNicoll
> mobile +44 (0)775 209 7859
> office +44 (0)1536 414994
> skype: ianmcnicoll
> email: ian at freshehr.com
> twitter: @ianmcnicoll
>
> Co-Chair, openEHR Foundation  <ian.mcnicoll at openehr.org>
> ian.mcnicoll at openehr.org
> Director, freshEHR Clinical Informatics Ltd.
> Director, HANDIHealth CIC
> Hon. Senior Research Associate, CHIME, UCL
>
> On 26 August 2015 at 13:28, Bert Verhees <bert.verhees at rosa.nl> wrote:
>
>> On 26-08-15 14:23, Ian McNicoll wrote:
>>
>>> but am not aware of any non-openEHR
>>> implementations
>>>
>> Is there a Xhosa implementation of 13606 or OpenEHR?
>>
>> Does that mean OpenEHR or 13606 are not able to support Xhosa?
>>
>> I would leave it with: AQL is an archetype bound query language, and
>> every system which is build on archetypes is able to implement AQL.
>>
>>
>> _______________________________________________
>> openEHR-technical mailing list
>> openEHR-technical at lists.openehr.org
>>
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>
>
>
>
> _______________________________________________
> openEHR-technical mailing listopenEHR-technical at lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
>
> --
>
> *Dr. Sebastian Garde*
> *Dr. sc. hum., Dipl.-Inform. Med, FACHI*
> Ocean Informatics
>
> Skype: gardeseb
>
>
> ------------------------------
> [image: Avast logo] <https://www.avast.com/antivirus>
>
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> www.avast.com <https://www.avast.com/antivirus>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150826/a83ebfaa/attachment-0002.html>


More information about the openEHR-technical mailing list