Skip to content

Releases: openEHR/archie

Version 0.4.2

01 Feb 13:47
f943530
Compare
Choose a tag to compare
  • fixes the ADLChecker
  • fixes for finding BMM models for template_overlays
  • fixes in flattening use_archetype occurrences matches {0}

A binary of the ADL Checker commandline utility is attached.

Version 0.4.1

01 Feb 12:50
9e95d0b
Compare
Choose a tag to compare

This fixes some bugs introduced in Archie 0.4.0 that we found when testing it with our EHR implementation:

  • differential paths sometimes throw errors when validating
  • BMM did not support RM model versions

Version 0.4.0: Validation, BMM and much more

01 Feb 12:49
7bdc03f
Compare
Choose a tag to compare

This is a big release:

We’re pleased to announce Archie version 0.4!

Version 0.4 is a big change from version 0.3. Many features have been added that make Archie suitable as a library for modelling archetypes, and the existing functionality has been improved.

It includes a BMM implementation contributed by Claude Nanjo, Joey Coyle and Kurt Allen. This enables Archie to work with other reference models than the included OpenEHR reference model. The BMM files and AOM profiles that are in the ADL workbench are included in the library – of course you can supply your own as well.

We developed an archetype validator that implements nearly all of the validations in the specification, and we improved the flattener and the operational template creator to be compliant with the specifications. The flattener, archetype validator and operational template creator work with both the BMM models or with metadata derived from an actual java reference model implementation.
Many tests were added to ensure better conformance with the specification and many fixes have been introduced. We’d like to thank Thomas Beale for giving advice about many details of the working of OpenEHR implementations and for fixing mistakes in the specifications when they were found.

Of course, Archie also contains a lot of other tools, many of which allow it to be used as the basis for an EHR implementation as well as a modelling tool: An ADL parser and serializer, the OpenEHR reference models, rule evaluation, path lookup, JSON and XML (de)serialization, ODIN parsing and RM object manipulation tools.