Governance Body Meeting Thursday, August 3, 2017 12:00 1:30 PM - - PowerPoint PPT Presentation

Governance Body Meeting

Thursday, August 3, 2017 12:00 – 1:30 PM EDT This meeting will be recorded for note taking purposes only

FOR DISCUSSION USE ONLY – August 3, 2017

• Transparency: Stakeholders will have

visibility into the Governance Body’s work and opportunities to provide input.

• Respect for Process: Governance Body

members will adhere to an agreed upon decision-making process. Members will

• bserve delineated and agreed upon roles

and responsibilities.

• Outreach: The Governance Body can solicit
• pinions and presentations from

stakeholders to inform its decision-making.

• Utility: The Governance Body will prioritize

use of existing information technology standards and infrastructure as it pursues shared and realistic goals that benefit all parties.

• Representativeness: Governance Body

members will represent their broader field and be responsive to the goals of the Digital Bridge partnership.

• Trust: Governance Body members will

honor commitments made to the Digital Bridge effort.

Digital Bridge Governance Principles

FOR DISCUSSION USE ONLY – August 3, 2017

Meeting Agenda

Time Agenda Item 12:00 PM Call to Order – John Lumpkin 12:03 PM Agenda Review and Approval – John Lumpkin 12:05 PM eCR Implementation (55 min)

1. Progress| Wave 1 implementations - R.Brown and B.Chang 2. Discussion| Issue: Variations on DB-eCR Approach – J.Jellison 3. Presentation| Legal and Regulatory – J.Jellison

12:15 PM Digital Bridge Strategy (20 min)

1. Action | Roadmap for the Digital Bridge – A.Cheeks-Lomax 2. Presentation | Draft: Digital Bridge Responsibility Scope – A.Cheeks-Lomax

1:20 PM Updates and Announcements (10 min)

1. Update | Communications – J.Cook 2. Review decision and major actions – C.Ishikawa

1:30 PM Adjournment – John Lumpkin

Purpose 1. Describe and discuss progress and issues in implementing eCR from technical and legal perspectives 2. Discuss and approve a Digital Bridge Roadmap; 3. Request comments on a draft Digital Bridge responsibilities scope document 4. Describe recent and upcoming communications activities Material 1. Governance body decision-making procedure 2. Summary report on Phase 3 Digital Bridge workgroup progress and participation 3. For discussion:

1. Issue Brief: Variations on DB-eCR Approach 2. Draft Digital Bridge Responsibilities

4. For approval:

1. Digital Bridge Roadmap

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge eCR Implementation

• 1. Progress |Wave 1 implementations - Rob Brown and Benson Chang
• 2. Discussion | Issue: Variations on DB-eCR Approach – Jim Jellison
• 3. Presentation| Legal and Regulatory - Jim Jellison

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge eCR Implementation

• 1. Progress |Wave 1 implementations - Rob Brown and Benson Chang
• 2. Discussion | Issue: Variations on DB-eCR Approach
• 3. Presentation| Legal and Regulatory - Jim Jellison

FOR DISCUSSION USE ONLY – August 3, 2017

Session Objectives: Wave 1 Implementations

• 1. Overview
• eCR Implementation Taskforce
• Implementation Sites
• 2. Progress
• Accomplishments and Activities
• Issues and Risks
• 3. Implementation Timeline Revisions

eCR Implementation Taskforce

Taskforce Charge

Oversight and coordination of technical implementation of the Digital Bridge electronic case reporting (eCR) approach during project phase 3. Deliverables 1. Digital Bridge eCR Implementation Plan 2. eCR onboarding document for public health agencies 3. eCR onboarding document for health care providers 4. eCR Implementation/Configuration Guide for EHR vendors 5. Implementation site communication plan 6. Updated Digital Bridge Technical Architecture Diagram (as required) 7. Test Management Plan 8. Updated Digital Bridge requirements (as required) 9. Implementation Architecture Diagram

• 10. Facilitate Reportability Response feedback from the taskforce

Update

• Test scenarios have increased in scope

and complexity to complete more thorough testing

• The implementation plan is being refined

to reflect the added complexities and dependences

• Current Wave 1 implementation date is

uncertain

eCR Site Participation

