Difference between revisions of "Marketing Committee"
Rene spronk (talk | contribs) |
|||
| Line 1: | Line 1: | ||
[[Image:Sunset_218.jpg|200px|right|thumb|Next Marketing meeting]] | [[Image:Sunset_218.jpg|200px|right|thumb|Next Marketing meeting]] | ||
| − | The HL7 Marketing Committee’s primary responsibility is to develop a promotion and marketing strategy for increasing the visibility of HL7 and advancing HL7 Standards globally. The focus of the | + | The HL7 Marketing Committee’s primary responsibility is to develop a promotion and marketing strategy for increasing the visibility of HL7 and advancing HL7 Standards globally. The focus of the committee activities is on the strategic aspects of marketing, not on day-to-day communications or PR issues. |
== Strategic Planning Task Force == | == Strategic Planning Task Force == | ||
Revision as of 15:43, 21 May 2007
The HL7 Marketing Committee’s primary responsibility is to develop a promotion and marketing strategy for increasing the visibility of HL7 and advancing HL7 Standards globally. The focus of the committee activities is on the strategic aspects of marketing, not on day-to-day communications or PR issues.
Strategic Planning Task Force
The Strategic Planning Task Force is a special project which is focused on organizational strategy and process redesign for HL7’s future. The initiative began in August 2005 at the HL7 Board Retreat where a process for developing long-term plans was determined. The work of the Task Force has an overlap with the activities of the Marketing Committee. The activities of the Marketing Committee will be dormant (i.e. be carried out in the context of the Task Force) until a later point in time.
Products
See HL7 Products.
- HL7 Messaging V2 can be positioned as:
- An HL7 success story it delivered results and has shown the way. Position V2.0 as success for early movers way back when, but also as legacy pointing out its short-comings for the 21st century (i.e. HL7 is response to the marketplace and its requirements)
- Important existing work-horse on which real-world deployments are based and this will continue to exist in production mode for some time to come.
- A standard that will continue to get maintained (i.e. errata) and supported.
- HL7 Messaging V3 and HL7 CDA V3 can be positioned as:
- The only internationally accepted, industry strength, standard to achieve interoperability within and across the HC enterprise.
- The standard upon which new deployments should be based
- The foundational standard of choice for regional, national and trans-national exchange of health information.
- Designed for the 21st century (i.e. HL7 is responsive to the marketplace and its requirements)
- Note: We can define V3 as being all RIM-derived, HDF based models, and specifications related to the transmission thereof.
- Service specifications (e.g. CTS II). The problem with service specifications is that they could be based on -or harmonized with- RIM models (but not necessarily so). In many (if not most, maybe even all?) cases, you can take a messaging or service based approach for the same business functionality. Which is more appropriate in which circumstances is still subjective, some more obvious than others. Service definitions could be part of the HDF if the HDF is rewritten to be applicable for service as well as messaging environments.
- Functional specifications (e.g. EHR, RLUS).
- CCOW
- Arden Syntax
Marketing Plan
The main activity of the comittee is the creation of a HL7 Marketing Plan. The goal of this document is to set forth a promotion and marketing plan for increasing the visibility of the HL7 organizations and advancing HL7 standards globally.
The Marketing Plan describes many aspects, the following of which are contained in this Wiki:
- HL7 Mission
- Stakeholder Analysis
