Embed Size (px)
Citation preview
Data StandardsThe 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
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
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.
5
Data Structure
CDA
HL7v3
HL7v2FHIR
other
The use of Data Structures
6
Example : Metadata
• Identifier of Model• Name & Description• Use• Misuse
* Image from openEHR Clinical Knowledge Manager site
7
Example : Blood Pressure
Mind Map
Tabular Form
* Images from openEHR Clinical Knowledge Manager site
8
The use of OpenEHR
• 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?
• We WILL use it for creating data structures (aka archetypes) for interoperability standards going forwards
• We WILL use the publicly available openEHR tooling for creating our models
• We WILL publish our models in formats including openEHR formats
• We WILL NOT use openEHR as the messaging layer• We WILL use openEHR for documentation, not
implementation
10
When will it arrive?
• 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
• 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
openEHR CDA
12
Child Screening Results
• Working with Public Health England :– Blood Spot Screening Results– Newborn Physical Examination– Newborn Hearing Screening
openEHR CDA
13
GP2GP Record Transfer
• Working with GP2GP suppliers :– Allergies & Adverse Reactions– Blood Pressure– Document Metadata
openEHR HL7v3
14
GPSoC IM2 (Prototypes)
• Working with industry partners:– Appointments– Repeat Prescriptions
openEHR FHIR
15
Questions
• What are your priority data structures? • How do these align with what we are already
working on – how do we create synergies?