Public Health Agency Health Care Provider EHR Vendor Wave 1: April – September 2017 Kansas Lawrence Memorial Hospital Cerner Michigan Local Public Health Clinics NetSmart Utah Intermountain Healthcare Cerner Wave 2: September – 2017/2018 (Tentative) California UC Davis Epic Houston Houston Methodist Epic Massachusetts Partners HealthCare Epic New York Institute of Family Health Epic

eCR Implementation Taskforce Activities

Initial AIMS Connectivity (hello world message)

• Utah - Completed
• Kansas - Completed PHINMS polling test
• Michigan - Reviewing legal agreements for VPN connectivity
• Houston - Working with the jurisdiction and Houston Methodist on direct transport

Validator

• NIST Validator has been customized/configured for eICR
• Additional performance testing is underway for inline and online validator
• Online Validator is publicly accessible for testing:

https://validator.sandbox.aimsplatform.com/hitspValidation2/

• Validator presentation will be delivered during the next Digital Bridge monthly all-site meeting
• Allscripts has started to test with the Online Validator

RR Constructor

• Initial work on building RR has started

eCR Implementation Taskforce Activities (cont.)

RCKMS Integration

• Continuous Integration/Deployment completed and in testing
• Configuration has been completed. Testing with RCKMS team started on July 5, 2017
• RCKMS Performance Testing on AIMS ongoing
• Session #1 was completed on June 22, 2017
• Session #2 was completed on July 13, 2017
• Session #3 is underway this week. Focused on throttling and burn-in
• Release and deployment planning with APHL ongoing

Trigger Code Analysis

• Conducting an analysis of what codes (lab and/or clinical codes) are currently used for the five reportable

conditions to identify whether the RCTC align with codes seen by PH and used by EHRs/HC

• RCTC will be updated based on analysis results
• Zika reporting logic updated to meet jurisdictional needs

eCR Implementation – Risks & Issues

# Risk Impact Mitigation

1 Epic implementation for eICR 1.1 support (minus travel history) is delayed. Medium Current Wave 2 timeline being pushed out allows enough time for Epic to roll out support for eICR 1.1 (minus travel history). 2 Third party security assessment will not occur before initial implementations are in production. Medium On eCR roadmap for March 2018 3 Legal agreements & Data use agreements beyond initial implementation (risk for both Implementation and sustainability workgroups). High The legal workgroup has identified a law firm to begin the planning and creation of the legal and data use agreements.

# Issue Impact Mitigation

1 Cerner implementation for eICR 1.1 support is delayed due to competing priorities. Medium Cerner is pursuing engagement of Cerner/Intermountain resources for development while at the same time pursuing development leveraging Intermountain Research Informatics department. 2 An increase in the complexity and thoroughness of the test scenarios will cause a delay in the creation of the test eICR. Medium Test scenarios have been sent to Lantana.

Revised Implementation Timeline – Wave 1

March April May June July August September October November 15 30 15 30 15 30 15 30 15 30 15 30 15 30 15 30 15 30 Planning RCKMS & AIMS Development and Testing Engagement With Implementation Sites Post Production

Site Selection

Planning Development & Test Engagement With Implementation Sites

RCKMS Criteria Testing (Internal, Jurisdictional Criteria) Performance Testing (Iterative) RCKMS Training Complete Integration Testing (AIMS & RCKMS Together) Functional Testing (AIMS & RCKMS Separate) AIMS Transport Onboarding End-to-End Testing Establish Post Production Technical Support Help Finalize Test Scenarios Finalize Test Data Legal Agreements

Complete In Progress Not started

DRAFT

Digital Bridge – Wave 1 Timeline Dependencies

Testing (RCKMS, AIMS)

• Test Scenarios – In Process
• Test Data – Not Started

Testing (end-to-end with sites)

• AIMS Onboarding – Not Started

AIMS Onboarding (including RCTC configuration)

• Trigger Code Analysis – In Process
• Cerner development and schedule – Not Started

Production Cutover

• Legal Agreements – Not Started

Digital Bridge eCR Implementation

• 1. Progress |Wave 1 implementations - Rob Brown and Benson Chang
• 2. Discussion | Issue: Variations on DB-eCR Approach – Jim Jellison
• 3. Presentation| Legal and Regulatory - Jim Jellison

FOR DISCUSSION USE ONLY – August 3, 2017

FOR DISCUSSION USE ONLY – August 3, 2017

Background

