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

Difference between revisions of "Product List"

From HL7Wiki
Jump to navigation Jump to search
Line 10: Line 10:
 
* [[Product_RIM|Reference Information Model (RIM)]]- see Modeling Standards
 
* [[Product_RIM|Reference Information Model (RIM)]]- see Modeling Standards
 
* [[Product_Vocabulary|Vocabulary Specifications]]- see Modeling Standards
 
* [[Product_Vocabulary|Vocabulary Specifications]]- see Modeling Standards
* [[Product_ITS_DT|Data Types]] - Abstract Specification  
+
* [[Product_DT|Data Types]] - Abstract Specification  
 
* [[Product_V3_RCL|Refinement, Constraint, and Localization]] to version 3 Messages  
 
* [[Product_V3_RCL|Refinement, Constraint, and Localization]] to version 3 Messages  
 
* XML and UML Implementation Technology Specification - [[Product_ITS_DT|Data Types]]  
 
* XML and UML Implementation Technology Specification - [[Product_ITS_DT|Data Types]]  

Revision as of 17:57, 20 January 2010

Product List

Summary Stats (2010-01-18): Products - 79 (79 on wiki)
Steward-reviewed (reviewed by steward Work Group) - 65 (82% complete)
Marketing-reviewed - 52

Health Information Exchange Standards

Foundation

Messaging

Documents

Services

Health Information Knowledge Representation Standards

Arden Syntax, SPL, GELLO

Modeling Standards

Application Functional Specifications

EHR-S FM, PHR-S FM, EIS SFM, RLUS SFM, DSS SFM, CRFQ SFM

Clinical Context Management Standards

Implementation Guides

Education Services

Governance and Maintenance

Ongoing and annual review, maintenance, and endorsement of Product Definitions

  • New product request - - TSC must be aware of and recognize on a PSS coming for approval, and add to inventory
  • Updates to products: review annually prior to September plenary, check for ANSI 5-year anniversary, etc.
  • Evaluate potential for expired products or standards: with DSTU expiration, withdrawal of ANS standard, replacement?

Suggested Additions

  • GOM
  • HDF
  • PLPCD
  • MoUs, Charter Agreements, and Liasons -- While these are not “traditional” products – they do cost involve giving away access to HL7 IP and/or meetings and/or brand, and so deliver value and have a cost
  • Podcasts (audio and/or Video) from WGMs — these could be delivered as a member benefit which would be hugely valuable to many current and potential members (helping to reduce very expensive member churn). Some extracts or complete items could be delivered free as a marketing exercise
  • If we're going to conflate classes and ennumerated instances in the diagram, we should list all of the serivces that have currently been approved, i.e. EIS, RLUS, CRFQ, and (I believe) PASS.
  • NCI notes we see the partnership with HL7 going forward as one of HL7 taking the lead on development and maintenance of the core SAEAF content as manifest in the SAEAF Book, a resource for all organizations interested in adopting SAEAF. In turn, the NCI CBIIT plans to develop a set of tools for managing SAEAF-derived semantic content (we lump this content under the rubrique "model/artifact management") which we would be willing to share with the larger community.
  • As well as selling membership and WGM attendance, HL7 currently runs a franchising operation. HL7 leases Affiliate rights to the National Organisations in return for a cut of their membership revenue. This should be captured, documented, and managed as a Product. We should be looking at how we maintain this product specification, and how we sell it, how we price it, and how we ensure that it is delivered in a cost effective and high value way. Maybe we will move to a different business model for global presence — but for now there are franchises and we need to include that in our documentation and planning processes