getting smart about fhir part 2 · why do we need profiling? fhir provides a single set of...

30
Getting smart about FHIR – part 2 Michael Lawley Research Group Leader, AEHRC AUSTRALIAN E-HEALTH RESEARCH CENTRE

Upload: others

Post on 19-Aug-2020

2 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Getting smart about FHIR – part 2Michael Lawley

Research Group Leader, AEHRC

AUSTRALIAN E-HEALTH RESEARCH CENTRE

Page 2: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Profiling

Page 3: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Why do we need profiling?

FHIR provides a single set of Resources

Many usage contexts:• Jurisdictional boundaries

• Acute care, primary care, specialist care, …

• Scale: Patient-oriented use, cohort-use, population-level use

Few systems will ever implement the entire specification

Most clients will only use a subset of the specification

Page 4: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

FHIR Profiles

Describe adaptations based on use & context• Which resources & elements are used

• Which API features are used

• Which terminologies are used

• How to map these to local requirements

Computable• Publish, share, re-use

• Drive tooling: validation, conformance checking, code generation

Page 5: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

FHIR Conformance Resources

Terminology

CodeSystem

ValueSet

ConceptMap

NamingSystem

Content

StructureDefinition

ElementDefinition

StructureMap

DataElement

Operations

OperationDefinition

SearchParameter

Compartment-Definition

Misc.

CapabilityStatement

Implementation-Guide

TestScript

TestReport

Page 6: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

FHIR Conformance Resources

Terminology

CodeSystem

ValueSet

ConceptMap

NamingSystem

Content

StructureDefinition

ElementDefinition

StructureMap

DataElement

Operations

OperationDefinition

SearchParameter

Compartment-Definition

Misc.

CapabilityStatement

Implementation-Guide

TestScript

TestReport

Page 7: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

FHIR Conformance Resources

Terminology

CodeSystem

ValueSet

ConceptMap

NamingSystem

Content

StructureDefinition

ElementDefinition

StructureMap

DataElement

Operations

OperationDefinition

SearchParameter

Compartment-Definition

Misc.

CapabilityStatement

Implementation-Guide

TestScript

TestReport

Page 8: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

StructureDefinition

Defines data structures

Core datatypes

Core resources

Constraints on resources & datatypes

Extensions

Logical Models

Page 9: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

StructureDefinition

Defines data structures

Core datatypes

Core resources

Constraints on resources & datatypes

Extensions – additions to resources

Logical Models

Page 10: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

StructureDefinition - metadata

Canonical url

Name, Title

Status (draft, active)

Date, Version (author assigned)

Author, publisher, contact, ...

Base profile

Page 11: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

StructureDefinition - content

List of ElementDefinitions•Name, cardinality, data type

•Definitions, usage notes, requirements

•Default or fixed values

•Complex constraints, length limits

•Terminology bindings

•Mappings to other specifications

Page 12: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

ImplementationGuide

Defines scope of usage

Describes requirements for a FHIR implementation

Specifies links to• Relevant FHIR artifacts (e.g. profiles, other IGs)

• Editorial content (documentation)

Usage• Allow authors to publish an implementation guide

• Allow tools to validate conformance

Page 13: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Tooling

•Forgehttps://simplifier.net/forge/

•Lantana Trifolia Workbenchhttps://trifolia.lantanagroup.com/

•ClinFHIRhttp://clinfhir.com

•Manually author XML/JSON

•Excel (build tool)

Page 14: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

on FHIR

Page 15: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Substitutable Medical Apps, Reusable Technology

“An App Platform for Healthcare”

A set of specifications to integrate Apps with EHRsand other Health IT systems

Page 16: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,
Page 17: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Source: https://apps.smarthealthit.org/app/growth-chart (Boston Children’s Hospital)

Page 18: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Data: FHIR

Scopes and permissions: OAuth2

Simple authentication: OpenID Connect

Lightweight UI: HTML5

Page 19: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Scopes & permissions

patient/*.read

user/*.*

openid profile

launch

launch/patient

Page 20: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Launch

Launch from host system:GET https://{app_launch_url}?

launch=123&

iss={fhir_base_url}

App requests CapabilityStatement to determine OAuth2 endpoint details

App performs OAuth2 authorization for required scopes

Page 21: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

CDS-hooks

Page 22: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Trigger decision support from the EHR

CDS Service

Invoked by EHR using a hook

Evaluates own rules using FHIR data

Returns decision support via cards

Page 23: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Example hooks

patient-view•a patient’s chart is opened

medication-prescribe•a medication is selected for prescription

order-review•reviewing pending orders for signing

Page 24: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Context and pre-fetch

Context•e.g., current patientId, encounterId, etc

Prefetch•e.g., the actual MedicationOrder

Page 25: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Cards

Information•Text for the user to read

Suggestion•Options for the user to choose between

App link•Link to an App (eg SMART) for more complex interactions

Page 26: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,
Page 27: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Example - https://example.com/cds-services

{

"services": [{

"hook": "medication-prescribe",

"title": "Medication Brand Substitution CDS Service",

"description": "An example CDS Service that offers other brands

of the medication being prescribed",

"id": "medication-echo",

"prefetch": {

"patient": "Patient/{{context.patientId}}",

"medications": "MedicationOrder?patient={{context.patientId}}”

}

}]

}

Page 28: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

FHIR & the Open Community

FHIR is disrupting healthcare IT & healthcare:

• Encouraging the development of open community

• Significantly reducing the cost of data exchange

• Creating new economies of scale and methods of engagement

• Building a solid base to scale healthcare analytics and application

Join our open community – or another one…

Page 29: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

Q & A

Page 30: Getting smart about FHIR part 2 · Why do we need profiling? FHIR provides a single set of Resources Many usage contexts: •Jurisdictional boundaries •Acute care, primary care,

More FHIR

The National Children’s DigitalHealth Collaborative

Mon 2:35-3:20, C2.2/3

MSIA Engagement Forum:FHIR State of the Nation

Tue 2:00-3:30, Pyrmont Theatre

AEHRC