• 1. One DB implementation site has 2 implementation projects
• 2. Some partners have concerns with one of the implementations

1. Timeliness 2. Completeness 3. Scalability

Digital Bridge eCR per Approved Approach (DB-eCR)

Health Care Public Health

Import Trigger Codes Provide Patient Care Match Trigger Codes Follow-Up Activity Process Case Report Process Response Electronic Lab Reporting

ELRs

Define Reporting Criteria Provide Trigger Codes Compare to Reporting Criteria

RCTC RCTC HL7 eICR

Determine Reportability Create Response Send Case Report Send Response Validate Case Report

Decision Support

(RCKMS) (AIMS) (AIMS)

Send Case Report

STLT-specific reporting criteria HL7 eICR HL7 RR HL7 RR

FOR DISCUSSION USE ONLY – August 3, 2017

eCR Process – MI Site Part A: DB-eCR

Health Care Public Health

Import Trigger Codes Provide Patient Care Match Trigger Codes Follow-Up Activity Process Case Report Process Response Electronic Lab Reporting

ELRs

Define Reporting Criteria Provide Trigger Codes Compare to Reporting Criteria

RCTC RCTC HL7 eICR

Determine Reportability Create Response Send Case Report Send Response Validate Case Report

Decision Support

(RCKMS) (AIMS) (AIMS)

Send Case Report

STLT-specific reporting criteria HL7 eICR HL7 RR

MiHIN

Send Response Validate eICR

HL7 eICR

Send Case Report

MiHIN

HL7 eICR

Send Case Report

HL7 RR

Send Response

FOR DISCUSSION USE ONLY – August 3, 2017

eCR Process – MI Site Part C: AA-eCR Health Care Public Health

Import Trigger Codes Provide Patient Care Match Trigger Codes Follow-Up Activity Process Case Report Process Response Electronic Lab Reporting

ELRs

Define Reporting Criteria Provide Trigger Codes Compare to Reporting Criteria

RCTC RCTC CCD

Determine Reportability Create Response Send Case Report Send Response Validate Case Report

Decision Support

(RCKMS) (AIMS) (AIMS)

Send Patient Care Documents

STLT-specific reporting criteria HL7 eICR HL7 RR

MiHIN

Follow-Up Activity Create and Validate eICR

HL7 eICR

Send Case Report

MiHIN

HL7 eICR

Send Case Report

HL7 RR

Send Response

FOR DISCUSSION USE ONLY – August 3, 2017

FOR DISCUSSION USE ONLY – August 3, 2017

Issue Summary

• 1. Issue resolved with withdrawal of alternative approach
• 2. Ongoing implementation work may uncover other issues that could require GB

decision

• 3. Digital Bridge support of eCR should entail

1. consideration of implementation experiences, evaluation findings, and legal recommendations 2. consensus recommendations for evolution of eCR requirements, architecture

Digital Bridge eCR Implementation

• 1. Progress |Wave 1 implementations - Rob Brown and Benson Chang
• 2. Discussion | Issue: Variations on DB-eCR Approach
• 3. Presentation| Legal and Regulatory - Jim Jellison

FOR DISCUSSION USE ONLY – August 3, 2017

Highlights

• DWT has drafted an analysis of privacy laws and related recommendations for eCR
• Legal & Regulatory Workgroup has provided feedback
• DWT has refined its eCR recommendations and discussed them with clients (RWJF, APHL,

TFGH/PHII)

• DWT discussed eCR recommendations with implementation stakeholders (Aug 2)
• Next Steps:
• Describe recommendations to Governance Body (Aug 3)
• Draft agreements for implementation sites’ review

FOR DISCUSSION USE ONLY – August 3, 2017

eCR Recommendations as of Aug 2, 2017

