An Archetype-based Testing Framework

Transcription

1 An Archetype-based Testing Framework Rong Chen a,b, Sebastian Garde c, Thomas Beale c, Mikael Nyström a, Daniel Karlsson a, Gunnar Klein d, Hans Åhlfeldt a a Department of Biomedical Engineering, Linköping University, Sweden b Cambio Healthcare Systems, Sweden c Ocean Informatics UK, London d Karolinska Institutet, Sweden May 26, 2008 MIE 2008 in Göteborg, Sweden 1

2 Where do we stand? Electronic Health Records (EHR) openehr, EN/ISO years EU & Australian R&D on EHR Archetypes & Semantic Interoperability Interoperable & adaptive EHR systems But how to validate that? May 26, 2008 MIE 2008 in Göteborg, Sweden 2

3 The openehr artefact ecosystem Data capture Data validation Fine-grained querying May 26, 2008 MIE 2008 in Göteborg, Sweden 3

4 Validation Objectives Not to find syntactic errors the parsing tools find those To validate archetypes against the clinical requirements semantic validation For a single archetype Use fixtures to test whether the archetype behaves the way it was intended For a repository of archetypes Search for refactoring and other design improvement opportunities, e.g. repetition, overlap, bad design May 26, 2008 MIE 2008 in Göteborg, Sweden 4

5 Unit testing But The Classic Way in Software it works, sort of implementation & platform specific Implementation and plaform independent testcases maintained in source code Portable test case specifications tedious manual effort Preferrably auto-generated tests May 26, 2008 MIE 2008 in Göteborg, Sweden 5

6 The technical Requirements Testing should be platform-independent and implementation-independent Tests are archetype-based and preferably auto-generated Test fixtures as input and expected output Kernel operations & Archetypes Scope: [ kernel ] + archetypes May 26, 2008 MIE 2008 in Göteborg, Sweden 6

7 Platform-independent Archetypes Design Diagram Test runner Any other platform test.net Kernel Implementation A derived from Test Fixtures Java test Kernel Implementation 1 derived from test Kernel Implementation 2 Test Cases run Test runner test Kernel Implementation 3 May 26, 2008 MIE 2008 in Göteborg, Sweden 7

8 RM instances or primitives Valid or invalid according to archetypes dadl format Auto-Generation strategies Test Fixtures based on constraints in the archetypes e.g. validation ranges, node existence < archetype_node_id = <"openehr-ehr-observation.blood_pressure.v1" name = < value = <"BP measurement" archetype_details = < archetype_id = (ARCHETYPE_ID) < value = <"openehr-ehr-observation.blood_pressure.v1" rm_version = <"1.0.1" language = < terminology_id = (TERMINOLOGY_ID) < value = <"ISO_639-1" code_string = <"en" encoding = < terminology_id = (TERMINOLOGY_ID) < value = <"IANA_character-sets" code_string = <"UTF-8" subject = (PARTY_SELF) < data = < archetype_node_id = <"at0001" name = < value = <"history" origin = < T09:22:00 events = < [1] = < archetype_node_id = <"at0006" name = < value = <"sitting" time = < T09:22:00 data = < archetype_node_id = <"at0003" name = < value = <"item list" <"openehr-ehr-observation.blood_pressure.v1" May 26, 2008 MIE 2008 in Göteborg, Sweden 8

9 Test Case Specifications 1. Kernel operation for the test case 2. Common test fixtures 3. List of tests unique name input values expected output <querytestspecification <instanceblood_pressure_002.dadl</instance <tests <test name="blood Pressure - Systolic Value Query - native language" <path/data/events['baseline reading']/data/items['systolic']/value/magnitude</path <expected120.0</expected </test <test name="blood Pressure - Diastolic Value Query - native language" <path/data/events['baseline reading']/data/items['diastolic']/value/magnitude</path <expected80.0</expected </test </tests </querytestspecification May 26, 2008 MIE 2008 in Göteborg, Sweden 9

10 <querytestspecification <instanceblood_pressure_002.dadl</instance <tests <test name="blood Pressure - Systolic Value Query - native la <path/data/events['baseline reading'] /data/items['systolic']/value/magnitude</path <expected120.0</expected </test <test name="blood Pressure - Diastolic Value Query - native l <path/data/events['baseline reading'] /data/items['diastolic']/value/magnitude</path <expected80.0</expected </test </tests </querytestspecification May 26, 2008 MIE 2008 in Göteborg, Sweden 10

11 Proof of Concept Extend JUnit testing framework For organizing testcases, fixtures and results Test result assertions Test runners for test excution openehr Java components the kernel, the parsers Prototype: archetype-testing ArchetypeTestCase ArchetypeQueryTestCase XML Schema for query test specification May 26, 2008 MIE 2008 in Göteborg, Sweden 11

12 Class Diagram junit.testcase +setup() +teardown() +runtest() execute TestRunner +starttest() +endtest() DADLBinding +bind() use ArchetypeTestCase +loadtestspecification() +loadrminstance() +loadarchetype() ADLParser +parse() use ArchetypeQueryTestCase ArchetypeValidationTestCase +counttests() +runtest() +setup() +suite() +runtest() invoke Kernel / EHR Client +create() +validate() +query() May 26, 2008 MIE 2008 in Göteborg, Sweden 12

13 Archetype Testing in Action May 26, 2008 MIE 2008 in Göteborg, Sweden 13

14 A Failed Query Test Expected Standing but was Sitting May 26, 2008 MIE 2008 in Göteborg, Sweden 14

15 Summary Testing framework for validation of archetype formalism implementations Future EHR Client API + more operations Auto-generation of test fixtures / test cases Integeration with archetype tools / repository EHR Semantic Interoperability!! May 26, 2008 MIE 2008 in Göteborg, Sweden 15

16 Thanks! Acknowledgements Contact Info The openehr Foundation Linköping University Karolinska Institute Ocean Informatics Cambio Healthcare Systems Rong Chen, Development May 26, 2008 MIE 2008 in Göteborg, Sweden 16