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
 
(7 intermediate revisions by the same user 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]].
  
SWOT Analysis: Reviewed January 16, 2012
+
SWOT Analysis: Reviewed May 11, 2015
 
Status: Updated SWOT and Goals
 
Status: Updated SWOT and Goals
  
This analysis is requested by the TSC. It requires input from the group members. Hence, CGIT members are invited and should feel free to add information.
 
  
The SWOT analysis should enumerate points/arguments assorted to the following topics:
+
==Strengths==     
 
 
 
 
 
 
==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==
*Limited resouces to support domain work groups conformance initiatives
+
*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==
 
*Define and operationalize the role of a conformance facilitators (approach Project Services, through Project Scope Statements)
 
*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
 
*CGIT = central group to collect information from real projects
*SAIF (ECCF) initiative and SOA are new paradigms requiring new conformance guidance
 
 
*Enhance guidance for v2.x  
 
*Enhance guidance for v2.x  
 
*Creating guidance for v2.x and V3
 
*Creating guidance for v2.x and V3
Line 29: Line 25:
 
*Vocabulary conformance guidance
 
*Vocabulary conformance guidance
 
*FHIR
 
*FHIR
 +
*ARB & Product Line Task Force looking for consistent approach to conformance and testing
  
 
==Threats==
 
==Threats==
*duplication of efforts and inconsistent strategy in domain projects
+
*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 CGIT
+
**Other committees do work, that should be done by CGIT
  
 
==Goals==     
 
==Goals==     
*Create alignment between v2 and V3 conformance (including terminology)
+
*Create conformance alignment across all product lines (including terminology)
 
*Provide consistent common guidance and in-depth guidance for projects
 
*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 CGIT
 
*Get more people involved in the CGIT
*engage with other groups like EHR 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
 
*Establish a role for Conformance Facilitator
*assign conformance facilitator role to qualified indidivuals
+
*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