Option Short-Term (Initial Sites) Medium-Term Long-Term Option 1 (De-Identification): De-identified case reports initially reported to Decision Support Intermediary; then as identified after processing by DSI’s case reporting logic No - Not technically feasible in short term No - Not technically feasible in short term ? - May be worth investment due to privacy law compliance and potential uses for de- identified data Option 2 (Public Health Agent): DSI is an agent of public health agencies; Providers/EHRs would consume both national and local calls from single national source (DSI) and execute case reporting logic; DSI only receives case reports that are likely reportable under local law. ? - Not feasible for most of the initial implementation sites, but it may be possible for one to test feasibility Yes; if EHRs/HIEs able and willing to implement case reporting logic. Benefits: Low HIPAA risk; manageable number of agreements Yes; see Medium-Term Option 3 (DSI as BA): DSI enters into BAAs with Providers, EHRs, HIEs. Providers/EHRs would consume national trigger codes and execute case reporting logic based on national codes. DSI receives case reports based on national triggers, executes RCKMS local-trigger-codes logic, and report cases reportable in the local jurisdiction. Yes – Initial sites familiar with BAAs ? – Increased legal risk to DSI due to HIPAA and amount of case reports received; scalability issues due to number of agreements. ? – see Medium Term

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Strategy Update

Alana Cheeks-Lomax

FOR DISCUSSION USE ONLY – August 3, 2017

Strategy Workgroup Updates

• Kicked off Funding Model & ROI Model Tiger Teams
• Workgroup Deliverables
• Finalized Digital Bridge roadmap for approval by governance body
• Developed list of Digital Bridge in/out activities based on discussion from the

Greenhouse

• Continued developing use case criteria and began discussing Digital Bridge’s next use

case

• Governance Body Asks
• Receive “greenlight” to develop new Digital Bridge by-laws and governance structure
• Approve Digital Bridge roadmap
• Receive feedback on Digital Bridge in/out activities

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Roadmap

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Strategic Roadmap

Milestones & Critical Activities

By-laws approved by Governance Body Operating model approved by Governance Body Reporting on five conditions Governance by-laws drafted Operating model self- sustaining Governance Body changes implemented Identify funders Recommend long-term funding modal Implement new funding model Establish communications advisory group Digital Bridge communications plan-V2 Establish Digital Bridge success stories Operating model implemented Marketing materials for funders Evaluate funding model Stand-up technical

• perations

workgroup Wave 1 – Test implementation complete Wave 2 – Test implementation complete Wave 1 – Production Wave 2 - Production

PHASE III (2017) PHASE IV (2018-2019) PHASE V (2020-2021) PHASE VI (2022-2023)

Jun Nov Jan Aug Dec Jan Nov Dec Jan Jan Apr Aug Concept of Operations developed Reportability Response (RR) Published Template for eCR legal agreements eCR legal agreement templates developed Develop long term legal strategy Legal agreement templates developed for new use cases Legal agreement templates developed for subsequent use cases Use case criteria agreed upon Governance Body approves use case 2 Use case 2 launched 7 sites up and running Funding Model 100% in effect Digital Bridge recruitment strategies & marketing Infrastructure for new use cases

Complexity Low High

Governance Body approves use case 3 Begin Technical Architecture Evaluation Develop and recommend long term technical architecture Use case 3 launched Implement long term technical architecture Governance Body approves long term technical architecture

Legend

Operations Communications Funding Technical Infrastructure Legal Users & Use Cases Critical Path Other Milestones

*** General Notes: (1) Complexity is used as a rough proxy for the needed resources and effort to complete a milestone, (2) Overall timeline and milestones are subject to change depending on project dependencies.

Wave 1 legal agreements signed Wave 2 legal agreements signed

FOR DISCUSSION USE ONLY – August 3, 2017

About the Digital Bridge

The vision of the Digital Bridge is to ensure our nation’s health through a bidirectional information flow between health care and public health. A first of its kind partnership, the Digital Bridge has created a forum for key decision makers in the health care, public health and health information technology arenas to share ideas to meet this vision. The Digital Bridge also acts as an incubator, cultivating projects that advance effective information sharing to improve clinical care and public health. As its first project, the Digital Bridge collaborative has designed a nationally scalable approach to electronic case reporting (eCR) that will be implemented across different states and cities. eCR reduces the burden of reporting infectious diseases, while improving the timeliness, accuracy and completeness of the data. While the initial focus is on electronic case reporting for infectious diseases, the governance principles and the infrastructure improvements that are developed will apply to chronic conditions and other public health issues in the future.

Accomplishments 2016-2017

• Established vision and project charter
• Formed governance body and workgroups
• Developed functional requirements and a technical architecture diagram for eCR
• Created initial sustainability plan and communications plan
• Shared preliminary legal recommendations
• Established new workgroups in the areas of implementation, evaluation, strategy

and legal/regulatory issues

• Selected seven eCR implementation sites

Upcoming Digital Bridge eCR Milestones

