Ross McKenna Information Directorate Ministry of Health, New Zealand www.moh.govt.nz IHE and Connected Health in New Zealand
Agenda <ul><li>What/who needs connecting to what/who? </li></ul><ul><li>Where does IHE fit? </li></ul><ul><li>New Networki...
Potential collaboration across market segments
 
What is “connected health”? <ul><li>Sector-wide collaborative patient care </li></ul><ul><li>“ Islands” of Information joi...
Through; people,  process  and  technology…
Enablers for a connected Health Sector Vendor Development  & Supply Key data elements NHI, HPI  Terminology  and coding He...
The roadmap… <ul><li>2005 HISAC AZ 1 National network strategy </li></ul><ul><li>2006 Phase 1  Planning (NGHN) </li></ul><...
Connected Health Programme <ul><li>The  Imperative for Change: </li></ul><ul><li>Inability to share and access health data...
The Integration Pyramid Interoperability High Level Architecture Standards Framework Typical Designs Specific Designs IHE ...
High Level  Architecture
Connected Health Architectural Framework Network-to-Network Interface. This interface will only be used by Telecommunicati...
Architecture Overview <ul><li>Wireless LAN (WLAN) </li></ul><ul><li>Direct Connections </li></ul><ul><li>Virtual LAN (VLAN...
With interconnected networks , interoperable applications and standards applied consistently across the health system…  Ho...
Applying Connected Health Standards and Architecture VPN Established VPN  Example 1:  GP establishes VPN Link to the “heal...
Applying Connected Health Standards and Architecture VPN  GP identify verified using HPI through the “connected.health.nz”...
and on the GP’s screen… Applying Connected Health Standards and Architecture  through a web portal
VPN Established VPN  Applying Connected Health Standards and Architecture  + XDS (IHE) GP can view test results
Applying Connected Health Standards and Architecture  with full application interoperability and ESB VPN  Converts message...
Summary <ul><li>The health system is probably not one </li></ul><ul><li>It will take more than just technology </li></ul><...
Upcoming SlideShare
Loading in...5
×

IHE and Connected Health in New Zealand

866

Published on

Ross McKenna
Information Directorate
Ministry of Health, New Zealand
IHE and Connected Health in New Zealand

Published in: Technology, Health & Medicine
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
866
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Transcript of "IHE and Connected Health in New Zealand"

  1. 1. Ross McKenna Information Directorate Ministry of Health, New Zealand www.moh.govt.nz IHE and Connected Health in New Zealand
  2. 2. Agenda <ul><li>What/who needs connecting to what/who? </li></ul><ul><li>Where does IHE fit? </li></ul><ul><li>New Networking and Interoperability capabilities for the NZ Health System </li></ul><ul><li>Example of a practical application to clinical workflow </li></ul>
  3. 3. Potential collaboration across market segments
  4. 5. What is “connected health”? <ul><li>Sector-wide collaborative patient care </li></ul><ul><li>“ Islands” of Information joined up </li></ul><ul><li>National approach to information sharing </li></ul><ul><ul><li>National reference standards on connectivity & interoperability </li></ul></ul>Some general principles… How do we achieve it?
  5. 6. Through; people, process and technology…
  6. 7. Enablers for a connected Health Sector Vendor Development & Supply Key data elements NHI, HPI Terminology and coding Health records – security, storage, reference, retrieval Adoption and application of health information standards Telecommunications infrastructure capability - Interoperability - Application access ..nationally agreed and nationally referenced
  7. 8. The roadmap… <ul><li>2005 HISAC AZ 1 National network strategy </li></ul><ul><li>2006 Phase 1 Planning (NGHN) </li></ul><ul><li>2007/8 Phase 2 Design (Connected Health) </li></ul><ul><li>2008/9 Phase 3 Implementation </li></ul><ul><li>2009/10 Phase 4 Consolidation </li></ul>Telecommunications infrastructure capability - Interoperability - Application access
  8. 9. Connected Health Programme <ul><li>The Imperative for Change: </li></ul><ul><li>Inability to share and access health data electronically reduces the effectiveness of health care delivery </li></ul><ul><li>The next steps in 2008/09: </li></ul><ul><li>Core networking infrastructure components for the entire health system </li></ul><ul><li>Reference Architecture, Interoperability and Security Standards </li></ul><ul><li>A new second level domain for health providers </li></ul><ul><li>Information sharing and interoperability are proven by pilots </li></ul><ul><li>The Payoff: </li></ul><ul><li>A foundation for significant national improvements in collaborative care delivery and reduction in heath care risks by enabling secure information sharing </li></ul>
  9. 10. The Integration Pyramid Interoperability High Level Architecture Standards Framework Typical Designs Specific Designs IHE Industry provided Connected Health supported
  10. 11. High Level Architecture
  11. 12. Connected Health Architectural Framework Network-to-Network Interface. This interface will only be used by Telecommunications Service Providers (TSPs) and covers the Interconnection points between IP carrier networks. NNI-1 and NNI-2 defined This is the User-to-Network Interface definition. This covers the physical and logical IP connectivity to the network from one of the end-points UNI-0 to UNI-5 are defined This is the System-Interface definition. This covers the connections of equipment (servers, workstations etc) to the UNI. SI-0 to SI-6 are defined
  12. 13. Architecture Overview <ul><li>Wireless LAN (WLAN) </li></ul><ul><li>Direct Connections </li></ul><ul><li>Virtual LAN (VLAN) </li></ul><ul><li>Mobile </li></ul><ul><li>Static IP Address </li></ul><ul><li>Routing </li></ul><ul><li>Version of IP </li></ul><ul><li>DNS </li></ul><ul><li>TSP Interconnections </li></ul><ul><li>Quality of Service (QoS) </li></ul><ul><li>DNS </li></ul><ul><li>DHCP </li></ul><ul><li>NTP </li></ul><ul><li>HL7 </li></ul><ul><li>Message Hub </li></ul><ul><li>Message Spoke </li></ul><ul><li>SSL/TLS </li></ul><ul><li>Web Services </li></ul><ul><li>Authentication/Authorisation </li></ul>SI 0-6
  13. 14. With interconnected networks , interoperable applications and standards applied consistently across the health system… How would a GP get instant access to a lab test result?
  14. 15. Applying Connected Health Standards and Architecture VPN Established VPN Example 1: GP establishes VPN Link to the “health.nz” domain Switch On
  15. 16. Applying Connected Health Standards and Architecture VPN GP identify verified using HPI through the “connected.health.nz” domain
  16. 17. and on the GP’s screen… Applying Connected Health Standards and Architecture through a web portal
  17. 18. VPN Established VPN Applying Connected Health Standards and Architecture + XDS (IHE) GP can view test results
  18. 19. Applying Connected Health Standards and Architecture with full application interoperability and ESB VPN Converts message to lab format and redirects PMS Application Converts message back to PMS Application format and redirects Test results modify treatment plan
  19. 20. Summary <ul><li>The health system is probably not one </li></ul><ul><li>It will take more than just technology </li></ul><ul><li>A lot of good work is being done but there is a lack of national leadership/approach/picture </li></ul><ul><li>Architecture and standards to enable national connectivity advances are progressing </li></ul><ul><li>Pilots will be established but suppliers and participants in the health system need to all support a national view for wide integration/collaboration benefits </li></ul>

×