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

Difference between revisions of "ICTC SWOT-Analysis"

From HL7Wiki
Jump to navigation Jump to search
 
(15 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
Return to [[Implementation_and_Conformance_TC#Active_projects|ICWG Projects]].
 
Return to [[Implementation_and_Conformance_TC#Active_projects|ICWG Projects]].
  
This analysis is requested by the TSC. It requires input from the group members. Hence, ICWG members are invited and should feel free to add information.
+
SWOT Analysis: Reviewed May 11, 2015
 +
Status: Updated SWOT and Goals
  
The SWOT analysis should enumerate points/arguments assorted to the following topics:
 
  
 
+
==Strengths==     
SWOT Analysis: Review May 18, 2011
 
Status: No modifications necessary
 
 
 
==Strength==     
 
 
*People want guidance on implementation and conformance
 
*People want guidance on implementation and conformance
 
*We have qualified team members
 
*We have qualified team members
 +
*We have experience with all the product lines
 +
*We have real-hands-on experience in both implementation and testing
  
 
==Weaknesses==
 
==Weaknesses==
*We have very limited resources due to low attendance
+
*Limited resources to support domain work groups conformance initiatives
*Unwareness in other groups
+
*Lack of awareness in other groups
*low feedback on open work items
+
*Low feedback on open work items
*inconsistent attendance at t-cons resulting in low interest
+
*Inconsistent attendance on bi-weekly telephone conference calls resulting in low interest
  
 
==Opportunities==
 
==Opportunities==
*ICWG = central group to collect information from real projects
+
*Define and operationalize the role of a conformance facilitators (approach Project Services, through Project Scope Statements)
*SAEAF (ECCF) initiative and SOA are new paradigms requiring new conformance guidance
+
*CGIT = central group to collect information from real projects
 
*Enhance guidance for v2.x  
 
*Enhance guidance for v2.x  
 
*Creating guidance for v2.x and V3
 
*Creating guidance for v2.x and V3
 
**Example of conformance profile for V3
 
**Example of conformance profile for V3
 
*Vocabulary conformance guidance
 
*Vocabulary conformance guidance
 +
*FHIR
 +
*ARB & Product Line Task Force looking for consistent approach to conformance and testing
  
 
==Threats==
 
==Threats==
*waste of resources and inconsistent strategy in work packages
+
*Duplication of efforts and inconsistent strategy in domain projects
*lack of awareness of other groups (working on conformance specifications without notice)
+
*Lack of awareness of other groups (working on conformance specifications without notice)
**other committees do "their work" without any notification
+
**Other committees do "their work" without any notification
**other committees do work, that should be done by ICWG
+
**Other committees do work, that should be done by CGIT
  
 
==Goals==     
 
==Goals==     
*Create alignment between v2 and V3 conformance
+
*Create conformance alignment across all product lines (including terminology)
**Same terminology in v2 and v3
+
*Provide consistent common guidance and in-depth guidance for projects
*an FAQ for implementors (website)
+
*Create an FAQ for implementers (website)
*Get more people involved in the ICWG
+
*Get more people involved in the CGIT
*engage with other groups like SD and SOA
+
*Engage with other work groups that are creating conformance guidance
*clarify with TSC about our mission and responsibilities
+
*Clarify with TSC about our mission and responsibilities
 +
*Establish a role for Conformance Facilitator
 +
*Assign conformance facilitator role to qualified individuals

Latest revision as of 14:33, 11 January 2016

Return to ICWG Projects.

SWOT Analysis: Reviewed May 11, 2015 Status: Updated SWOT and Goals


Strengths

  • People want guidance on implementation and conformance
  • We have qualified team members
  • We have experience with all the product lines
  • We have real-hands-on experience in both implementation and testing

Weaknesses

  • Limited resources to support domain work groups conformance initiatives
  • Lack of awareness in other groups
  • Low feedback on open work items
  • Inconsistent attendance on bi-weekly telephone conference calls resulting in low interest

Opportunities

  • Define and operationalize the role of a conformance facilitators (approach Project Services, through Project Scope Statements)
  • CGIT = central group to collect information from real projects
  • Enhance guidance for v2.x
  • Creating guidance for v2.x and V3
    • Example of conformance profile for V3
  • Vocabulary conformance guidance
  • FHIR
  • ARB & Product Line Task Force looking for consistent approach to conformance and testing

Threats

  • Duplication of efforts and inconsistent strategy in domain projects
  • Lack of awareness of other groups (working on conformance specifications without notice)
    • Other committees do "their work" without any notification
    • Other committees do work, that should be done by CGIT

Goals

  • Create conformance alignment across all product lines (including terminology)
  • Provide consistent common guidance and in-depth guidance for projects
  • Create an FAQ for implementers (website)
  • Get more people involved in the CGIT
  • Engage with other work groups that are creating conformance guidance
  • Clarify with TSC about our mission and responsibilities
  • Establish a role for Conformance Facilitator
  • Assign conformance facilitator role to qualified individuals