1. Thomas Beale CTO, Ocean Informatics Copyright 2012 Ocean Informatics Tromso 27 May 2014

2.  There is growing acceptance of standardised content-modelling in health using archetypes ◦ CIMI taskforce, led by Dr Stan Huff (Intermountain) ◦ openEHR.org archetypes ◦ Other national programmes ◦ New OMG Archetype Modelling Language (AML) RfP ◦ VA’s Model-driven Health Tools (MDHT) now moving to incorporate archetype semantics Copyright 2012 Ocean Informatics

3.  Specialisation fully specified ◦ Basis for all ‘profiling’, localisation etc ◦ Templates are specialised archetypes  Annotations  Direct archetype ref without slot now possible  New internal coding system & rules  Coded term is a built-in type  openEHR special types replaced by ‘tuples’  New value set system  Bindings simplified & done as IHTSDO URIs  New archetype identifiers  Standardised lifecycle  Added meta-data (description section)  openEHR wiki page openEHR wiki page Copyright 2013 Ocean Informatics

7.  Can be carried on indefinitely  Can be used e.g. just to add annotations Copyright 2013 Ocean Informatics

9.  C_ATTRIBUTE.differential_path enables specialised archetype to define constraints at a deep point with respect to a parent  ARCHETYPE_CONTRAINT.c_conforms_to() and c_congruent_to() allow validation down the specialisation lineage  SIBLING_ORDER class allows specialised archetype to insert object in container at particular point Copyright 2013 Ocean Informatics

10.  In ADL 1.5, a C_ARCHETYPE_ROOT can ‘fill’ a slot in the specialisation relation ◦ I.e. the slot-filling function of ‘templating’ is achieved like this  (not shown here) – flattening & diffing algorithms – available open source, and in final specification Copyright 2013 Ocean Informatics

11.  Template as single text file  Easy to read and understand  Tools can convert to multiple archetypes if necessary Copyright 2013 Ocean Informatics

14.  C_ARCHETYPE_ROOT class allows specialised archetype to define another archetype where a C_COMPLEX_OBJECT would normally be, with no need for a slot. ◦ Use for pure reuse / refactoring Copyright 2013 Ocean Informatics

15. ElementADL 1.4ADL 1.5 Node idsat0001id1, id24 Specialised node idsat0.1, at0001.1id0.1, id1.3 Value idsat-codes Value set idsac-codes Copyright 2013 Ocean Informatics Every node must have an id-code, but not every id-code has to have a definition in the terminology – avoid ‘junk’ definitions for 1:1 nodes e.g. DV_TEXT under ELEMENT.value Ids = names of things; separated from values of things (at-codes) openEHR wiki page

16. Copyright 2013 Ocean Informatics

18.  C_ARCHETYPE_ROOT class allows specialised archetype to define another archetype where a C_COMPLEX_OBJECT would normally be, with no need for a slot. ◦ Use for pure reuse / refactoring Copyright 2013 Ocean Informatics

19.  There is an AOM type TERMINOLOGY_CODE  We can map different RM coded term type to this using the ‘AOM profile’ in the AWB Copyright 2013 Ocean Informatics CIMI ISO13606

20.  This means that AOM-based archetype tools can detect coded terms natively  Enables proper visualisation  Enables proper connection to terminology services  Enables model conversion in the future Copyright 2013 Ocean Informatics

22. ADL 1.4 ADL 1.5

23. Copyright 2013 Ocean Informatics

24.  Tuple constraints allow generic way of constraining covarying attributes, e.g. speed range and units; volume and units  The ADL 1.4 special openEHR types for C_DV_QUANTITY and C_DV_ORDINAL are now gone, replaced by tuples  Automatically converted in 1.4 archetypes  openEHR wiki page openEHR wiki page Copyright 2013 Ocean Informatics

25. ADL 1.4ADL 1.5

26. Copyright 2013 Ocean Informatics ADL 1.4ADL 1.5

27. Copyright 2013 Ocean Informatics

30. ADL 1.4ADL 1.5 IHTSDO URIs

31.  3-part version numbers  Mostly follows rules of semver.orgsemver.org  Optional namespaces  Identifier is now generated from parts Copyright 2013 Ocean Informatics

34.  Could SNOMED CT ids or Guids or … be used in the future?  Possibly, but the infrastructure is not available today  Discussions with Mayo & MDHT groups indicate that current approach is optimal for this release Copyright 2013 Ocean Informatics

40.  ADL 1.5 archetypes are no longer technically a pure superset of ADL 1.4 semantics ◦ This is ok – it just means conversion ◦ The ADL workbench performs this automatically ◦ And finds quite a lot of errors on the way ◦ It can also generate old style paths for AQL queries into repositories based on ADL 1.4 version of archetypes Copyright 2013 Ocean Informatics

44.  Most tools still on ADL 1.4  ADL Workbench is 1.5 ◦ Still working on interactive editing  We are starting a java ADL 1.5 tooling project with openEHR developers ◦ Core parser, etc already done ◦ Announcement soon  The BMM RM file format is starting to be used outside openEHR – CIMI now uses it; there is a conversion plug-in for EA Copyright 2013 Ocean Informatics

45.  ADL 1.5 solves problems of ADL 1.4  ADL 1.5 adds numerous innovations  Detailed review by Mayo, Intermountain  Will support powerful content modelling including templating with any RM  Provides a proper way of doing what HL7 calls ‘profiling’  May be used to solve profiling problem in FHIR ◦ Experiment underway! Copyright 2013 Ocean Informatics

46.  Specification review  ADL 1.5 workbench testing  ADL 1.5 test archetype development  ADL 1.5 workbench development (Eiffel)  Java tooling platform development  Many resources at ◦ https://github.com/openEHR https://github.com/openEHR Copyright 2013 Ocean Informatics

47.  http://www.openEHR.org http://www.openEHR.org  Mailing lists ◦ http://www.openehr.org/community/mailinglists http://www.openehr.org/community/mailinglists Copyright 2012 Ocean Informatics