This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Product List"
Jump to navigation
Jump to search
| Line 75: | Line 75: | ||
*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]] | [[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 | ||
Revision as of 04:24, 20 January 2010
Contents
- 1 Product List
- 2 Governance and Maintenance
- 3 Suggested Additions
Product List
- see Product Brief Template
- Microsoft Excel Version (2009-12-17) of Product List
- Product List FAQ
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
- Reference Information Model (RIM)- see Modeling Standards
- Vocabulary Specifications- see Modeling Standards
- Data Types - Abstract Specification
- Refinement, Constraint, and Localization to version 3 Messages
- XML and UML Implementation Technology Specification - Data Types
- Common Terminology Services -see Services
- GELLO A Common Expression Language - see Knowledge Representation Standards
- Transport Specification - MLLP
- Transport Specification - ebXML, Release 1
- Role-based Access Control Healthcare Permission Catalog, Release 1
Messaging
Documents
Services
- Common Terminology Services (CTS)
- HL7 Version 3 Methodology: Service Oriented Architecture; Service Definition, Release 1
Health Information Knowledge Representation Standards
Arden Syntax, SPL, GELLO
Modeling Standards
- Healthcare Development Framework (HDF)
- Reference Information Model (RIM)
- Vocabulary Specifications
- Enterprise Architecture Specification (SAEAF)
Application Functional Specifications
EHR-S FM, PHR-S FM, EIS SFM, RLUS SFM, DSS SFM, CRFQ SFM
- Electronic Health Record Functional Model (EHR FM)
- HL7 EHR Behavioral Health Functional Profile
- HL7 EHR Child Health Functional Profile
- HL7 EHR Clinical Research Functional Profile
- DSTU: HL7 EHR Lifecycle FM (EHR/LM), Release 1; ends September 2010
- DSTU: Personal Health Record System Functional Model (PHR-S FM), Release 1; ends December 2010
- (Entity) Identification Service Functional Model (EIS SFM) aka Identity Cross-Reference Service Functional Model (IXS)
- Retrieve Locate Update Service Functional Model (RLUS SFM)
- DSTU: Decision Support Service Functional Model (DSS SFM)
- Healthcare, Community Services and Provider Directory Service Functional Model (SPDIR SFM)
- DSTU: HL7 Version 3 Standard: Regulated Studies; Clinical Research Filtered Query (CRFQ) Service Functional Model (SFM), Release 1; ends May 2010
Clinical Context Management Standards
Implementation Guides
- Implementation/Conformance Work Group Wiki page on 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
