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

Difference between revisions of "Conformance SWOT"

From HL7Wiki
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
SWOT Analysis: Reviewed January 16, 2017
+
SWOT Analysis: Reviewed January 29, 2018
 
Status: Updated SWOT and Goals
 
Status: Updated SWOT and Goals
  
Line 17: Line 17:
 
**Applying conformance rules to applications
 
**Applying conformance rules to applications
 
*Conformance WG = central group to collect information from real projects
 
*Conformance WG = central group to collect information from real projects
*Enhance guidance for v2.x
+
*Modernize HL7 V2
*Creating guidance for v2.x
+
**Develop migration strategy to modernize V2
 
*Vocabulary conformance guidance
 
*Vocabulary conformance guidance
*ARB and Product Line Task Force looking for consistent approach to conformance and testing
 
 
*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)
  
Line 33: Line 32:
  
 
==Goals==     
 
==Goals==     
 +
*More education, webinars?
 
*Create conformance alignment across all product lines (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

Latest revision as of 16:17, 29 January 2018

SWOT Analysis: Reviewed January 29, 2018 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

Opportunities

  • FHIR
    • Applying conformance rules to applications
  • Conformance WG = central group to collect information from real projects
  • Modernize HL7 V2
    • Develop migration strategy to modernize V2
  • Vocabulary conformance guidance
  • Define and operationalize the role of a conformance facilitators (approach Project Services, through Project Scope Statements)

Threats

  • FHIR
    • Conformance in FHIR is moving forward without Conformance WG participation
    • Implementors are not required to read base specification for FHIR and so are not aware of conformance constructs when using FHIR
  • Duplication of efforts and inconsistent strategy in domain projects in regards conformance
  • 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 Conformance WG

Goals

  • More education, webinars?
  • 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 Conformance WG
  • Engage with other work groups that are creating conformance guidance
  • Clarify with TSC about our mission and responsibilities
  • Assign conformance facilitator role to qualified individuals