Bob Dieterle

Alix Goss

Alex Kontur

Dan Chaput

Ed Martin

Mark Savage

Tim Young

Rick Geimer

Karl Davis

Pavel Smirnov

 

Anti-trust notice: Being a group of collaborators/competitors, we have to be mindful about not sharing proprietary information

 

P2 FHIR Taskforce Overview

  • Trying to solve an ecosystem/infrastructure problem à how do we scale things that work well in connectathons/pilots to the national level; how do make something that is universally and uniformly adopted?; How do we address those things that will create barriers to the adoption of FHIR-based solutions at the national level?
  • Solutions may be standards-based, best practice-based, or some combination
  • Want to create a knowledge-sharing process with the broader community
  • Will use demonstration projects to test learnings/outcomes and identify unexpected gaps/consequences

 

FHIR adoption barriers:

  • How to find endpoints
  • How to manage identity/identification
  • How to ensure security (and trust)
  • How to deal with testing/conformance/certification

 

Task Force comprised of federal and commercial stakeholders provides overall guidance/direction to Tiger Teams

  • Architectural effort spans across all Tiger Teams
  • Use Cases Tiger Team defines some of the inputs (i.e. information requirements necessary to support use cases) into other tiger teams
  • Sr. executive steering committee will meet periodically to provide guidance and promote outcomes

 

General information flow: Information requirements (from use cases Tiger Team) à detailed specifications (from other tiger teams) à testing/certification à implementation guides à pilots

 

Current Status:

Use case tiger team kicked off approximately 1.5 months ago

Identity, Directory, Exchange process, and pilot tiger teams all launched within the last couple of weeks

 

Each Tiger Team has ~6-8 members, 1-2 co-chairs, and an ONC staff support person

 

P2 FHIR Task Force vs. Da Vinci Project

  • Focused on addressing value-based care exchange
    • Defining the “vehicles” that drive on the “highway” developed by the P2 FHIR Taskforce
    • Da Vinci is addressing particular use cases, while P2 FHIR is addressing content that applies across all use cases
    • Da Vinci defines content, P2 FHIR defines scaling infrastructure
  • Different convener (HL7), but some overlap in participants

 

Karl Davis – There is a similar effort led by the CARIN Alliance, but not anticipating there will be much overlap

 

Directory Tiger Team

Problems to address:

  • Identifying FHIR endpoints & services – how can payers/providers identify appropriate endpoints and services for provider-payer exchange?
  • Managing multiple versions of FHIR – managing multiple versions of endpoints and artifacts (i.e. resource instances)
    • Growing interest in taking what an entity has received in v2 and exchanging it along with information represented in v3
    • Geimer – FHIR Infrastructure WG has decided to define a mechanism for FHIR resources to indicate which version of FHIR they use
  • Scaling ecosystem – How do we take things that work on a small, local scale and scale them?
    • Solutions must be capable of working on the scale of millions of transactions across thousands of endpoints

 

General approach:

  • Review current available solutions
  • Review existing standards
  • Discuss best practices in industry
  • Set vision
  • Define roadmap to achieve vision

 

Identified issues that fall outside the scope of the Tiger Team will be passed up to the Architecture Tiger Team, which will consider them and/or share them with the appropriate Tiger Team

  • Architecture Tiger Team will also consider requirements identified by the Use Cases Tiger Team and route those to the appropriate Tiger Team
  • Note: this is an evolving effort and processes are still being developed

 

Logistics

 

Next Steps

  • General discussion/brainstorming about deliverables at next meeting (July 12)
  • Complete brainstorming process by July 26
  • P2 working session at ONC’s August Interoperability Forum (primarily for coordinating committee/Task Force members)
    • Report out from attendees on August 9
  • No labels