This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "FHIR: Enhancing Implementation (ONC Grant Project)"

From HL7Wiki
Jump to navigation Jump to search
Line 14: Line 14:
 
#'''Project: Unified Terminology Governance Process (UTG); Working Prototype '''
 
#'''Project: Unified Terminology Governance Process (UTG); Working Prototype '''
 
#*''Project Description: ''1. Develop a working UTG prototype that further develops the current Proof of Concept (PoC) demonstration including the FHIR toolkit and Terminology Server, and use of JIRA/Confluence workflow) that includes the following capabilities:
 
#*''Project Description: ''1. Develop a working UTG prototype that further develops the current Proof of Concept (PoC) demonstration including the FHIR toolkit and Terminology Server, and use of JIRA/Confluence workflow) that includes the following capabilities:
#**Creation of sample Complete Harmonization Proposal(s) for any of the following (or any combination of following):
+
#**Creation of sample Complete Harmonization Proposal(s) for any of the following (or any combination of following): V3 vocabulary, V2 vocabulary, FHIR vocabulary, CCDA vocabulary (demonstrate all state transitions in the Workflow, with all screens to manage and document functions) consistent with UTG Functional Requirements
V3 vocabulary, V2 vocabulary, FHIR vocabulary, CCDA vocabulary (demonstrate all state transitions in the Workflow, with all screens to manage and document functions) consistent with UTG Functional Requirements
 
 
#**Editing existing Draft Harmonization Proposal(s)
 
#**Editing existing Draft Harmonization Proposal(s)
 
#**Submitting Harmonization Proposal(s) for Consensus approval (or abandonment)
 
#**Submitting Harmonization Proposal(s) for Consensus approval (or abandonment)

Revision as of 17:04, 4 April 2018

Return to the HL7 wiki Main Page.
Return to the ONC Grant Project Page

Overview

This page supports the FHIR projects occurring within the ONC Grant funded opportunities:

  • Enhancing C-CDA and FHIR Implementation (2015 - 2017)
  • Maturing C-CDA and FHIR Implementation (2018 - )

The collaboration encompasses the following projects to support a grant awarded to HL7 by the Office of the National Coordinator for Health Information Technology (ONC).

Deliverables from the Maturing C-CDA and FHIR Implementation (2018 - ) projects are below.

  1. Project: Unified Terminology Governance Process (UTG); Working Prototype
    • Project Description: 1. Develop a working UTG prototype that further develops the current Proof of Concept (PoC) demonstration including the FHIR toolkit and Terminology Server, and use of JIRA/Confluence workflow) that includes the following capabilities:
      • Creation of sample Complete Harmonization Proposal(s) for any of the following (or any combination of following): V3 vocabulary, V2 vocabulary, FHIR vocabulary, CCDA vocabulary (demonstrate all state transitions in the Workflow, with all screens to manage and document functions) consistent with UTG Functional Requirements
      • Editing existing Draft Harmonization Proposal(s)
      • Submitting Harmonization Proposal(s) for Consensus approval (or abandonment)
      • Auto and Manual Validate Proposals (show Pass and Fail paths)
      • Integration with Confluence for Consensus Discussions
      • Ability to gather votes for approval/rejection
      • Ability to triage Submitted Proposal as per Consensus Decision (Approve, Reject, Controversial, Withdraw, Rework)
      • Ability to process Approved Proposal into Terminology Store; document and enable new release
      • Enabling on-demand extract of any value set
      • Output of terms in V3, CCDA, and V2 vocabulary in publishable form (coremif, Trifolia or Art Decor input format, V2 tools input format)
      • Management of Active Proposals
      • Management of Permissions for Submitters and Consensus Pool
  2. Project: FHIR Ballot Process & Tooling
    • Project Description: Leveraging Confluence and JIRA, design and implement a new ballot management and reconciliation process and tooling.
    1. Deliverable: HL7’s Proposed Revised Ballot Process
      • The new process will improve reliability and support consistency between how feedback is delivered during ballot and during STU and periods between ballot cycles. It will also provide increased transparency around the reconciliation process and give participants easier ways of exploring what feedback has been provided and what decisions are in the process of being made about that feedback.
  3. Project: FHIR Bulk Data Access & Push Projects
    • Project Description: Add new capabilities to the FHIR specification to increase support for API-based access and push of data for large number of patients in support of provider-based exchange, analytics and other value-based services; upgrade existing FHIR reference server implementations to more effectively support “Bulk Access and Push” applications.
    1. Deliverable: January 2018 FHIR Connectathon Report
    2. Deliverable: Draft Implementation Guide
    3. Deliverable: Improvements discussed to the SMART Reference Implementation to support changes discussed at the January 2018 FHIR Connectathon and more reliable performance on very large dataset
    4. Deliverable: Initial work with Grahame on extracting the core of the bulk data approach into FHIR primitives
    5. Deliverable: Ongoing discussion with the community around how to name the operation and other implementation details
  4. Project: FHIR Connectathon Administrator
    • Project Description: Fulfill the roles and responsibilities of the FHIR Connectathon Administrator to maximize participant experience and outcomes, and produce the following deliverables:
      • FHIR Connectathon Communication Plan
      • Pre-Connectathon Survey for Participants
      • Post-Connectathon Satisfaction Survey
      • Orientation Package for all Track Leads
      • Event Report within one week of the FHIR Connectathon event
  5. Project: Support for FHIR R4 Ballot Processing
    • Project Description: Provide a quality review and pre-processing of the ballot comment spreadsheets for the April 2018 FHIR R4 ballot and facilitate loading them into gForge so comments can be expeditiously reconciled and resolved by the committees. Primary tasks include:
      • Upon close of the FHIR-related ballots at midnight eastern time end of day Monday May 7, begin processing the FHIR ballot responses in the following order:
        • Normative ballots first
        • FHIR Core STU ballot second
        • STU Implementation Guide (IG) ballots third
        • Draft IG ballots fourth
      • For each set of submitted contents, perform the steps identified in http://confluence.hl7.org/display/HL7/Process+for+Importing+Ballot+Spreadsheets+to+gForge
      • While it is difficult to know in advance how many line items of comments will be received, we expect on the order of 2000 lines of comments across all of the ballots
      • Objective is to have this process complete for all IGs by end of day Sunday May 12 prior to the official beginning of the May 2018 WGM.
      • The ballots must be completed sequentially, not in parallel, as there's a need for high-priority ballots to perform additional triaging prior to loading content into gForge after the clean-up process is complete.


