Models & Modelling Heather Leslie Sebastian Guard Heather Grain May 8, 2009 openEHR Heather Leslie Sebastian Guard Heather Grain openEHR + SNOMED CT = Making Health Compute

Presenters Heather Grain Sebastian Garde (Germany) member of GeHCO (NFP) providers of education for openEHR and OceanInformatics Sebastian Garde (Germany) OceanInformatics Heather Leslie (Australia) Clinical Knowledge Manager – Leader Not attending but happy to answer further questions © Ocean Informatics 2009

Outline of presentation Models & Modelling May 8, 2009 Outline of presentation Introduction to functionality Introduction to tools Demonstration of the tools Summary Users Open access components Education available openEHR © Ocean Informatics 2009 openEHR + SNOMED CT = Making Health Compute

Functionality EHR structure standard (ISO 13606) EHR content specifications (archetypes) Metadata Rules References Governance International, national, project, local Technical implementation Templates Exports © Ocean Informatics 2016

Moving the standards bar back to the core Records, Data repositories, Reports Forms, Messages, Software products, Use case data specifications Knowledge Based Data Specification © GeHCo 2016

Moving the standards bar back to the core Records, Data repositories, Reports Forms, Messages, Software products, Use case data specifications Knowledge Based Data Specification © GeHCo 2016

Moving the standards bar back to the core openEHR is underpinning standard and tooling Records, Data repositories, Reports Forms, Messages, Software products, Use case data specifications Knowledge Based Data Specification © GeHCo 2016

EHR structure (RIM) Composition (Author, dates, etc) Section Models & Modelling May 8, 2009 EHR structure (RIM) Includes Structure, Security, Versioning, People, Dates, Times, Data types Composition (Author, dates, etc) Section for forms/display/communication templates Entries (including groups of data) Administration Observations Evaluations Instructions Actions Includes versions © Ocean Informatics 2016 openEHR + SNOMED CT = Making Health Compute

Archetype Design Priorities Archetypes (instances of EHR structure) Priority 1: Design archetypes based on the semantic content Priority 2: Maximise re-usability of archetypes Priority 3: Create a maximal data set for a universal use case © Ocean Informatics 2009

Tooling Clinical Knowledge Manager www.openEHR/ckm - open to all Models & Modelling May 8, 2009 Tooling Clinical Knowledge Manager www.openEHR/ckm - open to all Library of archetypes (data specifications) Designed for clinical engagement Collaboration portal and Governance Clinically usable with technical capacity underpinning International open access Your version – has a cost to established © Ocean Informatics 2016 openEHR + SNOMED CT = Making Health Compute

Example screen of data spec. © Ocean Informatics 2016

Tooling Archetype editor Template Designer Consultation and consensus Models & Modelling May 8, 2009 Tooling Archetype editor Consultation and consensus Publication and progressive development Template Designer Select content from archetypes for form Constrain content for specific use case Create screen, form, xml Harmonise with messaging publication or implementation requirements Openly available © Ocean Informatics 2016 openEHR + SNOMED CT = Making Health Compute

b CARE ENTRY: Features Feature Eval Obs Inst Act Protocol – how and basis for recording b History – allows time-series and aggregates State – records patient data for interpretation Pathway – work flow steps and states © Ocean Informatics 2009

History/Event examples © Ocean Informatics 2009

Action State Model © Ocean Informatics 2009

Medication Order : Pathways Models & Modelling May 8, 2009 Medication Order : Pathways …including workflow/status pathways © Ocean Informatics 2009 openEHR + SNOMED CT = Making Health Compute

Archetype Specialisation Models & Modelling May 8, 2009 Archetype Specialisation Expressed as a hyphen between the parent archetype name and the child eg OBSERVATION.parent-child.v1.adl Specialisation of an archetype allows: Add new data elements (primarily) Changes to its definition such that its constraints are ‘narrower’ than those of the parent Any data created via the use of the specialised archetype is thus conformant both to it and its parent © Ocean Informatics 2009 openEHR + SNOMED CT = Making Health Compute

Specialisation © Ocean Informatics 2009

Open Components International CKM Archetype Editor Template Designer Costs associated with your own CKM tooling Education Support if required © Ocean Informatics 2016

Users © Ocean Informatics 2016

Education Scope Models & Modelling May 8, 2009 Face to face internationally, and online just in time learning © Ocean Informatics 2016 openEHR + SNOMED CT = Making Health Compute

Demonstration - Sebastian © Ocean Informatics 2016

Questions Additional information available at www.openEHR.org www.oceaninformatics.com Questions to heather.leslie@oceaninformatics.com © Ocean Informatics 2016