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
 
(36 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Product List==  
+
==Product List==
see [http://gforge.hl7.org/gf/download/trackeritem/999/1075/Product_Brief_2009.xls Product Brief Template]
+
 
 +
[[Image:ProductList_1.png|600px|Product List Relationships and Categories]]
 +
===Product Briefs - origins===
 +
*see [http://gforge.hl7.org/gf/download/trackeritem/999/1075/Product_Brief_2009.xls Product Brief Template]
 +
*Microsoft Excel Version (2009-12-17) of [http://gforge.hl7.org/gf/download/docmanfileversion/5395/6761/Product_Matrix_2009_v12.xls Product List]
 +
*[[Product List FAQ]]<br>
 +
Summary Stats (2010-06-22): Products - 96 (95 having material on wiki)<br/>
 +
Steward-reviewed (reviewed by steward Work Group) - 84 (88% complete) <br/>
 +
Marketing-reviewed - 52
 +
*List of product [[:CATEGORY:Products|category pages]]
 +
 
 +
 
 
===Health Information '''''Exchange''''' Standards===
 
===Health Information '''''Exchange''''' Standards===
====[[Product_V3#Foundation|Foundation]]====
+
[[Image:ProductList_2.png|600px|Product List Health Information Exchange Subcategories]]
* [[Product_V3_RCL|Refinement, Constraint, and Localization]] to version 3 Messages
+
 
* [[Product_RIM|Reference Information Model (RIM)]]- see Modeling Standards
+
<br/>
* XML and UML Implementation Technology Specification - [[Product_ITS_DT|Data Types]]  
 
* [[Product_ITS_DT|Data Types]] - Abstract Specification
 
* [[Product_CTS|Common Terminology Services]] -see Services
 
*[[Product_GELLO|GELLO]] A Common Expression Language - see Knowledge Representation Standards
 
*[[Product_ITS_Transport|Transport Specification]] - MLLP
 
*[[Product_ITS_Transport|Transport Specification]] - ebXML, Release 1
 
* [[Product_Sec_RBAC|Role-based Access Control Healthcare Permission Catalog]], Release 1
 
  
====Messaging====
+
====Version 2====
*[[Product_V3 |Version 3 (V3)]]
 
 
*[[Product_V2 | Version 2 (V2)]]
 
*[[Product_V2 | Version 2 (V2)]]
 +
**[[Product_V2_IG|Version 2.x Implementation Guides]]
 
**[[Product_V2_XML | V2 XML]]
 
**[[Product_V2_XML | V2 XML]]
====Documents====
+
 
 +
====[[Product_V3|Version 3]] (V3)====
 +
 
 +
 
 +
=====[[Product_V3#Foundation|Foundation]]=====
 +
*ANSI/HL7 V3 RIM, R1-2003; HL7 Version 3 Standard: [[Product_RIM|Reference Information Model (RIM)]], Release 1 - see Modeling Standards
 +
* [[Product_Vocabulary|Vocabulary Specifications]]- see Modeling Standards
 +
*ANSI/HL7 V3 DT, R1-2004; HL7 Version 3 Standard: [[Product_DT|Data Types]] - Abstract Specification, Release 1
 +
*ANSI/HL7 V3 RCL: R1-2003, R2-2007; HL7 Version 3 Standard: [[Product_V3_RCL|Refinement, Constraint, and Localization]] to version 3 Messages
 +
*XML Implementation Technology Specification (ITS) - [[Product_ITS_DT|Data Types]]
 +
**ANSI/HL7 V3 XMLITSDT, R1-2004; HL7 Version 3 Standard: XML Implementation Technology Specification - Data Types
 +
***HL7 V3 ITS, R2; XML Implementation Technology Specification R2 Guide, Release 1, Informative 2008May
 +
**HL7 V3 XMLITS_DT1.1, R1; XML ITS Data Types R1.1, Informative 2010Jan
 +
**HL7 V3 ISO DT, R1; R2-2009 ISO Datatypes 2009Sept
 +
**ANSI/HL7 V3 UMLITSDT, R1-2004; HL7 Version 3 Standard: UML Implementation Technology Specification - Data Types - defunct with ISO Datatypes; Work Group considering withdrawal.
 +
*XML [[Product_ITS_XML|ITS Structures]]
 +
**ANSI/HL7 V3 XMLITSSTR, R1-2005: HL7 Version 3 Standard: XML Implementable Technology Specification for V3 Structures; XML Structure R1 - 9/26/2005
 +
**HL7 V3 XMLITSSTR1.1, R1; XML Structure R1.1, 2009Sept
 +
**HL7 V3 ITS, R2; XML Structure R2 - 2010May. 
 +
**HL7 V3 ITS RIMSR, R1; RIM Serializations R1 - 2010May
 +
*[[Product_hData|hData Specifications]]
 +
*ANSI/HL7 V3 CTS, V1-2005, ISO/HL7 27951:2009(E); HL7 Version 3 Standard: [[Product_CTS|Common Terminology Services]], Release 1 -see Services
 +
*ANSI/HL7 V3 GELLO, R2-2010; HL7 Version 3 Standard: [[Product_GELLO|GELLO]]: A Common Expression Language, Release 2- see Knowledge Representation Standards
 +
*[[Product_ITS_Transport|Transport Specifications]]
 +
**ANSI/HL7 V3 TRMLLP, R2-2006; HL7 Version 3 Standard: [[Product_ITS_Transport#Product_Name_-_Transport_Specification:_MLLP.2C_Release_2|Transport Specification - MLLP, Release 2]]
 +
** ANSI/HL7 V3 TR ebXML, R1-2008; HL7 Version 3 Standard: [[Product_ITS_Transport#Product_Name_-_HL7_V3_Transport_Specification_-_ebXML.2C_Release_2|Transport Specification - ebXML, Release 1]]
 +
**[[Product_ITS_Transport#Product_Name_-_Transport_Specification:_Removable_Media|Transport Specification: ISO 9660 Removable Media Release 1]]
 +
*ANSI/HL7 V3 RBAC, R1-2008; HL7 Version 3 Standard: [[Product_Sec_RBAC|Role-based Access Control Healthcare Permission Catalog]], Release 1
 +
<!--
 +
*[http://www.hl7.org/dstucomments/ DSTU] - <s>HL7 V3 Templates - HL7 Version 3 Standard: Specification and Use of Reusable Constraint Templates, Release 2;</s> ends Feb 2010, not promoting to Normative
 +
-->
 +
*HL7 V3 MODELS, R1 (3rd Normative Ballot in May 2010) - [[Product_V3MODELS|Core Principles and Properties of V3 Models]]
 +
*HL7 V3 MIF, R1 (I1 May 2010) - [[Product_V3MIF|Model Interchange Format (MIF)]]
 +
 
 +
=====Messaging=====
 +
*[[Product_V3 |Version 3 (V3) Messaging]]
 +
 
 +
=====Documents=====
 
*[[Product_CDA | Clinical Document Architecture (CDA)]]
 
*[[Product_CDA | Clinical Document Architecture (CDA)]]
**CDA R2 [[Product_CDA_R2_IG |Implementation Guides]]
+
**CDA R2 [[Product_CDA_R2_IG_CommonClinDocs |Implementation Guides for Common Clinical Documents]] such as H&P, Progress Note, etc.
**:[[Product_CCD | Continuity of Care Document (CCD)]]
+
**CDA R2 [[Product_CDA_R2_IG |Implementation Guides]] for specialized or unstructured clinical documents
**:[[Product_Claims_Attachments | Claims Attachments]]
+
**[[Product_CCD | Continuity of Care Document (CCD)]]
 +
**[[Product_Claims_Attachments | Claims Attachments]]
  
====Services====
+
=====Services=====
 
*[[Product_CTS|Common Terminology Services (CTS)]]
 
*[[Product_CTS|Common Terminology Services (CTS)]]
 +
*HL7 Version 3 Standard: [[Product_PASS | Privacy, Access and Security Services (PASS)]]
 
*HL7 Version 3 Methodology: [[Product_SOA4HL7|Service Oriented Architecture; Service Definition]], Release 1
 
*HL7 Version 3 Methodology: [[Product_SOA4HL7|Service Oriented Architecture; Service Definition]], Release 1
  
Line 37: Line 80:
 
**[[Product_PracGuidSOA|Practical Guide to SOA in Healthcare]]
 
**[[Product_PracGuidSOA|Practical Guide to SOA in Healthcare]]
 
*[[Product_RIM|Reference Information Model (RIM)]]
 
*[[Product_RIM|Reference Information Model (RIM)]]
*[[Product_SAEAF|Enterprise Architecture Specification (SAEAF)]]
+
* [[Product_Vocabulary|Vocabulary Specifications]]
 +
*[[Product_SAIF|SAIF]] - the Services-Aware Interoperability Framework, formerly known as SAEAF - Services-Aware Enterprise Architecture Specification
  
 
===Application '''''Functional Specifications'''''===
 
===Application '''''Functional Specifications'''''===
EHR-S FM, PHR-S FM, EIS SFM, RLUS SFM, DSS SFM, CRFQ SFM
+
System Functional Models and Functional Profiles, Service Functional Models
 +
 
 
*[[Product_EHR_FM|Electronic Health Record Functional Model (EHR FM)]]
 
*[[Product_EHR_FM|Electronic Health Record Functional Model (EHR FM)]]
 +
**HL7 [[Product_EHR_AO_FP|Ambulatory Oncology Functional Profile]], in development
 
**HL7 [[Product_EHR_BH_FP|EHR Behavioral Health Functional Profile]]
 
**HL7 [[Product_EHR_BH_FP|EHR Behavioral Health Functional Profile]]
 
**HL7 [[Product_EHR_CH_FP|EHR Child Health Functional Profile]]
 
**HL7 [[Product_EHR_CH_FP|EHR Child Health Functional Profile]]
 
**HL7 [[Product_EHR_CR_FP|EHR Clinical Research Functional Profile]]
 
**HL7 [[Product_EHR_CR_FP|EHR Clinical Research Functional Profile]]
 +
**HL7 [[Product_EHR_LTC_FP|EHR System Long Term Care Functional Profile]]
 +
**HL7 [[Product_EHR_RMES_FP| Records Management and Evidentiary Support Functional Profile]]
 +
**HL7 [[Product_EHR_VR_FP|Vital Reporting Functional Profile]], in development
 
**[http://www.hl7.org/dstucomments/ DSTU]: [[Product_EHR_LM| HL7 EHR Lifecycle FM]] (EHR/LM), Release 1; ends September 2010
 
**[http://www.hl7.org/dstucomments/ DSTU]: [[Product_EHR_LM| HL7 EHR Lifecycle FM]] (EHR/LM), Release 1; ends September 2010
 
*[http://www.hl7.org/dstucomments/ DSTU]: [[Product_PHR_FM|Personal Health Record System Functional Model (PHR-S FM)]], Release 1; ends December 2010
 
*[http://www.hl7.org/dstucomments/ DSTU]: [[Product_PHR_FM|Personal Health Record System Functional Model (PHR-S FM)]], Release 1; ends December 2010
*[[Product_EIS_SFM|Entity Identification Service Functional Model (EIS SFM)]]
+
*[[Product_EIS_SFM|(Entity) Identification Service Functional Model (EIS SFM)]] aka Identity Cross-Reference Service Functional Model (IXS)
 
*[[Product_RLUS_SFM|Retrieve Locate Update Service Functional Model (RLUS SFM)]]
 
*[[Product_RLUS_SFM|Retrieve Locate Update Service Functional Model (RLUS SFM)]]
 
*[http://www.hl7.org/dstucomments/ DSTU]: [[Product_DSS_SFM|Decision Support Service Functional Model (DSS SFM)]]
 
*[http://www.hl7.org/dstucomments/ DSTU]: [[Product_DSS_SFM|Decision Support Service Functional Model (DSS SFM)]]
*Healthcare, Community Services and Provider Directory Service Functional Model (SPDIR SFM)
+
*[[Product_SPDIR_SFM|Healthcare, Community Services and Provider Directory Service Functional Model]] (SPDIR SFM)
 
*[http://www.hl7.org/dstucomments/ DSTU]: HL7 Version 3 [[Product_RR_CRFQ|Standard: Regulated Studies; Clinical Research Filtered Query (CRFQ) Service Functional Model (SFM)]], Release 1; ends May 2010
 
*[http://www.hl7.org/dstucomments/ DSTU]: HL7 Version 3 [[Product_RR_CRFQ|Standard: Regulated Studies; Clinical Research Filtered Query (CRFQ) Service Functional Model (SFM)]], Release 1; ends May 2010
  
Line 65: Line 114:
 
Ongoing and annual review, maintenance, and endorsement of Product Definitions
 
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
 
*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.
+
*Updates to products:  
 +
*#Each WGM cycle, review list of NIBs to identify and update Product Briefs for new items ready for ballot or updates to existing Products.
 +
*#Before each Plenary WGM, review list of products to check for ANSI 5-year anniversary, DSTU expiration, etc. requiring re-affirmation or withdrawal.
 +
*#Review of existing Product Briefs by a Work Group 'steward' annually can be
 +
*#*a Work Group conference call agenda item to discuss changes to a Product Brief, including any known implementations or case studies
 +
*#*an individual who reports his/her findings on the products to the Work Group.  
 
*Evaluate potential for expired products or standards: with DSTU expiration, withdrawal of ANS standard, replacement?
 
*Evaluate potential for expired products or standards: with DSTU expiration, withdrawal of ANS standard, replacement?
 +
[[Category:Products]]
 +
 +
==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

Latest revision as of 15:06, 9 November 2010

Product List

Product List Relationships and Categories

Product Briefs - origins

Summary Stats (2010-06-22): Products - 96 (95 having material on wiki)
Steward-reviewed (reviewed by steward Work Group) - 84 (88% complete)
Marketing-reviewed - 52


Health Information Exchange Standards

Product List Health Information Exchange Subcategories


Version 2

Version 3 (V3)

Foundation
Messaging
Documents
Services

Health Information Knowledge Representation Standards

Arden Syntax, SPL, GELLO

Modeling Standards

Application Functional Specifications

System Functional Models and Functional Profiles, Service Functional Models

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:
    1. Each WGM cycle, review list of NIBs to identify and update Product Briefs for new items ready for ballot or updates to existing Products.
    2. Before each Plenary WGM, review list of products to check for ANSI 5-year anniversary, DSTU expiration, etc. requiring re-affirmation or withdrawal.
    3. Review of existing Product Briefs by a Work Group 'steward' annually can be
      • a Work Group conference call agenda item to discuss changes to a Product Brief, including any known implementations or case studies
      • an individual who reports his/her findings on the products to the Work Group.
  • 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