Kudos to Motorcycle Guy (aka Keith Boone) for Implementation Technology Specifications. It puts in context four separate efforts to simplify the XML representation of clinical information in HL7 Version 3 and CDA and to achieve a RESTful URL. I know I speak for a lot of people that have the greatest respect for the precision with which clinical data is represented in its V3 products but feel the transparency of the resulting XML is an important barrier to adoption.
One hopes these efforts include a program of diet and exercise that is effective in reducing OID metastasis.
Through Clayton Christiansen’s work on disruptive technology we learn that designing for the high end of the requirement space is far from being a bonus that tops off a good design effort. It introduces nearly gratuitous complexity that makes the product more complex and therefore automatically less accessible to the majority of the market. OIDs are a clear example of such high-end design.
I applaud my many friends in HL7 for taking this on and Keith for finding the time to participate and report on it in such a lucid manner.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Gartner Top 10 Strategic Technology Trends for 2016
Strategic technology trends are rapidly changing disruptive trends with significant potential for enterprise impact over the next three...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.