Phase 3: eLTSS HL7 FHIR Implementation Guide (Nov 2018 - Ongoing)

• September 2018 – January 2019: Balloted the Informative Document, conducted disposition on all comments collected from ballot, and updated the eLTSS Informative Document to reflect comment dispositions
• January 2019: Submitted revised Informative Document to HL7 for publication
• February 2019: Informative Document was officially published by HL7 at:  http://www.hl7.org/implement/standards/product_brief.cfm?product_id=495 
• January – May 2019: Developed the eLTSS FHIR Implementation Guide (IG) and received all necessary HL7 approvals to be included in the May 2019 ballot
• May – September 2019: Reconciled IG ballot comments and update the IG accordingly; HL7 published the eLTSS FHIR IG at: http://hl7.org/fhir/us/eltss/
• September 2019: Tested the eLTSS IG in conjunction with community stakeholders at the September 2019 HL7 Connectathon
• September 2019: eLTSS FHIR IG published by HL7 http://hl7.org/fhir/us/eltss/
• February 2020: eLTSS Reference Implementation posted to ONC GitHub https://github.com/onc-healthit/eLTSS-Reference-Implementation
• May 2020: eLTSS FHIR IG tested by the PACIO - eLTSS Track at the HL7 May 2020 Connectathon
• August 2020: HL7 CBCP Workgroup approves an STU Update of the FHIR IG
• September 2020: eLTSS IG tested by the PACIO-eLTSS Track at the HL7 September 2020 Connectathon
• Ongoing - Continue the testing and piloting of the IG; document and submit possible IG updates to the HL7 CBCP WG

Phase 2: Initial Implementer Guidance (Nov 2017 - Sep 2018)

• The Georgia Team (Georgia Department of Community Health (DCH) and Georgia Tech Research Institute (GTRI)) and ONC Support team (ESAC, Carradora) with subject matter input from representatives from Minnesota, Connecticut and Colorado developed and submitted the “HL7 Cross-Paradigm Information Sharing for Electronic Long-Term Services & Supports (eLTSS), Release 1” Informative Document for the September 2018 balloting cycle 

• Mapped the eLTSS Dataset to HL7's FHIR standard
• Mapped the eLTSS Dataset to HL7's C-CDA standard
• Key Outcomes:

  • Ability to support electronic piloting of eLTSS data exchange: The informative document includes robust technical details specifying how to leverage Health IT content standards (FHIR and C-CDA) to support electronic exchange of the eLTSS Dataset. This serves as a key prerequisite for supporting electronic piloting activities by implementers of software solutions in the LTSS ecosystem.

  • Socialization of LTSS use cases, data elements and workflows with the broader HL7 community with an aim towards informing the standards development processes to be inclusive of both clinical and LTSS perspectives.

Phase 1: eLTSS Dataset (Nov 2014 - Nov 2017)

• Published the eLTSS Dataset and Summary: September 2017
  • Key Outcomes: 
  • • The eLTSS Dataset serves as the first step in enabling data-level electronic interoperability for LTSS
    • Identifies and documents an initial set of data requirements needed to support data-level electronic exchange of LTSS Service Plans.
      

• Pilots and Testing (Round 2): November 2016 to November 2017 

  • Test and validate working draft eLTSS Dataset

  • Test Use Case user stories and scenarios
  • Monitor progress and outcomes
  • Utilize Requirements Traceability Matrix

  • Implementation guidance balloting with Standards Development Organization

  • Implementation guidance publication (national standard) and piloting

• Pilot Evaluation Round 1 : May 2016 to October 2016

  • Evaluate outcomes against success metrics and criteria
  • Pilot Guidance updates based on pilot evaluation

• Pilots and Testing Round 1: October 2015 to April 2016 (minimum 6 month pilot period)

  • Pilot site readiness
  • Identify working draft eLTSS Dataset
  • Monitor progress and outcomes

• Pilot Guide Development: April 2015 to October 2015

  • Finalize candidate standards
  • Standards gap analysis
  • Technical and standards design
  • Develop Requirements Traceability Matrix (RTM)

• Use Case Development and Functional Requirements: January 2015 to March 2015

  • Develop, review, and finalize the Use Case and Functional Requirements

• Pre-Discovery: November 2014 to January 2015

  • Launch initiative

  • Review and finalize Project Charter

  • Review initial candidate standard