Download presentation
Presentation is loading. Please wait.
Published byLamont Chad Modified over 9 years ago
1
Data Standards The use of data structures and OpenEHR Richard Kavanagh, Head of Data Standards, HSCIC
2
What are Data Structures? Definitions of Information components used within Interoperability –Blood Pressure –Blood Spot Screening Results –Appointments Reusable definitions that are not based on any one implementation technology They are “documentation” assets not implementation assets 2
3
Why do we need them? Promotes reuse between different implementation forms Provides a “semantic target” for information structures Is more accessible than technical notation in HL7v3, HL7v2 etc. Enables engagement with less technically skilled people 3
4
The anatomy of a Data Structure. Id Name Use Misuse Metadata to describe the data structure Discrete component parts Groupings of data items Parent<>Child relationships The individual data items & their relationship to each other Text, Integer, Quantity, Coded etc SNOMED, dm+d, NHS Number Mandatory / Optional Their data types, optionality, coding details, definitions etc. 4
5
Data Structure CDA HL7v3HL7v2 FHIR other The use of Data Structures 5
6
Example : Metadata 6 Identifier of Model Name & Description Use Misuse * Image from openEHR Clinical Knowledge Manager site
7
Example : Blood Pressure 7 Mind Map Tabular Form * Images from openEHR Clinical Knowledge Manager site
8
The use of OpenEHR 8 A common reference model for all structures to drive consistency A stable set of open source tools for creating models, freely available today A growing community creating openEHR models (incl. Integration Pioneers) Options for publishing and collaboration platforms
9
How will HSCIC use openEHR? 9 WILLWe WILL use it for creating data structures (aka archetypes) for interoperability standards going forwards WILLWe WILL use the publicly available openEHR tooling for creating our models WILLWe WILL publish our models in formats including openEHR formats WILL NOTWe WILL NOT use openEHR as the messaging layer WILLWe WILL use openEHR for documentation, not implementation
10
When will it arrive? 10 Multiple projects are in progress within HSCIC that are using “Data Structures” This is being embedded into the internal development methodology Some retrospective modelling is expected during Q1/Q2 next year
11
Handover Documents – Discharge Summary 11 Working with PRSB, models to include : –Record Headings within Discharge Summary –Patient Demographics –GP Practice –Referral Details –Admission Details –Discharge Details –Reason for Admission –Diagnoses –Procedures –Clinical Summary –Person Completing record –Distribution List openEHRCDA
12
Child Screening Results 12 Working with Public Health England : –Blood Spot Screening Results –Newborn Physical Examination –Newborn Hearing Screening openEHRCDA
13
GP2GP Record Transfer 13 Working with GP2GP suppliers : –Allergies & Adverse Reactions –Blood Pressure –Document Metadata openEHRHL7v3
14
GPSoC IM2 (Prototypes) 14 Working with industry partners: –Appointments –Repeat Prescriptions openEHRFHIR
15
Questions 15 What are your priority data structures? How do these align with what we are already working on – how do we create synergies?
16
Connect with us www.hscic.gov.uk @hscic www.slideshare.net/hscic 0300 303 5678
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.