Dr.David Hay | Orion Health Product Strategist, FHIR Evangelist, Chair Emeritus HL7 NZ

clinFHIR / conMan:

A tool for clinicians and business

analysts

HIC | July 2018

Page 2 • 2017 © Orion Health™ group of companies

Inspiration

▸ We want clinicians involved in health care IT projects

▸ But: Information Technology is hard!

▸ FHIR makes it easier, but not enough

▸ ClinFHIR and ConMan tooling to help address this

– Education

– Design support

Page 3 • 2017 © Orion Health™ group of companies

Key parts of FHIR for a Clinician

‣ Resources & Profiles

‣ References between resources

‣ Terminology

‣ Exchange Paradigms

‣ Other uses

‣ Decision Support, Quality Measures

‣ Associated standards

‣ SMART

‣ CDS-Hooks

‣ FHIR Cast

‣ The Community

Page 4 • 2017 © Orion Health™ group of companies

Proposed process for designing project artifacts in FHIR

1. Gather Requirements

2. Create reference architecture

3. Create Information Models/s

4. Validate Information models

5. Create FHIR artifacts (including Implementation Guide)

6. Connectathon

7. Review and update models

8. Publish

Example using New Zealand Adverse

Reactions project

Page 5 • 2017 © Orion Health™ group of companies

Clinical problem

▸ Adverse Drug Reactions (ADR) constitute a major source of morbidity and mortality

within New Zealand.

▸ The current level of ADR reporting to CARM (Centre for Adverse Reaction Monitoring)

in NZ is estimated at 2% of all ADRs.

▸ ADR alerts for individual patients are currently siloed within a range of disparate PMS,

EMR, EHR systems which are unable to effectively share this importantly safety

information

▸ Need to:

– Make it easy to collect Adverse Reactions in shared repository

– Make available at Point Of Care

– Support Reporting / Analytics

– Enable Automated Decision Support

– Allow any author to submit report

Page 6 • 2017 © Orion Health™ group of companies

1. Requirements: Scenario

Page 7 • 2017 © Orion Health™ group of companies

2. Architecture

Page 8 • 2017 © Orion Health™ group of companies

3. Information model: Designer

Page 9 • 2017 © Orion Health™ group of companies

3. Information Model: Table

Page 10 • 2017 © Orion Health™ group of companies

4. Validate model: Form

Page 11 • 2017 © Orion Health™ group of companies

4. Validate model: Notes and Comments

Page 12 • 2017 © Orion Health™ group of companies

5. FHIR Artifacts: ConMan resources (scenario) Graph

Page 13 • 2017 © Orion Health™ group of companies

6. Connectathon

Page 14 • 2017 © Orion Health™ group of companies

Finishing up…

▸ FHIR makes interoperability easier…

– But it is still hard

– We need clinicians

• And clinicians need education and tooling

▸ Tomorrow:

– Implementing with an Ecosystem approach

Page 15 • 2017 © Orion Health™ group of companies

Thank you!