Difference between revisions of "May2006 WGM early adopter lunch"
Brett Esler (talk | contribs) |
Brett Esler (talk | contribs) |
||
| Line 4: | Line 4: | ||
=== Brett Esler === | === Brett Esler === | ||
| − | + | ==== Good ==== | |
Expert sources for clinical and administrative domains means generalist implementors can immediately gain the benefit of many years of experience and knowledge with completely specified models and interactions. | Expert sources for clinical and administrative domains means generalist implementors can immediately gain the benefit of many years of experience and knowledge with completely specified models and interactions. | ||
| − | + | ==== Bad ==== | |
To be an implementor at this point is not easy. It is pretty much necessary to become a modeller to understand how to construct messages. | To be an implementor at this point is not easy. It is pretty much necessary to become a modeller to understand how to construct messages. | ||
| − | + | ==== Challenges ==== | |
Tooling! - need tools that make it possible to find the domains needed, and support constraining content for local implemetation. Implementors should be able to discover what is appropriate based on their specific requirements and be able to assemble basic message profiles. This would make HL7 v3 the best choice from a business perspective as it enables interoperability and reduces the costs of delivering it. | Tooling! - need tools that make it possible to find the domains needed, and support constraining content for local implemetation. Implementors should be able to discover what is appropriate based on their specific requirements and be able to assemble basic message profiles. This would make HL7 v3 the best choice from a business perspective as it enables interoperability and reduces the costs of delivering it. | ||
Revision as of 21:27, 17 May 2006
The early adopter lunch is hosted by the Implementation Committee
Contents
Just Two Minutes
There was useful discussion at the Lunch, with three projects being asked to speak for no more than two minutes each, saying what they liked aabout HL7v3, what they did not like, and what they wanted to see HL7 do for them.
Brett Esler
Good
Expert sources for clinical and administrative domains means generalist implementors can immediately gain the benefit of many years of experience and knowledge with completely specified models and interactions.
Bad
To be an implementor at this point is not easy. It is pretty much necessary to become a modeller to understand how to construct messages.
Challenges
Tooling! - need tools that make it possible to find the domains needed, and support constraining content for local implemetation. Implementors should be able to discover what is appropriate based on their specific requirements and be able to assemble basic message profiles. This would make HL7 v3 the best choice from a business perspective as it enables interoperability and reduces the costs of delivering it.
Bob Grant / Leon Savail
David Dobbs
Discussion
During discussion a number of themes were raised:
- It was suggested that implementation workshops would be useful, where longer could be spent discussing implementation issues with the standard, and how they could be resolved. These sessions would focus on how to use the standard now, rather than on development of the standard which is what we focus on at the WGM
- There were questions about how to implement V3 with Snomed and who was doing it (a number were doing something with live interfaces now, but no-one claimed to be doing full post-co-ordination with Snomed and V3 yet)
