Role | FTE Implementation | Responsibilities |
|---|
Project Sponsor | 0.10 | Commits to participating in implementation project as outlined in implementation project charter. Provides oversight to all APHL ETOR technical assistance teams. Responsible for the staffing and scheduling of ETOR implementations. Serves as escalation and support for team.
|
Project Manager | 0.50 | Acts as APHL primary contact for PHL and HCO involved in the implementation project. Manages implementation project(s) and TA engagement(s) including scheduling and project planning, stakeholder management, risk identification and mitigation, issue tracking and solutioning, communication, and associated documentation per APHL standards. Coordinates with APHL TA team, PHL, and HCO to ensure tasks are completed and progress made. Provides review, quality control, and assurance on TA processes and deliverables. Provides project management updates following APHL and PMO policies. Collates feedback from APHL TA Team, PHL, and HCO on implementation process opportunities for improvement. Coordinates project meetings (and agendas) between APHL TAS teams and various stakeholders, documents meeting minutes/decisions/action items/next steps, and performs follow-up. Leads knowledge management activities to organize, track and communicate project activities in Smartsheet or Confluence. Utilizes APHL processes, communications, tracking systems or other logistical solutions to help ensure project success.
|
Lab Workflow SME | 0.50 | Observes, documents, and assesses current PHL and HCO workflows and processes around ordering and result reporting. Leads and analyzes gap analyses for 1) current workflow(s) vs future workflow(s) and 2) required and desired elements. Documents future-state PHL workflows, encompassing ETOR processes. Documents future-state HCO workflows, encompassing ETOR processes. Documents functions that differ from current processes and how to handle if/then situations. Documents requirements for test(s) in scope for ETOR implementation. Primarily supports the Planning & Analysis and Production portion of the Implementation. Provides insight to Terminologist should questions arise during Configuration and/or later steps of the approach.
|
Terminologist | 0.50 | Collecting information from the PHL and HCO. Identifies data element gaps. Map local codes to middle ground (intermediary) for both PHL and HCO. Assists with mapping local-to-standardized values across different vocabulary domains. Provides test case scenarios. Performs validation on HL7 messages and provides feedback. Assists in implementation of public health integration use cases using national messaging standards (HL7), implementation guides, and encoding guidelines. Helps develop and maintain message implementation guides, business rules, and message specifications as needed for APHL member and partner organization support (e.g., result reporting to CDC, ETOR for PHLs and their business partners, etc.). Seeks insight from the Lab Workflow SME should questions arise regarding workflow documentation. Provides training on Symedical (mapping tool).
|
Technical Architect | 0.25 | Analyzes client IT environments and messaging capabilities. Helps to identify technical solutions to meet messaging requirements. Provides TA consulting to healthcare organization and public health laboratory to advise on implementation of IT messaging solutions (e.g., reviewing for structural errors, writing queries to pick up messages outside of the S3 receiving bucket). Coordinates with centralized technical team for specific technical tasks. Provides training on DASH (message monitoring tool).
|
Data Integration Engineer | 0.50 | Establishes connection between PHL and middle ground. Establishes connection between HCO and middle ground. Determines extraction process from the LIMS (what can it import, export). Works closely with terminologists. Collects information on data workflow, primarily with LIMS and integration engine. Works with LIMS vendor as necessary.
|