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

Difference between revisions of "RIMBAA in the HL7 Roadmap"

From HL7Wiki
Jump to navigation Jump to search
Line 2: Line 2:
  
 
The main [[RIMBAA]] WG efforts fit within strategy 3 (below).  
 
The main [[RIMBAA]] WG efforts fit within strategy 3 (below).  
−
#The collection and publication of a set of best practices related to the implementation of HL7 v3, and  
+
#The collection and publication of a set of best practices (or: HL7 v3 implementation patterns) related to the implementation of HL7 v3, and  
 
#Working with third parties to create re-usable software components and tools to facilitate an easier implementation process for future implementers.  
 
#Working with third parties to create re-usable software components and tools to facilitate an easier implementation process for future implementers.  
  
Line 18: Line 18:
 
(updated: 2010-08-16)
 
(updated: 2010-08-16)
  
−
==SMART (TSC)==
+
==HL7 strategic initiative - criteria==
−
In 2010 the TSC has added some details to strategy 3:
+
Version 1.9 (August 3, 2010) of this TSC document has the objective to further clarify the HL7 Strategic Initiatives by providing concrete criteria upon which progress against each of the initiatives can be assessed.
  
−
Facilitate HL7 standards adoption and implementation. Description: Contribute (often in collaboration with other groups) solutions that make HL7 implementation easier.
+
For strategy 3 it contains the following (note: highlighting by the editor)
−
*Practicalize the HDF to Develop an example tool-based methodology for implementing one example V3 message or CDA template
+
 
