Skip to end of metadata
Go to start of metadata

This page provides information about the project and expected timelines. 

Tasks Required for UTG Go Live

Open Issues and Deficiencies in UTG Tooling

Executive Project Progress Report

Participating in UTG Content Testing

Participating in UTG Pilot Testing

Scope

The project scope statement (PSS) was approved by all co-sponsors at the San Antonio WGM the week of January 16, 2017. It was forwarded to FTSD for approval on January 20, 2017. The document may be directly downloaded from UTG PSS V1. 

Project Milestones 2020

  • Development Cycle 4 and System Test
    • Development Cycle 4 dedicated to release-related development, educational and rollout materials, tooling fixes, and any requirements from February WGM
    • First release of UTG content scheduled for end of March
    • Perform limited pilot testing as proof of concept in April in preparation for May ballot ballot cycle
    • Perform system testing in preparation for demo production rollout

Immediate Priority Timelines for Development Cycle 4 (2/8/20 - 5/16/20)

TaskTimelineStatus
Identify UAT Testers for content testingSydney WGMDONE - 4 content testers to participate (in addition to UTG team), more always welcome!
Create materials for content testingLate-FebruaryIN PROGRESS - see Participating in UTG Content Testing
Perform content testingEarly-March
Identify May Ballot SubmittersEarly-MarchCraig Newman has submission
Clean up content per content testing resultsMid-March
Publish Initial Release (2.0.0) of UTG ContentEnd of March
Perform Tooling and Workflow TestingEarly-April
Run Pilot for May ballot contentApril-May

If you are interested in testing UTG content, please see Participating in UTG Content Testing.

If you are interested in participating in the UTG Pilot testing, please see Participating in UTG Pilot Testing

See Tasks Required for UTG Go Live for a complete list of tasks that need to be completed prior to the May WGM.

Project Milestones 2019

  • Development Cycle 1 and May WGM (complete)
    • Complete harmonization functionality for demonstration at the WGM
    • Includes Source of Truth, tooling, and workflow
  • Development Cycle 2 and Alpha Testing (complete)
    • Development Cycle 2 dedicated to submitter and reviewer workflows and any requirements from May WGM
    • Alpha Testing to run alongside Development Cycle 2
    • Harmonization utilizing UTG tooling and workflow to run alongside current Harmonization process 
  • Development Cycle 3 (complete)
    • Development Cycle 3 dedicated to release-related development and any requirements from September WGM
    • Complete final cleanup from Alpha Test
    • Perform testing in preparation for demo in Sydney 

Project Plan

The project plan is organized by the project milestones in the timeline above and includes a more detailed outline of the remaining tasks required to meet these milestones. The project plan can be downloaded from the Document Repository (named 'UTG Project Plan.xlsx).

Project Documents

UTG Project Test Plan.pdf

UTG Test Scripts.xlsx

UTG Project Implementation and Rollout Plan.pdf

Development Cycle 1 (May 2019 WGM)

A full list of tasks can be viewed in the project plan. Additional documentation supporting the tasks:

UTG Mif-Conversion Issues.docx

FHIR Extension Modifications for UTG.docx

Montreal Demo Materials:

Demo outline for Montreal

UTG May 2019 WGM Demonstration.pdf

Development Cycle 2 (September 2019 WGM)

Slides from lunch demo on 9/18: UTG September ONC Demonstration.pdf

Summer Alpha Testing

Submitter test group: Riki Merrick, Sheila Abner and Kathleen Connor

Reviewer test group: Ted Klein, Jess Bota, Dave Hamill, Rob Hausam, Bryn Evans, Sandy Stuart, Brian Pech, Craig Newman, Scott Robertson, Alex Deleon, Joel Francis, Michael Stevens

Alpha Test Report: UTG Project Alpha Test Report.pdf

Development Cycle 3 (TSC Demo and February 2020 WGM)

Slides from TSC demo on 1/20: UTG TSC Demonstration.PPTX

Requirements from TSC Demo

UTG Sydney Demo.PPTX

Running List of Requirements to be Completed Prior to Production in 2020

  1. Way of dealing with the VERY long list of code systems (>1000) and value sets (>3000)



  • No labels