• Strengths
    • V2, V3, FHIR, and vocabulary expertise
    • Wide domain and general clinical workflow integration & implementation expertise including general orders and results, AP, Lab, Eyecare, etc.
    • Multi-Project management
    • Cross-work group coordination, synchronization (ARB, CS, FMG, SAIF, Rx, EST……) as well as external coordination with IHE.
    • HL7-savvy leadership (long history, experience, network)
  • Weakness
    • Involved in a broad range of activities
    • Shortage of participants able to spend time on and progress OO projects
    • Current drivers (co-chairs, facilitators, project leads) are spread thin and involved in many HL7 activities
    • Project synchronization with other workgroups needs attention to avoid divergent paths
  • Opportunities
    • Improve project synchronization to ensure other workgroups contribute to OO models (CDS, AP, CG…)
    • Ensure FHIR includes OO concepts
    • Mentor additional drivers.
    • Monitor the evolution of HL7 restructuring and determine opportunities to harmonize and collaborate with the new environment
    • Increase number of V2 implementation guide projects
    • Increase number of V2-FHIR cross-mapping or synchronization projects 
  • Threats
    • Heavy influence of government funding (ONC) on realm-specific projects 
    • Increased project overhead impacting work group participant time allocations
    • Volunteer workload expectations imposed by accelerators
    • Ongoing challenges of virtual working group meetings (time zones)
    • OO (and InM) are the only remaining sources of v2 knowledge 
    • The ongoing impact of lack analysis of the appropriateness of FHIR for the behavior model for lab interactions (determining the state of something other than the resource – e.g. orders/results, for US realm CLIA compliance) as well as the focus on 80% rule for inclusion in the core spec
  • No labels