−
*Teach it as a complete course on this methodology over “n?” sessions to a class with “modest” HL7/HIT experience
+
*Global adoption has increased
−
*Create a workbook of these message/CDA template definitions and then publishing them
+
**Description: "Adoption" is a decision to implement or use HL7. It can refer to choosing HL7 standards, incorporating HL7 standards into the "outside world" (external to HL7) (e.g. RFPs, strategies, specifications, software), etc.  
−
*Lead “connectathons” to demonstrate the implementability and usefulness of HL7 standards
+
**Example projects:
−
**Rene: assumes that people have already build things..
+
**#Establish a process for annually assessing the number of countries requiring the use of HL7.  
−
*Provide conformance testing criteria and services
+
**#Establish HL7 branch offices in Europe, Asia, South America, Africa.
−
**Rene: most implementers don't like anything that smells of certification, a freebie texting server, hosted somewhere online, or better yet: testing software one can download, will certainly be welcomed.
+
*'''Implementation of HL7 standards has gotten easier'''
−
*Review implementation experiences as part of each DESD [Rene: that's the Domain Experts Steering Devision] Face to Face meeting, identify obstacles and develop approaches to overcome implementation obstacles by Sept 2010.
+
**Description: "Implementation" means that a "vendor product" is installed in a live environment;
−
**Rene: interesting - curious as to why the DESD is seen as the most appropriate party to do this. I'd hope we as RIMBAA could also contribute to this, see my blogpost at [http://www.ringholm.de/column/how_to_lower_the_hurdle_for_HL7_v3_implementers.htm]
+
**Example projects:
−
*Participate in OHT with HL7 IP and information artifacts and examples
+
**#Establish a process for annually assessing the extent to which HL7 is used within a locale (because a growing number of implementations is a surrogate marker that implementation is getting easier).
−
**Rene: examples!
+
**#Define requirements for a testing harness and sandbox environment for validating HL7 V3 artifacts against the published specifications leveraging existing tooling. (V3 artifacts include messages, templates, CDA, service etc.)
−
*Description and example of building a V3 message profile/template.
+
**#'''Develop and secure TSC endorsement for a strategy for use of tooling to support implementation activities (e.g. RIMBAA, servlets).'''
−
*Develop v2 to v3 maps for domains well supported by v2
+
*End to end implementation guide infrastructure has been developed
−
**Rene: Robert Worden's activity..
+
**Description: Implementation guides further profile or characterize the use of an HL7 standard. Infrastructure supports publishing, development of sample instances, etc.
−
*Determine other methods for publishing/delivering our standards – e.g. publish on KINDLE or DITA
+
**Example projects:
−
**Rene: I hardly think the publication method is of interest - it's the content that needs to be different to suit the implementers
+
**#Publish standardized externally developed implementation guides and provide registration mechanism. (Note - This does NOT mean balloting – Implementation guides will remain real/project/scope specific – but will be registered and made available through HL7 in a consistent format).  
−
*V2/V3 strategy to help v2 users understand and help them migrate to V3 where they have requirements for V3 functionality.
+
**#Develop HL7-wide processes and guidelines for the development and publication of CDA Implementation Guides.
−
**Rene: sounds like a business-level argument
+
**#Complete the requirements for using our existing V3 tooling to create a standardized format for a V3 messaging implementation guide including output features commensurate with the V2 messaging workbench (e.g. contract language). Note: This is just the requirements step; work will continue on this in subsequent years.
−
*Require implementation guidance be part of all DESD [Rene: that's the Domain Experts Steering Devision] standards projects
+
*'''HL7 Education Plan has been developed'''
−
**Rene: I'd like to see an example of the type of implementation guidance they're looking to create
+
**Description: The number of trained HL7 V2 implementers far surpasses the number of trained V3/CDA implementers. An education plan lays the HL7 strategy for dramatically increasing the number of folks with V3/CDA implementation-level knowledge.
−
*Develop means of creating an example for each specification
+
**Example projects:
−
**Rene: examples!
+
**#Survey the overall HL7 international community regarding their needs in terms of HL7 Education.
−
*Look at establishing cross tutorial review teams, to improve tutorial quality.
+
**#Develop an internationally relevant Education Plan that includes such components as curriculum development, HL7 internship, academic research network, text books, eLearning. An objective of the plan is to figure out how to attain the same level of implementation knowledge in V3/CDA as there currently exists for V2.
−
**Rene: always a good idea, but in order to facilitate the adoption of standards one may need different tutorials, ones not primarily oriented at the methodology.
+
**#(added to the list, not present in the original) '''Publication of best practices and HL7 v3 implementation patterns. Tutorials covering same.'''
−
*(new, see [http://www.ringholm.de/column/how_to_lower_the_hurdle_for_HL7_v3_implementers.htm]) A "HL7 v3 for implementers book": I frequently get asked if there's a v3 book for implementers. If it were to describe an implementers view of the standard, combined with best practices and implementation guidance, and pointers to additional implementation oriented information and tools, it would be an invaluable resource. The current books related to HL7 v3 are all geared towards the standards developers. The creation of such a book would require an up-front investment by whomever is going to write it.
 
−
*(new, see [http://www.ringholm.de/column/how_to_lower_the_hurdle_for_HL7_v3_implementers.htm]) Examples, examples, examples: Examples (HL7 v3 XML Instances) are of key importance in understanding the standard, for testing, but also for software development (quite often development is driven by the available examples). The published HL7 v3 standard contains a few examples - which don't validate, and are old. here has been an initiative a couple of years ago to 'force' the standards developers to publish examples along with their domain content - but apparently that initiative has failed, for there are next to none examples,
 
−
*(new, see [http://www.ringholm.de/column/how_to_lower_the_hurdle_for_HL7_v3_implementers.htm]) Tools for implementers: Availability of off-the-shelf APIs and other open source tooling, guidance as how one could use cross-industry generic approaches and tools to implement HL7 version 3. It is encouraging that a number of tools has become available to aid the implementation of HL7 v3, notably MARC-HI Everest, a MIF based code generator. with v3
 
−
*(new, see [http://www.ringholm.de/column/how_to_lower_the_hurdle_for_HL7_v3_implementers.htm]) Stable software processable HL7 v3 specifications: Implementers either base their implementations on the XML Schema, or (better yet) on the MIFs. Neither the Schema, nor the MIF are normative/stable. Backwards compatibility of either format isn't assured by the standards development process. MIF have to become normative, and be subject to backwards compatibility rules, to really offer implementers the chance to build their software based on a software processable version of the HL7 v3 specifications.
 
−
*(new, see [http://www.ringholm.de/column/how_to_lower_the_hurdle_for_HL7_v3_implementers.htm]) Hotline e-mail address: If as an implementer one has a question, you get lost in the 50+ e-mail lists that are available on the hl7.org website. It should be relatively easy to create a support@hl7.org e-mail address, publish it far and wide as part of the marketing efforts, and triage/route the e-mails to the appropriate e-mail list.
 

Revision as of 08:47, 16 August 2010

The HL7 Roadmap defines a number of priorities.

The main RIMBAA WG efforts fit within strategy 3 (below).

  1. The collection and publication of a set of best practices (or: HL7 v3 implementation patterns) related to the implementation of HL7 v3, and
  2. Working with third parties to create re-usable software components and tools to facilitate an easier implementation process for future implementers.
STRATEGY 3 - Facilitate HL7 standards adoption and implementation.
Description: Contribute (often in collaboration with other groups) solutions 
that make HL7 implementation easier.

To a lesser degree RIMBAA represents the HL7 v3 implementer community in the standards development process (strategy 5, below). RIMBAA does provide feedback and new proposals based on implementation experiences (e.g. the new Context Conduction and a RIM ITS). 

STRATEGY 5 - Ensure broad and encompassing stakeholder engagement in the standards 
development process.
Description: Ensure a clear process whereby stakeholders such as clinicians, 
technical experts, and policy makers can contribute to the development of HL7 standards.

(updated: 2010-08-16)

HL7 strategic initiative - criteria

Version 1.9 (August 3, 2010) of this TSC document has the objective to further clarify the HL7 Strategic Initiatives by providing concrete criteria upon which progress against each of the initiatives can be assessed.

For strategy 3 it contains the following (note: highlighting by the editor)

  • Global adoption has increased
    • Description: "Adoption" is a decision to implement or use HL7. It can refer to choosing HL7 standards, incorporating HL7 standards into the "outside world" (external to HL7) (e.g. RFPs, strategies, specifications, software), etc.
    • Example projects:
      1. Establish a process for annually assessing the number of countries requiring the use of HL7.
      2. Establish HL7 branch offices in Europe, Asia, South America, Africa.
  • Implementation of HL7 standards has gotten easier
    • Description: "Implementation" means that a "vendor product" is installed in a live environment;
    • Example projects:
      1. Establish a process for annually assessing the extent to which HL7 is used within a locale (because a growing number of implementations is a surrogate marker that implementation is getting easier).
      2. Define requirements for a testing harness and sandbox environment for validating HL7 V3 artifacts against the published specifications leveraging existing tooling. (V3 artifacts include messages, templates, CDA, service etc.)
      3. Develop and secure TSC endorsement for a strategy for use of tooling to support implementation activities (e.g. RIMBAA, servlets).
  • End to end implementation guide infrastructure has been developed
    • Description: Implementation guides further profile or characterize the use of an HL7 standard. Infrastructure supports publishing, development of sample instances, etc.
    • Example projects:
      1. Publish standardized externally developed implementation guides and provide registration mechanism. (Note - This does NOT mean balloting – Implementation guides will remain real/project/scope specific – but will be registered and made available through HL7 in a consistent format).
      2. Develop HL7-wide processes and guidelines for the development and publication of CDA Implementation Guides.
      3. Complete the requirements for using our existing V3 tooling to create a standardized format for a V3 messaging implementation guide including output features commensurate with the V2 messaging workbench (e.g. contract language). Note: This is just the requirements step; work will continue on this in subsequent years.
  • HL7 Education Plan has been developed
    • Description: The number of trained HL7 V2 implementers far surpasses the number of trained V3/CDA implementers. An education plan lays the HL7 strategy for dramatically increasing the number of folks with V3/CDA implementation-level knowledge.
    • Example projects:
      1. Survey the overall HL7 international community regarding their needs in terms of HL7 Education.
      2. Develop an internationally relevant Education Plan that includes such components as curriculum development, HL7 internship, academic research network, text books, eLearning. An objective of the plan is to figure out how to attain the same level of implementation knowledge in V3/CDA as there currently exists for V2.
      3. (added to the list, not present in the original) Publication of best practices and HL7 v3 implementation patterns. Tutorials covering same.
Retrieved from "https://wiki.hl7.org/w/index.php?title=RIMBAA_in_the_HL7_Roadmap&oldid=39995"