• Template for eCR legal agreements; Phase III, July 2017
• Wave 1 test implementations complete; Phase III, August 2017
• eCR legal agreement templates developed; Phase III, August 2017
• Wave 1 legal agreements signed; Phase III, October 2017
• Wave 1 production go-live; Phase III, November 2017
• Wave 2 test implementations complete; Phase III, May 2018
• Wave 2 legal agreements signed; Phase III, July 2018
• Wave 2 production go-live; Phase III, August 2018

Benefits of the Digital Bridge Approach

• A unified approach to information exchange eases the burden and costs for all

stakeholder groups

• Projects such as eCR create more complete and accurate data in real time for action—

allowing for earlier intervention and reduced disease transmission with timely detection

• Empowers clinicians and public health professional through more collaboration and

information sharing FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Strategic Roadmap

Milestones & Critical Activities

By-laws approved by Governance Body Operating model approved by Governance Body Reporting on five conditions Governance by-laws drafted Operating model self- sustaining Governance Body changes implemented Identify funders Recommend long-term funding modal Implement new funding model Establish communications advisory group Digital Bridge communications plan-V2 Establish Digital Bridge success stories Operating model implemented Marketing materials for funders Evaluate funding model Stand-up technical

• perations

workgroup Wave 1 – Test implementation complete Wave 2 – Test implementation complete Wave 1 – Production Wave 2 - Production

PHASE III (2017) PHASE IV (2018-2019) PHASE V (2020-2021) PHASE VI (2022-2023)

Jun Nov Jan Aug Dec Jan Nov Dec Jan Jan Apr Aug Concept of Operations developed Reportability Response (RR) Published Template for eCR legal agreements eCR legal agreement templates developed Develop long term legal strategy Legal agreement templates developed for new use cases Legal agreement templates developed for subsequent use cases Use case criteria agreed upon Governance Body approves use case 2 Use case 2 launched 7 sites up and running Funding Model 100% in effect Digital Bridge recruitment strategies & marketing Infrastructure for new use cases

Complexity Low High

Governance Body approves use case 3 Begin Technical Architecture Evaluation Develop and recommend long term technical architecture Use case 3 launched Implement long term technical architecture Governance Body approves long term technical architecture

Legend

Operations Communications Funding Technical Infrastructure Legal Users & Use Cases Critical Path Other Milestones

*** General Notes: (1) Complexity is used as a rough proxy for the needed resources and effort to complete a milestone, (2) Overall timeline and milestones are subject to change depending on project dependencies.

Wave 1 legal agreements signed Wave 2 legal agreements signed

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge In/Out Activities

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Activities

• Workgroup continued the conversation from Digital Bridge Greenhouse
• Which activities are the responsibility of Digital Bridge and which are

not the responsibility of Digital Bridge?

• Conversation supports workgroup’s and tiger teams’ recommendations

for funding and business model approach

• Questions for consideration
• 1. Are there any activities that are currently not included on either lists?
• 2. Are there any activities that are currently in the incorrect category?
• 3. Are there any activities that are currently listed as the responsibility of Digital

Bridge, but may not be the responsibility of Digital Bridge in the future? And vice versa?

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Activities Cont’d

What is Digital Bridge Responsible For?

• Governance
• Incubator & Handoff
• Trust & Legal
• Communication
• Project Management
• Funding
• Standards Management
• Operations Coordination

What is Digital Bridge NOT Responsible For?

• Regulation & Policy
• Data Security
• Data Provision, Receipt, & Quality
• Recruitment
• Training, Technology, & Adoption
• Onboarding & Technical Assistance
• Integration
• Systems Maintenance, Enhancements, and

Development

• Systems Hosting
• Surveillance Science
• Funding (Digital Bridge Partner

Organizations)

• Legal

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Activities

• Workgroup continued the conversation from Digital Bridge Greenhouse
• Which activities are the responsibility of Digital Bridge and which are

not the responsibility of Digital Bridge?

• Conversation supports workgroup’s and tiger teams’ recommendations

for funding and business model approach

• Questions for consideration
• 1. Are there any activities that are currently not included on either lists?
• 2. Are there any activities that are currently in the incorrect category?
• 3. Are there any activities that are currently listed as the responsibility of Digital

Bridge, but may not be the responsibility of Digital Bridge in the future? And vice versa?

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Activities Cont’d

