connecting your software to the my health record system ... · conduct hi conformance tests. 7...

National E-Health Transition Authority www.nehta.gov.au1

Connecting your software to

the My Health Record system -

process and resources

Philip Wilford – Development and Technical Services Manager

Lars Becker – Manager, Integration Products

Odile Williams – Vendor Account Manager

Wednesday 3 February 2016

2 National E-Health Transition Authority

www.NEHTA.gov.au

Agenda

Welcome

Recap

Name Change

Part 1 – My Health Record Integration walk through Organisations working with you Key milestones and Resources

Prepare Design & Build Test & Go Live

Questions

Part 2 – Integration Resources Specification Integration Toolkit Template Package Clinical Package Validator Testing Environments Testing Resources

Questions

Thank you – Next Webinar and Webinar Survey


www.NEHTA.gov.au

Recap from previous webinar

Introduction to the My Health Record system delivered on 16 December 2015

Benefits of eHealth

Healthcare Identifiers (HI Service, HPI-Os, HPI-Is, IHIs)

National Authentication Service for Health (NASH) Public Key Infrastructure (PKI) certificates

Clinical Documents

PCEHR Views

The Introduction to the My Health Record system webinar recording is available on our website or through this link.

https://youtu.be/8jkPb9be_2k


www.NEHTA.gov.au

The ‘Personally Controlled Electronic Health Record’ (PCEHR) system has been renamed to the ‘My Health Record system’.

This name change has now been legislated, with the change to be reflected in the PCEHR system, as well as the new myhealthrecord.gov.au website (replacing ehealth.gov.au) and other communications.

Software vendors should now refer to the PCEHR system as the My Health Record system in day to day business activities.

PCEHR is changing its name to My Health Record.

https://myhealthrecord.gov.au/internet/ehealth/publishing.nsf/content/home


www.NEHTA.gov.au

The organisations working with you

My Health Record System Operator

System Owner

Approves production access to the My Health Record system

Assesses production issues

Vendor development [email protected]

Develops technical specifications

Maintains SNOMED CT-AU and AMT data sets

Vendor development support

Manages My Health Record Developer website

Department of HumanServices Online TechnicalSupport (OTS desk)

[email protected]

Operates Vendor Support Helpdesk for HI and My Health Record

Operates the test (HI SVT) and production HI Service

Performs the HI connectivity Notice of Connection (NOC) Tests.


www.NEHTA.gov.au

The organisations working with you

My Health Record National Infrastructure Operator (NIO)

[email protected]

Operates the testing (My Health Record SVT) and production My Health Record systems

Performs My Health Record connectivity (NOC) Tests.

NATA accredited test labs KJ Ross IV&V

Conduct HI conformance tests


www.NEHTA.gov.au

Healthcare Identifiers/My Health Record Connection testing

Healthcare Identifiers conformance testing by Test lab

Internal testing in preparation for Conformance, Compliance and Declaration

My Health Record Conformance Vendor Declaration form

-

3. Test and Go Live

1. Prepare

7

Pro

duction A

ccess

My Health Record integration –walk through

Healthcare Identifiers

My Health Record Software vendors

product details form

2. Design and Build Scenarios:

Access My Health Record system Upload to My Health Record system Assisted Registration


www.NEHTA.gov.au

Prepare – Healthcare Identifiers (HI)

1. Accept Licence agreement – Use of the Healthcare Identifiers licensed material (Department of Human Services web form)

2. Receive Logon ID and password from Department of Human Services

3. Review Healthcare Identifiers (HI) Documentation

Department of Human Services (Human Services) website:

HI B2B interface specifications

NEHTA website:

Conformance requirements

Use cases

Conformance test specifications

4. Build

5. Connect to the HI Software Vendor Test Environment (HI SVT)

6. Test

HI Connection (NOC) (Human Services OTS Liaison)

HI Conformance testing (NATA test lab)

7. Obtain HI production access letter


www.NEHTA.gov.au

Prepare – My Health Record system

1. Register for access to the My Health Record system [email Human Service Online Technical Support (OTS)]

2. Receive My Health Record system Welcome Pack from Human Services

3. Complete and return the My Health Record system Software Vendor Product Details Form and NASH PKI Test certificate kit application

4. Receive NASH PKI test certificate kit and NOC test pack from Human Services OTS

5. NIO to contact vendor regarding:a) Registration of test organisation assigned to the vendor to the

My Health Record SVT and b) My Health Record NOC testing process

6. Connect to the My Health Record SVT using test certificates


www.NEHTA.gov.au

Design & Build – My Health Record

My Health Record B2B specifications

