How HL7 UK is supporting implementation of healthcare messaging Philip Scott MSc MBCS CITP Head of IT Projects & Development Portsmouth Hospitals NHS Trust PhD student, University of Portsmouth HL7 UK board member Co-chair, HL7 UK NHS Implementers group BCS Health Informatics Forum – 25 April 2006
24
Embed
How HL7 UK is supporting implementation of healthcare messaging
BCS Health Informatics Forum – 25 April 2006. How HL7 UK is supporting implementation of healthcare messaging. Philip Scott MSc MBCS CITP Head of IT Projects & Development Portsmouth Hospitals NHS Trust PhD student, University of Portsmouth HL7 UK board member - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
How HL7 UK is supporting implementation of healthcare
messaging
Philip Scott MSc MBCS CITPHead of IT Projects & Development
Portsmouth Hospitals NHS Trust
PhD student, University of Portsmouth
HL7 UK board memberCo-chair, HL7 UK NHS Implementers group
BCS Health Informatics Forum – 25 April 2006
Topics• Brief history of HL7
• Summary of v2 v3
• HL7 UK purpose, activities, relationships
• NHS implementation support
• Future issues
• Questions
But… this is NOT an HL7 tutorial• See www.hl7.org.uk for training providers and web
When you’ve seen one HL7 v2 interface,you’ve seen one HL7 v2 interface!
“Rampant optionality”
Standards are great,let’s all have one!
Let there be v3…• Reference Information Model (RIM)
• Abstract cross-domain information model
Refinement from RIM to Message
HL7 UK purpose, activities, relationships• Mission statement
To support the development, promotion and implementation of HL7 standards in ways which meet the needs of healthcare organisations, health professionals and healthcare software suppliers in the United Kingdom
• 4-5 working meetings each year (next June 13-14)• Subgroups on v2, v3 domains, implementation• UK representation on .org SIGs/TCs• Strong NPfIT representation and contribution• Relationships with Intellect, IST/35• Cultivating relationships with IHE, IHC
HL7 UK purpose, activities, relationships• NPfIT Message Implementation Manual (MIM)
available to members via HL7 UK web site
NHS implementation support• NPfIT presentations in working meeting plenaries
• Annual HL7 Conference (next 25-26 October)
• NHS Implementers Group– Seminars in Feb 2005 and Feb 2006– Workshops on:
• Interface project management and technical issues• Integration engines• LSP local interface standardisation
– Subgroup session at each HL7 UK working meeting
NHS implementation support
Charter:• The NHS Implementers sub-group exists to
address the needs of those who need to implement HL7 specifications in the UK. Our aspiration is to build a UK HL7 self-help community.
• This includes:– raising awareness of the services and
information available from HL7 UK – signposting reference and training sources – facilitating liaison between NHS implementers,
suppliers and standards developers.
NHS implementation support
Charter:• The NHS Implementers sub-group exists to
address the needs of those who need to implement HL7 specifications in the UK. Our aspiration is to build a UK HL7 self-help community.
• This includes:– raising awareness of the services and
information available from HL7 UK – signposting reference and training sources – facilitating liaison between NHS implementers,
suppliers and standards developers.
NHS implementation support• A current issue: LSP standardisation
NHS implementation support• Pragmatic commercial reality rather than “ruthless
standardisation”
• Accenture/CSC: UK vA.2, v2.3, v2.4
• BT: UK A.2?
• Fujitsu: v2.3
• Which v2.3? Which v2.4? Which UK A.2?
• Issues:– Maintenance: no re-use possible, upgrades complex– Risk of varying semantics or data quality workarounds– Cross-boundary flows: specialty systems, cancer
networks, ISTCs
GP Lab 1v3 request/report
Lab 2
PMIPGP using two labs may receive PMIP and v3
Specialty
v2.4 UK A.2 report
v2.3 report
Specialty system using two labs may receive two kinds of v2
Each translation point adds maintenance and risk of error