Hi Wajahat,

just for reference, the openEHR EHR EXTRACT specification is here 
<http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/rm/ehr_extract_im.pdf>.
 
An example of this model being used for archetypes was mentioned in a 
post on the technical list reproduced below.

In addition, a new version of the ADL Workbench is coming out in a few 
days, with complete reference model browsing and a beta version of XML 
generation, which may help in your general design work. The following 
release will include ADL 1.4 and 1.5 level XML, with Template-based XSDs 
coming in a subsequent release. There will also be basic editing capability.

There will be a separate announcements about this. Obviously this 
doesn't actually 'do the work' you mention below, but in fact it is not 
that hard to do even now - I suggest looking at the example mentioned above.

- thomas

>
> I have updated the page 
> http://www.openehr.org/wiki/display/spec/openEHR+EHR+Extract on the 
> openEHR EHR Extract to now include a reference to a new ADL 1.5 
> template example for a full Extract of a simple discharge summary (do 
> an SVN update on your local copy of the 
> http://www.openehr.org/svn/knowledge2/ repository to get the new 
> archetypes and templates).
>
> This work illustrates a large, realistic structure modelled as an ADL 
> 1.5 template and archetypes, and the resulting structured can be seen 
> in the 'flat view' visualisation. Soon we will have the ADL and XML 
> OPT serialisation being output.
>
> Apart from the ADL 1.5 template-based modelling, this example might 
> help people understand the openEHR EHR Extract. I sometimes see, with 
> some amusement, web pages, posts or papers saying things like 'openEHR 
> is a model of an EHR, 13606 is a model of an Extract' etc. While it is 
> true that 13606 defines only a model of an Extract, openEHR defines a 
> model of EHR information, in both a form that could be used to design 
> an EHR, and a form that is used for Extracts. Indeed, the openEHR 
> Extract is significantly more flexible than the 13606 Extract (now 
> somewhat out of date). Perhaps if there any new version of 13606 in 
> the future might be able to benefit from the design used here.
>
> - thomas beale


On 23/08/2011 02:33, Wajahat Ali Khan wrote:
> I am working on interoperability aspect between healthcare standards. 
> For running end to end scenarios I require openEHR messages (EHR 
> Extracts). So my queries are
>
> 1. Can I be provided with EHR Extracts related to blood pressure, 
> laboratory messages etc that should be in the form of concrete openEHR 
> messages to be communicated between different HIS.
> 2. EHR Extracts are in the form of .adls extension. How to convert 
> that to XML form, are there any tools available to convert ADLS form 
> to XML?
>
> Best Regards
> Wajahat Ali Khan
>
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20110823/3de605b3/attachment.html>

Reply via email to