My Health Record scenarios

Upload to My Health Record system Check if an advertised PCEHR exists Upload a clinical document Supersede a clinical document (not applicable for

Shared Health Summary) Remove a clinical document

Access My Health Record system

Check if an advertised PCEHR exists Gain access to PCEHR Download a clinical document

Assisted Registration

Assisted PCEHR registration of an adult Assisted PCEHR registration of a child


www.NEHTA.gov.au

Design & Build – Key Specifications

Uploading DocumentsPCEHR

Conformance Profile

Common Conformance

Profile

CDA Implementation

Guide

CDA Rendering Specification

CDA Package Specification

EACH doc typeALL doc typesPackaging


www.NEHTA.gov.au


Accessing Documents

All of the above

Plus specs for document views:

Common Conformance

Profile

PCEHR Conformance

Profile

CDA Implementation

Guide

EACH doc typeALL doc types

PCEHR

Conformance

Profile

Common

Conformance

Profile

CDA

Implementation

Guide

CDA Rendering

Specification

CDA Package

Specification


www.NEHTA.gov.au


Assisted Registration

PCEHR Connecting SystemsUse Cases

PCEHR Connecting SystemsConformance Requirements


www.NEHTA.gov.au

Formal Testing

Healthcare IdentifierService

Notice of Connection(NOC)

Department of Human Services –OTS [email protected]

Conformancetesting

NATA Accredited test labs Cost Involved Conformance test

specifications available on NEHTA website

My Health Record system

Notice of Connection (NOC)

My Health Record NIO [email protected]

Conformance Testing

Vendor self-assessmentVendor conformance declaration

NEHTA provides interpretation of: Test reports Clinical Package Validator

validation results

In-house testing Conformance Test

Specifications Clinical Package

Validator

mailto:[email protected]

mailto:[email protected]


www.NEHTA.gov.au

Production Access

The My Health Record System Operator will authorise your software product to access the My Health Record system when:

Your software product is approved for connection to the HI Service

Your software product passes the relevantconnectivity tests to the My Health Record system(NOC)

Your product passes your internal conformance testing

And you complete the My Health Record Conformance Vendor Declaration form.

National E-Health Transition Authority www.NEHTA.gov.au

Questions?


www.NEHTA.gov.au

Specifications (B2B, SCS and IGs)

Integration toolkits (sample code)

Template Packages

Clinical Package Validator (CPV)

Testing Environments

Integration Resources


www.NEHTA.gov.au

My Health Record B2B - LSS & TSS Record Access

Document Exchange

View Service

Registration Service

Clinical Document SCS and IGs (CDA) DS, Ref, SL, ES, SHS

Prescription, Dispense

CeHR

Consumer

Medicare

Path, DI

Design and Build - Specifications


www.NEHTA.gov.au

Integration toolkits (sample code)Example implementations of the specifications (in c# and java)

Healthcare Identifiers Integration Toolkit

Sample code to implement and connect to the B2B - HI Service

Clinical Documents Integration Toolkit

Sample code to build clinical documents

Sample code to package a clinical document

Style Sheet to render a clinical document (Generic, Prescription Dispense View)

Sample code to extract data from a clinical document

My Health Record system (PCEHR) Integration Toolkit

Sample code to implement and connect to the B2B - PCEHR Service

eHISC

Sample implementation of a Communications solution to the HI and the My Health Record system

Uses the above sample code

Integration toolkits


www.NEHTA.gov.au

What is a template package?

Where are they used?

Conformance Levels – 1A, 1B, 2, 3A, 3B

How to use them?

Where to get them from?

Template Packages


www.NEHTA.gov.au

Clinical Package Validator


www.NEHTA.gov.au

Clinical Package Validator (CPV)

What is it for?

Supports development of Clinical Documents and Clinical Packages

What does it do?

It validates (conforming to SCS,IG,CP) a

Clinical Documents and/or

Clinical Packages

Downloads and uses Template Packages

Validates against SNOMED, AMT, PBS Terminology (local DB)


www.NEHTA.gov.au

Testing Environments

Environments

HI SVT environment (managed by Department of Humans Services)

My Health Record SVT environment (managed by Accenture)

eHRP environment (managed by NEHTA)

What do you need?

Certificates

HI - Medicare Site Certificate

My Health Record/eHRP - NASH Certificate

HI SVT environment

Sample identifiers provided

My Health Record SVT environment

Test pack has identifiers provided

eHRP environment

Material provided with access


Questions?


www.NEHTA.gov.au

[email protected]

1300 901 001


Thank You!

Next Webinar: Early March

Topic: Access and view information in

the My Health Record system