Yes, https://github.com/openEHR/java-libs works for ADL 1.4.
If you want the latest and newest, ADL 2 is the way to go. You can convert the archetypes to ADL 2 using the ADL workbench and they will parse with Archie. The workbench can be found at http://www.openehr.org. If you want compatibility with existing systems, ADL 1.4 for now – I think most EHRs are 1.4 only at the moment. Regards, Pieter Bos From: openEHR-technical <openehr-technical-boun...@lists.openehr.org> on behalf of Diego Boscá <yamp...@gmail.com> Reply-To: For openEHR technical discussions <openehr-technical@lists.openehr.org> Date: Monday, 12 November 2018 at 13:44 To: For openEHR technical discussions <openehr-technical@lists.openehr.org> Subject: Re: Parsing of Archetypes/Templates Hello Georg, Archie is meant to be used with ADL2 archetypes, if you want to parse 1.4 archetypes I think java implementation you mentioned before is your current best option. Regards El lun., 12 nov. 2018 a las 13:40, Georg Fette (<georg.fe...@uni-wuerzburg.de<mailto:georg.fe...@uni-wuerzburg.de>>) escribió: Hi Peter, The Archie-Toolkit looks promising. I tried to parse one of the archetypes from the CKM (BloodPressure) and tried to parse the exported ADL. However, I got a Exception when trying this because the exported ADL does not seem to be parseable: line 1:24 mismatched input '1.4' expecting VERSION_ID line 2:1 mismatched input 'openEHR-EHR-OBSERVATION.blood_pressure.v1' expecting ARCHETYPE_HRID With the exported XML and the try to unmarshal the XML with the JAXBUtil I also did not succeed. Is there somewhere a testcase were I can see a working example of a parsed ADL String ? Greetings Georg Hello George, If you are looking for something to handle ADL 2 archetypes - the most recent version -, have a look at https://github.com/opener/archie . It is a java library that can parse archetypes, flatten and validate them, create operational templates and more. Are you using the openehr reference model, or something else like fihr? Although Archie can parse and serialize archetypes in XML, archetypes are usually stored as ADL. This is a custom more readable format. Of course you can then easily convert it to XML or Json to work with them in other tools where you do not have an ADL parser ready. Note that for ADL 2 as far as I know there is no official XSD released yet, so it is possible you run into compatibility problems with XML. For ADL 1.4 this is not a problem. Regards, Pieter Bos Am 12.11.2018 um 09:18 schrieb Georg Fette: > Hello, > For a project we want to create a generic mechanism to transform > archetypes into FHIR Logical Models, so we can store, retrieve and > query archetype instance with FHIR tools (CQL, FHIR-REST-API-query). > At the moment we just want to read/write archetypes and not archetype > instances. We are looking for existing components to parse and process > archetypes. I have some questions I encountered related to these issues: > - I have found several projects that store openEHR-data (archetypes as > well as archetype instances) into different data substrates (Neo4J, > ARM (archetype relational mapping), EtherCIS). Although I have not yet > looked at the code of these projects I assume that they take an > archetype XML-file, parse it and thus create a runtime object of the > archetype. That runtime object can then be given as a parameter to a > persistence layer (e.g. JOOQ, Hibernate, etc.). In order to reuse > something from already existing projects I am looking for a parser > that creates a runtime object from an archetype-XML-String, so we can > write our own components that transform it into a FHIR runtime object. > The component we are looking for should preferably be written in Java, > as this is our language of choice in our project. > - I am not ye sure if we are looking for a method to transform > archetypes, templates or operational templates into FHIR related > structures, as I am not yet that familiar with which data structure is > preferably used for which kind of task. Therefore, component that, > instead of archetypes, parse templates or operational templates would > be appreciated as well. > Greetings > Georg > -- --------------------------------------------------------------------- Dipl.-Inf. Georg Fette Raum: B001 Universität Würzburg Tel.: +49-(0)931-31-85516 Am Hubland Fax.: +49-(0)931-31-86732 97074 Würzburg mail: georg.fe...@uni-wuerzburg.de<mailto:georg.fe...@uni-wuerzburg.de> --------------------------------------------------------------------- _______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org<mailto:openEHR-technical@lists.openehr.org> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- [VeraTech for Health SL]<https://htmlsig.com/t/000001C268PZ> [Twitter] <https://htmlsig.com/t/000001C47QQH> [LinkedIn] <https://htmlsig.com/t/000001C4DPJG> [Maps] <https://htmlsig.com/t/000001BZTWS7> [https://s3.amazonaws.com/htmlsig-assets/spacer.gif] Diego Boscá Tomás / Senior developer diebo...@veratech.es<mailto:diebo...@veratech.es> yamp...@gmail.com<mailto:yamp...@gmail.com> VeraTech for Health SL +34 654604676<tel:+34%20654604676> www.veratech.es<http://www.veratech.es/> La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde VERATECH FOR HEALTH, SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Le recordamos que sus datos han sido incorporados en el sistema de tratamiento de VERATECH FOR HEALTH, SL y que siempre y cuando se cumplan los requisitos exigidos por la normativa, usted podrá ejercer sus derechos de acceso, rectificación, limitación de tratamiento, supresión, portabilidad y oposición/revocación, en los términos que establece la normativa vigente en materia de protección de datos, dirigiendo su petición a Avda Puerto 237, 1º, pta 1 - 46011 Valencia o bien a través de correo electrónico d...@veratech.es<mailto:d...@veratech.es> Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
