This wiki has undergone a migration to Confluence found Here
Difference between revisions of "AID in the HL7 Roadmap"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (Created page with "The 2012 HL7 Roadmap defines a number of priorities. The main AID WG efforts fit within strategy 3 (below). #The collection and publication of a set of best practices (or:...") |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | The | + | The 2014 HL7 Roadmap defines a number of priorities. |
The main [[AID]] WG efforts fit within strategy 3 (below). | The main [[AID]] WG efforts fit within strategy 3 (below). | ||
| Line 5: | Line 5: | ||
#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. | ||
| − | *( | + | *(2014) STRATEGY 3 - HL7 Implementation: Develop standards that are easier to implement and more responsive to customer needs |
| − | **2.3.2 ( | + | **2.3.2 (2014) HL7 Standards implementation has gotten easier. Description: "Implementation" refers to the use of HL7 material in the development of software applications and messaging systems, for the exchange of health information. |
| − | **2.3.4 ( | + | **2.3.4 (2014) Tooling strategy has been developed. Description: Efficiency in HL7 implementation is supported by tools. ... Componets of a tooling strategy include, but are not limited to, prioritization of new tool development vs. ongoing support of existing tools, process for evaluating and incorporating externally developed tools. |
To a lesser degree RIMBAA represents the ''HL7 v3 implementer community'' in the standards development process. AID does provide feedback and new proposals based on implementation experiences (e.g. the new [[Context Conduction]], [[RIM ITS]]). | To a lesser degree RIMBAA represents the ''HL7 v3 implementer community'' in the standards development process. AID does provide feedback and new proposals based on implementation experiences (e.g. the new [[Context Conduction]], [[RIM ITS]]). | ||
| − | *( | + | *(2014) STRATEGY 1 |
| − | **2.1.5 ( | + | **2.1.5 (2014) Key stakeholder groups have been identified, with value propositions and action plans for engaging each group. Description: Groups that play a valuable role in the development of HL7 standards, whether through technical development, functional requirement identification, etc, have been defined. There is a written plan that describes how HL7 will seek to engage and involve each group in the standards development process. |
| − | (updated: | + | (updated: 2014-01-20) |
Latest revision as of 01:22, 22 January 2014
The 2014 HL7 Roadmap defines a number of priorities.
The main AID WG efforts fit within strategy 3 (below).
- The collection and publication of a set of best practices (or: implementation patterns) related to the implementation of HL7's standards, and
- Working with third parties to create re-usable software components and tools to facilitate an easier implementation process for future implementers.
- (2014) STRATEGY 3 - HL7 Implementation: Develop standards that are easier to implement and more responsive to customer needs
- 2.3.2 (2014) HL7 Standards implementation has gotten easier. Description: "Implementation" refers to the use of HL7 material in the development of software applications and messaging systems, for the exchange of health information.
- 2.3.4 (2014) Tooling strategy has been developed. Description: Efficiency in HL7 implementation is supported by tools. ... Componets of a tooling strategy include, but are not limited to, prioritization of new tool development vs. ongoing support of existing tools, process for evaluating and incorporating externally developed tools.
To a lesser degree RIMBAA represents the HL7 v3 implementer community in the standards development process. AID does provide feedback and new proposals based on implementation experiences (e.g. the new Context Conduction, RIM ITS).
- (2014) STRATEGY 1
- 2.1.5 (2014) Key stakeholder groups have been identified, with value propositions and action plans for engaging each group. Description: Groups that play a valuable role in the development of HL7 standards, whether through technical development, functional requirement identification, etc, have been defined. There is a written plan that describes how HL7 will seek to engage and involve each group in the standards development process.
(updated: 2014-01-20)
