Talk:ConCall-20070227

From HL7 TSC
Revision as of 16:18, 6 March 2007 by Virginia (talk | contribs) (New page: In our last call, we talked about "our the 3 divisions in the TSC OK"? I know its splicing hairs but want to add some two cents: - SOA is a technology. It also has semantic patterns. Bu...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

In our last call, we talked about "our the 3 divisions in the TSC OK"? I know its splicing hairs but want to add some two cents: - SOA is a technology. It also has semantic patterns. But mostly, there are specific specifications which belong under particular functional domains. EIS - should be under patient administration. Descision Support - under Decision Support. CTS - Vocab. Resource Locator - not sure. These are functional content related specs, not F&T. - Decision Support: has components of all three. Arden Syntax is definitely F&T, the Infobutton and Order Set domains are functional content and seem more related to DE, so does the Decision Support SOA spec. - CMETs and Shared Messages - aren't these semantic patterns? - In fact, it would not be surprising for domains to have documents, messages, and services all defined and domain experts working with all three. - A bit of gray is a good thing. - I think one of the main benefits of dividing by three is that it divided management and communication into more managable chunks. A long time ago, I was part of a reorg where this was done arbitrarily - Team A, Team B, Team C. It worked great. While that might be radical to consider now, the theme of it might be healthy. Let people know that the main purpose is not to categorize, but instead to reduce the amount of people in meetings brainstorming and making decisions so that work can get done.