Deliverables from the Enhancing C-CDA and FHIR Implementation (2015 - 2017) projects are below.

  1. Project: FHIR Repository Process
    1. Deliverable: HL7 FHIR Repository Governance, Process and Requirements, Release 1 - August 2017 - This Guide establishes the governance, process and requirements to manage FHIR artifacts in a repository / registry that is accessible to all users. The goal is to ensure the quality and availability of FHIR artifacts and support adoption of FHIR by the healthcare community and regulators.
  2. Project: FHIR Registry Prototype
    1. Deliverable: Beta version of https://registry.fhir.org/
  3. Project: Standardize FHIR Info Models/Transform CIMI Core Logical Models to FHIR Profiles
    1. Deliverable: Documentation:
      1. ClinicalModelingPrimmer.pdf – A document defining Clinical Modeling terms and Synonyms in use. Target audience is clinical subject matter experts that have never modeled before. Revisions will be made available here.
      2. ModelRequestProcess.pdf – A guide detailing out the process for preparing and submitting clinical content that can be standardized and used among and across settings. Target audience is clinical subject matter experts that have never modeled before
      3. ModelRequestSpreadsheetTemplate.xlsx – A template document [with examples] cited in the model request process. This aids the process of organized note taking for clinical subject matters in extracting and documenting the fundamental truths a.k.a data elements related to a clinical topic or a use case.
      4. CIMI and FHIR Tooling Road-Map.pdf – A draft of proposed tooling road-map for the larger CIMI team to discuss and consider during the HL7 plenary meetings in September’ 2017. Revisions will be made available here.
      5. Transforming CIMI core logical models to FHIR profiles - Cognitive Medical Systems Deliverable Report
    2. Deliverable: Content
      1. ONCGrant_FHIR Profiles.zip - FHIR profiles in their XML form. This set contains FHIR profiles for one of each type– Coded, Ordinal and Nominal Labs. 2623 total LOINC codes were addressed, of which 1555 required new CEM models. The CEM models are all created and we continue to work to develop the corresponding FHIR profiles for them all.
      2. ONCGrant_CrossWalk_LOINCLabs_FHIR Profiles.xlsx – Crosswalk document that maps data elements from LOINC to the FHIR data elements, along with a reference to it’s FHIR XML, LOINC codes, VSAC codes, CEM etc.
        1. A subsequent version of this artifact will contain a complete set of FHIR profiles corresponding to the LOINC codes addressed.
  4. Project: FHIR Tools Profile Roadmap
    1. The tooling roadmap is here: http://wiki.hl7.org/index.php?title=FHIR_Tooling_Eco-system.
    2. Registry Requirements Analysis / Registry Gap Assessment - Gevity Consulting Deliverable
    3. Deliverable Documentation: FHIR Core
      1. During the period from May 2017 to September 2017, the FHIR core infrastructure was subject to ongoing maintenance throughout the period. The FHIR code infrastructure includes the following:
        1. the main FHIR build process for the specification itself
        2. the IG publisher
        3. the java validator
        4. tx.fhir.org terminology service
      2. Though these tools are primarily provided for the generation of the published specifications, where ever it is possible for the tools to provide services that are relevant to implementers, they are moved into their own module so these services are available. This means that the tools - and their viability - are tied to implementation success.
        1. Links:
          1. build process documentation: http://wiki.hl7.org/index.php?title=FHIR_Build_Process
          2. gForge: https://gforge.hl7.org/gf/project/fhir
          3. terminology server: http://tx.fhir.org
    4. Deliverable Documentation: IG Publisher
      1. During the period from May 2017 to September 2017, we undertook substantial rework of the FHIR IG Publisher so that it would be possible to run it as a web server rather than as a batch file. The principle purpose of this work is to allow the IG publisher to be used to serve website tools that publish implemetnation guides, the most important of which is the FHIR registry eco-system. The idea is that a web site will provide authoring services, and then use the web services provided to by the IG publisher to actually produce the publication content.
      2. The fundamental problem the work faced was that the IG publisher was structured so that the project was loaded, the configuration analysed, and then all the dependency content was loaded - a process that could take up to a minute. In order to rework the build process so that it was suitable for use as a web service, the code had to be re-organised to be both thread safe and for the large resource dependencies (internal and external terminology servers, conformance service) to be loaded in advance. Most of the work was under the cover improvements around the code structure.
      3. The outcome is a web process that re-uses the same code base as the IG publisher command line version, but can be invoked across the web.
        1. Links:
          1. IG Publisher server: http://hapi.fhir.org/igweb (not functional yet)
          2. Documentation: http://wiki.hl7.org/index.php?title=IG_Publisher_Documentation#Using_the_IG_Publisher_Web_Server
          3. source code: https://gforge.hl7.org/svn/fhir/trunk/build/tools/java/org.hl7.fhir.igweb