What is Digital Bridge Responsible For?

• Governance
• Incubator & Handoff
• Trust & Legal
• Communication
• Project Management
• Funding
• Standards Management
• Operations Coordination

What is Digital Bridge NOT Responsible For?

• Regulation & Policy
• Data Security
• Data Provision, Receipt, & Quality
• Recruitment
• Training, Technology, & Adoption
• Onboarding & Technical Assistance
• Integration
• Systems Maintenance, Enhancements, and

Development

• Systems Hosting
• Surveillance Science
• Funding (Digital Bridge Partner

Organizations)

• Legal

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Responsibilities

• Governance
• Governance Body Meetings
• Final approval of all activities of Digital Bridge
• Outreach to government (federal, state, local) and private organizations for support, both financial and tactical
• Setting up and overseeing workgroups, tiger teams, taskforces, etc. for development of deliverables and milestones
• Overseeing the development long term by-laws and the Organizational Structure for Digital Bridge
• Approval of long term by-laws and the Organizational Structure for Digital Bridge
• Strategic systems enhancement (i.e. to support a new use case)
• Oversee development of Use Cases
• Approval of Use Cases
• Oversee development of functional requirements (for approved Use Cases)
• Approval of functional requirements (for approved Use Cases)
• Oversee development of technical requirements (for approved Use Cases)
• Approval of technical requirements (for approved Use Cases)
• Oversee development and maintenance of personnel/organization member directory and technical system directory
• Advise partner organizations in search for funding to support the needed components to fulfill the Digital Bridge vision

(i.e. AIMS & RCKMS)

Digital Bridge Responsibilities

• Incubator & Handoff
• Serve as an incubator facilitating the development of pilots to test the functional,

technical, business and legal approaches of each use case

• Establish a process to identify, evaluate and define the entity or entities that will
• perate a solution at a national level including the ability to support participants

signing agreements and frameworks

• Create a process to hand-off the implementation and operation of an approach
• f a use case to the entity or entities that will operate the solution at a national

level

• Perform ongoing monitoring and evaluation of the national operations of the

solutions for each use case

Digital Bridge Responsibilities

• Trust & Legal
• Development of common legal agreements to support a common platform
• Development of trust frameworks to support a common platform
• Support participants in understanding agreements and frameworks

Digital Bridge Responsibilities

• Communication
• Communicating activities Digital Bridge is taking part in
• Presenting at industry conferences as approved by Governance or an advisory group
• Communicating successes of Digital Bridge
• Getting feedback from the community on Digital Bridge activities
• Generating interest in participating in initial implementations and/or pilots in Digital Bridge
• Develop and execute targeted marketing strategies to ensure uptake of solutions at a national

level

• Develop and execute strategies for advocacy for Digital Bridge, tailored to specific user groups
• Maintaining and distributing digital and physical content related to Digital Bridge through

digitalbridge.us, social media, and other channels approved by Governance or an advisory group

• Define communications methods and necessary technical operations during emergent scenarios

(i.e. new infectious disease outbreak, pushing new trigger codes ASAP to all Digital Bridge participants)

• Track and monitor the information being communicated about Digital Bridge and where the

communications are happening

Digital Bridge Responsibilities

• Program Management
• Managing workgroups, tiger teams, taskforces, etc.
• Coordinating workgroups, tiger teams, taskforces, etc. meetings
• Assisting in development of deliverables of workgroups, tiger teams, taskforces,

etc.

• Support onboarding of tasks for all groups
• Determining, publishing, and coordinating lifecycle plans for all Digital Bridge use

cases (i.e. transitions to new standards, new technical infrastructure, sun setting

• f use cases if necessary)

Digital Bridge Responsibilities

• Funding
• Develop, pursue, secure, and manage a long-term Digital Bridge funding strategy,

including activities to produce ongoing revenue for the Digital Bridge

• Coordination with activities that are funded through other organizations and/or

agencies

Digital Bridge Responsibilities

• Standards Management
• Ensuring that standards are properly used, including management of any

Governance approved certification criteria

• Ensuring a common understanding of the standards and their purpose
• Common understanding of the platform requirements
• Taking an active role in standards identification, development, and maintenance

(i.e. identifying standards that are needed, communicating with the standards bodies, identifying liaisons, etc.)

Digital Bridge Responsibilities

