Difference between revisions of "AID SWOT"

From HL7Wiki
Jump to navigation Jump to search
m (moved RIMBAA SWOT to AID SWOT)
Line 1: Line 1:
 
===SWOT===
 
===SWOT===
Strengths, Weaknesses, Opportunities, and Threats for the RIMBAA WG
+
Strengths, Weaknesses, Opportunities, and Threats for the AID "user group"
 
   
 
   
 
====Strengths====
 
====Strengths====
*Active members with actual experience of v3 implementations
+
*Active members with actual experience of HL7 implementations
 
*Active members with a passion for health information technology  
 
*Active members with a passion for health information technology  
*Deep understanding of RIM and Methodology
+
*Deep understanding of HL7 standards and healthcare IT implementations
  
 
====Weaknesses====
 
====Weaknesses====
*Inbalance in ability to share information due to Intellectual Property issues
+
*Inbalance in ability to share information due to Intellectual Property issues (e.g. users that are unable to share because of company IP issues)
 
*Quite a few active contributors to the deliverables don't take part in WGMs (those are too much geared towards standards developers)
 
*Quite a few active contributors to the deliverables don't take part in WGMs (those are too much geared towards standards developers)
*Doesn't "quite fit" with most other ongoing HL7 activities - it doesn't produce standards.
 
  
 
====Opportunities====
 
====Opportunities====
*Has the ability to show the power of v3 well beyond that of "messaging"
+
*Has the ability to show the power of HL7 standards
*Shows value of Enterprise Architecture Framework (SAIF)
+
*Has the capability to ease implementations of HL7 standards (best practices, reference implementation)
*Has the capability to ease implementations of v3 (best practices, reference implementation)
+
*Free IP, and Grassroots adoption of FHIR, will expand our audience.
*RIMBAA will explore opportunities to include FHIR and other model based architectural approaches
 
  
 
====Threats====
 
====Threats====
 
*Stifling effect of Intellectual Property issues
 
*Stifling effect of Intellectual Property issues
*Irrelevance of RIMBAA in the eyes of some: the "We have too much legacy stuff to care about RIMBAA" argument
+
*AID not seen as an active WG because few implementers attend WGMs.
*RIMBAA not seen as an active WG because few implementers attend WGMs.
+
*Risk that commercial parties use AID as a marketing platform for tools.
*Risk that commercial parties use the WG as a marketing platform for tools.
 

Revision as of 22:08, 22 January 2014

SWOT

Strengths, Weaknesses, Opportunities, and Threats for the AID "user group"

Strengths

  • Active members with actual experience of HL7 implementations
  • Active members with a passion for health information technology
  • Deep understanding of HL7 standards and healthcare IT implementations

Weaknesses

  • Inbalance in ability to share information due to Intellectual Property issues (e.g. users that are unable to share because of company IP issues)
  • Quite a few active contributors to the deliverables don't take part in WGMs (those are too much geared towards standards developers)

Opportunities

  • Has the ability to show the power of HL7 standards
  • Has the capability to ease implementations of HL7 standards (best practices, reference implementation)
  • Free IP, and Grassroots adoption of FHIR, will expand our audience.

Threats

  • Stifling effect of Intellectual Property issues
  • AID not seen as an active WG because few implementers attend WGMs.
  • Risk that commercial parties use AID as a marketing platform for tools.