• Operations Coordination
• Support and manage coordination among sites during Digital Bridge onboarding

process, technical troubleshooting, and systems updates

• Connecting participants with appropriate POCs for technical infrastructure
• Coordinate with Digital Bridge participants to ensure they are able to satisfy the

requirements for each use case

Non Digital Bridge Responsibilities

• Regulatory and Policy
• Developing regulations to support information exchange/sharing
• Working with policymakers to inform and support Digital Bridge
• Data Security
• Ensuring the security of data (in transit and at rest)
• Data Provision, Receipt, & Quality
• Determining access rules for all types of data
• Ensuring that data is received correctly at all parties
• Quality assurance of data before sending
• Ensuring received data is the same as sent data

Non Digital Bridge Responsibilities

• Recruitment
• Identifying new participants
• Developing recruitment strategies and campaigns for participants needed for

new use cases

• Training, Technology, & Adoption
• Training participants on how to utilize Digital Bridge provided data to fulfill their

surveillance duties (from a public health perspective) or clinical efficacy goals (from a provider perspective)

Non Digital Bridge Responsibilities

• Onboarding & Technical Assistance
• Develop and maintain a provider helpdesk to support health care providers when

they attempt to configure systems for interconnect

• Integration
• Performing the integration work within the provider technical environments,

including and development/enhancement work necessary for the specific installation of provider’s EHR vendor software

Non Digital Bridge Responsibilities

• Systems Maintenance, Enhancements, & Development
• Performing standard maintenance on existing provider systems and EHR vendor

software

• Enhancing existing provider systems and EHR vendor software for further refined use

cases

• Developing new provider systems and EHR vendor software to support new use cases

and changing requirements

• Systems Hosting
• Hosting the decision support intermediary (i.e. AIMS & RCKMS)
• Hosting any other necessary centralized systems necessary for Digital Bridge use cases
• Providing high availability/disaster recovery services for centralized Digital Bridge

systems

Non Digital Bridge Responsibilities

• Surveillance Science
• Monitoring for disease outbreaks
• Confirm timeliness of data
• Connecting data from disparate sources
• Follow up on shared data
• Funding (Digital Bridge Partner Organizations)
• Ensuring that partner organizations are able to support the components needed

to fulfill the vision of Digital Bridge (i.e. AIMS & RCKMS)

• Legal
• Developing data use agreements

Strategy Workgroup Next Steps

FOR DISCUSSION USE ONLY – August 3, 2017

Strategy Workgroup Next Steps

• Workgroup will be going on hiatus until mid-September
• During the hiatus, the PMO will:
• Begin developing final workgroup artifacts – Digital Bridge sustainability plan

& eCR sustainability plan

• Continue to interact with and seek advice from the workgroup via the

Basecamp message board

• Convene the group as needed (via phone calls) for relevant topics

FOR DISCUSSION USE ONLY – August 3, 2017

Updates and Announcements

FOR DISCUSSION USE ONLY – August 3, 2017

Digital Bridge Communications

Jessica Cook

FOR DISCUSSION USE ONLY – August 3, 2017

Recent Communications Activity

• NACCHO Annual Conference, July 11-13
• Successful Digital Bridge and eCR presentations,

with significant activity at exhibit booth.

• Website traffic increased during and following

the NACCHO Conference.

• Walter Suarez presented the Digital Bridge legal

framework during the ONC 21st Century Cures Act Trusted Exchange Framework kick-off meeting on July 24.

FOR DISCUSSION USE ONLY – August 3, 2017

Upcoming Communications Activities

• Presentations
• Digital Bridge session on Aug. 4 for HIMSS staff
• Presentation at the APHA 2017 Annual Meeting, Nov. 7
• New eCR Communications Materials on Basecamp
• Will be integrated in Digital Bridge communications plan and slides this month.
• Digital Bridge Webinar Series
• Highlight workgroup topics; begins in October.
• Advisory Group
• Thank you in advance to our advisors!
• Our advisors will help us prioritize communications activities and limited resources.

FOR DISCUSSION USE ONLY – August 3, 2017

Review | Decisions & Actions

Charlie Ishikawa

FOR DISCUSSION USE ONLY – August 3, 2017

NEXT MEETING Thursday, September 7th @ 12:00 – 1:30 PM EDT

FOR DISCUSSION USE ONLY – August 3, 2017